Applies To:

Show Versions Show Versions

Release Note: BIG-IP WebAccelerator version 10.2.4
Release Note

Original Publication Date: 08/27/2013

Summary:

This release note documents the version 10.2.4 release of BIG-IP WebAccelerator system.

Contents:

- Supported hardware
- Supported system configuration files
- User documentation for this release
- New in 10.2.4
- New in 10.2.3
- New in 10.2.2
- New in 10.2.1
- New in 10.2.0
- Installation overview
     - Installation checklist
     - Installing the software
     - Post-installation tasks
     - Installation tips
- Upgrading from earlier versions
- Fixes in 10.2.4
- Fixes in 10.2.3
- Fixes in 10.2.2
- Fixes in 10.2.1
- Fixes in 10.2.0
- Known issues
- Optional configuration changes
     - Enabling the Accept-Encoding gzip feature
     - Enabling the half-closed TCP connection management feature
- Contacting F5 Networks
- Legal notices

Summary WA 10.2.4

Supported hardware

You can apply the software upgrade to systems running software versions 9.4.x and 10.x. For a list of supported platforms, see SOL9412: The BIG-IP release matrix. For information about which platforms support which module combinations, see SOL10288: BIG-IP software and platform support matrix.

Supported system configuration files

When upgrading from version 9.4.x to version 10.2.x, the BIG-IP WebAccelerator system replaces the /config/wa/pvsystem.conf configuration file with the version 10.2.x default configuration and saves the previous version's configuration file as /config/wa/pvsystem.conf.9.4.x. If you modified the default 9.4.x configuration and want to apply the same changes to version 10.2.x, you must edit the new /config/wa/pvsystem.conf as required. For specific information about how to modify the pvsystem.conf file, refer to the Changing Default Settings chapter of the Configuration Guide for the BIG-IP WebAccelerator System.

User documentation for this release

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

New in 10.2.4

This release contains no new WebAccelerator features.

New in 10.2.3

This release contains no new WebAccelerator features.

New in 10.2.2

This release contains no new WebAccelerator features.

New in 10.2.1

This release contains no new WebAccelerator features.

New in 10.2.0

Integrated WebAccelerator Configuration utility

Previously, the WebAccelerator Configuration utility opened in a secondary window. The WebAccelerator Configuration utility is now fully integrated into the BIG-IP Configuration utility.

Installation overview

This document lists only the very basic steps for installing the software. The BIG-IP Systems: Getting Started Guide contains details and step-by-step instructions for completing an installation. F5 recommends that you consult the getting started guide for all installation operations.

Installation checklist

Before you begin:

  • If using partitions, reformat for the 10.1.0 and later partition size, if needed (partitions created using version 9.x or 10.0.x do not accommodate the 10.1.0 and later software).
  • Reactivate the license and update the service contract.
  • 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 upgrading from version 9.3.x or 9.4.x, run im <downloaded_filename.iso> to copy over the new installation utility.
  • If you are running WAN Optimization Manager, set provisioning to Minimum.

Installing the software

F5 offers several installation methods. Choose the method that best suits your environment.
Warning: Do not use the --nomoveconfig option described in the following table on systems with existing, running installations of Application Security Manager. Doing so removes all content from the associated database. Instead, ensure that the configuration on the source installation location matches the one on the destination. To do so, save the UCS configuration on the location you want to preserve, and apply that configuration to the destination before or after the installation operation.

To install the software, use one of the methods described here.

Install method Command
Format for volumes, migrate source configuration to destination image2disk --format=volumes <downloaded_filename.iso>
Format for volumes, preserve destination configuration (for fully 10.x environments) image2disk --nomoveconfig --format=volumes <downloaded_filename.iso>
Install without formatting (not for first-time 10.x installation) bigpipe software desired HD.<n.n> version 10.x build <nnnn.n>.iso product BIG-IP
Format for partitions (for mixed 9.x and 10.x environments) image2disk --format=partitions <downloaded_filename.iso>
Install from the browser-based Configuration utility Use the Software Management screens in a web browser.

Post-installation tasks

This document lists only the very basic steps for installing the software. The BIG-IP Systems: Getting Started Guide contains details and step-by-step instructions for completing an installation. F5 recommends that you consult the getting started guide for all installation operations.

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. Log on to the browser-based Configuration utility.
  3. Run the Setup utility.
  4. Provision the modules.

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 view a list of the image2disk utility options by running the command image2disk --help.
  • 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. For image2disk installations, the system logs messages to the file you specify using the --t option. For other installations, 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. Software version 10.x introduced the ability to run multiple modules based on platform. The number and type of modules that can be run simultaneously is strictly enforced through licensing. For more information, see SOL10288: BIG-IP software and platform support matrix.

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 9.6.x or 10.x

