Release Notes : BIG-IP AAM 12.0.0

Applies To:

Show Versions Show Versions


  • 12.0.0
Release Notes
Original Publication Date: 06/01/2016 Updated Date: 04/18/2019


This release note documents the version 12.0.0 release of BIG-IP Application Acceleration Manager. You can apply the software upgrade to systems running software versions 10.1.0 (or later) or 11.x.


Platform support

This version of the software is supported on the following platforms:

Platform name Platform ID
BIG-IP 1600 C102
BIG-IP 3600 C103
BIG-IP 3900 C106
BIG-IP 6900 D104
BIG-IP 8900 D106
BIG-IP 8950 D107
BIG-IP 11000 E101
BIG-IP 11050 E102
BIG-IP 2000s, BIG-IP 2200s C112
BIG-IP 4000s, BIG-IP 4200v C113
BIG-IP 5000s, 5050s, 5200v, 5250v C109
BIG-IP 7000s, 7050s, 7055, 7200v, 7250v, 7255 D110
BIG-IP 12250v D111
BIG-IP 10150s-NEBS, 10350v (AC), 10350v-NEBS (requires 12.0.0 HF1) D112
BIG-IP 10000s, 10050s, 10055, 10200v, 10250v, 10255 D113
VIPRION B2100 Blade A109
VIPRION B2150 Blade A113
VIPRION B2250 Blade A112
VIPRION B4200, B4200N Blade A107, A111
VIPRION B4300, B4340N Blade A108, A110
VIPRION C2200 Chassis D114
VIPRION C2400 Chassis F100
VIPRION C4400, C4400N Chassis J100, J101
VIPRION C4480, C4480N Chassis J102, J103
VIPRION C4800, C4800N Chassis S100, S101
Virtual Edition (VE) Z100
vCMP Guest Z101

These platforms support various licensable combinations of product modules. This section provides general guidelines for module support.

Most of the support guidelines relate to memory. The following list applies for all memory levels:

  • vCMP supported platforms
    • VIPRION B2100, B2150, B2250, B4200, B4300, B4340N
    • BIG-IP 5200v, 7200v, 10200v

Memory: 12 GB or more

All licensable module-combinations may be run on platforms with 12 GB or more of memory, and on VE and vCMP guests provisioned with 12 GB or more of memory. Note that this does not mean that all modules may be simultaneously provisioned on all platforms with 12 GB or more of memory. The BIG-IP license for the platform determines which combination of modules are available for provisioning.

Memory: 8 GB

The following guidelines apply to the BIG-IP 2000s, 2200s, 3900, 6900 platforms, to the VIPRION B4100 and B4100N platforms, and to VE guests configured with 8 GB of memory. (A vCMP guest provisioned with 8 GB of memory has less than 8 GB of memory actually available and thus does not fit in this category.)

  • No more than three modules should be provisioned together.
  • On the 2000s and 2200s, Application Acceleration Manager (AAM) can be provisioned with only one other module.
  • In the case of Access Policy Manager (APM) and SWG together, no module other than LTM may be provisioned, and LTM provisioning must be set to None.

Memory: Less than 8 GB and more than 4 GB

The following guidelines apply to platforms, and to VE and vCMP guests provisioned with less than 8 GB and more than 4 GB of memory. (A vCMP guest provisioned with 8 GB of memory has less than 8 GB of memory actually available and thus fits in this category.)

  • No more than three modules (not including AAM) should be provisioned together.
  • Application Acceleration Manager (AAM) cannot be provisioned with any other module; AAM can only be provisioned standalone.
  • Analytics (AVR) counts towards the two module-combination limit (for platforms with less than 6.25 GB of memory).

Memory: 4 GB or less

The following guidelines apply to the BIG-IP 1600 and 3600 platforms, and to VE and vCMP guests provisioned with 4 GB or less of memory.

  • No more than two modules may be configured together.
  • AAM should not be provisioned, except as Dedicated.
  • ASM can be provisioned with this amount of memory, but a sizing exercise should be performed to ensure that it does not hit capacity issues.

VIPRION and vCMP caching and deduplication requirements

Application Acceleration Manager (AAM) supports the following functionality when configuring vCMP and VIPRION platforms.

  • AAM does not support disk-based caching functionality on vCMP platforms. AAM requires memory-based caching when configuring it to run on vCMP platforms.
  • AAM supports disk-based caching functionality on VIPRION chassis or blades.
  • AAM does not support deduplication functionality on vCMP platforms, or VIPRION chassis or blades.

