Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

6 week online course

Start now!
back to overview

VLANs used by Nexus 1000V

Chris sent me an interesting question:

Imagine L2 traffic between two VMs on different ESX hosts, both using Nexus 1000V. Will the physical switches see the traffic with source and destination MACs matching the VM's vNICs or traffic on NX1000V "packet" VLAN between VEMs (in this case, the packet VLAN would act as a virtual backplane)?

To decode the acronyms in the question, please read my What exactly is a Nexus 1000V post.

Digression into Nexus 1000V VLAN usage

Nexus 1000V uses up to three VLANs for its communication needs:

Packet VLAN is a data-plane VLAN used to exchange control protocol packets between VEMs and VSMs. It’s used to send CDP (as well as LACP and IGMP) packets received by a VEM to the VSM. It’s also used by the VSM to send CDP (or LACP) packets through the desired physical port(s) on desired VEM.

Control VLAN is a control-plane VLAN used by the VSM to download configuration information into individual VEMs.

VEM receives parts of initial configuration that it needs to establish VEM-to-VSM communication directly from vCenter.

You also have to establish communication between VSM and vCenter using a Management VLAN. VSM uploads parts of its configuration to the vCenter (to allow VEMs to start, see above) and uses vCenter API to create vCenter objects like port groups based on NX-OS configuration.

You can’t configure the management VLAN in VSM. You connect the management port of the VSM (a virtual machine) to a vCenter port group and specify the desired VLAN in the port group configuration (follow this procedure if the VSM uses a VEM to communicate with the physical network).

Read the article I published in CT3 wiki to learn more about control and data planes in networking devices.

You can use the same VLAN for all three purposes; you can also replace packet and control VLAN with layer-3 communication (using UDP). Using a separate management VLAN sounds like a good idea, but I fail to see why it would be a good idea to use separate Packet and Control VLANs.

Back to the original question

Have you noticed that I haven’t mentioned VM traffic in the previous section? VM traffic does not use the Nexus 1000V-specific VLANs; it gets a VLAN tag specified in the associated port profile (and reflected in the corresponding vCenter port group) and is sent toward the physical network using whatever load balancing mechanism you’ve configured.

The packet VLAN is never used for VEM-to-VEM communication. Even though the inter-VM traffic might pass through two VEMs, neither VEM is aware of that fact; they rely on the physical switches to sort out the MAC address information and forward the traffic toward destination VM.

Even more information

You’ll find in-depth descriptions of network virtualization technologies (including Cisco’s Nexus 1000V, VN-Tag/VM-FEX and VSG) in my VMware Networking Deep Dive webinar (recording or live session). The webinars is also available as part of the yearly subscription.

No comments:

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Sidebar