[1222] in North American Network Operators' Group
Re: outages, quality monitoring, trouble tickets, etc
daemon@ATHENA.MIT.EDU (Curtis Villamizar)
Fri Dec 1 03:11:12 1995
To: Matt Zimmerman <mdz@netrail.net>
cc: Curtis Villamizar <curtis@ans.net>, Ed Morin <edm@halcyon.com>,
Nathan Stratton <nathan@netrail.net>, nanog@merit.edu
Reply-To: curtis@ans.net
In-reply-to: Your message of "Thu, 30 Nov 1995 17:01:16 EST."
<Pine.LNX.3.91.951130161916.15338O-100000@netrail.net>
Date: Fri, 01 Dec 1995 03:03:47 -0500
From: Curtis Villamizar <curtis@ans.net>
In message <Pine.LNX.3.91.951130161916.15338O-100000@netrail.net>, Matt Zimmerm
an writes:
> On Thu, 30 Nov 1995, Curtis Villamizar wrote:
>
> > 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.
>
> 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]
Try running traceroute rather than or in addition to ping. How about
if we take this off line. This may not be a pressing NANOG issue.
Curtis
