Skip to main content
NetApp Knowledge Base

FC-AL LINK_FAILURE reported by stretch MetroCluster nodes

Views:
187
Visibility:
Public
Votes:
1
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • Stretch MetroCluster
  • ONTAP 9
  • FAS8200
  • X1133A FC Adapter in slot 1
  • ATTO FB7500N/7600N

Issue

  • An autosupport is triggered from one (or both) of the nodes titled FC-AL LINK_FAILURE
  • The FC port that reports the error is in a <DOWN> state
Example:
	slot 1: FC Host Adapter 1a (Emulex XE201 rev. 48, <DOWN>)
		Board name:        111-02455
		Serial Number:     ABCDEFGHIJ
		Firmware rev:      12.0.378.1
		Host Port Id:      N/A
		FC Node Name:      2:000:000000:000000
		FC Port Name:      1:000:000000:000000
		Link Data Rate:    N/A
  • There is a significant number of errors reported by the ATTO bridge
Example:

get FCPortErrors all

; Fibre Channel Error Counts 
; Port | Link Failures | Sync Loss | Signal Loss | Invalid Tx | Invalid CRC
;==========================================================================
   1           1051711     1795435         80860     14901579             0
   2           1052319     1792284         79121     22508820             0

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device