When Alteon received the IPv6 address in full length address i.e. more than 32 characters including colons (Ex: 2101:2101:2100:2100:2101:2100:2100:2101) and processed the IPv6 fragmented packet, a panic occurred on the platform.

prod00267495

In an SLB environment with a group metric svcleastconns and multi rport scenario, the load distribution to real server was not proper.

prod00267372

When Alteon sent a zero byte just before the EOM terminating sequence of 0x0d0a2e0d0a (observed in the capture file) and the server did not answer with anything. Alteon did not receive 250 response from the server after sending e-mail contents (syslog messages).

prod00267291

After upgrading to Alteon version 32.1.x, you needed to log in two times to get access to Alteon VA, ADC-VX, or vADC.

prod00267211

In an HA environment, when performing an Alteon reset (/boot/reset) on the master device resulting in the ports being disabled, the real servers went down and Layer4 sessions were deleted from both the master device and the backup device.

prod00267147

prod00267132

In a virtualization environment, when a vADC was deleted and when a new vADC was created with the same vADC number, the old configuration was restored in the newly created vADC.

prod00267106

In an SLB environment, after the primary real server went down and the backup real server and group took over, the service became inaccessible.

prod00267073

In an inbound link load balancing Smart NAT environment, the Availability metric in the SmartNAT GSLB rule was not processed, causing an improper ISP links order.

prod00267018

When Alteon was connected to a Cisco device using a LAG (Link Aggregation Group) that had two member ports in it and the Cisco device acting as the gateway for Alteon, with STG set to on and the LACP block port was enabled, when one of the ports moved out of the LACP LAG the interface went down.

prod00266983

In a management environment, when different management certificates on the master and backup were configured (/c/sys/access/https/cert), configuration sync failed without a meaningful error message.

prod00266875

In an SLB environment with dynamic address mode with an AppShape++ script (source NAT), Alteon forwarded the traffic to the server with the source MAC address set to the client MAC address instead of the Alteon/HA MAC address.

prod00266865

In an SLB environment, when overlapping IP addresses were defined in a network class configuration with exclude enabled, and when an exclude range was a subset of the other exclude range, the filter defined with this network class fired incorrectly for an excluded IP address, causing the filter to misfire.

prod00266850

When the NTP server was configured over IPv6, the IPv6 address was not recognized on routing through the management port IPv6 address.

prod00266822

Using WBM, configured AppShape++ script did not display.

prod00266773

Using WBM, when deleting a Layer 3 gateway, the gateway entry did not disappear, but a stale entry for the same gateway ID was displayed in the disabled state and with an IP address 0.0.0.0 and VLAN 0.

prod00266748

prod00266741

In a VRRP and SLB environment with vmasport enabled, sessions mirrored back with the incorrect real server index, which led to deletion of the session on the backup device.

prod00266684

In an SLB environment with an acceleration environment, due to connections being reset, some application outages and traffic failures were observed.

prod00266631

In an SLB environment, after configuring the real server weight using the CLI command /c/slb/real x/weight, a panic occurred.

prod00266604

In Outbound Link Load Balancing environment, the transparent health check to a destination server was sent from an inappropriate port/VLAN (WAN Link).

prod00266601

While using a REST API call to export the configuration, Alteon ignored the path and name specified in the API request. Alteon generated a name and transferred the file to the root folder of the SCP server instead.

prod00266586

In a DSSP environment, after applying a configuration change, the DSSP health checks failed.

prod00266583

Using WBM, users with user roles Operator, L4 Operator, SLB Operator, and SLB Viewer could execute Apply and Save for the a configuration created by the Administrator.

prod00266582

When importing a key which is not encrypted (plain text), due to minimal passphrase that was set, the import caused all onboarding of HTTPS applications that use non-encrypted certificates to fail.

prod00266571

In a configuration sync environment, after a routine configuration change, the MP CPU reached 100%.

prod00266551

In an environment with AX configured, the primary and secondary vADCs panicked one after the other.

prod00266524

In a VRRP environment with an SLB configuration, the session move operation did not get synchronized to the backup, leading to session mirroring not working, causing statistics discrepancies on the backup devices.

prod00266500

In a Layer 7 environment, if the original request did not contain any query, Alteon did not remove the query separator "?" in the redirect URI.

prod00266438

prod00266407

Using WBM, in the Outbound LLB Rule pane, the IP address/network could not be edited.

prod00266366

When the time zone was set to Asia/Jerusalem (GMT offset +02:00), as the daylight saving setting was not taken into account, Alteon displayed the incorrect time from the month of October.

prod00266299

In a Link Load Balancing (LLB) environment, after restoring the backup configuration using get config, the LLB-related configuration (/c/slb/gslb/network x/wangrp WAN-Group-1) was lost.

prod00266258

In a monitoring environment, invalid TRAP OIDs were sent for the SP CPU Pressure On/Off.Note: The correct MIB OID has been added to the trap.c and GENERIC-TRAP-MIB.MIBs: altSwSpCpuPressureActivatedTrap - 1.3.6.1.4.1.1872.2.5.7.0.214

altSwSpCpuPressureDeactivatedTrap - 1.3.6.1.4.1.1872.2.5.7.0.215

prod00266256

