Bug ID 1067757: System controller will not join cluster if internal chassis network range differs from existing controller

Last Modified: Jul 09, 2025

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-C 1.2.1, F5OS-C 1.2.2, F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.8.0, F5OS-C 1.8.1

Opened: Dec 13, 2021

Severity: 3-Major

Symptoms

When using a non-default internal chassis network range, an RMA replacement system controller running the correct software versions will not automatically join the cluster when inserted into the chassis. This will occur any time a system controller boots up with a different internal network address range.

Impact

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

Conditions

This will occur if a system controller is booting up, and has a different configuration for the internal chassis network range from the functioning system controller. This can occur when performing an RMA replacement, or a clean install of a controller via PXE or USB drive. This can also occur when removing the standby system controller and then reconfiguring the prefix via the 'system network config network-range-type RFC1918 prefix' command.

Workaround

If possible, only change the network prefix with both controllers present and joined. If affected by this issue: 1. Log into the functional system controller as root and examine /etc/sysconfig/chassis_network_active.txt 2. Log into the non-functional system controller as root, edit /etc/sysconfig/chassis_network_override.txt, and replace it with the contents of chassis_network_active.txt from the functional system controller. 3. Reboot the non-functional system controller.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips