nv-l

Antw: Re: tcpConnectionClose

2000-02-09 02:24:45
Subject: Antw: Re: tcpConnectionClose
From: Michael Seibold <Michael.Seibold AT GEK DOT DE>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 9 Feb 2000 08:24:45 +0100
Another possible reason for this trap is that someone is looking at your 
Cisco-Equipement using a web browser. Every time the picture he is looking at 
updates the port status etc. a tcp-Session will be initiated/closed. You can 
shut down the http server process on your cisco box, use access lists to permit 
only specific users access to the box etc.



>>> Leslie Clark <lclark AT US.IBM DOT COM> 08.02.2000  21.35 Uhr >>>
A repost of an explanation for a flood of tcpconnectclose traps...
- - - - - - - - -   - - - - - - - - - - - - - - -
I've had this problem before when migrating from rsrb to dlsw.  The source
of
the problem was a leftover source-bridge remote-peer statement in the cisco
config (with no matching peer statement on the remote router).

If you query the mib2 tcpConnTable for the routers in question, you should
see
the ip addresses that are the source of the trouble.  (You may need to
issue
the query several times to see which connections keep opening and closing.)

Hope that helps...

Mike Flood
Lands' End
Dodgeville, WI
- - - - - - - - - - - - - - - - - - -

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit


---------------------- Forwarded by Leslie Clark/Southfield/IBM on
02/08/2000 03:33 PM ---------------------------

Duane Waddle/Nashville/IBM@IBMUS AT UCSBVM.UCSB DOT EDU> on 02/08/2000 03:18:17 
PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

Sent by:  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:  Re: tcpConnectionClose



Based on my experiments w/ IOS 11.3, you will need to kill ALL snmp traps
coming from the box -- probably not your desire.  I'd suggest filtering it
at the ruleset level, or configuring trapd to "log only" for that trap.

Is that 1 or 2 per second per router, or 1 or 2 per second total?  What are
these routers doing (DLSW, RSRB, etc..)??


--D

Duane Waddle
waddle1 AT us.ibm DOT com 
"With sufficient thrust, pigs fly just fine..."  -- RFC1925


Gord Michaels <gord_michaels AT HOTMAIL DOT COM>@UCSBVM.UCSB.EDU> on 02/08/2000
02:00:39 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

Sent by:  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:  tcpConnectionClose



Hello All.

Does anyone know if and how I can turn just this trap off on my Cisco
Routers? Or do must I disable a complete catregory? I am getting 1 or 2 per
sec.

snmp-server disable trap ?????

Any help appreciated.

Gord Michaels.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


<Prev in Thread] Current Thread [Next in Thread>
  • Antw: Re: tcpConnectionClose, Michael Seibold <=