SwitchInfoUpdateFailure_Alert due to mismatched switch names
Applies to
- ONTAP 9
- Cluster Network switches
- Storage switches
- Ethernet switch health monitor (CSHM)
Issue
Alert may occur after any of the following activities such as applying a configuration file (RCF), rebooting the switch, or upgrading ONTAP
- System health monitor reports Alert SwitchInfoUpdateFailure_Alert for one of the cluster network switches
::*> system health alert show Node: Node1 Alert ID: SwitchInfoUpdateFailure_Alert Resource: Different.switch.name(Serial number) Severity: Major Indication Time: Wed Dec 24 12:59:36 2025 Suppress: false Acknowledge: false Probable Cause: Information from the Ethernet switch 'Different.switch.name(Serial number)' 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 "Different.switch.name(Serial number)" -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-discoveryEMS reports
- Notice the Switch name is reporting differently than the above Resource: field
Tue Dec 24 16:20:46 +0000 [Node1: cshmd: hm.alert.raised:alert]: Alert Id = SwitchInfoUpdateFailure_Alert , Alerting Resource =Different.switch.name(Same Serial number) raised by monitor ethernet-switch
- Another example of the switch name mismatch
Tue Dec 24 05:52:02 +0000 [Node1: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1011 and destination address 169.254.xxx.xxx might not be optimal for session 080638ef#######. The source is currently connected to Original.switch.name(Serial number) remote device and the destination is currently connected to Different.switch.name(Same Serial number) remote device.