Skip to main content
NetApp Knowledge Base

EMS log occasionally reports a 'cpeer.addr.stable.down' error

  1. Last updated
  2. Save as PDF
Views:
1,593
Visibility:
Public
Votes:
3
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP Select 9
  • SnapMirror

Issue

  • EMS log reports cpeer.addr.stable.down:error

[<NODE>: mgwd: cpeer.addr.stable.down:error]: Stable address <IP> of cluster <CLUSTER>, in IPspace Default, cannot be contacted.

Note: The following EMS events may also be triggered.

  • cpeer.pm.update.warn:error
  • mgmtgwd.jobmgr.jobcomplete.failure:info
  • peer.pm.update.warn:error
  • cpeer.xcm.addr.disc.warn:error
  • cpeer.unavailable:alert
  • cpeer.xcm.addr.disc.warn:error
  • mgmtgwd.jobmgr.private.jobcomplete.failure:info
  • MGWD log shows markFailure for the same address and clearFailure immediately

NOTICE: RpcConnectionCache: markFailure: markFailure: New Quarantine for <IP>:536873488(mgwd)/3[tcp]{ffffffff|40} with timeout(10.000s) Reason:: RPC: Remote system error - Invalid argument
NOTICE: RpcConnectionCache: clearFailure: called for <IP>:536873488(mgwd)/3[tcp]{ffffffff|40}

 

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.