- mice-discuss - lists.micemn.net

Re: Cacti Update

by Jeremy Lumby

When you do the update would you mind making the individual graph titles show the member's name? It makes it much easier than going back and forth to the participants page. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Anthony Anderberg Sent: Friday, August 31, 2012 1:20 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Cacti Update That's on my plate - I'm planning on grooming those this afternoon. It just takes a couple steps to make sure I can preserve the history for our aggregate graphs. Anthony Anderberg Sr. Systems Analyst 320-234-5239 anthonyanderberg(a)nu-telecom.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Friday, August 31, 2012 12:24 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Cacti Update I was just wondering if someone was working on updating Cacti to reflect the port assignments/new switches ######################################################################## 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 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 31, 2012

Re: Cacti Update

by Anthony Anderberg

That's on my plate - I'm planning on grooming those this afternoon. It just takes a couple steps to make sure I can preserve the history for our aggregate graphs. Anthony Anderberg Sr. Systems Analyst 320-234-5239 anthonyanderberg(a)nu-telecom.net -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Friday, August 31, 2012 12:24 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Cacti Update I was just wondering if someone was working on updating Cacti to reflect the port assignments/new switches ######################################################################## 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

Aug. 31, 2012

Cacti Update

by Jeremy Lumby

I was just wondering if someone was working on updating Cacti to reflect the port assignments/new switches ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 31, 2012

Re: Problem emailing TDS

by Koch, Andrew

I have sent an email message directly to Jeremy and also left a voicemail message to follow-up. My test email to our peering(a)tdstelecom.com and my personal andrew.koch(a)tdstelecom.com were working as expected. The mail servers listed in the message below are correct (scale and ring.teldta.com) and it looks that scale did establish a TCP connection, but failed with my address being incorrect. If you are seeing trouble, don't hesitate to email or call me. Thanks, Andy Koch TDS Telecom - IP Network Operations andrew.koch(a)tdstelecom.com Desk: 608-664-4694 Cell: 608-616-0072 > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > Jeremy Lumby > Sent: Thursday, August 30, 2012 16:18 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Problem emailing TDS > > I had a problem trying to email the TDS peering address, so I tried > Andrew directly with no luck. I am suspicious of the MX record (See > below), however I see the same result on several different DNS servers on > the web. Does anyone know if TDS is having an issue? > > Jeremy > > Failed address: koch(a)tdstelecom.com > > --- Session Transcript --- > Thu 2012-08-30 16:13:42: Parsing message > <xxxxxxxxxxxxxxxxxxxxxxxx\pd35000903998.msg> > Thu 2012-08-30 16:13:42: * From: jlumby(a)mnvoip.com Thu 2012-08-30 > 16:13:42: * To: koch(a)tdstelecom.com Thu 2012-08-30 16:13:42: * Subject: > Problem with peering address Thu 2012-08-30 16:13:42: * Size (bytes): > 4984 Thu 2012-08-30 16:13:42: * Message-ID: > <57736f1c.1cd86f4.3e061c.72ae(a)mnvoip.com> > Thu 2012-08-30 16:13:42: Attempting SMTP connection to [tdstelecom.com] > Thu 2012-08-30 16:13:42: Resolving MX records for [tdstelecom.com] (DNS > Server: 127.0.0.1)... > Thu 2012-08-30 16:13:42: * P=005 S=000 D=tdstelecom.com TTL=(41) > MX=[scale.teldta.com] {216.170.201.63} Thu 2012-08-30 16:13:42: * P=010 > S=001 D=tdstelecom.com TTL=(41) MX=[ring.teldta.com] {216.170.201.64} Thu > 2012-08-30 16:13:42: Attempting SMTP connection to [216.170.201.63:25] > Thu 2012-08-30 16:13:42: Waiting for socket connection... > Thu 2012-08-30 16:13:42: * Connection established (205.215.193.100:4305 > -> 216.170.201.63:25) Thu 2012-08-30 16:13:42: Waiting for protocol to > start... > Thu 2012-08-30 16:13:42: <-- 554 scale.teldta.com Thu 2012-08-30 > 16:13:42: --> QUIT > --- End Transcript --- > > ######################################################################## > > 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

Aug. 30, 2012

Re: Problem emailing TDS

by Matthew Beckwell

Our Bilateral sessions (IPv4 + IPv6) to TDS are up and passing traffic. Came up about 10 minutes after the "all clear" email was sent out. Although I'm still using the "old" IP...I haven't added anything (secondary or otherwise). ~Matthew -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Thursday, August 30, 2012 4:18 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Problem emailing TDS I had a problem trying to email the TDS peering address, so I tried Andrew directly with no luck. I am suspicious of the MX record (See below), however I see the same result on several different DNS servers on the web. Does anyone know if TDS is having an issue? Jeremy Failed address: koch(a)tdstelecom.com --- Session Transcript --- Thu 2012-08-30 16:13:42: Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd35000903998.msg> Thu 2012-08-30 16:13:42: * From: jlumby(a)mnvoip.com Thu 2012-08-30 16:13:42: * To: koch(a)tdstelecom.com Thu 2012-08-30 16:13:42: * Subject: Problem with peering address Thu 2012-08-30 16:13:42: * Size (bytes): 4984 Thu 2012-08-30 16:13:42: * Message-ID: <57736f1c.1cd86f4.3e061c.72ae(a)mnvoip.com> Thu 2012-08-30 16:13:42: Attempting SMTP connection to [tdstelecom.com] Thu 2012-08-30 16:13:42: Resolving MX records for [tdstelecom.com] (DNS Server: 127.0.0.1)... Thu 2012-08-30 16:13:42: * P=005 S=000 D=tdstelecom.com TTL=(41) MX=[scale.teldta.com] {216.170.201.63} Thu 2012-08-30 16:13:42: * P=010 S=001 D=tdstelecom.com TTL=(41) MX=[ring.teldta.com] {216.170.201.64} Thu 2012-08-30 16:13:42: Attempting SMTP connection to [216.170.201.63:25] Thu 2012-08-30 16:13:42: Waiting for socket connection... Thu 2012-08-30 16:13:42: * Connection established (205.215.193.100:4305 -> 216.170.201.63:25) Thu 2012-08-30 16:13:42: Waiting for protocol to start... Thu 2012-08-30 16:13:42: <-- 554 scale.teldta.com Thu 2012-08-30 16:13:42: --> QUIT --- End Transcript --- ######################################################################## 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

