Applies To:Show Versions
BIG-IQ Centralized Management
- 8.2.0, 8.1.0, 8.0.0, 7.1.0
Resolving Conflicts for Devices in a Silo
Overview of the in-silo LTM conflict resolution options
Identify LTM object conflicts
- At the top of the screen, clickDevices, then, on the left, clickBIG-IP DEVICE SILOS.The screen displays the list of silos defined on this device.
- Click the name of the silo that you want to analyze for conflicts.BIG-IQ opens the Silo Properties screen.
- From Target Silo, select the name of the silo that you want to compare with the current silo and clickCompare 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 namedDefault.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.
- 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.
- 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.
- 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 theNew Namefield 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.
- 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 toRevise LTM objects to resolve silo conflictsonsupport.f5.comfor details.
- When you finish reviewing the object configuration conflicts in the silo, clickSave & Close.
- For default objects that you want to rename, refer toMake a copy of a default objectonsupport.f5.com.
- For objects you want to revise, refer toRevise LTM objects to resolve silo conflictsonsupport.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 toAdd a BIG-IP device after removing it from a siloonsupport.f5.com.
Revise LTM objects to resolve silo conflicts
- The settings for theAllow Truncated Redirect,Pipeline Action,Unknown MethodandRedirect Rewriteparameters are correct in the silo.
- The settings for theRequest Chunking, andResponse Chunkingparameters are correct in BIG-IQ working configuration.
- At the top of the screen, clickConfiguration, then, on the left, click .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.
- In this example, scroll through the list of profiles to find the profile namedhttpthat displays the silo nameMySilo, then click on the profile name.
- Revise the values forRequest Chunking, andResponse Chunkingso that they match the settings in working configuration, and then clickSave & Close.
- Deploy these changes back to the device you imported it from.
- Remove the device from the silo.
- Import the device back to the BIG-IQ, and choose Use BIG-IP to resolve the remaining conflicts for this profile.
- 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
- At the top of the screen, clickConfiguration, then, on the left, click .The screen displays the list of profiles defined on this device.
- ClickCreate.The New Profiles screen opens.
- Type aNamefor 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 typehttp-newor something similar.
- ForSilo, selectMySilo.This tells BIG-IQ to create this new profile inside the silo you are using to resolve your conflicts.
- ForPartition, type the name of the BIG-IP device partition on which you want to create the profile.
- ForTypeselectProfile HTTP.TheParent Profilefield along with the additional properties required to define the selected profile type displays.
- FromParent Profile, selecthttp.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 selectOverride 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.
- For each setting that needs to change, select the check box in theOverridecolumn and then type or select the correct value.
- SelectSave & Close.