NCP-MCI-6.10 · Question #124
An administrator is trying to troubleshoot the environment after NCC raised an alert: Which two steps should an administrator follow to provide a solution? (Choose two.)
The correct answer is A. Confirm that the remote cluster is reachable, and ports 2009 and 2020 are open between the D. Check if ping packets with an MTU of 9000 reach the destination cluster. The NCC alert in this context is related to inter-cluster connectivity, likely for replication or Metro Availability. Confirming that the remote cluster is reachable and that ports 2009 and 2020 are open (A) is a foundational troubleshooting step - these ports are required for…
Question
An administrator is trying to troubleshoot the environment after NCC raised an alert:
Which two steps should an administrator follow to provide a solution? (Choose two.)
Options
- AConfirm that the remote cluster is reachable, and ports 2009 and 2020 are open between the
- BConfigure Network Address Translation performed by any device in between the two Nutanix
- CIf the remote site has been re-configured and the cluster has a new cluster incarnation ID, re-
- DCheck if ping packets with an MTU of 9000 reach the destination cluster.
How the community answered
(14 responses)- A71% (10)
- B21% (3)
- C7% (1)
Explanation
The NCC alert in this context is related to inter-cluster connectivity, likely for replication or Metro Availability. Confirming that the remote cluster is reachable and that ports 2009 and 2020 are open (A) is a foundational troubleshooting step - these ports are required for Nutanix cluster communication and replication traffic, and firewalls commonly block them. Checking if ping packets with an MTU of 9000 reach the destination cluster (D) verifies that jumbo frames are supported end-to-end across the network path, which is required for Nutanix replication performance; an MTU mismatch causes silent packet drops. Configuring NAT between clusters (B) is not recommended and not a solution - Nutanix replication requires direct IP reachability. Re-registering the remote site due to a changed cluster incarnation ID (C) is a valid fix in that specific scenario, but it is not a general first troubleshooting step and is more situational than A or D.
Topics
Community Discussion
No community discussion yet for this question.