User documentation for this release

In addition to these release notes, the following user documentation is available for this release.

WANJet appliance documentation

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.

• WANJet Appliance Administrator Guide
• WANJet 300 Quick Start Card
• Platform Guide: WANJet 300
• WANJet 500 Quick Start Card
• Platform Guide: WANJet 500
• Online help
• AskF5 Knowledge Base

You can find the product documentation and the solutions database on the AskF5 Technical Support web site.

BIG-IP system documentation

Because the WANJet appliance now runs on TMOS^tm, 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:

• BIG-IP Command Line Interface Guide (Version 9.4.2)
  This is a complete reference guide that describes all of the commands available from the command line. You can use all of the commands from the WANJet appliance command line through an SSH interface.
• Installation, Licensing, and Upgrades for BIG-IP Systems
  This is a guide that explains how to install, license, and upgrade BIG-IP systems such as the WANJet appliance.
• BIG-IP Network and System Management Guide (Version 9.4.2)
  This guide focuses on the network and system sections of the navigation pane.

Enterprise Manager documentation

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:

• Enterprise Manager Quick Start Instructions (Version 1.4)
• Enterprise Manager Administrator Guide (Version 1.4)

You can find the product documentation on the AskF5 Technical Support web site.

[ Top ]

Supported browsers

The supported browsers for the WANJet appliance web browser interface are:

• Microsoft^® Internet Explorer^®, version 6.x
• Mozilla^® Firefox^® 1.5x or version 2.0x, and other browsers that use the Mozilla engine

Supported platforms

This release supports the following platforms:

• WANJet 300
• WANJet 400
• WANJet 500

[ Top ]

Getting started

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.

Prerequisites for existing WANJet 400 or 500 appliances

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

• 8 GB CompactFlash^® with WANJet version 5.0 installed
• Grounding wrist strap
• WANJet Appliance Upgrade Instructions

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.

To start using the WANJet appliance

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.

1. If you have a management network, use the liquid crystal display (LCD) on the front of the WANJet appliance to configure these items:
   • Management Port IP address
   • Management Netmask
   • Management Gateway
   • Optionally, the WANJet Bridge IP address (also called the WANJet IP address)
   Instead of using the LCD, you can also log on to the WANJet appliance using a console (with the terminal settings 19200 8-n-1); log on using the root account with the password of default and run the config command to configure the Management IP address, netmask, and gateway.

   You can complete the rest of the configuration on the WANJet appliance.

2. Log on to the WANJet appliance by typing the following address into a browser address line.
   https://<IP address>
   Where: <IP address> is the Management Port IP address (if using out-of-band management) or the WANJet IP (Bridge IP) address.
   The WANJet appliance login screen opens.
3. Type the user name and password.
   The default user name is admin and the default password is admin.
4. Click OK.
   The WANJet appliance Configuration utility opens, and automatically runs the Setup utility the first time you log on to the WANJet appliance.
5. Follow through the screens in the Setup utility to complete initial configuration of the WANJet appliance. (These are the minimum settings that you need to complete.)
   
   
   1. Setup Utility >> Introduction: Click Next to start configuring the system.
   2. Setup Utility >>License: If a license appears, click Next (the appliance license has already been activated), and skip to step e.
      If no license appears, click Activate to activate the license.
   3. Setup Utility >>License: Type the Base Registration Key, select Automatic as the Activation Method, and leave the default Outbound Interface set to mgmt (unless you do not have a management network and plan to log on using the Bridge IP address; then change this to lan).
   4. Setup Utility >>License: Click Accept if you agree with the terms in the license.
      

      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.

   5. Setup Utility >>Platform: If you configured only the WANJet IP (bridge IP) address from the LCD, the Management Port settings are blank (otherwise they contain the values you specified). You must type a Management Port IP Address and Network Mask (use fictitious ones) to proceed with the setup.
   6. Setup Utility >>Platform: Type a fully qualified domain name for the Host Name, for example, store.newyork.siterequest.com), and then type the root account and the admin account passwords. Click Next to save the values.
   7. Setup Utility >> WANJet: Check the local WANJet appliance settings, and type the WANJet IP (Bridge IP), WANJet Netmask, and WAN Gateway addresses now if you did not do this using the LCD. Click Save to update the values.
   The Welcome screen opens. Close the browser.

   Important: You must reboot the WANJet appliance at this time if you activated the license.

