NAC down ?

Portal Home > Knowledgebase > Articles Database > NAC down ?

Posted by Cybje, 09-15-2004, 06:55 AM
I can't visit or ping both www.nac.net and my server at NAC, although I can visit another website at NAC (which is at another IP range). The problem seems to be the 207.99.0.0/16 range. A traceroute: Does anyone else have those problems ?
Posted by just4sc, 09-15-2004, 06:59 AM
Pings, tracerts, and access ok from here... Pinging nac.net [209.123.233.211] with 32 bytes of data: Reply from 209.123.233.211: bytes=32 time=79ms TTL=54 Reply from 209.123.233.211: bytes=32 time=79ms TTL=54 Reply from 209.123.233.211: bytes=32 time=79ms TTL=54 Reply from 209.123.233.211: bytes=32 time=79ms TTL=54 Ping statistics for 209.123.233.211: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 79ms, Maximum = 79ms, Average = 79ms Tracing route to nac.net [209.123.233.211] over a maximum of 30 hops: 1 11 ms 11 ms 11 ms lsanca1-wbar6-4-11-016-001.lsanca1.dsl-verizon.n et [4.11.16.1] 2 10 ms 11 ms 12 ms 4.9.14.161 3 10 ms 11 ms 11 ms so-4-1-0.bbr1.LosAngeles1.Level3.net [4.68.113.1 65] 4 11 ms 11 ms 10 ms so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9. 214] 5 11 ms 11 ms 11 ms att-level3-oc48.LosAngeles1.Level3.net [4.68.127 .134] 6 12 ms 12 ms 12 ms tbr1-p014001.la2ca.ip.att.net [12.123.29.2] 7 22 ms 21 ms 21 ms tbr2-cl3.sffca.ip.att.net [12.122.10.25] 8 21 ms 21 ms 22 ms tbr1-p012501.sffca.ip.att.net [12.122.9.137] 9 63 ms 65 ms 66 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5] 10 80 ms 80 ms 80 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1] 11 78 ms 79 ms 78 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181] 12 79 ms 79 ms 79 ms att-gige.esd1.nwr.nac.net [12.119.140.26] 13 78 ms 78 ms 78 ms 2.ge-0-0-0.gbr1.nwr.nac.net [209.123.11.213] 14 81 ms 86 ms 80 ms 0.so-7-3-0.gbr2.oct.nac.net [209.123.11.58] 15 80 ms 80 ms 79 ms smtp-out1.oct.nac.net [209.123.233.211] Trace complete. Last edited by just4sc; 09-15-2004 at 07:02 AM.
Posted by Cybje, 09-15-2004, 07:03 AM
Strange, but can you also traceroute www.nac.net? The IP is different from nac.net. The IP of my server is 207.99.44.195, are you able to ping this server? Otherwise I'll call my ISP.
Posted by Cybje, 09-15-2004, 07:13 AM
It seems to work fine now.
Posted by just4sc, 09-15-2004, 07:14 AM
Yup...tracerts ok... Tracing route to www.nac.net [207.99.0.101] over a maximum of 30 hops: 1 11 ms 11 ms 11 ms lsanca1-wbar6-4-11-016-001.lsanca1.dsl-verizon.n et [4.11.16.1] 2 11 ms 10 ms 11 ms 4.9.14.129 3 11 ms 12 ms 12 ms so-4-1-0.bbr1.LosAngeles1.Level3.net [4.68.113.1 65] 4 11 ms 12 ms 11 ms so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9. 214] 5 11 ms 10 ms 11 ms att-level3-oc48.LosAngeles1.Level3.net [4.68.127 .134] 6 12 ms 15 ms 13 ms tbr1-p014001.la2ca.ip.att.net [12.123.29.2] 7 21 ms 20 ms 20 ms tbr2-cl3.sffca.ip.att.net [12.122.10.25] 8 20 ms 20 ms 20 ms tbr1-p012501.sffca.ip.att.net [12.122.9.137] 9 64 ms 64 ms 64 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5] 10 83 ms 82 ms 81 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1] 11 80 ms 79 ms 80 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181] 12 80 ms 80 ms 80 ms att-gige.esd1.nwr.nac.net [12.119.140.26] 13 79 ms 79 ms 79 ms 2.ge-0-0-0.gbr1.nwr.nac.net [209.123.11.213] 14 84 ms 81 ms 81 ms 0.so-7-3-0.gbr2.oct.nac.net [209.123.11.58] 15 80 ms 81 ms 80 ms www.nac.net [207.99.0.101] Trace complete. Pinging 207.99.44.195 with 32 bytes of data: Reply from 207.99.44.195: bytes=32 time=78ms TTL=53 Reply from 207.99.44.195: bytes=32 time=79ms TTL=53 Reply from 207.99.44.195: bytes=32 time=78ms TTL=53 Reply from 207.99.44.195: bytes=32 time=78ms TTL=53 Ping statistics for 207.99.44.195: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 79ms, Average = 78ms Looks ok to me...
Posted by Cybje, 09-15-2004, 07:26 AM
Yep, it's back up now. I tried to ping/traceroute from 3 different networks in the Netherlands, but I didn't get reply from all 3 networks. I think something is rerouted now.
Posted by Senad, 09-15-2004, 07:28 AM
They fixed the issue around 2:50 a.m., the problem started exactly at 12:00 a.m. They are unsure about what happend there. This affected some servers while others were not affected on the network. Their senior network engineer is looking into the problem.
Posted by MattF, 09-15-2004, 08:56 AM
It is a shame there was no announcement in the forums or on NAC's status page, rather than worrying it was an issue related to one's server hardware.
Posted by Senad, 09-15-2004, 12:44 PM
Problem was the following: There was a problem with the loadbalancing between two switches, which caused some intermittent connecitivty.
Posted by Dan Grossman, 09-15-2004, 09:05 PM
May I ask where NAC's forums are? Thanks.