On an 8820 Symmetric platform, when the configuration was a super vADC, the ADC-VX went up to 45% CPU usage even without a configuration and the device was idle.

DE24490

In the SSL Inspection Wizard, the incorrect help pages displayed in several windows.

DE24539

Statistics continued counting beyond the mstat period range.

DE24401

After upgrading to version 31.0.0.0, because the internal security page .zip files are deleted from the disk, the vulnerability response was always returned as a 404 not found page instead of the configured security page.

DE22203

In an SSH environment, after an SSH authentication failure, a panic occurred.

prod00254700

When performing SSL offload for WebSocket traffic, a panic sometimes occurred. This issue had a higher probability of occurring if back-end SSL encryption was enabled.

prod00254459

Using WBM, in Configuration > Application Delivery > Server Resources > Health Check, for a RADIUS health check the "shared secret" was displayed in text.

prod00254449

In a virtualization environment on an ADC-VX, the SP memory utilization indicated that the Hi water mark value was greater than the Allowed Max.

prod00254436

Note: For SmartNAT to be processed, LinkProof must be turned on (/cfg/slb/lp/on). A warning message has been added to this version.

prod00254394

In an SLB environment, when a client request arrived with a query that was followed by some malicious content in the URI, Alteon incorrectly identified the query string.

prod00254378

In an SLB environment with the LDAP service, due to FDB corruption, there was a service interruption and multiple FDB entries for the same MAC+VLAN combination.

prod00254312

When logging in using RADIUS, a panic occurred.

prod00254305

In a VRRP hot standby environment, during failover Alteon sent GARP and VRRP advertisements in the incorrect order, causing MAC flaps and network loops.

prod00254287

On an Alteon 4416 platform, after reboot, using the CLI command /info/link, the SFP port links displayed as down.

prod00254283

Due to incorrect handling of strings in the code, Alteon was unresponsive and a panic occurred.

prod00254282

In an SLB environment with the stateless UDP DNS service configured, all client traffic to the DNS service was forwarded to the server with the destination port set to 0, causing the DNS feature to work incorrectly.

prod00254276

In an SSL environment, even though only an SSL policy was attached to a filter and front-end SSL encryption was disabled, the configuration Apply failed with an error message requesting you to attach a server certificate to the filter.

prod00254270

Using WBM, in Configuration > Application Delivery > Virtual Services > Persistency, the Persistency Mode displayed as Client IP even though Cookie was configured.

prod00254255

Alteon WBM users with class of service l4admin or slbadmin did not have permission to delete server groups, while they could do so using the CLI.

prod00254250

In upper left corner of the WBM page, the HA Status was not refreshed automatically after HA failover.

prod00254248

In Alteon Standalone mode, you could configure AppWall using WBM even though AppWall does not supported this form factor

prod00254244, prod00254243

When connecting the power cable to the platform, Alteon booted unexpectedly.

prod00254229

In a BGP environment, the BGP redistributed route metric did not work as expected for fixed networks.

prod00254171

In a High Availability environment, repeated HA failovers caused stale session entries with a higher age (32768-65535) value on the backup device.

prod00254160

After a panic, dummy MP messages displayed on the console.

prod00254147

When upgrading from version 30.2.0.0 to version 30.5.4.0, the LACP configuration was lost.

prod00254096

Could not remove the LinkProof license using the license removal command /oper/rmkey.

prod00254050

In a Global SLB environment, when a domain name with two or more GSLB rules was on the same GSLB network, Alteon replied with the server failed message that was already associated to a previous GSLB rule.

prod00254025

In an SLB environment with OSPF configured, even though the virtual servers were down or disabled, Alteon sent LS updates of the hosts to the OSPF peer.

prod00253986

In a virtualization environment, vADCs could not be synced to their configurations and there was no reply to ARP requests on the sync interface.

prod00253979

In an SLB environment with forceproxy and HA and a stress configuration, after HA failover, the real server statistics did not match the session table entries.

prod00253974

In an AppWall-in-Alteon environment, the Web security module flapped frequently even though no traffic impacts displayed during the flap.

prod00253944

Alteon logs were generated with the configuration sync successfully, even though the sync failed.

prod00253887

Using WBM, in Configuration > System > Users > Local Users, a Submit button was missing and changes could not be submitted.

prod00253876

