Manual Chapter : Migrating a Blade from One Chassis Partition to Another

Applies To:

  • F5OS-C

    2.0.0

back-action VELOS Systems: Migrating a Blade from One Chassis Partition to Another

Updated Date: 05/14/2026

Migrating a Blade from One Chassis Partition to Another

To expand the capacity of a chassis partition, you can migrate a blade from one chassis partition to another using the VELOS system controller and chassis partition webUIs.

Note: Before you can migrate a blade from one chassis partition to another, the physical blades must already be installed. See the Platform Guide: VELOS CX Series.

To remove a blade from a chassis partition, you must first remove any VLANs from the interfaces on the blade being removed. You must also remove ports from existing LAGs and either delete or move tenants from the slot.

If there are interfaces on the blade that are configured with VLANs, you must remove the VLANs from the interfaces on the blade being removed from the chassis partition. Removing other network configurations from the blade is optional.

  1. Log in to the VELOS chassis partition webUI using an account with admin access.

  2. On the left, click Network Settings > VLANs.

    The screen shows VLANs that are configured for that chassis partition.

  3. Select the VLAN from the table and click Delete.

Next, you remove ports from existing LAGs.

You must remove the blades from any existing link aggregation groups (LAGs). The LAGs will persist, but can only have members that reside on blades that will stay in the chassis partition.

  1. Log in to the VELOS chassis partition webUI using an account with admin access.

  2. On the left, click Network Settings > LAGs.

    The screen shows LAGs that are configured.

  3. Click the LAG name.

    The Edit LAG screen displays.

  4. For Configured Members, clear the check box for the ports you are removing from the chassis partition.

  5. Click Save.

The Configured Members column in the LAGs table is empty.

Next, you move tenants to other blades or delete them.

You must either delete any tenants that reside on the chassis partition, or reconfigure them so they only reside in slots that will remain in the chassis partition. No active tenants can reside on the chassis partition.

  1. To delete the tenants:

    1. Log in to the VELOS chassis partition webUI using an account with admin access.

    2. On the left, click Tenant Management > Tenant Deployments.

      The Tenant Deployments screen displays showing the existing tenant deployments and associated details.

    3. Select the check box next to the tenant to be removed and click Delete.

  2. To redeploy the tenants:

    1. Log in to the VELOS chassis partition webUI using an account with admin access.

    2. On the left, click Tenant Management > Tenant Deployments.

      The Tenant Deployments screen displays showing the existing tenant deployments and associated details.

    3. Click the name of the tenant deployment you want to modify.

      The Edit Tenant Deployment screen displays.

    4. Change the State to Provisioned.

    5. For Allowed Slots, select the slot to which you want to redeploy the tenant.

    6. Change the State to Deployed.

    7. Click Save.

Next, you remove the slots from the chassis partition.

You must remove any slots assigned to the chassis partition.

  1. Log in to the VELOS system controller webUI using an account with admin access.

  2. On the left, click Chassis Partitions.

    The Chassis Partitions screen displays.

  3. From the chassis partition list, select the chassis partition that you want to edit.

  4. Click Edit.

  5. Remove slots identified for removal from the chassis partition.

  6. Click Save.

Next, if you are adding the blade to a different chassis partition, you create the new chassis partition or edit an existing partition.

If you choose to add the removed blade to a different chassis partition, you must first create a new chassis partition or modify and existing one. VLANs and LAGs must then be reassigned, and tenants must be created or expanded.

You can create a new chassis partition to which you can add the blade or add the blade to an existing chassis partition.

  1. To create a new chassis partition:

    1. Log in to the VELOS system controller webUI using an account with admin access.

    2. On the left, click Chassis Partitions.

      The Chassis Partitions screen displays a graphical view of the VELOS chassis, which shows available slots, which slots contain blades, how many chassis partitions currently exist, which slots are associated with the chassis partition, and whether the chassis partitions are enabled or disabled. You select slots for the chassis partitions from this graphic.

    3. If all slots are assigned to the default chassis partition, the Create button is unavailable. Before you can create a new chassis partition, you first need to select one or more slots and remove them from the default chassis partition.

    4. Click Create.

    5. Enter the relevant information to create the chassis partition. For more information, see VELOS Systems: Administration and Configuration at Documentation - F5OS-C and VELOS.

  2. To edit an existing chassis partition:

    1. Log in to the VELOS system controller webUI using an account with admin access.

    2. On the left, click Chassis Partitions.

    3. From the chassis partition list, select the chassis partition that you want to edit.

    4. Click Edit.

    5. Adjust the settings as needed.

    6. Click Save.

Next, you add the blade to the chassis partition.

For the system to use a blade, you must first add the blade to a chassis partition

  1. Log in to the VELOS system controller webUI using an account with admin access.

  2. On the left, click Chassis Partitions.

    The Chassis Partitions screen displays a graphical view of the VELOS chassis, which shows available slots, which slots contain blades, how many chassis partitions currently exist, which slots are associated with the chassis partition, and whether the chassis partitions are enabled or disabled.

  3. From the chassis partition list, select the chassis partition that you want to edit.

  4. Click Edit.

  5. Add slots to the chassis partition.

  6. Click Save.

Next, you configure network settings.

You can now reconfigure network settings.

  1. Log in to the VELOS chassis partition webUI using an account with admin access.

  2. On the left, click Network Settings > VLANs.

    The screen shows VLANs that are configured for that chassis partition.

  3. Reassign VLANs.

  4. On the left, click Network Settings > LAGs.

    The screen shows LAGs that are configured.

  5. Reassign LAGs.

  6. Configure any other desired network settings.

    For more information, see VELOS Systems: Administration and Configuration at Documentation - F5OS-C and VELOS.

Next, you create new tenants or expand existing tenants.

You can create new tenants or expand existing tenants.

  1. Log in to the VELOS chassis partition webUI using an account with admin access.

  2. On the left, click Tenant Management > Tenant Deployments.

    The Tenant Deployment screen displays showing the existing tenant deployments and associated details.

  3. Add a tenant deployment or modify an existing tenant deployment.

    For more information, see VELOS Systems: Administration and Configuration at Documentation - F5OS-C and VELOS.

Before you perform an upgrade, it is a good idea to save and export a backup of the tenant configuration using that tenant’s backup mechanism. For BIG-IP tenants, you can create a UCS file from the tenant CLI to maintain tenant configuration.

You can create a UCS file to maintain tenant configuration from the tenant CLI. For more information, see

  1. Create a backup for each running tenant.

    tmsh save sys ucs <*filename*>

  2. Move these backup files to a safe location off of the tenant:

    • /config/bigip.conf
    • /config/bigip_base.conf
    • /config/bigip_user.conf (optional) If you perform a clean installation, the tenant will be formatted.

    Note: Consider naming the files to associate them with the appropriate tenants.

After the migration completes, restore the BIG-IP tenant configuration.