We have problems reaching www.worldspan.com (216.113.132.22) from
some locations. The common problem seems to be AT&T (AS 7018). Our
AS path towards the 216.113.128.0/19 prefix is typically
3356 7018 17228 19631
Anybody else see problems here? I note that I can ping 216.113.132.22
from some locations within our network - but not, for instance, from
route-server.ip.att.net.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
That host is not working for us either, but looks more like a host problem rather then BGP problem. I have no problem getting to other IP's in that range like 216.113.132.21 which is probably it's default gateway.
From: sthaug@nethelp.no
Sent: Monday, August 30, 2010 5:22 AM
To: nanog@nanog.orgWe have problems reaching www.worldspan.com (216.113.132.22) from
some locations. The common problem seems to be AT&T (AS 7018). Our
AS path towards the 216.113.128.0/19 prefix is typically3356 7018 17228 19631
Anybody else see problems here? I note that I can ping 216.113.132.22
from some locations within our network - but not, for instance, from
route-server.ip.att.net.Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Not sure if this would be helpful....
Similar from West Michigan-USA. I also have troubles via
Qwest (USA) and Qwest (via Colt) in Germany. I too
cannot ping that IP from these locations.
My guess is a possible node issue, not network.
#trace ip 216.113.132.22
Tracing the route to www.worldspan.net (216.113.132.22)
1 12.87.238.5 [AS 7018] 8 msec 4 msec 12 msec
2 cr82.dtrmi.ip.att.net (12.122.102.90) [AS 7018] 44 msec 40 msec 40 msec
<snip>
11 12-122-254-82.attens.net (12.122.254.82) [AS 7018] 40 msec 40 msec 40 msec
12 mdf001c7613r0004-tge-12-1.atl1.attens.net (12.129.65.142) [AS 17228] 44 msec 44 msec 40 msec
13 12.129.64.122 [AS 17228] 40 msec 40 msec
12.129.64.126 [AS 17228] 40 msec
14 10.5.158.229 40 msec
10.5.158.225 44 msec 44 msec
15 * * *
<snip>
#sh ip bgp 216.113.132.22/19
BGP routing table entry for 216.113.128.0/19, version 54509208
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
1
7018 17228 19631
12.87.238.5 from 12.87.238.5 (12.122.83.244)
Origin IGP, localpref 100, valid, external, best
From our German router (just a defgwy towards Qwest...)
#trace ip 216.113.132.22
Tracing the route to 216.113.132.22
1 209.181.1.21 12 msec 12 msec 16 msec
2 65.120.25.53 16 msec 12 msec 16 msec
3 205.171.251.110 104 msec 104 msec 108 msec
4 192.205.34.253 108 msec 108 msec 108 msec
5 12.122.134.166 128 msec 124 msec 128 msec
6 12.122.1.173 120 msec 120 msec 120 msec
7 12.123.22.110 124 msec 128 msec 128 msec
8 12.122.141.69 124 msec 124 msec 128 msec
9 12.122.254.82 128 msec 120 msec 132 msec
10 12.129.65.142 124 msec 128 msec
12.129.65.138 120 msec
11 12.129.64.122 124 msec
12.129.64.126 120 msec 120 msec
12 * * *
13 * * *
14 * * *
That host is not working for us either, but looks more like a host
problem rather then BGP problem. I have no problem getting to other
IP's in that range like 216.113.132.21 which is probably it's default
gateway.
I can ping 216.113.132.21 from all the places I have tried too. So I
agree with you, a possible host problem. *Or* it could be a problem
involving parallell links with src/dst hashing where one of the links
is not working properly.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no