vCMP memory provisioning calculations

The amount of memory provisioned to a vCMP guest is calculated using the following formula: (platform_memory- 3 GB) x (cpus_assigned_to_guest/ total_cpus).

As an example, for the B2100 with two guests, provisioned memory calculates as: (16-3) x (2/4) ~= 6.5 GB.

For certain platforms, the vCMP host can allocate a single core to a vCMP guest. However, because a single-core guest has relatively small amounts of CPU resources and allocated memory, F5 supports only the following products or product combinations for a single-core guest:
  • BIG-IP LTM standalone only
  • BIG-IP GTM standalone only
  • BIG-IP LTM and GTM combination only

Configuration utility browser support

The BIG-IP Configuration Utility supports these browsers and versions:

  • Microsoft Internet Explorer 8.x, 11.x
  • Mozilla Firefox 27.x
  • Google Chrome 32.x

BIG-IQ – BIG-IP Compatibility

SOL14592: Compatibility between BIG-IQ and BIG-IP releases provides a summary of version compatibility for specific features between the BIG-IQ system and BIG-IP releases.

User documentation for this release

For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP AAM / VE 12.0.0 Documentation page.

New in 12.0.0

There are no new features specific to Application Acceleration Manager.

Installation overview

This document covers very basic steps for installing the software. You can find complete, step-by-step installation and upgrade instructions in BIG-IP Systems: Upgrading Software, and we strongly recommend that you reference the information to ensure successful completion of the installation process.

Installation checklist

Before you begin:

  • Use BIG-IP iHealth to verify your configuration file. For more information, see SOL12878: Generating BIG-IP diagnostic data using the qkview utility.
  • Update/reactivate your system license, if needed, to ensure that you have a valid service check date.
  • Ensure that your system is running version 10.1.0 or later and is using the volumes formatting scheme.
  • Download the .iso file (if needed) from F5 Downloads to /shared/images on the source for the operation. (If you need to create this directory, use the exact name /shared/images.)
  • Configure a management port.
  • Set the console and system baud rate to 19200, if it is not already.
  • Log on as an administrator using the management port of the system you want to upgrade.
  • Boot into an installation location other than the target for the installation.
  • Save the user configuration set (UCS) in the /var/local/ucs directory on the source installation location, and copy the UCS file to a safe place on another device.
  • Log on to the standby unit, and only upgrade the active unit after the standby upgrade is satisfactory.
  • Turn off mirroring.
  • If you are running Application Acceleration Manager, set provisioning to Minimum.
  • If you are running Policy Enforcement Manager, set provisioning to Nominal.
  • If you are running Advanced Firewall Manager, set provisioning to Nominal.

Installing the software

You can install the software at the command line using the Traffic Management shell, tmsh, or in the browser-based Configuration utility using the Software Management screens, available in the System menu. Choose the installation method that best suits your environment.
Installation method Command
Install to existing volume, migrate source configuration to destination tmsh install sys software image [image name] volume [volume name]
Install from the browser-based Configuration utility Use the Software Management screens in a web browser.

Sample installation command

The following command installs version 11.2.0 to volume 3 of the main hard drive.

tmsh install sys software image BIGIP- volume HD1.3

Post-installation tasks

This document covers very basic steps for installing the software. You can find complete, step-by-step installation and upgrade instructions in BIG-IP Systems: Upgrading Software, and we strongly recommend that you reference the information to ensure successful completion of the installation process.

After the installation finishes, you must complete the following steps before the system can pass traffic.
  1. Ensure the system rebooted to the new installation location.
  2. Use BIG-IP iHealth to verify your configuration file. For more information, see SOL12878: Generating BIG-IP diagnostic data using the qkview utility.
  3. Log on to the browser-based Configuration utility.
  4. Run the Setup utility.
  5. Provision the modules.
  6. Convert any bigpipe scripts to tmsh. (Version 11.x does not support the bigpipe utility.)
Note: You can find information about running the Setup utility and provisioning the modules in the BIG-IP TMOS implementations Creating an Active-Standby Configuration Using the Setup Utility and Creating an Active-Active Configuration Using the Setup Utility.

Installation tips

  • The upgrade process installs the software on the inactive installation location that you specify. This process usually takes between three minutes and seven minutes. During the upgrade process, you see messages posted on the screen. For example, you might see a prompt asking whether to upgrade the End User Diagnostics (EUD), depending on the version you have installed. To upgrade the EUD, type yes, otherwise, type no.
  • You can check the status of an active installation operation by running the command watch tmsh show sys software, which runs the show sys software command every two seconds. Pressing Ctrl + C stops the watch feature.
  • If installation fails, you can view the log file. The system stores the installation log file as /var/log/liveinstall.log.

Upgrading from earlier versions

Your upgrade process differs depending on the version of software you are currently running.

Warning: Do not use the 10.x installation methods (the Software Management screens, the b software or tmsh sys software commands, or the image2disk utility) to install/downgrade to 9.x software or operate on partitions. Depending on the operations you perform, doing so might render the system unusable. If you need to downgrade from version 10.x to version 9.x, use the image2disk utility to format the system for partitions, and then use a version 9.x installation method described in the version 9.x release notes to install the version 9.x software.

Upgrading from version 10.1.0 (or later) or 11.x

When you upgrade from version 10.1.0 (or later) or 11.x software, you use the Software Management screens in the Configuration utility to complete these steps. To open the Software Management screens, in the navigation pane of the Configuration utility, expand System, and click Software Management. For information about using the Software Management screens, see the online help.

Upgrading from versions earlier than 10.1.0

You cannot roll forward a configuration directly to this version from BIG-IP version 4.x, or from BIG-IP versions 9.0.x through 9.6.x. You must be running version 10.1.0 software. For details about upgrading to those versions, see the release notes for the associated release.

Automatic firmware upgrades

If this version includes new firmware for your specific hardware platform, after you install and activate this version, the system might reboot additional times to perform all necessary firmware upgrades.

Fixes in 12.0.0

ID Number Description
431343 Fixed a situation where TMM may core when printing a URL processed by AAM in debug mode.
433087 Question mark in query component no longer prevents correct URL parsing.
442884 "We fixed iSession code for proper serve HUDEVT_ABORTED and HUDEVT_FLOW_INIT events. Now if HUDEVT_ABORTED arrives and HUDEVT_FLOW_INIT event was not passed up, iSession sends up HUDEVT_FLOW_INIT and forwards up HUDEVT_ABORTED only after that."
467633 Extra spaces are no longer added to the minified CSS.
474445 TMM no longer crashes when processing unexpected HTTP response in WAM.
476476 Restarting datastor no longer results in the possibility of some optimized PDFs or optimized images becoming uncacheable.
479183 Unexpected iSession tunnel state transitions are handled without causing TMM to restart or create a core file.
479889 This release resolves memory leaks that occurred when iSession and iControl were configured.
480065 Error handling during iSession tunnel reuse has been enhanced to avoid restarting TMM.
480305 Fixed iControl / iSession memory leak issue; set proper log level to prevent log flooding.
481431 Reloading AAM configuration no longer leaks memory associated with concatenation sets.
485182 The wom_verify_config now recognizes objects in sub-partitions.
486346 wamd no longer cores and now exits gracefully when shutting down.
488416 Connection pooling profiles and iSession profiles are now exclusive. Connection pooling for iSession tunnels is controlled by the connection reuse iSession profile attribute.
488917 The wamd process no longer generates potentially alarming debug log messages when shutting down.
497389 Missing virtual destructor was added.
498640 The wocplugin core assert(xb == NULL) issue has been corrected, so the wocplugin no longer restarts.
501714 The test to prevent low quality JPEGs from optimizing to higher quality (becoming larger) is fixed.
506315 When WAM/AAM policy is configured not to honor OWS maxage, it also does not honor OWS Age headers, which is correct behavior.
506557 Uncacheable updates from OWS will no longer set IBR tags to zero
509925 "TDR-2 cache size negotiation is now correct for memory-mode (disk disabled) page caches."
511534 Now, you can prevent AAM policy compilation from taking too long by turning the regular expression into plain matches using the '\' character to escape those symbols that turn a string into a regular expression. For example, previously, 'favicon.ico' was treated as a regular expression because '.' means 'any character'. Now the user can specify 'favicon\\.ico' (double '\' required by tmsh), which causes the '.' to mean the period character, thus avoiding the (unintended) regular expression.
514785 TMM no longer crashes when processing HTTP requests for certain types of AAM-optimized videos.
514838 Fix for relative paths that do not start with a forward slash, but do include parent directory references.
517567 In Acceleration :: Web Acceleration Policies objects, changes to fields now persist as expected.
521455 "Transcoded WebP images are no longer served to the Edge browser. By default, transcoded JPEG-XR is also no longer served to the Edge browser, but the db variable ccdb.allow.edge.jpegxr may be used to override this."
522231 Fix removes the condition when AAM starts to serve the response to the already aborting connection.
525478 Correctly handle requests for deflate compression of cached gzip documents with non-deflate compression methods.

