Original Publication Date: 08/27/2013
For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP WOM 11.0.0 Documentation page.
[ Top ]
Note: F5 Networks recommends that the BIG-IP platform on which you plan to provision the WAN Optimization Manager has a minimum of 4 GB of RAM.
Note: You cannot run this software on a CompactFlash media drive; you must use the system's hard drive.
The supported browsers for the Configuration utility and BIG-IP WAN Optimization dashboard are:
Note: F5 Networks recommends that you leave the browser cache options at the default settings.
Important: Popup blockers and other browser add-ons or plug-ins may affect the usability of the Configuration utility. If you experience issues with navigation, we recommend that you disable these types of browser plug-ins and add-ons.
[ Top ]
This release note documents the version 11.0 release of BIG-IP WAN Optimization Manager. You can apply the software upgrade to software versions 10.1.x on multiple platforms, as defined in SOL10288: BIG-IP software and platform support matrix.
If you are unsure of which platform you have, refer to the sticker on the back of the chassis, which displays the platform number.
Note: The hardware and software for each unit in a redundant system configuration must match.
[ Top ]
This document lists very basic steps for installing the software, which includes WAN Optimization Manager. The Upgrading BIG-IP Active/Standby Systems to Version 11.0 contains details and step-by-step instructions for completing an upgrade.
Before you begin:
Installation consists of the following steps.
Warning: Do not use the --nomoveconfig option described in the following procedure 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.
After the installation finishes, you must complete the following steps before the system can pass traffic.
These steps are covered in detail in Upgrading BIG-IP Active/Standby Systems to Version 11.0.0.
The upgrade process installs the software on the inactive installation location that you specify. This process usually takes between three 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. 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.
[ Top ]
WAN Optimization Manager (formerly, WAN Optimization Module) is supported in software versions 10.1.0 and later. For information about upgrading from earlier versions, without the WAN Optimization Module, refer to Release Note: BIG-IP Local Traffic Manager and TMOS version 11.0.
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 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.
Important: If the system you plan to upgrade has WAN Optimization Manager, WebAccelerator, or Application Security Manager already provisioned or if you have a number of volumes with software installed, you might experience an upgrade failure due to insufficient space. Before you proceed, set the module provisioning to Minimal, or remove unneeded volumes and reboot the system. After installation is complete, you can set the provisioning back to its original setting. For more information, see SOL10636: Upgrading to BIG-IP version 10.1.0 fails with a 'Disk full' error message.
When you upgrade from 10.x software versions, 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.
[ Top ]
This release includes the following new features.
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.
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.
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.
[ Top ]
This release includes the following fix.
Logical volume for datastor on disk on platforms with greater than 500 GB HDD (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.
[ Top ]
The following items are known issues in the current release.
No warning when advertised routes conflict with remote routes (CR109097, ID 204432)
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.
Deleted remote endpoint remains on dashboard (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.
CIFS read optimization not working with smbclient (CR128965)
If you use the smbclient (version 3.2 or later) program to get a file, CIFS read optimization does not occur.
FTP data ports changed (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.
Creating a new folder on mapped drive is taking too long (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.
Limited datastor memory cache size (CR131957, ID 223797)
The datastor memory cache size is limited to 4 GB on the 8900 and 8950 platforms.
Provisioning WAN Optimization Manager with another module and disk mode disabled results in a datastor size of 0 (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.
Dashboard graphs for Bandwidth Gain display random peaks of double bandwidth (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.
Diagnostic messages regarding TCP connection reset (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.
False failure for WOM license detection in browser interface (ID 341732)
If you run Diagnose WOM Configuration on the Troubleshoot screen of the BIG-IP WOM browser interface, you may receive a false failure message regarding the WOM license. To confirm the WOM configuration, you can use the tmsh utility to issue the command tmsh run wom verify-config for an accurate diagnosis of license validity.
Deduplication connection error with removal of peer (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:
Self IP address for iSession over IPsec (ID 344148)
You must use the same self IP address for IPsec and the WOM local endpoint.
Unsupported attribute appears for SSDs in command line interface (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.
Enabled bzip2 option automatically added to iSession profile in upgrade (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.
WCCPv2 incompatible with floating IP address (ID 349838)
You cannot use a floating IP address for a WCCPv2 configuration.
Connection to mcpd lost message after tmsh restart sys service all (ID 358063)
If you issue the command restart sys service all from the tmsh utility, the next command you issue results in the error message "The connection to mcpd has been lost, try again."
Continuous restarts after unprovisioning WOM (ID 359075, ID 359835)
Unprovisioning WOM (for example, changing the provisioning level from Dedicated to None) may require a reboot, even though the reboot prompt may not be visible.
Recommended deployment settings for IP encapsulation (ID 361018)
If you are using IP encapsulation, F5 recommends that you deploy BIG-IP WOM in a routed mode deployment. If you must use IP encapsulation in a bridge mode deployment, set the Transparency Mode for the VLAN group to Opaque.
Adaptive Compression performance not as expected (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 Adaptive option, and manually select a compression codec.
Hardware compression and single connection performance (ID 361243, 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 work around, 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 Local Traffic > Virtual Servers > Services > iSession, 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).
Removal of unknown TCP options may cause enhanced WOM TCP optimizations to fail (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.
Adjusting TCP profile setting for optimized applications that require an application-specific receiving side virtual server (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.
Discovery disabled by default on Quick Start screen (ID 365101)
On the Quick Start screen, the Discovery setting is disabled by default. To ensure the automatic discovery of endpoints and routes, change the setting to Enabled before you click Apply.
Documentation missing note about compression selection (ID 367803)
When the Adaptive compression setting in the iSession profile is disabled, the BIG-IP WOM devices negotiate the iSession connection to the highest compression ratio codec. If this is not the desired outcome, make sure that you select the compression codec you want for your network conditions, and disable the other codecs.
[ Top ]
Contacting F5 Networks
For additional information, please visit http://www.f5.com.