- mice-discuss - lists.micemn.net

Re: Please welcome Fastly to MICE!

by Jason Hanke

There is also a peeringDB API. It might be time for a database driven documentation. Then we could export/import to dns or switch configs. An online request form might be a good start. On Tue, Oct 25, 2016 at 1:56 PM, Richard Laager <rlaager(a)wiktel.com> wrote: > The exchange only cares about the max prefix value if it's larger than > our default route server limit of 1000. That's a big network, and I > think we've only hit that once. I'm not sure we need to bother getting > an explicit number from every network on turn-up. > > On the PeeringDB thing... I've thought about that before too. Is > *requiring* an entry going too far? I'm on the fence about that. > > I see that SIX links the AS number in the participants list to PeeringDB > rather than bgp.he.net. I like the bgp.he.net links, but I should see if > I can find some place on the list to put a PeeringDB link. > > -- > Richard -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Oct. 25, 2016

Re: MICE core switch maintenance window - 10/27/2016 12:30AM-1:00AM CDT

by Richard Laager

On 10/25/2016 09:40 AM, Andrew Hoyos wrote: > My suggestion would be for the formal creation of a technical committee by the board This is something I intend to work on soon, but the tax-exempt thing is higher priority. I'm envisioning: 1) making a page on the MICE website like the following page: https://www.seattleix.net/whos-who 2) asking the board to ACK its contents 3) asking for a MICE-TECH and/or MICE-OPS list be created (depending on whether we have distinct groups and what those people want). I expect at least one list will be closed to members only. -- Richard

Oct. 25, 2016

Re: Please welcome Fastly to MICE!

by Richard Laager

The exchange only cares about the max prefix value if it's larger than our default route server limit of 1000. That's a big network, and I think we've only hit that once. I'm not sure we need to bother getting an explicit number from every network on turn-up. On the PeeringDB thing... I've thought about that before too. Is *requiring* an entry going too far? I'm on the fence about that. I see that SIX links the AS number in the participants list to PeeringDB rather than bgp.he.net. I like the bgp.he.net links, but I should see if I can find some place on the list to put a PeeringDB link. -- Richard

Oct. 25, 2016

Re: Please Welcome Unggoy Broadband to MICE!

by Jason Hanke

Assignment sheet updated On Tue, Oct 25, 2016 at 1:37 PM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > On Tue, Oct 25, 2016 at 01:28:27PM -0500, Richard Laager wrote: >> On 10/25/2016 01:15 PM, anthonyanderberg(a)nu-telecom.net wrote: >> > Anyway NU-Telecom is in 2/0/7 now >> >> The original (off-list) email about the bad port swap said 2/0/2. (I >> checked.) Given that NU-Telecom is actually in 2/0/7, I've fixed that on >> the website. >> >> Unless we hear differently from Jay, the obvious answer is that Unggoy >> Broadband is now assigned 2/0/2. That's what I put on the website, but >> obviously I can change it if need be. > > > Sounds good to me, I updated the port description since there aren't > optics in xe-2/0/2, and we'll leave xe-2/0/7 to NU-Telecom. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Oct. 25, 2016

Re: Please Welcome Unggoy Broadband to MICE!

by Doug McIntyre

On Tue, Oct 25, 2016 at 01:28:27PM -0500, Richard Laager wrote: > On 10/25/2016 01:15 PM, anthonyanderberg(a)nu-telecom.net wrote: > > Anyway NU-Telecom is in 2/0/7 now > > The original (off-list) email about the bad port swap said 2/0/2. (I > checked.) Given that NU-Telecom is actually in 2/0/7, I've fixed that on > the website. > > Unless we hear differently from Jay, the obvious answer is that Unggoy > Broadband is now assigned 2/0/2. That's what I put on the website, but > obviously I can change it if need be. Sounds good to me, I updated the port description since there aren't optics in xe-2/0/2, and we'll leave xe-2/0/7 to NU-Telecom. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016

Re: Please Welcome Unggoy Broadband to MICE!

