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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Nutanix Exam NCP-MCI Topic 1 Question 19 Discussion

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

An administrator initially performed a cluster Foundation using a flat switch without any VLAN configuration. After the Foundation, the administrator moved the dual 25Gb data ports and single 1Gb IPMI port to the actual switches with the below network configurations:

. All VLANs are tagged

. VLAN 1000 for CVM\Hypervisor traffic

* VLAN 1001 for User VM traffic

. VLAN 100 for IPMI traffic

After moving the IPMI network links, the administrator can no longer ping the IPMI IPs.

Which two changes does the administrator need to make? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, C

The issue described pertains to the inability to ping the IPMI IPs after moving the IPMI network links to the actual switches with specific VLAN configurations. The two changes that the administrator needs to make are:

A . SSH to AHV and set the VLAN ID using IPMI Tool: Since all VLANs are tagged in the new network configuration, the IPMI network interface needs to be aware of the VLAN it's supposed to communicate on. This can be achieved by setting the VLAN ID using the IPMI Tool on the AHV.

C . SSH to AHV and change the IP address using IPMI tool: If the IPMI IP addresses were initially set in a different subnet that is not routable in the new network configuration, the administrator would need to change the IPMI IP addresses to match the new network configuration. This can be done by SSHing to the AHV and using the IPMI Tool to change the IP address.


by Venita at Sep 16, 2024, 09:24 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Tyra
15 days ago
The admin must have used the IPMI tool to order a pizza instead of configuring the network. I'd go with B and D just to be safe.
upvoted 0 times
...
Dorinda
18 days ago
Wait, the admin moved the IPMI port but forgot to move the admin's caffeine intake too? Looks like they need to restart their brain before the network!
upvoted 0 times
...
Sue
26 days ago
Hmm, I'm torn between B and D. Restarting Genesis might be the nuclear option, but it could work. Still, I'd try the network services first.
upvoted 0 times
...
Shawnda
27 days ago
Hold up, did the admin forget to configure the IPMI port VLAN? That's a rookie mistake, but at least it's an easy fix with option A.
upvoted 0 times
Celeste
12 days ago
Option B) SSH to CVM and restart network services on all host.
upvoted 0 times
...
Josefa
14 days ago
Option A) SSH to AHV and set the VLAN ID using IPMI Tool.
upvoted 0 times
...
Lyla
19 days ago
Option A) SSH to AHV and set the VLAN ID using IPMI Tool.
upvoted 0 times
...
...
Jaime
1 months ago
I believe the administrator should also SSH to CVM and restart network services on all hosts as the second change.
upvoted 0 times
...
Sheridan
1 months ago
I agree with Thurman. Changing the VLAN ID using IPMI Tool should fix the issue.
upvoted 0 times
...
Thurman
1 months ago
I think the administrator should SSH to AHV and set the VLAN ID using IPMI Tool.
upvoted 0 times
...
Isaiah
2 months ago
I think C is the right answer. Changing the IPMI IP address using the IPMI tool should resolve the connectivity issue.
upvoted 0 times
...
Corazon
2 months ago
Option B makes the most sense. Restarting the network services on the hosts should reconnect the IPMI ports to the correct VLAN.
upvoted 0 times
Svetlana
1 months ago
I agree. Restarting network services on hosts is a good first step to troubleshoot the issue.
upvoted 0 times
...
Tandra
1 months ago
Option B makes sense. Restarting network services should help reconnect IPMI ports to correct VLAN.
upvoted 0 times
...
...

Save Cancel