On Wed, 21 Mar 2001, Joe Wood wrote:
On Wed, 21 Mar 2001, John Fraizer wrote:
Joe, a LOT of providers don't accept 198.32.4.0/24. We see it on 2 out of four paths. The other two providers are filtering it.
I can understand this; However, if I see a path, I _should_ (in theory) be able to reach the destination network.
I'm not sure why routing policy is even being brought up right now.
People have been known to default into networks as a "oh crap" backup. In that case, even if there wasn't a BGP route in your tables to the net, you would hand it off to your "default" who may or may not have a bgp route to that network. It causes the same exact behavior you're seeing now. Prior to being multihomed, I ran into this trying to go to the EXACT same site because we were defaulting into a network that (STILL) filters 198.32.4.0/24.
Also note that ISIs border is now responding with !X:
PBI seems to be fine, perhaps another border router?
10 ded3-fe8-0-0.lsan03.pbi.net (206.13.29.130) [AS 5676] 8 msec 8 msec 12 msec 11 uscisi-usc-630375.cust-rtr.pacbell.net (209.232.128.190) [AS 5673] 20 msec 20 msec 16 msec 12 isi-usc-atm.ln.net (130.152.128.1) [AS 226] 20 msec 24 msec 20 msec 13 bah.isi.edu (128.9.160.26) [AS 226] 24 msec 24 msec 24 msec 14 flag.ep.net (198.32.4.13) [AS 226] 20 msec 20 msec 20 msec
Its interesting how it has suddenly gone from !A to !X.
Joe
It's working again for us. --- John Fraizer EnterZone, Inc