Applies To:

Show Versions Show Versions

Release Note: BIG-IP WebAccelerator version 11.0.0
Release Note

Original Publication Date: 08/27/2013

Summary:

This release note documents the version 11.0.0 release of BIG-IP WebAccelerator system. You can apply the software upgrade to software versions 10.x.x on multiple platforms, as defined in SOL10288: BIG-IP® software and platform support matrix.

Contents:

- Installing the software
- Features introduced in version 11.0.0
- Fixes in version 11.0.0
- Known issues
- Workarounds for known issues
     - Access logging on upgrade/ucs roll forward (ID 348816)
     - Default variation should have GET and POST different (ID 353833)
     - Not recognizing some lifetime updates (ID 354758)
     - Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 357320)
     - WA variation-matching: later cookie values don't override earlier ones (ID 357736)
     - MultiConnect should not be assembled for hostnames that are IP address (ID 359498)
     - Dual mode of WebAcceleration profile is confusing when using size settings that only WAM can use (ID 362275)
     - Asymmetric boot location population can cause WAM profile validation to fail (ID 363171)
     - WA UI allows creation of nodes with restricted keyword names (ID 363699)
     - 304 response for an unconditional GET with compression in request on node with custom object type (ID 363845)
     - UI and TMSH allow creation of object type identifier with a space in the name (ID 364338)
     - WAM dashboard throughput from cache 5 minute graph readings skewed (ID 364615)
     - wam app policy field reverts to "Select One" in WAGUI when invalid hostname attempted (ID 365374)
     - TMM crash: tmm_panic (format=0x111ad70 "umem_backstore_free: no such allocation\n") (ID 365585)
     - Contacting F5 Networks®

User documentation for this release

For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP® WebAccelerator version 11.0.0 Documentation page.


Installing the software

For complete instructions about upgrading BIG-IP Active/Standby systems, refer to BIG-IP® System: Upgrading BIG-IP® Active/Standby Systems.

For instructions about implementing new BIG-IP systems, refer to BIG-IP® TMOS: Implementations.


Features introduced in version 11.0.0

This release contains the following new features.

HTTP Compression profile
The HTTP Compression profile reduces the amount of data to be transmitted, thereby significantly reducing bandwidth usage. All of the tasks needed to configure HTTP compression on the BIG-IP system, as well as the compression software itself, are centralized on the BIG-IP system. The tasks needed to configure HTTP compression for objects in a WebAccelerator policy node are available in the WebAccelerator system, but an HTTP compression profile must be enabled for them to function.

Web Acceleration profile
When used with the WebAccelerator system, the Web Acceleration profile includes an ordered list of associated WebAccelerator applications, each of which defines the host names, IP addresses, and policy that is applied to a request that matches the specified host name or IP address.

Request Logging profile
With the Request Logging profile you can specify the data and the format for HTTP requests and responses that you want to include in a log file. If you prefer, you can tailor the information that appears in the logs so that the logs work seamlessly with whatever analysis tools you use for your origin web server's HTTP log files.

Lifetime rules
This release of the WebAccelerator system introduces design simplifications and improvements to Lifetime rules.

Interoperability for Local Traffic Manager, Global Traffic Manager, and WebAccelerator systems
This release provides the ability to provision Local Traffic Manager, Global Traffic Manager, and WebAccelerator systems concurrently.

PDF linearization
Through the Configuration utility, the WebAccelerator system provides the ability to display a requested page more quickly by using PDF linearization (optimization). PDF linearization prepares the PDF file for byte serving, which enables the WebAccelerator system to provide individual pages to a client when it receives byte-range requests.

Metadata cache responses
Because not all web applications generate ETags consistently, the WebAccelerator system creates its own ETag for each cached document that is based on a signature, or checksum, of the document's content. The WebAccelerator system stores content signatures in the Metadata cache for other optimizations, including Intelligent Browser Referencing. WebAccelerator system applications provide options to always or never send metadata.

Via headers
The Via header, configured in an HTTP profile, provides information about each intermediate router that forwards a message. Intermediate routers between a client and an origin web server use the Via header to indicate intermediate protocols and recipients.

