Allocate VNI ranges across segments and generate multicast group assignments. Get Linux VTEP, Open vSwitch, and Cisco NXOS deployment commands.
10000 - 110001,00110101| Segment | VNI Range | VNI Count | Multicast Group |
|---|---|---|---|
| Seg 1 | 10000 - 10100 | 101 | 239.1.1.1 |
| Seg 2 | 10101 - 10201 | 101 | 239.1.1.2 |
| Seg 3 | 10202 - 10302 | 101 | 239.1.1.3 |
| Seg 4 | 10303 - 10403 | 101 | 239.1.1.4 |
| Seg 5 | 10404 - 10504 | 101 | 239.1.1.5 |
| Seg 6 | 10505 - 10605 | 101 | 239.1.1.6 |
| Seg 7 | 10606 - 10706 | 101 | 239.1.1.7 |
| Seg 8 | 10707 - 10807 | 101 | 239.1.1.8 |
| Seg 9 | 10808 - 10908 | 101 | 239.1.1.9 |
| Seg 10 | 10909 - 11000 | 92 | 239.1.1.10 |
VXLAN (Virtual Extensible LAN) extends Layer 2 segments over Layer 3 UDP networks using 24-bit Virtual Network Identifiers (VNIs), supporting up to 16 million overlay segments versus the 4094 limit of traditional 802.1Q VLANs. The VNI Planner divides a VNI range into equal-sized segments and assigns each a unique multicast group for BUM (broadcast, unknown-unicast, multicast) traffic.
The Linux VTEP output uses ip link to create VXLAN tunnel interfaces, one per segment, each pinned to a specific VNI and multicast group. Open vSwitch uses ovs-vsctl to add VXLAN ports to an existing bridge. Cisco NXOS uses vn-segment to map VLANs to VNI ranges and assigns multicast groups in the NVE interface.
Choose a multicast base in the 239.x.x.x range (Organisation-Local scope). One multicast group per segment is the simplest model; production deployments may share a group across multiple segments if the multicast topology is constrained. The underlay device should be the NIC with the VTEP IP address.