Poking at this futher, Sprint is announcing 204.82.160/22; Digex is behind ANS; this route is not in the RADB; and since ANS insists on all routes being in the RADB, they are not accepting it, so Digex is not seeing it.
We are configured to hear this announcement at the Sprint NAP and Mae-East via AS1239 but it is not being announced. Could someone tell me *where* Sprint is announcing 204.82.160/22? I don't see it at the CIX or at any point where ANS peers with Sprint. It appears as if only 204.82/16 is being announced by MCI: BGP routing table entry for 204.82.0.0/255.255.0.0, version 724795 Paths: (1 available, best #1) advertised over EBGP 1280 3561 577 807 (aggregated by 577 192.68.66.14) 149.20.5.1 from 149.20.5.1 (149.20.64.1) Origin EGP, valid, external, atomic-aggregate, best
Fix: Either get ANS to not insist on all routes being in the RADB or submit an update to the RADB & wait for ANS to regenerate their configs.
Kai: Please don't widly accuse folks before poking into the facts. --asp@uunet.uu.net (Andrew Partan)
Thanks. <markd>