- mice-discuss - lists.micemn.net

Re: Link to all MICE peers dropped

by Jay Hanke

yea You can look at the mice weathermap for these as well. Just don't post the graphs. :) On Mon, May 3, 2021 at 3:03 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > > Thanks, Jay. Anyone else? > Did FiberComm take a hit, too? We share much of our path together. > > Frank > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke > Sent: Monday, May 3, 2021 2:59 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Link to all MICE peers dropped > > Looks like Premier and Fibernet both took a hit about that time. > > On Mon, May 3, 2021 at 2:55 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > > > > Our link to all MICE peers dropped at 2:47:39 pm – anyone else see an outage and/or disruption? > > > > > > > > Frank > > > > AS18883 > > > > > > ________________________________ > > > > 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, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 3, 2021

Re: Link to all MICE peers dropped

by Frank Bulk

Thanks, Jay. Anyone else? Did FiberComm take a hit, too? We share much of our path together. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Monday, May 3, 2021 2:59 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Link to all MICE peers dropped Looks like Premier and Fibernet both took a hit about that time. On Mon, May 3, 2021 at 2:55 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > > Our link to all MICE peers dropped at 2:47:39 pm – anyone else see an outage and/or disruption? > > > > Frank > > AS18883 > > > ________________________________ > > 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, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 3, 2021

Re: Link to all MICE peers dropped

by Steve Howard

May 3, 2021

Re: Link to all MICE peers dropped

by Jay Hanke

Looks like Premier and Fibernet both took a hit about that time. On Mon, May 3, 2021 at 2:55 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > > Our link to all MICE peers dropped at 2:47:39 pm – anyone else see an outage and/or disruption? > > > > Frank > > AS18883 > > > ________________________________ > > 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, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

May 3, 2021

Link to all MICE peers dropped

by Frank Bulk

Our link to all MICE peers dropped at 2:47:39 pm - anyone else see an outage and/or disruption? Frank AS18883

May 3, 2021

Re: Zayo Belle Plaine - April 15th

by Doug McIntyre

Yes, but I'll go do it again. That part of the config hasn't been changed since initial setup. On Fri, Apr 30, 2021 at 01:01:00PM +0000, Frank Bulk wrote: >Has someone HUP’d it, yet? > >Frank > >From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos >Sent: Tuesday, April 27, 2021 12:54 PM >To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >Subject: Re: [MICE-DISCUSS] Zayo Belle Plaine - April 15th > >Same here. Perhaps the BFD daemon on rs2 needs to be HUP’d to pick up values in config file? > > > Detect Transmit >Address State Interface Time Interval Multiplier >2001:504:27::d1af:0:1 Up xe-0/1/0.0 1.500 0.500 3 > Client BGP, TX interval 0.500, RX interval 0.500 > Session up time 2w1d 16:53:02, previous down time 00:00:00 > Local diagnostic None, remote diagnostic None > Remote state Up, version 1 > Session type: Single hop BFD > Min async interval 0.500, min slow interval 1.000 > Adaptive async TX interval 0.500, RX interval 0.500 > Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 > Remote min TX interval 0.500, min RX interval 0.500, multiplier 3 > Local discriminator 19, remote discriminator 2630753610 > Echo mode disabled/inactive Session ID: 0x0 > > Detect Transmit >Address State Interface Time Interval Multiplier >2001:504:27::d1af:0:2 Up xe-0/1/0.0 2.500 0.500 3 > Client BGP, TX interval 0.500, RX interval 0.500 > Session up time 2w1d 16:52:42, previous down time 00:00:00 > Local diagnostic None, remote diagnostic None > Remote state Up, version 1 > Session type: Single hop BFD > Min async interval 0.500, min slow interval 1.000 > Adaptive async TX interval 0.500, RX interval 0.500 > Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 > Remote min TX interval 0.100, min RX interval 0.010, multiplier 5 > Local discriminator 20, remote discriminator 3118078092 > Echo mode disabled/inactive Session ID: 0x0 > > > > > > >On Apr 27, 2021, at 12:27 PM, Justin Krejci <JKrejci(a)USINTERNET.COM<mailto:JKrejci@USINTERNET.COM>> wrote: > >We are not getting identical BFD timers or multiplier values from RS1 and RS2. > >(added blank lines for readability) >usi-cr02-mpls#show bfd peers bfd interface ethernet24/1 detail | i ^Peer|^Received|^TxI >Peer Addr 206.108.255.1, Intf Ethernet24/1, Type normal, State Up >TxInt: 500, RxInt: 500, Multiplier: 3 >Received RxInt: 500, Received Multiplier: 3 >Peer Addr 206.108.255.2, Intf Ethernet24/1, Type normal, State Up >TxInt: 500, RxInt: 500, Multiplier: 3 >Received RxInt: 10, Received Multiplier: 5 >Peer Addr 2001:504:27::d1af:0:1, Intf Ethernet24/1, Type normal, State Up >TxInt: 500, RxInt: 500, Multiplier: 3 >Received RxInt: 500, Received Multiplier: 3 >Peer Addr 2001:504:27::d1af:0:2, Intf Ethernet24/1, Type normal, State Up >TxInt: 500, RxInt: 500, Multiplier: 3 >Received RxInt: 10, Received Multiplier: 5 > > > > >________________________________ >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

