Clearing Previous Error Reports; Performing Internal Loopback Tests - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual
Cisco mds 9000 family cli configuration guide - release 4.x (ol-18084-01, february 2009)
Hide thumbs
Also See for AP776A - Nexus Converged Network Switch 5020:
- Command reference manual (1640 pages) ,
- Configuration manual (1486 pages) ,
- Reference (886 pages)
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
Clearing Previous Error Reports
You can clear the error history for Fibre Channel interfaces, iSCSI interfaces, an entire module, or one
particular test for an entire module. By clearing the history, you are directing the software to retest all
failed components that were previously excluded from tests.
If you previously enabled the failure-action option for a period of time (for example, one week) to
prevent OHMS from taking any action when a failure is encountered and after that week you are now
ready to start receiving these errors again, then you must clear the system health error status for each test.
The management port test cannot be run on a standby supervisor module.
Tip
Use the EXEC-level system health clear-errors command at the interface or module level to erase any
previous error conditions logged by the system health application. The bootflash, the eobc, the inband,
the loopback, and the mgmt test options can be individually specified for a given module.
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 test error history for the specified module:
switch# system health clear-errors module 1 mgmt
Performing Internal Loopback Tests
You can run manual loopback tests to identify hardware errors in the data path in the switching or
services modules, and the control path in the supervisor modules. Internal loopback tests send and
receive FC2 frames to/from the same ports and provide the round trip time taken in microseconds. These
tests are available for Fibre Channel, IPS, 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
Sent 1 received 1 frames
Round trip time taken is 79 useconds
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 and override the frame count configured
on the switch.
switch# system health internal-loopback interface iscsi 8/1 frame-count 20
Internal loopback test on interface iscsi8/1 was
Sent 1 received 1 frames
Round trip time taken is 79 useconds
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 and override the frame length configured
on the switch.
switch# system health internal-loopback interface iscsi 8/1 frame-count 32
Cisco MDS 9000 Family CLI Configuration Guide
59-14
Chapter 59
Monitoring System Processes and Logs
successful.
successful.
OL-18084-01, Cisco MDS NX-OS Release 4.x
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
