In WBM, the equivalent to the filterpbkp CLI command was missing.

DE59723

When the SSH connection with the correct password was attempted for a locked user, the user lockout status was checked too late.

DE60697

Using WBM, a 50X error occurred due to buffer leak in an HTTPS request.

DE60769

When resolving a DNS PTR record, IP matching was skipped (for both hostlk enabled or disabled) if the service hostname was not configured. Now, the service hostname check is skipped only if the hostlk is disabled.

DE60814

When sending an OCSP request over the management port, there were two leaks.

DE60854

When a syslog file had long log messages, the /info/sys/log command did not display any log messages.

DE60890

When the management WBM listener connection control block was closed during its validation, a 50X WBM error displayed.

DE60918

During configuration export, creating the AppWall configuration failed, and as a result the entire operation failed.

DE60954

Alteon sometimes would crash when it received the same applyfilter deletion and network class deletion that was assigned to the PIP that was defined for the real server.

DE61034

Following a set of SNMP operations, on some occasions Alteon panicked from a memory corruption with a boot reason power cycle.

DE61048

In an Alteon HA environment with an SNAT configuration in AppShape++, changing, applying, and synching non-SLB configurations resulted in the following syslog warning: Configuration is not synchronized

DE61099

If Alteon received a request when all real servers were down, the group with all the real servers' indexes less than 33 and the RR, BW, or response metric failed to select a real server, even if they came up.

DE61149

When Alteon had high MP memory utilization, restarting caused configuration loss. Alteon came up with the default configuration.

DE61210

There was no support for query type return errors even if the domain was found.

DE61257

On a 6024 standalone platform, starting with version 32.6.2.0 the maximum real servers’ value was incorrectly reduced from 8K to 1K as a result of a defect (DE61270) when moving the 6024 platform to the DPDK infrastructure.

DE61279

Accidently blocked disabled content rules with an HTTP content class to be configured on an HTTPS service without an SSL policy. It was blocked only if the content rule was enabled.

DE61347

AppWall was stuck and did not process traffic but was not restarted by the MP.

DE61469

Using WBM, when configuring the Nameserver group under DNS Authority, the table name in the mapping file was incorrect.

DE61488

Alteon did not forward traffic when LACP was disabled and worked as expected when LACP was enabled.

DE61527

Using WBM, there was a display issue when modifying a virtual service with actionredirect.

DE61604

There was no support for query type return errors even if the domain was found.

DE61646

The serial number was missing in the output for the /info/sys/general command.

DE61679

vADCs did not process SSL traffic.

DE61699

On a 4208 platform, the link was down for the 1 GB SFP port.

DE61724

There were no Mibs for the health check count to display them for the command /info/sys/capcityswitchCapHealthCheck
MaxEntswitchCapHealthCheckCurEnt.

DE61745

Alteon closed the front-end and back-end SSL connection abruptly. Fixed the classification of second request if there is content class SSL.

DE61786

When a DNS responder service was created, the user was allowed to configure parameters, which caused errors. Now the user can no longer configure parameters in this case.

DE61884

In an HA environment, synching the configuration to the peer device with sync tunnel config flag disabled results in the peer panicking.

DE62017

When the ND packet aggregation mechanism was active, a ping response was not sent immediately, resulting in a delay in the ICMP response.

DE62067

When while handling malicious DNS packet with compression pointer loops, Alteon panicked.

DE62134

Snmpbulkwalk on the capacityUsageStats node returned invalid OID output.

DE62236

Failed to access the Alteon WBM and the SSH connectivity was lost.

DE62312

After upgrading to version 31.0.13.0, uneven load balancing started.

DE62338

In a DSR and multi-rport configuration environment, the /stat/slb/virt X command returned statistics as 0.

DE62346

Actions changing the configuration (such as Apply, Save, and Diff) were incorrectly allowed for users with viewer/operator classes of service when REST requests were sent.

DE62396

Even after changing the log level from debug to error, warning messages continued to be issued.

