If you upgraded to version 31.0.8.0 from version 30.5.x or 31.x, if prior to the upgrade you set /c/l3/bgp/peer <x>/redist/default to non, red, or orig, the received BGP default route no longer was imported.

This limitation was fixed in this version.

 

In a virtualization environment with multiple versions on the primary and backup vADCs, when the configuration was, the configuration was not deleted from the backup vADC.

prod00269797, prod00269210

In an SLB environment, although only 29 real servers were configured, when trying to configure a real server (with a duplicate), the following error message was issued: The maximum of 1023 Real Servers has been reached. To add new real server, first delete any unused Real Servers and apply.

prod00269764

In a virtualization environment, during configuration synchronization the MP CPU usage of the vADC stayed at more than 80% for a long time.

prod00269708

In an SLB environment with force proxy enabled, when the server group names exceeded 50 characters, and first 50 characters were identical, after upgrading, Alteon stopped processing the traffic.

prod00269614

In an SLB environment with cookie persistent mode and forceproxy, the svclstconns metric always selected the same server as the collection of active connections, causing unequal load distribution for the service.

prod00269520

In a virtualized Alteon (VX) sometimes management access was lost to a vADC (MP CPU got stuck).

prod00269355

In an Alteon integrated with Appwall environment, after an upgrade, an Apply was required for WAF changes.

prod00269270

When RADIUS authentication was enabled and a user logged in using SSH (probably using scripts), a vADC panic occurred due to NULL memory access.

prod00269202

In an SLB environment, when the real service port (the rport of a virtual service) was configured with a value less than 5 (except for multiple rports/IP addresses service scenarios), the traffic on these rports failed.

For the fix, a validation has been added to allow rport 0-multirport or 1-ipservice or 5-65534.

prod00269097

Irrespective of the LACP port configurations, Alteon with STP off did not pass transparently BPDU from Cisco Nexus with MSTP.

prod00269092

In an SLB environment with DNS Responder VIPs, with mixed delegation/non-delegation traffic, a panic occurred.

prod00269060

In an SSH environment, downloading an image using SCP was slow compared to downloading through FTP.

prod00269009

In an SLB environment with forceproxy, after configuration sync (with associated real server removed) from the master to the backup device, the device rebooted.

prod00269005

Using CLI, an incorrect description was displayed for the command /c/l3/ha/service/dis.

prod00268933

When a data port was used for NTP, and the packets were received from non-configured NTP servers, the syslog message NTP illegal packet length for the dropped NTP packets was issued.

prod00268903

In a monitoring environment, a panic occurred when continuously polling for a set of OIDs (slbStatLinkpfIpTable, pip6CurCfgTable, pip6NewCfgTable, pip6CurCfgPortTable, pip6NewCfgPortTable, pip6CurCfgVlanTable, pip6NewCfgVlanTable) with GET REQUESTs.

prod00268851

In an SLB environment, when SNI was enabled with a persistent binding (pbind) client IP address, SNI was not inserted to the back-end SSL connection.

prod00268850

In a VRRP environment, changes to a VR's priority during migration failover ended with an apply lock and high MP memory usage.

prod00268824

Even though access on a device's management port was restricted using an access-list (/cfg/sys/acces/mgmt/add), it did not work properly.

prod00268807

Using CLI, In an SLB monitoring environment, in the virtual server statistics the displayed highest sessions were greater than the total sessions.

prod00268785

In an SLB environment, when the HTTP2 policy was enabled with a group of one real server and one backup real server configured, when the active real server went down, traffic was not shifted to the real server configured as the backup, and the client received a 503 error.

prod00268700

An HTTP head host modification rule could be changed or modified using CLI but not using WBM.

prod00268687

In an SLB environment, when a FQDN real server was changed, Alteon was not updated for more than a half an hour after the change, and it changed only after the FQDN real server was disabled and then enabled.

prod00268653

In an HA environment with the same network class associated to a SmartNAT and also a real server, the ARP for a few of the PIPs in the network class range were not answered.

prod00268644

The SNMP CLI configuration commands /c/sys/ssnmp/rcomm and /c/sys/ssnmp/wcomm in accepted a NULL string, resulting in errors when adding or removing real servers from the a group using WBM.

prod00268502

In an HA with SLB environment, even though the PIP Network Class Range was enabled to receive GARP (/c/l3/ha/nwclgarp ena), the GARP was not sent for all IP addresses from the proxy network class range.

prod00268491

In an environment with health checks, when the SNMP health check was configured, the weight displayed but it did not display when the SNMP heath check was part of a LOGEXP.

prod00268450

In an OSPF environment, Alteon was unable to update the peer with any change to the OSPF parameter.

prod00268278

In an SLB environment with filter sessions, when the primary became available, even though backup clear (clrbkp) was enabled, the sessions that were bound to the backup server were not cleared on the filter.

prod00268271

When the number of basic health check components used in the logical expression-based health check object was changed, such that the new expression had fewer objects than the old expression, a software panic occurred.

prod00268234

In an SLB environment, a filter configured with the protocol as "50" was not restored after rebooting the device.

