- mice-discuss - lists.micemn.net

Netflix Ramping Up

by Jeremy Lumby

I see Netflix is ramping up, and the link to the CNS switch is getting close to saturating. The University may need to move to the main switch soon to alleviate the link. Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington, MN 55425 Main: 612-355-7740 x211 Direct: 612-392-6814 EFax: 952-873-7425 jlumby(a)mnvoip.com

Oct. 21, 2014

Re: Agenda - MICE UG 14 - 22 Oct 2014

by Shaun Carlson

Thanks for the reminder, I even forgot my own response. ;) Added. s *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com On Mon, Oct 20, 2014 at 4:19 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > Lets add the discussion of Community Strings to the agenda > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Shaun Carlson > *Sent:* Monday, October 20, 2014 4:11 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Agenda - MICE UG 14 - 22 Oct 2014 > > > > All, > > > > Please see the attached agenda, if you have any additions, please let me > know. > > > > Please see the attached minutes from our previous meeting. If you have > any additions or corrections, please let me know. > > > > One agenda note, we'll be discussing the potential change of MICE to a > 501.(c)6 non-profit organization. I've attached some discussion points and > would encourage you to *send your questions and comments to the list.* > Jeff Clancy from Stinson Leonard Street LLP will be present at the meeting > to answer questions and facilitate our next steps should we choose to move > forward with the conversion. > > > > Last, we are still in need of a sponsor for refreshments at Wednesday's > meeting, any volunteers? > > > > *Remote Dial-in Info:* > > www.webex.com > > Meeting Number: 193 507 116 > > Meeting Password: MICEUG14 > > * Please try to have a web-cam hooked up to facilitate the best possible > interaction. > > ** I will start this web conference 15 minutes prior to the meeting to > allow you to dial-in and work past any technical difficulties. > > > > One request, does anyone have a projector they could bring to the meeting > for this web conference? I would need it approx. 30 minutes prior to the > meeting. > > > > Thanks! > > > > s > > > > > *Shaun Carlson*Senior Manager of Information Technology | Arvig > > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > > ------------------------------ > > 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 >

Oct. 20, 2014

Re: Agenda - MICE UG 14 - 22 Oct 2014

by Jeremy Lumby

Lets add the discussion of Community Strings to the agenda From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Shaun Carlson Sent: Monday, October 20, 2014 4:11 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Agenda - MICE UG 14 - 22 Oct 2014 All, Please see the attached agenda, if you have any additions, please let me know. Please see the attached minutes from our previous meeting. If you have any additions or corrections, please let me know. One agenda note, we'll be discussing the potential change of MICE to a 501.(c)6 non-profit organization. I've attached some discussion points and would encourage you to send your questions and comments to the list. Jeff Clancy from Stinson Leonard Street LLP will be present at the meeting to answer questions and facilitate our next steps should we choose to move forward with the conversion. Last, we are still in need of a sponsor for refreshments at Wednesday's meeting, any volunteers? Remote Dial-in Info: www.webex.com Meeting Number: 193 507 116 Meeting Password: MICEUG14 * Please try to have a web-cam hooked up to facilitate the best possible interaction. ** I will start this web conference 15 minutes prior to the meeting to allow you to dial-in and work past any technical difficulties. One request, does anyone have a projector they could bring to the meeting for this web conference? I would need it approx. 30 minutes prior to the meeting. Thanks! s Shaun Carlson Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Oct. 20, 2014

Agenda - MICE UG 14 - 22 Oct 2014

by Shaun Carlson

All, Please see the attached agenda, if you have any additions, please let me know. Please see the attached minutes from our previous meeting. If you have any additions or corrections, please let me know. One agenda note, we'll be discussing the potential change of MICE to a 501.(c)6 non-profit organization. I've attached some discussion points and would encourage you to *send your questions and comments to the list.* Jeff Clancy from Stinson Leonard Street LLP will be present at the meeting to answer questions and facilitate our next steps should we choose to move forward with the conversion. Last, we are still in need of a sponsor for refreshments at Wednesday's meeting, any volunteers? *Remote Dial-in Info:* www.webex.com Meeting Number: 193 507 116 Meeting Password: MICEUG14 * Please try to have a web-cam hooked up to facilitate the best possible interaction. ** I will start this web conference 15 minutes prior to the meeting to allow you to dial-in and work past any technical difficulties. One request, does anyone have a projector they could bring to the meeting for this web conference? I would need it approx. 30 minutes prior to the meeting. Thanks! s *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

