- mice-discuss - lists.micemn.net

Re: micemn-01.micemn.net route reflector at 206.108.255.1

by Brady Kittel

I've also seen issues with failing drives not flagging because of a buggy firmware version on the raid controller or drive at least a few times on Dell servers around that vintage. On Mar 13, 2014 12:19 AM, "Doug McIntyre" <merlyn(a)iphouse.net> wrote: > We've noticed this being unresponsive several times this evening. > > I'm into the machine, but it is behaving badly, and from past > experience, (and not direct evidence since it is remote and I can't > get the relavent logs), it feels like a hard drive failing on this > system. > > Ie. it may run some of its process out of memory for some functions, > but other functions are probably locking up and not behaving correctly. > Even RAIDed as it is. > > Probably the best course of action is to bring out a fresh drive to it > and swap whatever drive is failing and let the mirror rebuild. I think > we've got some of the 80GB WD800AAJS that is part of the mirror on the > other route reflector around somewhere... > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > 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 13, 2014

micemn-01.micemn.net route reflector at 206.108.255.1

by Doug McIntyre

We've noticed this being unresponsive several times this evening. I'm into the machine, but it is behaving badly, and from past experience, (and not direct evidence since it is remote and I can't get the relavent logs), it feels like a hard drive failing on this system. Ie. it may run some of its process out of memory for some functions, but other functions are probably locking up and not behaving correctly. Even RAIDed as it is. Probably the best course of action is to bring out a fresh drive to it and swap whatever drive is failing and let the mirror rebuild. I think we've got some of the 80GB WD800AAJS that is part of the mirror on the other route reflector around somewhere... -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ 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 13, 2014

XO issues Sunday morning?

by Frank Bulk

This isn't a MICE-related question, but since so many MICE members are in the Minnesota area I thought I would ask. Sunday morning from 1:11 am to about 4:20 am we saw an unusually high number of websites time out over IPv6. We monitor 50 IPv6-enabled web sites over IPv6, performing both an ICMP check (if possible) and then HTTP over IPv6. There were at least 17 sites during that time frame that timed out on our monitoring systems' HTTP GET request. One pattern emerged -- 14 of them traceroute through an XO link that goes through Minneapolis. Here's a sample: traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from 2607:fe28:0:1000::5, port 80, from port 36274, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.395 ms 0.325 ms 0.319 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.188 ms 0.135 ms 0.185 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.612 ms 1.545 ms 1.613 ms 4 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 6.667 ms 6.566 ms 8.002 ms 5 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 6.624 ms 7.995 ms 6.602 ms 6 2610:18:18b:c000::11 (2610:18:18b:c000::11) 12.108 ms 12.075 ms 12.137 ms 7 mcr1.minneapolis-mn.us.xo.net (2610:18::30b8) 21.431 ms 21.452 ms 21.421 ms 8 vb1710.rar3.chicago-il.us.xo.net (::ffff:216.156.0.169) 30.701 ms 23.639 ms 23.771 ms .... I then looked at the daily traceroutes we have on file for all 50 sites we monitor and it looks like 15 of them go through XO. So over 93% (14 out of 15) of the sites that go through XO timed out during the 1:11 am to 4:20 am time period. Did anyone with XO connectivity see issues Sunday morning? Frank ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 10, 2014

Re: 2 x 10GE Contact?

by Steve Howard

Hi Martin, I just wanted to make sure that somebody followed up with you. Did you get a response to your question? Thanks, Steve On 03/05/2014 02:55 PM, Hannigan, Martin wrote: > Who can I talk to about adding a second 10G? > > Best, > ######################################################################## 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, 2014

2 x 10GE Contact?

by Hannigan, Martin

Who can I talk to about adding a second 10G? Best, , -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

March 5, 2014