September 2019 - mice-discuss

Re: Anyone else down to Belle Plain since 3:45 pm?

by James Urwiller

Anyone that can provide transport from Fremont to Omaha NOT on Zayo? I’m ready to jump ship James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Justin Krejci *Sent:* Monday, September 9, 2019 18:13 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? I heard it is out somewhere between Sioux City and Alton, so it definitely could be that IDOT construction zone. We don't have growing pains we have Zayo pains. ------------------------------ *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> *Sent:* Monday, September 9, 2019 4:37 PM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Could be part of the Hwy 75 project: https://siouxcityjournal.com/news/local/idot-to-close-us-highway-during-nig… Our OSP staff said that Zayo was the laggard on the required moves. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of AnthonyAnderberg(a)nuvera.net Sent: Monday, September 09, 2019 4:21 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? We've got a link in NW Iowa down as well, we're on the same (former Neutral Path) link as you guys to Sioux City - so it's someplace between Sioux City, IA and Windom, MN. On 9/9/19, 4:02 PM, "MICE Discuss on behalf of James Urwiller" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of james.urwiller(a)TURNKEY-TELECOM.COM> wrote: YES SIR! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 9, 2019 16:02 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Sept. 9, 2019

Re: Anyone else down to Belle Plain since 3:45 pm?

by Justin Krejci

I heard it is out somewhere between Sioux City and Alton, so it definitely could be that IDOT construction zone. We don't have growing pains we have Zayo pains. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Frank Bulk <fbulk(a)MYPREMIERONLINE.COM> Sent: Monday, September 9, 2019 4:37 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Could be part of the Hwy 75 project: https://siouxcityjournal.com/news/local/idot-to-close-us-highway-during-nig… Our OSP staff said that Zayo was the laggard on the required moves. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of AnthonyAnderberg(a)nuvera.net Sent: Monday, September 09, 2019 4:21 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? We've got a link in NW Iowa down as well, we're on the same (former Neutral Path) link as you guys to Sioux City - so it's someplace between Sioux City, IA and Windom, MN. ?On 9/9/19, 4:02 PM, "MICE Discuss on behalf of James Urwiller" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of james.urwiller(a)TURNKEY-TELECOM.COM> wrote: YES SIR! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 9, 2019 16:02 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank

Sept. 9, 2019

Re: Anyone else down to Belle Plain since 3:45 pm?

by Frank Bulk

Could be part of the Hwy 75 project: https://siouxcityjournal.com/news/local/idot-to-close-us-highway-during-nig… Our OSP staff said that Zayo was the laggard on the required moves. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of AnthonyAnderberg(a)nuvera.net Sent: Monday, September 09, 2019 4:21 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? We've got a link in NW Iowa down as well, we're on the same (former Neutral Path) link as you guys to Sioux City - so it's someplace between Sioux City, IA and Windom, MN. On 9/9/19, 4:02 PM, "MICE Discuss on behalf of James Urwiller" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of james.urwiller(a)TURNKEY-TELECOM.COM> wrote: YES SIR! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 9, 2019 16:02 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank

Sept. 9, 2019

Re: Anyone else down to Belle Plain since 3:45 pm?

by AnthonyAnderberg＠nuvera.net

We've got a link in NW Iowa down as well, we're on the same (former Neutral Path) link as you guys to Sioux City - so it's someplace between Sioux City, IA and Windom, MN. On 9/9/19, 4:02 PM, "MICE Discuss on behalf of James Urwiller" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET on behalf of james.urwiller(a)TURNKEY-TELECOM.COM> wrote: YES SIR! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 9, 2019 16:02 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank

Sept. 9, 2019

Re: Anyone else down to Belle Plain since 3:45 pm?

by James Urwiller

YES SIR! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 9, 2019 16:02 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Anyone else down to Belle Plain since 3:45 pm? Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank

Sept. 9, 2019

Anyone else down to Belle Plain since 3:45 pm?

by Frank Bulk

