RSTP was not working properly

Interface 256 could not be selected for switch HA advertisements.

The Unit label for a rule level timeout was different between WBM and the CLI.

There was high SP memory utilization during a low traffic period.

Getting the vADC partition size failed and caused the vADC to hang on restart.

In WBM, the network class did not display, but did display in the CLI.

Could not configure filtpbkp in hot-standby mode. Modified the CLI validation to resolve the issue.

After running /stats/slb/pip, the SNMP OID was missing from the output.

VPN connectivity failed because of the IKE and the ESP sessions being bound to different servers.

Could not enter the hyphen (-) character in the New Host to Replace field on the Application Delivery > Virtual Services >Virtual Services of Selected Virtual Server > HTTP Content Modifications >HTTP Rules >URL Match & URL Action pane.

The Root Bridge was not properly declared in MSTP.

Using WBM, the hard disk capacity displayed incorrectly because secondary disk size was not counted.

SNMP walk failed because the OID did not increase.

An AppShape++ script trying to insert a script greater than 50k characters into the cmdLogMP-1-1 file caused the device to reboot.

System analytics were sent with null data.

There was an issue with FQDN and multiport applications because there was no server name for the FQDN ephemeral real server in the XML sent to AppXcel.

When setting the time zone by name and not changing the default NTP time zone, a warning is issued after the Apply.

When clsaging both is enabled with tunnels, the device rebooted.

The application services engine was not synchronized with the current configuration and the change was not saved.

In an SLB and PIP environment, there was a discrepancy in the PIP statistics between /st/slb/pip and /st/slb/aux.

The traceroute response packet was sent by Alteon with the wrong interface.