Monday, January 3, 2011

See the debug of a router when connecting with telnet

In order to see the debug on a vty line, you have to use the keyword "monitor" under vty section. This is a copy ( the debug still appear on the console line).
But this command must be entered whenever a vty line is active.
If you disconnect from a line, then you re-connect again, you need to type again the monitor command, in order to see the debug.
Let's take a look. We have 2 routers:
(192.168.15.1) tlclient f1/0 ------ f0 tlserver (192.168.15.5)
I enabled debug ip dhcp packet on the tlserver.
If I try to enter the monitor under the line vty of tlserver, I get the reply:
tlserver(config)#line vty 0 15
tlserver(config-line)#monitor
VTY must be active
VTY must be active
VTY must be active

Now I telnet from the client to the server, as there is IP communication, the debug messages appears on the server, but they do not appear on the vty line. I will enter monitor only for the line that I am using:
tlclient#telnet 192.168.15.5
Trying ... Open
User Access Verification
Password:
tlserver>en
Password:
tlserver#CONF T
tlserver(config)#line vty 0
tlserver(config-line)#monitor
tlserver(config-line)#
03:04:49: IP: tableid=0, s=192.168.15.1 (FastEthernet0), d=192.168.15.5 (FastEthernet0), routed via RIB
03:04:49: IP: s=192.168.15.1 (FastEthernet0), d=192.168.15.5 (FastEthernet0), len 42, rcvd 3
03:04:49: TCP src=23952, dst=23, seq=2724698209, ack=947203130, win=3821 ACK PSH
03:04:49: IP: tableid=0, s=192.168.15.5 (local), d=192.168.15.1 (FastEthernet0), routed via RIB
03:04:49: IP: s=192.168.15.5 (local), d=192.168.15.1 (FastEthernet0), len 42, sending

So the debug for the router tlserver is copied to the vty line 0 to which tlclient is using to connect
You can follow our FTP services and solutions blog on http://www.ftp.services

I hope this was helpful, and I would like to thank you for reading

No comments:

Post a Comment