HP FlexFabric Virtual Switch 5900v Technology White Paper

8
Figure 9 Automatic deployment of network policies for VM migration
VMware ESXiVMware ESXi
HP 5900v VDS
VM
#5
VM
#8
VM
#7
VM
#6
VM
#4
VM
#3
VM
#2
VM
#1
Station 1
VM
#1
VM
#2
VM
#3
VM
#4
Reasons for VM migration:
• VM failures
• Dynamic resource
scheduling (DRS)
• Hardware maintenance
• Hardware failures
5900v
VCE
Network policy migration:
• Maintains network
policies for ports through
the 802.1 Qbg standard.
• Makes sure network
policies remain the same
before and after VM
migration.
• Ensures service
continuity.
vCenter Server
Plug-in
Station 2
HP iMC
• EVB protocol negotiation
• VEPA traffic forwarding
SOAP/REST interface obtains
network policies for ports
Clear boundary between virtual computing and
network control
In a virtualized environment, vSwitch runs in stations to control inter-VM traffic. However, it is managed
by the server administrator, which results in difficult vSwitch configuration management.
Figure 10 Clear boundary between virtual computing and network control
VMware ESXiVMware ESXi
5900v virtual switch VDS
VM
#5
VM
#8
VM
#7
VM
#6
Station 1
VM
#1
VM
#2
VM
#3
VM
#4
5900v
VCE
vCenter Server
Plug-in
Station 2
HP iMC
Network administrator
• Manages virtual
switching policies
Server administrator
• Manages computing
resource virtualization
As shown in Figure 10, when the 5900v virtual switch is integrated with VMware vCenter Server, it
allows the server administrator to use the VMware tools for managing VMs. It also enables the network
administrator to use the Web configuration tools for managing the VM network. Although server
administration and network administration work independently, the 5900v virtual switch can implement
the same configurations and policies in the virtualization environment on the EVB stations. This clarifies
the boundary between virtual computing and network control.