North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: PSI woes
- From: William Allen Simpson
- Date: Thu Jun 26 01:01:41 1997
> From: firstname.lastname@example.org (Dave Rand)
> Is anyone else having routing problems with PSI?
I don't talk directly to PSI, but Morningstar/Ascend does, and I see the
peering between MCI and PSI drop for hours on a regular basis. I find
that the "host unreachable" comes from either #5 or #7 below:
5: 188.8.131.52 cpe3-fddi-1.WillowSprings.mci.net. (109 ms) (109 ms) (107 ms)
6: 184.108.40.206 bordercore2-hssi1-0.WillowSprings.mci.net. (190 ms) (136 ms) (134 ms)
7: 220.127.116.11 core3.Atlanta.mci.net. (420 ms) (501 ms) (418 ms)
8: 18.104.22.168 ast-psi-nap.Atlanta.mci.net. (199 ms) (208 ms) (301 ms)
9: 22.214.171.124 se2.sc.psi.net. (160 ms) (169 ms) (219 ms)
I'm not sure where the problem actually occurs, as WillowSprings is
rather congested, with rather variable transit times.
Apparently, all the MCI-PSI routing for the heartland (I'm in Michigan,
M-Star is in Ohio) goes through Atlanta, and there is no backup exchange
that I've seen recently (it used to be at Cornell).
I suppose this is an improvement, the path used to go Chicago,
Cleveland, Boston, NewYork, MAE-East on MCI, and back to Detroit on PSI,
before Columbus. Neither MCI nor PSI seem to be big on regional peering
at multiple points with failover....
Sure would be nice to put the "net" back in Internet.
Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32
Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2