Manual Chapter : Migration of Devices Running the Same Software Version

Applies To:

Show Versions Show Versions

BIG-IP LTM

  • 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.2, 14.1.0, 14.0.1, 14.0.0
Manual Chapter

Migration of Devices Running the Same Software Version

About migrating devices running the same software version

What is device migration?

Device migration
enables you to replace the devices in a BIG-IP device group running software version 12.1.3, or later, with newer devices running the same software version. It enables you to take an existing configuration on a device group's source device and easily replicate it on a target device.
Source devices in a device group
Source devices in a device group

Supported platforms

Supported source and target platforms include appliances, VIPRION® platforms, virtual edition (VE) devices, and vCMP® guests.

Configuration Dependencies

Migration to newer devices running software version 12.1.3, or later, ignores the following configuration objects. If your configuration includes dependencies on any of these objects, you must reconfigure them on the new device before you load the UCS file onto that device.
You must reconfigure the following objects on the new target device to use the same names as the objects on the source device, before you load the UCS file onto that device
  • Interfaces
  • Interface bundles
  • Management IP address
  • Management route

Migration of a device group running the same software version

When you migrate the source devices in a device group running BIG-IP software version 12.1.3, or later, to new target devices running the same BIG-IP software version, the following sequence of steps applies. This sequence migrates a device group composed of source devices 1 and 2 to a device group composed of new target devices 1 and 2.
  • For a device group, migration functionality reestablishes the device group with the target devices when you load an archive onto the second target device.
  • During migration, do not make any additional configuration changes. Reconfiguration during migration can cause unexpected behavior.
  • Devices run different software versions during migration, preventing normal config sync functionality until migration completes.

Step 1. Migrate source device 1 to target device 1.

  1. Prepare each source device in the device group.
  2. Create and save an archive for each device.
  3. Download an archive file for each device.
  4. Force source device 1 offline, and observe that source device 2 becomes active.
  5. Shut down source device 1.
  6. Install target device 1.
  7. Prepare target device 1.
  8. Upload the source device 1 archive, and load the archive onto the target device 1.
Migrated target device 1 in a device group
Migrated target device 1 in a device      group

Step 2. Migrate source device 2 to target device 2.

  1. Force source device 2 offline, and observe that target device 1 becomes active.
  2. Shut down source device 2.
  3. Install target device 2.
  4. Prepare target device 2.
  5. Upload the source device 2 archive, and load the archive onto the target device 2, reestablishing the device group.
Migrated target device 1 and target device 2 in a device group
Migrated target device 1 and target device      2 in a device group

About migrating to a target device

You can easily take an existing configuration on a source device (appliance, VIPRION®, VE, or vCMP® guest) and replicate it on a target device (appliance, VIPRION, VE, or vCMP guest). The migration process includes the following steps:
  1. Prepare the source device
  2. Archive and download the UCS file
  3. Shut down the source device
  4. Set up the target device
  5. Upload the archived UCS file
  6. Load the archived UCS file onto the target device
For a device group, the migration functionality reestablishes the device group with the target devices when you load an archive onto the second target device.

Preparing a source device

You can use these steps to prepare a source device for migration to a target device.
  1. Open the Traffic Management Shell (
    tmsh
    ).
    tmsh
    This starts
    tmsh
    in interactive shell mode, and displays the
    tmsh
    prompt:
    (tmos)#
    .
  2. Set the device master key to prompt for a password.
    (tmos)# modify sys crypto master-key prompt-for-password
    This master key password is used when configuring the source and target devices. You will want to remember or safely record it for configuration of source and target devices.
  3. On the Main tab, click
    Device Management
    Overview
    .
    In the Devices area of the screen, in the Sync Status column, view the sync status of each device:
    • If all devices show a sync status of green, the configurations of all device members are synchronized, and you do not need to perform a config sync operation.
    • If any device shows a sync status of Changes Pending, you must synchronize the configuration on that device to the other members of the device group.
    A status of
    Changes Pending
    for a device indicates that the device contains recent configuration changes that have not yet been synchronized to the other members of the device group.
  4. For each device, sync the configuration:
    1. On the Main tab, click
      Device Management
      Overview
      .
    2. In the Device Groups area of the screen, in the Name column, select the name of the relevant device group.
      The screen expands to show a summary and details of the sync status of the selected device group, as well as a list of the individual devices within the device group.
    3. In the Devices area of the screen, in the Sync Status column, select a device.
    4. From the
      Sync
      options list, select a sync option.
      Option
      Description
      Sync Device to Group
      Select this option to synchronize the configuration of the selected device to the device group.
      Sync Group to Device
      Select this option to synchronize the configuration of the device group to the selected device.
    5. Click
      Sync
      .
The source device is prepared for migration to a target device

Create and save an archive using the Configuration utility

