Bug ID 898665: Adding a peer BIG-IQ to HA configuration after primary BIG-IQ was reset to standalone

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IQ Platform(all modules)

Known Affected Versions:
7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9

Opened: Apr 14, 2020

Severity: 4-Minor

Symptoms

When BIG-IQ is in a high availability (HA) configuration with a DCD and you: *Reset the primary BIG-IQ to standalone *Remove the Remove HA Config on the secondary BIG-IQ Error removing DCD on secondary. An attempt to recreate the BIG-IQ HA configuration fails. This occurs because you should click the click Remove Standby button on the primary BIG-IQ.

Impact

Cannot recreate BIG-IQ HA configuration.

Conditions

Resting the primary BIG-IQ in an HA configuration to standalone.

Workaround

If this occurs, run the following commands: /usr/bin/ha_reset -f <discovery_address> /usr/bin/reset-data-collection-cluster After running these scripts on the console of primary and secondary the cluster could be recreated

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips