It is another thing to use debug commands on a production network that
users depend on for data ?¬‚ow. Without proper precautions, the impact of a broadly focused
debug command could make matters worse.
With proper, selective, and temporary use of debug commands, you can easily obtain
potentially useful information without needing a protocol analyzer or other third-party tool.
Other considerations for using debug commands are as follows:
?– Ideally, it is best to use debug commands during periods of lower network traf?¬?c and
fewer users. Debugging during these periods reduces the effect on other users.
?– When the information you need from the debug command is interpreted and the debug
(and other related con?¬?guration settings, if any) is undone, the router can resume its
faster switching. Problem solving can be resumed, a better-targeted action plan
created, and the network problem resolved.
All debug commands are entered in privileged EXEC mode, and most debug commands
take no arguments.
To list and see a brief description of all the debugging command options, enter the debug ?
command in privileged EXEC mode.
By default, the network server sends the output from debug commands and system error
messages to the console.
Pages:
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622