Last Modified: Nov 25, 2025
Affected Product(s):
F5OS Velos
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.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Dec 13, 2021 Severity: 3-Major
When using a non-default internal chassis network range, a fresh 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.
System will no longer have a redundant system controller configuration until the communication problem is resolved.
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.
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. On the non-functional system controller, ensure that platform-services-deployment has finished starting up before proceeding (approximately 15 minutes). Monitor "systemctl status -l platform-services-deployment" or "journalctl -f -u platform-services-deployment" until it finishes starting up: systemd[1]: Started Launch platform service containers through Docker Compose. 4. Reboot the non-functional system controller.
None