Debug options
This setting is used for troubleshooting purposes, enabling the WebAccelerator system to optionally insert an X-WA-Info response header that includes specific codes, which describe the properties and history of the object.

WebAccelerator application performance monitoring
This release provides the ability to enable performance monitoring per WebAccelerator application. The WebAccelerator system's performance reports provide information about page requests, the frequency of those requests, and how well the WebAccelerator system serviced those requests from cache. Additionally, performance reports provide information about the application, policy, policy node, HTTP response status, S-code, size range of the response, response object type, and ID of the WebAccelerator system or browser making the request.

WebAccelerator statistics in Dashboard
The BIG-IP Dashboard provides WebAccelerator statistics with this release, including data specific to memory usage, performance metrics, throughput metrics, and cache metrics.

SNMP access
This release of the WebAccelerator system provides SNMP access. The following table includes all WebAccelerator object identifiers, object types, and a description of each. All object identifiers and object types can be found in the /usr/share/snmp/mibs/F5-BIGIP-WAM-MIB.txt file.

Object Identifier Object Type Description
1 wamAppStatName The name of the WebAccelerator application.
2 wamAppStatVsName The name of the virtual server.
3 wamAppStatRqstTotal The total number of requests made to this WebAccelerator application.
4 wamAppStatProxied The total number of requests proxied by this WebAccelerator application.
5 wamAppStatProxiedBytes The total number of requests proxied by this WebAccelerator application measured in bytes.
6 wamAppStatProxied1500 The total number of requests between 0 and 1500 bytes proxied by this WebAccelerator application.
7 wamAppStatProxied10k The total number of requests between 1500 and 10K bytes proxied by this WebAccelerator application.
8 wamAppStatProxied50k The total number of requests between 10K and 50K bytes proxied by this WebAccelerator application.
9 wamAppStatProxied100k The total number of requests between 50K and 100K bytes proxied by this WebAccelerator application.
10 wamAppStatProxied500k The total number of requests between 100K and 500K bytes proxied by this WebAccelerator application.
11 wamAppStatProxied1m The total number of requests between 500K and 1M bytes proxied by this WebAccelerator application.
12 wamAppStatProxied5m The total number of requests between 1M and 5M bytes proxied by this WebAccelerator application.
13 wamAppStatProxiedLarge The total number of requests larger than 5M bytes proxied by this WebAccelerator application.
14 wamAppStatProxiedNew The total number of new requests proxied by this WebAccelerator application.
15 wamAppStatProxiedExpired The total number of expired requests proxied by this WebAccelerator application.
16 wamAppStatProxiedPerPolicy The total number of requests proxied per policy by this WebAccelerator application.
17 wamAppStatProxiedPerIRule The total number of requests proxied per iRule by this WebAccelerator application.
18 wamAppStatProxiedPerInvalidation The total number of requests proxied per invalidation rules by this WebAccelerator application.
19 wamAppStatProxiedPerClientRequest The total number of requests proxied per headers from client request by this WebAccelerator application.
20 wamAppStatProxiedBypass The total number of proxy requests bypassed by this WebAccelerator application.
21 wamAppStatFromCache The total number of requests served from cache by this WebAccelerator application.
22 wamAppStatFromCacheBytes The total number of request bytes served from cache by this WebAccelerator application.
23 wamAppStatFromCache1500 The total number of requests between 0 and 1500 bytes served from cache by this WebAccelerator application.
24 wamAppStatFromCache10k The total number of requests between 1500 and 10K bytes served from cache by this WebAccelerator application.
25 wamAppStatFromCache50k The total number of requests between 10K and 50K bytes served from cache by this WebAccelerator application.
26 wamAppStatFromCache100k The total number of requests between 50K and 100K bytes served from cache by this WebAccelerator application.
27 wamAppStatFromCache500k The total number of requests between 100K and 500K bytes served from cache by this WebAccelerator application.
28 wamAppStatFromCache1m The total number of requests between 500K and 1M bytes served from cache by this WebAccelerator application.
29 wamAppStatFromCache5m The total number of requests between 1M and 5M bytes served from cache by this WebAccelerator application.
30 wamAppStatFromCacheLarge The total number of requests larger than 5M bytes served from cache by this WebAccelerator application.
31 wamAppStatOws2xx The number of origin web server responses in the range of 200 to 206 (successful responses).
32 wamAppStatOws3xx The number of origin web server responses in the range of 300 to 307 (redirection responses).
33 wamAppStatOws4xx The number of origin web server responses in the range of 400 to 417 (client errors).
34 wamAppStatOws5xx The number of origin web server responses in the range of 500 to 505 (server errors).
35 wamAppStatOwsDropped The number of requests dropped by origin web server.
36 wamAppStatOwsRejected The number of requests rejected by origin web server.
37 wamAppStatWam2xx The number of responses in the range of 200 to 206 (successful responses) served by this WebAccelerator application.
38 wamAppStatWam3xx The number of responses in the range of 300 to 307 (redirection responses) served by this WebAccelerator application.
39 wamAppStatWam4xx The number of responses in the range of 400 to 417 (client errors) served by this WebAccelerator application.
40 wamAppStatWam5xx The number of responses in the range of 500 to 505 (server errors) served by this WebAccelerator application.
41 wamAppStatWam503 The number of 503 response served by this WebAccelerator application.
42 wamAppStatWamDropped The number of requests dropped by this WebAccelerator application.
 