Oct. 20, 2014

Re: Route Server Announcement Control?

by Shaun Carlson

This is a good discussion. I'll add it to our upcoming agenda to review in addition to our discussion here. I, too, am in favor of the community strings. s On Saturday, October 18, 2014, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > I would like to voice my opinion in support of community strings. I had 2 > incidents a while ago where a member connected to the route server had a > saturated link. It was impacting the quality of my customers > connectivity. I wish I had the ability to just not announce to the one > member, instead of the all or nothing option we currently have with the > route servers. > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <javascript:;>] > On Behalf Of Doug McIntyre > Sent: Friday, October 17, 2014 5:52 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <javascript:;> > Subject: Re: [MICE-DISCUSS] Route Server Announcement Control? > > On Fri, Oct 17, 2014 at 10:19:16PM +0000, Charles Monson wrote: > > Do the MICE route servers offer any way to control BGP announcement to > specific peers? I didn't see anything on the micemn.net website about > ways to do that. With some of the larger content providers connecting to > the exchange, the folks who have mostly inbound traffic might want a way to > stop the route servers announcements to those potentially high traffic > peers without entirely withdrawing advertisements to the route servers. > > > > Some of the other exchanges we connect at let you send a community > indicating the ASN you don't want your prefixes advertisements to reach > (e.g. you send a community of "0:11796" to stop the route servers from > advertising your prefixes to Airstream). It would be nice to have something > similar at MICE. Is this something already supported that I missed? Or > something that may be considered as a future feature? > > > We do not have any community filters setup currently. > > BIRD supports communities and filtering, but nobody has asked about it > prior to now. > > It looks like a huge example is at > > http://download.de-cix.net/bird.conf.gz > > Useful for others? > > -- > Doug McIntyre <merlyn(a)iphouse.net > <javascript:;>> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

Oct. 19, 2014

Re: Route Server Announcement Control?

by Shaun Carlson

This is a good discussion. I'll add it to our upcoming agenda to review in addition to our discussion here. I, too, am in favor of the community strings. s On Saturday, October 18, 2014, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > I would like to voice my opinion in support of community strings. I had 2 > incidents a while ago where a member connected to the route server had a > saturated link. It was impacting the quality of my customers > connectivity. I wish I had the ability to just not announce to the one > member, instead of the all or nothing option we currently have with the > route servers. > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <javascript:;>] > On Behalf Of Doug McIntyre > Sent: Friday, October 17, 2014 5:52 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <javascript:;> > Subject: Re: [MICE-DISCUSS] Route Server Announcement Control? > > On Fri, Oct 17, 2014 at 10:19:16PM +0000, Charles Monson wrote: > > Do the MICE route servers offer any way to control BGP announcement to > specific peers? I didn't see anything on the micemn.net website about > ways to do that. With some of the larger content providers connecting to > the exchange, the folks who have mostly inbound traffic might want a way to > stop the route servers announcements to those potentially high traffic > peers without entirely withdrawing advertisements to the route servers. > > > > Some of the other exchanges we connect at let you send a community > indicating the ASN you don't want your prefixes advertisements to reach > (e.g. you send a community of "0:11796" to stop the route servers from > advertising your prefixes to Airstream). It would be nice to have something > similar at MICE. Is this something already supported that I missed? Or > something that may be considered as a future feature? > > > We do not have any community filters setup currently. > > BIRD supports communities and filtering, but nobody has asked about it > prior to now. > > It looks like a huge example is at > > http://download.de-cix.net/bird.conf.gz > > Useful for others? > > -- > Doug McIntyre <merlyn(a)iphouse.net > <javascript:;>> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

Oct. 19, 2014

Re: Route Server Announcement Control?

by Jeremy Lumby

I would like to voice my opinion in support of community strings. I had 2 incidents a while ago where a member connected to the route server had a saturated link. It was impacting the quality of my customers connectivity. I wish I had the ability to just not announce to the one member, instead of the all or nothing option we currently have with the route servers. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Friday, October 17, 2014 5:52 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Route Server Announcement Control? On Fri, Oct 17, 2014 at 10:19:16PM +0000, Charles Monson wrote: > Do the MICE route servers offer any way to control BGP announcement to specific peers? I didn't see anything on the micemn.net website about ways to do that. With some of the larger content providers connecting to the exchange, the folks who have mostly inbound traffic might want a way to stop the route servers announcements to those potentially high traffic peers without entirely withdrawing advertisements to the route servers. > > Some of the other exchanges we connect at let you send a community indicating the ASN you don't want your prefixes advertisements to reach (e.g. you send a community of "0:11796" to stop the route servers from advertising your prefixes to Airstream). It would be nice to have something similar at MICE. Is this something already supported that I missed? Or something that may be considered as a future feature? We do not have any community filters setup currently. BIRD supports communities and filtering, but nobody has asked about it prior to now. It looks like a huge example is at http://download.de-cix.net/bird.conf.gz Useful for others? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 18, 2014

