During a city-festival webcam burst, top-of-rack MAC tables overflowed on a stretched civic VLAN. Which virtual-networking property addresses that traditional scale limit?
Select an answer to reveal the explanation.
Short Explanation
A stretched VLAN is like stuffing every festival-camera nametag into the ToR's tiny pocket. Encapsulation wraps those MACs inside tunnel packets so the physical switch mainly needs the host tunnel endpoints, not every webcam. Pinning VMs or using Workspace ONE does not empty that pocket.
Full Explanation
Physical ToR MAC tables are sized for attached servers, not for thousands of virtual NICs on a stretched VLAN. Overlay encapsulation carries inner VM MAC frames between tunnel endpoints, so the underlay typically learns those endpoint addresses rather than every guest MAC. Pinning each VM to a unique access port, using Workspace ONE UEM, or treating NSX-V VXLAN multicast as a ToR MAC store does not solve that scale problem.