Skip to main content
NetApp Knowledge Base

After upgrading, the switch name changed back to default ‘Cumulus'

Views:
46
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • 9.15.1P10
  • Upgrade from Cumulus Linux version 5.4.0 to Cumulus Linux version 5.11.0

Issue

We could see as per CSHM-SWITCH-CONFIG.XML, the CN switches are:

Device Name: ClusterSwitch01 (XX:1d:xx:0c:50:00)

Model to display: X190006-PE

Device Name: ClusterSwitch02 (XX:1d:xx:01:4e:7a)

Model to display: X190006-PE

After upgrading Cumulus Linux version 5.4.0 to Cumulus Linux version 5.11.0

The health alert shows the different switch name as cumulus

Alert ID: SwitchInfoUpdateFailure_Alert

Alerting Resource: cumulus (XX:1d:xx:01:4e:7a)

Subsystem: Switch-Health

Description: Information from the Ethernet switch 'cumulus (XX:1d:xx:01:4e:7a)' is no longer being updated. Other switch alerts might indicate possible causes for the issue.

Additional Information: Switch Name: cumulus (XX:1d:xx:01:4e:7a)

                                    Switch Model: X190006-PE

                                    Switch Information Resource Status: ok

Alert ID: SwitchInfoUpdateFailure_Alert

Alerting Resource: SwitchInfoUpdateFailure_Alert

Subsystem: Switch-Health

Description: Information from the Ethernet switch 'cumulus (XX:1d:xx:0c:50:00)' is no longer being updated. Other switch alerts might indicate possible causes for the issue.

Additional Information: Switch Name: cumulus (XX:1d:xx:0c:50:00)

                                   Switch Model: X190006-PE                     

                                   Switch Information Resource Status: ok

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.