--> VCMP host uses a flexible resource allocation mechanism to allocate the resources to VCMP Guests.
--> Flexible Resource Allocation mechanism uses the concept of cores to allocate the required resources to VCMP Guests.
--> The total number of cores you allocate to VCMP guests from the VCMP host defines the CPU/RAM.
--> We can allocate the different amount of cores to different VCMP guests depending upon their requirements.
--> Before allocating the number of cores to VCMP guests, You need to take following things into considerations:
1) The total number of Blades available on the VCMP host
2) The total number of Cores each Blade supports
3) The maximum number of VCMP guests can be created on each Blade
--> Once you are aware of the above things then you can proceed for creating VCMP Guests, Before creating them you should calculate the CPU/Memory requirements of each VCMP Guest.
--> The CPU/Memory requirements of each VCMP guest mainly depends upon following things:
1) The number of modules going to be provisioned on the guest/
2) The number connections per second the VCMP Guest is going to handle
3) SSL TPS.
--> For example, if you are using a VIPRION 2150 blade in the VCMP host, which provides approximately 32 GB memory through a maximum of eight cores, and you estimate that the guest will need two cores to satisfy the guest’s total memory requirement of 8 GB.
--> In the above case, Each Core is providing around 4 GB memory per core.
--> VCMP Guest can be configured with following number of cores:1,2,4,6,8,10,12,14,16,18,20
--> A single VCMP Guest can run on single Blade or it can span on multiple Blades. Even, If it is spanning on multiple blades the CPU/Memory will be the same( The memory you allocated on a single blade) and it is not going to be increased even if you span the guest on multiple blades.
--> We can add the VCMP Guest from single Blade to multiple Blades without having any downtime.
--> When you remove a blade from the chassis, the host remembers which guests were allocated to that slot.
--> If you then re-insert a blade into that slot, the host automatically allocates cores from that blade to the guests that were previously assigned to that slot.
Reference: F5.com
Md.Kareemoddin,
CCIE # 54759
--> Flexible Resource Allocation mechanism uses the concept of cores to allocate the required resources to VCMP Guests.
--> The total number of cores you allocate to VCMP guests from the VCMP host defines the CPU/RAM.
--> We can allocate the different amount of cores to different VCMP guests depending upon their requirements.
--> Before allocating the number of cores to VCMP guests, You need to take following things into considerations:
1) The total number of Blades available on the VCMP host
2) The total number of Cores each Blade supports
3) The maximum number of VCMP guests can be created on each Blade
--> Once you are aware of the above things then you can proceed for creating VCMP Guests, Before creating them you should calculate the CPU/Memory requirements of each VCMP Guest.
--> The CPU/Memory requirements of each VCMP guest mainly depends upon following things:
1) The number of modules going to be provisioned on the guest/
2) The number connections per second the VCMP Guest is going to handle
3) SSL TPS.
--> For example, if you are using a VIPRION 2150 blade in the VCMP host, which provides approximately 32 GB memory through a maximum of eight cores, and you estimate that the guest will need two cores to satisfy the guest’s total memory requirement of 8 GB.
--> In the above case, Each Core is providing around 4 GB memory per core.
--> VCMP Guest can be configured with following number of cores:1,2,4,6,8,10,12,14,16,18,20
--> A single VCMP Guest can run on single Blade or it can span on multiple Blades. Even, If it is spanning on multiple blades the CPU/Memory will be the same( The memory you allocated on a single blade) and it is not going to be increased even if you span the guest on multiple blades.
--> We can add the VCMP Guest from single Blade to multiple Blades without having any downtime.
--> When you remove a blade from the chassis, the host remembers which guests were allocated to that slot.
--> If you then re-insert a blade into that slot, the host automatically allocates cores from that blade to the guests that were previously assigned to that slot.
Reference: F5.com
Md.Kareemoddin,
CCIE # 54759
0 comments:
Post a Comment