Fixes in version 11.0.0

This release includes the following fixes.

Cannot delete partitioned vip if WAM-enabled httpclass attached at creation time (ID 224993)
On a partitioned system, a virtual server could not be deleted that had an http class with WebAccelerator set to Accelerate at creation time. This issue has been resolved.

Blocking page not shown when ASM and WA are enabled in httpclass (ID 344515)
When the WebAccelerator module and Application Security Manager are enabled on the same HTTP class, the blocking page is sent to the client and no longer times out.

MultiConnect and IBR are sticky to the http/https value component originally requested with (ID 345983)
Requests for expired cached items are not recorded as expired in WebAccelerator Performance Reports if the origin web server response is 304 (Not Modified). Instead, the response is recorded in the Performance Reports as a cache hit. However, if the response from the origin web server is 200 (OK), the response is recorded in the performance reports as expired, and all subsequent re-validations, where the origin web server responds with 304 (Not Modified), are recorded as expired.

Fix signal handling so that cores are more easily analyzed (ID 351218)
Signal handling enhancements simplify WebAccelerator system troubleshooting.

No error from UI when trying to create a leafnode from a parent containing a trigger rule (ID 352257)
This version does not allow branch nodes to contain an Invalidation Rule. You can only configure Invalidation Rules on child nodes.

pvac leaks memory when policy is reloaded and invalidations exist (ID 352275)
The pvac process no longer leaks memory when WebAccelerator policies are reloaded and document invalidations exist.

On RAID'd systems, datastor gets double the disk specified by provisioning (ID 362941)
Users can use all disk space allocated to the WebAccelerator module on systems with RAID drives.

Upgrade of 10.2 polices to 11.0 not honoring the same OWS response headers (ID 363079)
After upgrading from 10.x.x to 11.0.0, you might need to ensure that the origin web server Cache-Control header directives that are selected to be honored are what you expect. For example, IBR on documents with an origin web server Cache-Control Private directive will not work if this origin web server directive is honored in a WebAccelerator policy.

Requesting PDF doc after wa_clear_cache results in S10413 bypass (ID 364439)
The first request for a PDF file after clearing the cache will no longer bypass the WebAccelerator module.

Datastor page cache needs to be increased on the smaller platforms (ID 364997)
Datastor now gets more memory for the page cache when the WebAccelerator module is provisioned.

Our ETags should be in double quotes (ID 365163)
Double quotation marks enclose entity tag (ETag) strings that are created by the WebAccelerator module.


Known issues

The BIG-IP WebAccelerator system version 11.0 release contains the following known issues. Known issues are cumulative, and include all known issues for a release.

Symmetric Deployment non-functional in WAM (ID 346062)
Symmetric deployment support for the WebAccelerator module is not available in version 11.0.0.

