Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix NCP-MCI Exam - Topic 5 Question 18 Discussion

Posted by Chanel on Sep 09, 2024 at 07:18 PM

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 running, configured with appropriate IP addresses, and br0-up has been configured the same 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?

Suggested Answer: B

The task that needs to be performed when time is not synchronizing properly after deploying a cluster is NTP configuration. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, Network Time Protocol (NTP) is used to synchronize the system time across all the nodes in a cluster. If the time is not synchronizing properly, it indicates that there might be an issue with the NTP configuration. Therefore, checking and correcting the NTP configuration would be the appropriate action to resolve this issue. The other options like DNS configuration, HA configuration, and SMTP configuration are not directly related to time synchronization in a cluster.


Get Premium NCP-MCI Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
32 comments · newest first
SU
Suzi 10 months ago
Really? I thought LACP was done before expansion.
QU
Quiana 11 months ago
I agree, LACP is crucial for this setup.
SH
Sharika 11 months ago
Wait, are we sure there's no firewall blocking?
BA
Basilia 11 months ago
I think it's definitely the LACP config.
SE
Selene 11 months ago
Sounds like a VLAN issue to me.
RE
Reuben 11 months ago
I thought LACP needed to be set up before adding nodes, but I’m not confident if that’s the right answer for this question.
TA
Tamesha 12 months ago
I feel like I read that firewalls can block discovery traffic, but I can't recall if that applies to this scenario.
MA
Maricela 12 months ago
I think I came across a similar question where VLAN mismatches caused issues. Could that be the problem here too?
SH
Shawnta 1 year ago
I remember something about LACP configurations being crucial for cluster expansions, but I'm not entirely sure if it's the upstream switch settings or something else.
GL
Gladis 1 year ago
Alright, time to put on my troubleshooting hat. I'll start by verifying the LACP configuration on the upstream switch and make sure the VLANs are set up correctly.
AL
Alaine 1 year ago
I'm a bit confused by this one. I'll need to review the details and try to understand the network setup better before I can make a decision.
HA
Hailey 1 year ago
Ah, I think I know what the problem is. The firewall is probably blocking the discovery traffic, so I'll need to check the firewall rules.
JE
Jeannine 1 year ago
Okay, let's see here. The node is configured correctly, so it's likely an issue with the network setup. I'll need to double-check the VLAN and LACP configurations.
AM
Ammie 1 year ago
Hmm, this one seems tricky. I'll need to carefully review the information provided and think through the possible causes.
NI
Nicholle 1 year ago
Okay, let's see. Jian was acquiring feeds from sources like honeynets, P2P monitoring, and application logs. That sounds like he was gathering external intelligence feeds, so I'll go with option B.
CA
Carli 1 year ago
Wait, what if the answer is the ports on the upstream switch are not configured for LACP? That would be a real 'switch' up! Haha, get it?
SH
Shakira 1 year ago
↳ replying to Carli
User 3: Let's check the switch configuration to see if that's the issue.
GE
Gertude 1 year ago
↳ replying to Carli
User 2: It could be, but it might also be something else causing the problem.
LA
Lazaro 1 year ago
↳ replying to Carli
User 1: Maybe that's the issue, the ports on the switch are not configured for LACP.
DE
Delila 1 year ago
Ah, the old 'different VLAN' trick! Classic Nutanix exam question. Time to brush up on my network configuration skills.
NO
Nobuko 1 year ago
I'm going with option D. The LACP configuration must be completed after cluster expansion. It's like trying to put the cart before the horse!
EL
Elina 1 year ago
↳ replying to Nobuko
It could also be that there is a firewall blocking the discovery traffic from the tlu.
MA
Madonna 1 year ago
↳ replying to Nobuko
Maybe the ports on the upstream switch are not configured for LACP.
RI
Rima 1 year ago
↳ replying to Nobuko
I agree, the LACP configuration should be completed after cluster expansion.
MA
Margart 1 year ago
↳ replying to Nobuko
I think option D is the most likely cause of the issue.
JO
Josue 1 year ago
Hmm, I'm not sure. Could it be the firewall blocking the discovery traffic? Or maybe the LACP configuration needs to be done after expansion?
LA
Lavonda 1 year ago
The answer is B. The existing and the expansion node are on different VLANs. That would prevent the cluster from discovering the new node.
RE
Rebecka 1 year ago
↳ replying to Lavonda
B) The existing and the expansion node are on different VLANs.
CA
Candida 1 year ago
↳ replying to Lavonda
A) The ports on the upstream switch are not configured for LACP.
TY
Tyisha 1 year ago
I believe the firewall could also be blocking the discovery traffic.
VE
Veta 2 years ago
I agree with Jeannetta, it could be the ports on the switch not configured for LACP.
JE
Jeannetta 2 years ago
I think the issue might be with the LACP configuration.
0/2000 characters

Save Cancel