6. Before you can use the WANJet appliance, you need to reboot it if you have activated the license. From the command line: use an SSH client (such as PuTTY) to log on as root; at the command line, type reboot.
7. After a few minutes, the WANJet appliance reboots, and you can open a browser and log on again. Type:
   https://<IP address>
   The Welcome screen opens and you can begin using the WANJet appliance Configuration utility. Set up the remote WANJet appliance and adjust optimization policies. After the WANJet appliances are set up and processing traffic, you can refer to the Real Time Traffic and Diagnostics reports for information about traffic and connectivity statistics.

New features and enhancements

This release includes the following new features and enhancements.

Enterprise Management
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.

TMOS architecture
The WANJet appliance is now based on TMOS^TM (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,

• Restarting the appliance (use the reboot command)
• Shutting down the appliance (use the shutdown command)
• Updating the appliance
• Setting the time (use the date command)
• Restoring factory defaults (use the sys-reset command)
• Administration tools (use the tracepath and tcpdump commands)
• Booting from an alternate image (use the switchboot command)

Some functions are no longer available. For example,

• You can no longer create a pin to restrict access to the LCD.
• You can no longer add remote subnets.

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:

• Config utility: allows you to define the Management IP address, netmask, and gateway during initial configuration, if you prefer not to use the LCD.
• bigpipe utility: provides commands for configuring the WANJet appliance. To work in the bigpipe shell, type bigpipe shell.
  Type bp to see a list of bigpipe commands.
• Standard Linux commands: provide many standard commands for managing the WANJet appliance.
  Type help to see a list of 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.

Online help
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 ]

Enhancements to the web browser interface

The following table describes changes to features of the WANJet appliance web browser interface for this release as a result of TMOS integration.

[ Top ]

Features in release 4.2.x not in this release

The following features are not in this release:

• UDP optimization: UDP traffic is not optimized and is set to passthrough.
• TOS: You can no longer modify Type of Server (TOS) priorities for traffic using a specific port.
• Transparent proxy with WCCP v2 protocol: The WANJet appliance does not support the WCCP v2 protocol. (Primarily used as transparent proxy for one-arm configuration.)
• Transparent proxy with GRE tunneling: You cannot configure WANJet appliances in a one-arm configuration that sends passthrough traffic through a Generic Routing Encapsulation (GRE) tunnel.
• Non-transparent proxy (SNAT): Previous releases allowed you to configure the WANJet appliance as a non-transparent proxy whereby packets coming from the tunnel towards the server had their source address changed to that of the WANJet appliance. This feature, known as SNAT (Secure Network Address Translation), is not implemented in this release.
• Load balancing on remote redundant systems: The WANJet appliance does not load balance when sending data to a remote WANJet appliance with a redundant peer.
• VoIP differentiation in Application QoS: You cannot create an Application QoS policy that applies only to VoIP (Voice over Internet Protocol) traffic.
• Multiple VLAN support: The WANJet appliance cannot optimize VLAN-encapsulated traffic; this release does not support VLAN trunks.
• Update, reboot from the Configuration utility: You must update and reboot the WANJet appliance from the command line. If you have Enterprise Manager, you can also perform updates and reboot the system from the Enterprise Manager Configuration utility.
• Syslog server: You can no longer specify the IP address of a Syslog server from the web browser interface. You can manually edit the /etc/syslog-ng/syslog-ng.conf file to set up syslog logging. Refer to Sending data to a syslog server (CR76877) for more details.
• SNMP data transfer: You can use only the Management port for transferring SNMP data. In previous releases, you could choose between the WANJet IP (Bridge IP) address or the Management port IP address.

Optional configuration changes

If you have installed and configured Enterprise Manager, the following configuration information is relevant to you.

Managing WANJet appliances with Enterprise Manager

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 discover WANJet appliances from Enterprise Manager

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:

IPaddress,username,password

 

  IPaddress,username,password

 

  IPaddress,username,password

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.

