All about vSphere Distributed Virtual Switch ( DvSwitch)
- vSphere Distributed Switch
- Private VLANs (pVLANs)
- Networking policies
- Configuration tasks
Explain vSphere distributed switch (DvSwitch).
1. Creates a centralized virtual switch that multiple ESXi hosts can subscribe to.
2. Reduces N/Wing configuration and changes and reduces the windows errors. As we don’t need to perform N/W configuration multiple times of each ESXi host individually.
3. Allows you to centrally manage N/Wing for VMs across multiple ESXi hosts.
4. Consistent N/W configuration & stats as VMs are migrated using VMotion.
5. DvPort groups similar to standard vSwitch port groups but on the VDS level
6. Increase capabilities – security, traffic control, vLAN and more
7. Ability to add 3rd party switch – Nexus 1000V.
Explain Private vLANs or pVLANs?
Primary:- Original vLAN that can be subdivided into multiple secondary pVLANs.
Secondary:- They exist only inside the primary vLAN.
Each secondary pVLAN has vLAN ID i.e. a secondary subset vLAN ID with the original or primary vLAN ID.
So every packet that goes IN and OUT of the secondary private vLAN gets an additional ID tag to it so that you can identify it. Here take an example original vLAN ID is 1 and secondary vLAN ID pVLAN is 12 so the packet would look like 1.12 so that the physical switch can understand where this packet will destined to. You can have multiple secondary pVlAN in three different modes promiscuous, isolated, community.
It associates each packet with an ID that the physical switch can use to identify the mode (promiscuous, isolated, community).
PVLANs Secondary Mode Nodes:-
May send and receive packets to any secondary pVLANs.
Typically routers are attached to promiscuous ports.
May only send and receive packets from the promiscuous pVLANs.
May send and receive packets b/w any secondary pVLANs and also with the promiscuous pVLAN.