Last Modified: Apr 07, 2025
Affected Product(s):
BIG-IP Install/Upgrade, LTM
Known Affected Versions:
16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2
Opened: May 10, 2022 Severity: 3-Major
When the BIG-IP is deployed with either D series(v5) or E(v5) series, the Azure is unable to add a route to Azure which is used by Azure to communicate with the instance. It is throwing DHCP timeout error as below. Due to this, Azure is unable to communicate and fetch the status and other details of the instances deployed.
Deployment of BIG-IP on Dv5/Ev5 series timeout due to OS Provisioning timeout.
When the BIG-IP is deployed with either D series(v5) or E(v5) series
Pre-requisite for this is accelerated networking which is supported on CentOS 7.4 or later. Currently BIG-IP uses CentOS 7.3
None