Free Access Nutanix NCP-MCI-6.5 New Release

According to the Nutanix Support & Insights, IPAM enables AHV to assign IP addresses automatically to VMs using DHCP. You can configure each virtual network and associated VLAN with a specific IP subnet, associated domain settings, and group of IP address pools available for assignment.

A managed network is a type of network that can be created on an AHV cluster and allows VMs to automatically be assigned an IP address at creation time. A managed network uses the Nutanix IP Address Management (IPAM) service, which provides DHCP and DNS functionality for the VMs on the network. A managed network can be configured with a subnet range, a default gateway, and DNS servers. The IPAM service will allocate IP addresses from the subnet range to the VMs and register their hostnames in the DNS servers. The IPAM service will also release the IP addresses when the VMs are deleted or moved to another network1.

To create a managed network on an AHV cluster, the administrator can use Prism Element or Prism Central. The steps are as follows2:

• In Prism Element, go to the Network Configuration page and click Create Network.
• In Prism Central, go to the Networks page and click Create.
• Enter a name and description for the network.
• Select Managed as the network type.
• Enter the subnet range, default gateway, and DNS servers for the network.
• Optionally, enable VLAN tagging and enter a VLAN ID for the network.
• Click Save.

According to the web search results, the two impacts on the cluster that will result from increasing the vCPU count on all of the VDI VMs are:

• Increase CPU utilization%: CPU utilization is the percentage of time that a CPU is busy executing instructions5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the demand for CPU resources on the cluster, which will increase the CPU utilization percentage6.
• Increase CPU ready%: CPU ready is the percentage of time that a vCPU is ready to run but is waiting for a physical CPU to become available5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the contention for physical CPU resources on the cluster, which will increase the CPU ready percentage6. A high CPU ready percentage can indicate performance issues such as latency or slowdowns5.

The correct answer is B. The existing and the expansion node are on different VLANs.

The output shows that the new node has a br0-up bond with four interfaces: eth0, eth1, eth2, and eth3. The bond is configured with LACP active and LACP fallback set to false. This means that the bond will only work if the upstream switch supports LACP and is configured to form an LACP group with the four interfaces. However, the output also shows that the bond has no IP address assigned to it, which indicates that the bond is not operational. One possible reason for this is that the existing and the expansion node are on different VLANs, and the upstream switch is not configured to allow the VLAN traffic on the LACP group. This would prevent the new node from communicating with the cluster and being discovered by the Expand Cluster function in Prism.

To verify this, the administrator can check the VLAN configuration on the upstream switch and compare it with the existing nodes. Alternatively, the administrator can use the “manage_ovs show_uplinks” command on an existing node and compare the output with the new node. If there is a VLAN mismatch, the administrator can either change the VLAN configuration on the switch or on the new node to match the existing nodes.