Item | Description | Bug ID |
|---|---|---|
1. | Using SSH, there was no matching key exchange method found when connecting from Ubuntu 20. | DE70424 DE70427 |
2. | An Alteon cluster running on Azure had high availability issues. | DE72941 |
3. | Application delivery features were not available via API for the slbviewer user role. | DE74199 |
4. | When an IPv6 virtual server used IPv4 servers for load balancing and if any SLB config apply was performed, the existing sessions were closed. | DE74227 |
5. | An Alteon 5224 platform rebooted because of a power cycle. | DE74353 |
6. | An Alteon 5224 platform rebooted because of a power cycle. | |
7. | The device restarted by a software panic. | DE74397 DE64400 |
8. | After config sync, the Traffic Event Log policy sent a log via the data interface. | DE74451 |
9. | There was a Switch HA failover issue. | DE74515 |
10. | vADC buffer memory related to SSL caused a reboot. | DE74590 |
11. | An SSH management connectivity issue occasionally caused a reboot. | DE74607 DE74610 |
12. | The wrong time zone offset was sent to the NTP server. | DE74637 |
13. | On a vADC, the GET /config/SlbCurCfgEnhVirtServicesTable message was received during config sync and all hash tables were initialized (zeroed), causing a reboot. | DE74689 |
14. | A malformed server caused a miscalculation of the RTO, which led to the retransmission taking a minute, in which time the server closed the connection. | DE74761 |
15. | A vADC stopped processing production traffic. | DE74789 |
16. | The MP CPU utilization was high with DNS packets (dport 53). | DE74810 |
17. | When configuring network settings, an internal error was issued. | DE74819 |
18. | On an ADC-VX, an LACP issue was caused by high MP CPU utilization. | DE74845 |
19. | When the device started after a reboot, it stopped performing ARP base health checks. | DE74867 |
20. | Alteon Bot Manager used 1.1.1.4 in the Host Header while sending POST request to the endpoint. | DE74919 |
21. | Alteon VA devices deployed in Hyper-V experienced high CPU usage compared to other hypervisors. | DE74934 |
22. | Using SNMPv3, the "Unknown user name" is now issued for invalid usernames and invalid passwords. | DE74949 |
23. | The Ext.HC script did not generate traffic. | DE75008 |
24. | From WBM, when the SSH key was set to be deleted, after clicking Submit it was immediately deleted before the device was rebooted. | DE75021 |
25. | The device rebooted because of a software panic. | DE75039 |
26. | After inserting a 1 G GBIC, message logs did not display. | DE75059 |
27. | Changing vADC CUs caused syslogs to be removed. | DE75089 |
28. | AppWall LDAP connection failures were caused due to the multiple creation of MP processes. | DE75156 |
29. | After rebooting, configuration sync failed and the configuration was stuck in diff with the same error. | DE75228 |
30. | Alteon did not display the Korean language correctly when using local language-Korean. | DE75255 |
31. | When trying to use Single IP in Azure, a message was issued that the user should use Multiple IP address mode. | DE75285 |
32. | After an Apply failure due to an empty passphrase for certificates, after reboot the entire configuration went into diff. | DE75336 |
33. | There was duplicate entry validation error for two domains where one had a hostname and the other did not have a hostname. | DE75356 |
34. | When using the Russia time zone, the incorrect time displayed for the /info/sys/time command and in AppWall Forensics. | DE75403 |
35. | On an Alteon VA, packets larger than the negotiated MTU size were forwarded. | DE75428 |
36. | On a vADC, when executing SSL stats commands, the vADC rebooted. | DE75447 |
37. | The /oper/slb/group command displayed different output when two SSH sessions were opened to a single device. | DE75485 |
38. | After the primary real server was activated in a group, the session handled by the backup real server was fastaged. | DE75537 |
39. | An SSH management connectivity issue occasionally caused a reboot. | DE75551 |
40. | When gathering the device output, memory stats information did not appear in the techdata. | DE75688 |
41. | The client certificate went through OCSP verification even though it is in OCSP stapling mode. | DE75807 |
42. | SNMP polling resulted in an incorrect response. | DE75836 DE75839 |
Item | Description | Bug ID |
|---|---|---|
1. | Request of /v2/config/aw/SecurityEvents/ returned a false response. | DE75916 |
2. | The forensics search engine was not accurate. | DE74469 |
3. | Wildcard hostname (*nma.lt) worked incorrectly and caused false positive. | DE74667 |
4. | Session filter removed the cookie in passive mode. | DE74748 |
5. | There was no detailed information about a pattern. | DE74850 |
6. | Protected applications behind AppWall went down suddenly. | DE75232 |
7. | Under certain conditions, no explanation is provided in the Forensics API Security event. | DE75513 |
8. | Geo filter (ZZ) to display the Forensics logs for Private networks did not work. | DE75593 |
9. | In Forensics, the filter according to the Geo-Location did not work. | DE74346 |
10. | Failure to update the GEO file. | DE74563 |
11. | In API Protection, AppWall identifies parameters as "required" even when they are not in the uploaded file. | DE74572 |
12. | Failure occurs with unexpected headers in the server response. | DE74998 |
13. | AppWall Management REST for Allow-List misinterpreted a wildcard in the configuration. | DE75050 |