In a Smart NAT environment, due to the sequence of validations in Global SLB, the warning messages for gmetric were confusing to the user.

Note: The proximity metric for Inbound Link Load Balancing rules with Smart NAT is not yet supported.

prod00260964

In a Smart NAT environment with Global SLB turned off and LinkProof turned on, the validations related to Smart NAT were skipped and no warning messages were issued.

Note: Proximity is not yet supported for SmartNAT.

prod00260962

In a VRRP environment, after sync was performed, the server group setting was removed from the peer device.

prod00260805

In an SLB environment with the round robin or least connections metric, and with a traffic pattern that had few connections that were opened with relatively long time periods between each other, after migrating all virtual servers from the 5208 platform to the 6420 platform, the round robin metric kept selecting only one specific real server from the server group and did not balance traffic to some servers.

prod00260665

In WBM, the SLB Viewer user role was allowed to enable/disable physical ports, when this user role should only be able to view Alteon information, SLB statistics, and information, but should not be able to make any configuration changes.

prod00260638

In a virtualization environment, when accessing the device on an ADC-VX using REST API with an incorrect customized Authorization header value, a panic occurred.

prod00260577

On a 6024 XL platform with 32 GB RAM, in Maximum vADC Density mode, you could not allocate the twelfth (12th) CPU core (the fourth core for MP processing).

prod00260574

Using REST API, image upload did not work.

prod00260561

The load time of REST API calls was much slower than the load time in earlier Alteon versions.

prod00260504

In a DNS environment where DNS responses were received, and with VRRP or HA, performing a configuration sync ended with an FQDN error.

prod00260503

In an SLB environment with SSL Hello or HTTPS health checks configured, after upgrading to version 30.2.9.0, real servers configured with these health checks failed.

prod00260483

In an SLB environment with the phash metric, the traffic load was unevenly distributed to real servers with random source IP addresses

prod00260468

You could not paste a geo network class configuration as taken from the configuration file and mandate it to add None for the Country and State fields.

prod00260446

Alerts regarding DUAL PSU failure were generated, but after 6 seconds a notice was issued that the Status was Ok. This issue persisted even after changing to a new PSU.

prod00260438

Using WBM, when adding an IPv6 NAT IP address with the default prefix, because the IP address was added with prefix 0 instead of 128, the Apply operation failed.

prod00260336

Using WBM or REST API with certificate repository management, you could not overwrite a certificate.

prod00260328

In a BGP environment, after sending a BGP route update after a set of apply operations and a BGP toggle, a panic occurred.

prod00260316

In a BGP environment, during BGP route update or when the BGP peer went down during BGP peer "cleanup," the platform hung.

prod00260315

For unknown reasons, an unexpected reboot and a panic occurred.

prod00260314

Using WBM with a WAN Link configuration, there were discrepancies between the upload bandwidth of the Per WAN Link IP and the Per WAN Link ID.

prod00260298

In an SLB environment, ESP traffic was not passed to the back-end servers.

prod00260295

Using WBM, a real server's Description accepted 128 characters while only 31 characters are supported, causing the real server Description not be synced from Active to Standby.

prod00260294

When using REST API to change the next image to boot, the correct image was not set.

prod00260257

Using CLI, when configuring network classes, there were no validations when geo information was added for a network class as a one line command.

prod00260256

In an SLB environment with delayed binding enabled and APM enabled, because Alteon did not create persistent entries for a few specific clients, Alteon sent the request from a specific Client IP address to a virtual service on Alteon to different real servers, even with the persistent binding Client IP address set on the virtual service.

prod00260095

Due to a large file size, the techdata generation failed with the following message: Unknown Error

prod00260081

Using WBM, in an SSL environment, when enabling back-end SSL encryption and the back-end SSL cipher was selected as "user-defined," and then the back-end SSL encryption was disabled, the saved configuration was improper due to a malformed XML.

prod00260024

In a virtualization environment on an ADC-VX, when using a REST API call to create a vADC, a panic occurred.

prod00259833

In an SLB environment with the health check configuration destination set as hostname, the health check failed after performing an apply operation.

prod00259827

In a virtualization environment on an ADC-VX, when a configuration import (putcfg) operation was performed via SNMP, a panic occurred on the ADC- VX.

prod00259826

When SSH/Telnet connections exceeded the allowed limit, no syslog message generated.

prod00259796

In a virtualization environment with vADCs on the same ADC-VX cross-connected, ARP responses were dropped, causing a gateway failure.

prod00259666

Using WBM, in Monitoring > Network > High Availability, the VRRP labels were incorrect.

prod00259624

In a LinkProof environment configured with the bandwidth metric, Alteon did not select a WAN link based on the bandwidth metric configured on the DNS hostname and the DNS response included WAN links with the bandwidth overloaded.

prod00259617

When Alteon was accessed via SSH, the TCP connections opened for SSH sessions were not closed properly as the client continued to send data and caused stale TCP sessions. This led to SSH access failure to the device.

prod00259567

In an Outbound Link Load Balancing environment, LinkProof continued to send dispatching traffic towards WAN links whose bandwidth utilization was above 100%.

prod00259551

In an SLB environment with FQDN real servers configured, on a virtual server with FQDN real servers, Alteon returned a 503 error even though the real servers were up.

prod00259490

In an SLB environment with delayed binding as forceproxy and cookie persistency, when trying to access an account, some of the clients received error 503 for no reason.

prod00259431

