A Private VLAN is further divided into the groups:
· Primary PVLAN– The original VLAN that is being divided into smaller groups is called Primary, and all the secondary PVLANs exist only inside the primary.
· Secondary PVLANs – The secondary PVLANs exist only inside the primary. Each Secondary PVLAN has a specific VLAN ID associated to it, and each packet travelling through it is tagged with an ID as if it were a normal VLAN, and the physical switch associates the behavior (Isolated, Community or Promiscuous) depending on the VLAN ID found in each packet.
Note: Depending upon the type of the groups involved, hosts are not able to communicate with each other, even if they belong to the same group.
One type of Primary PVLAN:
· Promiscuous – A node attached to a port in a promiscuous secondary PVLAN may send and receive packets to any node in any others secondary VLAN associated to the same primary. Routers are typically attached to promiscuous ports.
Two types of Secondary PVLANs:
· Isolated – A node attached to a port in an isolated secondary PVLAN may only send to and receive packets from the promiscuous PVLAN.
· Community – A node attached to a port in a community secondary PVLAN may send to and receive packets from other ports in the same secondary PVLAN, as well as send to and receive packets from the promiscuous PVLAN.
Teaming and Failover Policies:
Route based on the originating virtual port:
Round robin fashion based on vm or vmkernel virtual port
1st VM is hashed to vNic 1 2nd VM is hashed to vNic 2 and so on, then it start over to vNic 1
default configured and works everywhere without Physical switches configuration
What if 1st and 2nd VM are very high consumption and they are hashed to their respective vNic ?
Route based on source MAC hash:
Round robin fashion based on vm MAC address
Same as virtual port ID if the VM has one vNIC
useful if a VM has more than vNics "Multiple MAC addresses"
Basic Round robin distribution
Route based on IP hash:
· Requires port channel on physical switch.
· Best client / server hashing mechanism , connections are spread over multiple NICs.
· No single conversation uses a single throughput.
· Some Physical switches vendor do not support ether channel if you want to configure port channel 2 ports one per each physical switch "Cisco 6500 have issues in this as an example"
Route Based NIC load "LBT Load Based Teaming":
initial based on VM hash round and robin when vpshere boot VMs up , then If more than 30 seconds a nice is 75% utilized , it starts moving VMs MAC conversation to less utilized NIC
· No special configuration on the
· Enterprise Plus license.
· Must be a vDS