by Richard Laager

On 10/25/2016 01:15 PM, anthonyanderberg(a)nu-telecom.net wrote: > Anyway NU-Telecom is in 2/0/7 now The original (off-list) email about the bad port swap said 2/0/2. (I checked.) Given that NU-Telecom is actually in 2/0/7, I've fixed that on the website. Unless we hear differently from Jay, the obvious answer is that Unggoy Broadband is now assigned 2/0/2. That's what I put on the website, but obviously I can change it if need be. -- Richard

Oct. 25, 2016

Re: Please Welcome Unggoy Broadband to MICE!

by anthonyanderberg＠nu-telecom.net

Sorry, that's my fault - after the copper switch work a couple weeks ago the my NU-Telecom port 0/0/15 didn't come back up. After different SFP+ didn't fix the issue we moved NU-Telecom to port 2/0/7 but I hadn't gotten documentation cleaned up yet; shoe maker's kid phenomenon I guess. Anyway NU-Telecom is in 2/0/7 now - we haven't had a chance to test 0/0/15 but were going to do that after the upgrade/reboot. Cheers, anthony -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, October 25, 2016 12:51 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Please Welcome Unggoy Broadband to MICE! On Mon, Oct 24, 2016 at 05:04:56PM -0500, Jason Hanke wrote: > Name: Unggoy Broadband LLC > ASN: 393846 > IPv4: 206.108.255.41/24 > IPv6: 2001:504:27:0:6:0276::1/64 > BFD: Available > Contact: support(a)unggoy.net > Route Servers: Yes > Port: Main Switch xe-2/0/7 Umm, I currently show this port for Nu-Telecom and it has been up for 2w, and Nu-Telecom's assigned port of xe-2/0/2 currently has no optics in that port. Perhaps somebody's 7 turned into a 2 or vice-versa wrongly? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016

Re: Please welcome Fastly to MICE!

by Doug McIntyre

On Tue, Oct 25, 2016 at 09:20:52AM -0500, Jason Hanke wrote: > Name: Fastly, Inc > ASN: 54113 > IPv4: 206.108.255.72/24 > IPv4: 206.108.255.73/24 > IPv6: 2001:504:27:0:0:d361::1/64 > IPv6: 2001:504:27:0:0:d361::2/64 > Ports: Main Switch xe-2/0/25, xe-2/0/26 (NO LAG) > Contact: peering(a)fastly.com > > Route Server and website please, I'm checking on BFD support. Sure, I've got the route servers, switch description and reverse PTRs all set for both these and the Unggoy Broadband entry (once the port assignment is cleared up). Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016

Re: Please Welcome Unggoy Broadband to MICE!

by Doug McIntyre

On Mon, Oct 24, 2016 at 05:04:56PM -0500, Jason Hanke wrote: > Name: Unggoy Broadband LLC > ASN: 393846 > IPv4: 206.108.255.41/24 > IPv6: 2001:504:27:0:6:0276::1/64 > BFD: Available > Contact: support(a)unggoy.net > Route Servers: Yes > Port: Main Switch xe-2/0/7 Umm, I currently show this port for Nu-Telecom and it has been up for 2w, and Nu-Telecom's assigned port of xe-2/0/2 currently has no optics in that port. Perhaps somebody's 7 turned into a 2 or vice-versa wrongly? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016

Re: Please welcome Fastly to MICE!

by Doug McIntyre

On Tue, Oct 25, 2016 at 04:35:59PM +0000, Justin Krejci wrote: > For example, I notice we don't have an official position (at least not a documented official position which arguably means we don't have a position) on PTR records for the member IP addresses. I realize PTRs are not significantly important but they can be useful when troubleshooting and having them I feel gives a little extra polish to the exchange in general. ... Documentation and policy writing sucks loads and loads of time out of people, just as an experience point. It is difficult to get anybody to do that sort of thing in general. I've switched on the PTR updates from batches to doing it more on demand on turn up notices from Jay now. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 25, 2016