March 2013 - mice-discuss - lists.micemn.net

Re: MICE Route Server #1 offline?

by Frank Bulk

Sounds like it's time to get a managed PDU in place. Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Saturday, March 09, 2013 12:40 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Route Server #1 offline? On Sat, Mar 09, 2013 at 06:22:13PM +0000, Chris Scheidecker wrote: > Having trouble pinging 206.108.255.1 and BGP session dropped about 3 hours ago. Yes, the hardware does seem to be borked. If anybody is around 511 this weekend near the MICE cabinet, we probably just need the 1st server power cycled and brought back online when somebody can get to it. -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## 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

March 9, 2013

Re: Comptel Plus

by Mike Hemphill

See you there Mike Hemphill General Manager - Minneapolis 612-333-1922 office 612-812-5242 cell mike.hemphill(a)cologix.com Sent from my Samsung Epic 4G phone On Mar 9, 2013 11:15 AM, "Jay Hanke" <jayhanke(a)mankatonetworks.net> wrote: > I'll be wandering around at Comptel plus in Vegas Monday and Tuesday. If > there is anyone I should talk to while I'm there regarding MICE just let me > know. > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > PO Box 54 > 619 S Front St > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > Consulting http://www.mankatonetworks.com/ > Colo 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 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 9, 2013

Re: Comptel Plus

by Reid Fishler

I will be there as well. Reid On Sat, Mar 9, 2013 at 12:15 PM, Jay Hanke <jayhanke(a)mankatonetworks.net>wrote: > I'll be wandering around at Comptel plus in Vegas Monday and Tuesday. If > there is anyone I should talk to while I'm there regarding MICE just let me > know. > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > PO Box 54 > 619 S Front St > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > Consulting http://www.mankatonetworks.com/ > Colo 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 > -- Reid Fishler Director Hurricane Electric +1-510-580-4178 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 9, 2013

Re: MICE Route Server #1 offline?

by Doug McIntyre

On Sat, Mar 09, 2013 at 06:22:13PM +0000, Chris Scheidecker wrote: > Having trouble pinging 206.108.255.1 and BGP session dropped about 3 hours ago. Yes, the hardware does seem to be borked. If anybody is around 511 this weekend near the MICE cabinet, we probably just need the 1st server power cycled and brought back online when somebody can get to it. -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 9, 2013

MICE Route Server #1 offline?

by Chris Scheidecker

Having trouble pinging 206.108.255.1 and BGP session dropped about 3 hours ago. Chris Scheidecker - Infrastructure Engineer Atomic Data 615 North 3rd Street Minneapolis, MN 55401 612.466.2000 Main Line 612.466.2044 Direct Dial Twitter<http://twitter.com/AtomicData> | Facebook<http://www.facebook.com/AtomicDataCenters> | LinkedIn<http://www.linkedin.com/companies/atomic-data-centers> Simple. Safe. Smart. www.atomicdata.com<http://www.atomicdata.com/> This message and any information or attachments included therewith is intended only for the individual or entity named above. If the reader is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copy of this message or any information attached or contained therein is strictly prohibited. If you have received this message in error, please notify the sender by return e-mail and destroy all copies of the message and any attachments. Thank you. Please consider the environment before printing this email. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 9, 2013

Comptel Plus

by Jay Hanke

I'll be wandering around at Comptel plus in Vegas Monday and Tuesday. If there is anyone I should talk to while I'm there regarding MICE just let me know. -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net Consulting http://www.mankatonetworks.com/ Colo 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 9, 2013

Re: AS112 Project

by Owen DeLong

