Hi,

On Tue, Jun 09, 2009 at 09:33:38AM +0100, Phil Mayers wrote:
> Gert Doering wrote:
> >On Mon, Jun 08, 2009 at 09:39:08PM -0500, Frank Bulk - iName.com wrote:
> >>Have you tried the SNMP approach?
> >
> >What is "the SNMP approach"?
> 
> You can use SNMP to close the TCP connection. Our local docs reckon:
> 
> snmpwalk -c READCOMM -v 2c ROUTER .1.3.6.1.2.1.6.13.1.1
> 
> ...to get a list of connections, then:
> 
> snmpset -c WRITECOMM -v 2c ROUTER 
> .1.3.6.1.2.1.6.13.1.1.locip.locport.remip.remport integer 12

Thanks.  Indeed, there *is* a connection, stuck in CLOSEWAIT state.

Knowing what to look for, I can see it with "show tcp" as well, and
can clear it with "clear tcp tcb...".

I'm not sure whether it actually helped anything - now the session is
in "CLOSED" state, the VTY is still stuck, and the TCP session refuses
to "really" go away... :-(

But thanks for the explanation :-)

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             [email protected]
fax: +49-89-35655025                        [email protected]

Attachment: pgpCXyGLB81I5.pgp
Description: PGP signature

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to