Manual Chapter : Best Practices

Applies To:

Show Versions Show Versions


  • 12.1.4, 12.1.3, 12.1.2, 12.1.1


  • 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1


  • 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1


  • 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1


  • 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1
Manual Chapter

Best Practices

vCMP best practices

F5 Networks makes the following recommendations for managing a vCMP® system.

Category Recommendation
vCMP® disk management Ensure that you allocate enough disk space for other installation slots for the vCMP host before you provision the vCMP feature.
Network setup Before setting up a vCMP system, verify that each slot's management interface is physically wired to an external bridge.
Change of vCMP management IP address You should only change the vCMP management IP address when logged into the vCMP host. Changing this address when logged into a guest could produce unexpected results. Note that changing individual cluster member IP addresses when logged into a guest is fully supported.
Slot assignment to guests Whenever possible, configure a guest to allow the guest to run on more slots than are actually populated with blades. The result is an automatic expansion of the guest cluster when you insert an additional blade.
Virtual disk management To prevent unattached virtual disks from consuming disk space over time, consider deleting unwanted virtual disks from the system. Otherwise, previously provisioned virtual disks remain on disk after their associated vCMP guest configurations have been deleted.
Protection from performance degradation To protect a guest from performance degradation if a blade failure occurs, configure high availability if possible. You do this by setting up device service clustering (DSC®). For a standalone vCMP system, consider deploying guests with sufficient cores and slots to ensure that a single blade failure does not result in unacceptable service degradation.