prod00268223

In an SLB environment, when a content rule group contained a remote real server with the DSSP health check, an inconsistent DSSP health check status displayed.

Note: A Config Apply action is now not allowed if the content rule group contains a remote real server with a DSSP health check and the DSSP health check is not part of the default service group.

prod00268114

Using WBM, HA Real Server Tracking could not be configured.

prod00268051

In an HA environment with an SLB configuration, configuration of the backup real server and/or backup group was not synced to the peer device.

Note: In some cases, when a backup or second backup group was configured, the diff flash sometimes displayed an internal index.This internal index did not display in the configuration and disappeared after the first save.

prod00268049

In an integrated AppWall with Alteon environment, the number of connections reached the maximum limit and AppWall stopped processing traffic.

prod00268010

When a client connected to Alteon using SSH with RADIUS authentication, a panic occurred.

prod00267973

When OCSP used DNS over management, after 64K DNS requests, failures occurred, causing Alteon to close the connection during SSL handshake.

prod00267958

In an SLB filters environment, the IPv6 redirect filter used a proxy port to forward packets to the server, but the IPv4 redirect filter did not.

prod00267950

In an SLB environment with forceproxy configured and with the HTTP2 Gateway implemented caused high SP memory usage.

prod00267929

In an SLB environment, when operationally disabling or enabling a real server in a server group, a syslog message indicating the action was not generated.

prod00267891

In an AppWall integrated with Alteon environment, when the secondary Alteon device was upgraded and traffic shifted to that device, it worked correctly for a few minutes and then after some time some of the services configured on the device stopped working.

prod00267814

When Alteon was managed with a "notacacs" and "noradius" login, the following issues occurred:

- When backdoor users logged in, permissions to change the admin password were based on the previous user login

- The who command displayed nothing or displayed the previous user's login name

- When logging in with the "noradius" user with the admin password, the user could not change the admin password

prod00267747

In an HA environment, when a proxy was configured for a filter was same as a floating IP address, the filter's proxy entries were added to the ARP table of the backup with the device MAC address without checking the HA state, causing the backup to reply to ARP queries.

prod00267744

In an SSH environment, when the export/import of configuration operations were performed using gtcfg or ptcfg, SSH sessions became permanently stuck.

prod00267715

In an HA environment, even though the configurations were the same on both the active and standby devices, a warning message related to an HA configuration mismatch was issued.

prod00267680

In a BGP environment, when deny route redistribution was disabled for a BGP peer, although the BGP peer went down and came back up, Alteon stopped sending advertisements.

prod00267677

In a virtualization environment, a vADC was accessible over HTTPS, even though HTTPS access was disabled in the configuration.

prod00267641

Using WBM, even though a user logged in with the "admin" user, the user could not operationally disable a real server.

prod00267595

When the Fastview license expired, Alteon also lost the compression license.

prod00267555

When services were moved from the master node to the backup node, no SNMP traps were sent to the Monitoring server.

Note: These traps were omitted when implementing the new feature "Extended HA".

Traps, syslog messages, and log messages have been updated, extended, or replaced with new messages.

prod00267549

In an SLB environment with forceproxy, the TCP policy/pushack worked as disabled even though it was enabled, causing a TCP retransmission problem.

prod00267351

Using WBM, when trying to set the group real server status to connection shutdown, its status kept displaying as enabled.

prod00267322

In a virtualization environment on an ADC-VX, when the API request of the default image "agDefaultImageVer" was queried, an incorrect and/or gibberish response was returned.

prod00267306

Using WBM, while monitoring the servers and being logged in as a real server operator, when trying to disable the server operational status through Application Delivery > Server Resources > Real Servers, the status of that real server did not change.

prod00267238

When performing an Apply of a configuration imported using REST API, an error was issued.

prod00267141

In an SSL environment, certificates that were set to expire after 100 years displayed as expired.

prod00267014

Using WBM, when configuring an SSL service, the certificate and the group were set and configured even when the user chose the 'any' option. This caused the newly configured APP to function slowly.

prod00266782

In an HA environment, the filter proxy were added to the ARP table with the device MAC address instead of the HA MAC address, causing Alteon to not forward dynamic NATed DNS responses to the internal DNS server.

prod00266414

Using WBM, in an SLB environment, when configuring a virtual service in the Content Rule pane, an invalid URI was accepted for the redirect URI configuration, while the CLI displayed an error message for that invalid URI.

prod00266378

In a virtualization environment on a vADC, the SP memory displayed as HIGH all of the time, while the device had no traffic and no SLB configuration.

prod00266225

Using WBM, you could modify the privacy and authentication settings for SNMP default users.

prod00265938

Pings to PIP/VPRs are now blocked.

prod00265900

In an AppWall integrated with Alteon environment, you could enable SSL for the authsrv (/c/security/websec/authsrv/ldap 1/ssl ena) even though SSL will not be used.

As a fix, this command has been removed from the CLI.

prod00265464

In an AppWall integrated HA environment with filter changes in AppWall, after running the sync, the changes were not synced.

DE24995