Skip to main content
NetApp Knowledge Base

SwitchInfoUpdateFailure_Alert after Motherboard Replacement in MetroCluster IP Fabric

Views:
5
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

Applies to

  • ONTAP 9
  • MCC IP
  • ClusterSwitchHealthMonitor (CSHM)

Issue

  • After replacing the motherboard (MB) and DIMM in slot 2 on Node1 of a MetroCluster IP configuration, the following persistent alert appears in ONTAP:

cluster::*> system health subsystem alert show
               Node: cluster-02
           Alert ID: SwitchInfoUpdateFailure_Alert
           Resource: IP_switch_A_1
     Probable Cause: Information from the Ethernet switch 'IP_switch_A_1'
                     is no longer being updated. Other switch alerts might
                     indicate possible causes for the issue.
    Possible Effect: When switch information is not being updated,
                     monitoring of the switch's performance and health has
                     stopped, potentially leading to unnoticed issues,
                     service disruptions, and loss of communication.
                     Furthermore, the log collection configuration will be
                     deleted after 7 days.
 Corrective Actions: 1) Review current switch alerts for the affected switch.
                     2) Examine the monitoring status of the switch using the 'system switch ethernet show' command. If the switch is listed in the output, resolve the issue listed in the reason field, then attempt to restart the monitoring process using the 'system switch ethernet modify -device "IP_switch_A_1" -is-monitoring-enabled-admin true' command.
                     3) If the switch is not listed under the 'system switch ethernet show' command, investigate the cause of its absence. This could be due to the switch being disconnected, or because link discovery information via CDP or LLDP is not being received by ONTAP.
                     If the switch was not disconnected, start by confirming it is listed in the output of 'network device-discovery show'.
                     If the Ethernet switch is not listed, check that the
                     appropriate link discovery protocol is enabled.

  • Switch health is degraded

cluster::*> system health alert subsystem show
Subsystem         Health
----------------- ------------------
SAS-connect       ok
Environment       ok
Memory            ok
Service-Processor ok
Switch-Health     degraded
CIFS-NDO          ok
Motherboard       ok
IO                ok
MetroCluster      ok
MetroCluster_Node ok
FHM-Switch        ok
FHM-Bridge        ok
SAS-connect_Cluster ok
13 entries were displayed.

  • Switch is not been monitored with IP address not reachable

cluster::*> system switch ethernet show
Switch                      Type               Address          Model
--------------------------- ------------------ ---------------- ---------------
IP_switch_A_1               cluster-network    10.128.XX.XXX    BES-53248
     Serial Number: QTFCUXXXXX
      Is Monitored: false
            Reason: IP address not reachable
  Software Version: 3.7.0.4
    Version Source: CDP/ISDP

IP_switch_A_2               cluster-network    10.128.XX.XXX    BES-53248
     Serial Number: unknown
      Is Monitored: false
            Reason: IP address not reachable
  Software Version: 3.7.0.4
    Version Source: CDP/ISDP

  • Ping from cluster to switch doesn't work

cluster::*> network ping -lif BFLNTAPCLA-01_mgmt1 -vserver test-vserver -destination 10.128.XX.XXX
no answer from 10.128.XX.XXX

  • Telnet results no connection to host

cluster-01% telnet 10.128.XX.XXX 443
Trying 10.128.XX.XXX...
telnet: connect to address 10.128.XX.XXX: Connection refused
telnet: Unable to connect to remote host

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

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.