To get started using Enterprise Manager to manage WANJet appliances

1. Install the WANJet appliances and perform initial configuration using the LCD; then log on and run the Setup utility on each WANJet appliance.
2. Install Enterprise Manager, version 1.4 or later, as instructed in the Enterprise Manager documentation.
3. Log on to the Enterprise Manager.
4. In the navigation pane, expand Enterprise Management and click Devices.
   The Device List opens.
5. Click Discover.
   The Device Discovery screen opens.

   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.

6. Click Import from File.
   The Import Address List screen opens.
7. Click Browse and navigate to the CSV file you created that lists the IP addresses, user names, and passwords of the WANJet appliances.
8. To import the list of addresses, click Import.
   The Device Discovery screen opens again with the addresses from the file in the Address List.
9. To locate the WANJet appliances, click Discover.
   The Enterprise Manager uses the information provided to locate the WANJet appliances and shows them in the device list.

To create and deploy a topology changeset from Enterprise Manager

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).

1. In the navigation pane, expand Enterprise Management and click Changesets.
   The Changeset List screen opens.
2. Click Create.
   The Step 1: New Changeset screen opens.
3. Type a name (for example, WJTopology) and description (optional), and from the Source list, select Device.
4. From the Device list, select one of the WANJet appliances. (It does not matter which one you select at this point.) Leave the Partition field set to Common.
5. Click Next.
   The Step 2: Class Selection screen opens.
6. From the Path List labeled Available, select WAN Optimization/WANJet Topology, and click the Move button (<<) to transfer it to the Selected list. (You can also find a WANJet Topology Example file in the list, which you can refer to if you need additional help.) These files are also located on the WANJet appliance in /config/wj/changeset_template and the examples subdirectory.
7. Click Next.
8. No changes are necessary on the next two screens, Step 3 and Step 4. Click Next twice to skip these screens.
   The Step 5 of 5: Text of Changeset screen opens.
9. The Text box shows the XML text of the topology file template. You need to modify the text so it describes your configuration. Here is a suggestion on how to edit the text.
   
   
   1. Type Ctrl + A, Ctrl + C to select and copy the contents of the file.
   2. Paste it into any XML editor for easier editing. Refer to the section Topology file format and the comments in the file itself for details about how to create the file.
   3. When you are done creating the file, paste it back into the Text box.
10. Next, you need to push the topology file out to all of the WANJet appliances so they all know about each other and can communicate. Click Stage Changeset to start the Staged Changesets wizard.
    The Step 1 of 3: Target Device Selection screen opens.
11. From the Compatible Devices list, select the WANJet appliances that you want to receive the topology file; then click Next.
12. In the Step 2 of 3: Device Partition Selection screen, check that all of the WANJet appliances are listed, then click Next.
13. In the Step 3 of 3: Staged Changeset Properties screen, you can click Verify to make sure that the changeset is well-formed. You can click Deploy Stages Changeset Now to apply it to the WANJet appliances, or click Save to save the changeset for later deployment. See To deploy the changeset later for instructions.
14. In the navigation pane, expand Enterprise Management and click Devices.
    The Device List screen opens.
15. To check that the topology was applied to the WANJet appliances you selected, click the Device Name of one of the appliances, then click Launch to log on to it. You can look at the Remote WANJets list (in WAN Optimization click Remote WANJets) and local subnets (click Local Subnets on the WAN Optimization >> Local WANJet page) to see if they correspond to those defined in the changeset.

To deploy the changeset later

1. In the navigation pane, expand Enterprise Management, and click Changesets.
2. Click the changeset name.
   The changeset properties screen opens.
3. Click Stage for Deployment.
   Step 1 of 3 of the deployment wizard opens.
4. Select the WANJet appliances on which you want to deploy the topology, and click Next.
   Step 2 of 3 of the deployment wizard opens.
5. Click Next (no changes are required).
   Step 3 of 3 of the deployment wizard opens.
6. In the Description box, provide a brief explanation of the changeset being applied, then click Deploy Staged Changeset Now.

To create an optimization policy on a WANJet appliance

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.

