- mice-discuss - lists.micemn.net

Re: Update for Akamai (AS 20940) < > MICE

by Jason Hanke

This is the right list. Not everyone follows it. On Apr 27, 2016 7:17 AM, "Hannigan, Martin" <marty(a)akamai.com> wrote: > > I haven't seen this approach to an administrative operational message > before. Isnt this the right list? This is routine stuff. *shrug* > > Best, > > -M< > > On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby(a)MNVOIP.COM > <jlumby(a)mnvoip.com>> wrote: > > Thanks Marty, If someone with appropriate permissions could copy Marty's > email to the announce list, I feel it should reach more of the membership > since not everyone monitors the discuss list. > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET > <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *Hannigan, Martin > *Sent:* Tuesday, April 26, 2016 9:34 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net> > *Subject:* [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE > > > > > > Greetings everyone. And Reid. :-) > > > > Our implementation is proceeding and we’re projecting that we’ll be moving > bits back to the exchange in the next few weeks. > > > > Unfortunately, we’re dropping our route server sessions permanently. > Everyone who is now route server only will need to established bi lateral > peering. Send your peering request to peering(a)akamai.com with the > requisite details (ASN, peer addresses). If you had a direct session > previously, we have not forgotten it and there’s no need to restate. > Traffic will return slowly, first with our SSL bits and then full on edge a > few weeks after that. > > > > Thanks for your patience and for helping to build a better Internet in MSP. > > > > Best, > > > > Martin Hannigan // AS 20940 // AS 32787 > > > > > > > > > > > > > > > ------------------------------ > > 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-2…> > > ------------------------------ > > 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-2…> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

April 27, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug* Best, -M< On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby(a)MNVOIP.COM<mailto:jlumby@mnvoip.com>> wrote: Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@lists.iphouse.net> Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we're projecting that we'll be moving bits back to the exchange in the next few weeks. Unfortunately, we're dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there's no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________ 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-2…> ________________________________ 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-2…>

April 27, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Jeremy Lumby

Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

April 27, 2016

Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787

April 27, 2016

Re: HE issue this afternoon

by Brady Kittel

