Unable to show all results as the remote cluster is not reachable during metrocluster check
Applies to
- ONTAP 9
- MetroCluster
Issue
- MetroCluster check command reports warnings for some parameters and an error that remote cluster is not reachable:
Cluster_A::> MetroCluster check show
Last Checked On: 12/17/2024 10:47:00
Component Result
------------------- ---------
nodes warning
lifs ok
config-replication warning
aggregates ok
clusters warning
connections not-applicable
volumes ok
Error: show failed: Unable to show all results as the remote cluster is not reachable.
7 entries were displayed.
- The metrocluster check node reports the following internal error as the DR partner node is unreachable:
Cluster_A::> metrocluster check node show -instance -result !ok
Node Name: Cluster_B-01
Type of Check: symmetric-dr-auxiliary-relationship
Cluster Name: Cluster_B
Result of the Check: not-run
Additional Information/Recovery Steps: An internal error occurred while running "metrocluster check". Contact technical support for assistance. Error details: Failed to check if the node's DR relationship is symmetric. Details: Internal error occurred on node "ef91d23b-1234-56ab-78cd-00aXXXXXXXX" in cluster "Cluster_A". Details: (Failed to contact peer cluster "Cluster_B" at addresses: 10.10.10.11, 10.10.10.12. RPC: Remote system error [from mgwd on node "Cluster_A-01" (VSID: -1) to mgwd at 10.10.10.11, 10.10.10.12]).
-
The config-replication section reports the below warnings:
Cluster_A::> metrocluster check config-replication show -instance
Enabled: true
Running: true
Recovery Steps: -
Remote Heartbeat: warning
Last Heartbeat Sent: 12/17/2024 10:03:26
Last Heartbeat Received: 12/17/2024 10:48:25
Recovery Steps: Verify the partner cluster is "Available" using the "cluster peer show" command. To view additional diagnostic information, run "metrocluster check config-replication show" on the partner cluster.
Vserver Streams: warning
Recovery Steps: Run the "metrocluster vserver show" command for more details.
Cluster Streams: warning
Recovery Steps: The remote operational state of stream 12d19641-103e-421a-9091-342c52c87910 is unknown. Follow the recovery steps associated with the "Remote Heartbeat" field.
-
The status of all the SVMs is unhealthy, as the partner cluster is not reachable:
Cluster Name: Cluster_B
Vserver: svm_B_1
Partner Vserver: svm_B_1-mc
Configuration State: unhealthy
Corrective Action: Verify the partner cluster is "Available" using the "cluster peer show" command. To view additional diagnostic information, run "metrocluster check config-replication show" on the partner cluster.
Creation Time on the source: 9/16/2024 10:47:14
Is out of sync: false
configuration Resume Time: -
-
The MGWD logs report the following errors:
ERR: metrocluster::cli: Network error for remote xc call mccCheckLifResults error:Failed to contact peer cluster "Cluster_B" at addresses: 10.10.10.11, 10.10.10.12. RPC: Remote system error [from mgwd on node "Cluster_A" (VSID: -3) to mgwd at 10.10.10.11, 10.10.10.12] {in next_imp() at src/tables/metrocluster.cc:12507}
ERR: metrocluster::cli: isRemoteClusterAvailable():True, xcLifItr.error:Failed to contact peer cluster "Cluster_B" at addresses: 10.10.10.11, 10.10.10.12. RPC: Remote system error [from mgwd on node "Cluster_A" (VSID: -3) to mgwd at 10.10.10.11, 10.10.10.12] isNetworkError:True {in next_imp() at src/tables/metrocluster.cc:12524}