Using CLI, on a vADC with a QAT SSL card, in the output from the stats/sp x/mem command, the tech support dump (tsdump) did not contain the QAT driver memory usage.

prod00266233

In a VRRP environment, when health checks failed on the backup, statistics discrepancies (incorrect number of sessions to the real servers) occurred on the backup device.

prod00266216

In an SLB environment with HA, after the failover, uneven load distribution occurred on the new master device.

prod00266153

Using WBM, In the certificate repository, when importing an intermediate CA, the size displayed as 0.

Note: After the fix, the size is not calculated and is displayed blank.

prod00266149

In an SLB environment, when there was a change in the virtual server configuration (disable/enable), the session move operation via CLI did not move the session to a different real server.

prod00266103

In a Cloud environment, when there was a VSAN failure, and when switching to redundant storage from the VMware side caused an I/O failure for a few seconds, the MP was stuck, causing the watcher to trigger the soft reboot and an outage of all Alteon VAs.

prod00266093

In an AppWall integrated with Alteon environment, although either the header name or header value was configured under Successful login detection, AppWall ignored the settings and caused unpredictable behavior.

prod00266069

Using WBM, with the "User" role, configuration sync could be performed even though the "User" account should not be able to do this.

prod00266005

In an SLB environment, when real servers were allocated to multiple virtual services and a Revert Apply was performed, the session table was deleted automatically.

prod00265997

While running a vDirect script on Alteon devices, it took more than 20 minutes to display the output or the script timed out with no result.

prod00265980

Using WBM, on an ADC-VX, when attempting to log out of WBM, the device kept the user logged in.

prod00265979

In an SSL environment, the user was unable to change the ciphers string under the advanced HTTPS health check.

prod00265899

Using WBM, from the health check pane Configuration > Application Delivery > Health Check > add , the Always Perform Health Check field displayed twice

prod00265860

Using WBM, you could not set the action as Discard for a virtual server.

prod00265856

Using WBM, in the Configuration > Setup > High Availability pane, there was no option to delete VR Group settings.

prod00265851

When performing SNMP monitoring on SSL offloading stats (FE/BE), due to a memory corruption, a panic occurred and the device rebooted a few times.

prod00265834

On Alteon non switch platforms, a panic occurred frequently.

prod00265718

In a virtualization environment for a vADC, after performing a Revert Apply on an ADC-VX, the admin password changed back to the default password (admin) on the vADC.

prod00265708

When a new virtual server with a service-based proxy address and a corresponding VPR were both configured within the same Apply operation, Alteon did not display the VPR status in the VRRP and the ARP cache.

prod00265534

In an SLB environment, if the configuration had a disabled virtual server and one of the services of the virtual server had a non-existent AppShape++ script, the configuration could not be saved.

prod00265533

When agTftpCfgFileName was more than 83 characters, exporting the configuration with SCP through the REST API server failed.

prod00265514

If the data-class entry contained a backslash (\) character and configuration sync was performed, the configuration was not synced correctly.

prod00265344

In a BGP environment, you could not import the default gateway alone or any other "range of IP"/"IP" separately.

prod00265276

When dumping the FDB entries in the SP using the /maint/debug/spfdb command, only 8K entries were dumped when the Max size of the FDB per SP was actually 16K.

prod00265208

Using WBM, from the Certificate Repository pane, you could not perform a search in the table.

prod00265197

In an SLB environment, when a MAC address was not known for a real server, even though the link was up, the link health check failed and the link did not succeed.

prod00265176

In an SNMP monitoring environment, when accessing the MIB OID 1.3.6.1.4.1.1872.2.5.4.3.14 corresponding to runtime instances of a health check, a panic occurred.

prod00265073

Using WBM, when a real server was deleted from a GSLB network, as these entries could not be reused even after deletion, once all the maximum 128 entries were exhausted, the following error message displayed: Real server precedence table is full

prod00264833

In a Global SLB environment, when the network element was of type subnet, the fromIp was incremented by 1 to skip the network address and the toIp was decremented by 1 to skip the broadcast address, causing a large value for the IP count, and Alteon prevented the subsequent network elements and network classes from being added to the internal tables. This caused a GSLB SIP lookup failure for missing network ranges.

prod00264832

In an SLB environment, filter processing processed the traffic addressed to the SmartNAT dynamic address/PIP addresses, failing the DNS amplification scan.

prod00264072

In an HA environment, when duplicate IP addresses were configured for DNS responder virtual servers and regular virtual server IP addresses on the master device, configuration sync to the peer device did not work, ending with errors.

prod00263896

In a Global SLB environment, when the network gmetric used a network class as the source IP address, the DNS response was incorrect.

prod00263894

When "Security Bypass" feature was used in the cloud WAF portal, Alteon was stuck in an inconsistent state.

prod00263487

When configured a URI under CDP group with a char of '(' in the URI for example:

http://r.q.y.v:4/CR/Ng%20GlTst%20CA%2004(3).crl,

and with traffic, a panic occurred on the platform.

prod00262698

Alteon did not handle a specific condition related to FQDN and went into an inconsistent state.

prod00262317

On the 6024 platform with 32 GB RAM, the vADC-5 license could not be installed on top of Alteon NG/NG+.

prod00259444