Software Release Date: 09/09/2007
Updated Date: 04/21/2011
In addition to these release notes, the following user documentation is available for this release.
The following WANJet appliance documentation is relevant to this release. Although some of the documentation is not yet updated, it still contains relevant information for this release. Refer to the online help by clicking the Help tab for up-to-date details about the screen that you are currently viewing.
You can find the product documentation and the solutions database on the AskF5 Technical Support web site.
Because the WANJet appliance now runs on TMOStm, some parts of the product are described in the BIG-IP® system documentation. Therefore, the following BIG-IP® system documentation is also relevant to this release:
If you are using the Enterprise Manager to manage multiple WANJet appliances, refer to Managing WANJet appliances with Enterprise Manager later in this document. For additional details on setting up and using Enterprise Manager, refer to the following documentation:
You can find the product documentation on the AskF5 Technical Support web site.
[ Top ]
The supported browsers for the WANJet appliance web browser interface are:
This release supports the following platforms:
[ Top ]
WANJet appliance version 5.0 is pre-installed on new hardware platforms. No software installation is necessary. Continue with To start using the WANJet appliance, below.
If you have existing WANJet 400 or 500 appliances running v4.2.x and want to run version 5.0, you must order a version 5.0 upgrade kit through your F5 Sales Representative. The upgrade kit contains
You need to replace the 1 GB CompactFlash® with the 8 GB CompactFlash card on which version 5.0 is installed. Existing WANJet 500 appliances also require a BIOS upgrade to OBJ-0200-03 Rev A. Refer to the WANJet Appliance Upgrade Instructions for information on how to replace the CompactFlash card (WANJet 400 and 500) and upgrade the BIOS (WANJet 500 only).
Important: For the WANJet appliance to function properly, any firewalls separating the WANJet appliances must have TCP ports 3702 and 3701 open on the firewall. For specific information about configuring ports, refer to the WANJet Appliance Administrator Guide.
Note: We strongly recommend using the Management Port. However, if you do not have a management network, use the LCD to configure the WANJet Bridge IP address, WANJet Netmask, and WANJet Gateway.
You can complete the rest of the configuration on the WANJet appliance.
Note: If you configured the WANJet IP (Bridge IP) address rather than the Management Port IP, refer to WAN Gateway lost after licensing (CR85442) in Known Issues.
Important: You must reboot the WANJet appliance at this time if you activated the license.
You can now deploy and manage multiple WANJet appliances from the Enterprise Manager, a centralized management solution. You need to have purchased and set up Enterprise Manager, which is a separate product from the WANJet appliance. Refer to Managing WANJet appliances with Enterprise Manager later in this document for information about managing WANJet appliances from Enterprise Manager. For details on setting up and using Enterprise Manager, refer to the Enterprise Manager documentation on the AskF5 Technical Support web site.
The WANJet appliance is now based on TMOSTM (Traffic Management Operating System) architecture. TMOS provides a unified system for application delivery and network adaptability.
Web browser interface redesign
The WANJet appliance has a new streamlined web browser interface as a result of the TMOS integration. What used to be called the Web UI is now called the Configuration utility. Refer to Changes to the web browser interface for more details.
Some functions are no longer available in the web browser interface. You must perform them from the command line. For example,
Some functions are no longer available. For example,
Command line functionality
You access the command line locally using a terminal emulator, or remotely using an SSH program as you did with previous releases. You have to log on as root (until you allow terminal access to the admin account or create new users). At the command line, you have full access to Linux (not a restricted shell) including these utilities and commands:
TDR-2 disk support
WANJet 500 and 300 appliances now have TDR-2 disk support enabled. WANJet 500 and 300 appliances can cache additional data on hard disk, and use that data for faster optimization. If the WANJet appliance has a hard drive, the Operational Mode screen includes a TDR-2 Storage Mode setting that you can configure as Disk Based Storage (the default value) or Memory Based Storage.
WANJet 300 platform
The 5.0 version of the WANJet appliance software supports the WANJet 300 platform.
The WANJet appliance includes online help for all screens in the web browser interface. To view the help for the current screen, click the Help tab to display the content in the navigation pane, or click the Launch button to open the help in a separate window. When you open a popup screen, click the Help tab again to change to content relevant to the popup.
[ Top ]
The following table describes changes to features of the WANJet appliance web browser interface for this release as a result of TMOS integration.
|Setup utility||The first time you log on to the WANJet appliance, you must run the Setup utility to license and configure the system.|
|Navigation pane||The features in the navigation pane are organized into four sections: Overview, WAN Optimization, Network, and System.|
|WAN Optimization section||The WAN Optimization section contains all features specific to the WANJet appliance. Most of the settings that were previously in the Reports, Optimization, Configuration, Security, and System sections in 4.2.x are now located in WAN Optimization.|
|WAN Optimization >> Operational Mode||
This screen now includes TDR-2 Storage Mode on WANJet 300 and 500 platforms. Select Disk Based Storage to use the disk.
The Failure Mode feature is available only on WANJet 400 appliances. If you select Fail Close as the failure mode, the system stops traffic in the case of hardware failure; in this case, you also have to make a hardware adjustment to the jumper settings on the NIC of the WANJet 400. Refer to the WANJet Appliance Administrator Guide for details on how to make this adjustment. The Failure Mode setting is not available on WANJet 300 and 500 appliances; if the hardware fails, traffic is automatically set to passthrough.
|WAN Optimization >> Optimization Policy||Configuring optimization policies is easier to do now. Optimization policies now apply to all remote WANJet appliances in the configuration. You can specify passthrough policies for ports on which you do not want to optimize traffic. This screen no longer requires you to add local or remote subnets. You can access a screen to add local subnets from the Local WANJet appliance screen.|
|WAN Optimization >> Application QoS||You can configure Application QoS policies and use the Save As Template feature to save the policy so that Enterprise Manager can deploy it on other WANJet appliances.|
|WAN Optimization >> Traffic Class||
Traffic class was formerly called IT Service Policy. You can group ports, machines, and subnets under the heading of a traffic class. You can then create an Application QoS policy assigning a minimum and a maximum amount of bandwidth for the traffic class.
|WAN Optimization >> Tuning||The Queue Size setting is no longer required.|
|WAN Optimization >> Local WANJet||You configure redundant peers on this screen. You can click Local Subnets to access a screen to add subnets from this screen. The VLAN Settings link is no longer available from this screen.|
|WAN Optimization >> Local WANJet >> Local Subnets||You can add local subnets on this screen. The Optimize All Subnets setting is no longer available. You can specify all subnets by adding a subnet with the address and netmask set to 0.0.0.0.|
|WAN Optimization >> Local WANJet >> Settings for Delayed Connection Acceptance||You can specify ports on which to postpone acceptance of LAN requests until the server connection is verified.|
|WAN Optimization >> Remote WANJets||
You can view and ping remote subnets on the Remote WANJets screen. You no longer need to add remote subnets, because policies apply to all remote WANJet appliances.
Remote WANJet appliance status and subnet status are now shown on this screen. You can ping any remote WANJet appliance by clicking its IP address.
|WAN Optimization >> Diagnostics||Several reports are no longer relevant, and have been removed from the Diagnostics screens. The Administrative tools that were formerly located on the General tab are now available from the command line. The Clear Logs button is no longer on the Diagnostic log.|
|WAN Optimization >> Monitoring||The WANJet appliance now has two SNMP agents (one for TMOS and one for the WANJet appliance). SNMP settings are located in two places: Enable RMON2 Logs is on the WAN Optimization >> Monitoring screen, and the general TMOS SNMP settings are located on the System >> SNMP screen. The SNMP Server IP, SNMP IP, and Community String fields are no longer available.|
|Network section||This section is all new and includes screens used to configure interfaces and static routes, and view interface statistics.|
|System section||This section now includes screens for licensing the system, adding users, changing root and admin passwords, creating archives, setting up SNMP, and so on. IP Access Control is on the System >> Platform screen. Backup and restore is now performed using the System >> Archives screen.|
You can find information about the current state of the local and remote WANJet appliances and the current number of optimized and passthrough sessions in the upper left corner of the WANJet Configuration utility. For example, the dashboard shows:
WANJet Links: Active (1/1)
Point the cursor and hover over these lines to see more details about current status. The bar preceding the lines is green when the link is up, yellow when you have more than two WANJet appliances and only some of the links are up, and red if the links are not up.
If you have set up a redundant peer successfully, you also see:
Redundant Status: OK
[ Top ]
The following features are not in this release:
If you have installed and configured Enterprise Manager, the following configuration information is relevant to you.
Generally, you should refer to the Enterprise Manager documentation and online help for details about administering devices using Enterprise Management. This section provides general instructions for how to get started with managing WANJet appliances using Enterprise Manager.
Note: To use Enterprise Manager to configure WANJet appliances, you must use the Management Port IP address rather than the WANJet IP (bridge IP) address to log on.
To manage WANJet appliances, the Enterprise Manager must first discover the devices. You can do this either by manually entering the credentials into the Enterprise Manager Configuration utility, or by importing a comma-separated value (CSV) file containing the relevant details. The format of the CSV file is as follows:
Where IPAddress is the Management IP address of the WANJet appliance, the user name is admin, and the password is the one you specified for this account when you ran the Setup utility on the appliance. Save the file as a text file with any name.
Note: At this point, if you are not using a CSV file to import the WANJet appliance Management IP addresses, you can type the Management IP address, user name, and password, and click Add to add each one to the Address List. Then skip to step 9.
When you are installing several WANJet appliances, it may be convenient to use a topology changeset from Enterprise Manager rather than logging in to each individual WANJet appliance's web browser interface to add remote WANJet appliances. You describe the overall network topology in a simple XML format (including IP address, subnets, and so on), and deploy this changeset from the Enterprise Manager to all devices.
An XML schema controls the format of the changeset. You can create this schema and a simple example topology changeset from any WANJet appliance managed by the Enterprise Manager, as described in detail below. For more information on changesets and staged changesets, refer to Chapters 6 and 7 of the Enterprise Manager Administrator Guide (Version 1.4).
You can create optimization policies on one WANJet appliance that you can deploy to other WANJet appliances. The WANJet appliance creates an XML file that includes the policies; you use the changeset feature on the Enterprise Manager to deploy them.
Tip: When the popup screen opens, click the Help tab to view details on the screen.
Application QoS policies allow you to dedicate a percentage of bandwidth to specific network traffic. If you have several WANJet appliances to set up, you can create Application QoS policies on one WANJet appliance and deploy them to other WANJet appliances. This saves having to create the policies over and over on each WANJet appliance.
Tip: When the popup screen opens, click the Help tab to view details on the screen.
Now, you can push the optimization and Application QoS policies that you just created on one WANJet appliance to other WANJet appliances. You must deploy the two types of policies separately.
Note: After saving an optimization or a QoS policy on a WANJet appliance, there is a short delay before the changes are reflected in Enterprise Manager. This is normally no more than 30 seconds, but may take longer on a slow network. If you create a changeset on Enterprise Manager and do not see the expected policies, wait a couple of minutes and try again.
Note: You need to deploy optimization policies separately from QoS policies.
This section provides additional details about the XML file formats used to configure the WANJet appliance from Enterprise Manager. You can configure the following areas using an XML changeset file:
The Enterprise Manager lets you access three files for each area:
The topology changeset allows you to specify the topology of all the WANJet appliances on their network. When you deploy this file to the devices, all of the connections between the WANJet appliances are automatically created.
The file has two distinct sections. In the first section (the WANJet appliance section), you describe all of the WANJet appliances that form part of the topology. Minimally, you must assign an alias and a WANJet IP (bridge IP) address to each WANJet appliance. For example:
Additionally, for each WANJet appliance, you can associate one or more subnets in the Subnets section. Each Subnet entry includes the following information:
The second section of the file, the WanLink section, specifies the links between each of the WANJet appliances. Define each two-way link with a pair of IP addresses and a shared key. For example:
The Application Quality of Service (QoS) changeset defines each QoS policy using an alias and the maximum and minimum bandwidth. It then defines the services covered by the policy as shown in the following example:
The Optimization changeset consists of a series of policy sections that specify a port range and define the optimization strategies to apply to that port range. For example:
[ Top ]
The following items are known issues in the current release.
Application QoS policies help you to obtain better network performance by dedicating bandwidth to specific network traffic that travels between two WANJet appliances or over a WAN link. The Application QoS feature has the following issues in this release.
Application QoS: Adding subnets to WAN links (CR82905)
When you are adding subnets on the Manage the Application QoS Settings of a WAN Link popup screen, the added subnet does not initially show on the screen. However, the subnet has been added, as you can see if you edit the WAN link from the main Application QoS screen.
Avoid Application QoS policies for passthrough data (CR84651)
Application QoS policies with passthrough data are not performing up to the overall QoS bandwidth limit configured. The workaround is not to create Application QoS policies for passthrough traffic.
Application QoS policy fails when first implemented (CR85260)
When you first create an Application QoS policy, it may not perform traffic shaping as expected until you edit that policy and save it. The Application QoS policy then works as configured.
Application QoS policy disabled if peer loses link to redundant peer (CR85380)
For WANJet appliances set up as redundant peers only: If a WANJet appliance is configured with a redundant peer and the link between the two is lost, Application QoS policies are disabled. The workaround is to bring up the link between the peers, or temporarily disable the redundant peer on the Local WANJet appliance screen.
Firefox rendering issue
In versions 220.127.116.11 and 18.104.22.168 of the Firefox® web browser, empty text boxes in the WANJet browser interface may contain XX. This does not affect the WANJet appliance functionality.
Cannot specify MTU in Enterprise Manager topology file (CR75704)
When a LAN router is present, you must create a static route for every remote WANJet appliance. To create a route, you need to specify the MTU setting (largest allowed packet size). When configuring WANJet appliances from the topology file on Enterprise Manager, there is currently no way to specify this value. You must configure it on the WANJet appliances itself.
Sending data to a syslog server (CR76877)
Although the WANJet appliance does not provide a way to send logs to a syslog server from the web browser interface, you can manually edit the /etc/syslog-ng/syslog-ng.conf file and use the HUP syslog-ng command to allow logging to a remote server, and this is consistent with how TMOS-based products work. For example:
user.* @my_remote_server_IP # log all user messages to a remote server
kern.crit @my_remote_server_IP # log only the critical kernel messages to a remote server
*.* @my_remote_server_IP # log everything to remote server
Refer to SOL5527: Configuring BIG-IP to log to a remote syslog server and the syslog-ng and syslog-ng.conf man pages for additional information.
LCD shutdown does not power down (CR78158)
Attempting to shut down the WANJet appliance from the LCD causes the operating system to halt, and does not physically power down the hardware. The workaround is to press the On/Off switch after the system halts.
Remote WANJet appliance with redundant peer (CR78462)
When a local WANJet appliance pings a remote WANJet appliance that has a redundant peer, the local WANJet appliance can contact only the first remote WANJet appliance, not the second one.
Internet Explorer 7 not supported (CR78511, CR83783)
If you log on to the WANJet appliance web browser interface using Internet Explorer® 7, you see alignment problems and possible error messages, and the online Help is not displayed. We recommend using Internet Explorer 6 or Firefox®, which are fully supported.
Dashboard statistics not updating (CR78655)
In certain cases, the dashboard in the web browser interface may not show the latest statistics. To be sure that the dashboard statistics are up to date, click the Refresh button in the browser.
Expired or missing license (CR79535)
The WANJet appliance gives no warning in the web browser interface if the license is expired or missing. You should periodically check the License screen (System >> License) to be sure it is valid.
Removing disk drive stops traffic (CR79928)
Removing a disk drive while the WANJet 500 is actively passing traffic using Disk Based Storage for the TDR-2 Storage Mode stops traffic. If you need to replace the disk drive, set the WANJet appliance operational mode to Inactive before removing the disk drive.
System Statistics Memory information (CR80371)
The information displayed in the System Memory Used column on the System Statistics screen may not be accurate on WANJet 500s. It shows 15.9S.
SOD service description (CR80973)
On the High Availability screen (System >> High Availability), the SOD service description reads Failover, but should say High availability management.
Default optimization policy shows different values on popup screen (CR81060)
When you first start a WANJet appliance, the default optimization policy for all ports is that all traffic is set to passthrough and TDR-1 and TDR-2 optimization is not enabled. However, when you click the Service Name of the default optimization policy, the Edit Port/Service Name popup screen shows TDR-1 and TDR-2 as selected but grayed out. They are not enabled and should not appear selected, and can be ignored.
WANJet 300 appliance does not shut down using ACPI (CR81349)
You need to press the power switch on the WANJet 300 to turn off the power after the shutdown sequence completes.
Re-enabling a disabled interface (CR82218)
On the Interface screen (Network >> Interfaces), you must click Enable twice to re-enable an interface that has been disabled.
Disabling the WAN interface on a WANJet 400 (CR82291)
Disabling the WAN Interface on a WANJet 400 brings down the LAN interface and restarts the tmm process. We do not recommend disabling the WAN interface on a WANJet 400.
Inconsistent data on Passthrough Sessions screen (CR83331, CR83717)
The number of passthrough sessions reported on the Passthrough Sessions screen (WAN Optimization >> Diagnostics >> Monitoring >> Passthrough Sessions) may not accurately reflect current system activity.
Fedora Core 3 and optimization performance (CR83500)
Using the Fedora Core 3 client or server produces some illegal IP packets that degrade optimization performance significantly, especially with TDR-2 enabled.
Local WANJet appliance screen values not validated (CR83543)
On the Local WANJet appliance screen, when you specify the local WANJet IP (Bridge IP) address, netmask, gateway, and LAN router, the syntax of the values is checked, but the WANJet appliance does not check the validity of the addresses. Be sure that you specify valid addresses for these settings.
Topology changeset validation in Enterprise Manager (CR84195)
When you deploy a topology changeset from Enterprise Manager, it is important to be accurate about IP addresses, subnets, and netmasks. Information within changesets is not fully validated in this release. If you deploy a changeset with invalid values, you will not receive an error message.
System reboot displays message (CR84296)
If you reboot the WANJet appliance with the web browser still displayed, you may see the message Configuration Utility Restarting, and the web browser interface is unavailable. When the system is restarted, you can either refresh the web browser interface or open a new browser window to display the login prompt.
RMON-1 values not available (CR84513)
Only RMON-2 values are available if you use a MIB browser to view data in the WANJet appliance MIBs.
SNMPwalk may fail (CR84638)
Many Management Information Base (MIB) browsers use the SNMPwalk function while reading values from an SNMP agent. This function may fail after reading the RMON2 MIB. You can still query the MIB using OID values.
TDR-2 Storage Mode change requires reboot (CR84725)
On the Operational Mode screen (WAN Optimization >> Operational Mode), you need to reboot the WANJet appliance if you change the TDR-2 Storage Mode from Disk Based Storage to Memory Based Storage, or the reverse.
Set Operational Mode to Active (CR84777)
When you start up WANJet appliances and configure remote WANJet appliances, you may need to set the Operational Mode to Inactive, click Save, then set Operational Mode to Active, and click Save again to bring all WAN links up and establish links between all appliances.
Diagnostic reports may not show correct data (CR84856, CR84544)
The information displayed in the Optimized Sessions report may not show accurate data, or the report may be blank. The workaround is to refresh the screen.
Real Time Traffic report (CR84857)
The amount of network traffic shown in the Real Time Traffic report may occasionally appear to spike to 1.5 GB of throughput. This amount is not accurate.
Peer configuration copies WAN Gateway to LAN router setting (CR85044)
On the Local WANJet appliance screen, checking the Enable Redundant Peer box and typing values in the peer fields causes the WAN Gateway value to be copied into the LAN Router setting. The workaround is to clear the LAN Router box manually before clicking the Save button to apply the changes.
System reboot may cause message to appear (CR85327)
After rebooting a WANJet appliance, you may see the message Cannot start genericproxy because reboot is required. If the system does not restart properly, try rebooting the system again.
WAN Gateway lost after licensing (CR85442)
If you are using the WANJet IP (Bridge IP) address rather than the Management port for managing the WANJet appliance, after you license the system, the information configured for the WAN gateway is lost. Your response is dependent on the location of the computer you are working on.
[ Top ]