The management port status of eth0 and eth1 displayed incorrectly.

On an Alteon VA device, in some cases SSH and WBM connections failed due to the non-availability of free virtual memory.

The Throughput threshold license caused an error even though the high threshold had not been reached.

When accessing the tunnel meta header of a frame for non-tunnel traffic with filter reverse session support, the device rebooted.

After upgrade, running the /boot/cur command displays the image download date incorrectly.

In an Alteon SLB environment, external health checks failed when a tag was enabled on the real server port.

In WBM, the configured Server Side Idle Timeout values were not displayed.

Generating applogs resulted in high MP CPU utilization.

A new warning message regarding this is now issued when running the /maint/applog/showlog command.

Traffic was sent to a real server when the real server health check failed due to its related buddy server failing.

Features that in the background automatically created virtual servers sometimes caused the High Availability configuration to be different between the HA devices.

Changing a health check for LDAP(S) caused a reboot.

Configuration sync issued caused the device to reboot.

Bandwidth Management (BWM) did not restrict upload bandwidth.

IPC module issue caused the device to reboot.

Configuring 3044 real servers caused high MP CPU and LACP problems.

The power supply failure logs had the wrong status for the power supply.

The device ran out of Heap memory, causing it to reboot.

Syslog servers and protocol definitions were saved in the vADC configuration, but were not actually used when delegated from the ADC-VX to the vADCs.

In an SLB environment with dbind forceproxy and dbind ena, the device rebooted unexpectedly.

When generating techdata, the techdata creation failed.

Changing the SIP from network class to subnet/network in a filter was not updated in the configuration.

When configuring the action in an HTTP modification rule, the Alteon action was not validated correctly.

No data was received from Alteon for LinkProof Analytics

The device rebooted because of an issue with nsgroup auto-completion.

The device rebooted because of hardware Watchdog issues.

The DNS persistence cache cleared on Apply of GSLB changes. An alert was added to display when this occurs.

Generating tech data could take a long time.

vDirect issued an error for table SpMemUseStatsTableEntry using SNMP.

MP CPU utilization was high, causing the device to reboot.

With a BWM rate limiting contract assigned to a forceproxy service, when AppXcel sent a frame to the client/server, the contract information stored in the frame was overwritten with the default contract, causing a failure with BWM enforcement.

After changing the user role from User to Web AppSecurity Viewer without submitting the change, associating a Web application resulted in an error message which was not clear.

Importing the configuration resulted in a missing bitmap handling.

The device rebooted with the following error: SIGSEGV(11) thread STAT(tid=71)

When performing a simultaneous operation of import and apply config, changes were displaying in diff.

Defect with the Connection module handling traceroute packets.

When a packet capture running on a data port stopped, the device rebooted.

The device rebooted when executing a diff from SNMP.

In an outbound LB environment, the source port of the connections was changed, leading to traffic failure.

A random reboot was analyzed and fixed.

The database filter removed part of the refinements, and only regex refinements remained.

DE75781

There were cases (only in version 7.6.17 for a few signatures) where traffic was blocked although the signatures were refined.

DE76455

In rare cases, POST request were blocked.

DE76522

In the integrated AppWall platform, the security events were not using the correct syslog facility.

DE77260

In rare cases and under specific conditions, AppWall restarted.

DE77492

GEO blocking was conduct to false positive.

DE77880