DE62439

A ticket from a failed connection required passing over the authentication policy on the next connection.

DE62489

In rare circumstances during tsdmp or techdata export, a panic would occur.

DE62555

With specific browsers, HTTP2 traffic with an uncommon form in the header was not answered.

DE62611

Exporting a configuration from ADC-VX did not work.

DE62636

Incorrect MTU syslog messages were issued for vADCs.

DE62663

The packet capture timestamp was incorrect.

DE62734

On an ADC-VX, the HW Watchdog rarely rebooted due to an unknown trigger.

DE62751

While exporting techdata, IPv6 connectivity went down for a short while and then came back up.

DE62824

When uploading a Layer 2 packet capture from an ADC-VX to the FTP server, Alteon panicked.

DE62855

Using Ansible, could not configure the TLS 1_3 parameter.

DE62866

The WANlink current sessions count for IPv6 SmartNAT were not decremented properly due to using the wrong index. As a result, the /stat/slb/real and /stat/slb/lp/wanlink command displayed accumulated values. It has been fixed by using an appropriate index for updating the statistics.

DE62886

There was vADC auto-reboot issue because of a software panic.

DE62947

A config sync from a non-HA device to an HA-configured device caused the loss of the HA configurations.

DE62954

Health check tables were not supported for the l4 admin and slb admin users. 

DE62978

Using WBM, from the Virtual Service Monitoring perspective, the health check failure reason differed from the correct one displayed by the CLI when some of the related virtual services for the given virtual server were blocked.

DE63055

A non-supported configuration caused a crash.

DE63074

There was an Inconsistency in the current throughput per second statistics units of virtual servers.

DE63120

In an HA environment, a config sync operation with a tunnel configuration led to disruption in traffic on the peer device due to a shift in the internal tunnel indices.

DE63195

The /maint/geo/info command displayed an error message when the ISP GeoDB was not yet loaded onto Alteon.

DE63206

In Ansible, it was not possible to remove one VLAN from all interfaces because the value "0" was not accepted.

DE63213

When multiple VIPs are configured with srcnet, the ptmout value was not being considered.

DE63484

When VIRT6 went down, when deleting the IPv6 SLB virt, Alteon panicked.

DE63545

When the user changed the dbind settings to disabled along with the SSL configuration, the dbind configuration was set to forceproxy even though it was set to disabled.

DE63561

SSL statistics in the CLI and WBM did not match on Alteon running version 32.4.5.0.

DE63573

Fetching the routing table via REST API when the routing table was full caused a panic.

DE63590

When a real server had an rport set to 0 and an rport ser to x, the service became unavailable.

DE63624

After SSL Offloading was enabled, Alteon stopped accepting connections.

DE63632

LACP failed due to TX latency on the network driver.

DE63648

When a vADC management gateway was configured with an IP address other than the ADC-VX management gateway, Alteon caused an ADC-VX management connectivity issue.

DE63694

After changing the admin password and Applying, there were configuration sync issues with the peer.

DE63761

Using CLI, after running the /stats/slb/virt command, backup real servers did not display.

DE63805

After changing a group on an FQDN server, the servers were bound to the older group as well as the new group.

DE63835

After a signal panic, Alteon stopped booting.

DE63893

When HA mode was set to VRRP, VRs with some specific VRIDs were active on the backup vADC because some of the VRID bits were incorrectly used in the HAID calculation, causing the advertisements to be dropped due to a bad HAID.

DE64075

On a 9800 platform with QAT, SPTHREADS caused a panic.

DE63923

In some edge cases, AppWall did not come up because of an invalid variable that was not initialized. The fix was to initialize the variable.

DE63980

On the 4208 platform, the option to convert to virtual mode (ADC-VX) was mistakenly available.

DE64100

After Alteon received a packet and tried to open a session entry, an incorrect initialization of a pointer resulted in a NULL access and Alteon panicked.

DE64190

Alteon VA did not initiate a BGP connection to a peer.

DE64238