Serviceability Tracing Packet Commands 154375Serviceability Tracing PacketCommandsDebug commands cause the output of the enabled trace to display on a serialport or telnet console. Note that the output resulting from enabling a debugtrace always displays on the serial port. The output resulting from enabling adebug trace displays on all login sessions for which any debug trace has beenenabled. The configuration of a debug command remains in effect the wholelogin session.The output of a debug command is always submitted to the syslog utility at aDEBUG severity level. As such, it can be forwarded to a syslog server, stored inthe buffer log, or otherwise processed in accordance with the configuration ofthe syslog utility. Configuration of console logging in the syslog utility is notrequired in order to view the output of debug traces.Debug commands are provided in the normal CLI tree. Debug settings arenot persistent and are not visible in the running configuration. To view thecurrent debug settings, use the show debug command.The output of debug commands can be large and may adversely affect systemperformance.Enabling debug for all IP packets can cause a serious impact on the systemperformance; therefore, it is limited by ACLs. This means debug can beenabled for IP packets that conform to the configured ACL. This also limitsthe feature availability to only when the QoS component is available. Debugfor VRRP and ARP are available on routing builds.Commands in this ChapterThis chapter explains the following commands:debug arp debug ip igmp debug ipv6 pimdm debug ripdebug auto-voip debug ip mcache debug ipv6 pimsm debug sflowdebug clear debug ip pimdmpacketdebug isdp debug spanning-tree
