1. Platform Preparation and Installation Guide
  2. Public Cloud Platforms
  3. Create and Deploy on OCI
  4. Migrating to an Optimized3.Flex Machine Shape

Migrating to an Optimized3.Flex Machine Shape

The SBC supports machine migration to and from supported versions on OCI VM.Optimized3.Flex shapes.

The table lists the supported standard shapes that you can migrate to their respective VM.Optimized3.Flex shapes. Changing instance type from VM.Standard2.X to VM.Optimized3.Flex is supported only when both the instances have the same number of OCPUs, the same amount of memory, the same number of vNICs attached, and the same type of networking mode (SRIOV).

From Instance Type To Instance Type OCPUs Memory
VM.Standard2.4 VM.Optimized3.Flex-Small 4 60
VM.Standard2.8 VM.Optimized3.Flex-Medium 8 120
VM.Standard2.16 VM.Optimized3.Flex-Large 16 240

The SBC supports this instance type modification for both standalone and HA deployments. Follow the steps below to migrate a standalone VM from the VM.Standard2.X shape to the VM.Optimized3.Flex shape .

  1. Upgrade the software on VM.Standard2.X shape to the vSBC version that supports VM.Optimized3.Flex shapes.
  2. After upgrading the software, stop your VM from the OCI console.

    The image below depicts a VM.Standard2.4 instance’s Shape Configuration before migration.

    This image depicts how you identify an OCI machine shape.

    Stop your instance by clicking the “stop” button.

    This image depicts how you stop an OCI machine.
  3. Navigate to Edit, Edit Shape, and select the target shape name (Intel, VM.Optimized3.Flex).This image depicts how you edit an OCI machine shape.
  4. Set the same number of OCPUs and amount of memory as that of standard shape, then Save changes. This image shows where you select OCI machine criteria.
  5. Start your migrated vSBC machine.

Migrating an HA Pair

Follow the steps below to migrate an HA pair of VM.Standard2.X instances to VM.Optimized3.Flex shapes. Both the starting and target instances of the HA pair must be the same instance type, with the same number of OCPUs, the same amount of memory, and the same networking type (SRIOV).

  1. Upgrade the software on both nodes of VM.Standard2.X shapes to the vSBC version that supports VM.Optimized3.Flex shapes.
  2. From OCI console, stop your standby VSBC.
  3. Navigate to Edit, Edit Shape, and select the target shape name (VM.Optimized3.Flex).
  4. Set number of OCPUs and amount of memory to be the same as that of standard shape and save your changes.
  5. Start your migrated standby vSBC machine.
  6. After startup, check that the original active and standby are in the same roles and are synchronized.
  7. From OCI console, stop your active vSBC. The vSBC over the new Flex VM takes the role as new Active.
  8. Navigate to Edit, Edit Shape, and select the target shape name (VM.Optimized3.Flex).
  9. Set the number of OCPUs, the amount of memory (the same as that of standard shape) and save your changes
  10. Start the instance. This instance takes the new standby role.
  11. Verify the HA roles and that the systems are synchronized.

If you want to change the number of forwarding cores in your deployed VM.Optimized3.Flex shape, change the active instance first and reboot it after the configuration fully synchronizes. Once the first VM comes up, it takes the role as “Standby”. Reboot the newly active vSBC for the forwarding core count changes to come into effect on both instances of your HA pair.