In an SLB environment, when the client was directly connected but through different VLANs for forward and backward traffic, the SP CPU utilization became high even though the amount of traffic did not increase, causing a degradation.

prod00265556

In a Global SLB environment, when a configuration apply was executed during the periodic statistics calculation, because the internal data structures used in GSLB were reset and repopulated, an illegal access occurred, leading to a panic.

prod00265463

In a virtualization environment, when the vADC IP address/net mask combination was configured incorrectly and failed to add the relevant gateway, disabling and then enabling vADCs caused Linux ifconfig errors, resulting in the ADC-VX management losing connectivity.

Note: The issue is addressed by not allowing invalid gateway settings and ensuring that the ADC-VX and vADC management IP addresses are defined to be on the same network.

prod00265369

In a virtualization environment, when LACP was configured with 40G ports, during vADC boot-up there were many gateway health check failures.

prod00265343

In an SLB forceproxy environment with IP service and filters configured, when performing an Apply, Alteon attempted to add a service mapping entry (required for IP address and port translation) for a filter, but instead accessed data meant for a virtual service, causing a panic.

prod00265199

In an SSL environment, when configuring Client IP, SSL ID persistency, and SSL ID traffic, a panic occurred.

prod00265198

Using WBM with the Class Of Service as 'slboper', the user could perform following actions when they should have been blocked:

prod00265158

In a virtualization environment with HA configured, during upgrade one of the vADCs hung and panicked.

prod00265034

Using WBM, when logged in with a TACACS/RADIUS user, the following message displayed:

prod00265005

Using WBM, on the Layer 7 Load Balancing Content Class Configuration pane, if the content class string contained a backslash (escape characters), the Regex text field value displayed incorrectly.

prod00264997

From the Monitoring perspective, attempting to fetch the Layer 3 interface statistics using REST API did not work.

prod00264976

From the CLI menu with verbose 1 set, when a health check that is associated to a server group or real server was deleted, a prompt for user input did not display.

prod00264969

In an HA environment during configuration sync, the real server configuration under HA triggers was not synced to the peer correctly.

prod00264926

In an HA environment with session mirroring enabled after failover, the new master did not mirror sessions to the new backup.

prod00264925

