I now have vty 0 through 14 occupied on a router, as the idle sessions are not timing out. I have specified exec-timeout 60 0, so it should be timing out after 60 minutes, but some have been idle for 4 days. I suspect that one of the vty processes is locking the running-config as I cannot enter some commands without locking the vty session, and when entering "show running-config" I get "Unable to read configuration. Try again later".
Typing "clear line vty #" does not clear the line. Also, while typing "sh proc mem" I see that the first idle vty line session 66 is taking up 5335612 Bytes of Memory.
So I am wondering if there is an undocumented way to force kill a process or line session - or am I in need of reloading the router?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...