Last Modified: Apr 28, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-A 1.0.0, F5OS-A 1.0.1, F5OS-A 1.1.0, F5OS-A 1.1.1, F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2, F5OS-A 1.4.0, F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.7.0, F5OS-A 1.8.0
Opened: Aug 08, 2022 Severity: 2-Critical
The LOP may be inaccessible due to being stuck in bootloader mode. This can have various symptoms, including: - the inability to reboot the appliance via the API or CLI - the AOM is not be accessible - interfaces may not come up - power supply LEDs may not light correctly. - repeating log messages of the form "LOP USB Device is not present at either: /dev/ttyAOM or /dev/ttyACM0"
Some CLI commands may not work such as reboot or show interface: r10900_appliance(config)# system reboot The reboot of the system results in data plane and management connectivity to be disrupted. Proceed? [no,yes] yes Error: application communication failure
LOP status can be verified via the lsusb command. A device with the address of f5f5:df11 confirms the LOP is in bootloader mode. Example: [root@appliance-1(r10900_appliance) ~]# lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 1d6b:0102 Linux Foundation EEM Gadget Bus 001 Device 002: ID f5f5:df11 <-------------- Bus 001 Device 004: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
1. From a root login to the system, locate the most recent firmware for the LOP: [root@appliance-1 ~]# docker exec platform-fwu ls /usr/lib/firmware/ | grep ^lop- lop-vanquish-v0.00.140.0.1.dfu lop-vanquish-v1.00.239.0.1.dfu 2. Use the latest version of the lop-vanquish or lop-chassis-controller firmware to reprogram the LOP: docker exec -it platform-fwu dfu-util -D /usr/lib/firmware/lop-vanquish-v1.00.239.0.1.dfu
None