In an SLB environment with the Action set to redirection, a very large, and incorrect, number of current sessions displayed for the total number of sessions for a virtual server on which redirection was configured. In addition, SLB statistics clear command (stats/slb/clear) did not clear the current session value.

prod00253818

In a multi-rport SLB configuration with content rules and the Action set to redirect, statistics did not display for these virtual service content rules.

prod00253781

In an SLB environment, when the FTP service was configured with FTPP disabled, the warning message related to such a configuration displayed with the incorrect virtual server index. This information was confusing as the internal index does not appear in the configuration.

prod00253608

When logged into the WBM with the slbview class of service, it you could not monitor virtual servers.

prod00253599

When multiple DNS requests with the same query that were triggered by AX requests were sent before the first one answered, and were stored in the DNS cache, OCSP failed due to DNS failures.

prod00253528

The Slow Start feature did not work as expected. In an SLB environment, when the real server was up (enabled or added) and slowstart was enabled, the other real servers in the group that were UP already did not receive more weight, and the requests were not directed to these servers.

prod00253523

You could not create a LOGEXP health check binding that had a '.' (period) character in its name.

prod00253513

As the aging procedure started the termination procedure (0.5 hours later) on a half-closed session, it caused a panic.

prod00253505

Alteon did not parse an HTTP request with a blank Host header.

prod00253503

WBM support was not available for the dynamic NAT persistence type configuration (LinkProof Smart NAT).

prod00253453

When performing SSL offload for WebSocket traffic, a panic sometimes occurred. This issue had a higher probability of occurring if back-end SSL encryption was enabled.

prod00253438

In a virtualization environment, after a panic on a vADC and the vADC was then disabled through the ADC-VX, an Apply on the configuration returned the following error message: vADC management changes due to a previous apply are currently under progress. Please try to apply the new changes after some time.

prod00253434

In a virtualization environment, when extracting techdata from a vADC, the Disk Space Exceeded syslog displayed.

prod00253432

In WBM, when duplicating a virtual server with a GSLB rule, after removing the old GSLB rule and associating a new one, the old rule remained associated.

prod00253431

In WBM, the Configuration Export button did not work in Internet Explorer and Firefox over HTTPS, but it worked in Google Chrome.

prod00253428

In WBM, the Configuration Export button did not work in Internet Explorer and Firefox over HTTPS, but it worked in Google Chrome.

prod00253426

In a SmartNAT (static NAT) environment, Inbound ICMP did not work.

prod00253411

In an SLB environment with X-forward and delayed binding configured, after Revert or Revert Apply, Alteon changed delayed binding (dbind) settings.

prod00253404

Smart NAT statistics using the command /stats/slb/lp/nat all displayed an incorrect number of current sessions.

prod00253398

When captured packets used the CLI command with the "-a" and "-s" options, the vADC froze and crashed.

prod00253395

In an SSL environment, Alteon limited the SSL Certificate size to 5000 bytes and returned an error for larger sized certificates.

prod00253387

In an SLB environment with forceproxy, the Accept encoding header was removed from the client request before forwarding it to the server, even though the RFC requires that if no compression is desired, you must have Accept encoding towards the server with its value is set to only identity.

prod00253355

Enabling signature auto-update in WAF-integrated Alteon resulted in an error message.

prod00253310

In GSLB environment, when a DNS query arrived, even though the rule's resource record was set to 1, Alteon responded with two DNS records in a DNS response.

prod00253248

When displaying a real server's health check statistics using the CLI command /stats/slb/realhc, the real server name was not properly formatted before display and garbage values displayed in place of the real server name

prod00253243

In a Global SLB environment, remote real server p-entries with a different rport on the service were never deleted. As a result, the c: counter was high while there were barely any live sessions, causing a routing Loop till TTL expired.

prod00253241

When the NTP server configured the time zone for /cfg/sys/timezone Israel, the time was displayed one hour earlier on Alteon.

prod00253209

Using WBM, the Virtual Service pane displayed incorrect the application type for the POP3 service.

prod00253205

With the UDP connection originating from Alteon, when the DNS health check tried to resolve a DNS query and it created a UDP listener on 53 with the wrong handler and cookie, when the DNS packet arrived, due to memory access that was already freed, a panic occurred.

prod00253173

