- mice-discuss - lists.micemn.net

Re: Mice routes via Northern Lights GigaPoP

by Jay Hanke

> I'm back in the office next week and I'll try to get around to contacting > Zayo. Probably later in the week, as I know I'm going to have a bunch of > stuff waiting for me when I get into the office. :) Zayo has been to a MICE meeting and has been approached multiple times they should be aware. You can lead a horse to water... There are a number of carriers who have equipment within 150' of the MICE rack but haven't connected. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 4, 2011

Re: Mice routes via Northern Lights GigaPoP

by David Farmer

On 8/31/11 19:31 CDT, Richard Laager wrote: > On Wed, 2011-08-31 at 19:26 -0500, Mike Horwath wrote: >> On Wed, Aug 31, 2011 at 03:28:00PM -0500, Jeremy Lumby wrote: >>> I have a case where I am seeing 199.199.0.0/16 in BGP via >>> MICE/Northern Lights GigaPoP. I have noticed that traffic to this >>> network takes MICE, however the return traffic is coming in across >>> one of my public Internet connections. I am assuming that either by >>> choice, or by accident that they are not accepting my route via >>> MICE/Northern Lights GigaPoP. I am wondering who would be the best >>> person to chat with about this since MICE does not list a peering >>> contact for Northern Lights GigaPoP in the participants page, and I >>> realize that the correct peering contact might be another level or >>> two deeper. >> >> Zayo (old Onvoy) network. >> >> Didn't we see something like this before when UMN connected things up >> with Zayo not accepting the route updates/insertions? > > FWIW: I'm seeing another possible problem the opposite way. I'm a > customer of Zayo and my routes to minnesota.edu go through the UMN, but > the return traffic goes to Zayo via Level3. Can you give me a prefix? The only routes I'm seeing from Zayo that I'm not accepting are ones that I have a better route to through MICE or a GigaPOP participant. Also, I'm not seeing any routes from AS33362 that are going via Level3, Cogent, TWTC, TransitRail or Internet2 CPS, our upstream Transit providers. Thanks -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 4, 2011

Re: Mice routes via Northern Lights GigaPoP

by David Farmer

Sorry, I'm out of the country and a bit behind on email. We are announcing the routes we learn from MICE to Zayo and VISI, two commercial peers we had prior to the creation of MICE. I've been meaning to contact them and suggest that they peer directly at MiCE. We also announce all of the GigaPOP R&E participants, the state, MnSCU, many of the private colleges, much of K12 in the state, North Dakota Higher Ed and K12, Iowa State and much of ICN, etc... I believe VISI is actually accepting the routes and that Zayo is not accepting the routes. As was discussed on the list I believe they have old static prefix filters in place and are not accepting the routes. I've also been meaning to contact them about that too. But it has been a busy summer, and I haven't had a chance to get to it. I'm back in the office next week and I'll try to get around to contacting Zayo. Probably later in the week, as I know I'm going to have a bunch of stuff waiting for me when I get into the office. :) On 8/31/11 15:28 CDT, Jeremy Lumby wrote: > I have a case where I am seeing 199.199.0.0/16 in BGP via MICE/Northern Lights GigaPoP. I have noticed that traffic to this network takes MICE, however the return traffic is coming in across one of my public Internet connections. I am assuming that either by choice, or by accident that they are not accepting my route via MICE/Northern Lights GigaPoP. I am wondering who would be the best person to chat with about this since MICE does not list a peering contact for Northern Lights GigaPoP in the participants page, and I realize that the correct peering contact might be another level or two deeper. > > Thanks, > Jeremy > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 4, 2011

Re: Bird Help

by James Montz

I am On Sep 2, 2011 4:10 PM, "Jay Hanke" <jayhanke(a)mankatonetworks.net> wrote: > Is someone around build a couple of new bgp sessions for a new carrier > on the route servers? > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > 320 East Liberty Street > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > http://www.mankatonetworks.com > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 3, 2011

Bird Help

by Jay Hanke

Is someone around build a couple of new bgp sessions for a new carrier on the route servers? -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC 320 East Liberty Street Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 2, 2011

Re: Mice routes via Northern Lights GigaPoP

by Matthew Beckwell

Yeahhh... It's by choice-- there are (old/outdated) static prefix filters on Zayo's peering session to the Gigapop. With the addition of MICE to AS57-- there's a lot more diverse traffic headed that direction than there used to be. I'll start a dialog with my contacts over there and see if we can get them to take more of a standard "transit" approach to that session. We have the same problem with our (relatively new) IPv4 prefix...MICE out...Level3/XO return... ~Matthew On Aug 31, 2011, at 3:28 PM, Jeremy Lumby wrote: > I have a case where I am seeing 199.199.0.0/16 in BGP via MICE/Northern Lights GigaPoP. I have noticed that traffic to this network takes MICE, however the return traffic is coming in across one of my public Internet connections. I am assuming that either by choice, or by accident that they are not accepting my route via MICE/Northern Lights GigaPoP. I am wondering who would be the best person to chat with about this since MICE does not list a peering contact for Northern Lights GigaPoP in the participants page, and I realize that the correct peering contact might be another level or two deeper. > > Thanks, > Jeremy > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 1, 2011

