Bug ID 1271417: VELOS system controller fails to PXE boot when network-range-type is RFC1918

Last Modified: Oct 22, 2024

Affected Product(s):
F5OS F5OS-C, Velos(all modules)

Known Affected Versions:
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

Opened: Mar 15, 2023

Severity: 3-Major

Symptoms

If the network-range-type is set to RFC1918, a VELOS system controller will fail to PXE boot from its peer system controller, reporting an error message "Unable to locate configuration file".

Impact

Unable to PXE boot the system controller.

Conditions

- The Internal Chassis Networking range (network-range-type) is set to RFC1918 (the default is RFC6598).

Workaround

Log into the peer controller (the one NOT being PXE booted) as root, and navigate to the /var/images/pxelinux.cfg directory. In the directory, locate the file whose name is six hex characters ("0a", followed by two digits, followed by "07"), and rename the file to uppercase. For example: [root@controller-1(VELOS):Active ~]# cd /var/images/pxelinux.cfg/ [root@controller-1(VELOS):Active pxelinux.cfg]# ls -l 0a* -rwxr--r--. 2 root root 352 Oct 7 15:14 0ae107 [root@controller-1(VELOS):Active pxelinux.cfg]# mv 0ae107 0AE107 [root@controller-1(VELOS):Active pxelinux.cfg]#

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips