## Forum Discussion

# relocation cpu core on vcmp host the guest configuration back to default configuration

Hi i have a problem after relocation cpu core and the configuration back to default Before : guest A : on slot 2 with 4 core After : guest A : on slot 3 and 4 with 2 core per slot after the guest...

  * Hi Herdi,

When you do adding cores to vcmp guest, it must be in "**Configured" state, then when you are done with the settings must put it in "Provisioned" state. Finally when you want to use the guest you must set it as "Deployed" state. It takes some minutes o get the state change hence wait for the processes to complete before moving to the bext step.**

## Increasing CPU cores for a deployed guest

Before doing this task, confirm that your BIG-IP® user account has an Administrator role assigned to it.

If you have a deployed vCMP guest, and you decide that you need to allocate more CPU cores per slot to the guest than you had originally allocated, you can increase the number of cores per slot for the guest.

To do this, you'll first need to set the guest state from Deployed to Configured. Once you've increased the number of cores per slot for the guest, you can set the guest back to the Deployed state.

Note that when switching between guest states, the process can take several minutes for the guest to shut down cleanly and restart again.

Important: When you set a guest to the Configured state, the guest is removed from service until you set the guest back to the Deployed state.
    1. Log in to the BIG-IP Configuration utility on the vCMP host, using the VIPRION® system's primary management IP address.
    2. On the Main tab, click **vCMP > Guest List .**
    3. View the graphic to determine the number of unused cores available on the slot.

This tells you how many cores are available to add to the guest.

    4. In the Name column, find the name of the guest that needs additional CPU cores and confirm that the Requested State is Deployed.
    5. To the left of the guest name, select the check box.
    6. Click the Disable button.

The guest state changes from Deployed to Configured.

Important: It might take a few minutes for the guest state to change to Configured. Although the Guest List screen does not display a progress indicator during this state change, you can log into the console and view the status of the guest at any time, using the command tmsh show vcmp guest.

    7. Once the screen shows that the guest is now in the Configured state, click the guest name.

The guest properties screen opens.

    8. From the Cores per Slot list, select a higher number of CPU cores.

Note: Do not select a value that exceeds the total number of unused cores available for use on the slot.

For example, if you currently have two cores per slot allocated to the guest and you want to add two cores, then from the Cores per Slot list, select 4.

    9. From the Requested State list, select Deployed.
    10. Click Update.

The Guest List screen opens again and you will see that the guest state is changing. 

Important: It might take a few minutes for the guest state to change back to the Deployed state.

After you complete this task, the guest has additional CPU cores per slot and is capable of processing application traffic. 

  


# Just for reference as the actual implementation of vCMP on your Box series platform could be little different different 

Virtualized Clustered Multiprocessing (vCMP) is a feature of the BIG-IP® system that allows you to run multiple instances of BIG-IP software on a single hardware platform. VCMP ™ assigns a specific share of the hardware resources for each BIG-IP instance, or guest vCMP (Guest). Each Guest you create behaves as a separate, independent BIG-IP device, having its own CPU, memory, and disk space. Each Guest also has its own configuration file, log files, and Kernel version.

Virtualized Clustered Multiprocessing (vCMP) is a feature of the BIG-IP® system that allows you to run multiple instances of BIG-IP software on a single hardware platform. VCMP ™ assigns a specific share of the hardware resources for each BIG-IP instance, or guest vCMP (Guest). Each Guest you create behaves as a separate, independent BIG-IP device, having its own CPU, memory, and disk space. Each Guest also has its own configuration file, log files, and Kernel version.

VCMP ™ is built on CMP F5 Networks technology. VCMP allows cluster members (ie Slots within a chassis or Microkernel Traffic Management - TMM instances on a device) to work together to form a distributed, coherent, traffic-processing system to share the traffic. VCMP takes this a step further by allowing you to build and run virtualized BIG-IP modules using a built-in hypervisor based on virtualization standards.

This creates a guest (Guest) in bridge mode (Briged). When creating a Guest, if you get an error message about / shared / vmdisks see the disk space. VCMP needs 24,354 MB of additional space. You can or should delete existing virtual disks until you have freed up 24,354 MB of disk space.

       1. **  