Aug. 30, 2012

Problem emailing TDS

by Jeremy Lumby

I had a problem trying to email the TDS peering address, so I tried Andrew directly with no luck. I am suspicious of the MX record (See below), however I see the same result on several different DNS servers on the web. Does anyone know if TDS is having an issue? Jeremy Failed address: koch(a)tdstelecom.com --- Session Transcript --- Thu 2012-08-30 16:13:42: Parsing message <xxxxxxxxxxxxxxxxxxxxxxxx\pd35000903998.msg> Thu 2012-08-30 16:13:42: * From: jlumby(a)mnvoip.com Thu 2012-08-30 16:13:42: * To: koch(a)tdstelecom.com Thu 2012-08-30 16:13:42: * Subject: Problem with peering address Thu 2012-08-30 16:13:42: * Size (bytes): 4984 Thu 2012-08-30 16:13:42: * Message-ID: <57736f1c.1cd86f4.3e061c.72ae(a)mnvoip.com> Thu 2012-08-30 16:13:42: Attempting SMTP connection to [tdstelecom.com] Thu 2012-08-30 16:13:42: Resolving MX records for [tdstelecom.com] (DNS Server: 127.0.0.1)... Thu 2012-08-30 16:13:42: * P=005 S=000 D=tdstelecom.com TTL=(41) MX=[scale.teldta.com] {216.170.201.63} Thu 2012-08-30 16:13:42: * P=010 S=001 D=tdstelecom.com TTL=(41) MX=[ring.teldta.com] {216.170.201.64} Thu 2012-08-30 16:13:42: Attempting SMTP connection to [216.170.201.63:25] Thu 2012-08-30 16:13:42: Waiting for socket connection... Thu 2012-08-30 16:13:42: * Connection established (205.215.193.100:4305 -> 216.170.201.63:25) Thu 2012-08-30 16:13:42: Waiting for protocol to start... Thu 2012-08-30 16:13:42: <-- 554 scale.teldta.com Thu 2012-08-30 16:13:42: --> QUIT --- End Transcript --- ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 30, 2012

Re: IP address changes

by merlyn

On Thu, Aug 30, 2012 at 06:12:39PM +0000, Koch, Andrew wrote: > Was there consensus on v6 addressing scheme? 2001:504:27::/48 was the assigned block. Are we keeping the same last hextet here as well? Not yet. I tried to circle some people in internally since I was supposed to be helping with this part, give us a few days please. -- 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

Aug. 30, 2012

Re: IP address changes

by Koch, Andrew

> -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > merlyn > Sent: Thursday, August 30, 2012 12:59 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] IP address changes > > On Thu, Aug 30, 2012 at 12:41:00PM -0500, Jeremy Lumby wrote: > > I vaguely remember someone from the iphouse mentioning that they were > going to add secondary IP addresses to the route servers during the > outage. Just wondering if this has happened since I can only ping them on > their original addresses. > > That was Mike who is out of town this week, and the schedule of the > changeover took he and I unprepared as well. > > There, I've gone ahead and did the IPv4 entries to be 206.108.255.1 & > 206.108.255.2 since the general consensys is to keep the same IPv4 last > octet. > > Nobody should be announcing prefixes with the next hop of > 206.108.255.x yet though. > Was there consensus on v6 addressing scheme? 2001:504:27::/48 was the assigned block. Are we keeping the same last hextet here as well? Andy ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 30, 2012

Re: IP address changes

by merlyn

On Thu, Aug 30, 2012 at 12:41:00PM -0500, Jeremy Lumby wrote: > I vaguely remember someone from the iphouse mentioning that they were going to add secondary IP addresses to the route servers during the outage. Just wondering if this has happened since I can only ping them on their original addresses. That was Mike who is out of town this week, and the schedule of the changeover took he and I unprepared as well. There, I've gone ahead and did the IPv4 entries to be 206.108.255.1 & 206.108.255.2 since the general consensys is to keep the same IPv4 last octet. Nobody should be announcing prefixes with the next hop of 206.108.255.x yet though. -- 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

Aug. 30, 2012

IP address changes

by Jeremy Lumby

I vaguely remember someone from the iphouse mentioning that they were going to add secondary IP addresses to the route servers during the outage. Just wondering if this has happened since I can only ping them on their original addresses. Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington, MN 55425 Main: 612-355-7740 Direct: 612-392-6814 E-Fax: 952-873-7425 jlumby(a)mnvoip.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 30, 2012