Installation Guide

Figure 11 KVM sample network configuration
Provider Networks
Cloud Data TrunkManagement Trunk
Cloud Management Network
Data Center Management Network
External Network
Private Provided Network
KVM appliance management - CloudSystem components
CS Network Node
Appliance VM
Beta 2
Multiple
vNICo vNIC1 vNIC2
CS Network Node
Appliance VM
Beta 2
Multiple
vNICo vNIC1 vNIC2
vSphere
VM
5.X
CloudSystem
Foundation base
appliance VM
vCenter proxy
appliance VM
CloudSystem
Enterprise
appliance VM
SDN
appliance
VM
bondA X
DC Mgmt
bondB bondC
bondA Y
Cloud Mgmt
br-dc-mgmt br-cloud-mgmt br-external br-cloud-trunk
ethQ ethRvmkM vmkN
vNIC1 vNIC0 vNIC0
vNIC0
Management Vswitch / Port groups
dc-mgmt
vmkM vmkN
ethO ethPethM ethN
vNIC0
vNIC0
vNIC1
Network node
appliance VMs
(multiple)
vNIC0 vNIC2
vNIC1
bondA
NOTE: The vCenter proxy appliance shown in the figure is only used if you are managing ESX
compute nodes from a KVM management hypervisor.
Configure the network infrastructure on the KVM management hypervisor
The following procedure describes the steps needed to configure the network interfaces on a KVM
hypervisor. The procedure is based on the information provided in the image above, but you can
modify the configuration to fit your network needs.
Read the following important information before you configure the networks for the Foundation
base appliance.
Table 15 Important network configuration information
Why it mattersImportant to know
A network of cables must be physically connected to allow
the supported virtual appliances to communicate over the
Make sure the VLANs in the Management Trunk are
actually assigned to cables plugged into the interface
network ports. networks. Make sure the virtual and physical components
have correct association such that data can transfer
between points (between appliances, hypervisors, servers,
nodes, etc.)
iSCSI initiators are set up on the compute nodes, not the
management hypervisor. Initiators check to see which
storage resource on the network are available.
Do not configure the iSCSI initiators on the management
hypervisor.
It is important to use the same names defined in the
hardware profile when assigning the networks in the
Generic names, as shown on the sample configuration
figure above, are used in this procedure. Make sure to
management hypervisor ifconfig files. If the names do
not match, then network communication errors will occur.
36 Installing CloudSystem on a KVM hypervisor