Last Modified: Apr 28, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.6.2
Fixed In:
F5OS-C 1.8.0
Opened: Sep 19, 2023 Severity: 2-Critical
If a booting system controller receives invalid chassis network prefix information from its peer, it may use that information and configure an invalid network prefix for the chassis.
Docker fails to start because the configured prefix info is invalid.
Chassis startup.
Netowrk prefix info validation is added to ensure network prefix info received form the peer system controller is valid. If not, the receiver will reboot expecting to receive valid network prefix info on the next startup.
After validating network prefix info received duing startup, docker startup failures caused by overlapping network prefixes are no longer seen.