Behavior changes in 12.0.0

ID Number Description
488416 Connection pooling profiles and iSession profiles are now exclusive. Connection pooling (e.g., OneConnect) profiles and iSession profiles both configure connection pooling. Beginning in this release, they have been made mutually exclusive. Connection pooling for iSession tunnels is controlled by the connection reuse iSession profile attribute. Note: Configurations with both a connection pooling profile and an iSession profile with a virtual server should be corrected before installing releases containing this profile exclusion.

Known issues

ID Number Description
222201 If you change the compression or deduplication options for the iSession profile on a BIG-IP system that is running both the WAN Optimization Module and the WebAccelerator system, you must also clear the RAM cache from the command line. To clear the RAM cache, use the command b profile http <http profilename> ramcache entry all delete. If you do not clear the RAM cache after changing these options, the WebAccelerator system may not accelerate the HTTP traffic as expected. Workaround: None.
222545 In the case of an abnormal TCP connection reset, the iSession connection is terminated and reset. While this action is transparent to the user, this action might appear in diagnostics. Workaround: None.
223434 (CR129753) For active FTP, the system changes the data ports advertised by the server, so the client might see a different port than the one originally sent by the server. For passive FTP, the system changes the data ports advertised by the client, so the server might see a different port than the one originally sent by the client. In both cases, the data transfers are successful. Workaround: None.
223624 An initial active FTP connection fails when dynamic discovery is enabled and allow routing is disabled on the remote peer. Active FTP connections are initiated from the FTP server to the FTP client. When the FTP server initiates this connection, the allow routing option of the remote endpoint is enabled. To avoid the initial failure, enable outbound connections before initiating FTP traffic. On the Remote Endpoints List screen (Acceleration > Symmetric optimization > Remote Endpoints), click the name of the remote endpoint. On the Properties screen that opens, select the Outbound Connections check box, and then click Update. Workaround: None.
342251 "If you are trying to remove the iSession connection between two peers, to prevent reconnection, you must delete the remote endpoint before you delete the local endpoint. If you are using the browser interface, the procedure is as follows: 1. On the Discovery screen (Acceleration > Remote Endpoints > Discovery), disable (clear) the settings Allow Remote Endpoints to Discover This Endpoint and Automatically save discovered Remote Endpoints. 2. On the Remote Endpoints screen, select the remote endpoint and click Delete. 3. On the Local Endpoint screen, click Delete." Workaround: None.
346536 If resources for PDF linearization become unavailable while accepting a PDF file, the linearization and connection to client will abort. No workaround is available; however, if the origin web server supplies Content-Length headers for PDF content, this condition becomes less likely. Workaround: None.
348741 If you are upgrading from 10.x to 11.x, and you are rolling over existing iSession configurations, the bzip2 compression option (enabled) is added to all existing iSession profiles. For best performance, after the upgrade, review all iSession profiles to ensure that the compression settings are correct. In some cases, you might want to disable the bzip2 compression option. Workaround: None.
348816 When rolling forward a WebAccelerator 10.x configuration to version 11.0.0, access logging configuration on the acceleration policy is not rolled forward. Workaround: To enable access logging for BIG-IP WebAccelerator version 11.0.0, please see Using the Request Logging Profile (chapter 18) in the WebAccelerator Implementations guide.
356867 Earlier versions of the BIG-IP WebAccelerator module allowed importing of identically named acceleration policies without selecting the Overwrite existing policy of the same name check box, resulting in a number appended to the imported acceleration policy name. In this version, you must select the Overwrite existing policy of the same name check box to import identically named acceleration policies. Or you can ensure the policy you are importing has a unique name. Workaround: None.
357320 For iRules associated with a virtual server that has an associated Web Acceleration profile, [CACHE::disable] can only be used if there is no WebAccelerator Application enabled in the Web Acceleration profile, and [WAM::disable] can only be used if there is a WebAccelerator Application enabled in the Web Acceleration profile. Workaround: Edit the iRules to use the correct command, either CACHE::disable or WAM::disable, for the virtual server's Web Acceleration profile.
357706 In the BIG-IP Dashboard, in the Web Acceleration view, on the Performance pane, with the Errors tab in focus, Requests bypassed due to overload shows zero statistics because the WebAccelerator module does not bypass traffic due to resource constraints. Workaround: None.
357712 The stat field proxied_per_iRule, in the stat table tmctl wam_application_stat, remains at zero. Workaround: None.
357921 The Configuration utility should provide a specific error message when an extension or MIME type for an object type is not unique, instead of a generic error message. Workaround: None.
358109 Invalidation rules on a given node are only effective in invalidating one single extension. Workaround: None.
358785 The WebAccelerator GUI displays dormant proxy rules on a node even when it is set to Always Proxy. Workaround: None.
359093 "If you want to receive an HTTP POST request and decompress it before sending it to the origin web server, and the client software sends an Expect: 100-continue header and the HTTP request-chunking mode is set to preserve, the request will not be decompressed. Specifically, the following iRule will not decompress the request in the presence of the Expect header with request-chunking set to preserve: when HTTP_REQUEST { DECOMPRESS::enable } Instead, to receive an HTTP POST request and decompress it before sending it to the origin web server, do one of the following steps: - Ensure that the client doesn't send an Expect header. - Change the request-chunking to selective, instead of preserve." Workaround: None.
359498 In tmsh, the WebAccelerator module can assemble hostnames that include IP addresses with MultiConnect prefixes, for example, wa1. In tmsh, specify zero (0) for the number of HTTP and HTTPS subdomains on any WebAccelerator hostnames that are IP addresses. Workaround: None.
359835 Deprovisioning AAM (for example, changing the provisioning level from Dedicated to None) may require a reboot, even though the reboot prompt may not be visible. Workaround: None.
360211 Invalidation rules that match on components not in the UCI will not invalidate content if it is first accessed without those components matching the rule before it is accessed with those components matching the rule. Workaround: None.
360229 If you are upgrading from 10.x to 11.x, and you receive the warning DISK MGMT REQUIRED, try rebooting the BIG-IP system. Workaround: None.
360488 Using the Configuration utility to make changes to the WebAccelerator configuration, such as deleting an Acceleration Policy or Object Type, might take up to 30 seconds to write to disk. This process can result in deleted objects reappearing in the configuration if it is reloaded immediately after making the change. Workaround: None.
361243 Under certain conditions, Adaptive Compression does not perform as well as a static algorithm. If you experience this issue, in the iSession profile you are using, disable the option Adaptive, and manually select a compression codec. Workaround: None.
361810 If two invalidation rules match the same path but have different extensions, one will match and one will not. Workaround: None.
361852 Invalidation rules that specify cached content by protocol invalidate content regardless of the protocol. Workaround: None.
361869 An invalidation rule that specifies Client IP as a condition for invalidation never matches. The trigger can match an IP; however, the content to invalidate cannot match. Workaround: None.
361875 An invalidation rule that specifies an empty or absent Query Parameter for Cached Content to Invalidate is not functional. This invalidation rule works, however, if you specify a non-empty Query Parameter value for Cached Content to Invalidate. Workaround: None.
361982 Some combinations of spaces and tabs, before and after HTTP header values, are not properly ignored and defeat invalidation that is based on those headers. Workaround: The workaround is to remove the leading/trailing whitespace from the values.
362005 A message needs to be logged when the Cache-Control header is truncated to a maximum length of 256 characters. Workaround: None.
362275 "Setting the Web Acceleration Profile to optimized-acceleration for a virtual server without enabling a WebAccelerator Application will result in an error message similar to the following: cache memory assigned to Web Acceleration profiles (6144MB) exceeds the maximum amount (697MB) defined by Ramcache.MaxMemoryPercent (50) The optimized-acceleration profile is designed for use with the WebAccelerator module. If you are not using the WebAccelerator module with your virtual server and wish to use standard cache, you should use the optimized-caching profile, or create a customized webacceleration profile that uses either the optimized-caching profile or basic webacceleration profile as the parent." Workaround: None.
363059 Renaming a top-level policy node may cause an unintended re-ordering of policy nodes, resulting in a different prioritization of matching criteria. Workaround: None.
363171 "Validation of Web Acceleration profiles can fail during a config sync when the sum of the cache sizes exceeds the Datastor volume size on the receiving BIG-IP system. For all BIG-IP systems in the Device Group: 1) Run each BIG-IP system with identical provisioning. 2) Ensure that each BIG-IP system has the same volume size for Datastor: # tmsh show sys disk application-volume datastor 3) Configure the Web Acceleration profiles. 4) Sync each BIG-IP system to the Device Group." Workaround: None.
363402 Specifying content to invalidate as the Referer header from the invalidation trigger (which specifies request-data-type referrer) is not functional. Workaround: None.
363413 Specifying content to invalidate as the User-Agent header from the invalidation trigger (which specifies request-data-type user-agent) is not functional. Workaround: None.
363699 "The WebAccelerator module Configuration utility incorrectly allows creation of nodes with reserved keyword names, which results in the configuration improperly loading the next time that the unit is rebooted or the configuration is loaded. This issue also causes config sync in a High Availability pair to fail. When creating WebAccelerator policy node names in the Configuration utility, avoid using the following reserved keywords. invalidations matching order proxy substitutions variation code description" Workaround: None.
364338 The WebAccelerator module allows the creation of Object Types that contain a space in the identifier name on the Object Types page in the Configuration utility and by using TMSH. Including a space prevents the ability to delete the object type from the Configuration utility. When you create an identifier name for an object type from the Configuration utility or in TMSH, do not include a space in the name. If you have an object whose name contains a space, you can delete it using TMSH. Workaround: None.
365600 In the BIG-IP Dashboard, in the Web Acceleration view, reporting of statistics show spikes at irregular intervals with a magnitude of 2 to 3 times the average traffic through the WebAccelerator module. This was observed for the 5-min interval window. Workaround: None.
368823 A user account restricted to a certain partition, can invalidate the cache associated with any Application, regardless of in which partition the application resides. Workaround: None.
368982 Disabling any virtual server stops traffic from passing through the BIG-IP WOM device, even though other virtual servers may be enabled. To avoid this issue, you can delete the virtual server rather than disabling it. Workaround: None.
369282 On a BIG-IP provisioned LTM/WAM nominal, when WAM is de-provisioned back to none, the load average of the system spikes to 30+ making the box basically unresponsive for roughly 5 minutes. After this time, the system appears to return to normal and the prompt status returns to REBOOT REQUIRED. Workaround: None.
369961 The space character in a path prefix is not evaluated correctly. Workaround: To work around this, use the regular expression in a path segment match.
370311 "If you create a virtual server with Type set to Reject, or change the Type setting to Reject for an existing virtual server and update the screen, when you open the screen to modify the virtual server, a second iSession Profile setting appears in the browser interface. The additional setting lacks a Context field, and has no effect on the configuration." Workaround: None.
375477 Beginning with version 11.2.0, WAM parses and IBR/MC links inside a CSS file. Four new settings "IBR-to", "IBR-within", "MC-to", and "MC-within" are added to replace "IBR" and "MC" settings at WAM policy assembly page. For custom policies that have "IBR" and "MC" enabled, "IBR-to", "IBR-within", "MC-to", and "MC-within" will be enabled too after migration to this release. In other words, WAM will IBR/MC CSS files for these policies. If you prefer not to use this feature, you must disable the settings on corresponding policy nodes. Workaround: None.
381712 In an active/standby configuration, modifying the WAN optimization codec from SDD v2 to SDD v3, or the reverse, requires that you issue a bigstart restart command on the standby BIG-IP system for the change to take affect. Workaround: None.
382629 If you update or delete an iSession self IP, and then create a new self IP before deleting the associated local endpoint and iSession listener, the local endpoint becomes unmodifiable. Workaround: To avoid this issue, delete the local endpoint and associated iSession listener before creating another self IP on the same VLAN.
382744 Exporting Excel or CSV performance monitor reports will generate a file with an unexpected extension in some browsers. In most instances the saved file will have a .do extension. The workaround is to rename the file with the correct extension. Workaround: None.
384068 When large files are served from cache, the optional X-WA-Info header may, on occasion, incorrectly contain S10205 when no invalidation/revalidation occurred. Workaround: None.
385722 If a Web Acceleration profile has more than one WebAccelerator application enabled, ESI and triggered invalidations rules in version 11.0 through 11.5 incorrectly invalidate content regardless of which WebAccelerator application cached it. Workaround: None.
392549 The Performance Monitor Data Retention Period setting for WAM application is not being recognized properly. Performance Monitor data will be removed after 30 days regardless of the retention period setting. There is no workaround. Workaround: None.
395368 When specifying the Requested Host in a Web Accelerator Application, using a port number causes IBR to not be used. Workaround: None.
398452 With successive calls to wa_clear_cache and parking enabled, it is possible that a somewhat higher than usual amount of proxying occurs the content refreshes stop and server-side throughput returns to normal. Workaround: None.
401471 Assembly parameter substitution option Query Parameter target does not recognize escaped XML entities. If the URL to be substituted has multiple query parameters, the parameters that follow the '&' may not work as expected. For example, if the URL to be substituted has a pattern of field1=x&field2=y, substitution works for both fields. However, if the URL is field1=x&amp;field2=y, substitution works for the 'field1' parameter, but does not work for the 'field2' parameter. Workaround: To work around this, include the escape sequence as part of the Query Parameter Name. In the example, a Query Parameter of 'field1=x&&amp;field2' yields the expected substitution.
401922 In a second or third request for an object (JS, CSS, Image, etc.) expected to be cached, the Content-Length header will return a larger size, causing the client to hang waiting for more data than what BIG-IP sent. LTM virtual with Web Accelerator profile configured. The http profile (LTM) must have the setting response-chunking set to other than SELECTIVE. Failed requests for objects from multiple clients. Workaround: Change the response-chunking setting to SELECTIVE in the http profile for this virtual server.
403350 "WAM uses OWS response headers if it proxies a request, and format its own response headers if it serves from cache. This could result in the inconsistent Date header value if there is clock skew between BIGIP and OWS. If this happens, we suggest OWS to use NTP server to sync their clock." Workaround: None.
415243 When HTML is requested over https, images will not be inlined into CSS that are in-turn inlined into HTML. "* Images are configured to be inlined into CSS. * CSS is in-turn configured to be inlined into HTML. * Image URL resource specified as inlining candidate, has ""http"" in the scheme part of the URI. * HTML is requested over https." Inlining is not performed for the image and hence browser requires more roundtrips to render the page. Workaround: "* Configure another entry for the same image in the URL resources section, but with ""https"" as the scheme. * Add this as a candidate for inlining on the policy node."
416733 In WebAccelerator's Symmetric Deployment mode, when configuration changes made on one device are synced to other devices in the deployment, the changes are not automatically saved to bigip.conf. Workaround: "Save the configuration manually by running tmsh save sys config on all devices in the symmetric deployment after configuration changes are made."
419617 "Configuration error like 01070734:3: Configuration error: Configuration from primary failed validation: 01070734:3: Configuration error: Policy ""/Common/IBM Tivoli Maximo Asset Management"" node ""segment"" must have ordinal greater then its base node ordinal. when editing several wam policy nodes in a single command on the command line on bladed Centaur or Puma II platforms." Bladed Centaur or Puma II platform. AAM licensed and provisioned. Attempt to edit wam policy nodes using tmsh. Workaround: On these platforms, do not create several policy nodes in a single command, or, if doing so, specify correct ordinals for each node in that command.
423204 The C-codes in the debug WA-Info codes indicate continued serving from the wrong cache. If tmm is running low on memory and the small object size limit has been increased, this is a candidate for consuming tmm memory. The small object size threshold db variable is changed from default values. Reducing or increasing the small object limit in order to free up memory or move currently cached content to datastor doesn't have the desired effect. Workaround: "To move content into datastor, temporarily reduce the number of cached objects. This will cause all small objects to be evicted; datastor content will still be available. Then increase the limit once again (it can be done immediately) and the content will be cached in datastor. There is no workaround to move currently cached content from datastor into the small object cache. Restarting datastor will flush all content including content that should remain in datastor."
426652 Deduplication does not occur and wocd daemon control connections are frequently aborted. Workaround: None.
432072 "It is not possible to add a web acceleration profile inheriting either directly or indirectly from the built-in profiles to a sync folder of a device group. An error message similar to the following is seen: 01070734:3: Configuration error: Invalid Devicegroup Reference. The profile_webacceleration (/testing/foowebaccel) requires profile_webacceleration (/Common/webacceleration) to be synced to the same devices" Attempt to add a web acceleration profile inheriting from a built in profile to a devicegroup that is synced to other devices. Config changes that create this condition (i.e. creating a webacceleration profile in a synced folder, or adding syncing to a folder containing a profile) will be rejected. Workaround: Edit bigip.conf to remove the /Common/webacceleration profile, then reload the config.
435434 When Intelligent Client cache is enabled, JS/CSS/Images are expected to be inlined. But CSS of size greater than 32k will not be inlined. "* Webacceleration is attached to the Virtual * Intelligent client cache is enabled on WAM policy * CSS size limit is set to greater than 32k * CSS optimizations are turned on - such as IBR, inlining images into CSS." Customer not getting the benefit of Intelligent client cache in this scenario. Workaround: * Turn off CSS optimizations (IBR, inlining images into CSS)
435947 Upon WAM cache lifetime expiry, when revalidating content cached in tmm memory and receiving a 304 Not Modified response from OWS, WAM sometimes serves a response with S code 10232 (as expected) but lacking an Etag, and indicates the response came from datastor, when there is no indication of the reason this occurred. WAM is configured to cache compressed static content from OWS, and OWS does not send a Last-Modified date header in the response. Without an Etag sent back to the client, WAM might get unnecessary load from clients that otherwise could perform a conditional GET with the Etag. Workaround: Configure OWS to return the Last-Modified header for content it serves.
447254 TMM core error in a previously parked transaction "* Stand-is enabled on the policy. * Request queueing is turned on in the policy * Document may have been removed from entity due to not matching policy on node." Loss of service. Workaround: * Disable stand-in and/or Request queueing
456845 WAM generated customized ETag sent to OWS. Client has content cached and sends a conditional GET. wa_clear_cache has been issued or content has been evicted from WAM cache. The ETag sent by the client in headers is sent to the OWS. Customized WA ETag makes it to the client. Assuming the server does not generated WA ETags, the behavior would be the same irrespective of whether the ETag makes it to the server or not. The expectation is to receive a 200 OK from the server so that the content can be cached by WAM. Workaround: None.
459851 The connection is aborted when using If-Match header with a Always Proxy response policy node but No Proxy request policy node. "Virtual server with Web Accelerator. GET request with Header: If-Match with strong tag. WA Policy: Node matching the request: No-Proxy Node matching the response: Always Proxy" The connection is reset when it should return 412. Workaround: None.
476460 When doing a request with multiple ranges, depending on the current state of the document in the cache (due to previous requests), WAM responds with 'HTTP 416 Requested range not satisfiable'. Client requesting more than 8 ranges in a single HTTP Range request for a document that has an active cache record. Document is not possible retrieve, even with valid range values. Workaround: Force the document to not be cached in the Policy and to be always proxied to the OWS.
517551 In some rare cases, if a document is "assembled", it can stall, giving little or no response to the client. The original document has to be smaller than the small object cache size limit, but grow to be larger than the small object cache size limit during assembly. In rare cases, this can cause the document to be unservable. Requests for that document will result in client timeouts. Workaround: Create a policy node for that specific document, and set to "proxy always."

Contacting F5 Networks

Phone: (206) 272-6888
Fax: (206) 272-6802

For additional information, please visit

Additional resources

You can find additional support resources and technical documentation through a variety of sources.

F5 Networks Technical Support

Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.


AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.

F5 DevCentral

The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.

AskF5 TechNews

Weekly HTML TechNews
The weekly TechNews HTML email includes timely information about known issues, product releases, hotfix releases, updated and new solutions, and new feature notices. To subscribe, click TechNews Subscription, complete the required fields, and click the Subscribe button. You will receive a confirmation. Unsubscribe at any time by clicking the Unsubscribe link at the bottom of the TechNews email.
Periodic plain text TechNews
F5 Networks sends a timely TechNews email any time a product or hotfix is released. (This information is always included in the next weekly HTML TechNews email.) To subscribe, send a blank email to from the email address you are using to subscribe. Unsubscribe by sending a blank email to

Legal notices