Hey guys!

I had problems getting to SM this evening. I went over and looked at AT+T's route server. sh ip bgp 67.18.42.0 is showing the route now being picked up via L3 (3356)(was GBLX earlier (3549)). The aggregate did not get picked up by AT+T peers for about 15 minutes (route not in table).

Just an FYI.

Matt

Err, I should say, best path was GBLX..now is L3. :-)

This is intentional as it appears to be the only way to ease the latency caused by inbound overloading in ATT's network. Once they've completed their network upgrades in Dallas, we'll start advertising routes to them again.

I can undestand if you guys intentionally stop advertising and receiving traffic from AT+T if you or they are having facility issues. What I do not understand is why they stopped learning the aggregate from other peers (L3, GBLX, UUNet, etc). Their route server shows your route as not being in their table at all (unless their route server is just acting goofy). It appears to be only affecting Comcast subscribers, though. Since AT+T is the only carrier for Comcast, this kind of leaves me wtih a delimna: Did Comcast deliberately filter out your routes?


route-server.ip.att.net does not show your route in their tables BUT if you traceroute to my box (omg.deadnet.net), it gets through.

In the immortal words of Elmer Fudd:
"There's somethin scwewy goin on here....hahahahahaha."

Clients still cant get to the sm network.

Him to server

C:Documents and SettingsMaD>tracert 69.93.232.106

Tracing route to 106.69-93-232.reverse.theplanet.com [69.93.232.106]
over a maximum of 30 hops:

1 8 ms 7 ms 7 ms 10.246.104.1
2 8 ms 10 ms 9 ms bar01-p1-0.plnehe1.fl.attbb.net [66.176.1.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * btr01-p2-1.pmbhhe1.fl.attbb.net [66.176.1.89] reports: D
estination host unreachable.

Trace complete.


Server to him

C:>tracert 66.176.238.93

Tracing route to c-66-176-238-93.se.client2.attbi.com [66.176.238.93]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 105.69-93-232.reverse.theplanet.com [69.93.232.1
05]
2 <1 ms <1 ms <1 ms ibr4-ge-0-1-0-v2.dllstx2.theplanet.com [12.96.16
0.36]
3 <1 ms 1 ms <1 ms 12.119.136.17
4 <1 ms <1 ms <1 ms gar2-p343.dlstx.ip.att.net [12.123.196.102]
5 <1 ms <1 ms <1 ms gbr5-p80.dlstx.ip.att.net [12.123.17.26]
6 1 ms 1 ms 1 ms tbr1-p012401.dlstx.ip.att.net [12.122.12.65]
7 19 ms 18 ms 18 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
8 18 ms 17 ms 17 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
9 25 ms 25 ms 25 ms gbr4-p10.ormfl.ip.att.net [12.122.12.122]
10 29 ms 29 ms 29 ms gar1-p310.fldfl.ip.att.net [12.123.218.65]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * ^C


Is there any work around for him, or is he just out of luck untill this issue is fixed?