1. Log on to one of the WANJet appliances.
2. In the navigation pane, expand WAN Optimization and click Optimization Policy.
3. To create optimization policies for selected ports or services, click Add below the Common table, and provide the information requested on the popup screen.

   Tip: When the popup screen opens, click the Help tab to view details on the screen.

4. To create exceptions from the optimization policies, click the Add button below the Passthrough Destinations table, and provide the information requested on the popup screen.
5. When you are done creating policies, click Save.
   This saves the policy on the WANJet appliance so it takes effect on the local appliance, and so it is accessible and can be deployed from Enterprise Manager.

To create an Application QoS policy on a WANJet appliance

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.

1. Log on to one of the WANJet appliances.
2. In the navigation pane, expand WAN Optimization and click Application QoS.
   The screen automatically lists the WAN links that connect the local WANJet appliance to remote appliances.
3. You create Application QoS policies for a WAN link from the Application QoS screen. Click the IP address of the remote WANJet appliance.
   The Manage the Application QoS Settings of a Remote WANJet popup screen opens.

   Tip: When the popup screen opens, click the Help tab to view details on the screen.

4. To specify the bandwidth for the link, type a value in the Link Bandwidth box.
5. To add an Application QoS policy, click the Add button.
   The Application QoS popup screen opens.
6. Type the Alias (name for the policy) and percentage of bandwidth to guarantee that the policy can use, and after Maximum type the maximum percentage that the policy can borrow from additional unused bandwidth.
7. In the Services box, select the services that you want the policy to apply to; then click OK.
8. When you are done creating policies, click OK.
   You return to the main Application QoS screen.
9. Click Save.
10. Click Save As Template.
    This saves the policy you just created as a template that you can deploy to other WANJet appliances from Enterprise Manager.

To deploy optimization and Application QoS policies from Enterprise Manager

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.

1. Log on to the Enterprise Manager.
2. In the navigation pane, expand Enterprise Management and click Changesets.
   The Changeset List screen opens.
3. Click Create.
   The Step 1: New Changeset screen opens.
4. Type a name (for example, WJPolicies) and description (optional), and from the Source list, select Device.
5. From the Device list, select the WANJet appliance where you created the optimization or Application QoS policy.
6. Click Next.
   The Step 2: Class Selection screen opens.
7. From the Available Path List, select WAN Optimization/Optimization (for optimization policies) or WAN Optimization/Quality of Service (for Application QoS policies), and click the Move button (<<) to transfer it to the Selected list.

   Note: You need to deploy optimization policies separately from QoS policies.

8. Click Next.
9. No changes are necessary on the next two screens, Step 3 and Step 4. Click Next twice to skip these screens.
   The Step 5 of 5: Text of Changeset screen opens.
10. The Text box shows the XML text of the policy template. You use this file as is; no changes are necessary.
11. Click Stage Changeset to start the Staged Changesets wizard.
    The Step 1 of 3: Target Device Selection screen opens.
12. From the Compatible Devices list, select the WANJet appliances that you want to receive the policy file; then click Next.
13. On the Step 2 of 3: Device Partition Selection screen, check that the WANJet appliances you want to receive the policy are listed, then click Next.
14. On the Step 3 of 3: Staged Changeset Properties screen, you can click Verify to make sure that the changeset policy is well-formed. You can click Deploy Stages Changeset Now to apply it to the WANJet appliances. (You can also click Save to save it for later deployment as for the topology changeset.)
15. In the navigation pane, expand Enterprise Management and click Devices.
    The Device List opens.
16. To check that the policy was applied to the WANJet appliances you selected, click the device name of one of the appliances, then click Launch to log on to it. You can look at the policies (in the navigation pane, expand WAN Optimization and click Optimization Policy or Application QoS) to see if they are applied to the appliance.

Changeset formats

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:

• Topology
• Application QoS
• Optimization

The Enterprise Manager lets you access three files for each area:

