Wastewater must keep a physical ToR VLAN for a lab-instrument network and still attach VMs in NSX. How should the operator create that network in the GUI?
Select an answer to reveal the explanation.
Short Explanation
Some lab gear still lives on a numbered copper VLAN. That's a VLAN-backed segment: Networking > Segments, VLAN transport zone, plus the ToR VLAN ID—not a Geneve overlay with no VLAN.
Full Explanation
Wastewater’s lab-instrument network that must remain a physical ToR VLAN while still attaching VMs in NSX is created as a VLAN-backed segment: Networking > Segments with a VLAN transport zone and the ToR VLAN ID. That bridges the civic lab VLAN into NSX without forcing Geneve overlay encapsulation for that instrument LAN. Creating the segment only on the overlay (Geneve) transport zone with no VLAN ID builds an overlay segment, not the ToR VLAN attachment required for the physical lab network. Gateway Firewall context profiles do not create VLAN L2 segments. System > Licenses keys do not instantiate VLAN segments. Exam caveat: VLAN segments require hosts/Edges in a VLAN transport zone that includes the VLAN; overlay TZ membership alone will not carry that ToR VLAN. Operational check: confirm the VLAN transport zone and uplink VLAN trunking on the ToR, create the segment with the correct VLAN ID, realize it, attach a lab VM, and verify connectivity to physical instruments; document VLAN ID and segment name in the wastewater network register. Confirm the ToR still trunks the lab VLAN after any switch change, and keep the VLAN ID in both NSX and the physical runbook identical so instrument techs and NSX operators troubleshoot the same Layer-2 domain.