Applies To:

Show Versions Show Versions

Manual Chapter: Deployment Examples
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

A single-slot LTM guest on a standalone system

The simplest example of the deployment of a vCMP system is a standalone system configured with one guest that is provisioned to run BIG-IP Local Traffic Manager (LTM) on a single slot in the VIPRION cluster.

The following illustration depicts a single-slot, two-core LTM guest on a standalone VIPRION chassis.

 Single-slot guest on a standalone VIPRION system

Dual-slot LTM guest within a device group

If you have a redundant system consisting of two VIPRION chassis, you can deploy a vCMP guest on each chassis, where each guest is provisioned to run BIG-IP Local Traffic Manager (LTM) on two slots in the VIPRION cluster.

With this configuration, the host has allocated twice the amount of CPU and memory to the BIG-IP Local Traffic Manager (LTM) module than a configuration where the BIG-IP LTM module is assigned to a single slot only. By putting both guests in a BIG-IP Sync-Failover device group, you are assured that when failover occurs, the LTM guest can continue processing application traffic.

Note: For best results, particularly when connection mirroring is enabled, configure the two guests so that the number of slots, the slot numbers, and the amount of core allocation for the two guests match.

The following illustration depicts the deployment of LTM within a two-slot, four-core guest on each VIPRION chassis in a two-member device group.

 Dual-slot guests in a device group

Multiple guests on multiple slots in device groups

A common use of a vCMP system is to create a redundant system configuration with multiple guests, where each guest contains a different set of BIG-IP modules, with varying amounts of system resource allocated to each guest. In this case, the system is in a redundant configuration consisting of two separate VIPRION systems. For each guest, you can create an equivalent peer guest on the other VIPRION system and create a BIG-IP Sync-Failover device group with the two equivalent guests as members. If failover occurs, the equivalent guest on the peer system can assume the processing of the guest's application traffic.

The following illustration depicts the deployment of BIG-IP guests on multiple populated slots, on two VIPRION chassis. The illustration shows that each guest has an equivalent guest on a peer chassis and that each pair of equivalent guests comprises a separate device group, resulting in a total of three device groups.

 Multiple guests in device groups
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)