Bug ID 940225: Not able to add more than 6 NICs on VE running in Azure

Last Modified: Feb 07, 2024

Affected Product(s):
BIG-IP MA-VE(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2

Fixed In:
17.1.0, 17.0.0.1, 16.1.3, 15.1.6.1, 14.1.5.1

Opened: Aug 26, 2020

Severity: 2-Critical

Symptoms

Azure BIG-IP Virtual Edition (VE) with more than 6 NICs fails to boot.

Impact

Not able to boot BIG-IP VM with 8 NICs, which should be supported for Standard_DS4_v2 instance type: 8 vCPU 28 GiB 8 Max NICs Adding more NICs to the instance makes the device fail to boot.

Conditions

-- Standard_DS4_v2 Azure instance type. -- Mellanox ConnectX-3 ethernet controller. -- A greater-than-2-NIC template is used, for example https://github.com/F5Networks/f5-azure-arm-templates/tree/master/supported/standalone/n-nic/existing-stack/byol with "numberOfAdditionalNics" set. -- Accelerated networking is enabled on two or more NICs.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips