In an IPv6 Hot Standby environment (where an IPv6 virtual router is configured), a panic occurred.

prod00256609

In an SLB environment with an AppShape++ script and AppWall policy attached to the virtual server, the Web page did not load after refreshing the page in the browser.

prod00256604

Shortly after configurationally enabling ports that were previously disabled, the MP CPU reached 100% and Layer 3 interfaces remained down.

prod00256438

Shortly after configurationally enabling ports that were previously disabled, the MP CPU reached 100% and Layer 3 interfaces remained down.

prod00256381

In an SLB environment with X-Forward for enabled on a virtual server and the current persistent binding mode set as cookie, intermittently the X-forward for and client IP address was not added to header.

prod00256343

In a VRRP environment with the switch group enabled, when the directly connected Master device rebooted, the backup device moved to the INIT state rather than changing state to Master.

prod00256308

In an SLB environment, when gateway per VLAN was enabled and operational, client traffic was forwarded to a switch port on which the VLAN gateway was learned rather than forwarding to the default gateway, causing client traffic to fail.

prod00256305

In a monitoring environment with TACACS and command logging enabled, when executed the global commands together with a slash i.e. "apply/save", a panic occurred on the platform.

prod00256269

In an SLB environment with some of the real servers containing multiple services (with the same IP address but different ports), if the ARP resolution did not yet finish, only the first health check towards that real server would get queued up, while the rest were discarded, resulting in the real server health check flapping.

prod00256171

In a Global SLB environment, when a DSSP health check is configured as part of logical expression, the logical expression (logexp) health check did not work as expected.

prod00256104

As a fix, a validation has been added during the apply operation to not have same IP address on the virtual server and the real server.

prod00256101

When using an APSolute Vision version 3.80.00 VM to configure Alteon, when performing an Apply or Save operation, errors occurred.

prod00256097

Using the CLI, when trying to execute the command '/cfg/slb/gslb/dssphc", the following error message was not generated, as expected:

prod00256080

Using WBM, the wrong number of Network Subnets within a Network Class displayed.

prod00256039

Using WBM, when the UI timed out, the browser displayed the 'Authentication Required' pop-up to log in again, but also displayed a Configuration Error - The server is busy processing requests window.

prod00256037

In a Global SLB environment on all user interfaces, uploading the GeoLite2 data base resulted in "406 Not Acceptable".

prod00256020

In WBM, the HTTP HOST header value was used when redirecting the WBM request for "/" to the "/webui/default.html" path, incorrectly indicating an HTTP host header attack vulnerability.

prod00256016

When executing a Revert Apply, the port links toggled, disturbing the data traffic.

prod00255974

In an AppWall integrated with Alteon environment, the AppWall module logs failed to send syslog messages on the configured Alteon port (other than the default port).

prod00255958

Using the CLI, when pressing Tab to view the command syntax, the output was displayed on the same line instead of the next line.

prod00255944

Commands have been added to the configure IP Fragmentation table size (/c/l3/fragtble) and to clear fragmentation table statistics (/oper/l3/ipfrgclr).

prod00255911

Using WBM, when accessing the virtual services Create/Edit a Virtual Server pane, an IP address with 255 in the last octet (x.x.x.255) resulted in a validation error message.

prod00255880

In an SLB environment, the SIPOPTIONS health check failed and caused a service outage.

prod00255846

In High Availability Switch mode, on a backup device working as the DHCP relay, a MAC flap occurred.

prod00255842

In a BGP environment, during BGP state change, SNMP traps were not generated.

prod00255839

When vDirect Automation was run, traffic stopped going through Alteon.

prod00255800

When the SNMP community string contained the @ symbol followed by any three (3) characters, the SNMP query failed, causing APSolute Vision to not add an Alteon device.

prod00255757

In an SLB environment with an AppShape++ script configured, when a new group was configured and saved using WBM, after performing a Revert Apply operation, client requests were forwarded to a different real server rather than to the real server attached to the AppShape++ script.

prod00255713

In an SLB environment with AppXcel (where delayed binding (dbind) set to forceproxy mode), the expected behavior of sending a client's ICMP error packets to the server without any source NAT caused a client MAC flapping issue on an adjacent Layer 2 device.

prod00255662

The fix now accepts /c/sys/syslog/hst1 0.0.0.0 7 0 all 0 to delete the syslog host configuration.

prod00255621

In an HA environment with data class configured, when performing configuration sync, the data class configuration was not synced while the rest of the configuration was.

prod00255467

In an SIP SLB environment, when the SIP content-length was incorrect, Alteon stopped forwarding SIP messages.

prod00255411

In FTP Active mode, due to an endian issue when performing TCP sequence adjustments for retransmitted PORT command packets, clients experienced FTP communication failures.

prod00255390

In a Link Load Balancing (LLB) environment, during client processing of the ICMP destination with an unreachable packet containing a payload matching an outbound-LLB session, a panic occurred.

prod00255311

In an SLB environment, when both nonat and rport were configured for a DNS service, nonat overrode the rport settings, causing packets to be sent to the real server without modifying the rport configuration.

prod00255261

