...
BugZero found this defect 188 days ago.
A dma-agent seg_fault occurs when there is a conflict between special EPVA allow-list entries.
Traffic loss as the dma-agent needs to be restarted by its watchdog/start up script. Tenants need to re-register with the datapath.
A conflict between two entries on the allow-list triggers a code path in the dma-agent and resulting in a seg_fault.
None
This issue has been fixed by setting a THREAD local variable in the epva_tbl_mgmt thread, preventing a seg_fault when the edge case method is triggered.
9.45
Install fails as lind keeps failing due to "Fatal error: block id new probe failed - device file:/dev/cdrom"9.4
Diag-agent service memory utilization increases because of heartbeat probe9.4
Unable to load in the dashboard for SWG reports9
No PDF attachment is received in ASM Scheduled Charts9
ASM Charts: Custom Advanced Filters not working9.85
VCMP guest on version 16.1.4 or above might experience constant TMM crashes.9.45
Install fails as lind keeps failing due to "Fatal error: block id new probe failed - device file:/dev/cdrom"9.45
Incomplete or missing IPv6 IPI database results to connection reset and/or high TMM CPU usage9.45
For E810 100G SR-IOV NICs, traffic disruption is seen with ICE driver v1.11.14 and NVM 4.20 combination.9.4
EPVA related dma-agent crash9.85
VCMP guest on version 16.1.4 or above might experience constant TMM crashes.9.85
Global search and other queries fail if BIG-IQ system in an high availability (HA) configuration use IPv6 discovery addresses9.85
BIG-IQ high availability (HA) peer unavailable for a few minutse approximately once a day9.85
Configuration pages might show a banner indicating that import conflicts must be resolved, but links to incorrect device9.85
Menu visibility issue with newly activated license.