An engineer must verify that a VLAN used by court-records servers is mapped into the correct VXLAN VNI on a Junos leaf. What should they confirm?
Select an answer to reveal the explanation.
Short Explanation
VLAN is the local room number; VNI is the campus-wide hallway ID—you need the map that ties them together. On the leaf, check the VLAN-to-VNI / bridge-domain binding is present and up. Matching AS numbers or wishing on DHCP won’t build that map.
Full Explanation
On Junos data-center switches, tenant VLANs are associated to VXLAN through bridge-domain (or equivalent) configuration that maps VLAN to VNI. Verification should show that mapping is configured and operational on the leaf hosting the servers. Spines generally do not need the same access VLAN locally present for VXLAN bridging. Operators who skip this check often chase underlay symptoms when the overlay segment was never bound.