In an SLB environment with the metric set to phash, when requests arrived from a few specific client IP addresses, Alteon failed to distribute the traffic among the real servers.

prod00255226

In an SLB environment with acceleration, if a caching policy was associated with a service, the persistency timeout (/c/slb/virt 1/service 80/ptmout X) was ignored and the persistency entry was created only after 10 minutes of timeout.

prod00255203

When the security configuration was set to /c/security/websec/authsrv/ldap <n>/base xyz, and a sync was performed or the device was rebooted, this configuration was lost.

prod00255197

When processing SSL data from the WBM client over the management port, a panic occurred.

prod00255158

In an AppWall integrated on Alteon environment, you could access the AppWall configuration even though no AppWall license was installed.

prod00255121

In an SLB environment, using the REST API, when configuring other applications, reserved ports reserved ports such as 20, 21, 69, 389, and 5060 were allowed.

prod00255070

In an IPv6 environment with link local address configured, connection to device with an IPv6 gateway address did not work.

prod00255054

Using the CLI, while configuring an LDAP health check, the usage/guidance message for the LDAP bind input was not clear, leading to misconfigured input.

prod00255049

When the default gateway ARP entry aged out and health check instances attempted to send a TCP SYN to real servers, an ARP burst for the default gateway flooded the network.

prod00255045

For servers indirectly connected to Alteon, the Maximum Segment Size (MSS) was set to 536 in the TCP header, causing servers to segment their large-sized packets.

prod00255000

In a BGP environment with VIP advertisement send enabled (/cfg/l3/bgp/vipa e) and the virtual server configurationally disabled, if the virtual server had active sessions, it was not removed from the ARP and routing tables.

prod00254987

When attempting to log in through a TACACS server, after a few unsuccessful login attempts Alteon rebooted.

prod00254981

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.

prod00254978

During configuration synchronization, when configuring a real server with the name and ID greater than 32 bytes, when the real server was synced to a peer device, a dummy real server was also created.

prod00254923

In a Layer 7 SLB environment, when a non-existent Web application was associated with a content class, even though the content class was in the disabled state, after performing an Apply a panic occurred.

prod00254841

Note: By default, fovdelay is disabled. The command can be enabled only if hot standby is also enabled (/cfg/l3/vrrp/hotstand e).

prod00254831

In an SLB environment, when the real server ID definition was very long, configuration synchronization did not work.

prod00254812

In a SIP SLB environment with forceproxy, the SIP packets were dropped, even with very low traffic.

prod00254798

In SLB environment using REST API, real server statistics using the API command SlbStatEnhContRuleActionGroupTable did not display all the information properly.

prod00254759

In an SLB environment, even though the gateway mentioned in the ICMP packet was not in the subnet of the real server, Alteon forwarded (load-balanced) ICMP redirects (ICMP Type 5, Code 1 / redirect for host) to the real server.

prod00254440

In an SLB environment, when attempting to configure two different virtual servers with same the SERVICE port, the same VIP, and a unique source network, the following error displayed:

prod00253836

In a virtualization environment on an ADC-VX using WBM, after importing the WBM certificate, key, and intermCA, there were issues with the diff display and the Certificate Repository displayed nothing in WBM.

prod00253613

During proxy processing, SLB's (VIRT/FILT) server traffic returning to the PIP address is classified, and this classification is used in the server processing.

prod00253260

Using WBM, both the techdata and packet capture exports caused health checks to stop for a long interval.

prod00253174

The OpenSSL version has now been upgraded to version 1.0.2.

prod00251523

The OpenSSL version has now been upgraded to version 1.0.2.

prod00251521

Using WBM, In an SLB environment with SSL certificates, a user with the username crtadmin could not be used to log in to the device, although it worked using CLI.

prod00248567

In an SLB environment, the IDS servers could not be configured without an IP address, and an error displayed during Apply.

prod00244588

When the RADIUS server was down, when logging in to or logging out from RADIUS through Alteon, a panic occurred.

DE27909

When an HTTP parsing failure occurred, an incorrect security event message displayed.

DE24622

Under certain conditions, the options “Support Base 64 Data” and “Support XML Data” within the database filter became disabled although they had been enabled.

DE23364

The HTTP parser blocked requests with a double slash in the URL without any security event.

DE25505

When changing the Cluster Manager’s management IP address, policy sync between the nodes and the Cluster Manager failed.

DE24408

The AppWall disk partition became full due to an unmanaged log file.

DE25918

When connecting with TACACS to AppWall, the Administration Event in Forensics did not display the login name.

DE27516

In a first time configuration change after the Alteon upgrade process, a failure sometimes occurred in the AppWall configuration file once changes were applied.

DE27962

Different AppWall instances running on the Alteon platform sent logs to APSolute Vision with different hostnames, but with the same management IP address.

DE28056

The AppWall Management application failed after creating a complex RegEx in the security policies settings.

DE28086

The hostname field truncated in the logs sent to APSolute Vision.

DE28456

Under certain conditions, AppWall sent messages to APSolute Vision with the wrong destination IP address in the message.

DE28650

Under certain conditions, the tunnel name was not properly imported during an import process.

DE28721