- mice-discuss - lists.micemn.net

Re: Problem with my connection to MICE
by Keith Anderson 22 Oct '19

22 Oct '19

Thanks everyone. Another MICE member reached out to me directly and said they had a similar problem with this Brocade "feature" and advised me how to filter this unwanted traffic. The port now appears to be online and I can re-enable my peering tonight.

2 1

Re: Problem with my connection to MICE
by Keith Anderson 22 Oct '19

22 Oct '19

Thanks, Jeremy. I was hoping you could provide just that sort of detail. I'm just not sure how there would be multiple coming from my side when this is a P2P link and the switch port is in route-only mode; I may have to work with Brocade on that. I will look into it, but can you tell me if the MAC addresses appear to be all from the same vendor?

2 1

Re: Problem with my connection to MICE
by Jeremy Lumby 22 Oct '19

22 Oct '19

We are seeing Port security errors on your port for too many Mac addresses. The industry standard is one Mac address, however currently mice allows up to five. Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington MN 55425 Main 612-355-7740 Direct 612-392-6814 EFax 952-873-7425 jlumby(a)mnvoip.com -------- Original message -------- From: Keith Anderson <keith.anderson(a)MARCONET.COM> Date: 10/22/19 8:33 AM (GMT-06:00) To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Problem with my connection to MICE _____ >From : Keith Anderson [keith.anderson(a)MARCONET.COM] To : MICE-DISCUSS(a)LISTS.IPHOUSE.NET [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] Date : Tuesday, October 22 2019 08:23:08 Good morning all. I have a problem with my MICE connection and I'm wondering if anyone can give me some direction. On September 9th, my predecessor disabled our port facing MICE due to BGP flapping (his description). Since there was chatter on this board about a fiber cut that day, he thought it was related to that. Unfortunately, when I re-enabled the port, I saw similar behavior. BGP seems to flap about every three minutes, and my log indicates that link is actually dropping on that port. Even though light levels never seem to drop below -4.4db, I had Cologix check the cross connect, clean the ends of the fiber, and re-seat the sfp. None of that helped. On Wednesday I replaced the SFP, but when I enabled the port, I still saw the same behavior. Last night I disabled all of my BGP peers and brought the port back online for further layer2 testing, but I can't ping any of my peers and I'm not seeing any arp entries on this port. Anyone have any ideas what could be going on or what I should check next? I've included my port config below for reference. The log entries associated with this problem are: Oct 22 08:17:33:I:SYSTEM: port 2/4 link fault status is cleared(physical link goes down 24) Oct 22 08:17:33:I:SYSTEM: port 2/4 is down( local fault) Oct 22 08:17:33:I:System: Interface ethernet 2/4, state down - local fault Oct 22 08:17:09:I:System: Interface ethernet 2/4, state up Oct 22 08:16:45:W: Latched low RX Power warning, port 2/4 Oct 22 08:16:45:A: Latched low RX Power alarm, port 2/4 interface ethernet 2/4 port-name BGP peering with MICE Arista 5/19 XC23175 load-interval 30 no fdp enable no cdp enable route-only ip address xxx.xxx.xxx.xxx/24 no spanning-tree sflow forwarding !

1 0

Problem with my connection to MICE
by Keith Anderson 22 Oct '19

22 Oct '19

Good morning all. I have a problem with my MICE connection and I'm wondering if anyone can give me some direction. On September 9th, my predecessor disabled our port facing MICE due to BGP flapping (his description). Since there was chatter on this board about a fiber cut that day, he thought it was related to that. Unfortunately, when I re-enabled the port, I saw similar behavior. BGP seems to flap about every three minutes, and my log indicates that link is actually dropping on that port. Even though light levels never seem to drop below -4.4db, I had Cologix check the cross connect, clean the ends of the fiber, and re-seat the sfp. None of that helped. On Wednesday I replaced the SFP, but when I enabled the port, I still saw the same behavior. Last night I disabled all of my BGP peers and brought the port back online for further layer2 testing, but I can't ping any of my peers and I'm not seeing any arp entries on this port. Anyone have any ideas what could be going on or what I should check next? I've included my port config below for reference. The log entries associated with this problem are: Oct 22 08:17:33:I:SYSTEM: port 2/4 link fault status is cleared(physical link goes down 24) Oct 22 08:17:33:I:SYSTEM: port 2/4 is down( local fault) Oct 22 08:17:33:I:System: Interface ethernet 2/4, state down - local fault Oct 22 08:17:09:I:System: Interface ethernet 2/4, state up Oct 22 08:16:45:W: Latched low RX Power warning, port 2/4 Oct 22 08:16:45:A: Latched low RX Power alarm, port 2/4 interface ethernet 2/4 port-name BGP peering with MICE Arista 5/19 XC23175 load-interval 30 no fdp enable no cdp enable route-only ip address xxx.xxx.xxx.xxx/24 no spanning-tree sflow forwarding !

1 0

2019 Election Results
by AnthonyAnderberg＠nuvera.net 17 Oct '19

