![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1532519.1 : Brocade M-Series (McData) Switches with "Failed" Port status
In this Document
Applies to:McData Sphereon 4500 Fabric Switch - Version Not Applicable to Not Applicable [Release N/A]McData Sphereon 4700 Fabric Switch - Version Not Applicable to Not Applicable [Release N/A] Brocade M4700 Switch - Version Not Applicable to Not Applicable [Release N/A] McData Intrepid 6140 Director - Version Not Applicable to Not Applicable [Release N/A] McData Intrepid 6064 Director - Version Not Applicable to Not Applicable [Release N/A] Information in this document applies to any platform. SymptomsTo discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk/Tape Storage Area Networks
Switch port data shows one or more ports in a "Failed" status. This could be from switch CLI, the EFCM Basic BUI, or a host application like EFCM or DCFM (or their associated data collection logs). Example (taken from EFCM Data Collection logs): Port Data <SNIP> NOTE: On the 4x00 series switches, you may also see the switch a CTP FRU status of "Failed" as well, which may lead to unnecessary concern. Example (taken from the same EFCM Data Collection logs): FRU List
ChangesNone CauseThe described condition is caused by a faulted SFP. SolutionReplace the affected SFP(s). Once the new SFP is in place, the port condition should return to "Online" status (assuming something is attached to it). Replacing the SFP will also clear the misleading "Failed" CTP status on the 4x00 series. If a "Failed" CTP is seen in a 6064 or 6140, that should be addressed separately. Attachments This solution has no attachment |
||||||||||||||||||
|