A vCMP guest is an object that you create on the vCMP™ system for the purpose of running an instance of one or more BIG-IP® modules. An example of a guest is an instance of both BIG-IP® Local Traffic Manager™ and BIG-IP® Global Traffic Manager™. A guest has its own portion of system resources allocated to it, such as CPU cores and disk space, effectively making the guest appear as if it were a separate BIG-IP device. On a vCMP system, you can run up to sixteen guests simultaneously, depending on licensing and type of hardware.
In addition to containing BIG-IP modules, each guest contains its own instance of TMOS®. This TMOS instance gives you the ability to provision, configure, and manage each BIG-IP module within the guest.
This illustration shows three guests running on a BIG-IP system. Guest 1 runs on a single slot only. Guest 2 and Guest 3 each run on all available slots.
When you initially create a vCMP guest, you actively select the ISO image to install for that guest. Then, when you move the guest to the Provisioned state, the vCMP host installs that ISO image onto each of the newly-created virtual disk images pertaining to that guest.
You can configure each vCMP guest to operate in one of two modes: Bridged or Isolated. The mode you choose specifies whether the guest is bridged to or isolated from the vCMP host's management network.
Bridged mode is the default network mode for a vCMP guest. This mode provides full Layer 2 access between guests, and creates a bridge between each guest's management interface, the host's management interface, and devices connected to the host's front-panel management port. Typically, you configure a guest's management port to be on the same IP network as the host's management port, with a gateway identical to the host's management gateway. This allows you to make TCP connections (for SSH, HTTP, and so on) easily from either the host or the external network to the guest, or from the guest to the host or external network. Although the guest and the host share the host's Ethernet connection, the guest appears as a separate device on the local network, with its own MAC address and IP address.
Changing this property while the guest is in the Configured or Provisioned state has no immediate effect.
A vCMP guest is always in one of these states:
The system resources that the BIG-IP® system allocates to each guest are: CPU cores, physical memory, and virtual disk space. The system allocates resources to a guest when you set the state of the guest to Provisioned.
For single-slot guests, when allocating CPU cores to a guest, the system determines the best slot for the guest to run on, that is, the slot with the most unallocated CPU cores. For all-slot guests, the system allocates CPU cores from every available slot.
|Guest type||CPU core allocation|
|Single slot||The system allocates one or more CPU cores to the guest.|
|All slot||The system allocates two CPU cores from each available slot. For example, if three slots are available, the system allocates two CPU cores from each slot, totaling six CPU cores for that guest. The maximum number of CPU cores that the system can allocate to a guest is eight.|
This illustration shows that the BIG-IP system has allocated two CPU cores to guest1, which is deployed on slot 1. Note that guest0 has no CPU cores allocated to it because the guest has not yet been deployed.
A virtual disk is a portion of the total disk space on the BIG-IP system that the system allocates to a vCMP guest. The system allocates one virtual disk to each slot on which the guest resides. Although each virtual disk for a guest has a fixed, maximum size limit, the actual size of a virtual disk is the amount of space that the guest actually uses on that slot.
You cannot explicitly create virtual disks; instead, the BIG-IP system creates virtual disks whenever you set the state of a guest to Provisioned and the guest does not already have an attached virtual disk.
You can configure a single vCMP guest to run on either one slot or all slots of the system:
Before modifying a vCMP guest, be aware of the following facts for these properties.
|Host Name||The system immediately propagates the modification to all VMs of the guest, if the guest is in the Deployed state.|
|Cluster IP Address||The system immediately propagates the modification to all VMs of the guest, if the guest is in the Deployed state.|
|Virtual Disk||If you change this value from a specific file name to None, the
BIG-IP® system detaches that virtual disk file from the guest. In this
case, the virtual disk remains on the system as an unattached virtual disk. If you want to
delete the virtual disk, you must do this explicitly, using the Virtual Disk List screen of
the BIG-IP Configuration utility.
Note: You can only modify the Virtual Disk property by first changing the State property to Configured.
|VLAN List||The system immediately propagates the modification to all VMs of the guest, if the guest is in the Deployed state.|
|State||If you change this value from Deployed or Provisioned to Configured, the BIG-IP system automatically de-allocates all resources except for the guest's virtual disk.|
|Management Network||If you change the value of the Network Mode property while the
guest is in the Deployed state, then:
Changing the Network Mode property while the guest is in the Configured or Provisioned state has no immediate effect.