Skip to main content

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

INSIGHT Japan :2023年 1月25日(水)ANAインターコンチネンタルホテル開催 へ参加・申込を行う

NetApp Knowledge Base

BES-53248 switch info not displayed under device-discovery

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

Applies to

  • BES-53248 network switches with EFOS 3.7.0.4
  • ONTAP 9.8P12, 9.9.1P10, 9.10P6
  • MetroCluster IP (MCCIP)

Issue

  • After EFOS upgrade to 3.7.0.4 on both BES-53248 switches, one controller in the MCCIP no longer displays cluster network switches in device-discovery show
  • Switch logs confirm that storage side ports are properly displayed under show isdp neighbors
    *************** show isdp neighbors ***************
    
    
    Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge,
                      S - Switch, H - Host, I - IGMP, r - Repeater
    
    Device ID                Intf      Holdtime  Capability Platform         Port ID
    ------------------------ --------- --------- ---------- ---------------- ---------
    Node-01                  0/9       150       H          AFF-A220         e0b
    Node-02                  0/10      149       H          AFF-A220         e0b
    Switch-01                0/55      177       R S        BES-53248        0/55
    Switch-01                0/56      177       R S        BES-53248        0/56
    
  • Increasing checksum errors are observed under cdpd show-stats
    Cluster::*> run -node Node-01 cdpd show-stats
    RECEIVE
     Packets:           611k | Csum Errors:       366k | Unsupported Vers:    0 
     Invalid length:      0  | Malformed:           0  | Mem alloc fails:     0 
     Missing TLVs:        0  | Cache overflow:      0  | Received Own Adv:    0 
     Other errors:        0  | Unknown TLV:         0  | Ejected entries:     0 
     Eject failed:        0  | Bad Value:           0 
    
    
    TRANSMIT 
     Packets:         76375  | Xmit fails:          0  | No hostname:         0 
     Packet truncated:    0  | Truncate fails:      0  | Mem alloc fails:     0 
     Other errors:        0 
  • Affected controller intermittently reports warnings such as the below for the switches
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1023 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-01 remote device.
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1024 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-02 remote device.
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1023 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-01 remote device.
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1024 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-02 remote device.
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1023 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-01 remote device.
    Thu Aug 25 13:29:06 +0200 [Node-01: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1024 and destination address xxx.xxx.xxx.xxx might not be optimal for session xxxxxxxxxxxxxxxx. The source is currently connected to - remote device and the destination is currently connected to Switch-02 remote device.
  • Collected packet-traces from the switches confirm that Cisco Discovery Protocol (CDP) packets are being forwarded to the storage correctly
  • Migrating the cluster LIF between nodes and then disabling and re-enabling the ports makes no difference
  • Performing a takeover and giveback between nodes doesn't help
  • Updating ONTAP to version 9.9.1P10 or 9.10P6 leads to no change
  • Physical inspection of the storage and switches confirms all ports and cables are working correctly

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

 

  • Was this article helpful?