Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just recently upgraded from 8.3.2 to 9.1P20 and started to see these alert messages being sent.
Message: cpeer.addr.warn.host: Address 172.31.x.x is not any of the addresses that peer cluster <vserver> considers valid for the cluster peer relationship; Details: An introductory RPC to the peer address "172.31.x.x" failed to connect: RPC: Remote system error - No route to host. Verify that the peer address is correct and try again.
Description: This message occurs when a stable IP address for the peer cluster is no longer valid, making the peer cluster unreachable and causing cross-cluster operations to fail.
I'm sure there was a change in the upgrade, however how do I narrow down what's causing this issue?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is the IP address valid and do you have a default route for the SVM set up so it can reach out to that IP address?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are two similar ones. I don't know which one applies
1. Check the output and see if 'Remote Intercluster Addresses' field contains DNS hostname of the remote peer LIFs. ONTAP repeatedly reports "logging cpeer.addr.warn.host" EMS messages - NetApp Knowledge Base
2.Cluster peer unavailable alerts cpeer.addr.warn.host:alert - NetApp Knowledge Base