You can use the BIG-IP Configuration utility to create and save archives on the BIG-IP system.
Any UCS file that you create includes the host name of the BIG-IP system as part of the data stored in that file. Later, when you specify this UCS file while restoring configuration data to a BIG-IP system, the host name stored in this UCS file must match the host name of the system to which you are restoring the configuration data. Otherwise, the system does not fully restore the data. Also, if your configuration data includes SSL keys and certificates, make sure to store the archive file in a secure environment.
  1. Force the source device to the offline state.
    1. On the Main menu, click
      Device Management
      Devices
      .
    2. Click the name of the source.
      The device properties screen opens.
    3. Click
      Force Offline
      .
      The source device changes to the offline state.
      Once the source device changes to the offline state, ensure that traffic passes normally for all active traffic groups on the other devices.
      When
      Force Offline
      is enabled, make sure to manage the system using the management port or console. Connections to self IP addresses are terminated when
      Force Offline
      is enabled.
  2. On the Main tab, click
    System
    Archives
    .
    The Archives screen displays a list of existing UCS files.
  3. Click
    Create
    .
    If the
    Create
    button is unavailable, you do not have permission to create an archive. You must have the Administrator role assigned to your user account.
  4. In the
    File Name
    field, type a unique file name for the archive.
    F5 recommends that the file name match the name of the BIG-IP system. For example, if the name of the BIG-IP system is
    bigip2
    , then the name of the archive file should be
    bigip2.ucs
    .
  5. To encrypt the archive, for the
    Encryption
    setting, select
    Enabled
    .
    If the
    Encryption
    setting is unavailable, you must configure the
    Archive Encryption
    setting located on the Preferences screen.
  6. To include private keys, for the
    Private Keys
    setting, select
    Include
    .
    Make sure to store the archive file in a secure environment.
  7. Click
    Finished
    .

Downloading a copy of an archive to a management workstation

You can use the Configuration utility to download a copy of an archive to a management workstation. This provides an extra level of protection by preserving the configuration data on a remote system. In the unlikely event that you need to restore the data, and a BIG-IP® system event prevents you from accessing the archive in the BIG-IP system directory, you still have a backup copy of the configuration data.
  1. For the
    Archive File
    setting, click the
    Download: <filename>.ucs
    button.
    A confirmation screen appears.

Shutting down a source device

Before you shut down a source device during the migration process, download a copy of the archive file to a management workstation.
You can shut down a BIG-IP source device, as needed, when migrating a configuration to a new target device.
  1. Complete one of these steps.
    • For BIG-IP software version 11.x.x, type
      halt
      . When a message appears indicating that the device is halted, turn off the power.
    • For BIG-IP software version 12.0.0, and later, type
      shutdown
      .
The BIG-IP source device is shut down.

Installing a target device

You can install a target device when migrating from an older source device to a new target device.
  1. Install and license the new target device in accordance with the platform guide installation instructions for the device.
    When installing the new target device, use the Configuration utility to specify the same IP address, Netmask, and Management Route as the source device.
  2. Provision the target device according to the provisioning of the source device.
The target device is installed, licensed, and provisioned.

Preparing a target device for migration

You can prepare a target device for migration.
  1. Open the Traffic Management Shell (
    tmsh
    ).
    tmsh
    This starts
    tmsh
    in interactive shell mode, and displays the
    tmsh
    prompt:
    (tmos)#
    .
  2. Set the device master key to prompt for a password.
    (tmos)# modify sys crypto master-key prompt-for-password
    This master key password is used when configuring the source and target devices. You will want to remember or safely record it for configuration of source and target devices.
  3. Save the configuration.
    (tmos)# save sys config
The target device is prepared for migration.

Uploading an archive from a management workstation

If you previously downloaded a copy of an archive to a management workstation, you can upload that archive to the BIG-IP® system at any time. This is useful when a BIG-IP system event has occurred that has caused the archive stored on the BIG-IP system to either become unavailable or corrupted.
You can use the Configuration utility to upload a copy of an archive stored on a management workstation.
When you upload a copy of an archive, you must specify the exact path name for the directory in which the downloaded archive copy is stored.
  1. Click
    Upload
    .
    The Upload screen opens.
  2. For the
    File Name
    setting, click
    Browse
    .
  3. For the
    Options
    setting, select the
    Overwrite existing archive file
    check box if you want the BIG-IP system to overwrite any existing archive file.
    The BIG-IP system overwrites an existing file with the uploaded file only when the name of the archive you are uploading matches the name of an archive on the BIG-IP system.
  4. Click
    Upload
    .
    The specified archive is now uploaded to the
    /var/local/ucs
    directory on the BIG-IP system.

Loading an archive using tmsh

Migration to newer devices running software version 12.1.3, or later, ignores the following configuration objects. If your configuration includes dependencies on any of these objects, you must reconfigure them on the new device before you load the UCS file onto that device.
You must reconfigure the following objects on the new target device to use the same names as the objects on the source device, before you load the UCS file onto that device
  • Interfaces
  • Interface bundles
  • Management IP address
  • Management route
You can use
tmsh
to load and migrate data from an archive file. The
/var/local/ucs
directory is the only location on the BIG-IP system from which you can migrate an archive. If no archive exists in that directory, then you cannot migrate configuration data.
The host name stored in the archive file must match the host name of the target BIG-IP device; otherwise, the system does not fully migrate the data.
  1. Connect to the system using the serial console.
  2. Open the Traffic Management Shell (
    tmsh
    ).
    tmsh
    This starts
    tmsh
    in interactive shell mode, and displays the
    tmsh
    prompt:
    (tmos)#
    .
  3. Load the configuration contained in a specified UCS file.
    (tmos)# load sys ucs my_file.ucs platform-migrate
    When you load the configuration for a second device in a device group, the migration functionality reestablishes the device group.
    The UCS is loaded into the running configuration of the device.