Manual Chapter : Resolving Conflicts for Devices in a Silo

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 7.1.0
Manual Chapter

Resolving Conflicts for Devices in a Silo

Overview of the in-silo LTM conflict resolution options

To resolve LTM object conflicts from a silo, you first identify the conflicts. Then you either revise or rename the conflicting objects in the silo.
Identify/resolve LTM conflicts in the silo
Workflow for changing object settings on a managed device
This figure illustrates the work flow for using a silo to resolve LTM object conflicts triggered by importing a BIG-IP device. Resolving conflicts within the silo is the second step in this process.

Identify LTM object conflicts

Once you have imported a device to a silo, the next task is to determine which objects are triggering conflicts. To find these conflicts, you compare the settings for the LTM objects you imported to a silo with the settings for objects with the same name that are currently in BIG-IQ working configuration. You can analyze the details of each conflict and determine how you want to respond.
  1. At the top of the screen, click
    Devices
    , then, on the left, click
    BIG-IP DEVICE SILOS
    .
    The screen displays the list of silos defined on this device.
  2. Click the name of the silo that you want to analyze for conflicts.
    BIG-IQ opens the Silo Properties screen.
  3. From Target Silo, select the name of the silo that you want to compare with the current silo and click
    Compare Silos
    .
    Most often, you are trying to compare the settings in the current silo with the settings in working configuration. Objects in working configuration reside in a silo named
    Default
    .
    BIG-IQ displays a list of objects that have configuration settings that conflict with the settings for that object in the silo you chose for comparison.
  4. For each conflicting object, decide how you want to resolve the conflict.
    For most conflicts, you make note of your decision and perform the resolution in a later step.
    1. Select the object to display a differences panel at the bottom of the screen.
      The differences panel displays JSON representations of both versions of the object. The version in the current silo is on the left.
    2. Scroll through the JSON representation of the object configuration to make note of the differences. As you review each conflict, make a note of how you want to resolve it.
      Except for Renaming a non-default object, you do not choose that option here. Instead, make a note of your decision so you can carry it out in one of the tasks that follow this one.
      Use BIG-IP
      If the settings in the current silo are the ones you want to use, make a note of the object name.
      Use BIG-IQ
      If the settings in the target silo are the ones you want to use, make a note of the object name.
      Rename a non-default object
      If you find conflicts for a non-default object and determine that you need an object that uses the settings currently in the BIG-IQ working configuration and an object that uses the settings in the Silo, then use the
      New Name
      field to rename the version in the silo. BIG-IQ creates a new object, using the name you specified, and deletes the version in the silo. This resolves the conflict, because when you deploy these changes and re-import the device, the new object is unique on the BIG-IQ.
      If you rename an object that is referenced by an iRule, you need to make manual revisions to the iRule so that it references the new object.
      Default objects that you need to change
      If you find conflicts for a default object and determine that you need an object that uses the settings currently in the BIG-IQ working configuration, but you also need an object that uses the settings in the Silo, then make a note of the object name. You can create a copy of the object in the silo using the default object as a template. Again, when you deploy these changes and re-import the device, the new object is unique on the BIG-IQ.
      Revise
      If you determine that you need some settings from the silo version and some settings from the working configuration version, then revise the version that is closest to what you need. Make a note of which version is closest and then list the objects that you need to revise. Refer to
      Revise LTM objects to resolve silo conflicts
      on
      support.f5.com
      for details.
  5. When you finish reviewing the object configuration conflicts in the silo, click
    Save & Close
    .
BIG-IQ attempts to rename the objects that you typed in a new name for. If any rename attempts were unsuccessful, an error message displays to let you know. Make a note of these objects and add the names to the list of objects that you need to revise in-silo.
Use the notes created in the step 4 to determine what you need to do next.
  • For default objects that you want to rename, refer to
    Make a copy of a default object
    on
    support.f5.com
    .
  • For objects you want to revise, refer to
    Revise LTM objects to resolve silo conflicts
    on
    support.f5.com
    .
  • Hold on to the list of names and actions for the remaining objects you noted in step 4. For these objects, all that remains is to select the correct resolution option when you re-import the device. For details, refer to
    Add a BIG-IP device after removing it from a silo
    on
    support.f5.com
    .

Revise LTM objects to resolve silo conflicts

