We are redesigning the NetApp Knowledge Base site to make it easier to use and navigate. The new and improved site will be available the first week of October. Check out our video or read this KB article to know more about changes you’ll see on the site.

Cluster peering displays an incorrect name after a cluster was renamed

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 446

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: core

Last Updated:

Applies to

ONTAP 9
Cluster Peering
Commvault
Active IQ Unified Manager (AIQUM) 9.X

Issue

When intercluster peering is already setup and one of the peered clusters is renamed there will be mismatch in naming on the peering destination(s), which can also cause problems with the ComVault backups.

For example error in AIQUM post source cluster name change of an existing peer , AIQUM will show error "resource-key not discovered" for Source SVM and Source volume. Commvault Aux copy jobs will fail due to this.

******************************************************* *******************************************************