Skip to main content
NetApp Knowledge Base

cpeer.addr.warn.host due to Stale RemoteInterclusterAddresses in MetroCluster

  1. Last updated
  2. Save as PDF
Views:
8
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster

Issue

Cluster event logs repeatedly report the following EMS alert:
[mgwd:cpeer.addr.warn.host:alert]: Address [xxx.xxx.xxx.xxx] is not any of the addresses that peer cluster [A400B] considers valid for the cluster peer relationship; Details: An introductory RPC to the peer address "[xxx.xxx.xxx.xxx]" failed to connect: RPC: Remote system error [from mgwd on node "A400A-01" (VSID:-3) to xcintro at xxx.xxx.xxx.xxx]. Verify that the peer address is correct, and then try the operation again.
  • The cluster peer relationship remains available and healthy.
  • The alert is persistent after intercluster LIF IPs were changed.
  • cluster peer show-instance displays old RemoteInterclusterAddresses (e.g., 192.168.93.145/146) instead of the new ones (e.g., 172.16.16.215/216/217/218).

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.