In an SLB environment, when submitting a service (that supports non-standard ports) with a standard port, although the Alteon bank-end returned an error, due to the standard port, Alteon internally configured the corresponding service even after issuing the error without informing the user.

prod00259421

In a virtualization environment, after manual reboot on a vADC and when the vADC was disabled/enabled using the ADC-VX, the Apply operation 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.

prod00259409

When attempting to upload a configuration to an RMA device, a panic occurred.

prod00259397

In an SLB environment with AppShape++ configured, after aging, the TCP::close_type AppShape++ command returned an incorrect value in CLIENT_CLOSED, SERVER_CLOSED events.

prod00259382

In a Geo proximity configuration, you could not set the country Niger in an Alteon GEO network class.

prod00259348

In an SLB environment with AppShape++ configured, after aging, TCP::close reset AppShape++ command did not send a reset when called from CLIENT_CLOSED, SERVER_CLOSED events

prod00259332

Using WBM, in a Layer 7 environment when a content class was deleted and a new one was created, some AX-related configuration errors displayed upon Apply/Revert Apply, leading to some AX traffic processing issues with the content class.

prod00259206

In a virtualization environment, after disabling a vADC, the vADC's internal syslogs were deleted from the ADC-VX.

prod00259150

The vulnerability scan on the Alteon ADC-VX management IP address issued the following message: SSL/TLS Server supports TLSv1.0

Note: Configuration for the TLS version was added (affecting management traffic only):

In CLI: /cfg/sys/access/https/tlsver

In WBM: System > Management Access > Management Protocol > HTTPS

prod00258997

Outbound Telnet connections from ADC-VX/vADCs are not terminated when the respective inbound Telnet/SSH connections to the ADC-VX/vADCs are abruptly terminated, causing the user to not be able to access the ADC-VX after closing Telnet sessions abruptly.

prod00258968

After configuring two interfaces, and not on same network, when a SNMP request was sent to one interface IP address, the response came from another interface.

prod00258924

In an HA environment, when the proxy IP range is configured under the network class and a failover occurs, a GARP was not sent for all the proxy IP addresses in the range.

Note: The following new command was implemented: /cfg/l3/ha/nwclgarp ena/dis

If the network class range is huge, then the GARP being sent affects the peers ARP table.

prod00258852

After generating a Tech Support dump or Techdata, the resource allocation table information (/maint/debug/rsrcdump) was missing.

prod00258833

In an SLB environment with AppShape++ attached to a particular service, although alwayson was disabled, when the service went down, the request was forwarded to AppXcel.

prod00258824

Sometimes you could not configure a management port with an IPv6 address that was identical to one generated by SLAAC.

prod00258815

In an HA environment, although synchronization was successful, the backup device issued the following error: HA: Configuration is not synchronized between the HA devices

prod00258715

In WBM, you could not configure a network class in a range of IP addresses.

prod00258582

In an SLB environment with IPv4 and IPv6 services and IPv6 PIP configured, a panic occurred.

prod00258578

In an SLB environment with server groups, although the mhash configuration is only relevant for the minmisses metric, you could also configure it for other metrics (leastconn and svcleast), causing an Apply in these cases to fail.

prod00258547

Using WBM, In a virtualization environment on an ADC-VX, the administrator could not change a vADC's administrator password.

prod00258404

In an SLB environment with session mirroring enabled for virtual services, the session statistics were incorrect on the backup device compared to the primary device.

prod00258380

For DNS Responder virtual servers with DNS over UDP only, DNS resolution failed.

prod00258329

In an SLB environment with IPv4 and IPv6 services and IPv6 PIP configured, a panic occurred.

prod00258071

When logging into WBM using TACACS and performing configuration changes and later performing Apply/Save operations, in the audit logs another user ID was recorded instead of the user who logged in.

prod00257517

In an SLB environment with persistent binding (pbind) configured with a cookie and Client IP, when Layer 4 sessions aged out, the reference count was decremented for the wrong persistent session, causing stale p-sessions.

prod00256511

Using WBM, using $PROTOCOL instead of http:// or https:// in the redirection URL for content rules action redirect or action redirect for a service did not work.

prod00255737

Using WBM, in an SLB monitoring environment, the real server IP addresses for a server group were displayed incorrectly.

prod00255359

In an AppWall for Alteon VA environment, techdata generation abruptly stopped and a reboot was required.

prod00255272

SSL Hello health checks using TLS (instead of SSL v2/v3) were not working on XL/Extreme platforms.

DE34416

The Application Accelerator (AX) was not affected when there is an Overwrite certificate in the intermediate chain under a certificate.

DE34062

Because Alteon used TLS1 on the management port and it was not configurable to remove it, PCI compliance tests failed sometimes.

In the SSL Inspection Wizard, when Submitted changes for Transparent Mode, HTTP and HTTPS, creating new criteria, adding Layer 7 content, and Hostname List the message Internal Error displayed instead of a clear error message.

DE24421

In an ADC-VX environment with a Perform license, when enabled global on the vADC, an irrelevant message displayed:

The configuration upload failed with the following error message if the device included an IPv6 DNS responder VIP:

upgrade can be enabled for UDP services only.

From WBM, you cannot change the vADC management IP address from within the ADC-VX environment.

prod00216388

Using WBM, in the Configuration > Application Delivery > GSLB > Edit DNS Redirection Rule  pane, you cannot configure the fall back action for a GSLB Rule (/cfg/slb/gslb/rule x/fallback ena).

Using the API call with import option for policy distribution resulted in a Duplicate IP Group and Security WebApplication Role.

DE34185

DE34453