Bounce and then down. Sep 9 15:45:21 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:19 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:37 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Cleared), Link (Failure), Link failure, 2019-09-09 08:45:27 PM (GMT), to Belle Plaine via WIT for MICE Sep 9 15:45:52 Fibercomm, 10G Ethernet Term. ETH-1-1-4, Critical (Raised), Link (Failure), Link failure, 2019-09-09 08:45:49 PM (GMT), to Belle Plaine via WIT for MICE Frank

Sept. 9, 2019

Re: Could I have a MICE admin look at the route reflectors?

by Frank Bulk

Good news -- Jeremy identified an issue in his transport that looks very similar to a Zayo issue he worked through in another link a few months ago, so he's opened up a ticket with Zayo. Thanks, Doug and Jeremy, for your help! Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Monday, September 09, 2019 8:33 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? Thanks, I will try to turn one of the two route-reflector sessions up this morning. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Sunday, September 08, 2019 11:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? Sure, I have commented out AS53347 for you now. Both IPv4 and IPv6 sessions. On Mon, Sep 09, 2019 at 02:15:18AM +0000, Frank Bulk wrote: >Doug, > >Thanks. We have been transitioning from AS53347 to AS18883 .... so if you can remove the AS55347 configuration on MICE's RR's, that would be great. > >Frank > >-----Original Message----- >From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre >Sent: Saturday, September 7, 2019 4:15 PM >To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? > >On Fri, Sep 06, 2019 at 11:51:41PM +0000, Frank Bulk wrote: >>For some reason at 5:38 pm we (AS18883, FiberNet) lost IPv4 and IPv6 peering with both of MICE RR's and Hurricane Electric and it's been unstable since then. >> >>All our other peers with MICE are fine. >> >>I didn't change any configuration, even though the "bad AS number" note in some of the error messages would suggest that. > > >We've been getting a lot of these.. > >Sep 3 18:02:14 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:18 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:23 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:28 micemn-01 bird6: NASN_18883: Received: Connection collision resolution > > >And these > >2019-09-07 16:08:15 <RMT> NASN_53347: Error: Bad peer AS: 18883 > >As well as I suppose the expected > >2019-09-07 16:08:16 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:20 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:24 <RMT> NASN_18883: Received: Administrative shutdown > >If you have 18883 link shutdown. > >But with the first and second errors, I see you have two AS's, and two >IPs coming across Eth10 on the switch. The middle error message seems >to imply that the configuration we have setup for AS 53347 on >206.108.255.67 is receiving a peer attempt for 18883 which is >configured to talk on 206.108.255.133 on our side. > >Could these two be mixed up at all? > > > > >-- >Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Sept. 9, 2019

Re: Could I have a MICE admin look at the route reflectors?

by Frank Bulk

Thanks, I will try to turn one of the two route-reflector sessions up this morning. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Sunday, September 08, 2019 11:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? Sure, I have commented out AS53347 for you now. Both IPv4 and IPv6 sessions. On Mon, Sep 09, 2019 at 02:15:18AM +0000, Frank Bulk wrote: >Doug, > >Thanks. We have been transitioning from AS53347 to AS18883 .... so if you can remove the AS55347 configuration on MICE's RR's, that would be great. > >Frank > >-----Original Message----- >From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre >Sent: Saturday, September 7, 2019 4:15 PM >To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? > >On Fri, Sep 06, 2019 at 11:51:41PM +0000, Frank Bulk wrote: >>For some reason at 5:38 pm we (AS18883, FiberNet) lost IPv4 and IPv6 peering with both of MICE RR's and Hurricane Electric and it's been unstable since then. >> >>All our other peers with MICE are fine. >> >>I didn't change any configuration, even though the "bad AS number" note in some of the error messages would suggest that. > > >We've been getting a lot of these.. > >Sep 3 18:02:14 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:18 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:23 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:28 micemn-01 bird6: NASN_18883: Received: Connection collision resolution > > >And these > >2019-09-07 16:08:15 <RMT> NASN_53347: Error: Bad peer AS: 18883 > >As well as I suppose the expected > >2019-09-07 16:08:16 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:20 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:24 <RMT> NASN_18883: Received: Administrative shutdown > >If you have 18883 link shutdown. > >But with the first and second errors, I see you have two AS's, and two >IPs coming across Eth10 on the switch. The middle error message seems >to imply that the configuration we have setup for AS 53347 on >206.108.255.67 is receiving a peer attempt for 18883 which is >configured to talk on 206.108.255.133 on our side. > >Could these two be mixed up at all? > > > > >-- >Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Sept. 9, 2019

