Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP MA-VE
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Opened: Oct 24, 2016 Severity: 2-Critical
BIG-IP doesn't support more than 4 NICs. As a result of this issue, you may encounter following symptoms: - BIG-IP boot time is increased. - Number of interfaces attached to tmm aren't more than 4 NICs. - In the /var/log/boot.log file, you observe messages similar to the following examples: + info plymouthd: udev still not settled. Waiting.udevd[367]: worker [380] unexpectedly returned with status 0x0100 + info plymouthd: udevd[367]: worker [380] failed while handling '/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:08/VMBUS:01/vmbus_11' + info plymouthd: udevd[367]: worker [373] unexpectedly returned with status 0x0100 RHEL7.2 (or newer) guests are similarly affected, so this issue is not unique to BIG-IP 7.2 kernels. The issue isn't reproduced on Hyper-V on Window Server 2012 R2.
BIG-IP doesn't support more than 4 NICs on Hyper-V on Windows Server 2012.
This issue occurs when all of the following conditions are met: - Your hypervisor version is Hyper-V on Windows Server 2012. - You have more than 4 NIC attached to BIG-IP.
None.
None