17 Oct '19

Richard was re-elected unanimously, thanks for your continued service! [cid:60F64B08-B963-4E01-B287-F9A49C3DDDFD-L0-001] Sent from my iPhone

2 1

MICE UG 33
by Richard Laager 14 Oct '19

14 Oct '19

Reminder: UG 33 is on Wednesday of this week (October 16) at 3:00pm Remote Conferencing: 952-562-5400 passcode MICE (6423) Location: 511 Building Cafeteria Agenda The agenda is attached. I'm behind on getting this out, so I didn't send a separate call for agenda. If you have something to add, let me know ASAP and I'll send an updated agenda. I'd like to try the modified ordering again. The idea here is to group business (official reports and things that could involve a motion/vote) before open discussion. This way, people who are not interested in the discussion can leave earlier if they wish, confident that they won't miss an official motion/vote. By shortening the "mandatory" part of the meeting, this may make the meetings more accessible. I'd like to give this a try for a couple meetings and see what people think. The UG 32 draft minutes are also attached. -- Richard

1 0

Re: Zayo Maintenance??
by Tim Fjeld 14 Oct '19

14 Oct '19

Zayo was in our DC Tuesday afternoon. They were working their way north from Omaha testing fibers and verifying connections in effort to finalize turn up of their new transport equipment. I would imagine the outage might be related to that project, but cannot say with certainty. Tim Fjeld City of Windom

6 10

MN VoIP Remote Upgrade
by Jeremy Lumby 11 Oct '19

11 Oct '19

In accordance with the MICE remote switch operator guidelines, MN VoIP will be upgrading their remote switch and uplink to the MICE core on the afternoon of October 11th at approx 2PM to keep uplink utilization under 66% of the link capacity. Prior to the maintenance, BGP will be blocked so traffic can gracefully reroute. During the maintenance connectivity will be down for approximately 15 minutes. A 100G switch will be added between the existing MN VoIP extension and the MICE core. This switch will not only increase the MN VoIP uplink from 40G to 100G, it will also make 32 100G ports available to anyone wishing to connect to MICE via MN VoIP @ 100G. I will send out a notification to the discuss list right before I commence with the maintenance. Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

3 4

Zayo Maintenance??
by James Urwiller 10 Oct '19

10 Oct '19

Does anyone know if Zayo is doing maintenance ? I find it strange that my circuit dropped at 00:04 CST. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300]

3 3

MICE 2019 Board Election
by Richard Laager 04 Oct '19

04 Oct '19

The MICE board consists of three directors with staggered 3-year terms. One position is up for election each year at our fall meeting. This year's fall meeting, UG 33, will be held on October 16 at the 511 Building. The current seat up for election is the one that I hold. At this time, the board would like to open nominations. If you or someone you know is interested in running, please reply on the MICE-DISCUSS list or contact any board member. Nominations will close September 30th. -- Richard

2 2

Please welcome Land O'Lakes to MICE!
by Jay Hanke 01 Oct '19

01 Oct '19

Name: Land O Lakes Port: Ethernet 4/39 Main Switch ASN: 14161 IPv4: 206.108.255.145/24 IPv6: 2001:504:27:0:0:3751::1/64 Peering Contact: kghugill(a)landolakes.com Route Servers- YES BFD: NO Please provide your optic to either a tech committee member (Jeremy) or to Cologix when you place your cross connect order! Also, if you haven't already please join the MICE mailing lists at micemn.net Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

2 1

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 26 Sep '19

26 Sep '19

latest Zayo update Wed 9/25/2019 4:16 PM Current update Crews have located the damage and are waiting on 811 to perform emergency locates, Estimating 60 minutes. Once the locates are done crews will be digging up 100 ft on each side of of the fiber. The reason for the extra digging is the cable is near a high pressure gas main and crews must be extra careful. ETR is 6 hours. We apologize for any inconveniences and delays along the way and will continue to work towards resolution and provide updates as they are available. Regards Joshua Johnson NCC Technician (Fiber & Facilities) | Zayo Group

4 5

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

Current update 9:51 PM: ETR 2-3 hours

1 0

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

Zayo is responding to our ticket about every hour with the standard general response "Issues are still currently being investigated by the field teams on site"

1 0

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

Zayo ticket update: Wed 9/25/2019 1:31 PM Current update, Zayo OSP is on site searching for the damage, Splicers will be on site in 1 hour, Underground construction team is on site with dig equipment and Trailer with conduit and fiber expected in 90 minutes We apologize for any inconveniences and delays along the way and will continue to work towards resolution and provide updates as they are available. Regards Joshua Johnson NCC Technician (Fiber & Facilities) | Zayo Group

3 2

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

Zayo Ticket update:Current update, Zayo crews are currently dispatching to County Rd 35 near Roberts Ave Worthington, MN as this looks to be the location of the cut, OSP is en route and splice teams are also being dispatched. We apologize for any inconveniences and delays along the way and will continue to work towards resolution and provide updates as they are available. Regards Joshua Johnson NCC Technician (Fiber & Facilities) | Zayo Group

