I am working with a web site that is putting in a new server soon and
was told that the co-lo they are using is about to change isps.  I guess
the new network is not up yet since I cannot get traceroute to even get
to the point where it tries to get to a machine on the network when I
try to traceroute to the default gateway.  after 10 hops I get a !H that
the man page says is host or network unreachable: 

 5  bb2-p4-0.dllstx.sbcglobal.net (151.164.188.246)  23.623 ms  24.005 ms  22.848 ms
 6  sl-gw40-fw-3-0.sprintlink.net (144.228.39.225)  24.649 ms  24.641 ms  22.827 ms
 7  sl-bb21-fw-4-3.sprintlink.net (144.232.8.245)  24.404 ms  25.404 ms  22.367 ms
 8  sl-bb21-chi-6-0.sprintlink.net (144.232.8.53)  44.096 ms  44.869 ms  43.045 ms
 9  sl-gw34-chi-9-0.sprintlink.net (144.232.26.38)  42.653 ms  44.484 ms  42.811 ms
10  sl-sbc-107-0-0.sprintlink.net (144.223.73.146)  45.229 ms !H *  45.798 ms !H

Is this normal for new subnets? They are getting 2 /24 ranges (Class C?)
subnets and I was wondering if this is normal for newly issued ip
ranges.  whois has the co-lo name and the name of the wholesale isp
(Ameritech) registered but still no routing available to either network
from SBC in Tulsa.

What can I expect? I assume that the routing protocols in the Internet
backbone allow for discovery of new subnets and routes to them.  If this
is the case how long does it take for a new route to propagate?  The isp
in in Wisconsin and it looks like the route makes it to Chicago which
seems like the right direction but then dies on what looks like a sbc
router. SBC is Ameritech so should I suggest that the talk to them?

The co-lo tech guy is not really up on routing issues as far as I can
tell but I thought I would ask here before offering my 2 cents.  My
experience with SBC here in Tulsa has not been too encouraging either
for that matter so I thought I might try to point them in the right
direction if I can find it myself :)  

Tips appreciated.

Bret


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to