NCP-MCI v6.5 Exam QuestionsBrowse all questions from this exam
Go to Exam

NCP-MCI v6.5 Exam - Question 66

Refer to the exhibit.

An administrator is adding a new node to a cluster. The node has been imaged ta the same versions of AHV and AOS that the cluster is running, configured with appropriate IP addresses, and br0-up has been configured in the same manner as the existing uplink bonds.

When attempting to add the node to the cluster with the Expand Cluster function in Prism, the cluster is unable to find the new node.

Based on the above output from the new node, what is most likely the cause of this issue?

Show Answer
Correct Answer: A

The most likely cause of the issue is that the existing cluster and the expansion node are on different VLANs. When adding a new node to a cluster, it is crucial that all nodes are on the same VLAN in order to communicate properly. If they are on different VLANs, the cluster cannot discover the new node. The provided exhibit shows correctly configured LACP settings, so the upstream switch ports are likely not the problem.

Discussion

5 comments
Sign in to comment
Blitz1Option: A
May 25, 2024

A is the correct answer because: B - bond is up and lacp is active as per image so LACP was configure on the switch C - is total non-sense D - might be BUT hard to believe there is a firewall on the same subnet... A- remain the only one which makes sense because the fallowing must be true when you add new host: "Add host or CVM IPs to discover hosts within the same network." Those can be in the same network but if there on diff vlan it will not work

Blitz1
May 27, 2024

I believe i was wrong with this done. A is still valid but also B and because there is a picture related to B maybe the correct answer should be B. From my point of view this question might be incomplete. Br0-up is the name of the bond and not the status of the bond.(like interface up ... or like you configure in a switch a port-channel and if it's not up there is a issue with it) To check the status of the bond we should use " ovs-appctl bond/show br0-up " and if lacp_status: negotiated is present than we have a succesful lacp conf in both party. https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0320000004H0vCAE

DEEGEE1977Option: C
Oct 5, 2024

LACP status should = negotiated not active if LACP was functioning

jay9114Option: B
Oct 13, 2024

Nutanix relies on smooth network communication to discover and add new nodes. If the network bonding isn’t working due to the LACP mismatch, the node won’t be able to communicate with the cluster, making it impossible for Prism to discover the node.

vuhidusOption: B
Oct 17, 2024

I think it's B

JordansGhostOption: B
Feb 7, 2025

Its B. There is no VLAN info in the output so A has to be ruled out. D possible if an ACL was on the switch or it was a different switch to the other hosts but there is insufficient info to confirm this. the simple answer which is most likely the cause is the upstream switch needs to be configured correctly.