April 30, 2021

Re: Zayo Belle Plaine - April 15th

by Frank Bulk

Has someone HUP’d it, yet? Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos Sent: Tuesday, April 27, 2021 12:54 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Zayo Belle Plaine - April 15th Same here. Perhaps the BFD daemon on rs2 needs to be HUP’d to pick up values in config file? Detect Transmit Address State Interface Time Interval Multiplier 2001:504:27::d1af:0:1 Up xe-0/1/0.0 1.500 0.500 3 Client BGP, TX interval 0.500, RX interval 0.500 Session up time 2w1d 16:53:02, previous down time 00:00:00 Local diagnostic None, remote diagnostic None Remote state Up, version 1 Session type: Single hop BFD Min async interval 0.500, min slow interval 1.000 Adaptive async TX interval 0.500, RX interval 0.500 Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 Remote min TX interval 0.500, min RX interval 0.500, multiplier 3 Local discriminator 19, remote discriminator 2630753610 Echo mode disabled/inactive Session ID: 0x0 Detect Transmit Address State Interface Time Interval Multiplier 2001:504:27::d1af:0:2 Up xe-0/1/0.0 2.500 0.500 3 Client BGP, TX interval 0.500, RX interval 0.500 Session up time 2w1d 16:52:42, previous down time 00:00:00 Local diagnostic None, remote diagnostic None Remote state Up, version 1 Session type: Single hop BFD Min async interval 0.500, min slow interval 1.000 Adaptive async TX interval 0.500, RX interval 0.500 Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 Remote min TX interval 0.100, min RX interval 0.010, multiplier 5 Local discriminator 20, remote discriminator 3118078092 Echo mode disabled/inactive Session ID: 0x0 On Apr 27, 2021, at 12:27 PM, Justin Krejci <JKrejci(a)USINTERNET.COM<mailto:JKrejci@USINTERNET.COM>> wrote: We are not getting identical BFD timers or multiplier values from RS1 and RS2. (added blank lines for readability) usi-cr02-mpls#show bfd peers bfd interface ethernet24/1 detail | i ^Peer|^Received|^TxI Peer Addr 206.108.255.1, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 500, Received Multiplier: 3 Peer Addr 206.108.255.2, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 10, Received Multiplier: 5 Peer Addr 2001:504:27::d1af:0:1, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 500, Received Multiplier: 3 Peer Addr 2001:504:27::d1af:0:2, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 10, Received Multiplier: 5 ________________________________ 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

April 30, 2021

Re: Zayo Belle Plaine - April 15th

by Andrew Hoyos

