Forum Discussion
NimbostratusHow to avoid conflicts in bigiq by keeping each BIGIP separately.
Hello experts,
Suppose there is a environment running with BIGIP devices of prod and UAT having similar object names based on the application. So if we want to onboard these devices to BIGIQ for the central management, Facing conflicts while on boarding the devices to BIGIQ because the similar object names. To resolve the conflicts if we choose the BIGIP option it will replace the configuration which is not our goal, because we cannot go with changing the unique object name for lot off object.
How to keep each device configuration separately in BIGIQ to avoid conflicts. we try to keep devices in different device groups but that doesn't solve the conflict issue.
Please help how we can achieve this.
- Paulius
MVP
RajeshB Sadly the only option is to have a unique name for the specific configuration item that you don't want to be the same across all devices that the BIG-IQ manages. We had a similar situation where the configuration for Primary and Secondary sites needed to be slightly different because of their location so the only alternative was to use unique names among the different BIG-IPs.
RajeshBHi Sebastian,
Thank you for the response, but the silo is only for temporary to avoid conflicts. Here our scenario is with devices having same object names accross prod and Dev bigips. So we want to keep all bigip devices seperate groups.
How we can address this.
