Bug ID 999833: Backplane connectivity failures upon blade boot

Last Modified: Oct 20, 2022

Bug Tracker

Affected Product:  See more info
F5OS Velos(all modules)

Known Affected Versions:
1.1.0, 1.1.1

Fixed In:
1.2.0, 1.1.2

Opened: Mar 05, 2021
Severity: 3-Major
Related Article:
K74379524

Symptoms

After powering on or rebooting one or more blades in a partition, blades can fail to establish data plane connectivity between each other across the backplane, resulting in complete loss of traffic in between blades. This can exhibit itself with symptoms such as an inability for multi-blade tenants to cluster, or traffic received by one blade being unable to route that traffic to another blade, among other possibilities. The problem can be identified more specifically by inspection of the tmstat 'vqf_cfg' table in the partition_fpga container. On each blade perform the following: docker exec -it partition_fpga tmctl -d blade -w 120 vqf_cfg If the 'active_blades' column does not have the same value for all assigned and enabled blades within a partition, and are otherwise expected to be running with good states, then this issue has likely been encountered.

Impact

Loss of data plane traffic in between blades within a partition.

Conditions

A blade is booted for the first time, or rebooted.

Workaround

Attempt to reboot the blade until the condition clears.

Fix Information

None

Behavior Change