Release Notes > Maintenance Fixes > Fixed in 31.0.10.50
Fixed in 31.0.10.50
Item
Description
Bug ID
1.  
Using WBM, when changing "DNS Responder VIP" between dis to ena, Alteon did not update the flags that are used to identify the configuration change. Because of this, Alteon did not recognize the configuration change during apply, causing a problem.
prod00273231
2.  
Using LinkProof NG, when uploading or downloading WANlink limits that are configured to greater than 455 Mbps, WANlink bandwidth utilization produced incorrect statistics.
prod00272911
3.  
Alteon rebooted unexpectedly by Watchdog
prod00273364
4.  
Using WBM, the HTTP modification rule configuration had problems.
prod00273297
5.  
In a GSLB with VRRP/High Availability environment, after applying a configuration, DSSP health checks failed.
prod00273145
6.  
Using APSolute Vision, could not access a vADC.
prod00272750
7.  
Sending syslog messages caused a panic.
prod00272261
8.  
When the DUT connected to one port and the server was connected to a different port, a MAC flap occurred on Layer 2.
prod00273044
9.  
On a vADC, there was high MP CPU utilization.
prod00273992
10.  
When applying configuration changes, the VIP stopped responding.
prod00272557
11.  
When the DNS virtual service protocol was UDP stateless, the HTTP and FTP services failed for IPv6 traffic.
prod00273831
12.  
Using WBM, when VIPs were added to/removed from the HA service list, a panic occurred.
prod00273657
13.  
SIP INVITE and fragmented packets were not forwarded to real servers
prod00273236
14.  
When reverting an unsaved configuration, the HA state remained INIT did not updated automatically.
prod00272978
15.  
When a Submit occurred via QAS, the rport service was overwritten.
prod00272875
16.  
After resetting the admin password from the console, the new admin password displayed in clear text in diff flash.
prod00274146
17.  
Handled CVE-2019-11477.
prod00273357
18.  
Configuration sync failed with timeout.
prod00273100
19.  
Using WBM,generating a certificate resulted in the following error: Invalid EC Key Size (6)
prod00272084
20.  
Using /cfg/slb/group x/cur, configurationally changing to "shutdown" did not displayed correctly.
prod00272731
21.  
When a lower BFD rx-int was configured, when there was a change of the session table type between ABT and PBT, the BFD session went down, causing the BGP session to be deleted. This issue was addressed by yielding control to the SP for sending BFD packets
prod00272648
22.  
In a GSLB environment, Alteon did not resolve a DNS query even though the remote real servers were UP.
prod00272899
23.  
When VLAN 1 was disabled and applied for any configuration change, the ping response to the interface was delayed, causing a timeout.
prod00273597
24.  
After upgrading to version 32.2.1.0, session logs were not generated.
prod00272744
25.  
SNMP data in the polling interface details incorrectly displayed the interface type
prod00273387
26.  
The GSLB DNS client network rules real server selection screen was too small.
prod00272848
27.  
Was not able to configure service 111 for TCP and UDP.
prod00272609
28.  
Using Passive FTP, the RTS session was created instead of the filter session for FTP data traffic.
prod00272726
29.  
When enabling an HTTP/2 policy, a panic occurred.
prod00273789
30.  
There was a service failure/RIP leakage due to sessions abruptly aging out.
prod00275793