nv-l

Re: Cisco trap G-6 S-1 tcpConnectClose

1998-12-17 09:16:02
Subject: Re: Cisco trap G-6 S-1 tcpConnectClose
From: Fältman, Mikael <mifal AT WMDATA DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Thu, 17 Dec 1998 15:16:02 +0100
Are your routers configured for rsrb or dlsw ?

---
Mikael Fältman (mifal AT wmdata DOT com)
Network Services
WM-data Dataservice AB, BOX 164, S-295 22 BROMOLLA

> -----Original Message-----
> From: Mark van Kerkwyk [SMTP:kerkwyk AT COMTECH.COM DOT AU]
> Sent: den 16 december 1998 05:53
> To:   NV-L AT UCSBVM.ucsb DOT edu
> Subject:      Re: Cisco trap G-6 S-1 tcpConnectClose
> 
> Yes, me too, I am getting heaps and heaps of these and don't know why ??
> 
> Mark
> 
> 
> 
> 
> 
> Leslie Clark <lclark AT US.IBM DOT COM> on 16/12/98 13:34:35
> 
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
>       NetView <NV-L AT UCSBVM.ucsb DOT edu>
> 
> 
> 
>  To:      NV-L AT UCSBVM.ucsb DOT edu
> 
>  cc:
> 
> 
> 
>  Subject: Cisco trap G-6 S-1 tcpConnectClose
> 
> 
> 
> 
> 
> 
> 
> Anybody had trouble with lots and lots of these? The customer can't see
> what would cause
> a couple of 2500 routers to send these out at the rate of up to 1/sec.
> There was a half-baked
> install of Ciscoworks on the system, but I killed all of those daemons and
> moved the
> registration file out of sight in case somehow the application was
> generating them, to no
> avail. The only other place I've seen this was when a customer had a
> script
> running that
> repeatedly connected to the router to run something. I can filter them out
> but we really want
> to stop them. Besides the traffic (if there is any real traffic), they are
> filling up the event log,
> so we have no useful history. I appreciate any suggestions...
> 
> Cordially,
> 
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> (248) 552-4968 Voicemail, Fax, Pager

<Prev in Thread] Current Thread [Next in Thread>