- mice-discuss - lists.micemn.net

Wikstrom Telephone MICE Port Move
by Jason Hanke Sept. 9, 2016

Sept. 9, 2016

Wikstrom Telephone is moving their connection from the Mankato Networks Remote Switch to the Main Switch The new port will be xe-2/0/6 on the main stack. IP information will remain the same. Welcome aboard (again)! -- 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

Richard Laager Board Seat
by Jason Hanke Sept. 9, 2016

Sept. 9, 2016

Richard Laager has thrown his hat in the ring for the open MICE board seat. -- 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

Candidate Question
by Jason Hanke Sept. 7, 2016

Sept. 7, 2016

Question for all candidates- Up to this point MICE has been fairly successful without any required port fees for members. There have been minor difficulties paying hardware support and annual ARIN fees. We have reached a long-term (5 year) agreement with Cologix to continue the existing no cost relationship for space and power. Do you see the finical current model as sustainable for MICE? What changes would you suggest on the business side? -- 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

11 15

MICE UG/Elections
by Jason Hanke Sept. 7, 2016

Sept. 7, 2016

We will be holding elections at the MICE UG on September 27th. As of now we have two candidates listed in the spreadsheet. Owen Delong (Akamai) James Renken (ipHouse) If your name is missing from the list or you would like to be on the list please email peering(a)micemn.net. The nomination period will close September 20th. Also, please RSVP to the Facebook event if you're planning to attend. https://www.facebook.com/events/1734560673466829/ 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 5

MICE Traffic Growth
by Jason Hanke Sept. 2, 2016

Sept. 2, 2016

Using the double counting method, MICE ran 176 Gbps using 30 minute averages Sunday night. I believe we might be the second largest non-profit ix in the US by traffic behind the SIX. Does anyone have an easy way to verify? -- 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 3

Member traffic drop
by Jason Hanke Sept. 1, 2016

Sept. 1, 2016

We're seeing a number of western MN and SD networks drop off of MICE. Is there a cut someplace? -- 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

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. 26, 2016

Aug. 26, 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