Resolving LTM object conflicts by changing the settings for an existing object use the same screens and essentially the same steps as any other LTM object management task. The only difference is that you need to identify the correct silo in which to create or revise the object.
For example, let's assume, that you are revising conflicts in a profile named
http
. To resolve these conflicts, you created a silo (
MySilo
). When you compared the settings for the profile in your silo with the settings in working configuration, you found that there were only six parameter settings with conflicts. Four of the settings are correct in the silo and two are correct in BIG-IQ working configuration.
  • The settings for the
    Allow Truncated Redirect
    ,
    Pipeline Action
    ,
    Unknown Method
    and
    Redirect Rewrite
    parameters are correct in the silo.
  • The settings for the
    Request Chunking
    , and
    Response Chunking
    parameters are correct in BIG-IQ working configuration.
You determine that the quickest way to resolve the conflicts is to edit the object settings in the silo. The steps you follow should go something like this:
  1. At the top of the screen, click
    Configuration
    , then, on the left, click
    LOCAL TRAFFIC
    Profiles
    .
    The screen displays the list of profiles defined on this device.
    If you select the check box for a profile, you can either delete or clone it. You can also view details about other configuration objects to which this profile relates.
  2. In this example, scroll through the list of profiles to find the profile named
    http
    that displays the silo name
    MySilo
    , then click on the profile name.
  3. Revise the values for
    Request Chunking
    , and
    Response Chunking
    so that they match the settings in working configuration, and then click
    Save & Close
    .
The settings for the profile named
http
in the silo
MySilo
are now correct for this profile.
To finish this resolution work flow you need to:
  1. Deploy these changes back to the device you imported it from.
  2. Remove the device from the silo.
  3. Import the device back to the BIG-IQ, and choose Use BIG-IP to resolve the remaining conflicts for this profile.
  4. When the import is complete, all six of the parameters that had conflicts will have the values you intended.

Make a copy of a default LTM object

BIG-IQ does not support renaming or deleting default shared objects (like monitors or profiles). Instead, if you need an object that primarily uses the default object settings, but also uses settings you've modified for your needs, you can create a new object and use the default object as the parent.
These steps detail how to make a copy of the default HTTP profile named
http
. Assume for this example that you imported a BIG-IP device and created a silo named
MySilo
so you could resolve conflicts. When you compared the silo to the BIG-IQ working configuration, you noted that the settings for the version of this profile in the silo were useful. But you determined that you still need the default settings for this profile. You want both profiles, so you decide to create a copy of the profile.
  1. At the top of the screen, click
    Configuration
    , then, on the left, click
    LOCAL TRAFFIC
    Profiles
    .
    The screen displays the list of profiles defined on this device.
  2. Click
    Create
    .
    The New Profiles screen opens.
  3. Type a
    Name
    for the LTM profile you are creating.
    You probably want to name the profile so that it is obvious that it's a copy of the one it will replace. So maybe in this case, you would type
    http-new
    or something similar.
  4. For
    Silo
    , select
    MySilo
    .
    This tells BIG-IQ to create this new profile inside the silo you are using to resolve your conflicts.
  5. For
    Partition
    , type the name of the BIG-IP device partition on which you want to create the profile.
  6. For
    Type
    select
    Profile HTTP
    .
    The
    Parent Profile
    field along with the additional properties required to define the selected profile type displays.
  7. From
    Parent Profile
    , select
    http
    .
    The parent profile you select determines the value of the profile parameters for this profile. If you do not override these values, the parent profile values propagate to this profile. If you do override a value, the profile stops inheriting values from the parent profile. For this reason, it's best practice to only override the parameters that you want to change. If you select
    Override All
    , and then at some point in the future, parameters in the parent profile are revised, those changes won't propagate down to this profile.
    A number of additional settings display, specifying the parameters associated with the http profile you selected as parent. There are two controls for each field. The first one (a check box) controls whether you want to override the inherited value for that field. The second control (the type varies by field) sets the value you want for the parameter.
  8. For each setting that needs to change, select the check box in the
    Override
    column and then type or select the correct value.
  9. Select
    Save & Close
    .
Next, you need to deploy these changes back to the device that triggered the conflict, and then reimport that device. When you choose resolution options on the Resolve Import Conflicts screen, select Use BIG-IQ for the default profile named
http
.