Skip to main content
NetApp Knowledge Base

Constant csm.mismatchRemoteDevice errors pointing to a single node

Views:
22
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP
  • Switched Cluster

Issue

  • Cluster lifs on other nodes in the cluster are calling to cluster lifs owned by a specific node in the cluster
 
 [?]  Fri Dec 20 22:25:55 -0500 [Cluster1-02: util_connmgr_0: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 879 and destination address 169.254.xx.201 might not be optimal for session 0f0629bf52367d97. The source is currently connected to ClSw1(xxxxxxxxx) remote device and the destination is currently connected to - remote device.
 [?]  Fri Dec 20 22:25:55 -0500 [Cluster1-02: util_connmgr_0: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 880 and destination address 169.254.xx.12 might not be optimal for session 0f0629bf52367d97. The source is currently connected to ClSw2(xxxxxxxxx) remote device and the destination is currently connected to - remote device.
 
 [?]  Thu Dec 19 19:00:25 -0500 [Cluster1-03: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 901 and destination address 169.254.xx.201 might not be optimal for session 10062325388b33ae. The source is currently connected to ClSw1(xxxxxxxxx) remote device and the destination is currently connected to - remote device.
 [?]  Thu Dec 19 19:00:25 -0500 [Cluster1-03: client_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 901 and destination address 169.254.xx.12 might not be optimal for session 0f062325388b33ae. The source is currently connected to ClSw2(xxxxxxxxx) remote device and the destination is currently connected to - remote device
  • The node who's being called out from the above messages is pointing to all other nodes in the cluster
 [?]  Thu Dec 19 20:27:21 -0500 [Cluster1-01: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 924 and destination address 169.254.xx.168 might not be optimal for session 10062326cd441a9d. The source is currently connected to - remote device and the destination is currently connected to ClSw2(xxxxxxxxx) remote device.
 [?]  Thu Dec 19 20:27:21 -0500 [Cluster1-01: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 924 and destination address 169.254.xx.242 might not be optimal for session 00062702a1d1cba1. The source is currently connected to - remote device and the destination is currently connected to ClSw2(xxxxxxxxx) remote device.
 [?]  Thu Dec 19 20:27:21 -0500 [Cluster1-01: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 924 and destination address 169.254.xx.150 might not be optimal for session 0f062326d884dfa1. The source is currently connected to - remote device and the destination is currently connected to ClSw2(xxxxxxxxx) remote device.
 [?]  Thu Dec 19 20:27:21 -0500 [Cluster1-01: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 924 and destination address 169.254.xx.175 might not be optimal for session 0b062326cd2d33a1. The source is currently connected to - remote device and the destination is currently connected to ClSw2(xxxxxxxxx) remote device.

 

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.