When resources are low, XOFF inbound PDF linearizations to catch up (ID 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.

Access logging on upgrade/ucs roll forward (ID 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. See Access logging on upgrade/ucs roll forward (ID 348816), in the Workarounds for known issues section.

Default variation should have GET and POST different (ID 353833)
When creating a new policy, instead of modifying a predefined policy, nodes are created with the Method parameter on the Variation tab set to Same Content. See Default variation should have GET and POST different (ID 353833), in the Workarounds for known issues section.

Not recognizing some lifetime updates (ID 354758)
Modified Lifetime settings for a policy node might not be applied to content already in cache. For example, a cached object that is valid for 7 days will not automatically expire if you change the Lifetime page for its matched node to 300 seconds, or if you choose to honor the origin web server max-age or s-maxage setting. See Not recognizing some lifetime updates (ID 354758), in the Workarounds for known issues section.

Expired items showing up as cached in performance reporting (ID 354983)
Requests for expired cached items are not recorded as expired in WebAccelerator Reports if the origin web server response is 304 (Not Modified). Instead, the response recorded in the Performance Reports as a cache hit. However, if the response from the web server is 200 (OK), the response is recorded in the performance reports as expired, and subsequent re-validations, where the origin web server responds with 304 (Not Modified), recorded as expired.

iRule COMPRESS::disable on HTTP_RESPONSE not taking effect on cached objects (ID 356245)
A COMPRESS::enable or COMPRESS:disable iRule does not take effect on cached items.

Policy import 'overwrite existing policy of the same name' should function like 10.x import (ID 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.

Upgrade loses unmapped hosts settings (ID 356875)
During a configuration migration, the BIG-IP version 11.0 software does not issue a warning that Unmapped Hosts elements of the WebAccelerator configuration will be lost when converting a configuration with Unmapped Hosts (forward proxy) options enabled.

Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 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. See Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 357320), in the Workarounds for known issues section.

Remove "Requests Bypassed Due to Overload" reporting in the errors tab of WA Dashboard Performance window (ID 357706)
In the BIG-IP Dashboard, in the Web Acceleration view, on the Performance pane, with the Errors tab in focus, the Requests bypassed due to overload graph shows zero statistics because the WebAccelerator module does not bypass traffic due to resource constraints.

Remove "proxied_per_iRule" from wam_application_stat from reporting to WA Dashboard (ID 357712)
The stat field proxied_per_iRule, in the stat table tmctl wam_application_stat, remains at zero.

WA variation-matching: later cookie values don't override earlier ones (ID 357736)
Matching rules for the Cookie parameter always match the first cookie. Subsequent instances of the same cookie in the request are ignored by matching. See WA variation-matching: later cookie values don't override earlier ones (ID 357736), in the Workarounds for known issues section.

Not possible to match on values that have white-space (ID 357906)
You cannot add conditions to WebAccelerator policy matching that test for white space.

WAGUI needs specific error message for extension collision between object types (ID 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.

Triggered invalidation target extension fails when multiple extensions specified (ID 358109)
Invalidation rules on a given node are only effective in invalidating one single extension.

Value of "a(b|c)d" is disaplayed as "MATCHES a(b or MATCHES c)d", but is stored as entered (ID 358530)
Various matching parameters in WebAccelerator Configuration utility that contain a regular expression with a pipe symbol (|) are incorrectly formatted for display.

Not enough memory for LTM+WAM combo on a 2GB platform (ID 358698)
The WebAccelerator module is not supported on 2GB systems.

WAGUI displays dormant proxy rules when node set to always proxy (ID 358785)
The WebAccelerator GUI displays dormant proxy rules on a node even when it is set to Always Proxy.

Symmetric Deployment is not rolled forward during upgrade or UCS install (ID 358802)
Version 11.0 does not support symmetric WebAccelerator systems. You must reconfigure symmetric WebAccelerator systems as asymmetric systems before you upgrade them from version 10.x to version 11.0.

Parameter value substitution source request URL 'relative' option ineffective (ID 358833)
For parameter value substitution, the Request URL setting for the source definition type always applies an absolute URL, even though a relative URL is specified.

Query parameter matching application/x-www-form-urlencoded not functional (ID 359062)
This version does not include query parameters in a POST body for any rules: matching, variation, proxy, or invalidation.

DECOMPRESS::enable iRule should indicate to user if no inflate compatible filters/profiles present on VIP (ID 359089)
If you configure a Web Acceleration profile for a virtual server without enabling a WebAccelerator application, an INFLATE hudfilter is unavailable, which will cause DECOMPRESS:: commands to fail.

Deflate compressed payload not inflated by DECOMPRESS::enable iRule (ID 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.


MultiConnect should not be assembled for hostnames that are IP address (ID 359498)
In TMSH, the WebAccelerator module can assemble hostnames that include IP addresses with MultiConnect prefixes, for example, wa1.10.0.0.1. See MultiConnect should not be assembled for hostnames that are IP address (ID 359498), in the Workarounds for known issues section.

Disable Normalization in WA plugin (ID 359647)
For version 11.0.0, during configuration upgrades, the software does not warn users that URL normalization and normalization-related elements of the configuration will be lost. No workaround for this issue is available.

Invalidations missed after object accessed by request not matching rule (ID 360211)
Invalidation rules that use components not in the UCI might not invalidate content if it is accessed without those components before it is accessed with those components.

Unusually long delay updating bigip.conf when saving or deleting objects in WAUI (ID 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.

pvac and comm_srv do not restart when mcpd restarts (ID 361618)
When an MCPD communication failure occurs, the WebAccelerator wamd process does not automatically restart. There is no workaround for this issue.

Log a message when fieldnames in Cache-Control headers are truncated to client (ID 361671)
Cache-Control field names are truncated to 16 characters in length. Log message not written out when field names for Cache-Control headers are truncated.

Invalidation cache-content extension effective for only one rule specifying same cache-content path (ID 361810)
If two invalidation rules match the same path but have different extensions, one will match and one will not.

Invalidation cache-content protocol ineffective (ID 361852)
Invalidation rules that specify cached content by protocol invalidate content regardless of the protocol.

Invalidation cache-content client IP non-functional (ID 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.

Invalidation cache-content various criteria as empty or absent not functional (ID 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.

Problems with pvac/wamd header matching handling leading/trailing LWS in field-values (ID 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.

Entire Cache-Control header sent to client not to exceed a maximum length (ID 362005)
A message needs to be logged when the Cache-Control header is truncated to a maximum length of 256 characters.

Dual mode of WebAcceleration profile is confusing when using size settings that only WAM can use (ID 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)
See Dual mode of WebAcceleration profile is confusing when using size settings that only WAM can use (ID 362275), in the Workarounds for known issues section.

Standin period after client requests: min-fresh and max-age not functional (ID 362862)
During the period after cached content expires according to client cache-control directive values for min-fresh or max-age, and before cached content expires according to the WebAccelerator lifetime settings, requests are proxied to the origin web server. For these requests, if standin codes are provided by the origin web server, the standin period is not invoked.

Renaming a node in the WAGUI is ineffective. Needs to be implemented (ID 363059)
Renaming a top-level policy node may cause an unintended reordering of policy nodes, resulting in a different prioritization of matching criteria.

Upgrade of 10.2 polices to 11.0 not honoring the same OWS response headers (ID 363079)
After upgrading from 10.x.x to 11.0.0, you might need to ensure that the origin web server Cache-Control header directives that are selected to be honored are what you expect. For example, IBR on documents with an origin web server Cache-Control Private directive will not work if this origin web server directive is honored in a WebAccelerator policy.

Asymmetric boot location population can cause WAM profile validation to fail (ID 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. See Asymmetric boot location population can cause WAM profile validation to fail (ID 363171), in the Workarounds for known issues section.

Invalidation request-data-type referrer is not functional (ID 363402)
Specifying content to invalidate as the Referer header from the invalidation trigger (which specifies request-data-type referrer) is not functional.

Invalidation request-data-type user-agent is not functional (ID 363413)
Specifying content to invalidate as the User-Agent header from the invalidation trigger (which specifies request-data-type user-agent) is not functional.

WA UI allows creation of nodes with restricted keyword names (ID 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. See WA UI allows creation of nodes with restricted keyword names (ID 363699), in the Workarounds for known issues section.

304 response for an unconditional GET with compression in request on node with custom obect type (ID 363845)
After changing the compression mode on a custom object type, a full GET request, for compressed content that matches a node with this custom object type, gets a 304 (Not Modified) response. See 304 response for an unconditional GET with compression in request on node with custom object type (ID 363845), in the Workarounds for known issues section.

Range extending beyond end of entity from small object cache yielding status 416 (ID 363994)
The WebAccelerator module responds with a 416 (Requested Range Not Satisfiable) status code for requests with byte ranges that have an end value that exceeds the resource length.

UI and TMSH allow creation of object type identifier with a space in the name (ID 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. See UI and TMSH allow creation of object type identifier with a space in the name (ID 364338), in the Workarounds for known issues section.

wam dashboard 'cache:entries' drawing from cache hits instead of cache count (ID 364603)
For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Cache pane, with the Entries tab in focus, the graph displays an incorrect value. The graph displays the number of cache transactions per second, instead of displaying the number of entries in cache.

WAM Dashboard throughput numbers labeled as bps, should be Bps (ID 364611)
In the BIG-IP Dashboard, in the Web Acceleration view, on the Throughput pane, the units for the graphs in the From cache and Proxied tabs are incorrectly shown as bps (bits per second). The actual units measured are Bps (bytes per second).

WAM dashboard throughput from cache 5 minute graph readings skewed (ID 364615)
In the BIG-IP Dashboard, in the Web Acceleration view, all graphs with the 5 minutes tab selected might display data with a greater value than the actual value. See WAM dashboard throughput from cache 5 minute graph readings skewed (ID 364615), in the Workarounds for known issues section.

IBR/MultiConnect metadata not clearing with wa_clear_cache when html being requested (ID 365310)
Some metadata may not be cleared by using the wa_clear_cache command. This issue is fixed.

Lack of accept-ranges on S10201 proxy causing Adobe 10.1 plugin to fail rendering PDF (ID 365337)
The WebAccelerator module does not add an Accept-Ranges header to the response when the cache misses (S code 10201).

WAM app policy field reverts to "Select One" in WAGUI when invalid hostname attempted (ID 365374)
When an invalid hostname is specified in the Requested Host field for a WebAccelerator application, the selected policy in the Policy list box reverts to Select One. See wam app policy field reverts to "Select One" in WAGUI when invalid hostname attempted (ID 365374), in the Workarounds for known issues section.

In Dashboard Performance window, reporting of From Cache levels not correct for 5min intevals (ID 365487)
For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Performance pane, with the From cache tab in focus, the 5 minutes time interval shows waveforms with levels that need to be scaled correctly.

Dashboard levels reported for Throughput "From Cache" tab incorrect for 5 min intervals (ID 365492)
For this version, in the BIG-IP Dashboard, in the Web Acceleration view, on the Throughput pane, with the Throughput tab in focus, the 5 minutes time interval shows waveforms with levels that need to be scaled correctly.

TMM crash: tmm_panic (format=0x111ad70 "umem_backstore_free: no such allocation\n") (ID 365585)
If a Web Acceleration profile is used by a virtual server and the cache size for the Web Acceleration profile is set to zero, the Traffic Management Microkernel (TMM) will crash. See TMM crash: tmm_panic (format=0x111ad70 "umem_backstore_free: no such allocation\n") (ID 365585), in the Workarounds for known issues section.

Spikes displayed in WAM Dashboard stats reporting (ID 365600)
In the BIG-IP Dashboard, in the Web Acceleration view, reporting of statistics shows 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.


Workarounds for known issues

The following section describes the workaround for the corresponding known issue listed in the previous section.

Access logging on upgrade/ucs roll forward (ID 348816)

To enable access logging for BIG-IP® WebAccelerator version 11.0.0, refer to Using the Request Logging Profile in the WebAccelerator Implementations guide. For information about this known issue, see Access logging on upgrade/ucs roll forward (ID 348816).

Default variation should have GET and POST different (ID 353833)

When creating a new policy, F5 Networks recommends setting the Method parameter on the Variation tab for GET or POST to Different Content. For information about this known issue, see Default variation should have GET and POST different (ID 353833).

Not recognizing some lifetime updates (ID 354758)

To apply modified policy settings before they expire, invalidate the cache for the applicable application. For information about this known issue, see Not recognizing some lifetime updates (ID 354758).

Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 357320)

Edit the iRules to use the correct command, either CACHE::disable or WAM::disable, for the virtual server's Web Acceleration profile. For information about this known issue, see Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 357320).

WA variation-matching: later cookie values don't override earlier ones (ID 357736)

To match subsequent instances of the same cookie in the request, create the matching rule to specify the cookie name, and match any value. For example, creating the rule with a regular expression of .* will match if the cookie name is identical and the cookie value is any value. For information about this known issue, see Requests to WAM enabled VIP which has iRule CACHE::disable on it results in iRule error (ID 357320).

MultiConnect should not be assembled for hostnames that are IP address (ID 359498)

In TMSH, specify zero (0) for the number of HTTP and HTTPS subdomains on any WebAccelerator hostnames that are IP addresses. For information about this known issue, see MultiConnect should not be assembled for hostnames that are IP address (ID 359498).

Dual mode of WebAcceleration profile is confusing when using size settings that only WAM can use (ID 362275)

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 Web Acceleration profile that uses either the optimized-caching profile or basic webacceleration profile as the parent. For information about this known issue, see Dual mode of WebAcceleration profile is confusing when using size settings that only WAM can use (ID 362275).

Asymmetric boot location population can cause WAM profile validation to fail (ID 363171)

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.

For information about this known issue, see Asymmetric boot location population can cause WAM profile validation to fail (ID 363171).

WA UI allows creation of nodes with restricted keyword names (ID 363699)

When creating WebAccelerator policy node names in the Configuration utility, avoid using the following reserved keywords.

  • invalidations
  • matching
  • order
  • proxy
  • substitutions
  • variation
  • code
  • description

For information about this known issue, see WA UI allows creation of nodes with restricted keyword names (ID 363699).

304 response for an unconditional GET with compression in request on node with custom object type (ID 363845)

After changing the compression setting on object-types, you need to clear the cache:

  • # tmsh delete ltm profile wa-cache all

This command clears the cache at the cost of losing the cache contents, causing some requests to return to the origin web server. For information about this known issue, see 304 response for an unconditional GET with compression in request on node with custom object type (ID 363845).

UI and TMSH allow creation of object type identifier with a space in the name (ID 364338)

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. For information about this known issue, see UI and TMSH allow creation of object type identifier with a space in the name (ID 364338).

WAM dashboard throughput from cache 5 minute graph readings skewed (ID 364615)

In the BIG-IP Dashboard, in the Web Acceleration view, to display data that is more accurate than the 5 minutes tab, click a tab with a different period, for example, the 3 Hours tab. For information about this known issue, see WAM dashboard throughput from cache 5 minute graph readings skewed (ID 364615).

wam app policy field reverts to "Select One" in WAGUI when invalid hostname attempted (ID 365374)

Do one of the following steps to work around this issue.

  • In the Policy list, select a policy.
  • Click Cancel.

For information about this known issue, see wam app policy field reverts to "Select One" in WAGUI when invalid hostname attempted (ID 365374).

TMM crash: tmm_panic (format=0x111ad70 "umem_backstore_free: no such allocation\n") (ID 365585)

Either delete the Web Acceleration profile or set the cache size to a value of 1 or greater. For information about this known issue, see TMM crash: tmm_panic (format=0x111ad70 "umem_backstore_free: no such allocation\n") (ID 365585).


Contacting F5 Networks®

  Phone: (206) 272-6888
Fax: (206) 272-6802
Web: http://support.f5.com
Email: support@f5.com

For additional information, please visit http://www.f5.com


This list is believed to be current as of August 17, 2011.

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)