S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
B-10
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Appendix B Troubleshooting Tools and Methodology
Using Cisco MDS 9000 Family Tools
•
uSecs = microseconds of CPU time in average for each process invocation.
•
1Sec = CPU utilization in percentage for the last one second.
Example B-5
show processes cpu Command
switch#
show processes cpu
PID Runtime(ms) Invoked uSecs 1Sec Process
----- ----------- -------- ----- ----- -----------
1016 7 2 3714 0.0 tftpd
1017 20627 2921172 7 0.0 syslogd
1218 299 11710 25 0.0 licmgr
1219 25 38 676 0.0 fs-daemon
1220 1558 6985 223 0.0 feature-mgr
1221 263 11772 22 0.0 fcfwd
1223 512 8996 56 0.0 capability
1237 313 29072 10 0.0 syslogd
1249 912 18815 48 0.0 xbar_client
1250 1481 6214 238 0.0 wwn
1251 1460 68079 21 0.0 vsan
1253 457 29220 15 0.0 ttyd
1254 138 6309 21 0.0 sysinfo
Using the show system resource CLI Command
Use the
show system resources
command to display system-related CPU and memory statistics. The
output includes the following:
•
Load is defined as number of running processes. The average reflects the system load over the past
1, 5, and 15 minutes.
•
Processes displays the number of processes in the system, and how many are actually running when
the command is issued.
•
CPU states shows the CPU usage percentage in user mode, kernel mode, and idle time in the last one
second.
•
Memory usage provides the total memory, used memory, free memory, memory used for buffers, and
memory used for cache in KB. Buffers and cache are also included in the used memory statistics.
Example B-6
show system resources Command
switch#
show system resources
Load average: 1 minute: 0.00 5 minutes: 0.00 15 minutes: 0.00
Processes : 152 total, 3 running
CPU states : 0.0% user, 0.0% kernel, 100.0% idle
Memory usage: 960080K total, 412900K used, 547180K free
2340K buffers, 292380K cache
Using On-Board Failure Logging
The Generation 2 Fibre Channel switching modules provide the facility to log failure data to persistent
storage, which can be retrieved and displayed for analysis. This on-board failure logging (OBFL) feature
stores failure and environmental information in nonvolatile memory on the module. The information will
help in post-mortem analysis of failed cards.