Last Modified: Jun 04, 2025
Affected Product(s):
F5OS Velos
Fixed In:
F5OS-C 1.3.0
Opened: Jun 01, 2021 Severity: 3-Major
Blades fresh from manufacturing do not contain an OS image. If not made part of a chassis partition with an os image defined, when inserted, they will wind up in a continuous reboot loop. There is potential that this might cause damage to blade components if allowed to continue for an extensive period of time. As systems shipped from factory include all slots in the default chassis partition and that partition is set up with a partition image already configured, this condition should only be possible when blades are added in the field, and the site has added chassis partition definitions that do not have OS images set.
Potential drive media damage if the reboot loop is allowed to continue for an extended period of time.
Freshly-manufactured blade installed in a system slot that is not part of a chassis partition with a defined ISO image.
Options to mitigate: 1. Install an os image on the new blade. 2. Power down the blade using AOM until ready to load an image. The simplest method to install an os image is to be sure the installation slot is part of a chassis partition definition that includes a set os image. By default the blade will PXE boot that image.
None