When you upgrade from software version 9.6.x or 10.x, you can 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, or the relevant chapters in the BIG-IP Systems: Getting Started Guide.

Important: Upgrading a version 9.6.x platform to version 10.x also performs a BIOS upgrade. (You can find more information in the following Solution: SOL10633: BIOS update may be required before installing BIG-IP version 10.1.0 or later on the VIPRION platform.) If you also apply a version 10.x hotfix when you attempt the software upgrade, the operation fails to install the new BIOS. This can cause additional issues. For more information, see SOL10548: The BIOS of the VIPRION platform is not upgraded when installing BIG-IP version 10.0.x and a hotfix in a single step and SOL10016: A VIPRION kernel panic occurs following an upgrade to BIG-IP version 10.x.

Upgrading from version 9.3.x or 9.4.x

If you plan to install this version of the software onto a system running 9.3.x or 9.4.x, you must perform a one-time upgrade procedure to make your system ready for the new installation process. When you update from software version 9.3.x or 9.4.x to 10.x, you cannot use the Software Management screens in the Configuration utility. Instead, you must run the image2disk utility on the command line. For information about using the image2disk utility, see the BIG-IP Systems: Getting Started Guide.

Upgrading from versions earlier than 9.3.x

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.2.x. You must be running software version 9.3.x, 9.4.x, 9.6.x, or 10.x. For details about upgrading to those versions, see the release notes for the associated release.

Important: Beginning with version 10.0.0 of the software, a redundant system configuration must contain failover peer management addresses for each unit. If you roll forward a redundant system configuration from 9.3.x or 9.4.x, the units start up in an offline state because each one needs a failover peer management address. To configure the failover peer management addresses, navigate to System > High Availability > Network Failover , and specify the management IP address of the peer unit in the Peer Management Address field. Then do the same on the other unit in the configuration. Once you specify both IP addresses, the system should operate as expected. For more information, see SOL9947: Change in Behavior: The Peer Management Address setting is required for BIG-IP version 10.x systems configured for network failover.

Fixes in 10.2.4

This BIG-IP WebAccelerator release includes all previously released hot fixes.

ID Number Description
ID 327077 pv_ntlm_auth cookie with a control character (ASCII values 0 to 31) are no longer erroneously presented to the OWS.
ID 371551 IBR now correctly handles included files that are preceded by a tab character.
ID 373368 This release corrects a condition in which invalidation rules could be erroneously re-applied when PVAC receives a HUP signal.

Fixes in 10.2.3

This BIG-IP WebAccelerator release includes all previously released hot fixes.

ID Number Description
ID 366511 WAM now correctly restrains the number of ranges in a request preventing a PVAC out of memory condition.

Fixes in 10.2.2

This BIG-IP WebAccelerator release includes all previously released hot fixes.

ID Number Description
ID 353823 This release fixes a defect that corrupted memory, which caused the pvac daemon to abort.

Fixes in 10.2.1

This BIG-IP WebAccelerator release includes all previously released hot fixes.

This release contains no new fixes.

Fixes in 10.2.0

This BIG-IP WebAccelerator release includes all previously released hot fixes.

ID Number Description
CR134226 ESI inline statements are served from the default BIG-IP Local Traffic Manager pool when the base page is requested by the WebAccelerator system. By default, the WebAccelerator system constructs the inline proxy request with the default pool member's IP as host. This functionality now supports external ESI content, as well. The content record stores the details of the host that served the content. Additionally, a DNS lookup for the host is included in the inline statement.

Known issues

