Cluster peering displays an incorrect name after a cluster was renamed
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.