Cisco MDS-9124 Troubleshooting Guide - Page 520

Using Cisco MDS 9000 Family Tools Appendix B Troubleshooting Tools and Methodology Send documentation comments to [email protected] Table B-1 Debug Commands (continued) Debug command license logfile module ntp platform port port-channel qos radius rib rlir rscn scsi-target security snmp span svc system tlport vni vrrp vsan wwn zone Purpose Enables license debugging. Directs the debug command output to a logfile. Enables module manager debugging. Enables NTP debugging. Enables platform manager debugging. Enables port debugging. Enables PortChannel debug. Enables QOS Manager debugging. Enables RADIUS debugging. Enables RIB debugging. Enables RLIR debugging. Enables RSCN debugging. Enables scsi target daemon debugging. Enables security and accounting debugging. Enables SNMP debugging. Enables SPAN debugging. Enables SVC debugging. Enables System debugging. Enables TL Port debugging. Enables virtual network interface debugging. Enables VRRP debugging. Enables VSAN manager debugging. Enables WWN manager debugging. Enables zone server debugging. FC Ping and FC Traceroute Note Use the Fibre Channel ping and Fibre Channel traceroute features to troubleshoot problems with connectivity and path choices. Do not use them to identify or resolve performance issues. Ping and traceroute are two of the most useful tools for troubleshooting TCP/IP networking problems. The ping utility generates a series of echo packets to a destination across a TCP/IP internetwork. When the echo packets arrive at the destination, they are rerouted and sent back to the source. Using ping, you can verify connectivity to a particular destination across an IP routed network. The traceroute utility operates in a similar fashion, but can also determine the specific path that a frame takes to its destination on a hop-by-hop basis. Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x B-4 OL-9285-05