Release Notes > Maintenance Fixes > Fixed in 32.2.6.0
Fixed in 32.2.6.0
General Bug Fixes
Item
Description
Bug ID
1.  
In an HTTP Modification rule, when clicking the path option, the Path field was not visible.
DE58288
DE58290
2.  
In an ADC-VX environment, after executing the techdata, tsdump, or td-stats all commands, the MP CPU reached 100% utilization.
DE58250
3.  
The Alteon NTP time jumped one month ahead.
DE58133
4.  
At boot time, when AppWall crashed, Alteon also crashed.
DE58058
5.  
When user configuring a scripted health check for port 25 (SMTP), during runtime the syslog was flooded with health check failure logs.
DE57867
6.  
On receiving an ICMP_UNREACH packet, when matching an existing session with no real server, a panic occurred.
DE57860
7.  
When a VRRP group was configured, sharing did not work properly.
DE57848
8.  
In AppShape++ scripting, an early and unnecessary variable validation was removed from the validator function.
DE57762
9.  
After upgrading from version 31.0.10.50 to 32.2.3.50, the GSLB DNS Summary Statistics displayed with a 0.
DE57675
10.  
In Layer 2 mode when flooding to more than one port, fragmented packets (both in order and out-of-path) were lost.
DE57641
11.  
In an ADC-VX environment, after enabling /cfg/slb/ssl/adv/bereuse, after a reset or reboot the value changed back to disabled.
DE57632
12.  
When an unchained buffer was treated as a chained buffer in non-DPDK platforms, a one-time crash occurred. A check was added to packet captures to prevent this.
DE57568
13.  
Due to an incorrect version comparison, TLS 1.1 displayed as disabled by default.
DE57561
14.  
The length of the hostname in the HTTP healthcheck field was increased to 128 characters as required.
DE57548
15.  
There was a high load on the queues from Alteon to AppWall, a session entered into the pending list twice, and activated after termination. This caused a panic.
DE57537
16.  
When PIP mode was configured as address and HA mode as switch, if the same PIP range was associated to more than one service or real server, the PIP ARP limit was reached.
DE57517
17.  
Alteon incorrectly validated unsupported path attributes (currently the BGP community path attribute).
DE57512
18.  
Using WBM, the percent character (%) in the passphrase for private keys did not work.
DE57488
19.  
Using WBM, could not renew existing certificates because of internal indexing issues.
DE57470
20.  
When a DPDK initialization failed on any error except a queue error, it reverted to tuntap.
DE57371
21.  
On a 9800 platform, after saving a configuration the following error displayed: mgmt: Flash Write Error
DE57349
22.  
Using WBM, removing a target address from the SNMV3 did not remove the address from the AppWall UI server list.
DE57314
23.  
When the SNMP OID hwApplicationSwitchNameInfo was probed, the port state incorrectly changed to disabled by referring to the wrong port flag state. This led the gateway health check to fail.
DE57304
24.  
When the MP froze, the Watcher did not also kill the AW process of this MP.
DE57293
25.  
When the real server rindex fell in a different word index group (rindex value /32), SLB traffic ignored the real server's weight for the roundrobin group metric.
DE57269
26.  
After rebooting a master and it comes up with an RSTP setup, an ARP packet was sent and received over the backup's block port.
DE57251
27.  
The interface IP address and floating IP address were swapped and applied. The IF IP address was added to the IP6 Neighbor Cache table as the new IF IP address, but was deleted as the old floating IP address.
DE57224
28.  
After rebooting a vADC, the GSLB/LinkProof licenses were disabled.
DE57178
29.  
After performing a recovery, the session capacity value was incorrect.
DE57147
30.  
As per RFC 3416, the SNMP Get Next values should be in lexicographical format, but Alteon did not follow this for the FDB table and other tables. A fix was made only for the FDB table.
DE57060
31.  
On a FIPS card, a session terminated while it was still pending for a task.
DE57049
DE57051
32.  
After a period of no traffic, the race condition timing could lead to an AppWall restart.
DE56991
33.  
OSPF was not able to send a link state update (redistributed route) to peed when the gateway went down.
DE56965
34.  
In an SLB environment with HA and session mirroring enabled, real server current session statistics and redirect statistics displayed incorrectly in the /i/slb/virt x summary on the backup device. This resulted in traffic failure when the backup became the active.
DE56946
35.  
A configuration with many real servers caused a delay in context switching, resulting in LACP messages not being handled.
DE56933
36.  
Using WBM, when trying to modify the throughput limit, an error occurred. Added a REGEX to support all the throughput licenses.
DE56921
37.  
After version upgrade, GEL licenses were rejected.
DE56887
38.  
In an HA environment with vADCs, when trying to send more OSPF routes to the peer device, a panic occurred.
DE56836
39.  
An incorrect FIPS license string (deprecated) caused a flow of FIPS tests.
DE56812
40.  
When a service was configured in a non-existing VIRT, it remained unnoticed until the VIRT was defined.
DE56794
41.  
Using WBM, the Edit Security Policy option did not display.
DE56783
42.  
When mgmt was disabled and the syslog defined on mgmt, the new syslogs did not display in /info/sys/log.
DE56733
43.  
There was a RADIUS Authentication failure because secret was not configured. No warning was issued for this.
DE56722
44.  
After inserting a 1G SX Multimode transceiver, the following error displayed: “Cannot work with 1G transceivers.”
DE56713
45.  
Alteon DPDK platforms dropped out-of-order fragmented packets.
DE56700
46.  
The vconsole internally used Terminal MultiPlexer (TMUX), which is not available on DPDK-based platforms.
DE56691
47.  
When trying to upload tech data when the management network was slow, an SCP timeout error occurred.
DE56655
48.  
After applying the /info/sys/general command, the output was incorrectly 7612 S instead of 7612 SL.
DE56608
49.  
While deleting an IPv6 configuration, a panic occurred. Added defensive validations.
DE56597
50.  
Using WBM, the Monitoring > System > Capacity > Application Delivery page did not display capacity information.
DE56486
51.  
Port 2233 was visible to public networks. The new behavior is that port is visible to a local host only (for example: 127.0.0.1:2233).
DE56399
52.  
Using the CLI, after configuring a local add as a nwclass ID, after reboot, the configuration was not applied.
DE56336
53.  
Using WBM, the configured Server Certificate group in a configuration did not display.
DE56289
DE56291
54.  
Configuring the data class IP address with mask 0 caused a panic. Because mask 0 is invalid, the fix was to ignore it.
DE56281
55.  
When IPv6 TCP small packets were received by the MP out of order via the data port, the memory associated with the packets was not returned (after the usage) to the pool of free small packets, causing problems for features allocating such packets.
DE56080
56.  
On an ADC-VX, an NTP timeout occurred.
DE55856
DE55861
57.  
In an SLB environment with forceproxy, the TCP policy/pushack worked as disabled even though it was enabled, causing a TCP retransmission problem.
prod00267404
AppWall Bug Fixes
Item
Description
Bug ID
1.  
Integrated WAF: Websec module down/up events are shown in the device system logs.
DE57855
2.  
Error API call when trying to change a tunnel operational status using AppWall API.
DE57217
3.  
AppWall API - Get specific security event resulted in error.
DE57216
4.  
Doc bug in AppWall API documentation
DE57200
5.  
Integrated WAF: Incorrect information under syslog’s DIP field.
DE56918
6.  
Alteon is not sending syslog messages for integrated AppWall.
DE56861
7.  
WAF XML file breaks Event detains into multiple queries.
DE56386
8.  
Activity tracking refinement issue.
DE56277
9.  
Multiple events from different sessions are seen with same transaction ID
DE56260