Item | Description | Bug ID |
---|---|---|
1. | Alteon sends multiple requests to the RADIUS server for one login to WBM. | prod00270429 |
2. | When submitting the SECWA configuration, AppWall issued the following error: You are not authorized to edit this Web Application. | prod00265178 |
3. | When the user enabled vmasport and entered Apply, Alteon rebooted due to a software panic. | prod00270547 |
4. | A real server under /info/slb/group displayed in the BLOCKED state. When a group was not attached to any service or filter, no svc-pool entry waa created for it. As a result, the wrong group was displayed with the /info/slb/group command. Fix: If at least one group is configured for the real server with no svc-entry corresponding to the group, the svc-pool entry is preserved with the default health check and group ID. In addition, if there is not any svc-entry corresponding to the group that is being queried, the default health check for the real server is displayed. | prod00272031 |
5. | When reading techdata on a ADC-VX, the device crashed and the vADCs rebooted. | prod00270910 |
6. | In a filter configuration, the default value of "matchdev" diffred between WBM and CLI. | prod00269978 |
7. | Out-of-order TCPv6 segments from the client to the MP caused a panic. | prod00270263 |
8. | Using the command /info/slb/sess/dump, the configuration sync fails while dumping huge SLB sessions onto the console. | prod00271199 |
9. | In an SLB environment, when the primary group became operational, the backup group's session table was removed. As part of the fix, the session entry is removed if the real server is not enabled under the group. In this scenario, this condition failed because the session's real server that is backed up is removed from the group when the primary real server becomes operational. This leads to removal of the backup real server's session entry when the primary real server comes up. | prod00270085 |
10. | In a hot-standby VRRP environment, when port 1 was disabled on the backup, Alteon attempted to disable the port as part of the hot standby algorithm irrespective of the current status of port. The functions called during the flow used ND APIs and they resulted in high MP CPU. As part of the fix, disabling the port again is prevented if the port is already in the disabled state. | prod00271914 |
11. | On a vADC and standalone, entering the command blkport disable caued a panic. | prod00270629 |
12. | Using WBM, the user lost access to a vADC. | prod00270705 |
13. | Was unable to install a legacy compression license on top of NG/NG+. | prod00271476 |
14. | The binary health check failed with a timeout even through the checked server replied with unexpected value. | prod00271032 |
15. | Using WBM, Alteon panicked when generating techdata. | prod00271198 |
16. | When a user tried to configure a group "metric response" with the dynamic weight SNMP health check, a warning message was issued. | prod00268995 |
17. | After enabling compression, file download failed. | prod00272069 |
18. | The VRRP backup sent advertisements after failover. | prod00271940 |
19. | The EDNS+Source network-based name resolution failed for certain source addresses. The GSLB query failed when it contained the EDNS extension with the client subnet address, which fails to match the network class configuration. | prod00270636 |
20. | When switching from an ADC-VX/vADC form factor to Standalone, the device became unresponsive. | prod00270987 |
21. | The "new cached bytes" field in the statisctics for the acceleration engine cache mechanism, displayed the wrong value. | prod00271363 |
22. | After a vADC rebooted from a panic, that part of the configuration was lost. | prod00271642 |
23. | Using WBM, when adding interfaces to a VM, Flow Continutation Ingress ports could not be validated. | prod00256871 |
24. | If a bandwidth management contract is associated to a traffic pattern and the TOS overwrite feature is enabled, a packet capture did not reflect the DSCP field modification. | prod00269734 |
25. | In a BGP environment, when network class changes were applied, the device panicked. | prod00270640 |
26. | On an Alteon D 6024 platform, could not assign more than 7200 CPS with the entire 40 CU. | prod00270007 |
27. | When trying to open WAF, received a 50x error in the browser. | prod00271715 |
28. | When running a vDirect script in Alteon, received a timeout. | prod00270578 |
29. | After upgrading from version 30.5.8.0 to 31.0.9.0, vADC-1 booted with configuration in diff. The configuration could be applied but generated the following error: ERROR mgmt: Error: Save not done. Application services engine is not synchronized with the current configuration. | prod00271383 |
30. | In an ADC-VX environment, the WBM, SSH, and console were not available until device was rebooted. | prod00270986 |
31. | Using SLB monitoring with API calls, the status of a real server that was part of a content rule and its health check failure reason could not be fetched using the API SlbStatEnhContRuleActionGroupEntry. | prod00269948 |
32. | Policy Distribution replicated Session Filter Refinements with cookies not bound to any tunnel or host. | prod00269607 |
33. | After rebooting the device, with configuration changes in diff, received errors after Apply. | prod00270462 |
34. | Using WBM, the dashboard displayed the wrong throughput for a virtual server, even though here was no traffic for the virtual server. | prod00270094 |
35. | When the filter action was "nat", the client NAT IP address options were missing from the Dynamic NAT tab | prod00272348 |
36. | With reverse ena under filter and vmasport enabled, the return traffic was not undergoing server processing/NATing, causing the server packets seen on client network. | prod00272531 |
37. | The Alteon secondary device was inaccessible via the mgmt port and console. | prod00271295 |
38. | The STG-VLAN configuration failed to apply on reboot because the number of parameters exceeded 64. Fix: After upgrade, perform the configuration and save, then reboot. | prod00271340 |
39. | WBM did not display the virtual service configuration after synchronization. | prod00270170 |
40. | Updated the online help for IPv6 local networks to "rem6 <Local Network v6 Address entry index>" / "rem <Local Network v4 Address entry index> . | prod00270572 |