In an HA environment, when a backslash ("\") character was used in the LDAP user name, the main device was not synced to the peer device. Also, WBM did not display the devices.

prod00264902

In an HA environment configured with SLB, the mirrored P-session on the backup vADC was getting bound with the incorrect real server group, causing services to get hampered.

prod00264846

In a virtualization environment, one of the vADCs hanged and panicked.

prod00264775

In an SLB environment with health checks configured, with a HTTP health check there was no difference in the failure status regardless of the failure reason. If the checked file was removed (404 code), the file required authentication (401 code) or an internal server error (500 code), For all cases, Alteon displayed the following message: Reason: Server's response is not as expected

prod00264675

On 4408 and 5208 platforms, upgrading from versions earlier than 30.2.8.0 to version 30.2.8.0 or later where in the configuration the ports were enabled for management access, the configuration was inconsistent after the upgrade.

prod00264671

In an SLB environment with AppShape++ scripts, after adding an AppShape++ script to a virtual server without creating the service on that virtual server, and then performing an apply, an apply error did not occur, and any further configuration change and apply on the virtual server resulted in the message Pending configuration displaying.

prod00264595

In a DNS environment, Alteon does not include the edns0 client subnet in the DNS response.

prod00264580

Alteon allowed management access via data ports on IPv6, even though the access was disabled.

prod00264532

When PIP was configured in a DNS-UDP stateless service, because it is not applicable it was ignored.

Note: As a fix, a warning message has been added only in CLI.

prod00264517

Image upload on the Management port using SCP was slower than with FTP.

prod00264508

In an HA environment with SLB configured, after the configuration sync, as Alteon attempted to configure the backup real server as a backup group, the backup real servers in a group on the peer device were removed.

prod00264424

In an SLB environment, incorrect statistics were displayed when fetching virtual service statistics (/stats/slb/virt). The statistics for a real server (Current, Highest, Total sessions) displayed as 0, even though the real server handled the connections.

prod00264422

In an IPv6 environment, even though IPv6 local networks were configured, Alteon sent server responses to the default gateway instead of sending them directly to the connected client. As a result, a real server could not be reached from the subnet.

prod00264377

In a forceproxy SSL environment, when MP and AX internally went out of synchronization, Alteon continued to send old certificates even after installing a new certificate.

prod00264337

Due to an SHA256 digest validation failure, the image upload using SCP failed.

prod00264278

In an HA environment, after synchronizing the configuration from the master device, the health checks for a real server failed/toggled on the backup device.

prod00264253

Using WBM, in an Inbound Link load balancing environment, the NAT address configuration was missing on the Global SLB's Client Network Rule pane.

prod00264247

Using WBM, when attempting to configure an HTTP modification for header removal, Alteon forced the user to input a header value.

prod00264243

In an SSL environment, when attempting to import the server certificate from the file containing the certificate, there was no validation to import the certificate part and it failed with a 406 error.

prod00264144

In an SLB environment when filter processing was enabled, because the VMAed traffic source MAC learning did not occur, the traffic flooded on all the ports of this VLAN, causing higher throughput utilization.

prod00264006

In an SSL environment with Cavium cards, after upgrading some certificates and performing an Apply, a panic occurred.

prod00264005

Using HTTPS, a user was not able to access the platform with the default IP address, and a 50x error was issued.

prod00263995

In a virtualization environment with HA, when p-session sync updates were received from the master, the backup attempted to become the master. The issue disappeared when p-session sync was configurationally disabled.

prod00263977

In a Global SLB environment, when the same virtual server IP address or real server IP address was part of multiple GSLB networks, the selected entries were sorted based on the created preference value and were not according to the network's preference values. As a result, the DNS response could not be controlled based on the source IP address.

prod00263895

In an HA environment, when configuration sync failed with a Global SLB/Link Load Balancing configuration, after the failure a new configuration would move automatically to the current configuration without performing an Apply.

prod00263892

For BWM-history-related e-mails, when the SMTP 'To' user was not configured and Alteon tried a number of times to send this e-mail, after a while, Alteon did not respond to SSH/HTTPS via management.

prod00263877

In an SLB environment with content rules, when the AE rebound the HTTP request based on the metric, and if the selected real server was operationally disabled, the current session statistics of real server were not decremented correctly.

prod00263857

Using the CLI, when running the command /stat/sp x/allcpu, the SP CPU statistics displayed as 0%.

prod00263833

Using the CLI, when executing a non-existing or hidden command with the /maint/pktcap menu, an error was not issued.

Note: As a fix, all the hidden commands under the /maint/pktcap menu were removed and cannot be executed.

prod00263823

In an SLB environment, after a particular sequence of SLB configuration steps involving an HTTP virtual service and another virtual server along with an Apply, the configuration became corrupted.

prod00263787

In an SLB environment, when a real server with the same IP address was configured for different groups, and each of the groups was configured with the same logical expression health check, Alteon failed to evaluate the logical expression except for the group in which the real server came up first, and the remainder of the real servers remained down in their respective groups.

prod00263771

Using WBM, when creating a new HTTP or HTTPS service, Alteon added an extra command for FTP for the service.

prod00263712

In an SLB environment, you could not configure a virtual server with a different protocol, the following error was issued: Error: Virtual server v1 has the same SIP SLB group id as virtual server v1-udp

prod00263675

In an SLB environment with multiple rports, when a new real server was created with addports and if it was associated to more than one service, if any of the service health checks was toggled, Alteon forwarded client requests to the server on the service port rather than on the real server's service port (rport = addport of the real server).

prod00263661

In the virtualization environment, when ADC-VX rebooted with a panic, the RADIUS secret became corrupted and the RADIUS login failed.

prod00263619

In an SLB environment, after enabling an SNMP health check for a group with the roundrobin metric, a panic occurred.

prod00263589

In an SLB environment, when a group was manually configured with one or more real servers, when deleting or removing the real servers from the group, the following Apply error displayed: Error: Real server group 100 associated to virtual server 100 service 80 is not defined

prod00263581

In a virtualization environment, when autosync was enabled on both the ADC-VX and vADCs, configuration changes of the primary vADC from the ADC-VX triggered the sync to loop between the vADCs.

prod00263519

In an Alteon integrated with AppWall environment and AppWall in inline mode, you could not download a 17 Mb TXT file and only partial files were downloaded, even though the same action worked while AppWall was in out-of-path mode

prod00263428

On an Alteon VA platform, even though new VLANs were defined to contain default ports, after reboot, this configuration was always pending in the diff operation.

prod00263373

In an SLB environment with APM and AppWall enabled on a service, when downloading a big HTML file, SP memory reached 100%.

prod00263313

In a VRRP active-standby configuration, when configuration sync was performed, although the corresponding virtual service was UP, the virtual router (VSR) went into the INIT state.

prod00263221

In a virtualization environment on an ADC-VX, with vadcadv enabled, when an upgrade was performed from versions earlier than 30.5.3.0/31.0.3.0 to the 32.x versions, the configuration appeared in the diff after reboot.

prod00263165

In a configuration where a client packet comes into Alteon on one VLAN (ingress), and after server processing the response packet leaves to the client on another VLAN (egress), duplicate IP FDB entries were created for external IP addresses.

prod00263126

If the IDSChain was not working for subsequent fragments or did not forward fragment IP frames that matched a filter, RADIUS Server communication broke.

prod00263100

In a SmartNAT environment, the concurrent session’s value of the WAN link server was far greater than the displayed session statistics.

prod00261498

There was a discrepancy between the peak compressions usage command output (/info/swkey) and Alteon syslog messages.

prod00261322

Due to a kernel issue, Alteon went into ULP mode and could not be accessed via Telnet, SSH, HTTP or HTTPS while the Management IP address was reachable only over ICMP.

prod00260718

Using WBM, in an SSL environment, in the Export tab, even though the certificate and key option was selected for export, only one export button displayed.

prod00258540

Note: As a fix, the following message was introduced for Cavium cards: /cfg/slb/ssl/adv/hwoffld: This command is not applicable with Cavium card

prod00258474

Using WBM for SLB monitoring, when a content rule was used with a real port, the session counter displayed incorrectly.

prod00245170

Using WBM, from the Configuration > Application Delivery > LinkProof > Inbound LLB Rules pane, there were several issues during configuration.

prod00243119

DE40272

In an SLB environment, when the system was booted from /boot/shutdown state, a Revert Apply at a later point caused the group ID under the first virtual service to become corrupt.

DE42023