Skip to main content
NetApp Knowledge Base

ClusterSwitchlessConfig_Alert with BES-53248 cluster switch

Views:
6
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
CORE
Last Updated:
3/17/2025, 1:58:07 AM

Applies to

  • ONTAP 9
  • BES-53248

Issue

  • ONTAP system alert/health alert with below content:
Problem Summary:
 Node: nodename
 Alert ID: ClusterSwitchlessConfig_Alert
 Resource: clustername
 Severity: Major
 Indication Time: Sat Dec 14 20:15:25 2024
 Suppress: false
 Acknowledge: false
 Probable Cause: No cluster switch is detected and the switchless option is not enabled.
 Possible Effect: Communication problems and cluster connectivity issues occur.
 Corrective Actions:
                     1) If the cluster network is configured as a two-node switchless cluster (TNSC), enable switchless detection by using the "network options detect-switchless-cluster modify -enabled true" command.
                     No further action is required.
                     2) If the cluster network is configured with cluster switches, the nodes fail to detect the switches.
                     Ensure that the network interfaces on the cluster switches connected to the node cluster ports are enabled on both sides.
     If the errors are corrected, stop. No further action is required. Otherwise, continue to step 3.
                     3) Check the physical connections between the nodes and the cluster switches. Replace network cables with known-good cables.
      If the errors are corrected, stop. No further action is required. Otherwise, continue to step 4.
                     4) Ensure that either CDP (for Cisco switches) or ISDP(for NetApp CN1610 and Broadcom BES-53248 switches) is enabled on the cluster switches.
  • EMS event log has many vifmgr.cluscheck.ctdpktloss  error entries:

Mon Dec 16 00:53:32 +0800 [<nodename>: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif <nodename>_clus1 (node <nodename>) to cluster lif <nodename>_clus2 (node <nodename>).

 

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.