Release Notes > Maintenance Fixes > Fixed in 32.2.3.0
Fixed in 32.2.3.0
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.  
Site selection rules displayed the MIB name instead of the Rule ID.
prod00272405
4.  
NTP requests were not sent in an OSPF network.
prod00274152
5.
When viphlth was enabled, there was no response to ICMP health checks directed at VIPs.
prod00274567
6.  
The GSLB DNS client network rules real server selection pane was too small.
prod00272404
7.  
After upgrading to version 32.2.2.0, constant VRRP flaps with MP keepaliveFailure occurred.
prod00274443
8.  
While loading the configuration from flash, an Apply failure occurred during bootup time.
prod00274156
9.  
In a GEL Environment, the Alteon VA prompt license server was constantly reestablishing.
prod00274121
10.  
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.
prod00272433
11.  
In an AppWall integrated with Alteon environment, the Websocket bypass feature stopped.
prod00274445
12.  
While running a scan over SSH, Alteon panicked.
prod00274764
13.  
After a device reset, could not connect to the Alteon VA management IPv6 address.
prod00274941
14.  
In an AppWall integrated with Alteon environment, there were multiple "Networking Problem" events.
prod00274862
15.  
Using WBM, could not change the default of factory configuration to save the management configuration.
US64628
16.  
With Layer 7 Application Acceleration, some connections were dropped in the middle.
DE50652
17.  
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.
prod00273016
18.  
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.
prod00274561
19.  
SIP INVITE and fragmented packets were not forwarded to real servers.
prod00273235
20.  
Using WBM, a Notify View ISO could not be configured without creating a custom Notify Tag.
prod00273725
21.  
Using WBM, could not configure the sync passphrase.
prod00274327
22.  
After running /stat/slb/clear, only part of the filter statistics was cleared, and the others remained cleared.
prod00272888
23.  
A vADC panicked.
prod00274793
24.  
Configuration sync failed with a timeout.
prod00273099
25.  
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.
prod00273282
26.  
After resetting the admin password from the console, the password displayed in clear text in diff flash.
prod00274145
27.  
In a GSLB environment, Alteon did not resolve a DNS query even though the remote real servers were UP.
prod00272897
28.  
While running a scan over SSH, Alteon panicked.
prod00274797
29.  
After a Submit via QAS, a service’s rport was overwritten.
prod00272874
30.  
Using config sync, disabling virt synchronization removed virtual servers from the backup device.
prod00273196
31.  
A vADC could not handle any data traffic including a health check. The vADC did not restart after an SP panic/freeze.
prod00274323
32.  
SNMP data of polling interface details incorrectly displayed the interface type.
prod00273386
33.  
A vADC panicked, became stuck, and was not able to handle any traffic.
prod00274804
34.  
After reverting an unsaved configuration, the HA State remained INIT and was not updated automatically.
prod00272980
35.  
Using WBM, an Invalid EC Key Size (6). error displayed while generating an SSL certificate an RSA key.
prod00273179
36.  
After upgrading to version 32.2.1.0, session logs were not generated.
prod00272743
37.  
Handled CVE 2019-11477, CVE 2019-11478, and CVE 2019-11479 using a Linux Kernel patch.
prod00273353
38.  
Alteon indirectly caused a vulnerability to the DNS cache poisoning attack.
prod00269190
39.  
When idbynum was enabled, there were issues with Revert Apply.
prod00273940
40.  
When enabling an HTTP/2 policy, a panic occurred.
prod00273687
41.  
Using Passive FTP, an RTS session was created instead of a filter session for FTP data traffic.
prod00272718
42.  
When Alteon sent syslog messages, a panic occurred.
prod00272887
43.  
A MAC flap on Layer 2 occurred when the DUT was connected on one port and the server was connected on a different port.
prod00273062
44.  
Using APSolute Vision, importing a certificate in Alteon did not work with the ADC + Certificate Administrator role.
prod00274709
45.  
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.
prod00273596
46.  
Was not able to configure service 111 for TCP and UDP.
prod00272575
47.  
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.
prod00272402
48.  
Alteon was rebooted unexpectedly by Watchdog.
prod00273479
49.  
A packet capture's TCP stream displayed corrupted data due to TSO allocated buffers.
prod00269186
50.  
When the DNS virtual service protocol is UDP Stateless, HTTP and FTP services failed for IPv6 traffic.
prod00273832
51.  
Using WBM, when VIPs were added to/removed from the HA service list, Alteon panicked.
prod00273658
52.  
After Applying configuration changes, VIPs stopped responding.
prod00272576
53.  
Using WBM, there was an HTTP modification rule configuration issue.
prod00273396
54.  
Using WBM, the Maximum Session Number was not changed after adding a CU. It only was changed in CLI.
prod00274757
55.  
After upgrading to version 32.2.1, the MP CPU utilization spiked.
prod00273889
56.  
In a GSLB with VRRP/HA environment, after applying a configuration, the DSSP health checks failed.
prod00273181
57.  
A configurational change to shutdown did not display correctly under /cfg/slb/group x/cur.
prod00272733