I've seen several providers claim "it's AOL's fault" because the provider
themselves didn't properly set up an RADB entry so the ANS network would
carry their packets. Given that AOL is on the other side of the ANS
network, that could be a big problem. So, just sitting down and showing
the site is accessible from a dozen other sites proves nothing about it
not being the provider's problem -- it helps to show that it works in
some cases though.
Ed Morin
Northwest Nexus, Inc.
[AOL unreachability]
I've seen several providers claim "it's AOL's fault" because the provider
themselves didn't properly set up an RADB entry so the ANS network would
carry their packets. Given that AOL is on the other side of the ANS
network, that could be a big problem. So, just sitting down and showing
the site is accessible from a dozen other sites proves nothing about it
not being the provider's problem -- it helps to show that it works in
some cases though.
Hmm. I was under the impression that our maintainer object
(NETRAIL-NOC), AS object (AS4006), and route object (205.215.0.0/18,
containing the server in question) were sufficient. Do I need to go
through some additional motions to satisfy ANS? Also, this seems to
only be an intermittent problem (I would think that ANS not carrying our
packets would result in complete unreachability).
// Matt Zimmerman Chief of System Management NetRail, Inc.
// mdz@netrail.net sales@netrail.net
// (703) 524-4800 [voice] (703) 524-4802 [data] (703) 534-5033 [fax]