Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix Exam NCP-MCI Topic 2 Question 14 Discussion

Actual exam question for Nutanix's NCP-MCI exam
Question #: 14
Topic #: 2
[All NCP-MCI Questions]

Refer to the Exhibit:

An administrator is adding a new node to a cluster. The node has been imaged to 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 Suggested Answer Hide Answer
Suggested Answer: B

The output in the exhibit indicates that the node's network interfaces (eth0-eth3) are bonded together using LACP (Link Aggregation Control Protocol) with 'balance-tcp' as the bonding mode and LACP speed set to 'fast'. For LACP to function correctly, the switch ports to which the node is connected must also be configured to support LACP. If the ports on the upstream switch are not configured for LACP, the bond will not be able to establish properly, and the node will not communicate effectively on the network, making it undiscoverable when attempting to expand the cluster.

The absence of an operational LACP configuration could prevent the new node from joining the existing cluster as the node's network interfaces would not be able to pass traffic correctly. This can be verified by checking the switch configuration to ensure that the ports are set to participate in an LACP bond.

The other options, such as a firewall blocking discovery traffic (Option A) or the node being on different VLANs (Option C), are possible causes for a node not being discovered, but given the specific command output provided, the most likely cause is related to the switch port configuration for LACP. Option D, regarding completing LACP configuration after cluster expansion, is not correct because LACP needs to be operational for the node to communicate with the cluster during the expansion process.

Proper LACP configuration is critical for network communication in a Nutanix AHV cluster, and this is covered in detail in the Nutanix AHV and Networking documentation. It outlines the steps for configuring network bonds and LACP on both the AHV hosts and the connecting network infrastructure.


Contribute your Thoughts:

Alaine
4 months ago
Haha, 'LACP configuration must be completed after cluster expansion'? That sounds like a classic IT joke. But seriously, option D doesn't seem right.
upvoted 0 times
Fletcher
3 months ago
Cordelia: True, those could be causing the problem.
upvoted 0 times
...
Gwenn
3 months ago
Could be, or maybe the VLANs are different between the cluster and the new node.
upvoted 0 times
...
Cordelia
3 months ago
Maybe the issue is with the firewall blocking the discovery traffic?
upvoted 0 times
...
Jose
4 months ago
Yeah, option D does sound like a joke.
upvoted 0 times
...
...
Lawanda
4 months ago
I think we should check if the existing cluster and the expansion node are on different VLANs as well.
upvoted 0 times
...
Wayne
5 months ago
I believe the ports on the upstream switch not being configured for LACP could also be a reason.
upvoted 0 times
...
Ashley
5 months ago
I agree with Amie, it's possible that the firewall is causing the problem.
upvoted 0 times
...
Carolynn
5 months ago
Hmm, the new node and the existing cluster being on different VLANs sounds plausible. I'll go with option C.
upvoted 0 times
...
Chaya
5 months ago
You know, if the firewall is the issue, I bet the admin forgot to turn it off. Classic rookie mistake!
upvoted 0 times
Bonita
4 months ago
Yeah, the admin probably forgot to turn it off.
upvoted 0 times
...
Dorian
4 months ago
Maybe the firewall is blocking the discovery traffic.
upvoted 0 times
...
...
Amie
5 months ago
I think the issue might be with the firewall blocking the discovery traffic.
upvoted 0 times
...
Rebbeca
5 months ago
The firewall blocking the discovery traffic seems like the most likely cause. I'm pretty sure option A is the correct answer.
upvoted 0 times
Lashandra
4 months ago
Once we address the firewall issue, the node should be able to join the cluster.
upvoted 0 times
...
Fletcher
4 months ago
It's important to make sure the discovery traffic is not being blocked.
upvoted 0 times
...
Elvera
4 months ago
Maybe we should check the firewall settings to confirm.
upvoted 0 times
...
Brock
4 months ago
I agree, option A makes the most sense.
upvoted 0 times
...
...

Save Cancel