On Mar 7, 2013, at 10:01 AM, Richard Laager <rlaager(a)WIKTEL.COM> wrote: > On Thu, 2013-03-07 at 11:18 -0600, David Farmer wrote: >> It would be better for everyone connected to MICE >> to implement the recommendations of RFC 6761 > > If I'm reading that correctly, the requirements for a network operator > boil down to: > > 1. The following zones MUST be configured on our recursive and > authoritative DNS servers. They MUST either be empty of records > or contain records matching our uses of *routable* private > space. > 10.in-addr.arpa. > 16.172.in-addr.arpa. > 17.172.in-addr.arpa. > 18.172.in-addr.arpa. > 19.172.in-addr.arpa. > 20.172.in-addr.arpa. > 21.172.in-addr.arpa. > 22.172.in-addr.arpa. > 23.172.in-addr.arpa. > 24.172.in-addr.arpa. > 25.172.in-addr.arpa. > 26.172.in-addr.arpa. > 27.172.in-addr.arpa. > 28.172.in-addr.arpa. > 29.172.in-addr.arpa. > 30.172.in-addr.arpa. > 31.172.in-addr.arpa. > 168.192.in-addr.arpa. > > 2. The "test." zone MUST be configured on our recursive and > authoritative DNS servers. It MUST be empty of records. > > 3. The "localhost." zone MUST be configured on our recursive and > authoritative DNS servers. It MUST contain wildcard A and AAAA > records pointing to 127.0.0.1 and ::1, respectively. > You are reading it incorrectly. The RFC specifies how your name server should behave by default without you configuring anything. If you WANT to respond differently than the default stated in the document, you would have to configure your name server accordingly. Admittedly, if your name servers do not implement RFC6761 by default, then you can mimic most of what it specifies by taking the actions you state above. > I'm not sure it's possible to implement the "invalid." zone behavior > without writing a patch. Suggestions are welcome. Right… The RFC is aimed at name server developers more than name server operators. > In my network, we have #1 implemented already. I believe it's setup by > default in BIND, at least in Debian. Yes, modern versions of bind ship with RFC6761 compliance. Owen > > -- > Richard > > ######################################################################## > > 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

March 7, 2013

Re: AS112 Project

by Richard Laager

On Thu, 2013-03-07 at 11:18 -0600, David Farmer wrote: > It would be better for everyone connected to MICE > to implement the recommendations of RFC 6761 If I'm reading that correctly, the requirements for a network operator boil down to: 1. The following zones MUST be configured on our recursive and authoritative DNS servers. They MUST either be empty of records or contain records matching our uses of *routable* private space. 10.in-addr.arpa. 16.172.in-addr.arpa. 17.172.in-addr.arpa. 18.172.in-addr.arpa. 19.172.in-addr.arpa. 20.172.in-addr.arpa. 21.172.in-addr.arpa. 22.172.in-addr.arpa. 23.172.in-addr.arpa. 24.172.in-addr.arpa. 25.172.in-addr.arpa. 26.172.in-addr.arpa. 27.172.in-addr.arpa. 28.172.in-addr.arpa. 29.172.in-addr.arpa. 30.172.in-addr.arpa. 31.172.in-addr.arpa. 168.192.in-addr.arpa. 2. The "test." zone MUST be configured on our recursive and authoritative DNS servers. It MUST be empty of records. 3. The "localhost." zone MUST be configured on our recursive and authoritative DNS servers. It MUST contain wildcard A and AAAA records pointing to 127.0.0.1 and ::1, respectively. I'm not sure it's possible to implement the "invalid." zone behavior without writing a patch. Suggestions are welcome. In my network, we have #1 implemented already. I believe it's setup by default in BIND, at least in Debian. -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 7, 2013

Re: AS112 Project

by David Farmer

I'm aware of it, its discussed in RFC 6304, it wouldn't hurt anything. However, as RFC 6761 becomes in more common use the need for this should reduce significantly. It would be better for everyone connected to MICE to implement the recommendations of RFC 6761 with regards to their recursive name servers, than to build a AS112 node for MICE. http://tools.ietf.org/html/rfc6304 http://tools.ietf.org/html/rfc6761 On 3/7/13 10:55 , Jay Hanke wrote: > Is anyone familiar with the AS112 project? > > http://public.as112.net/ > > Would this be worthwhile on MICE? > > -- > Jay Hanke > CTO, CCIE #19093 > Mankato Networks LLC > PO Box 54 > 619 S Front St > Mankato, MN 56001-3838 > Google 530-618-2398 > jayhanke(a)mankatonetworks.net > http://www.mankatonetworks.com > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- ================================================ David Farmer Email: farmer(a)umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 7, 2013

AS112 Project

by Jay Hanke

Is anyone familiar with the AS112 project? http://public.as112.net/ Would this be worthwhile on MICE? -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 7, 2013