November 2011 - mice-discuss - lists.micemn.net

Re: Nextera MICE port Assignment Request

by Anthony Anderberg

They should be ready to go. Anthony Anderberg Sr. Systems Analyst 320-234-5239 anthonyanderberg(a)nu-telecom.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Wednesday, November 30, 2011 11:25 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Nextera MICE port Assignment Request Nextera Main Switch ge-0/0/8 ASN 22402 69.147.218.8/24 2607:fe10:ffff::8/64 peering(a)nextera.net Please build them in the route servers and update the website and cacti server. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC 619 S Front St 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

Nov. 30, 2011

Nextera MICE port Assignment Request

by Jay Hanke

Nextera Main Switch ge-0/0/8 ASN 22402 69.147.218.8/242607:fe10:ffff::8/64peering@nextera.net Please build them in the route servers and update the website and cacti server. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC 619 S Front St 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

Nov. 30, 2011

New Data center in Eagan

by Frank Bulk

http://www.datacenterknowledge.com/archives/2011/11/22/five-9s-digital-expa… Thought this might interest some of the Minnesota folks. Frank ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 23, 2011

Re: New Arvig Port Assignment

by Mike Bushard Jr

Sounds great Jay. We'll work on getting you the info. We're excited to become part of the group! Mike Bushard, Jr Network Engineer IV *Arvig Communication Systems* diversicom-Melrose Telephone-Mainstreet Communications 320.256.7471 Office 320.256.0178 Direct mike.bushard(a)arvig.com On Mon, Nov 21, 2011 at 10:28 AM, Jay Hanke <jayhanke(a)mankatonetworks.net>wrote: > Arvig > Port Main switch 7 (copper) > 69.147.218.7/24 > 2607:fe10:ffff::7/64 > We need your contact info and ASN. Also please update your peeringDB > information. > > Thanks and welcome aboard! > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > 619 S Front St > 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 > -- *Mike Bushard, Jr* Network Engineer Arvig Communications Systems diversicom-Melrose Telephone-Wisper Wireless 320.256.7471 320.256.0178 Direct 320.333.9448 Mobile 320.256.7555 Fax ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 23, 2011

Re: MICE incident @11:47 CST

by Anthony Anderberg

Looks like the routes came back up for everyone but DCN. If anyone needs a hand just let us know. Anthony Anderberg Sr. Systems Analyst - NU-Telecom O: 320-234-5239 C: 320-234-5539 anthonyanderberg(a)nu-telecom.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Tuesday, November 22, 2011 2:10 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE incident @11:47 CST On Tue, Nov 22, 2011 at 1:54 PM, James Stahr <stahr(a)mailbag.com> wrote: > Anyone else have an issue? stats.micemn.net show spikes which would > likely indicate a spanning tree loop or a broadcast storm. Whatever > the traffic was, it caused a CPU spike and upset all of our other BGP > sessions on our ASR as well. I apologize, that was my mess up. I was working on a customer transport link and didn't realize I had a bridge-domain built on the port. It created a loop when the port came up within the customer network and it looks like it spewed garbage on to the MICE vlan. Jay ######################################################################## 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

Nov. 22, 2011

Re: MICE incident @11:47 CST

by Justin Krejci

