NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.

Home
Advice and Troubleshooting
Data Storage Software
ONTAP OS
Cluster peering displays an incorrect name after a cluster was renamed

Cluster peering displays an incorrect name after a cluster was renamed

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

Views:: 648

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.