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
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@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
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
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
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
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
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
On 9/3/11 22:26 CDT, Jay Hanke wrote:
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.
Just like I can announce them the routes, but can't make the take them, that is the basics of Internet routing policy. :) If people would like, I can stop announce Zayo's routes to MICE or you can filter them if you want to maintain routing symmetry. I still plan to poke them again. :) I never said I would be successful. :) -- =============================================== 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
On 9/3/11 11:26 PM, "Jay Hanke" <jayhanke@MANKATONETWORKS.NET> wrote:
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.
Hopefully our presence can influence some of that for you. Akamai has an open peering policy. If you are connected to the IX and can send us an email (even a garbled one) asking us to peer, we'll say YES 100% of the time. Best, -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Will Akamai be peered multi-laterally through the MICE route servers, or will we need to email to setup individual bi-lateral BGP sessions with Akamai? Is there an updated timeframe on when Akamai will be live on the exchange? Thanks, Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 E-Fax: 952-873-7425 jlumby@mnvoip.com -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, September 06, 2011 11:15 AM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Mice routes via Northern Lights GigaPoP On 9/3/11 11:26 PM, "Jay Hanke" <jayhanke@MANKATONETWORKS.NET> wrote:
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.
Hopefully our presence can influence some of that for you. Akamai has an open peering policy. If you are connected to the IX and can send us an email (even a garbled one) asking us to peer, we'll say YES 100% of the time. Best, -M< ######################################################################## 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
On 9/6/11 10:35 AM, "Jeremy Lumby" <jlumby@MNVOIP.COM> wrote:
Will Akamai be peered multi-laterally through the MICE route servers, or will we need to email to setup individual bi-lateral BGP sessions with Akamai? Is there an updated timeframe on when Akamai will be live on the exchange?
We prefer both. Time frame is soon. Best, -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
participants (7)
-
David Farmer -
Hannigan, Martin -
Jay Hanke -
Jeremy Lumby -
Matthew Beckwell -
Mike Horwath -
Richard Laager