I know they had something with their Chicago router today. We opened a ticket with them when we lost routes through our separate transit link with them for about 5 minutes earlier today. On Apr 26, 2016 3:30 PM, "Frank Bulk" <fbulk(a)mypremieronline.com> wrote: > During this afternoon’s HE hiccup ( > https://puck.nether.net/pipermail/outages/2016-April/008962.html) there > was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, > and 23. Here’s an example: > > > > > > Anyone know what that’s about? > > > > Frank > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

April 27, 2016

Re: HE issue this afternoon

by Justin Krejci

HE reported to me their issue was in Chicago. ________________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Doug McIntyre [merlyn(a)IPHOUSE.NET] Sent: Tuesday, April 26, 2016 3:41 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > Anyone know what that's about? I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 26, 2016

Re: HE issue this afternoon

by Doug McIntyre

On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > Anyone know what that's about? I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 26, 2016

Re: HE issue this afternoon

by Dale W. Carder

Given the rate, it looks like a 10Mbit/sec storm-control policer. Dale Thus spake Frank Bulk (fbulk(a)MYPREMIERONLINE.COM) on Tue, Apr 26, 2016 at 08:30:07PM +0000: > During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: > > [cid:image001.png@01D19FD0.2A25A860] > > Anyone know what that's about? > > Frank

April 26, 2016

Re: HE issue this afternoon

by Shaun Carlson

And, of course, if I actually read your original email, I would know that you already mentioned the "hiccup" and wouldn't repeat the fact. During the event, were others trying to route through the cluster to get to HE? s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com On Tue, Apr 26, 2016 at 4:35 PM, Shaun Carlson <shaun.carlson(a)arvig.com> wrote: > According to our ticket, HE had a router failure at around that time. > > s > > > > *Shaun Carlson*Director of Information Technology | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > On Tue, Apr 26, 2016 at 4:30 PM, Frank Bulk <fbulk(a)mypremieronline.com> > wrote: > >> During this afternoon’s HE hiccup ( >> https://puck.nether.net/pipermail/outages/2016-April/008962.html) there >> was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, >> and 23. Here’s an example: >> >> >> >> >> >> Anyone know what that’s about? >> >> >> >> Frank >> >> ------------------------------ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > >

April 26, 2016

Re: HE issue this afternoon

by Shaun Carlson

According to our ticket, HE had a router failure at around that time. s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com On Tue, Apr 26, 2016 at 4:30 PM, Frank Bulk <fbulk(a)mypremieronline.com> wrote: > During this afternoon’s HE hiccup ( > https://puck.nether.net/pipermail/outages/2016-April/008962.html) there > was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, > and 23. Here’s an example: > > > > > > Anyone know what that’s about? > > > > Frank > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

April 26, 2016

HE issue this afternoon

by Frank Bulk

During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: [cid:image001.png@01D19FD0.2A25A860] Anyone know what that's about? Frank

April 26, 2016

Fwd: Invite to Target's Network Engineering event!

by David Farmer

I'll be at the ARIN meeting next week, but maybe some other MICEers would be interested in attending. ---------- Forwarded message ---------- From: Beatrice Nguyen <hit-reply(a)linkedin.com> Date: Fri, Apr 15, 2016 at 9:13 AM Subject: Invite to Target's Network Engineering event! To: David Farmer <farmer(a)umn.edu> Hi David, Happy Friday! I wanted to send a quick note to invite you to our "Target Network Engineering - Learning and Development" event on Monday, April 18 at the Target Plaza Commons. This is a unique opportunity as we are trying to bring the network engineering community together in the Twin Cities. So come to this free event where we'll provide food, beverages (includes alcohol), and tons of networking! Join Principal Engineers from Target as they discuss an innovative approach for the continuous development of Network Engineers within a company. The evening will include an overview of Target’s Cisco Network Learning Group, live sample demonstrations of technical tutorials, a question and answer panel, and time to network with fellow Network Engineers. You can sign up for the event here and feel free to share as well: http://www.meetup.com/Skyway-Software-Symposium/events/230117097/ Network newcomers, veterans, and all those in between are welcome! Hope to see you there! Bea beatrice.nguyen(a)target.com -- =============================================== 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 ===============================================

April 15, 2016

Montreal Internet Exchange Reaches Milestone

by Mike Hemphill

All, Thought you would find this interesting relative to where MICE is at. I see that the peak last week was north of 72Gig and I count over 65 members. You are doing great things! Congrats!!! Mike Montreal Internet Exchange Reaches Milestone On Path To New Peaks, Reinforcing The Value Of Independent Internet Exchange Model Cologix Inc. April 13, 2016 8:10 AM QIX attracts 50 peering members who realize localized, optimized network performance and reduced costs DENVER and MONTREAL , April 13, 2016 /CNW/ -- Network, content and Internet service providers continue to ramp up interest in the independent, member-run Internet exchange model employed by the Montreal Internet Exchange (www.qix.ca <http://www.qix.ca/> ) <http://www.qix.ca/> , a nonprofit organization working to create a more robust, high-performing Internet in the province of Quebec . QIX recently reached 50 peering members, including some of the largest content providers and cloud service providers in the world. "It has been immensely gratifying to see QIX establish itself as a key exchange point, with traffic peaking over 35 gigabits per second (Gbps)," commented QIX Board of Directors Chair and Interconnection Relations at Google Inc. Sylvie LaPerriere . "This progress underscores the value of QIX as an important component of the Internet fabric serving Eastern Canada and the growth of traffic localization at the Internet's edge. QIX members are finding accelerated traffic flow, reduced IP transit costs and enhanced data sovereignty through the peering arrangements facilitated by QIX. The strong upticks in membership levels and aggregate traffic are a testament to the significance of Montreal on the overall network map." QIX launched in April 2013 with nodes at both 625 and 1250 Rene-Levesque Boulevard West and support from the Quebec Scientific Information Network (RISQ) and Cologix. QIX traffic is exchanged locally in Quebec , while non-QIX Internet traffic that originates in Quebec is often routed to major networking hubs like Chicago and New York City , then back to the enduser in Quebec . This inefficient routing often diminishes network performance and the user experience while increasing latency, costs and risk. "The success of QIX has created a new institution for the benefit of the Internet community in Montreal , which is a model for independent Internet Exchanges in markets across North America ," commented Cologix Chief Operating Officer Graham Williams . "Cologix is a proud supporter of QIX, especially because of the value the exchange delivers to the local Montreal economy and broader Canadian tech infrastructure." About Cologix Inc. Cologix provides reliable, secure, scalable data center and interconnection solutions from 24 prime interconnection locations across 9 strategic North American edge markets. Over 1,600 leading network, managed services, cloud, media, content, financial services and enterprise customers trust Cologix to support their business critical infrastructure and connect them to customers, vendors and partners. Our dedicated, experienced local teams and scalable solutions enable us to provide industry-leading customer service and the ability to successfully support customers at the Internet's new edge. For a tour of one of our data centers in Columbus , Dallas , Jacksonville , Lakeland , Minneapolis , Montreal , New Jersey , Toronto or Vancouver visit www.cologix.com <http://www.cologix.com/> or email sales(a)cologix.com. Follow Cologix on LinkedIn <https://www.linkedin.com/company/1881451> and Twitter <https://twitter.com/Cologix4Colo> . To view the original version on PR Newswire, visit:http://www.prnewswire.com/news-releases/montreal-internet-exchange-rea ches-milestone-on-path-to-new-peaks-reinforcing-the-value-of-independent-int ernet-exchange-model-300250586.html SOURCE Cologix Inc. Contact: Britni Myers Cologix, Inc., Britni.myers(a)cologix.com, 720.940.2564, http://www.cologix.com Mike Hemphill Hemphill Professional Services 612-812-5242 <mailto:HempProSvs@gmail.com> HempProSvs(a)gmail.com

April 15, 2016

Re: CNS Port addition

by Doug McIntyre

On Thu, Apr 14, 2016 at 10:13:52AM -0500, Jason Hanke wrote: > Please at xe-2/0/15 on Main Switch to the CNS remote switch LAG (AE5). The > port is to accommodate growth. I've configured the switch and added in xe-2/0/15 into AE5. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 14, 2016

Re: CNS Port addition

by Dean Bahls

Thanks Jay! Dean From: Jason Hanke [mailto:jayhanke@neutralpath.net] Sent: Thursday, April 14, 2016 10:14 AM To: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Dean Bahls <dean.bahls(a)cooperative-networks.com> Subject: CNS Port addition Please at xe-2/0/15 on Main Switch to the CNS remote switch LAG (AE5). The port is to accommodate growth. There are no IP address changes. Dean, Please send your Juniper Compatible SFP+ optic to Cologix for installation with your x-conn. Thanks! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net <mailto:jayhanke@neutralpath.net> www.neutralpath.net <http://www.neutralpath.net>

April 14, 2016

CNS Port addition

by Jason Hanke

Please at xe-2/0/15 on Main Switch to the CNS remote switch LAG (AE5). The port is to accommodate growth. There are no IP address changes. Dean, Please send your Juniper Compatible SFP+ optic to Cologix for installation with your x-conn. 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

April 14, 2016

Re: Please Welcome LTD Broadband to MICE

by Doug McIntyre

On Mon, Apr 11, 2016 at 05:00:44PM -0500, Jason Hanke wrote: > Name: LTD Broadband > Port: Neutral Path Remote ge-0/0/1 > ASN: 394330 > IPv4: 206.108.255.68/24 > IPv6: 2001:504:27:0:6:045A::1/64 > Contact: corey.hauer(a)ltdbroadband.com > > Webserver and Route server configuration please! I've got the route servers all set for them. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

April 12, 2016

Please Welcome LTD Broadband to MICE

by Jason Hanke

Name: LTD Broadband Port: Neutral Path Remote ge-0/0/1 ASN: 394330 IPv4: 206.108.255.68/24 IPv6: 2001:504:27:0:6:045A::1/64 Contact: corey.hauer(a)ltdbroadband.com Webserver and Route server configuration please! Welcome Aboard! -- 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

April 11, 2016

Re: Please Welcome Velocity Telephone to MICE!

by Richard Laager

On 03/31/2016 10:19 AM, anthonyanderberg(a)nu-telecom.net wrote: > After a little discussion in the tech committee I’ve changed their > interface to ge-1/1/3 to save on 10G interfaces. Good call! I've updated the website. -- Richard

March 31, 2016

Re: Please Welcome Velocity Telephone to MICE!

by Jason Hanke

ok, I updated the assignment sheets. On Thu, Mar 31, 2016 at 10:19 AM, anthonyanderberg(a)nu-telecom.net < anthonyanderberg(a)nu-telecom.net> wrote: > After a little discussion in the tech committee I’ve changed their > interface to ge-1/1/3 to save on 10G interfaces. > > > > > > Cheers, > > anthony > > > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Jason Hanke > *Sent:* Wednesday, March 30, 2016 3:01 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Please Welcome Velocity Telephone to MICE! > > > > Name: Velocity Telephone > > Port: ge-2/0/4 (Main switch, note fiber 1G not 10G) > > ASN: 15250 > > IPv4: 206.108.255.56/24 > > IPv6: 2001:504:27:0:0:3b92::1/64 > > Contact: noc(a)velocitytelephone.com > > > > Website and Route Server Configuration Please! > > > > Welcome Aboard! > > > > -- > > 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 > > > ------------------------------ > > 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 > -- 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

March 31, 2016

Re: Please Welcome Velocity Telephone to MICE!

by anthonyanderberg＠nu-telecom.net

After a little discussion in the tech committee I’ve changed their interface to ge-1/1/3 to save on 10G interfaces. Cheers, anthony From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jason Hanke Sent: Wednesday, March 30, 2016 3:01 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Please Welcome Velocity Telephone to MICE! Name: Velocity Telephone Port: ge-2/0/4 (Main switch, note fiber 1G not 10G) ASN: 15250 IPv4: 206.108.255.56/24<http://206.108.255.56/24> IPv6: 2001:504:27:0:0:3b92::1/64 Contact: noc(a)velocitytelephone.com<mailto:noc@velocitytelephone.com> Website and Route Server Configuration Please! Welcome Aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net<mailto:jayhanke@neutralpath.net> www.neutralpath.net<http://www.neutralpath.net> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 31, 2016

Re: Please Welcome Velocity Telephone to MICE!

by Todd Mueller

Great, thanks - looking forward to jumping on! Todd On 2016-03-30 17:58, Doug McIntyre wrote: > On Wed, Mar 30, 2016 at 03:01:08PM -0500, Jason Hanke wrote: >> Name: Velocity Telephone >> Port: ge-2/0/4 (Main switch, note fiber 1G not 10G) >> ASN: 15250 >> IPv4: 206.108.255.56/24 >> IPv6: 2001:504:27:0:0:3b92::1/64 >> Contact: noc(a)velocitytelephone.com >> >> Website and Route Server Configuration Please! > > Sure, all setup on both the switch (only had 10G setups there, so some > redoing), > and on the route servers now. > > Welcome!

March 30, 2016

Re: Please Welcome Velocity Telephone to MICE!

by Doug McIntyre

On Wed, Mar 30, 2016 at 03:01:08PM -0500, Jason Hanke wrote: > Name: Velocity Telephone > Port: ge-2/0/4 (Main switch, note fiber 1G not 10G) > ASN: 15250 > IPv4: 206.108.255.56/24 > IPv6: 2001:504:27:0:0:3b92::1/64 > Contact: noc(a)velocitytelephone.com > > Website and Route Server Configuration Please! Sure, all setup on both the switch (only had 10G setups there, so some redoing), and on the route servers now. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

March 30, 2016

Please Welcome Velocity Telephone to MICE!

by Jason Hanke

Name: Velocity Telephone Port: ge-2/0/4 (Main switch, note fiber 1G not 10G) ASN: 15250 IPv4: 206.108.255.56/24 IPv6: 2001:504:27:0:0:3b92::1/64 Contact: noc(a)velocitytelephone.com Website and Route Server Configuration Please! Welcome Aboard! -- 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

March 30, 2016

Re: Please welcome Packet Clearing House to MICE

by Doug McIntyre

On Tue, Mar 29, 2016 at 04:11:33PM -0500, Jason Hanke wrote: > PCH will receive 2 IP allocations for their peering connection with MICE > > Name: PCH.net > Port: TBD ipHouse Remote Switch > ASN: 42 > IPv4: 206.108.255.86/24 > IPv6: 2001:504:27:0:0:002a::1/64 > Contact: peering(a)pch.net > > Name: PCH.net > Port: TBD ipHouse Remote Switch > ASN: 3856 > IPv4: 206.108.255.87/24 > IPv6: 2001:504:27:0:0:0f10::1/64 > Contact: peering(a)pch.net > > Welcome aboard! Route reflectors all set to go when they are ready. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

March 30, 2016