CISCO MDS Switch Port going into initializing status.

[msgunjetti]

Please advise in what scenario the port may get into initialization status .(Currently one of our Switch port down with initializing state).

Host is connected to MDS switch Port.

[xiazhen01]

hi, guys:

 it must be host HBA adapter issues.  please check HBA adapter etc.  

or you can try shutdown and no shutdown switch FC  port.

if also cannot solve it,  paste switch logs.

[santkumd528]

were you able to resolve it ? Was it an FC port or an IP port ?

[Walter Dey]

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	Possible Cause	Solution
Port remains in the initializing state.	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.	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 "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." section. 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.
	A software bug resulted in an error while handling the FLOGI packet.

---

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.

[santkumd528]

Walter :

Which document covers these troubleshooting details.

[Walter Dey]

http://www.cisco.com/en/US/products/ps5989/prod_troubleshooting_guide_chapter09186a008067a2bb.html#wp50777