Re: Route Server Announcement Control?

by Doug McIntyre

On Fri, Oct 17, 2014 at 10:19:16PM +0000, Charles Monson wrote: > Do the MICE route servers offer any way to control BGP announcement to specific peers? I didn't see anything on the micemn.net website about ways to do that. With some of the larger content providers connecting to the exchange, the folks who have mostly inbound traffic might want a way to stop the route servers announcements to those potentially high traffic peers without entirely withdrawing advertisements to the route servers. > > Some of the other exchanges we connect at let you send a community indicating the ASN you don't want your prefixes advertisements to reach (e.g. you send a community of "0:11796" to stop the route servers from advertising your prefixes to Airstream). It would be nice to have something similar at MICE. Is this something already supported that I missed? Or something that may be considered as a future feature? We do not have any community filters setup currently. BIRD supports communities and filtering, but nobody has asked about it prior to now. It looks like a huge example is at http://download.de-cix.net/bird.conf.gz Useful for others? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 17, 2014

Route Server Announcement Control?

by Charles Monson

Do the MICE route servers offer any way to control BGP announcement to specific peers? I didn't see anything on the micemn.net website about ways to do that. With some of the larger content providers connecting to the exchange, the folks who have mostly inbound traffic might want a way to stop the route servers announcements to those potentially high traffic peers without entirely withdrawing advertisements to the route servers. Some of the other exchanges we connect at let you send a community indicating the ASN you don't want your prefixes advertisements to reach (e.g. you send a community of "0:11796" to stop the route servers from advertising your prefixes to Airstream). It would be nice to have something similar at MICE. Is this something already supported that I missed? Or something that may be considered as a future feature? Charles Monson Associate Network Administrator Airstream Communications, LLC Wisconsin Independent Network, LLC

Oct. 17, 2014

FW: MICE L2 Security Project

by Anthony Anderberg

As a reminder, we're planning on making the last of the changes below that will include all of our ports. As before we don't expect there to be any issues or downtime, I can be reached at 320-234-5539 if anyone has issues. Cheers, anthony Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net> From: Anthony Anderberg Sent: Wednesday, October 01, 2014 11:58 PM To: MICE Discuss (MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>); 'MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET' Subject: MICE L2 Security Project We're at a point where the L2 security team feels ready to make the config changes we've talked about in the past. Although these changes can't protect us from every scenario they should protect the exchange from the many common issues. As discussed at the last meeting member ports will be limited to 5 MAC addresses, storm control will be enabled at 20%, and spanning tree BPDU packets will be filtered. Additionally the exchange will support jumbo frames should members want to exchange them with each other. Obviously if any member needs alternate configuration we'll strive to be as accommodating as possible within the larger project goals. We do not anticipate any downtime, but will send out a group reminder before starting the configuration work. Our schedule: Thursday 10/9/2014 at 10AM = Make global config changes and port changes for beta testers Thursday 10/16/2014 at 10AM = Make port config changes for all other members The beta testers are: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. Below is the configuration we'll be using and will publish on our web site for members to review and enjoy. As always questions and comments are welcome, anthony ----------------------------- **Cisco Switch Config ** Global Config: system mtu 1998 # Already set system mtu jumbo 9198 # Already set mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent Cisco Port Config: switchport block multicast switchport block unicast # Unknown unicasts that is. switchport port-security maximum 5 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable ----------------------------- ** Juniper Switch Config ** Juniper Core Switch Global: set protocols rstp bridge-priority 1 # On the main switch stack set ethernet-switching-options storm-control interface all Juniper Port Config: set interface XXX mtu 9216 set protocols rstp interface XXX edge set ethernet-switching-options bpdu-block interface XXX set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options secure-access-port interface XXX mac-limit 5 set storm-control interface XXX level 20 -----------------------------

Oct. 16, 2014