NCP-MCI-6.10 · Question #61
A newly-hired Nutanix administrator was tasked by the CIO to create a single VM on a test network. The network administrator stated that a native VLAN was used on the Cisco TOR switches with the…
The correct answer is B. Change VLAN field from vlan. 1 to vlan.0. In Nutanix AHV networking, VLAN ID 0 represents untagged (native) traffic, not VLAN ID 1. A native VLAN on a Cisco switch means frames are sent untagged, so Nutanix must be configured with VLAN 0 to match that behavior. Setting the VLAN field to 1 tells Nutanix to tag the…
Question
A newly-hired Nutanix administrator was tasked by the CIO to create a single VM on a test network. The network administrator stated that a native VLAN was used on the Cisco TOR switches with the following parameters:
IP address:172,16.1.2 Network Mask: 255.255.255.0 Default gateway: 172.16.1.1 VLAN:1 The same parameters were used to create a network profile on Nutanix, but the when the VM was on ... What should the Nutanix administrator do to fix this issue?
Options
- ANutanix removed support for native VLAN.
- BChange VLAN field from vlan. 1 to vlan.0.
- CEnable IPv6 on the VM.
- DUse DHCP as opposed to static IP
How the community answered
(30 responses)- A10% (3)
- B80% (24)
- C3% (1)
- D7% (2)
Explanation
In Nutanix AHV networking, VLAN ID 0 represents untagged (native) traffic, not VLAN ID 1. A native VLAN on a Cisco switch means frames are sent untagged, so Nutanix must be configured with VLAN 0 to match that behavior. Setting the VLAN field to 1 tells Nutanix to tag the traffic with VLAN ID 1, which the switch does not expect on a native VLAN port, causing the VM to lose connectivity. Changing the network profile from VLAN 1 to VLAN 0 aligns Nutanix's behavior with the switch's native (untagged) configuration and restores connectivity.
Topics
Community Discussion
No community discussion yet for this question.