After upgrading the Alteon software version, the application Intermittently was not working.

prod00277501

On an Alteon VA, Alteon reset the connection when traffic failed over.

prod00277059

IPv6 SNMP queries over the data port were not working because checking for management access with the ingress data port failed.

prod00277282

On an Alteon 5424 platform with 24G RAM and software version 32.4.1.10, the maximum sessions remained as 11M even though the sesscap value was 100%.

prod00277362

AppWall for Alteon was not parsing parameters whose values matched the string "banana" (%F0%9F%8D%8C).

prod00274209

When using HTTP/2 after login, traffic stops working.

prod00278070

Connections to a VIP closed abruptly.

prod00276584

During stress traffic, a panic occurred.

prod00278081

The Alteon 6024 platform rebooted due to a panic.

prod00276360

The Alteon NG+ license did not apply the 5 vADC license.

prod00276639

The port speed capability was not handled for the MR platform XGE interface while dumping the port configuration and port auto-negotiation configuration options, resulting ins no diff configuration.

prod00275660

Using WBM, when starting a packet capture, unexpected data displayed for /c/sys/alerts when the packet capture filter string was set to more than 128 characters.

prod00275473

In an SLB environment, when the session move operation was executed, in some cases this operation was not reset on one of the SPs, which resulted in all subsequent session move operations to fail on that particular SP.

prod00276340

The priorities for remote real servers among different GSLB network did not behave as expected.

In this version, priority is given to nwclasses matching in added networks. As a result, if there is a SIP match for one of the networks, a network with SIP=any will not be considered. If there is no SIP match for networks with SIP configured, then a network with SIP=any will be considered. Priority is considered among the real servers of the matched network.

prod00277208

After upgrading to version 31.0.11.0, SSL offload did not work properly.

prod00276274

SSL traffic caused a panic.

prod00278067

When a device came up after reboot, the HA status displayed as NONE because the HA state was recorded based on the current HA service group state for which the apply was in process.

prod00275640

In an SLB environment with a pbind client IP address, persistence was not maintained.

prod00275950

Trend Micro's IWSVA (AV) in ICAP mode (with Alteon acting as ICAP client) was only partially working.

prod00277015

With AES used for privacy and/or encryption, the initialization vector was not set properly, causing AES encryption to fail.

prod00276313

When logged in as a TACACS or RADIUS user, could not modify or create SNMPv3 authentication or privacy passwords.

prod00277012

Using WBM, a user could change the admin password while being authenticated via TACACS or RADIUS. Usually a user is not allowed to change the admin password when logged in with "admin Privileged" using TACACS or RADIUS.

prod00277394

During SNMP polling, a panic occurred.

prod00277993

In an SLB environment, after a config sync was performed with PIP sync disabled. Alteon did not replace the client IP address with a PIP.

prod00277517

When changing to the default configuration, the runtime session capacity was not reflected.

prod00276875

During an upgrade to version 32.2.30 or later, the configuration became stuck in diff.

prod00276743

When an HTTP modification string was configured with multiple escape sequences, Alteon did not insert an escape sequence.

prod00276936

In a GSLB environment, Alteon became stuck with high MP CPU utilization.

prod00276520

When the management port was disabled, syslog messages were not sent on the data port.

prod00278037

In a DSR environment, there was a discrepancy between /info/swkey and virtual server statistics.

prod00277932

When processing the second fragment destined for the Alteon interface when the redirect filter was configured, Alteon panicked.

prod00277481

Using WBM, you could not edit the IP address for a new Outbound LLB Rule.

prod00277386

BGP 4 Byte ASN was not compatible with Cisco Nexus 9K and Huawei routers.

prod00276711

An invalid hypervisor type was set for virtual platforms.

prod00276260

VRs and Switch HA and Service HA configurations sometimes would flap or go into the INIT state after synching the configuration from the secondary device to the primary device if there was a difference in the configuration between the two devices.

prod00276501

Using WBM, could not configure BGP 4-byte-ASN.

prod00276810

Traffic was forwarded to a failed WAN real server.

prod00276356

The remote system refused the connection, impacting Azure NA self-service.

prod00277311

When the Alteon HA state changed from Master to Backup, the gateway and real server's health checks failed.

prod00278210

When changing from ena to dis and vice versa, could not apply the /cfg/l3/ha/switch/filtpbkp command.

prod00277753

Could not log in to AppWall.

prod00275567

On DPDK platforms, Interface errors for port statistics were issued.

prod00278281

ICAP responses were not forwarded to the client.

prod00276506

In an IPv6 SLB environment with an IPv6 HTTP health check and IPv6 HA configured, the memory allocated for HTTP HC was not freed, which led to a memory leak.

prod00276962

When AES was used for privacy and/or encryption, the initialization vector was not set properly, causing AES encryption failure.

prod00276312

On an ADC-VX, the device banner and /boot/cur show different active Alteon versions.

prod00276979

On a vADC, incorrect Throughput Alert messages were issued.

prod00275924

While STG information was sent from an ADC-VX to a vADC, a panic occurred.

prod00278078

When importing a configuration with BGP, Alteon issued Notice messages with non-ASCII characters.

prod00275647

On an ADC-VX, the device banner and /boot/cur show different active Alteon versions.

prod00276977

Added GSLB site IP address validation.

prod00277095

After a panic, the Admin context went into a reboot loop.

prod00276327

There were many FLOOD entries being created in the FDB table for the PIP MAC. This caused some of the traffic to fail.

prod00277246

Using the preempt disabled feature, a primary real server that was moved to the OPER DIS state by the HC module when the backup was UP for the service, continued to be in the OPER DIS state even when the "backup" and "preempt dis" settings were removed from it.

prod00276616

Using WBM, during configuration sync, continuous fetching of the virtual server table caused a panic.

prod00277467

Could not sync or apply changes.

prod00276399

In an SLB environment with preemption disabled for the primary real server, when it was in the failed state and the backup real server became the primary, the original primary real server became the backup server when its health check came UP, even though preemption was disabled.

prod00277337

When the primary WAN link went down and the backup WAN link took over, an incorrect syslog message displayed.

prod00276691

A confusing configuration resulted while implementing LDAP(S) health check.

prod00275745

In a LinkProof for Alteon environment, there were Intermittent ICMP packet drops. When pinging from the same sequence number, the ping reply packets dropped intermittently.

prod00276795

Using WBM on a vADC, could not renew an SSL certificate.

prod00276405

An HTTP header modification value set to None was considered as valid input.

prod00277186

After HA failover, Alteon lost router connectivity in order to reach real servers.

prod00277715

Enabling and disabling HTTP/2 caused service impact.

prod00275418

The backup group status in a content rule displayed an incorrect status when the backup group was not directly associated to any service.

prod00276758

In an Azure environment, Alteon VA crashed.

prod00276481

Using WBM, when "Return to Last Hop" was set for a virtual server, an additional field type was also set internally.

prod00276933

The Intermediate CA certificate could not be imported due to unexpected max limit.

prod00278075

Using Alteon VA, there were multiple core dumps that resulted in the file system becoming full.

prod00277683

An explicit proxy caused unexpected behavior for HTTP/HTTPS traffic.

prod00278421

An unexpected LACP changed state resulted in the device switching to BACKUP state.

prod00278167

Using vADC, generating a new Web Management Certificate caused a panic.

prod00278260

After upgrading to version 32.2.3.0, the device constantly rebooted due to a panic.

prod00278289

After upgrading to version 32.2.3.50, SSL inspection and ICAP Integration were not working properly.

prod00278451