Nutanix NCP-MCI Exam - Topic 2 Question 14 Discussion

Actual exam question for Nutanix's NCP-MCI exam

Question #: 14
Topic #: 2

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?

AThere is a firewall blocking the discovery traffic from the cluster.

BThe ports on the upstream switch are not configured for LACP.

CThe existing cluster and the expansion node are on different VLANs.

DLACP configuration must be completed after cluster expansion.

Show Suggested 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.

by Merissa at Jul 07, 2024, 12:16 PM

Limited Time Offer

25%

Off

Get Premium NCP-MCI Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Matthew

3 months ago

I’m surprised it’s not just a simple IP conflict!

upvoted 0 times

...

Regenia

3 months ago

Wait, are we sure the node is even powered on?

upvoted 0 times

...

Lemuel

3 months ago

Could be LACP misconfiguration on the switch.

upvoted 0 times

...

Roxane

4 months ago

I think it’s definitely a firewall blocking the traffic.

upvoted 0 times

...

Providencia

4 months ago

Sounds like a VLAN issue to me.

upvoted 0 times

...

Arlette

4 months ago

I feel like the upstream switch configuration could be the key here. If LACP isn't set up correctly, it might prevent the node from joining the cluster.

upvoted 0 times

...

Wilburn

4 months ago

I'm a bit unsure about the LACP settings. I thought they needed to be configured before adding a node, but maybe it’s different for expansion?

upvoted 0 times

...

Malinda

4 months ago

I think I practiced a question where VLANs were the issue. If the new node is on a different VLAN, that might explain why it's not being found.

upvoted 0 times

...

Jimmie

5 months ago

I remember something about firewalls causing issues with node discovery. Could that be the problem here?

upvoted 0 times

...

Diane

5 months ago

I'm a bit confused by the networking terminology in this question. I'll need to review my notes on LACP and cluster expansion to make sure I understand the concepts before attempting to answer.

upvoted 0 times

...

Arminda

5 months ago

Ah, I see. The question is hinting that the LACP configuration might be the problem. I'll focus on that and see if I can figure out the right solution.

upvoted 0 times

...

Linwood

5 months ago

Hmm, the question mentions the node has been configured correctly, so I don't think it's a firewall or VLAN issue. Maybe it's something to do with the LACP configuration?

upvoted 0 times

...

Donette

5 months ago

This looks like a tricky networking issue. I'll need to carefully review the information provided and think through the possible causes.

upvoted 0 times

...

Solange

5 months ago

Okay, I think I've got it. The question is suggesting that the LACP configuration needs to be completed after the cluster expansion, so that's likely the cause of the issue. I'll select that option.

upvoted 0 times

...

Herman

5 months ago

I feel pretty good about this one. Intelligent Document Automation and Care Authorizations seem like the obvious choices to recommend. The question is straightforward, and those capabilities align well with the described needs.

upvoted 0 times

...

Mickie

5 months ago

I'm a bit confused by the wording of this question. Can someone help me understand what exactly they're looking for here? I want to make sure I get the right answer.

upvoted 0 times

...