Manual Chapter : Make an urgent LTM deployment

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 7.1.0
Manual Chapter

Make an urgent LTM deployment

If you need to make an urgent change, you can skip the
Evaluate configuration changes
task and immediately deploy changes to the BIG-IP device. The system still validates changes to configuration objects; if there are critical errors, the deployment does not proceed. But you can avoid the task of creating an evaluation and viewing the changes and get right to deploying your changes.
F5 does not generally recommend making a deployment without evaluating the changes first. However, in situations where you need to deploy changes as quickly as possible, you can deploy the changes right away. The urgent deployment work flow skips the task of creating an evaluation, which speeds up the process of deploying your changes.
  1. At the top of the screen, click
    Deployment
    .
  2. Under
    EVALUATE & DEPLOY
    , select
    Local Traffic & Network
    .
    The screen opens a list of LTM evaluations and deployments that have been created on this device.
  3. Under Deployments, click
    Create
    .
    The New Deployment screen opens.
  4. Type a name
    Name
    for the deployment task you are creating.
  5. Type a brief
    Description
    for the deployment task you are creating.
  6. For the
    Source
    setting, select what you want to deploy.
    • To deploy your changes to the managed device, select
      Current Changes
      .
    • To deploy the object settings from a stored snapshot, select
      Existing Snapshot
      , then choose the snapshot you want to use.
  7. Determine the
    Source Scope
    ; that is, choose whether you want to deploy all of the changes from the selected source, or specify which changes to deploy (either
    All Changes
    or
    Partial Changes
    ).
    If you choose to do a partial deployment, the screen displays additional controls.
    If you select
    All Changes
    , skip the rest of this step.
    1. If you want to deploy changes only to the selected objects, for
      Supporting Objects
      , clear the
      Include
      check box. It is almost always best to deploy changes to the associated objects, as well.
      The objects that you manage using BIG-IQ depend on associations with other, supporting objects. These object associations form relationship trees that are sometimes quite complex. Generally, when you deploy a change to a managed object, it is a very good idea to include these supporting objects in the deployment. This diagram illustrates a typical relationship tree for a Network Services managed object. For Local Traffic or Web Application Security objects, the trees are equally complex and just as vital to include.
      Network Services supporting objects tree
    2. For
      Method
      , consider one more time how you want to deploy these changes.
      • If you want to review the changes, click
        Create evaluation
        .
      • To make the changes right now, click
        Deploy immediately
        .
    3. Under Available, select the object type for which you want to deploy changes.
    4. From the list of objects, select the ones that you want to deploy, and move them to the Selected list.
      If you include objects in an deployment that have not been changed, the unchanged objects are not deployed to your BIG-IP device. Only objects that have been changed are deployed.
    5. If you want to include additional object types in this deployment, repeat the last two sub-steps (steps 3 and 4) for each object type.
    6. If you add an object to the deployment and then change your mind, you can move it back to the Available list.
    7. Under Target Device(s), click
      Find Relevant Devices
      .
      The objects you select for deployment determine which devices display in the
      Available
      list. You cannot deploy a device-specific object (like a pool) to a device on which it does not already exist. You can deploy a shared object (like a profile) to a device on which it does not exist, as long as the shared object is referenced by an object on that device. For example, consider a device (
      BIG-IP1
      ) with a virtual server (
      Virt1
      ). If you add a profile named
      Pro1
      to
      Virt1
      , then
      BIG-IP1
      will appear in the list of devices that you can deploy changes to.
      BIG-IQ lists all devices to which you can deploy the selected objects.
    8. From the list of relevant devices, select the devices that you want to deploy these changes to, and move them to the Selected list.
  8. If you selected
    All Changes
    , there are a couple more options to specify.
    1. Specify whether you want unused objects to be deleted from the BIG-IP devices to which you are deploying changes. If you do not want unused objects to be deleted, select
      Keep Unused Objects
      .
      To understand what an unused object is, consider the following example:
      There are two address lists on the BIG-IP device to which you are about to deploy changes (
      AddressList-a
      and
      AddressList-b
      ).
      • AddressList -a
        is referenced by a policy that is in turn referenced by a firewall context.
      • AddressList-b
        is not referenced (directly or indirectly) by any objects.
      If you leave
      Remove Unused Objects
      (the default) selected, then when you deploy changes to the BIG-IP device,
      AddressList-b
      is deleted. If you don’t want it deleted, select
      Keep Unused Objects
      .
    2. For
      Method
      , consider one more time how you want to deploy these changes.
      • If you want to review the changes, click
        Create evaluation
        .
      • To make the changes right now, click
        Deploy immediately
        .
    3. From the Available list under Target Devices, select the devices to which you want to deploy changes, and move them to the Selected list.
      If you deploy changes to a device in a DSC cluster, you must make changes to all devices in the cluster before you can create the evaluation.
  9. Click
    Deploy
    to start deployment.
    A confirmation screen notifies you that you are about to trigger a deployment.
  10. Click
    Deploy
    again to deploy the changes to your device.