Applies To:

Show Versions Show Versions

Release Note: BIG-IP WOM 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 WAN Optimization Manager.

Contents:

- User documentation for this release
- Supported hardware
- 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
- Known Issues
- Contacting F5 Networks
- Legal notices

Summary WOM 10.2.4

User documentation for this release

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

Supported hardware

You can apply the software upgrade to systems running software versions 9.3.x, 9.4.x, 9.6.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.

New in 10.2.4

This release contains no new WAN Optimization Manager features.

New in 10.2.3

This release contains no new WAN Optimization Manager features.

New in 10.2.2

This release contains no new WAN Optimization Manager features.

New in 10.2.1

Optimized application for NetApp FlexCache

You can now set up application optimization for NetApp FlexCache by simply checking a box on the Quick Start screen. When you check the NetApp FlexCache box, the system automatically creates the necessary virtual servers with the correct optimization features enabled and tuning parameters set for this application.

New in 10.2.0

Enhanced User Interface

The new Quick Start screen gives you a quick and easy way to configure the WAN Optimization Manager, all on one screen. On the same screen, you can set up application optimization by simply checking (enabling) the applications you want to optimize. Then, the system automatically creates the necessary virtual servers with the correct optimization features enabled and tuning parameters set.

iSession support for live VMware migration

The iSession connections available with the WAN Optimization Manager can optimize traffic when the BIG-IP Local Traffic Manager migrates virtual machine servers between data centers. You can configure an EtherIP tunnel to ensure that the BIG-IP system retains connections to the virtual machines during and after the live migration.

iSession support for BIG-IP Virtual Edition

The WAN Optimization Manager allows the BIG-IP Virtual Edition to perform TCP Optimization and Adaptive Compression across a WAN with up to 50Mbps of compression.

Traffic Management Shell (tmsh) support for WCCPv2

Command line support is available for Web Cache Communication Protocol (WCCPv2), a content-routing protocol developed by Cisco Systems, which provides a mechanism to redirect traffic flows in real time. The primary purpose of the interaction between WCCPv2-enabled routers and a BIG-IP system is to establish and maintain the transparent redirection of selected types of traffic flowing through those routers.

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 WAN Optimization Manager release includes all previously released hot fixes.

Fixes in 10.2.3

This WAN Optimization Manager release includes all previously released hot fixes.

ID Number Description
ID 345527 This release fixes a sporadic failure that sometimes occurred when uploading a file to a remote CIFS server.
ID 361676 The BIG-IP platforms 6900, 8900, 8950, and 11050 using hard drives greater than 500 GB, no longer fail to create a logical volume for datastor when provisioning WOM. To determine what size disk you have, log on to the command-line interface using the root account, and run the command pvscan.

Fixes in 10.2.2

This WAN Optimization Manager release includes all previously released hot fixes.

ID Number Description
ID 334135, 334136 Using packet filters for rate shaping on the server side WAN Optimization Manager no longer fails.
ID 355291 The connection failure that sometimes occurred with larger file transfers no longer occurs.

Known Issues

This release contains the following known issues.

ID Number Description
ID 204432 (CR109097) The system does not log a warning if local advertised routes conflict with advertised routes on remote endpoints. Having two systems with conflicting routes is most likely a configuration error.
ID 218151 (CR109093) If you are using a self IP address for the WAN Optimization Module and the Port Lockdown setting of the self-IP address on the server-side endpoint is set to Allow Default (the default value), certain types of TCP and UDP traffic are blocked; for TCP: SSH, domain, SNMP, HTTPS, and 4353; and for UDP: domain, SNMP, EFS, 1026, and 4353. You must set the self IP address to Allow None (the command line default) to successfully optimize all types of traffic.
ID 218156 (CR109099) When you are using Internet Explorer 6 to display the dashboard, the system might display a message about mixed HTTPS and HTTP on the page. This is a known issue in version 6, and Microsoft has fixed it in Internet Explorer 7. You may ignore the message. All communications remain secure.
ID 222201 (CR114972) If you change the compression or deduplication options for the iSession profile on a BIG-IP system that is running both the WAN Optimization Manager 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 might not accelerate the HTTP traffic as expected.
ID 223191 (CR128182) If you remove all remote endpoints from a configuration, any active dashboard continues to show the last remote endpoint as connected. To refresh the screen, close the dashboard and then reopen it.
ID 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.
ID 223624 (CR130848) 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 ( WAN 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.
ID 223738 (CR131638) Using the bigpipe command b profile tcp all stats reset fails to reset the statistics for woctunnel_tcp.
ID 223797 (CR131957) The datastor memory cache size is limited to 4 GB on the 8900 and 8950 platforms.
ID 242092 (CR132950-1) When the BIG-IP system is under a heavy load, you may see occasional spikes on the Bandwidth Gain graphs on the WAN Optimization dashboard. A system delay in reporting the statistics to the dashboard causes the delay, which is usually about twice the average amount.
ID 247625 (CR125095) If you are using a Firefox version earlier than v3.0 and a Flash plug-in earlier than version 9, Firefox issues a shockwave flash error when you attempt to launch the dashboard. To avoid this problem, install the latest version of Firefox.
ID 293593 (CR132785) If the datastor disk mode is disabled when you provision WAN Optimization Manager along with any other module and then you enable the datastor disk, you must restart the system to show the correct datastor size.
ID 335216 (CR128965) If you use the smbclient (version 3.2 or later) program to get a file, CIFS read optimization does not occur.
ID 335217 (CR130507) If you map a network drive and create a new folder, it takes more than 10 seconds for the folder to appear in the directory and does now allow you to name the folder. To name the folder, right-click it and select rename.
ID 342197 (CR137376, CR138046) Installing or upgrading a pre-10.2.x system that has a full disk can fail. A disk might be full for several reasons, for example:
  • WAN Optimization Manager is provisioned as Nominal, which does not allow the system to allocate enough space for the new Maintenance Operating System (MOS) or installation location
  • There are too many installation locations configured
  • Application Security Manager or WebAccelerator System is provisioned for multiple installation locations
  • You are installing/upgrading to version 10.1.0 or later on a version 10.0.x or 9.x partition, which is too small to hold the version 10.1.0 or later image
  • You are upgrading a 6900 or 6800 platform
There are several workarounds, depending on the cause of the disk-full condition. One option is to back up your existing configuration and perform a clean installation, another is to remove unneeded boot locations, another is to deprovision WAN Optimization Manager and then save and reboot before upgrading, and there are others. For more information, see SOL10636: Upgrading to BIG-IP version 10.1.0 fails with a 'Disk full' error message.
ID 342251 If you are trying to remove the WOM connection between two peers, you must delete the remote endpoint before you delete the local endpoint to prevent reconnection. If you are using the browser interface, the procedure is as follows:
  1. On the Dynamic Discovery screen, disable 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.
ID 363550 A deduplication failure or restart does not trigger the failover mechanism. A more effective method of recovery in the case of a deduplication failure is to restart deduplication on the same BIG-IP WOM on which it failed, rather than changing platforms by failover.

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)