Last Modified: Sep 13, 2023
Known Affected Versions:
12.1.2, 12.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
14.0.0, 188.8.131.52, 184.108.40.206
Opened: Oct 25, 2017 Severity: 2-Critical Related Article:
Related Article: K25263287
In rare circumstances, it is possible for the embedded Packet Velocity Acceleration (ePVA) chip to try to process non-ePVA connflows. Due to this improper internal connflow tracking, TMM can crash and dump core.
TMM crashes and dumps core. A redundant unit will fail over. Traffic may be impacted while TMM restarts.
This issue can occur on any system equipped with an ePVA and configured with virtual servers that make use of it to accelerate flows. While no other conditions are required, it is known that modifying a FastL4 virtual server to Standard while the virtual server is processing traffic is very likely to cause the issue.
It is not recommended to switch virtual server profiles while running traffic. To change virtual server profiles, it is recommended to halt traffic to the system first. However, this does not eliminate entirely the chances of running into this issue.
The system now checks for HSB flow status update data and prevents false positive matches to virtual servers with non-FastL4 profiles.