Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!PURDUE.EDU!narten
From: narten@PURDUE.EDU (Thomas Narten)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Not a good day for EGP
Message-ID: <8801172110.AA08692@percival.cs.purdue.edu>
Date: 17 Jan 88 21:10:31 GMT
References: <8801171317.aa23158@Huey.UDEL.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21

>Neighbors:
>
>	DOWN:	192.5.48.18 (purdue-cs-net) (EGP or indirect via EGP)

The list of "down" neighbors may be a bit deceiving.  The machine
192.5.48.18 hasn't peered with Purdue LSI gateway since before
Christmas. I would suggest that the LSI gateway hasn't been rebooted
in over a month and that the entry is old, but...

>However, the three EGPspeakers I watch are now crashing at intervals
>of a few hours, so the bogon generator may be barking at those
>intervals or less.

Perhaps the definition of "crashed" needs to be examined. According to
my own logs, the Purdue gateway has flawlessly responded to ICMP
echoes every 15 minutes for the last 3 days. Although the gateway can
probably reboot and completely rebuild all its route tables in only a
few minutes, it seems unlikely that I would miss every one of the
crashes.

Thomas