My favorite quote from their config guide: 4.2.6. Non-unicast IPv4: IGMP, DHCP, TFTP On the ISP peering LAN, the only non-unicast traffic that is allowed is the ARP query. Sometimes we see equipment trying to get a configuration through broadcast TFTP, or configure themselves through DHCP. We will leave it to the reader to consider why this is a bad idea. On Tue, 2011-11-22 at 14:14 -0600, Andrew Hoyos wrote: > Can we revisit the whole spanning tree on the IX thing again? > > My two cents last time was for 1 mac address per participant facing port, proper storm control limts, bpdufilter, etc. > > Also, I'd encourage all participants to review their config's, *especially* if they have layer2 devices in the mix somewhere. > AMS-IX has put together very nice and self-explainatory guides about how to keep your layer2 devices acting nice and not have a negative effect on the entire MICE IX. > > That configuration guide is located here: http://www.ams-ix.net/config-guide > > -- > Andrew Hoyos > hoyosa(a)gmail.com > > On Nov 22, 2011, at 2:06 PM, Eric Crist wrote: > > > Judging by the graphs, it was something between Cooperative Net and HE… > > > > --- > > Eric F Crist > > System Administrator > > ClaimLynx, Inc > > (952) 593-5969 x2301 > > > > > > > > On Nov 22, 2011, at 13:54:12, James Stahr wrote: > > > >> Anyone else have an issue? stats.micemn.net show spikes which would likely indicate a spanning tree loop or a broadcast storm. Whatever the traffic was, it caused a CPU spike and upset all of our other BGP sessions on our ASR as well. > >> > >> -James > >> Berbee/CDW > >> > >> ######################################################################## > >> > >> 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 > > ######################################################################## > > 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

Nov. 22, 2011

Re: MICE incident @11:47 CST

by Andrew Hoyos

Can we revisit the whole spanning tree on the IX thing again? My two cents last time was for 1 mac address per participant facing port, proper storm control limts, bpdufilter, etc. Also, I'd encourage all participants to review their config's, *especially* if they have layer2 devices in the mix somewhere. AMS-IX has put together very nice and self-explainatory guides about how to keep your layer2 devices acting nice and not have a negative effect on the entire MICE IX. That configuration guide is located here: http://www.ams-ix.net/config-guide -- Andrew Hoyos hoyosa(a)gmail.com On Nov 22, 2011, at 2:06 PM, Eric Crist wrote: > Judging by the graphs, it was something between Cooperative Net and HE… > > --- > Eric F Crist > System Administrator > ClaimLynx, Inc > (952) 593-5969 x2301 > > > > On Nov 22, 2011, at 13:54:12, James Stahr wrote: > >> Anyone else have an issue? stats.micemn.net show spikes which would likely indicate a spanning tree loop or a broadcast storm. Whatever the traffic was, it caused a CPU spike and upset all of our other BGP sessions on our ASR as well. >> >> -James >> Berbee/CDW >> >> ######################################################################## >> >> 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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 22, 2011

Re: MICE incident @11:47 CST

by Jay Hanke

On Tue, Nov 22, 2011 at 1:54 PM, James Stahr <stahr(a)mailbag.com> wrote: > Anyone else have an issue? stats.micemn.net show spikes which would likely > indicate a spanning tree loop or a broadcast storm. Whatever the traffic > was, it caused a CPU spike and upset all of our other BGP sessions on our > ASR as well. I apologize, that was my mess up. I was working on a customer transport link and didn't realize I had a bridge-domain built on the port. It created a loop when the port came up within the customer network and it looks like it spewed garbage on to the MICE vlan. Jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Nov. 22, 2011

Re: MICE incident @11:47 CST

by Eric Crist

Judging by the graphs, it was something between Cooperative Net and HE… --- Eric F Crist System Administrator ClaimLynx, Inc (952) 593-5969 x2301 On Nov 22, 2011, at 13:54:12, James Stahr wrote: > Anyone else have an issue? stats.micemn.net show spikes which would likely indicate a spanning tree loop or a broadcast storm. Whatever the traffic was, it caused a CPU spike and upset all of our other BGP sessions on our ASR as well. > > -James > Berbee/CDW > > ######################################################################## > > 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

Nov. 22, 2011

Re: MICE incident @11:47 CST

by Ryan Goldberg

Saw same, bgp poof, and mac-flap ick... Ryan ----- Reply message ----- From: "James Stahr" <stahr(a)MAILBAG.COM> To: "MICE-DISCUSS(a)LISTS.IPHOUSE.NET" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] MICE incident @11:47 CST Date: Tue, Nov 22, 2011 1:54 pm Anyone else have an issue? stats.micemn.net show spikes which would likely indicate a spanning tree loop or a broadcast storm. Whatever the traffic was, it caused a CPU spike and upset all of our other BGP sessions on our ASR as well. -James Berbee/CDW ######################################################################## 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

Nov. 22, 2011