1\. Connect to the BIG-IP Chassis (Host) and access with the appropriate user credentials and password;**
       2. On the main tab, click VCMP and Guest List, and then click Create.

  
(Figure_01)

          3. From the list of properties, select Advanced;

  
(Figure_02)

             4. In the Name field, type a name for the Guest; 

# 

  
(Figure_03)

                5. In the Host Name field, enter the host name of the BIG-IP system. Be sure to assign a fully qualified domain name (FQDN). If you assign a name that is not an FQDN, the system may display an error message. If you leave this field blank, the system assigns the name localhost.localdomain;
                   5.   
(Figure_04)

                   6. Choose the amount of Colors (Processors) that will be used by Slost; 
                      1.                       4.   
(Figure_05)

                      7. Choose the number of Slots allocated in the equipment (in this case the equipment only has one blade); 
                         6.   
(Figure_06)

                         8. Choose the Minimum Slots Number. When choosing more than one slot, in case a slot fails, the VCMP will continue to function; 
                            7.                             8.   
(Figure_07)

                            9. From the Number of slots list, select either single slot or all slots. This causes the Guest to reside in one slot or can span all slots. Note that once you set up a Guest to span all slots, you can not change this value later for a single slot unless you first change the Guest state to Configure. 
                               8.   
(Figure_08)

                               10. In the IP Address field, enter a unique management IP address that you want to assign to the Guest. You will use this IP address to access the Guest when you want to manage a module running within the Guest; 
                                  10.   
(Figure_09)

                                  11. In the Network mask field, type the network mask for the IP address of the cluster. 
                                     11.   
(Figure_10)

                                     12. In the Management Path field, type a gateway address for the IP address of the cluster. 
                                        12.   
(Figure 11)

                                        13. From the initial image list, select an ISO image file for the TMOS® installation and any licensed BIG-IP modules for the guest virtual disk (Guest). If necessary, choose HotFix for the System version. 
                                           13.   
(Figure_12) 

                                           1. (Figure_13) 

                                           14. From the virtual disk list, keep the default value of None. The BIG-IP system creates a virtual disk with a default name (the name of the Guest plus the .img string, such as guestA.img). Note that if a loose virtual disk file with this default name already exists, the system displays a message. You must manually attach the virtual disk. You can do this by using the tmsh command-line interface. 

  
(Figure_14)

                                              15. To configure the VLAN list, select an internal and external VLAN name from the available box, and using the Move button, move the VLAN names to the Selected box. 
                                                 1.   
(Figure_15) 

                                                 13.                                                     14.                                                        15.                                                        16.                                                     15.                                                  16.   
16\. From the Required State list, select Provisioned. This allocates all the necessary resources for the Guest, such as CPU cores, virtual disk, and so on. 
                                                    16.   
(Figure 16)

                                                    17. Click Finish. 
                                                       17.   
(Figure 17)

refer here: 

**https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/vcmp-administration-viprion-13-1-0/7.html**

**At the same time you can also check**

# K14218: vCMP guest memory/CPU core allocation matrix

https://my.f5.com/manage/s/article/K14218

# K14088: vCMP host and compatible guest version matrix

https://my.f5.com/manage/s/article/K14088

# K33853204: How to change the core allocation for vCMP guests when there is not enough cores left?

https://my.f5.com/manage/s/article/K33853204

Please let me know if you still face issues.

HTH

F5 Design Engineer

🙏🙏




Hi

Thank you for giving advice

i didnt provision state just back to configure > add cpu core > Deployed

based on https://techdocs.f5.com/en-us/bigip-14-0-0/vcmp-for-appliance-models-administration-14-0-0/cpu-core-upgrade-for-deployed-guests.html, 

maybe that why guest back to default configure

i want to ask every add or delete resource should we provision state before deploy ?

Thanks

ok, i see

thanks for the information

maybe that why after change cpu core and upgrade on vcmp host, that why on the host allocation cpu core back to existing

Thanks