ID Number Description
CR76031 If you make changes to the http-acceleration profile settings, Minimum Object Size, Maximum Object Size, URI Caching, and Ignore Headers, it adversely affects the way the BIG-IP WebAccelerator system manages HTTP traffic for your site. You should not modify these settings. For more information about the default settings, refer to SOL8780: The default RAM Cache settings for the http-acceleration profile should not be modified.
CR80537 The BIG-IP WebAccelerator system does not currently support the Basic and Digest Access Authentication schemes. To ensure that clients receive properly authenticated content, enable the proxying rule option, Always proxy requests for this node, for the acceleration policy that is assigned to the application that is using Basic and Digest Access Authentication schemes. To enable the always proxy option, select the node on the Policy Tree. Then, from the Matching Rules list on the Policy Editor menu bar, select Acceleration Rules, and then click Proxying. Finally, in the Proxying Options section on the Proxying rules screen, click the button next to Always proxy requests for this node. For the new policy to be in effect for your site, you must publish it. For more information, see Chapter 3, Using Acceleration Policies, in the Policy Management Guide for the BIG-IP WebAccelerator System. Once you publish the acceleration policy, the BIG-IP WebAccelerator system sends all matched requests to the origin server for content.
CR80763 If the comm_srv system process is down on a BIG-IP WebAccelerator system in a symmetrical deployment, and you make changes to other BIG-IP WebAccelerator systems in the symmetrical deployment, the configuration changes may not synchronize properly.
CR80878 In a symmetric deployment of BIG-IP WebAccelerator systems, a BIG-IP Local Traffic Manager HTTP monitor on the remote WebAccelerator system does not properly report the status of the origin web server located behind the central WebAccelerator system. To work around this issue, monitor the status of the origin web server, through the BIG-IP Local Traffic Manager's HTTP monitor, only on the central WebAccelerator system. For more information about configuring and using HTTP monitors, see the Configuration Guide for BIG-IP Local Traffic Manager.
CR81083 Destination hosts are not supported for BIG-IP WebAccelerator systems in symmetric deployments. To use destination hosts, you must configure pools through the BIG-IP Local Traffic Manager. For information about configuring pools, see the Configuration Guide for BIG-IP Local Traffic Manager.
CR81084 When configured in a symmetrical deployment, the BIG-IP WebAccelerator system does not properly process requests for unmapped hosts.
CR81333 If you modify a user-defined acceleration policy on a BIG-IP WebAccelerator systems in a symmetrical deployment, and you do not publish the policy before you synchronize the configuration, your changes may be lost. To avoid losing configuration changes to user-defined acceleration policies, always publish the policy you changed before you synchronize the BIG-IP WebAccelerator systems in a symmetrical deployment.
CR81698 The hit log does not currently report statistics for documents on which the BIG-IP WebAccelerator system has performed URL normalization.
CR81829 The logging feature does not currently report requests that the BIG-IP WebAccelerator system has served from Hot Cache (previously known as RAM Cache).
CR85606 If you remove an HTTP class profile from the BIG-IP Local Traffic Manager system's virtual server's resources, the BIG-IP WebAccelerator system may continue to accelerate traffic. To resolve this issue, restart the pvac service using the bigstart restart pvac command. Traffic flow may momentarily halt while the service restarts.
CR95401 The WebAccelerator system performs PDF linearization on all PDF documents. This setting cannot currently be changed through the user interface, but can be changed by modifying the globalfragment.xml file.
CR105976 If you provision or de-provision the WebAccelerator system, the Configuration utility restarts. During this time the Configuration utility is temporarily unavailable. Once the Configuration utility has restarted, it prompts you to continue.
CR106567 When running on a platform with multiple CPUs, the WebAccelerator system may serve responses only from Smart Cache (indicated by the S10101 code in the X-PvInfo header), until the Hot Cache associated with each CPU is populated. Platforms with multiple CPUs include: 3600, 3900, 6400, 6800, 6900, 8400, 8800, and 8900.
CR106990 If you import an acceleration policy when the /shared file system is full, the acceleration policy appears on the Policies screen, but does not appear in the policies list for an application; therefore, you cannot assign the imported policy to an application. To resolve this issue, free additional space in the /shared file system.
CR107173 If you modify the same acceleration policy on both the remote and central WebAccelerator systems in a symmetric deployment and then attempt to publish them simultaneously, the WebAccelerator system returns an exception error.
CR108671 If you manually invalidate cached content for unmapped hosts, the WebAccelerator system invalidates cached content for all applications.
CR110577 If you change the time on the system clock, the WebAccelerator services pvac and comm_srv may restart, temporarily halting traffic to your applications. In order for you to avoid this issue, F5 Networks recommends that you change the system clock only when the WebAccelerator system is offline and not processing requests.
CR123170 If you enable the Compression setting for the http-acceleration profile, the BIG-IP WebAccelerator system no longer compresses content, regardless of the acceleration policy settings. To avoid this issue, do not modify the http-acceleration profile's Compression setting.
CR128875 If you perform an operation that requires loading the configuration on a volume that has insufficient disk space to contain it, the operation fails at the module-provisioning step. Depending on the modules you provision and the space available, the failure might occur when rolling forward a configuration at installation, running bigpipe config install <config.ucs>, or provisioning modules in a command line operation. When the provisioning failure occurs, the system logs a message in the /var/log/ltm file: 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. MB are required to provision these modules, but only MB are available.' To recover, free up sufficient disk space by removing unneeded volumes using the command: bigpipe software desired HDn.n delete, and then try the operation again.
CR132771 If you create a virtual server enabled for WebAccelerator Module that does not use the pre-defined http-acceleration profile, you cannot invalidate the web application defined for the virtual server.
CR134815 The Frame setting for URL Normalization Method on the URL Normalization page does not function and is deprecated.
CR136453-1 If you run the wa_clear_cache script to delete the WebAccelerator disk cache while hds_prune is pruning the cache, the hds_prune process can fail and restart. To avoid this issue, shut down hds_prune before running the wa_clear_cache script.
CR137225 When a PNG file contains a highly compressed ancillary chunk, libpng can stall or fail.
CR137453 When the system is booting from version 10.1 to 10.2, the Policy Editor appears blank on the left side, except for a small rectangular bar at the very top of the policy navigation tree area. To correct this problem, refresh the policy navigation tree, or close and reopen all browser windows.
CR137545 When the WebAccelerator system processes ESI markup tags with a short lifetime setting (for example, 0) for the matching leaf node, stack traces or a pvac core dump might result.
CR138094 The WebAccelerator system normalized content excludes s-maxage and max-age values.
CR139014 If you sign a user-defined acceleration policy that has been published, and attempt to import the signed acceleration policy, the message You are attempting to import a Signed Acceleration Policy that will overwrite a Pre-Defined or User-Defined Policy. Do you wish to proceed? is hidden, preventing the ability to click Yes or No.
CR139143 If content in RamCache has an expiration that is longer than the expiration in WebAccelerator cache, MultiConnect cannot be re-enabled until the RamCache content expires.
CR133821 The URL setting for Authorization Method on the URL Normalization page does not function when Require Authorization is set to Yes.
CR136185 When an origin web server sends a Cache-Control: no-transform header in response to a request, the WebAccelerator system modifies the header. Clearing the Ignore no-cache HTTP headers in the request check box and the Ignore no-cache HTTP headers in the response check box on the Lifetime tab does not prevent the header from being modified.
ID 222510 When using Intelligent Browser Referencing or MultiConnect functionality to accelerate images, using a form input may produce inconsistent results.