Re: Could I have a MICE admin look at the route reflectors?

by Doug McIntyre

Sure, I have commented out AS53347 for you now. Both IPv4 and IPv6 sessions. On Mon, Sep 09, 2019 at 02:15:18AM +0000, Frank Bulk wrote: >Doug, > >Thanks. We have been transitioning from AS53347 to AS18883 .... so if you can remove the AS55347 configuration on MICE's RR's, that would be great. > >Frank > >-----Original Message----- >From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre >Sent: Saturday, September 7, 2019 4:15 PM >To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? > >On Fri, Sep 06, 2019 at 11:51:41PM +0000, Frank Bulk wrote: >>For some reason at 5:38 pm we (AS18883, FiberNet) lost IPv4 and IPv6 peering with both of MICE RR's and Hurricane Electric and it's been unstable since then. >> >>All our other peers with MICE are fine. >> >>I didn't change any configuration, even though the "bad AS number" note in some of the error messages would suggest that. > > >We've been getting a lot of these.. > >Sep 3 18:02:14 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:18 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:23 micemn-01 bird6: NASN_18883: Received: Connection collision resolution >Sep 3 18:02:28 micemn-01 bird6: NASN_18883: Received: Connection collision resolution > > >And these > >2019-09-07 16:08:15 <RMT> NASN_53347: Error: Bad peer AS: 18883 > >As well as I suppose the expected > >2019-09-07 16:08:16 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:20 <RMT> NASN_18883: Received: Administrative shutdown >2019-09-07 16:08:24 <RMT> NASN_18883: Received: Administrative shutdown > >If you have 18883 link shutdown. > >But with the first and second errors, I see you have two AS's, and two >IPs coming across Eth10 on the switch. The middle error message seems >to imply that the configuration we have setup for AS 53347 on >206.108.255.67 is receiving a peer attempt for 18883 which is >configured to talk on 206.108.255.133 on our side. > >Could these two be mixed up at all? > > > > >-- >Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Sept. 9, 2019

Re: Could I have a MICE admin look at the route reflectors?

by Frank Bulk

Doug, Thanks. We have been transitioning from AS53347 to AS18883 .... so if you can remove the AS55347 configuration on MICE's RR's, that would be great. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Saturday, September 7, 2019 4:15 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Could I have a MICE admin look at the route reflectors? On Fri, Sep 06, 2019 at 11:51:41PM +0000, Frank Bulk wrote: >For some reason at 5:38 pm we (AS18883, FiberNet) lost IPv4 and IPv6 peering with both of MICE RR's and Hurricane Electric and it's been unstable since then. > >All our other peers with MICE are fine. > >I didn't change any configuration, even though the "bad AS number" note in some of the error messages would suggest that. We've been getting a lot of these.. Sep 3 18:02:14 micemn-01 bird6: NASN_18883: Received: Connection collision resolution Sep 3 18:02:18 micemn-01 bird6: NASN_18883: Received: Connection collision resolution Sep 3 18:02:23 micemn-01 bird6: NASN_18883: Received: Connection collision resolution Sep 3 18:02:28 micemn-01 bird6: NASN_18883: Received: Connection collision resolution And these 2019-09-07 16:08:15 <RMT> NASN_53347: Error: Bad peer AS: 18883 As well as I suppose the expected 2019-09-07 16:08:16 <RMT> NASN_18883: Received: Administrative shutdown 2019-09-07 16:08:20 <RMT> NASN_18883: Received: Administrative shutdown 2019-09-07 16:08:24 <RMT> NASN_18883: Received: Administrative shutdown If you have 18883 link shutdown. But with the first and second errors, I see you have two AS's, and two IPs coming across Eth10 on the switch. The middle error message seems to imply that the configuration we have setup for AS 53347 on 206.108.255.67 is receiving a peer attempt for 18883 which is configured to talk on 206.108.255.133 on our side. Could these two be mixed up at all? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Sept. 9, 2019