outages, quality monitoring, trouble tickets, etc

The policy toward AS4006 was set to 1:3561 2:1239 based on the
advisories for the 3 AS4006 nets that existed when we froze the
aut-num. If you add prefixes to AS4006, you don't have to do
anything except to make sure to register route objects with the
correct origin AS.

For AS that have never registered an AS690 advisory (there were 20 AS
covering 59 prefixes in the IRR) we didn't have any policy. For AS
that have never registered anything in the IRR, we don't have any
import policy and we won't be importing their routes.

We plan to run a perl program to detect new aut-nums and keep md5 sums
of prior aut-nums so we can detect changes (assuming the changed field
won't get changed). We will be basing any new import policy on the
paths seen in the IRR, just sending a notification message to the AS
affected when we change things. This will give us as reliable routing
as we have now, but less burden on others to tell us how they want us
to route towards them.

I'm hoping to be able to catch things we need to change by noting
changes to the aut-nums. Right now the tools to do this are not
available, so we need to trace paths manually. It might be that
updating prpaths is about all that is needed.

Curtis

The prefix in question was one of these three, and our networks seem to
be talking just fine. The fact that our system also sends and receives
hundreds of messages to/from AOL customers every day would seem to suggest
further that the original problem was/is with AOL. Of course, the fact
that a good percentage of their servers don't respond to pings from
here makes it difficult to isolate when this is happening. Are they
just broken in this aspect, or is this another symptom of a connectivity
problem between us? (I just tried this from another location outside our
network, and trying to ping a.mx.aol.com produced a _segfault_ (Solaris
box)...what's going on here?)

// 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]