Owen, Thanks - the reason I saw it and fews other did was because I connect through Belle Plaine and some equipment ran into a hiccup there ... talk to Jay offline if you want more details. Frank From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of DeLong, Owen Sent: Friday, August 05, 2016 7:59 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] [Peering-lists] [MICE-DISCUSS] BGP sessions down... We were still doing active maintenance on COLOGIX-MSP3 (our clusters connected to MICE), so it may have been a brief outage on our part related to that. Owen On Aug 4, 2016, at 15:09 , Frank Bulk <fbulk@mypremieronline.com<mailto:fbulk@mypremieronline.com>> wrote: Looks like it was 4:52 to 5:02 pm. And it's back up to all but one, which I need to check. Aug 4 16:52:19 192.168.0.85 BGP: Peer 206.108.255.84 DOWN (Hold Timer Expired) Aug 4 16:52:23 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Hold Timer Expired) Aug 4 16:52:24 192.168.0.85 BGP: Peer 2001:504:27::51cc:0:1 DOWN (Hold Timer Expired) Aug 4 16:52:27 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:1 DOWN (Hold Timer Expired) Aug 4 16:52:27 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:2 DOWN (Hold Timer Expired) Aug 4 16:52:27 192.168.0.85 BGP: Peer 2001:504:27::1b1b:0:1 DOWN (Hold Timer Expired) Aug 4 16:54:56 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Hold Timer Expired) Aug 4 16:54:57 192.168.0.85 BGP: Peer 206.108.255.52 DOWN (Hold Timer Expired) Aug 4 17:02:11 192.168.0.85 BGP: Peer 2001:504:27::1b1b:0:1 UP (ESTABLISHED) Aug 4 17:02:11 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Aug 4 17:02:12 192.168.0.85 BGP: Peer 206.108.255.52 UP (ESTABLISHED) Aug 4 17:02:12 192.168.0.85 BGP: Peer 2001:504:27::51cc:0:1 UP (ESTABLISHED) Aug 4 17:02:12 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:1 UP (ESTABLISHED) Aug 4 17:02:12 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:2 UP (ESTABLISHED) Aug 4 17:02:14 192.168.0.85 BGP: Peer 206.108.255.84 UP (ESTABLISHED) Aug 4 17:02:16 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Aug 4 17:02:38 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.52: exceeds warning limit 90000 Aug 4 17:05:58 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.52: exceeds warning limit 90000 <image001.png> -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Frank Bulk Sent: Thursday, August 04, 2016 5:05 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@lists.iphouse.net> Subject: Re: [MICE-DISCUSS] BGP sessions down... Thanks -- looks like it's down just to Akamai and MICE MRS #2. Since they all share the same physical path, not clear to me how this can be, but I'll start digging. Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Richard Laager Sent: Thursday, August 04, 2016 5:01 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] BGP sessions down... On 08/04/2016 04:58 PM, Frank Bulk wrote:
Problem at MICE? Physical link is up.
All of my MICE sessions (including both route servers) are up, and I can still ping across the exchange. -- Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2Dbin_wa-3FSUBED1-3DMICE-2DDISCUSS-26A-3D1&d=DQMFAg&c=96ZbZZcaMF4w0F4jpN6LZg&r=MJ9m6mlVJrWIyxSYEMDah-0oNiPbOmFEMKuZCiZZwoI&m=7xVzF9svzGGKqTYZvqjK-iiGd0YIUE3dPrxuTMp7fV8&s=rdktmGLuhD1wzx9WQNOjWt1Rko4qHtvU6egdAlzm3Sw&e=> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1