Skip to main content
NetApp Knowledgebase

MetroCluster EMS show "cpeer.addr.stable.down:error" and "CSM failed to create a connection" messages

Views:
94
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

MetroCluster

Issue

  • EMS messages include:
[NetApp: mgwd: cpeer.addr.stable.down:error]: Stable address <IC LIF of peered cluster> of cluster <peered cluster name>, in IPspace Default, cannot be contacted.
 
 [NetApp: kernel: csm.connectionFailed:debug]: CSM failed to create a connection: localBladeUUID = <node_name>:dblade, remoteBladeUUID = <node_name>:dblade, uniquifier = xxxxxxxxxxxxxxx, localVifId = 1035, remoteVifIP = x.x.x.x, CsmError = CSM_CONNTIMEOUT, ctLoError = CTLOPCP_ERR_CONNTIMEDOUT, socketError = 60.
 
[NetApp: mgwd: mgmtgwd.jobmgr.private.jobcomplete.failure:info]: Private job "Cross-Cluster Manager" [id 694] (Cross-Cluster Address Manager) completed unsuccessfully: discovery failure (1)
 
[NetApp: mgwd: cpeer.xcm.addr.disc.warn:error]: Address discovery failed for peer cluster <cluster_UUID>. Reason: Failed to discover remote addresses: Failed to contact peer cluster "<cluster_name>" at addresses: x.x.x.x, x.x.x.x, x.x.x.x. RPC: Remote system error [from mgwd on node "<node_name>" (VSID: -3) to mgwd at x.x.x.x, x.x.x.x, x.x.x.x].
 
  • The output of command "cluster peer ping" show some ip address is unreachable.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support