Cisco Nexus 5000 Series Switch CLI Software Configuration Guide, NX-OS 4.0(1a)N1 (OL-16597-01, January 2009)

Send feedback to [e-mail]
32-6
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 32 Configuring Fibre Channel Interfaces
Information About Fibre Channel Interfaces
Note Only some of the reason codes are listed in Table 32-4.
If the administrative state is up and the operational state is down, the reason code differs based on the
nonoperational reason code. Table 32-4 describes the reason codes for nonoperational states.
Table 32-4 Reason Codes for Nonoperational States
Reason Code (long version) Description
Applicable
Modes
Link failure or not connected The physical layer link is not operational. All
SFP not present The small form-factor pluggable (SFP) hardware is not
plugged in.
Initializing The physical layer link is operational and the protocol
initialization is in progress.
All
Reconfigure fabric in progress The fabric is currently being reconfigured.
Offline The switch software waits for the specified R_A_TOV
time before retrying initialization.
Inactive 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.
Hardware failure A hardware failure is detected.
Error disabled 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 then
administratively shut down or enable the interface.
Isolation because limit of
active port channels is
exceeded.
The interface is isolated because the switch is already
configured with the maximum number of active SAN
port channels.