In SLB environment with APM enabled on a service, an APM script caused issues in loading the application page in the browser.

prod00249517

In a configuration with AppWall, syslog messages could not be sent for any event (such as. Security, Admin) triggered by AppWall.

prod00249340

Using WBM, from the Application Delivery > Global Traffic Redirection > DNS Redirection Rule > Client Network Rules pane, a virtual server could not be added under a GSLB client network rule.

prod00249217

In a VRRP hot standby environment, when ISL ports links went down due to some events, or the master shut down, the backup device was also triggered to go into the INIT state, and the LACP trunks of the host standby ports remained in the Blocking state.

prod00249070

In a VRRP hot standby environment, when the backup vADC processed incoming frames during the holdoff timer period, after reboot a Layer 2 loop occurred.

Note: If ISL port is down, all hot standby ports are in forwarding state to process health check packets during hold off period. So it is recommended to use "holdoff 0" to prevent network loop.

prod00249017

When upgrading with the cipher user-defined "ALL" in an SSL configuration, the configuration could not be saved after the upgrade.

prod00248984

In a Geolocation environment, when verifying the security log for AppWall in the integrated Alteon version, the Geolocation information about the attacker IP address was missing.

prod00248976

In an SLB environment with the backup group configured to the primary group, when all primary real servers reached maximum connections (maxconn), the backup server was not activated if the backup server also reached maxconn.

prod00248878

SMTP traps were not sent from Alteon at regular intervals. To solve this, the following commands were added:

The /maint/debug/stemmsglog command prints the allocated stem messages to the pool. The log level should be set to debug.

The /stats/mp/msg command has been included in the tsdump.

prod00248756

Using WBM in an SLB environment, when deleting a virtual service, and before performing the Apply, the Inbound LLB rules were incorrectly displayed.

prod00248738

In an SLB environment, when the real server connection threshold (/cfg/slb/real x/thrsh) was reached or exceeded, a log message was not generated in the log file.

prod00248704

In an SLB environment with some aged certificates, a memory leak occurred in the inspection flow, resulting in the allocation failing and the configuration was being lost on reboot.

prod00248641

In an SLB VRRP environment, when the HTTPS service (non-generic SSL) was on the backup device, and a generic SSL service when configured on the primary device and synched to backup device, the generic SSL configuration was not synchronized.

prod00248627

In WBM in a VRRP environment without AppWall enabled, when syncing the configuration a panic occurred on the master.

prod00248608

In a Global SLB environment, Alteon used the incorrect source IP address in response to DNS requests.

prod00248591

When using Web Application Firewall (WAF) with Alteon, due to a memory leak on Alteon, a panic occurred.

prod00248558

In a virtualization VRRP environment, after a configuration change on the backup ADC VX immediately followed by a change on the primary ADC VX caused a sync freeze that disrupted the communication between the vADCs.

prod00248547

In an SLB environment, disabled virtual servers associated to Layer 7 content classes caused a service and the network to go down.

prod00248428

In a VRRP environment, after configuration sync from the master to the backup, the WBM Sync button stayed highlighted on the backup platform.

prod00248351

In an SLB and new HA environment with multiple virtual servers configured with the same virtual IP address and BGP, when one virtual server was deleted or disabled, this caused the VIP entry to be withdrawn from the routine table on the BGP peer.

prod00248349

Using WBM or APSolute Vision, changes to the security level under access rights for SNMPv3 were not saved.

prod00248317

In WBM in an SLB environment, when a configured Content Rule name with the maximum character size of 32, the Content Rule name was removed after reboot. The CLI allowed 31 instead of 32 characters.

Relevant command: /cfg/slb/virt <xxx>/service 80 http/cntrules <y>/name.

prod00248314

On a 6024 platform, un an HA environment, the HA peers failed to process advertisements from each other.

prod00248159

In an SLB environment with two virtual servers with the same IP address and service, with one virtual server with the source net and another virtual server without source net configured, the persistent entries did not age out, causing a constant increase of sessions in the session table

prod00248101

In the Alteon CLI, when the command /cfg/slb/ssl/sslpol x/secreneg was executed and the user closed the session, a panic occurred.

prod00248092

In a virtualization environment, when automatic sync was enabled on a vADC and some specific configuration changes were made on the ADC VX, a sync was incorrectly initiated amongst the vADCs.

prod00248059

In an SLB environment with session mirroring enabled for all the virtual services, the session statistics were incorrect or empty on the backup peer.

prod00247988

In a basic SLB environment, when the client port was the same as the proxy port (pport) of the active ongoing SLB connection, direct access to the real server failed, causing problems with the service.

prod00247948

The following weaknesses were reported with the CVEs on Alteon with OpenSSL version 1.0.1p:

CVE-2016-6303 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6303

CVE-2016-6302 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6302

CVE-2016-2182 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2182

CVE-2016-2181 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2181

CVE-2016-2179 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2179

prod00247797

In an SLB environment with IPv4 address virtual servers and X Forward-For (XFF) enabled, even after disabling delayed binding (dbind), the platform performed dbind on the incoming connections.

prod00247745

In WBM, the Search option did not work for static routes based on IP address.

prod00247738

