Cisco MDS-9124 Troubleshooting Guide - Page 188
Port Remains in Initializing State, show hardware internal fc-mac port, statistics, attach module
View all Cisco MDS-9124 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 188 highlights
Common Problems with Port Interfaces Chapter 8 Troubleshooting Ports Send documentation comments to [email protected] Port Remains in Initializing State Symptom Port remains in the initializing state. A port goes into the initialization state after a successful completion of link level initialization. For Fx and FL types of ports, the next step is to complete the FLOGI process. The port remains in the initialization state until the FLOGI (fabric login) process completes. For E or TE port types, the next step is to complete the ELP process. If the ELP fails the port is moved to the offline state after a timeout and the entire process repeats until the port comes online. Table 8-4 lists possible causes for FLOGI to fail for a given port and possible solutions. Table 8-4 Port Remains in the Initializing State Symptom Port remains in the initializing state. Possible Cause Solution The port is up because the link partner has put itself in a bypass mode. Use the show hardware internal fc-mac port port statistics command to check whether the Class-3 input counter is increasing after the successful completion of link initialization. Note You must use the attach module CLI command to access the FC-MAC show commands. The FLOGI packet was dropped somewhere in the data path, starting from FC-MAC to the FLOGI server. A software bug resulted in an error while handling the FLOGI packet. Use the show hardware internal fc-mac port port statistics command to check for Class-3 packet counters. Note You must use the attach module CLI command to access the FC-MAC show commands Analyze the output of the show hardware internal error command for a possible drop of FLOGI packets somewhere in the path. See the "NoteWe recommend that you do not disable and then enable a T or TE port. This would affect all the VSANs crossing the EISL instead of just the VSAN experiencing the problem." section on page 8-16. Right-click on the port in Device Manager and select disable and then enable, or use the shut CLI command followed by the no shut command to disable and enable the port. If this does not clear the problem, try moving the connection to a different port on the same or another module. Note We recommend that you do not disable and then enable a T or TE port. This would affect all the VSANs crossing the EISL instead of just the VSAN experiencing the problem. 8-16 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05