Optional configuration changes

This software release includes the following features:

Name Description
Accept-Encoding gzip The Accept-Encoding gzip feature forces the WebAccelerator system to request content from the origin web server that is compressed by using the gzip utility, if it is available.
Half-closed TCP connection management The half-closed TCP connection management feature allows the WebAccelerator system to properly manage half-closed connections.

Enabling the Accept-Encoding gzip feature

This software release includes the Accept-Encoding gzip feature, but the feature is disabled by default. Use the following procedure to enable the Accept-Encoding gzip feature.
  1. Using SSH, log on to the BIG-IP WebAccelerator system using the root user name and password.
  2. At the command line, switch to the /config/wa directory by typing the following command: cd /config/wa
  3. Using a text editor, view the pvsystem.conf file and locate the following line: <forceOWSGzippedRequests>false</forceOWSGzippedRequests>
  4. Change the value to true, so the line now appears as follows: <forceOWSGzippedRequests>true</forceOWSGzippedRequests>
  5. Save the change and close the text editor.
  6. Restart the BIG-IP WebAccelerator system by typing the following command: bigstart restart

Enabling the half-closed TCP connection management feature

This software release includes the half-closed TCP connection management feature, but the feature is disabled by default. Use the following procedure to enable the half-closed TCP connection management feature.
  1. Using SSH, log on to the BIG-IP WebAccelerator system using the root user name and password.
  2. At the command line, switch to the /config/wa directory by typing the following command: cd /config/wa
  3. Using a text editor, view the pvsystem.conf file and locate the following line: <disableHalfClose>true</disableHalfClose>
  4. Change the value to false, so the line now appears as follows: <disableHalfClose>false</disableHalfClose>
  5. Save the change and close the text editor.
  6. Restart the BIG-IP WebAccelerator system by typing the following command: bigstart restart

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.

Legal notices

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)