In a monitoring environment, LACP multicast traffic statistics displayed as unicast traffic in the port general outgoing statistics (/stats/port X/if).

prod00247731

In a DNS load-balancing environment with metric as roundrobin and with weights allocated to real server in a group, the DNS sessions were unevenly distributed between the real servers in the group.

prod00247594

In an SLB environment, when the IP address of the virtual server was also configured as a PIP under filter, the packet intermittently was not forwarded to the back-end server.

prod00247590

In version 30.5.x using the CLI, the configuration could not be imported using the SCP.

prod00247567

In an SLB environment, when performing Revert Apply and the sync dialog hung, services went down and the virtual servers were not reachable.

prod00247540

In an SSL environment, when configuring CDP URI in a CRL Group (/cfg/slb/ssl/crlgrp x) with a hostname, the following message repeatedly displayed on the console: Error: bad "<hostname>"

prod00247504

On an Alteon VA platform, deletion of the (default) VLAN 2 was allowed while it should not have, causing the apply after reboot and configuration to diff to fail.

prod00247344

In version 30.x, in an SLB monitoring environment, when a group was not associated with any virtual service, the group information (/info/slb/group) did not display its real server status, but it did in older versions.

prod00247298

Using WBM in a virtualization environment, the vADCs could not be enabled, but they could be enabled using the CLI.

prod00247233

Using WBM, when navigating to Configuration > Application Delivery > Virtual Servers, when selecting the relevant virtual server and scrolling down to the Virtual Services of Selected Virtual Server table, the Protocol column displayed incorrectly for Application IP instead of displaying TCP and UDP. The edit option also displayed incorrectly.

prod00247226

In a Global SLB environment, the GSLB metric local did not respond with the configured number of resource records even if there were records available for that particular domain.

prod00247208

In virtualization environment, when importing the configuration for an ADC VX an all vADCs, Alteon searched for non-existing vADCs in the configuration file and a syslog notice was issued.

prod00247017

When the configuration was restored by /cfg/gtcfg or through an upgrade, an invalid management port configuration displayed in the configuration dump even though the management configuration (/cfg/sys/mmgmt) was globally disabled.

prod00247015

In a virtualization environment on a vADC, when a configuration change was made and applied, when performing revert apply, the SNMP access configuration was automatically set to disabled.

prod00247003

In a Link Load Balancing environment, when using a network class to redirect traffic and more than 4096 subnets were configured, the network class was not found and the LLB did not work as expected.

prod00246976

In an SLB environment, any change to a network class or the elements within the network class caused all the virtual servers and services to reset the connections.

After the fix, changing a network class that is not attached to any service does not have an impact on services. However, any change (addition/deletion/modification) to any elements in a network class that is configured on a service results in deletion of all the session entries that relate to that service.

prod00246960

In an SLB environment with the virtual server configuration persistent bind (pbind) as clientip and delayed binding (dbind) as forceproxy, when the virtual server was deleted, the persistent sessions and PIP counter were not freed or aged out.

prod00246895

In an SSL environment with more than 256 certificates configured, accessing certificate groups through the WBM (Configuration > Application Delivery > SSL > Certificate Groups) or SNMP caused a panic.

prod00246859

Before this version, virtual services on which AppShape++ scripts are attached are always available even if all servers are down or overloaded. This is done in order to allow defining behavior when no servers are available via AS++ script (send sorry page, send redirect to another site or to a sorry server, select other group, and so on). If the virtual service would be considered down, the request would not reach AppShape++. Because there is no way to know if the AppShape++ script in fact took care of the service down case, services with AS++ scripts are also considered as up.

This can cause issues for customers who use AppShape++ scripts for other issues, especially in a GSLB environment; for example, the VIP is still advertised even though there are no active servers behind it.

The fix allows the user to define whether a virtual service is always up or not when an AppShape++ script is attached.

This parameter has no meaning when there is no AppShape++ script on the device.

The default value of the parameter is that services are not always up (disable). However, after upgrade of all services that have an AppShape++ script attached, the value must be set to keep the service always up (enable).

The parameter was added in the virtual service AppShape menu (cfg/slb/virt X/service Y/appshape) in the CLI and in the virtual service AppShape++ tab in WBM as a check box at the beginning of the tab before AppShape++ script table.

prod00246707

In an SLB monitoring environment with two virtual servers having the same IP address and the same service with delayed binding (dbind) as forceproxy and virtual statistics (vstat) enabled, the sessions did not display with /stats/slb/virt x, even though the sessions displayed in the session table.

prod00246617

In a VRRP and SLB environment, when proxy IP sync was disabled and a sync (/oper/slb/sync) was performed, because the index number of the virtual server was different for the master and backup, the sync failed between the master and backup.

prod00246506

You could access the service map using REST API without authentication (username or password).

prod00241393

When the same real server was defined in more than one virtual server, the VIP advertisement was withdrawn only when there were no connections on both virtual servers.

In addition, if one virtual server had no active connections, but the other one did have active connections, the advertisement was sent for both virtual servers.

In an environment with AppWall, the authentication requests with content length = 0 and POST multipart were not served.

US25973

In an AppWall-Alteon environment, when a caching policy was activated, there were too many error logs. The error logs have now been removed.

US25974