Send documentation comments to mdsfeedback-doc@cisco.com
8-13
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 8 Troubleshooting Ports
Common Problems with Port Interfaces
NPI2# sh flogi
INTERFACE VSAN FCID PORT NAME NODE NAME
-------------------- ---- -------- ----------------------- -----------------------
fc1/5 1 0x9f0100 50:06:04:82:c3:a0:98:5c 50:06:04:82:c3:a0:98:5c
fc1/9 1 0x9f0020 21:00:00:e0:8b:08:dd:22 20:00:00:e0:8b:08:dd:22
fc1/12 1 0x9f0040 50:06:04:82:c3:a0:98:52 50:06:04:82:c3:a0:98:52
fc1/13 1 0x9f0300 21:00:00:e0:8b:08:a2:21 20:00:00:e0:8b:08:a2:21
fc8/6 1 0x9f0101 20:00:00:e0:69:40:8d:63 10:00:00:e0:69:41:a0:12
fc8/14 1 0x9f0003 50:06:04:82:c3:a0:98:4c 50:06:04:82:c3:a0:98:4c
Step 5 If you do not see the ports in the show flogi output, use the debug flogi even interface command to
isolate the FLOGI issue.
NPI1# debug flogi event interface fc2/5
Step 6 If the ports are in the show flogi output, use the show fcns database command to verify that the assigned
FC ID during FLOGI exists in the name server database.
NPI2# show fcns database
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x9f0100 N 50:06:04:82:c3:a0:98:5c (EMC) scsi-fcp:target 250
0x7e0200 N 21:00:00:e0:8b:08:d3:20 (QLogic) scsi-fcp:init
At this point the HBA and subsystem ports have successfully established link level connectivity and each
one can communicate with its locally attached switch in the fabric. The next step is to verify zone
membership. For a more detailed discussion and description of vsans and zones see Chapter 14,
“Troubleshooting Zones and Zone Sets.”
Common Problems with Port Interfaces
The following issues are commonly seen with port interfaces:
• Port Remains in a Link Failure or Not Connected State, page 8-13
• Port Remains in Initializing State, page 8-16
• Unexpected Link Flapping Occurs, page 8-21
• Port Bounces Between Initializing and Offline States, page 8-26
• E Port Bounces Remains Isolated After a Zone Merge, page 8-28
• Port Cycles Through Up and Down States, page 8-31
• Port Is in ErrDisabled State, page 8-31
• Troubleshooting Fx Port Failure, page 8-32
Port Remains in a Link Failure or Not Connected State
If a link does not come up, then the switch was unable to achieve bit or word synchronization with the
node device. This situation may occur if nothing is connected to the interface, as in the case of a broken
fibre, or if there is no bit synchronization between the switch interface and the directly connected Nx
port. This problem may be the result of one or more of the possible causes listed in Table 8-3.
To Next Page
Loading...
Need help?
General