Same here. Perhaps the BFD daemon on rs2 needs to be HUP’d to pick up values in config file? Detect Transmit Address State Interface Time Interval Multiplier 2001:504:27::d1af:0:1 Up xe-0/1/0.0 1.500 0.500 3 Client BGP, TX interval 0.500, RX interval 0.500 Session up time 2w1d 16:53:02, previous down time 00:00:00 Local diagnostic None, remote diagnostic None Remote state Up, version 1 Session type: Single hop BFD Min async interval 0.500, min slow interval 1.000 Adaptive async TX interval 0.500, RX interval 0.500 Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 Remote min TX interval 0.500, min RX interval 0.500, multiplier 3 Local discriminator 19, remote discriminator 2630753610 Echo mode disabled/inactive Session ID: 0x0 Detect Transmit Address State Interface Time Interval Multiplier 2001:504:27::d1af:0:2 Up xe-0/1/0.0 2.500 0.500 3 Client BGP, TX interval 0.500, RX interval 0.500 Session up time 2w1d 16:52:42, previous down time 00:00:00 Local diagnostic None, remote diagnostic None Remote state Up, version 1 Session type: Single hop BFD Min async interval 0.500, min slow interval 1.000 Adaptive async TX interval 0.500, RX interval 0.500 Local min TX interval 0.500, minimum RX interval 0.500, multiplier 3 Remote min TX interval 0.100, min RX interval 0.010, multiplier 5 Local discriminator 20, remote discriminator 3118078092 Echo mode disabled/inactive Session ID: 0x0 > On Apr 27, 2021, at 12:27 PM, Justin Krejci <JKrejci(a)USINTERNET.COM> wrote: > > We are not getting identical BFD timers or multiplier values from RS1 and RS2. > > (added blank lines for readability) > usi-cr02-mpls#show bfd peers bfd interface ethernet24/1 detail | i ^Peer|^Received|^TxI > > Peer Addr 206.108.255.1, Intf Ethernet24/1, Type normal, State Up > TxInt: 500, RxInt: 500, Multiplier: 3 > Received RxInt: 500, Received Multiplier: 3 > > Peer Addr 206.108.255.2, Intf Ethernet24/1, Type normal, State Up > TxInt: 500, RxInt: 500, Multiplier: 3 > Received RxInt: 10, Received Multiplier: 5 > > Peer Addr 2001:504:27::d1af:0:1, Intf Ethernet24/1, Type normal, State Up > TxInt: 500, RxInt: 500, Multiplier: 3 > Received RxInt: 500, Received Multiplier: 3 > > Peer Addr 2001:504:27::d1af:0:2, Intf Ethernet24/1, Type normal, State Up > TxInt: 500, RxInt: 500, Multiplier: 3 > Received RxInt: 10, Received Multiplier: 5 > > > > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1>

April 27, 2021

Re: Zayo Belle Plaine - April 15th

by Doug McIntyre

On Tue, Apr 27, 2021 at 05:27:43PM +0000, Justin Krejci wrote: >We are not getting identical BFD timers or multiplier values from RS1 and RS2. I posted the configs directly out of the files earlier. I do see my sessions have different "Detect Time" for the same config, but Transmit Interval is the same. Perhaps the CPE negotiates a second link differently to provide diversity some how. Detect Transmit Address State Interface Time Interval Multiplier 206.108.255.1 Up ge-1/3/9.0 1.500 0.500 3 206.108.255.2 Up ge-1/3/9.0 2.500 0.500 3 2001:504:27::d1af:0:1 Up ge-1/3/9.0 1.500 0.500 3 2001:504:27::d1af:0:2 Up ge-1/3/9.0 2.500 0.500 3

April 27, 2021

Re: Zayo Belle Plaine - April 15th

by Justin Krejci

We are not getting identical BFD timers or multiplier values from RS1 and RS2. (added blank lines for readability) usi-cr02-mpls#show bfd peers bfd interface ethernet24/1 detail | i ^Peer|^Received|^TxI Peer Addr 206.108.255.1, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 500, Received Multiplier: 3 Peer Addr 206.108.255.2, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 10, Received Multiplier: 5 Peer Addr 2001:504:27::d1af:0:1, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 500, Received Multiplier: 3 Peer Addr 2001:504:27::d1af:0:2, Intf Ethernet24/1, Type normal, State Up TxInt: 500, RxInt: 500, Multiplier: 3 Received RxInt: 10, Received Multiplier: 5

April 27, 2021