Table of Contents
Advertisement
Chapter 11
Configuring Interfaces
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 .
Reason Codes
Reason codes are dependent on the operational state of the interface as described in
Table 11-3
Administrative
Configuration
Up
Down
Up
If the administrative state is up and the operational state is down, the reason code differs based on the
nonoperational reason code as described in
Table 11-4
Reason Code
Link failure or not connected
SFP not present
Initializing
Reconfigure fabric in progress The fabric is currently being reconfigured.
Offline
Inactive
Hardware failure
Error disabled
OL-6973-03, Cisco MDS SAN-OS Release 2.x
Reason Codes for Interface States
Operational
Status
Reason Code
Up
None.
Down
Administratively down—If you administratively configure an interface
as down, you disable the interface. No traffic is received or transmitted.
Down
See
Table
Reason Codes for Nonoperational States
Description
The physical layer link is not operational.
The small form-factor pluggable (SFP) hardware is not
plugged in.
The physical layer link is operational and the protocol
initialization is in progress.
The Cisco SAN-OS software waits for the specified
R_A_TOV time before retrying initialization.
The interface VSAN is deleted or is in a suspended
state.
To make the interface operational, assign that port to a
configured and active VSAN.
A hardware failure is detected.
Error conditions require administrative attention.
Interfaces may be error-disabled for various reasons.
For example:
Configuration failure.
•
Incompatible buffer-to-buffer credit configuration.
•
To make the interface operational, you must first fix the
error conditions causing this state; and next,
administratively shut down or enable the interface.
11-4.
Table
11-4.
Cisco MDS 9000 Family Configuration Guide
Fibre Channel Interfaces
Table
11-3.
Applicable
Modes
All
11-7
Advertisement
Table of Contents
