Item | Description | Bug ID | |
---|---|---|---|
1. | Could not log in to AppWall because the AppWall token did not match the Alteon token. | prod00275564 | |
2. | A long certificate name was not accepted when attached to back-end policy. | prod00272989 | |
3. | In switch HA mode, unexpected failback sometimes happened. | prod00274830 | |
4. | When idbynum was enabled, there were issues with Revert Apply. | prod00273939 | |
5. | Using WBM, the Maximum Session Number was not changed after adding a CU. It only was changed in CLI. | prod00274618 | |
6. | A vADC panicked, became stuck, and was not able to handle any traffic. | prod00274773 | |
7. | In an AppWall Integrated in Alteon environment, an attack was blocked but the security event did not display. The Transaction ID was 0. | prod00272360 | |
8. | There was an AppWall state INIT issue. | prod00274124 | |
9. | Handled CVE 2019-11477, CVE 2019-11478, and CVE 2019-11479 using a Linux Kernal patch. | prod00273352 | |
10. | Alteon indirectly caused a vulnerability to the DNS cache poisoning attack. | prod00266906 | |
11. | Using WBM, a Notify View ISO could not be configured without creating a custom Notify Tag. | prod00273674 | |
12. | The REST API documentation was missing the option for graceful server shutdown. | prod00273991 | |
13. | A packet capture's TCP stream displayed corrupted data due to TSO allocated buffers. | prod00262898 | |
14. | In an AppWall Integrated in Alteon environment, configuration import was only partial. | prod00274253 | |
15. | A vADC could not handle any data traffic including a health check. The vADC did not restart after an SP panic/freeze. | prod00274245 | |
16. | When enabling an HTTP/2 policy, a panic occurred. | prod00273673 | |
17. | Using WBM, could not change the default of factory configuration to save the management configuration. | US64628 | |
18. | With Layer 7 Application Acceleration, some connections were dropped in the middle. | DE50652 | |
19. | SNMP data of polling interface details incorrectly displayed the interface type. | prod00273383 | |
20. | While running a scan over SSH, Alteon panicked. | prod00274796 | |
21. | After reverting an unsaved configuration, the HA State remained INIT and was not updated automatically. | prod00272979 | |
22. | On a vADC, there was high MP CPU utilization. | prod00274055 | |
23. | SIP INVITE and fragmented packets were not forwarded to real servers. | prod00273232 | |
24. | Using Linkproof NG, when the upload/download limits for the WAN link were configured to be greater than 455 Mbps, WAN link bandwidth utilization displayed incorrect statistics. | prod00273014 | |
25. | Health checks failed due to a corruption in the small/medium/jumbo packet free pool list because of a synchronization problem in the ARP module. | prod00274563 | |
26. | After upgrading to version 32.2.1.0, session logs were not generated. | prod00272745 | |
27. | Using WBM, when VIPs were added to/removed from the HA service list, Alteon panicked. | prod00273652 | |
28. | Using WBM, there was an HTTP modification rule configuration issue. | prod00273395 | |
29. | Configuration sync failed with a timeout. | prod00273096 | |
30. | While loading the configuration from flash, an Apply failure occurred during bootup time. | prod00274182 | |
31. | In a GSLB with VRRP/HA environment, after applying a configuration, the DSSP health checks failed. | prod00273185 | |
32. | Alteon was rebooted unexpectedly by Watchdog. | prod00273483 | |
33. | The GSLB DNS client network rules real server selection pane was too small. | prod00272844 | |
34. | With lower BFD rx-int configured, when there was a change in the session table type between ABT and PBT, the BFD session went down, causing deletion of the BGP session. This issue has been addressed by yielding control to the SP to send BFD packets. | prod00272647 | |
35. | IEEE 802.3 standard protocol packets (such as STP packets that run over LLC) sometimes were incorrectly classified as packets with a length error by the Fortville MAC. The CRC was not stripped from such packets, and the RLEC counter was incremented. These packets later caused problems when they were transmitted with the unstripped CRC to other entities in the network. | prod00272401 | |
36. | A MAC flap on Layer 2 occurred when the DUT was connected on one port and the server was connected on a different port. | prod00273320 | |
37. | When viphlth was enabled, there was no response to ICMP health checks directed at VIPs. | prod00274666 | |
38. | A configurational change to shutdown did not display correctly under /cfg/slb/group x/cur. | prod00272732 | |
39. | After resetting the admin password from the console, the password displayed in clear text in diff flash. | prod00274142 | |
40. | Using WBM, a Notify View ISO could not be configured without creating a custom Notify Tag. | prod00273732 | |
41. | Using WBM, when changing the "DNS Responder VIP" from "dis" to ena" and vice versa, Alteon did not update the flags that are used to identify the config change. Because of this, Alteon found no config change during Apply and an issue occurred. | prod00273455 | |
42. | Was not able to configure service 111 for TCP and UDP. | prod00272572 | |
43. | NTP requests were not sent in an OSPF network. | prod00274316 | |
44. | Using WBM, an Invalid EC Key Size (6). error displayed while generating an SSL certificate an RSA key. | prod00273180 | |
45. | In a GSLB environment, Alteon did not resolve a DNS query even though the remote real servers were UP. | prod00272894 | |
46. | After upgrading to version 32.2.2.0, constant VRRP flaps with MP keepaliveFailure occurred. | prod00274526 | |
47. | After a Submit via QAS, a service's rport was overwritten. | prod00272876 | |
48. | Using Passive FTP, an RTS session was created instead of a filter session for FTP data traffic. | prod00272715 | |
49. | When the DNS virtual service protocol is UDP Stateless, HTTP and FTP services failed for IPv6 traffic. | prod00273829 | |
50. | When VLAN 1 was disabled and an Apply was done for any config change, the ping response to the interface was delayed, causing a timeout. | prod00273593 | |
51. | When Alteon sent syslog messages, a panic occurred. | prod00272883 | |
52. | After Applying configuration changes, VIPs stopped responding. | prod00272573 | |
53. | While running a scan over SSH, Alteon panicked. | prod00274825 |