Re: Mice routes via Northern Lights GigaPoP

by Richard Laager

On Wed, 2011-08-31 at 19:26 -0500, Mike Horwath wrote: > On Wed, Aug 31, 2011 at 03:28:00PM -0500, Jeremy Lumby wrote: > > I have a case where I am seeing 199.199.0.0/16 in BGP via > > MICE/Northern Lights GigaPoP. I have noticed that traffic to this > > network takes MICE, however the return traffic is coming in across > > one of my public Internet connections. I am assuming that either by > > choice, or by accident that they are not accepting my route via > > MICE/Northern Lights GigaPoP. I am wondering who would be the best > > person to chat with about this since MICE does not list a peering > > contact for Northern Lights GigaPoP in the participants page, and I > > realize that the correct peering contact might be another level or > > two deeper. > > Zayo (old Onvoy) network. > > Didn't we see something like this before when UMN connected things up > with Zayo not accepting the route updates/insertions? FWIW: I'm seeing another possible problem the opposite way. I'm a customer of Zayo and my routes to minnesota.edu go through the UMN, but the return traffic goes to Zayo via Level3. Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 1, 2011

Re: Mice routes via Northern Lights GigaPoP

by Mike Horwath

On Wed, Aug 31, 2011 at 03:28:00PM -0500, Jeremy Lumby wrote: > I have a case where I am seeing 199.199.0.0/16 in BGP via > MICE/Northern Lights GigaPoP. I have noticed that traffic to this > network takes MICE, however the return traffic is coming in across > one of my public Internet connections. I am assuming that either by > choice, or by accident that they are not accepting my route via > MICE/Northern Lights GigaPoP. I am wondering who would be the best > person to chat with about this since MICE does not list a peering > contact for Northern Lights GigaPoP in the participants page, and I > realize that the correct peering contact might be another level or > two deeper. Zayo (old Onvoy) network. Didn't we see something like this before when UMN connected things up with Zayo not accepting the route updates/insertions? -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 1, 2011

Mice routes via Northern Lights GigaPoP

by Jeremy Lumby

I have a case where I am seeing 199.199.0.0/16 in BGP via MICE/Northern Lights GigaPoP. I have noticed that traffic to this network takes MICE, however the return traffic is coming in across one of my public Internet connections. I am assuming that either by choice, or by accident that they are not accepting my route via MICE/Northern Lights GigaPoP. I am wondering who would be the best person to chat with about this since MICE does not list a peering contact for Northern Lights GigaPoP in the participants page, and I realize that the correct peering contact might be another level or two deeper. Thanks, Jeremy ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 31, 2011

Re: IPv6 Route Server Check-in

by Owen DeLong

Check your IPv6 MaxPrefixes limit. Owen On Aug 30, 2011, at 1:41 PM, Doug McIntyre wrote: > On Tue, Aug 30, 2011 at 03:23:46PM -0500, Matthew Beckwell wrote: >> I just noticed both of our IPv6 sessions to the route servers are down. (2607:fe10:ffff::1, 2607:fe10:ffff::2). IPv4 is fine....other IPv6 sessions seem ok. >> (Although I'm not sure for how long-- my logging wasn't setup yet). >> >> Just doing a "DownForEveryoneOrJustMe" check... > > Hmm, up for us. > ... > 2607:fe10:ffff::1 > 4 53679 144213 126038 0 0 0 02w5d00h 19 > 2607:fe10:ffff::2 > 4 53679 144120 126038 0 0 0 02w5d00h 19 > > > And.. > > [merlyn@micemn-01 /]$ ping6 2607:fe10:ffff::25 > PING6(56=40+8+8 bytes) 2607:fe10:ffff::1 --> 2607:fe10:ffff::25 > > ^C > > [merlyn@micemn-01 /]$ telnet 2607:fe10:ffff::25 bgp > Trying 2607:fe10:ffff::25... > telnet: connect to address 2607:fe10:ffff::25: Host is down > telnet: Unable to connect to remote host > > > Check your IPv6 stack? > > > > -- > Doug McIntyre <merlyn(a)iphouse.net> > -- ipHouse/Goldengate/Bitstream/ProNS -- > Network Engineer/Provisioning/Jack of all Trades > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 30, 2011