Item | Description | Bug ID |
|---|---|---|
1. | A misleading license error message was issued. | DE76144 |
2. | A search operation did not work correctly. | DE76185 DE76187 |
3. | In WBM, after Submit, SSH keys is incorrectly displayed as Do Not Erase. | DE76220 |
4. | The management port status of eth0 and eth1 displayed incorrectly. | DE76251 |
5. | On an Alteon VA device, in some cases SSH and WBM connections failed due to the non-availability of free virtual memory. | DE76264 DE76266 |
6. | The Throughput threshold license caused an error even though the high threshold had not been reached. | DE76314 |
7. | When accessing the tunnel meta header of a frame for non-tunnel traffic with filter reverse session support, the device rebooted. | DE76381 |
8. | After upgrade, running the /boot/cur command displays the image download date incorrectly. | DE76392 DE76394 |
9. | In WBM, the configured Server Side Idle Timeout values were not displayed. | DE76501 |
10. | Generating applogs resulted in high MP CPU utilization. A new warning message regarding this is now issued when running the /maint/applog/showlog command. | DE76526 |
11. | Traffic was sent to a real server when the real server health check failed due to its related buddy server failing. | DE76546 |
12. | Features that in the background automatically created virtual servers sometimes caused the High Availability configuration to be different between the HA devices. | DE76554 |
13. | Changing a health check for LDAP(S) caused a reboot. | DE76642 |
14. | Configuration sync issued caused the device to reboot. | DE76657 |
15. | Bandwidth Management (BWM) did not restrict upload bandwidth. | DE76720 |
16. | IPC module issue caused the device to reboot. | DE76759 |
17. | Configuring 3044 real servers caused high MP CPU and LACP problems. | DE76790 |
18. | The power supply failure logs had the wrong status for the power supply. | DE76833 |
19. | The device ran out of Heap memory, causing it to reboot. | DE76886 |
20. | Syslog servers and protocol definitions were saved in the vADC configuration, but were not actually used when delegated from the ADC-VX to the vADCs. | DE76965 |
21. | In an SLB environment with dbind forceproxy and dbind ena, the device rebooted unexpectedly. | DE77026 |
22. | When generating techdata, the techdata creation failed. | DE77064 |
23. | Changing the SIP from network class to subnet/network in a filter was not updated in the configuration. | DE77189 |
24. | When configuring the action in an HTTP modification rule, the Alteon action was not validated correctly. | DE77278 |
25. | No data was received from Alteon for LinkProof Analytics | DE77438 |
26. | The device rebooted because of an issue with nsgroup auto-completion. | DE77457 |
27. | The device rebooted because of hardware Watchdog issues. | DE77488 |
28. | The DNS persistence cache cleared on Apply of GSLB changes. An alert was added to display when this occurs. | DE77518 |
29. | Generating tech data could take a long time. | DE77626 |
30. | vDirect issued an error for table SpMemUseStatsTableEntry using SNMP. | DE77643 |
31. | MP CPU utilization was high, causing the device to reboot. | DE77728 |
32. | 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. | DE77825 |
33. | 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. | DE77901 |
34. | Importing the configuration resulted in a missing bitmap handling. | DE77913 |
35. | The device rebooted with the following error: SIGSEGV(11) thread STAT(tid=71) | DE77946 |
36. | When applying configuration changes unrelated to the SLB module, the nbind session table entry erroneously cleared. | DE77952 |
37. | When performing a simultaneous operation of import and apply config, changes were displaying in diff. | DE77994 DE77996 |
38. | Defect with the Connection module handling traceroute packets. | DE78001 |
39. | When a packet capture running on a data port stopped, the device rebooted. | DE78059 |
40. | The vADC iprep setting was lost after performing a reboot. | DE78113 |
41. | The device rebooted when executing a diff from SNMP. | DE78154 |
42. | In an outbound LB environment, the source port of the connections was changed, leading to traffic failure. | DE78212 |
43. | The device rebooted because of the Hardware watchdog | DE78638 DE76658 |
44. | A random reboot was analyzed and fixed. | DE78925 |
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 |