Bug ID 948417: Network Management Agent (Azure NMAgent) updates causes Kernel Panic

Last Modified: May 29, 2024

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

Known Affected Versions:
15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 16.0.0,, 16.0.1,,

Fixed In:
16.1.0, 15.1.4

Opened: Sep 24, 2020

Severity: 3-Major


- TMM crashes - kernel panics - BIG-IP core file created - Cloud Failover Extension unexpected behavior (where applicable)


- Traffic disrupted while tmm restarts - BIG-IP restarts - Cloud Failover Extension state data lost (where applicable)


- BIG-IP Azure Virtual Edition - Azure Host performs a Network Management Agent (NMAgent) update while TMM is running - BIG-IP VE using Accelerated Networking


- Disable Accelerated Networking on BIG-IP network interfaces (Reversed settings from Azure documentation) Individual VMs & VMs in an availability set First stop/deallocate the VM or, if an Availability Set, all the VMs in the Set: Azure CLI az vm deallocate \ --resource-group myResourceGroup \ --name myVM Important, please note, if your VM was created individually, without an availability set, you only need to stop/deallocate the individual VM to disable Accelerated Networking. If your VM was created with an availability set, all VMs contained in the availability set will need to be stopped/deallocated before disabling Accelerated Networking on any of the NICs. Once stopped, disable Accelerated Networking on the NIC of your VM: Azure CLI az network nic update \ --name myNic \ --resource-group myResourceGroup \ --accelerated-networking false Restart your VM or, if in an Availability Set, all the VMs in the Set and confirm that Accelerated Networking is disabled: Azure CLI az vm start --resource-group myResourceGroup \ --name myVM

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips