- mice-discuss - lists.micemn.net

Martin Hannigan Paypal Donation
by Jason Hanke Aug. 31, 2016

Aug. 31, 2016

Marty Hannigan has donated $300 to MICE! Thanks for your support! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

1 0

MICE Pull up banner
by Jason Hanke Aug. 29, 2016

Aug. 29, 2016

Does anyone know where the MICE pull up banner is? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

2 1

Connect MN Cologix Event
by Jason Hanke Aug. 29, 2016

Aug. 29, 2016

Is anyone interested in working with me in the MICE booth at the Cologix Connect MN event? Wednesday, September 7th from 4:00 - 8:00 p.m. @ the U.S. Bank Stadium -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

6 9

Prefix count
by Frank Bulk Aug. 27, 2016

Aug. 27, 2016

We had a max IPv4 prefix count of 2000 with a warning when it hit 90%. At 10:20 am our BGP session was torn down when it apparently exceeded 2000: Aug 18 14:09:18 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:09:18 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:14:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:14:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:19:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:19:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:24:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:24:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:29:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:29:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:12:20 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:12:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:17:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:17:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:22:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:27:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:27:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:32:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:32:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 10:20:10 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1 exceeds maximum prefix limit...shutdown Aug 21 10:20:10 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Peer had exceeded the prefix limit) Aug 21 10:20:11 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2 exceeds maximum prefix limit...shutdown Aug 21 10:20:11 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Peer had exceeded the prefix limit) The Cacti graph (http://micelg.usinternet.com/cacti/graph.php?action=view&local_graph_id=236…) doesn't show that ... but is there any further confirmation that there was a short burst in routes advertised by the RR's? Frank

2 2

MICE gets a shout-out in CloudFlare blog
by Frank Bulk Aug. 19, 2016

Aug. 19, 2016

https://blog.cloudflare.com/bandwidth-costs-around-the-world/ Frank

2 1

Stealth Broadband Updated Information
by Jason Hanke Aug. 18, 2016

Aug. 18, 2016

Stealth Broadband has received their ASN from ARIN, Please update ASN and IPv6 information in the route-servers and website: Name: Stealth Broadband IPv4: 206.108.255.69/24 IPv6: 2001:504:27:0:6:07BA::1/64 ASN: 395194 Port: NP MSP1 Remote ge-0/0/2 Contact: james.urwiller(a)stealthbroadband.net Thanks! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

3 2

ipHouse Remote Switch
by Jason Hanke Aug. 11, 2016

Aug. 11, 2016

Is there any update on the ipHouse remote switch? -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

2 1

Airstream Communications Maintenance 2016/08/11
by Charles Monson Aug. 10, 2016

Aug. 10, 2016

Good Afternoon, Airstream Communications (AS11796) will be performing maintenance tonight 2016/08/11 between the hours of Midnight and 6am. We will be shutting down our BGP sessions for approximately 20 minutes to reroute traffic while work is done and turning them back up when complete. If your session to us has not returned by 6am please send an email to support(a)wins.net<mailto:support@wins.net> with your BGP AS number and we will address it as soon as possible. Charles Monson Associate Network Administrator, Airstream Communications (AS11796)

1 0

BGP sessions down...
by Frank Bulk Aug. 9, 2016

Aug. 9, 2016

Problem at MICE? Physical link is up. Frank -----Original Message----- From: nagios(a)nagios.mtcnet.net [mailto:nagios@nagios.mtcnet.net] Sent: Thursday, August 04, 2016 4:53 PM To: Frank Bulk <fbulk(a)mypremieronline.com> Subject: PROBLEM: CRITICAL alert for Premiers Spencer-facing Brocade MLXe-4 router/BGP ***** Nagios ***** This is a PROBLEM notice that Premiers Spencer-facing Brocade MLXe-4 router/BGP is CRITICAL Date/Time: Thu Aug 4 16:52:57 CDT 2016 Additional Info: CRITICAL: critical 2, warning 6 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the BGP peer state is in state connect Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the BGP peer state is in state connect Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the elapsed time the remote peer has been in the Established state or how long since this peer was last in the Established state changed from 39 days, 19 hours, 41 minutes, 12 seconds to 0 seconds Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the elapsed time the remote peer has been in the Established state or how long since this peer was last in the Established state changed from 23 days, 4 hours, 33 minutes, 7 seconds to 0 seconds Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the number of received route prefixes changed from 1763 to 0 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: 0 learned prefixes is less than the specified minimum of 1 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the number of received route prefixes changed from 10 to 0 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: 0 learned prefixes is less than the specified minimum of 1 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the number of installed route prefixes changed from 1763 to 0 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the number of installed route prefixes changed from 10 to 0 BGP state of premier.spnc-mlx.fbnt.netins.net [173.215.60.1/AS 18883]: established; prefixes (received/installed): 1/1 BGP state of AS53679-MRS-1.micemn.net [206.108.255.1/AS 53679]: established; prefixes (received/installed): 1769/1769 BGP state of AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: connect; prefixes (received/installed): 0/0 BGP state of AS6939.micemn.net [206.108.255.52/AS 6939]: established; prefixes (received/installed): 92186/91624 BGP state of AS29040.micemn.net [206.108.255.84/AS 20940]: connect; prefixes (received/installed): 0/0

3 5

route servers - bogon ASN filtering
by Andrew Hoyos Aug. 8, 2016

Aug. 8, 2016

Hi all, We recently implemented bogon ASN filtering on all transit/peering edges (see http://mailman.nanog.org/pipermail/nanog/2016-June/086078.html) There were a few participants we peer with via route servers that had bogon ASN’s in path for various prefixes which we are now rejecting. I’d suggest that we look at adding similar filtering to the route-servers as well, similar to RFC1918 filters already in place. Thoughts? — Andrew Hoyos Hoyos Consulting LLC ofc: +1 608 616 9950 andrew(a)hoyosconsulting.com http://www.hoyosconsulting.com

3 2