Bug ID 1067757: Don't pull the standby system controller and then reconfigure the RFC1918 prefix before reinserting it

Last Modified: Jan 14, 2022

Bug Tracker

Affected Product:  See more info
F5OS Velos(all modules)

Opened: Dec 13, 2021
Severity: 3-Major

Symptoms

If the standby system controller is removed and the system is then reconfigured to a different RFC1918 network prefix for internal traffic, and then the system controller is reinserted, it will fail to rejoin.

Impact

System will no longer have a redundant system controller configuration until the communication problem is resolved

Conditions

This occurs when removing the standby system controller and then reconfiguring the prefix via the 'system network config network-range-type RFC1918 prefix' command.

Workaround

Only change the network prefix with both controllers present and joined. If the condition is encountered, change the operating system controller back to the prefix the standby was configured for when it was removed, reinsert it, and then reconfigure after it joins. If thats not practical, reload the standby controller via pxeboot or usb stick.

Fix Information

None

Behavior Change