2 1

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

Our Zayo ticket case comments from Zayo: Wed 9/25/2019 9:51AM Your case has been associated to a higher level outage in the Zayo network affecting MN please standby for further updates Wed 9/25/2019 10:51AM Issues are still currently under investigation with our field teams

1 0

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

We show on graphing that Zayo is down hard to Omaha from Windom at 8:10am. Put a ticket in with Zayo and offered to OTDR from Windom south towards Omaha. Jeff Dahna Windomnet

3 3

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

I received word from another company on the Zayo Omaha route, that Zayo thinks it is a possible fiber cut in the Worthington, MN area. Zayo fiber crew going to investigate.

1 0

Re: Anyone else see their Zayo-based link to MICE go down?
by Jeff Dahna 25 Sep '19

25 Sep '19

We cannot see the port at Bigelow, MN Zayo hut. So I'd say it is between Windom and Bigelow. Fiber cut or equipment failure/fat finger. Jeff Dahna Windomnet

1 0

Anyone else see their Zayo-based link to MICE go down?
by Frank Bulk 25 Sep '19

25 Sep '19

Our 10G dropped at 8:10 am. Frank

6 6

Anyone else down to Belle Plain since 3:45 pm?
by Frank Bulk 23 Sep '19

23 Sep '19

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

8 19

Zayo Bell Plaine
by Jeremy Lumby 20 Sep '19

20 Sep '19

Just an FYI, I have received temperature alarms from the Zayo hut in Belle Plaine again. A ticket has been opened with Zayo Jeremy Lumby Minnesota VoIP 9217 17th Ave S #216 Bloomington, MN 55425 M: 612-355-7740 D: 612-392-6814 F: 952-873-7425 jlumby(a)mnvoip.com

1 0

BGP Optimizers
by David Farmer 19 Sep '19

19 Sep '19

I found an interesting article in my LinkedIn feed last night on BGP Optimizers; https://www.itnews.com.au/news/bgp-optimisers-seem-a-good-idea-until-they-b… ? I'd be interesting if anyone in the MICE community is using a BGP Optimizer? Especially one that generates more specific prefixes in BGP. I don't want to expose anyone to ridicule, so please don't go there if anyone fesses up, even in jest, this needs to be treated seriously. However, if anyone is using a BGP Optimizer, especially one generating more specific prefixes, I think it would behoove the MICE community to put in extra defenses against propagating these more specific prefixes through the exchange and out to the Internet in general or even our own downstream customers. For example we could create a MICE-DROP BGP Community that we can tag any routes that should be dropped if they are (accidentally) announced to the MICE route server or to other MICE peers, such as these more specific routes created by a BGP Optimizer. Basically we would each add something to our routing policy, and on the MICE route servers too, looking for that BGP Community and immediately dropping any routes tag with it. Also, if anyone is using a BGP Optimizer in our community that would be a very good reason to accelerate IRR based router filtering for our exchange. Thanks. -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

5 6

Could I have a MICE admin look at the route reflectors?
by Frank Bulk 09 Sep '19

09 Sep '19

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. Any hints would be welcomed. I've shutdown those six sessions for now. Frank Sep 6 17:38:49 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:1 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:38:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:1 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:39:21 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:2 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:39:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:2 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:39:28 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.1 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:39:28 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.1 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:39:28 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.1 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x000049c3 Sep 6 17:39:33 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.2 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:39:33 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.2 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:39:36 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.2 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x000049c3 Sep 6 17:39:39 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:1 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:40:02 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:1 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:40:02 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:1 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:40:06 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:1 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x0000d063 Sep 6 17:40:22 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.1 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:40:28 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.2 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:40:48 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.1 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:40:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.1 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:41:46 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:1 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:41:51 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:2 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:41:51 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:2 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:42:00 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:2 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x0000d063 Sep 6 17:42:33 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 206.108.255.1 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x000049c3 Sep 6 17:42:34 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.1 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:42:44 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:1 (AS 53679) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Sep 6 17:42:44 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:1 (AS 53679) old state Established event RecvNotify new state Idle Sep 6 17:42:44 207.32.15.28 Rib: %BGP-3-NOTIFICATION: received from neighbor 2001:504:27::d1af:0:1 (AS 53679) 2/2 (Open Message Error/bad AS number) 4 bytes 0x0000d063 Sep 6 17:43:46 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::d1af:0:2 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:44:36 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.2 (AS 53679) old state OpenConfirm event RecvKeepAlive new state Established ... Sep 6 17:44:34 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 17:44:39 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 17:46:15 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 17:50:54 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 17:50:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:00:44 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:00:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:04:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:11:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:11:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:13:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:13:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:14:37 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:14:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:15:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:23:11 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:23:16 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:26:58 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:27:46 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:27:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::1b1b:0:1 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established Sep 6 18:33:58 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state Established event RecvNotify new state Idle Sep 6 18:34:07 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.52 (AS 6939) old state OpenConfirm event RecvKeepAlive new state Established

3 7