- mice-discuss - lists.micemn.net

Re: DFS WIFI Interference

by Ryan Goldberg

Thanks Dave- We're careful about this, especially in the metro area. We'll double check our unlicensed stuff down there. Ryan On Jun 19, 2013, at 6:07 PM, "David Farmer" <farmer(a)UMN.EDU<mailto:farmer@UMN.EDU>> wrote: The University received a courtesy call from the Doppler radar people at KSTP about interference on the 5.57G band they use for sever weather tracking. Their next step is to call the FCC, but they would rather whoever is causing this interference to stop, rather than have people's gear confiscated, fines or whatever. We know at least a few of you have wireless gear in the Dinkytown area thought we would pass along a note along to all of you. I'm sure most of you know this, but just in case you don't, if you are running radio gear at or around 5.57 Ghz (Wifi channels 108, 112) you need pay attention to this issue, especially in this part of town with KSTP's radar nearby. There are conditions to the opening of this spectrum for public use that require shutdown in the presence of Doppler radio. (often referred to as DFS) (Publication Number: 443999 Rule Parts: 15E"<http://apps.fcc.gov/kdb/GetAttachment.html?id=dV24P2kaxB%2BkKzIPZxHxHg%3D%3D>. FCC<http://en.wikipedia.org/wiki/Federal_Communication_Commission>. October 5, 2009. "Devices must be professionally installed when operating in the 5470 – 5725 MHz band") Since KSTP's radar facility is just up the street from campus, it has been our experience that it is best just not to use those frequencies at all, they seem to run the radar all the time. The dish they use has very high gain, so something as small signal-wise as Wifi or cordless microphones could be the issue. So, the source might not be outside and may not be very powerful. The vector for this interference is parallel to University Ave, and is likely high above the ground, maybe as much as 150ft, but given the elevation changes in this part of town that could be misleading. We are double checking all our gear and with our other departments within the University. We were thinking maybe the Chateau or one of the other several new apartment buildings in the area could be the source and thought we should give you all a heads up. Thanks. ________________________________ 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

June 19, 2013

DFS WIFI Interference

by David Farmer

The University received a courtesy call from the Doppler radar people at KSTP about interference on the 5.57G band they use for sever weather tracking. Their next step is to call the FCC, but they would rather whoever is causing this interference to stop, rather than have people's gear confiscated, fines or whatever. We know at least a few of you have wireless gear in the Dinkytown area thought we would pass along a note along to all of you. I'm sure most of you know this, but just in case you don't, if you are running radio gear at or around 5.57 Ghz (Wifi channels 108, 112) you need pay attention to this issue, especially in this part of town with KSTP's radar nearby. There are conditions to the opening of this spectrum for public use that require shutdown in the presence of Doppler radio. (often referred to as DFS) (Publication Number: 443999 Rule Parts: 15E" <http://apps.fcc.gov/kdb/GetAttachment.html?id=dV24P2kaxB%2BkKzIPZxHxHg%3D%3D>. /FCC <http://en.wikipedia.org/wiki/Federal_Communication_Commission>/. October 5, 2009. "Devices must be professionally installed when operating in the 5470 – 5725 MHz band") Since KSTP's radar facility is just up the street from campus, it has been our experience that it is best just not to use those frequencies at all, they seem to run the radar all the time. The dish they use has very high gain, so something as small signal-wise as Wifi or cordless microphones could be the issue. So, the source might not be outside and may not be very powerful. The vector for this interference is parallel to University Ave, and is likely high above the ground, maybe as much as 150ft, but given the elevation changes in this part of town that could be misleading. We are double checking all our gear and with our other departments within the University. We were thinking maybe the Chateau or one of the other several new apartment buildings in the area could be the source and thought we should give you all a heads up. Thanks. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 19, 2013

Re: 2-byte or 4-byte ASN

by Josh Shields

I think its just a matter of equipment compatibility. We have a 32-bit ASN and I think most new applicants get those. I had the same question when I joined ARIN and from what I found at the time, it didn't seem to matter. A quick google search on which to apply for resulted in this answer: If you are using the latest equipment and software and your upstream provider supports 32-bit ASNs, apply for a 32-bit ASN. If you are using older equipment and software, apply for a 16-bit ASN. *Josh Shields** Technology Director**, MyTELEPATH, Inc.* Support: (952) 400-6000 | Direct: (952) 400-6014 support(a)mytelepath.com | jshields(a)mytelepath.com <https://www.facebook.com/MyTelepath> Facebook<https://www.facebook.com/MyTelepath> <http://twitter.com/#!/mytelepath> Twitter<http://twitter.com/#!/mytelepath> <http://www.linkedin.com/company/mytelepath> LinkedIn<http://www.linkedin.com/company/mytelepath> <http://blog.mytelepath.com/> Blog <http://blog.mytelepath.com/> On Fri, Jun 7, 2013 at 11:42 AM, Eric Crist <ecrist(a)claimlynx.com> wrote: > We're working on obtaining our initial IP allocation and an ASN. ARIN has > asked us to consider a 4-byte ASN, as they are low on 2-byte ASN. I don't > know the ramifications of either. Any of you have recommendations or > insight? > > Cheers > --- > Eric F Crist > System Administrator > ClaimLynx, Inc > (952) 593-5969 x2301 > > > > > -- > This e-mail and any files transmitted with it are confidential and are > intended solely for the use of the individual or entity to whom they are > addressed. If you are not the intended recipient or the individual > responsible for delivering the e-mail to the intended recipient, please be > advised that you have received this e-mail in error and that any use, > dissemination, forwarding, printing, or copying of this e-mail is strictly > prohibited. > > If you have received this communication in error, please return it to the > sender immediately and delete the original message and any copy of it from > your computer system. If you have any questions concerning this message, > please contact the sender or call ClaimLynx at (952) 593-5969. > > ######################################################################## > > 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

June 7, 2013

2-byte or 4-byte ASN

by Eric Crist

We're working on obtaining our initial IP allocation and an ASN. ARIN has asked us to consider a 4-byte ASN, as they are low on 2-byte ASN. I don't know the ramifications of either. Any of you have recommendations or insight? Cheers --- Eric F Crist System Administrator ClaimLynx, Inc (952) 593-5969 x2301 -- This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, please be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender or call ClaimLynx at (952) 593-5969. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 7, 2013

Re: Participants link missing on website?

by Mike Horwath

On Jun 5, 2013, at 9:41 AM, Darin Steffl <dcshobby(a)GMAIL.COM> wrote: > Works for me The direct link worked, that's why I posted it to the list. I didn't see it linked on the main page, cause I am old and blind I guess. Move along, just ramblings of a blind person. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 5, 2013

Re: Participants link missing on website?

by Mike Horwath

On Jun 5, 2013, at 9:33 AM, Mike Horwath <drechsau(a)geeks.org> wrote: > http://www.micemn.net/participants.html > > I don't see it there anymore. I'm blind. It is right above Donations. I'm bad. Sorry. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 5, 2013

Re: Participants link missing on website?

by Darin Steffl

Works for me On Wed, Jun 5, 2013 at 9:33 AM, Mike Horwath <drechsau(a)geeks.org> wrote: > http://www.micemn.net/participants.html > > I don't see it there anymore. > > -- > Mike Horwath, reachable via drechsau(a)Geeks.ORG > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Darin Steffl ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 5, 2013

Participants link missing on website?

by Mike Horwath

http://www.micemn.net/participants.html I don't see it there anymore. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 5, 2013

Re: MICE PeeringDB entry

by Mike Tindle

Gave 'em a poke and they've updated the IP blocks. Also, a gentle nudge to folks who have not updated their own records (or who have none!) to the new IPs. Regards, Mike On May 23, 2013, at 11:08 AM, "Koch, Andrew" <andrew.koch(a)TDSTELECOM.COM> wrote: > The MICE PeeringDB entry has the old IP address blocks listed. I am not sure who may have access to the record to update it, so I am sending this to the list. > > https://www.peeringdb.com/private/exchange_view.php?id=446 > > IP Address Blocks > Type Address Block Reverse DNS Scan > IPv4 Unicast 69.147.218.0/24 Link > IPv6 Unicast 2607:fe10:ffff::/64 Unsupported > > Best Regards, > > Andy Koch > TDS Telecom - IP Network Operations > andrew.koch(a)tdstelecom.com > Desk: 608-664-4694 > Cell: 608-616-0072 > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > *----------- H U R R I C A N E - E L E C T R I C ---------->> | Mike Tindle | Senior Network Engineer | mtindle(a)he.net | ASN 6939 | http://www.he.net | 510-580-4126 *--------------------------------------------------->> ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 31, 2013

Re: Nanog?

by Reid Fishler

Does that make me Midwest Long Island? Reid On Wed, May 29, 2013 at 9:08 AM, Hannigan, Martin <marty(a)akamai.com> wrote: > I'm Midwest Boston. :-) > > Sent from my mobile not so smartphone > > On May 29, 2013, at 9:04, "Jay Hanke" <jayhanke(a)MANKATONETWORKS.NET> > wrote: > > > I'll be there. We should get all the "midwest" folks together. > > > > On Tue, May 28, 2013 at 11:42 PM, Hannigan, Martin <marty(a)akamai.com> > wrote: > >> +1 > >> > >> > >> Sent from my mobile not so smartphone > >> > >> On May 29, 2013, at 0:41, "Reid Fishler" <rfishler(a)HE.NET> wrote: > >> > >> Who is going to be at Nanog next week? > >> > >> Reid > >> > >> -- > >> Reid Fishler > >> Director > >> Hurricane Electric > >> +1-510-580-4178 > >> > >> ________________________________ > >> > >> 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 > > > > > > > > -- > > Jay Hanke > > CTO, CCIE #19093 > > Mankato Networks LLC > > PO Box 54 > > 619 S Front St > > Mankato, MN 56001-3838 > > Google 530-618-2398 > > jayhanke(a)mankatonetworks.net > > http://www.mankatonetworks.com > > http://www.neutralpath.net > > > > ######################################################################## > > > > 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 > > -- Reid Fishler Director Hurricane Electric +1-510-580-4178 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 29, 2013

Re: Nanog?

by Hannigan, Martin

I'm Midwest Boston. :-) Sent from my mobile not so smartphone On May 29, 2013, at 9:04, "Jay Hanke" <jayhanke(a)MANKATONETWORKS.NET> wrote: > I'll be there. We should get all the "midwest" folks together. > > On Tue, May 28, 2013 at 11:42 PM, Hannigan, Martin <marty(a)akamai.com> wrote: >> +1 >> >> >> Sent from my mobile not so smartphone >> >> On May 29, 2013, at 0:41, "Reid Fishler" <rfishler(a)HE.NET> wrote: >> >> Who is going to be at Nanog next week? >> >> Reid >> >> -- >> Reid Fishler >> Director >> Hurricane Electric >> +1-510-580-4178 >> >> ________________________________ >> >> 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 > > > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > PO Box 54 > 619 S Front St > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > http://www.mankatonetworks.com > http://www.neutralpath.net > > ######################################################################## > > 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

May 29, 2013

Re: Nanog?

by Jay Hanke

I'll be there. We should get all the "midwest" folks together. On Tue, May 28, 2013 at 11:42 PM, Hannigan, Martin <marty(a)akamai.com> wrote: > +1 > > > Sent from my mobile not so smartphone > > On May 29, 2013, at 0:41, "Reid Fishler" <rfishler(a)HE.NET> wrote: > > Who is going to be at Nanog next week? > > Reid > > -- > Reid Fishler > Director > Hurricane Electric > +1-510-580-4178 > > ________________________________ > > 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 -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 29, 2013

Re: Nanog?

by Hannigan, Martin

+1 Sent from my mobile not so smartphone On May 29, 2013, at 0:41, "Reid Fishler" <rfishler(a)HE.NET<mailto:rfishler@HE.NET>> wrote: Who is going to be at Nanog next week? Reid -- Reid Fishler Director Hurricane Electric +1-510-580-4178 ________________________________ 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

May 29, 2013

Nanog?

by Reid Fishler

Who is going to be at Nanog next week? Reid -- Reid Fishler Director Hurricane Electric +1-510-580-4178 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 29, 2013

Re: [#2175746] MICE reachability

by Bertsch, Steven

There are some fun interoperability quirks with Cisco PVST where it will declare the port inconsistent if it receives a PVST BPDU with the wrong VLAN encoded in it (e.g. BPDU says VLAN 10, but tag is something different). In this case, it's a non-trunk port receiving a PVST BPDU. If someone originates such a BPDU towards their interface on a MICE cisco switch, then it will place just their port into this inconsistent state. If their port happens to be on a non-cisco switch that doesn't know what PVST is, it will happily "tunnel" it, usually causing the uplinks on any connected Cisco switches that receive it to go into this inconsistent state. An ingress MAC ACL on the customer-facing ports of the non-cisco switches to block 0100.0CCC.CCCD should prevent this from happening, while leaving IEEE STP BPDUs alone. There's no way to change this behavior in Cisco switches AFAIK (aside from running bpdufilter of course). If it's not this way already, it would be best to run MST for inter-op with the Cisco switches if multiple VLANs will be connected. Though even when running MST, Cisco switches still run "PVST+ Emulation," so tunneled PVST+ BPDUs will provide the same excitement as before. Regardless of any amount of STP tweaking on MICE switches, there is still the risk that a dual-connected customer could cause a loop. Storm-control can help there to at least constrain the amount of broadcast and multicast traffic that ends up looping. Steven Bertsch Engineer III VISI, a TDS® Company 24x7 Support: 612.395.9010 Direct: 612.395.8966 Main: 612.395.9000 Email: support(a)visi.com Web: www.visi.com -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Steve Howard Sent: Saturday, May 25, 2013 10:24 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] [#2175746] MICE reachability On 05/25/2013 09:42 AM, James Stahr wrote: > On 5/25/2013 9:13 AM, Jay Hanke wrote: >> > From the Mankato Networks remote switch I'm able to get to everything >> except for carriers on the CNS remote switch. >> >> > > I can't ping HE (bgp session with them has been down since 00:58:04) > who is on the remote switch, but I also see weirdness pinging the > route servers: > > r-pop-min-1#ping 206.108.255.1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms > r-pop-min-1#ping 206.108.255.1 source loop1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > Packet sent with a source address of 205.173.182.62 > ..... > Success rate is 0 percent (0/5) > r-pop-min-1# > > Do the route servers not use the routes they receive and use a > provider on the CNS switch for transit? > > -James > >> On Sat, May 25, 2013 at 6:46 AM, Kelly Cochran (Hurricane Electric >> Internet Services)<noc(a)he.net> wrote: >> >>> Are you aware of any partitions on the exchange? We're only seeing >>> other people on the CNS switch that we're on. >>> >>> -- -H U R R I C A N E - E L E C T R I C- >>> Kelly Cochran Sr. Network Engineer >>> 510-580-4100 http://www.he.net/ AS6939 >>> > It looks like something happened last night between the CNS & Main CNS switches. The CNS switch showed the following in its log: May 24 21:31:26.315 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 24 21:31:26.315 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. May 24 22:49:51.831 CDT: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet0/10 on VLAN0847. Port consistency restored. May 25 00:57:45.614 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 25 00:57:45.614 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. I added a "spanning-tree bpdufilter enable" on the port that points toward the main CNS switch to solve the problem. This solved the problem for now. But, it might be nice if the technical committee could come up some technical guidelines for spanning-tree that will work for MICE. Thanks, Steve ######################################################################## 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

May 25, 2013

Re: [#2175746] MICE reachability

by Chris Scheidecker

I'm able to see HE now, and all of my other sessions have been up since last night…anyone aware of any maintenances or any changes made last night ~21:30 that may have caused this? While it worked for now, disabling spanning tree and/or bpdus on two switches that are in the same infrastructure seems like a band-aid…disabling facing client ports or uplinks I can see though. I think this could use a little more technical review at some point. Chris On May 25, 2013, at 10:23 AM, Steve Howard wrote: On 05/25/2013 09:42 AM, James Stahr wrote: On 5/25/2013 9:13 AM, Jay Hanke wrote: >From the Mankato Networks remote switch I'm able to get to everything except for carriers on the CNS remote switch. I can't ping HE (bgp session with them has been down since 00:58:04) who is on the remote switch, but I also see weirdness pinging the route servers: r-pop-min-1#ping 206.108.255.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms r-pop-min-1#ping 206.108.255.1 source loop1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: Packet sent with a source address of 205.173.182.62 ..... Success rate is 0 percent (0/5) r-pop-min-1# Do the route servers not use the routes they receive and use a provider on the CNS switch for transit? -James On Sat, May 25, 2013 at 6:46 AM, Kelly Cochran (Hurricane Electric Internet Services)<noc(a)he.net<mailto:noc@he.net>> wrote: Are you aware of any partitions on the exchange? We're only seeing other people on the CNS switch that we're on. -- -H U R R I C A N E - E L E C T R I C- Kelly Cochran Sr. Network Engineer 510-580-4100 http://www.he.net/ AS6939 It looks like something happened last night between the CNS & Main CNS switches. The CNS switch showed the following in its log: May 24 21:31:26.315 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 24 21:31:26.315 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. May 24 22:49:51.831 CDT: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet0/10 on VLAN0847. Port consistency restored. May 25 00:57:45.614 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 25 00:57:45.614 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. I added a "spanning-tree bpdufilter enable" on the port that points toward the main CNS switch to solve the problem. This solved the problem for now. But, it might be nice if the technical committee could come up some technical guidelines for spanning-tree that will work for MICE. Thanks, Steve ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Chris Scheidecker - Infrastructure Engineer Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2044 Direct Dial Twitter<http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> | LinkedIn<http://www.linkedin.com/companies/atomic-data-centers> Simple. Safe. Smart. www.atomicdata.com<http://www.atomicdata.com/> This message and any information or attachments included therewith is intended only for the individual or entity named above. If the reader is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message or any information attached or contained therein is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail and destroy all copies of the message and any attachments. Thank you. Please consider the environment before printing this email. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: [#2175746] MICE reachability

by Steve Howard

On 05/25/2013 09:42 AM, James Stahr wrote: > On 5/25/2013 9:13 AM, Jay Hanke wrote: >> > From the Mankato Networks remote switch I'm able to get to everything >> except for carriers on the CNS remote switch. >> >> > > I can't ping HE (bgp session with them has been down since 00:58:04) > who is on the remote switch, but I also see weirdness pinging the > route servers: > > r-pop-min-1#ping 206.108.255.1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms > r-pop-min-1#ping 206.108.255.1 source loop1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > Packet sent with a source address of 205.173.182.62 > ..... > Success rate is 0 percent (0/5) > r-pop-min-1# > > Do the route servers not use the routes they receive and use a > provider on the CNS switch for transit? > > -James > >> On Sat, May 25, 2013 at 6:46 AM, Kelly Cochran (Hurricane Electric >> Internet Services)<noc(a)he.net> wrote: >> >>> Are you aware of any partitions on the exchange? We're only seeing >>> other people on the CNS switch that we're on. >>> >>> -- -H U R R I C A N E - E L E C T R I C- >>> Kelly Cochran Sr. Network Engineer >>> 510-580-4100 http://www.he.net/ AS6939 >>> > It looks like something happened last night between the CNS & Main CNS switches. The CNS switch showed the following in its log: May 24 21:31:26.315 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 24 21:31:26.315 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. May 24 22:49:51.831 CDT: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking TenGigabitEthernet0/10 on VLAN0847. Port consistency restored. May 25 00:57:45.614 CDT: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk TenGigabitEthernet0/10 VLAN847. May 25 00:57:45.614 CDT: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking TenGigabitEthernet0/10 on VLAN0847. Inconsistent port type. I added a "spanning-tree bpdufilter enable" on the port that points toward the main CNS switch to solve the problem. This solved the problem for now. But, it might be nice if the technical committee could come up some technical guidelines for spanning-tree that will work for MICE. Thanks, Steve ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: [#2175746] MICE reachability

by James Stahr

On 5/25/2013 9:13 AM, Jay Hanke wrote: > > From the Mankato Networks remote switch I'm able to get to everything > except for carriers on the CNS remote switch. > > I can't ping HE (bgp session with them has been down since 00:58:04) who is on the remote switch, but I also see weirdness pinging the route servers: r-pop-min-1#ping 206.108.255.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms r-pop-min-1#ping 206.108.255.1 source loop1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: Packet sent with a source address of 205.173.182.62 ..... Success rate is 0 percent (0/5) r-pop-min-1# Do the route servers not use the routes they receive and use a provider on the CNS switch for transit? -James > On Sat, May 25, 2013 at 6:46 AM, Kelly Cochran (Hurricane Electric > Internet Services)<noc(a)he.net> wrote: > >> Are you aware of any partitions on the exchange? We're only seeing other people on the CNS switch that we're on. >> >> -- -H U R R I C A N E - E L E C T R I C- >> Kelly Cochran Sr. Network Engineer >> 510-580-4100 http://www.he.net/ AS6939 >> >> > > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > PO Box 54 > 619 S Front St > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > http://www.mankatonetworks.com > http://www.neutralpath.net > > ######################################################################## > > 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

May 25, 2013

Re: [#2175746] MICE reachability

by Jay Hanke

>From the Mankato Networks remote switch I'm able to get to everything except for carriers on the CNS remote switch. On Sat, May 25, 2013 at 6:46 AM, Kelly Cochran (Hurricane Electric Internet Services) <noc(a)he.net> wrote: > > Are you aware of any partitions on the exchange? We're only seeing other people on the CNS switch that we're on. > > -- -H U R R I C A N E - E L E C T R I C- > Kelly Cochran Sr. Network Engineer > 510-580-4100 http://www.he.net/ AS6939 > -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: MICE status?

by Andrew Hoyos

I can confirm that from the "main switch", seemed like only peers on the CNS switch were affected. Since there is a few new participants, I'll just re-paste this message below from last year here. The key being, if you are using a a Layer2 device, check out the very well done AMS-IX config guide, and *please* follow all the steps or template config to ensure your device is acting properly. -- Andrew Hoyos Hoyos Consulting LLC ofc: +1 608 616 9950 andrew(a)hoyosconsulting.com http://www.hoyosconsulting.com/ > 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 On May 24, 2013, at 11:39 PM, Matthew Beckwell wrote: > I'm back to seeing ~6846 IPv4 Prefixes and ~912 IPv6 Prefixes from the route servers. > Seems to be back to normal here. > > I'd be interested in hearing more about the Layer 2 IP address situation, though… > ~Matthew > > > From: Chris Scheidecker <CScheidecker(a)ATOMICDATA.COM> > Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > Date: Friday, May 24, 2013 11:03 PM > To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] MICE status? > > After converting our L2 interface (used for new IP scheme cutover) to L3 all peers are up and I am able to ping both route servers and other peers at MICE. > > > On May 24, 2013, at 10:40 PM, Jeremy Lumby wrote: > >> I am seeing the same limited connectivity >> >> -----Original Message----- >> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Matthew Beckwell >> Sent: Friday, May 24, 2013 10:35 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: Re: [MICE-DISCUSS] MICE status? >> >> I can see both route servers from here (AS13746), along with these next-hops. >> (I don't see anyone on the CNS switch.) But I also don't see ipHouse or Atomic Data...and all 3 of us are on the main switch. >> >> TDS 206.108.255.4 >> VISI 206.108.255.6 >> Arvig 206.108.255.7 >> Nextera 206.108.255.8 >> Airstream 206.108.255.10 >> MN VoIP 206.108.255.11 >> Spiralight 206.108.255.12 >> Enventis 206.108.255.18 >> US Internet 206.108.255.19 >> Berbee 206.108.255.26 >> SDN 206.108.255.49 >> Akamai 206.108.255.84 >> Vaultas 206.108.255.100 >> Compudyne 206.108.255.101 >> MyTelepath 206.108.255.102 >> Windomnet 206.108.255.104 >> Jaguar 206.108.255.105 >> NU-Telecom 206.108.255.106 >> Broadband Visions 206.108.255.107 >> >> ~Matthew >> >> -- >> Matthew Beckwell - Senior Network and Application Engineer Advanced Integrated Technologies Technical Support: 1-800-300-5408 >> Office: 1-952-829-5511 x204 >> E-Mail: matthewb(a)aitech.net >> >> >> >> >> -----Original Message----- >> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre >> Sent: Friday, May 24, 2013 10:16 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: [MICE-DISCUSS] MICE status? >> >> What happened to the MICE switch? My gear at Cologix is up, and I have link up on my MICE port, but I can't ping the switch, or any other MICE connected site? >> >> -- >> 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 >> >> ######################################################################## >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > Chris Scheidecker - Infrastructure Engineer > > Atomic Data > 615 North 3rd Street > Minneapolis, MN 55401 > 612.466.2000 Main Line > 612.466.2044 Direct Dial > > Twitter | Facebook | LinkedIn > > Simple. Safe. Smart. > www.atomicdata.com > > This message and any information or attachments included therewith is intended only for the individual or entity named above. If the reader is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message or any information attached or contained therein is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail and destroy all copies of the message and any attachments. > > Thank you. > > > Please consider the environment before printing this email. > > > 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 -- Andrew Hoyos hoyosa(a)gmail.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: MICE status?

by Matthew Beckwell

I'm back to seeing ~6846 IPv4 Prefixes and ~912 IPv6 Prefixes from the route servers. Seems to be back to normal here. I'd be interested in hearing more about the Layer 2 IP address situation, though… ~Matthew From: Chris Scheidecker <CScheidecker(a)ATOMICDATA.COM<mailto:CScheidecker@ATOMICDATA.COM>> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Date: Friday, May 24, 2013 11:03 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> Subject: Re: [MICE-DISCUSS] MICE status? After converting our L2 interface (used for new IP scheme cutover) to L3 all peers are up and I am able to ping both route servers and other peers at MICE. On May 24, 2013, at 10:40 PM, Jeremy Lumby wrote: I am seeing the same limited connectivity -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Matthew Beckwell Sent: Friday, May 24, 2013 10:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE status? I can see both route servers from here (AS13746), along with these next-hops. (I don't see anyone on the CNS switch.) But I also don't see ipHouse or Atomic Data...and all 3 of us are on the main switch. TDS 206.108.255.4 VISI 206.108.255.6 Arvig 206.108.255.7 Nextera 206.108.255.8 Airstream 206.108.255.10 MN VoIP 206.108.255.11 Spiralight 206.108.255.12 Enventis 206.108.255.18 US Internet 206.108.255.19 Berbee 206.108.255.26 SDN 206.108.255.49 Akamai 206.108.255.84 Vaultas 206.108.255.100 Compudyne 206.108.255.101 MyTelepath 206.108.255.102 Windomnet 206.108.255.104 Jaguar 206.108.255.105 NU-Telecom 206.108.255.106 Broadband Visions 206.108.255.107 ~Matthew -- Matthew Beckwell - Senior Network and Application Engineer Advanced Integrated Technologies Technical Support: 1-800-300-5408 Office: 1-952-829-5511 x204 E-Mail: matthewb(a)aitech.net<mailto:matthewb@aitech.net> -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, May 24, 2013 10:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] MICE status? What happened to the MICE switch? My gear at Cologix is up, and I have link up on my MICE port, but I can't ping the switch, or any other MICE connected site? -- Doug McIntyre <merlyn(a)iphouse.net<mailto:merlyn@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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Chris Scheidecker - Infrastructure Engineer Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2044 Direct Dial Twitter<http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> | LinkedIn<http://www.linkedin.com/companies/atomic-data-centers> Simple. Safe. Smart. www.atomicdata.com<http://www.atomicdata.com/> This message and any information or attachments included therewith is intended only for the individual or entity named above. If the reader is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message or any information attached or contained therein is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail and destroy all copies of the message and any attachments. Thank you. Please consider the environment before printing this email. ________________________________ 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

May 25, 2013

Re: MICE status?

by Chris Scheidecker

After converting our L2 interface (used for new IP scheme cutover) to L3 all peers are up and I am able to ping both route servers and other peers at MICE. On May 24, 2013, at 10:40 PM, Jeremy Lumby wrote: I am seeing the same limited connectivity -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Matthew Beckwell Sent: Friday, May 24, 2013 10:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] MICE status? I can see both route servers from here (AS13746), along with these next-hops. (I don't see anyone on the CNS switch.) But I also don't see ipHouse or Atomic Data...and all 3 of us are on the main switch. TDS 206.108.255.4 VISI 206.108.255.6 Arvig 206.108.255.7 Nextera 206.108.255.8 Airstream 206.108.255.10 MN VoIP 206.108.255.11 Spiralight 206.108.255.12 Enventis 206.108.255.18 US Internet 206.108.255.19 Berbee 206.108.255.26 SDN 206.108.255.49 Akamai 206.108.255.84 Vaultas 206.108.255.100 Compudyne 206.108.255.101 MyTelepath 206.108.255.102 Windomnet 206.108.255.104 Jaguar 206.108.255.105 NU-Telecom 206.108.255.106 Broadband Visions 206.108.255.107 ~Matthew -- Matthew Beckwell - Senior Network and Application Engineer Advanced Integrated Technologies Technical Support: 1-800-300-5408 Office: 1-952-829-5511 x204 E-Mail: matthewb(a)aitech.net<mailto:matthewb@aitech.net> -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, May 24, 2013 10:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] MICE status? What happened to the MICE switch? My gear at Cologix is up, and I have link up on my MICE port, but I can't ping the switch, or any other MICE connected site? -- Doug McIntyre <merlyn(a)iphouse.net<mailto:merlyn@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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Chris Scheidecker - Infrastructure Engineer Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2044 Direct Dial Twitter<http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> | LinkedIn<http://www.linkedin.com/companies/atomic-data-centers> Simple. Safe. Smart. www.atomicdata.com<http://www.atomicdata.com/> This message and any information or attachments included therewith is intended only for the individual or entity named above. If the reader is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message or any information attached or contained therein is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail and destroy all copies of the message and any attachments. Thank you. Please consider the environment before printing this email. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: MICE status?

by Jeremy Lumby

I am seeing the same limited connectivity -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Matthew Beckwell Sent: Friday, May 24, 2013 10:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE status? I can see both route servers from here (AS13746), along with these next-hops. (I don't see anyone on the CNS switch.) But I also don't see ipHouse or Atomic Data...and all 3 of us are on the main switch. TDS 206.108.255.4 VISI 206.108.255.6 Arvig 206.108.255.7 Nextera 206.108.255.8 Airstream 206.108.255.10 MN VoIP 206.108.255.11 Spiralight 206.108.255.12 Enventis 206.108.255.18 US Internet 206.108.255.19 Berbee 206.108.255.26 SDN 206.108.255.49 Akamai 206.108.255.84 Vaultas 206.108.255.100 Compudyne 206.108.255.101 MyTelepath 206.108.255.102 Windomnet 206.108.255.104 Jaguar 206.108.255.105 NU-Telecom 206.108.255.106 Broadband Visions 206.108.255.107 ~Matthew -- Matthew Beckwell - Senior Network and Application Engineer Advanced Integrated Technologies Technical Support: 1-800-300-5408 Office: 1-952-829-5511 x204 E-Mail: matthewb(a)aitech.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, May 24, 2013 10:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE status? What happened to the MICE switch? My gear at Cologix is up, and I have link up on my MICE port, but I can't ping the switch, or any other MICE connected site? -- 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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 25, 2013

Re: MICE status?

by Matthew Beckwell

I can see both route servers from here (AS13746), along with these next-hops. (I don't see anyone on the CNS switch.) But I also don't see ipHouse or Atomic Data...and all 3 of us are on the main switch. TDS 206.108.255.4 VISI 206.108.255.6 Arvig 206.108.255.7 Nextera 206.108.255.8 Airstream 206.108.255.10 MN VoIP 206.108.255.11 Spiralight 206.108.255.12 Enventis 206.108.255.18 US Internet 206.108.255.19 Berbee 206.108.255.26 SDN 206.108.255.49 Akamai 206.108.255.84 Vaultas 206.108.255.100 Compudyne 206.108.255.101 MyTelepath 206.108.255.102 Windomnet 206.108.255.104 Jaguar 206.108.255.105 NU-Telecom 206.108.255.106 Broadband Visions 206.108.255.107 ~Matthew -- Matthew Beckwell - Senior Network and Application Engineer Advanced Integrated Technologies Technical Support: 1-800-300-5408 Office: 1-952-829-5511 x204 E-Mail: matthewb(a)aitech.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, May 24, 2013 10:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE status? What happened to the MICE switch? My gear at Cologix is up, and I have link up on my MICE port, but I can't ping the switch, or any other MICE connected site? -- 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

May 25, 2013

Re: MICE status?

by Chase Rydberg

We're seeing the same on our end. Triggered at 9:31pm CST. Chase Rydberg* **MDU Ethernet Solutions* (p) 952.314.4288 (c) 952.212.8390 On Fri, May 24, 2013 at 10:20 PM, Chris Scheidecker < CScheidecker(a)atomicdata.com> wrote: > Spanning tree loop? Anyone down there plugging stuff in? > > I'm seeing spanning tree blocking facing MICE port. > > On May 24, 2013, at 10:15 PM, Doug McIntyre wrote: > > What happened to the MICE switch? My gear at Cologix is up, and > I have link up on my MICE port, but I can't ping the switch, or any > other MICE connected site? > > -- > 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 > > > *Chris Scheidecker* - Infrastructure Engineer > > Atomic Data > 615 North 3rd Street > Minneapolis, MN 55401 > 612.466.2000 Main Line > 612.466.2044 Direct Dial > > Twitter <http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> > | LinkedIn <http://www.linkedin.com/companies/atomic-data-centers> > > Simple. Safe. Smart. > www.atomicdata.com > > This message and any information or attachments included therewith is > intended only for the individual or entity named above. If the reader is > not the intended recipient, you are hereby notified that any use, > dissemination, distribution or copy of this message or any information > attached or contained therein is strictly prohibited. If you have received > this message in error, please notify the sender by return e-mail and > destroy all copies of the message and any attachments. > > Thank you. > > *Please consider the environment before printing this email.* > > > ------------------------------ > > 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

May 25, 2013