Bug ID 963993: Unsuccessful import of SSL Orchestrator configurations if the BIG-IP device and the BIG-IQ both deployed topologies with the same name

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IQ SSL Orchestrator(all modules)

Known Affected Versions:
8.0.0, 8.0.0.1

Fixed In:
7.1.0.3

Opened: Nov 11, 2020

Severity: 3-Major

Symptoms

You cannot import BIG-IP device configurations to BIG-IQ if the BIG-IP devices and your BIG-IQ have any deployed SSL Orchestrator configurations with the same name. The import process for all BIG-IP devices with duplicate SSL Orchestrator topology names fails with the error message "Duplicate names 'sslo_XXXX' detected between the BIG-IP device and BIG-IQ, please delete them on either side, then discover again."

Impact

You will not be able to discover and import the configuration to the BIG-IQ, unless you delete or rename the SSL Orchestrator configuration in BIG-IQ causing the issue and re-deploy the topology.

Conditions

This issue occurs when the name of the SSL Orchestrator configuration deployed onto the BIG-IP device you want to import is the same as the name of an SSL Orchestrator configuration originating from a BIG-IP device already being managed by BIG-IQ.

Workaround

N/A

Fix Information

Discovery and import of BIG-IP devices with SSL Orchestrator provisioned is successful, even when you use the same name for SSL Orchestrator configurations across multiple BIG-IP devices, provided all BIG-IP devices are running the same SSL Orchestrator RPM version.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips