Table of Contents
Advertisement
Online System Health Management
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 .
The following example clears the error history for the specified Fibre Channel interface:
switch# system health clear-errors interface fc 3/1
The following example clears the error history for the specified module:
switch# system health clear-errors module 3
The following example clears the management port test error history for the specified module:
switch# system health clear-errors module 1 mgmt
Performing Internal Loopbacks
Internal loopback tests send and receive FC2 frames to/from the same ports and provides the round trip
time taken in microseconds. These tests are available for both Fibre Channel and iSCSI interfaces.
Use the EXEC-level system health internal-loopback command to explicitly run this test on demand
(when requested by the user) within ports for the entire module.
switch# system health internal-loopback interface iscsi 8/1
Internal loopback test on interface iscsi8/1 was
Round trip time taken is 79 useconds
If the test fails to complete successfully, the software analyzes the failure and prints the following error:
Note
External loopback test on interface fc 7/2 failed. Failure reason: Failed to loopback,
analysis complete Failed device ID 3 on module 1
Performing External Loopbacks
External loopback tests send and receive FC2 frames to/from the same port. You need to connect a cable
(or a plug) to loop the Rx port to the Tx port before running the test. This test is only available for Fibre
Channel interfaces.
Use the EXEC-level system health external-loopback command to run this test on demand for external
devices connected to a switch that is part of a long-haul network.
switch# system health external-loopback interface fc 3/1
This will shut the requested interfaces Do you want to continue (y/n)?
External loopback test on interface fc3/1 was
Use the system health external-loopback interface force command to shut down the required interface
directly without a back out confirmation.
switch# system health external-loopback interface fc 3/1 force
External loopback test on interface fc3/1 was
If the test fails to complete successfully, the software analyzes the failure and prints the following error:
Note
External loopback test on interface fc 7/2 failed. Failure reason: Failed to loopback,
analysis complete Failed device ID 3 on module 1
Cisco MDS 9000 Family Configuration Guide
50-14
Chapter 50
Monitoring System Processes and Logs
successful.
successful.
successful.
OL-6973-03, Cisco MDS SAN-OS Release 2.x
[n] y
Advertisement
Table of Contents