• Changeset: To provide an XML file representing the actual configuration on the WANJet appliance (located on the WANJet appliance in /config/wj/changeset_templates/*.xml)
• Example file: To aid users in creating new changesets (located on the WANJet appliance in /config/wj/changeset_templates/examples/*.xml)
• Schemata: To provide an overview of the changeset structure and for use with XML editing tools (located on the WANJet appliance in /config/wj/changeset_templates/schemata/*.xsd)

Topology file format

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:

 <WANJet appliance>

 

 <Alias>New York</Alias>

 

 <IP>10.142.1.100</IP> 

 

  </WANJet appliance>

Additionally, for each WANJet appliance, you can associate one or more subnets in the Subnets section. Each Subnet entry includes the following information:

• IP address of the subnet
• Netmask
• Alias for the subnet
• Status flag of either 1 (enabled) or 0 (disabled).

For example:

 <WANJet appliance>

 

 <Alias>Paris</Alias>

 

 <IP>10.142.5.100</IP>

 

 <Subnets>

 

 <Subnet>

 

 <subnetIP>2.2.2.2</subnetIP>

 

 <subnetMask>255.255.255.0</subnetMask>

 

 <subnetAlias>Sarkozy</subnetAlias>

 

 <subnetStatus>1</subnetStatus>

 

 </Subnet>

 

           <Subnet>

 

 <subnetIP>1.1.1.1</subnetIP>

 

 <subnetMask>255.255.255.0</subnetMask>

 

 <subnetAlias>Royal</subnetAlias>

 

 <subnetStatus>1</subnetStatus>

 

 </Subnet>

 

 </Subnets>

 

  </WANJet appliance>

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:

<WanLink>

 

 <IP>10.142.1.100</IP>

 

 <IP>10.142.5.100</IP>

 

 <SharedKey>MySharedKey</SharedKey>

 

 </WanLink>

Application QoS file format

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:

 <QualityOfServicePoliciesTemplate...>

 

 <Policy>

 

 <Alias>VoIP Policy</Alias>

 

 <Bandwidth>

 

 <MinimumPercentage>30</MinimumPercentage>

 

 <MaximumPercentage>50</MaximumPercentage>

 

 </Bandwidth>

 

 <Services>

 

 <Service>

 

 <Name>VoIP</Name>

 

 <Protocol>TCP</Protocol>

 

 </Service>

 

 </Services>

 

 </Policy>

 

 </QualityOfServicePoliciesTemplate>

Optimization policies file format

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:

<Policy>

 

 <Protocol>UDP</Protocol>

 

 <Service>

 

 <PortRange>

 

 <From>1</From>

 

 <To>2</To>

 

 </PortRange>

 

 </Service>

 

 <ProcessingMode>Optimized</ProcessingMode>

 

 <TDR1>On</TDR1>

 

 <TDR2>NotApplicable</TDR2>

 

 <Encryption>NotApplicable</Encryption>

 

 <ConnectionIntercept>NotApplicable</ConnectionIntercept>

 

 <TOSPriority>

 

 <NumericPriority>1</NumericPriority>

 

 </TOSPriority>

 

 </Policy>

[ Top ]

Known issues

The following items are known issues in the current release.

Application QoS issues

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.

Other issues

Firefox rendering issue
In versions 1.5.0.12 and 2.0.0.4 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.

• If the computer you are working on is in the same subnet as the WANJet appliance, you can continue configuring the system from the web browser interface. When you get to the Local WANJet appliance screen, you must retype the WAN gateway IP address.
• If the computer you are working on is in a different subnet from the WANJet appliance, you also lose contact through the web browser interface and remain on the Activating the License screen indefinitely. You need to go to the WANJet appliance and use the LCD to reconfigure the gateway for the bridge IP before you can continue with configuration.

[ Top ]

Copyright © 2007, F5 Networks, Inc., Seattle, Washington.  All rights reserved. 
F5, F5 Networks, the F5 logo, BIG-IP, 3-DNS, iControl, Internet Control Architecture, IP Application Switch, iRules, OneConnect, Packet Velocity, SYN Check, Control Your World, ZoneRunner, uRoam, FirePass, TrafficShield, Transparent Data Reduction, TDR, Swan, WANJet, WebAccelerator, and TMOS are registered trademarks or trademarks, and AskF5 is a service mark, of F5 Networks, Inc., in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. F5 Networks' trademarks may not be used in connection with any product or service except as permitted in writing by F5.

This product protected by U.S. Patent 6,327,242. Other patents pending.