Item | Description | Bug ID |
|---|---|---|
1. | On an Alteon VA device, in some cases SSH and WBM connections failed due to the non-availability of free virtual memory. | DE76265 |
2. | The Throughput threshold license caused an error even though the high threshold had not been reached. | DE76313 |
3. | When accessing the tunnel meta header of a frame for non-tunnel traffic with filter reverse session support, the device rebooted. | DE76380 DE76384 |
4. | Bandwidth Management (BWM) did not restrict upload bandwidth. | DE76718 |
5. | Configuring 3044 real servers caused high MP CPU and LACP problems. | DE76788 DE76789 |
6. | The device ran out of Heap memory, causing it to reboot. | DE76885 |
7. | In an SLB environment with dbind forceproxy and dbind ena, the device rebooted unexpectedly. | DE77024 |
8. | Changing the SIP from network class to subnet/network in a filter was not updated in the configuration. | DE77187 DE77188 |
9. | When configuring the action in an HTTP modification rule, the Alteon action was not validated correctly. | DE77277 |
10. | No data was received from Alteon for LinkProof Analytics | DE77437 |
11. | The device rebooted because of an issue with nsgroup auto-completion. | DE77456 |
12. | The device rebooted because of hardware Watchdog issues. | DE77487 |
13. | The DNS persistence cache cleared on Apply of GSLB changes. An alert was added to display when this occurs. | DE77516 DE77517 |
14. | Generating tech data could take a long time. | DE77625 |
15. | vDirect issued an error for table SpMemUseStatsTableEntry using SNMP. | DE77641 |
16. | MP CPU utilization was high, causing the device to reboot. | DE77727 |
17. | With a BWM rate limiting contract assigned to a forceproxy service, when AppXcel sent a frame to the client/server, the contract information stored in the frame was overwritten with the default contract, causing a failure with BWM enforcement. | DE77824 |
18. | After changing the user role from User to Web AppSecurity Viewer without submitting the change, associating a Web application resulted in an error message which was not clear. | DE77899 DE77900 |
19. | Importing the configuration resulted in a missing bitmap handling. | DE77914 |
20. | The device rebooted with the following error: SIGSEGV(11) thread STAT(tid=71) | DE77944 DE77945 |
21. | When applying configuration changes unrelated to the SLB module, the nbind session table entry erroneously cleared. | DE77950 |
22. | When performing a simultaneous operation of import and apply config, changes were displaying in diff. | DE77995 |
23. | There was an issue with the Connection module handling traceroute packets. | DE78002 |
24. | When a packet capture running on a data port stopped, the device rebooted. | DE78058 |
25. | The vADC iprep setting was lost after performing a reboot. | DE78114 |
26. | The device rebooted when executing a diff from SNMP. | DE78153 |
27. | In an outbound LB environment, the source port of the connections was changed, leading to traffic failure. | DE78210 |
28. | The device rebooted because of the Hardware watchdog | DE78676 |
29. | A random reboot was analyzed and fixed. | DE78923 DE78924 |
Item | Description | Bug ID |
|---|---|---|
1. | The database filter removed part of the refinements, and only regex refinements remained. | DE75781 |
2. | There were cases (only in version 7.6.17 for a few signatures) where traffic was blocked although the signatures were refined. | DE76455 |
3. | In rare cases, POST request were blocked. | DE76522 |
4. | In the integrated AppWall platform, the security events were not using the correct syslog facility. | DE77260 |
5. | In rare cases and under specific conditions, AppWall restarted. | DE77492 |
6. | GEO blocking was conduct to false positive. | DE77880 |