Here is a great one. I don’t like my console timing out. Let’s cancel the timeout. The correct command is exec-timeout 0 0, but you can do it with no exec-timeout. I’m even lazier:
R2#conf t Enter configuration commands, one per line. End with CNTL/Z. R2(config)#line con 0 R2(config-line)#no exec R2(config-line)#^Z R2# *Mar 1 14:37:03.697: %SYS-5-CONFIG_I: Configured from console by console R2#
Five minutes later, my console times out. Not only that, but it seems to have locked up. What is going on?
Luckily, I am well advanced in my lab, and I can telnet from another router. Let’s have a look:
R2#show run | sec con Building configuration... Current configuration : 4296 bytes no ip dhcp use vrf connected redistribute ospf 100 include-connected redistribute connected control-plane line con 0 privilege level 15 logging synchronous no exec R2#
Ooops!
Normally if a command is ambiguous, the CLI comes back and tells you so. Not in this case. Gotcha!
