Skip to main content
NetApp Knowledge Base

Nodes down during RCF Configuration Upgrade

Views:
43
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
hw
Last Updated:

Applies to

  • Nexus-3132 Cluster Switch
  • AFF-A300

Issue

  • Two nodes down while performing an RCF upgrade
  • Cluster ports flapping and degraded:

[NetApp-01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node NetApp-01, port e0b.
[NetApp-01: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node NetApp-01 has gone down unexpectedly.
[NetApp-01: intr: netif.linkUp:info]: Ethernet e0b: Link up.
[NetApp-01: vifmgr: vifmgr.portup:notice]: A link up event was received on node NetApp-01, port e0b.
[NetApp-01: vifmgr: vifmgr.reach.noreach:notice]: Network port e0b on node NetApp-01 cannot reach its expected broadcast domain Cluster:Cluster. No other broadcast domains appear to be reachable from this port.
[NetApp-01: intr: netif.linkDown:info]: Ethernet e0a: Link down, check cable.
[NetApp-01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node NetApp-01, port e0a.

  • Loss of cluster communication between nodes:

HA Group Notification (Health Monitor process cshm: ClusterSwitchConnectivity_Alert[Switch01]) ALERT
HA Group Notification (Health Monitor process cshm: ClusterIfIslDownWarn_Alert[Switch01(XXXXXXX)/Ethernet1/XX]) ALERT
HA Group Notification (CLUSTER NETWORK DEGRADED) ALERT
HA Group Notification (NODE(S) OUT OF CLUSTER QUORUM) EMERGENCY

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