AskF5 Knowledge Base
- Home
- Supported Products
- BIG-IP WOM
- BIG-IP WOM 11.3.0
Applies To:
Show Versions
Release Note: BIG-IP WOM 11.3.0
Original Publication Date: 12/17/2012
Summary:
This release note documents the version 11.3.0 release of BIG-IP WAN Optimization Manager.
Contents:
- Configuration utility browser support
- User documentation for this release
- New in 11.3.0
- New in 11.2.1
- New in 11.2.0
- New in 11.1.0
- New in 11.0.0
- Installation overview
- Installation checklist
- Installing the software
- Post-installation tasks
- Installation tips
- Upgrading from earlier versions
- Fixes in 11.3.0
- Fixes in 11.2.1
- Fixes in 11.2.0
- Fixes in 11.1.0
- Fixes in 11.0.0
- Known issues
- Contacting F5 Networks
- Legal notices
Supported hardware
You can apply the software upgrade to systems running software versions 10.x or 11.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.
Configuration utility browser support
The BIG-IP Configuration Utility supports these browsers and versions:
- Microsoft Internet Explorer 8.x and 9.x
- Mozilla Firefox 15.0.x and 9.0.x
- Google Chrome 21.x
User documentation for this release
For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP WOM / VE 11.3.0 Documentation page.
New in 11.2.0
Symmetric Data Deduplication Enhancements
Symmetric Data Deduplication (SDD) enhancements provide support for large hub and spoke, and mesh deployments.
New in 11.1.0
WOM-Lite Support on Chassis Platforms
WAN Optimization services, including TCP optimization and symmetric adaptive compression, are now available on the VIPRION chassis-based platforms to provide maximum throughput and scalability. In addition, with optional vCMP support, customers can benefit from the flexibility of virtualization and multi-tenancy. Note: Symmetric data deduplication and CIFS and MAPI proxies are not available on VIPRION in this release.
Expanded Hypervisor Support
New WOM Virtual Edition (VE) expanded hypervisor support for Citrix XenServer and Microsoft HyperV enables broader deployment for cloud-based environments.
600 GB SSD Option
Larger capacity 600 GB SSD option for the 11000 platform delivers improved disk-based data deduplication performance for large replication environments.
New in 11.0.0
WOM Standalone
WOM standalone provides dedicated WAN optimization without the overhead of additional BIG-IP module licenses.
WOM Virtual Edition (VE)
WOM VE offers an option to deploy full-featured WAN optimization technology, including deduplication, independent of the hardware platform.
WOM SSD Support for 11000 Platform
The BIG-IP WOM 11000 platform supports four 300 GB solid-state drives, thus accommodating a large cache size for WOM datastor. The resulting bigger and faster datastor provides higher performance, particularly for data center to data center deployments. Note: When using SSDs, you must unprovision the WOM datastor on the local disk, and then provision datastor on the SSDs.
Subnet Discovery
WOM automatically adds subnets that can be reached through the local endpoint. Remote endpoints use this information for routing decisions. When WOM discovers a server, it adds the subnet to the list of advertised routes, which simplifies the table of discovered servers, and increases the efficiency of the discovery process.
iSession over IPsec
IPsec support provides secure communication over both TCP and UDP. For example, you can create an IPsec tunnel for all IP traffic to simplify the security and routing required for moving traffic between data centers. Note: Only the TCP traffic is optimized.
WOM Quick Start Screen Enhancements
The WOM Quick Start screen now includes IPv6 support and additional optimized applications.
Compression Enhancements
Hardware compression enhancements provide performance improvement for single connection compression. The addition of the bzip2 compression algorithm for software compression expands the algorithms available to symmetric adaptive compression logic, which selects the best codec for compression based on link conditions. The bzip2 codec is useful for improving compression ratios and throughput for lower speed links.
TCP Packet Loss Enhancements
Enhancements to the TCP stack improve performance across WAN links that have significant packet loss.
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 System: Upgrading Active/Standby Systems and BIG-IP System: Upgrading Active-Active Systems, and we strongly recommend that you reference these documents to ensure successful completion of the installation process.
Installation checklist
Before you begin:
- 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.0.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 WAN Optimization 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
| 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-11.2.0.2446.0.iso 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 System: Upgrading Active/Standby Systems and BIG-IP System: Upgrading Active-Active Systems, and we strongly recommend that you reference these documents to ensure successful completion of the installation process.
- Ensure the system rebooted to the new installation location.
- Log on to the browser-based Configuration utility.
- Run the Setup utility.
- Provision the modules.
- Convert any bigpipe scripts to tmsh. (Version 11.x does not support the bigpipe 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. 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.
Upgrading from version 10.x or 11.x
When you upgrade from version 10.x 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.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.6.x. You must be running version 10.x 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 11.2.1
| ID Number | Description |
|---|---|
| ID 385066 | If you select IPsec for the IP Encapsulation Type setting on the local endpoint, the browser interface now correctly retains the IPsec policy you select for the IPSEC Policy setting. |
Fixes in 11.2.0
| ID Number | Description |
|---|---|
| ID 344148 | The system no longer requires that you use the same self IP address for IPsec and the WOM local endpoint. |
| ID 347070 | When you are using IPsec between a BIG-IP WOM pair, it is no longer necessary to enable the Passive setting for the IKE peer on the server-side BIG-IP WOM. |
| ID 370600 | When IPIP or GRE encapsulation is enabled, disabling and re-enabling a remote endpoint no longer causes it to go down. |
| ID 371232 and ID 371251 | When you run the command tmsh show wom remote-endpoint or tmsh show wom local-endpoint, the system now displays the correct management IP address on vCMP. |
| ID 371309 | Passing traffic through a TCP optimization virtual server (such as http_optimize) no longer causes the discovered route to appear on the Advertised Routes List screen of the client-side WOM device, instead of the server-side WOM device. |
| ID 371323 | BIG-IP WOM peers on a VIPRION cluster now display the correct primary floating IP address of the cluster. |
| ID 371361 | Running WOM connection diagnostics on a VIPRION cluster no longer fails to complete. |
| ID 371362 | When you run the WOM configuration diagnostics, the Runtime Configuration Checks correctly display the Endpoint UUID. |
| ID 371996 | When you delete a local endpoint, the system now automatically deletes the iSession listener (terminating virtual server) on that endpoint. |
| ID 375590 | Intermittent routing failures with an IPsec deployment in a redundant or HA configuration have been fixed. |
| ID 379537 | IKE now consistently succeeds in renegotiation when recovering from a link failure. |
Fixes in 11.1.0
| ID Number | Description |
|---|---|
| ID 341732 | Running WOM diagnostics now correctly validates the WOM license. |
| ID 365101 | On the Quick Start screen, the Discovery setting is now enabled by default. |
Fixes in 11.0.0
| ID Number | Description |
|---|---|
| ID 223797 | (CR131957) The datastor memory cache size is now 8 GB on the 8900 and 8950 platforms. |
| 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. |
Known issues
This release contains the following known issues.
| ID Number | Description |
|---|---|
| ID 403592 | Platforms with less than 6.5G memory cannot be upgraded to 11.3 if three or more modules are provisioned. Note that upgrades from 10.0.x display only an "upgrade failed" message as a software status. All other versions show a clear error message, guiding the users to SOL13988. Before upgrading, make sure you have only one or two modules provisioned if the BIG-IP system has less than 6.5G of memory. |
| 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 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. |
| 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 | 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, as follows.
|
| 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 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 not allow you to name the folder. To name the folder, right-click it and select rename. |
| 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:
|
| ID 346875 | Although the attribute vg-reserved is shown when you issue the command tmsh list sys disk, the attribute is not supported on SSDs, and the system does not reserve the 1024 that is shown. |
| ID 348741 | If you are upgrading from 10.x to 11.x, and you are rolling over existing WOM 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. |
| ID 357720 | File copying might be significantly slower when IPsec encapsulation is used with CIFS optimization. |
| ID 359075 and ID 359835 | Deprovisioning WOM (for example, changing the provisioning level from Dedicated to None) might require a reboot, even though the reboot prompt may not be visible. |
| ID 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. |
| ID 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. |
| ID 361490 | If a device between the BIG-IP WOM endpoints strips out unknown TCP options, the BIG-IP WOM TCP optimizations may fail to negotiate, which can reduce overall performance. |
| ID 363821 | On the server-facing BIG-IP WOM, if you configure the iSession receiving virtual server to target another virtual server, connection resets might occur. To avoid this problem, set the Zero Window Timeout setting value for the client-side TCP profile on the targeted virtual server to at least 300000. |
| ID 365390 | If the BIG-IP WOM platform you are using has hardware compression, and the intended use case is a single connection, you might see compression performance issues in some scenarios. As a workaround, F5 recommends that you disable hardware compression to achieve better single-connection performance on platforms that support hardware compression. To disable hardware compression, change the Deflate Level setting in the iSession profile to a number greater than or equal to 3, using the browser interface (click , and then click the iSession profile you are using) or the command-line interface (type tmsh modify wom profile isession isession deflate-compression-level 3). |
| ID 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. |
| ID 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. |
| ID 381712 | In an active/standby configuration, modifying the WAN optimization codec from SDD v3 to SDD v2, or the reverse, requires that you issue a bigstart restart command on the standby BIG-IP system for the change to take effect. |
| ID 382629 | If you update or delete a WOM self IP, and then create a new self IP before deleting the associated local endpoint and iSession listener, the local endpoint becomes unmodifiable. To avoid this issue, delete the local endpoint and associated iSession listener before creating another self IP on the same VLAN. |
| ID 383985 | When you configure WAN optimization using the Quick Start screen, the BIG-IP system creates two virtual servers for HTTP traffic, http_optimize_client and http_optimize_client_v6, which specify a default network destination of 0.0.0.0 (all networks). If you change the destination to point to a specific subnet, and then attempt to change the IP Encapsulation Type on either the Quick Start or Local Endpoint screen, the user interface displays an error message, and the change does not take effect. As a workaround, you can make the change using the command-line interface. For example, after you update the virtual servers to point to a specific subnet, modify the ip-encap-type attribute for the local-endpoint component by typing tmsh modify wom local-endpoint ip-encap-type ipsec ip-encap-profile replace-all-with {default-ipsec-policy}. |
| ID 384759 | For best performance, F5 recommends using the SDD v2 symmetric deduplication codec for CIFS Layer 7 optimization. |
| ID 385066 | If you select IPsec for the IP Encapsulation Type on the local endpoint, the browser interface displays default-ipsec-policy-isession for the IPSEC Policy setting, regardless of whether you select or specify a different IPsec policy. To work around this issue, configure IPsec policy changes using the tmsh command-line interface, and do not attempt to update the setting through the browser interface. To verify the policy in use, type tmsh list wom local-endpoint. |
| ID 385740 | You cannot configure IPIP or GRE encapsulation on a WOM local endpoint that uses an IPv6 address. |
| ID 393966 | The BIG-IP 4000 platform supports hardware accelerated compression. However, it does not decompress using hardware, as other BIG-IP platforms do. |
| ID 405977 | In this release, you cannot configure an IP-forwarding virtual server with an iSession profile. |
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.
Additional resources
You can find additional support resources and technical documentation through a variety of sources.
- The F5 Networks Technical Support web site: http://www.f5.com/support/
- The AskF5 web site: http://support.f5.com/kb/en-us.html
- The F5 DevCentral web site: http://devcentral.f5.com/
- AskF5 TechNews
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
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, fill out 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 technews-subscribe@lists.f5.com from the email address you would like to subscribe with. Unsubscribe by sending a blank email to technews-unsubscribe@lists.f5.com.