In a virtualization environment, when the OCSP protocol was configured to use a management interface, OCSP requests sent from vADC 1 did not use vADC 1's management IP address but sometimes used the ADC-VX's management IP address, and at other times used the vADC 2's management IP address.

prod00253169

When the SMTP server was not reachable over the management port, the MP CPU spiked to 100% every two minutes.

prod00253080

When NTLM health checks were used, device memory slowly leaked, sometimes preventing the user to complete the config-apply operation.

prod00253078

In an SLB environment with forceproxy, the current session statistics value of the real server was not decremented properly.

prod00252995

In a VRRP environment, a Nessus security scan resulted in high MP CPU utilization on the backup, causing delays and drops of VRRP advertisements.

prod00252897

In a GSLB persistency environment, gmetric persistence did not work and the gmetric phash did not respond to DNS queries to the interface IP address.

prod00252719

When the packet capture command was executed using a script with the -c 4000 option, the stop command executed immediately, and then dumpcap command executed, Alteon registered a power cycle and generated a 1.7GB core dump.

prod00252712

In a Global SLB environment, Alteon responded for DNS query type AAAA queries even though it had no IPv6 configuration.

prod00252557

When Alteon used the IPv6 health check as a script health check, after a three-way handshake, Alteon closed the connection by sending the RST.

prod00252500

In a SmartNAT environment with the NONAT type, the source MAC address substitution (submac) feature did not work, causing an MAC-FLAP.

prod00252335

In a SmartNAT environment, when a lot of inbound sessions were sent to the SmartNAT static NAT addresses, Alteon created a session with Rt/Ru/Ri flags.

prod00252325

When WAN link was configured with PIP mode nonat, LinkProof WANlinks bandwidth metric statistics displayed 0 statistics for reverse-enabled outbound llb filter sessions.

Note: The download stats can be 0 if the reverse filter is not configured or not enabled, or the reverse traffic is not processed by the reverse filter session. In this case, the traffic may be successful since the packet is not modified (due to NONAT), and Alteon can forward the response to the client without server session lookup.

prod00252321

In a SmartNAT with Global SLB environment, the WANlink bandwidth metric for GSLB inbound rules did not work as expected and traffic was blocked.

prod00252312

In a virtualization environment on an ADC-VX, importing the ADC-VX configuration with mansync enabled, disabled VLANs were added to the default STG (STG1).

prod00252098

When making a change on a vADC and performing a save, the changes were reflected in config1.txt file. However, the last save date timestamp did not get updated.

prod00251985

In an inbound link load balancing (LLB) environment, when least connections was configured as the metric for LLB, the DNS responder returned only one VIP and distribution could not be performed for DNS requests.

prod00251980

Using WBM, in Configuration > Network > High Availability > Legacy VRRP > VRRP Authentication, a special character authentication password for VRRP was not accepted.

prod00251956

An Alteon WBM user with class of service slbview could not view servers per group from the Server Groups table.

prod00251954

In an SLB environment, when non-printable characters were entered as a Cookie name, the input was accepted. When trying to save, the following error displayed: Application services engine is not synchronized with the current configuration

prod00251840

When a content-length header arrived in a separate TCP segment, NTLM health checks sometimes failed by error.

prod00251311

Using WBM, when you attempted to edit a redirect filter, an error message displayed.

prod00251031

In Virtualization environment, as the watcher was killing an unresponsive MP during AppWall process creation, the vADC became inaccessible.

prod00249704

To send e-mails for BWM statistics, Alteon initiated a connection with the SMTP server with default format of the FROM field, although it should have taken it from the syslog e-mail settings in /cfg/sys/syslog/email.

prod00249397

In a Smart NAT environment for outbound traffic and Global SLB DNS queries, sometimes the priority doesn't work as expected.

DE19218

In a No NAT static NAT environment, even though the local server is up and running and HTTP requests are forwarded to the local server, no response is given to the ICMP command (that is, the ping to the static address does not work).

DE18963

A memory leak in the Activity Tracking module was fixed.

When exporting the configuration of an Alteon device with integrated AppWall, the AppWall configuration file did not include configured security filters.

DE25043

When Alteon retrieved CPU information from AppWall with SNMP, the MIB always returned a zero value.

When an HTTP parsing violation was logged and CDN support was configured, the logged source IP address displayed the Layer 3 source IP address rather than the XFF source IP address.

Reverse DNS lookup was not working properly when Activity Tracking was enabled.