• Features in release 4.2.x not in this release

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. 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 Appliance 4.2.x to 5.0.2 Migration 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 Knowledge Base on the AskF5 Technical Support web site.

BIG-IP system documentation

Because the WANJet appliance 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 (Version 9.4.2)
  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 browser-based 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 (C25)
• WANJet 400 (D41)
• WANJet 500 (D100)

[ Top ]

Installing the software

The installation instructions vary, depending on whether you are installing the WANJet appliance version 5.0.2 onto a system that is running version 5.0.1, 5.0, or 4.2.x. You can upgrade or install version 5.0.2 under several different conditions as shown in the table that follows.

Note: You cannot upgrade from version 5.0. However, you can perform a PXE (clean) install of version 5.0.2.

Prerequisites for existing WANJet 400 or 500 appliances

If the WANJet appliances you want to update to version 5.0.2 are running version 5.0.1, they already have an 8 GB CompactFlash^® and their BIOS has already been upgraded. You can proceed to install or update the software using any of the methods described here.

If you have existing WANJet 400 or 500 appliances running version 4.2.x and want to run version 5.0.2, unless the appliance already has an 8 GB CompactFlash^®, you must order an upgrade kit through your F5 Sales Representative. The upgrade kit contains

• 8 GB CompactFlash^® with WANJet version 5.0.1 installed
• WANJet 500 BIOS Upgrade CD-ROM
• WANJet Appliance CompactFlash Card and BIOS Upgrade Instructions

You need to replace the 1 GB CompactFlash^® with the 8 GB CompactFlash card on which version 5.0.1 is installed. Existing WANJet 500 appliances also require a BIOS upgrade to OBJ-0200-03 Rev A. Refer to the WANJet Appliance CompactFlash Card and BIOS Upgrade Instructions for information on how to upgrade the BIOS (WANJet 500 only) and replace the CompactFlash card (WANJet 400 and 500). After you update the CompactFlash and the BIOS, the system will be running version 5.0.1. You can proceed to install or update the software using any of the methods described here.

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 additional information, refer to the WANJet Appliance Administrator Guide.

Optional 10K RPM hard disk drive upgrade kit for WANJet 500 appliances

If you plan to use disk-based storage for TDR-2, WANJet 500 appliances have an optional hard drive upgrade kit available. The kit allows you to upgrade existing 7200 RPM hard drives to 10K RPM hard drives. The upgraded disk drives provide the best possible TDR-2 disk caching performance when using storage on disk. You can order upgrade kits to replace the 7200 PRM drives on existing appliances. New WANJet 500 appliances come with one 10K RPM drive. Ask your F5 Networks representative if it would be to your advantage to use disk-based storage, as opposed to memory-based storage.

Upgrading the WANJet appliance to version 5.0.2

If your system is running WANJet software version 5.0.1, you can perform a local, remote, or a clean installation of version 5.0.2. If you are running WANJet software version 4.2.x on an appliance with an 8 GB CompactFlash, you must perform a clean installation of version 5.0.2.

Performing a local installation

For a local upgrade, you copy an IM package onto the system you intend to upgrade. For details about downloading the software and using this installation method, see Local Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.

Performing a remote installation

For a remote upgrade, you run the upgrade from a management workstation that is not directly connected to the system you intend to upgrade. A remote upgrade requires that the Management IP address has been configured (rather than the Bridge IP address). For details about downloading the software and using this installation method, see Remote Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.

Performing a PXE server installation

If you do not plan to roll forward a configuration, you can perform a clean installation on the system. For details about downloading the software and using this installation method, see PXE Installation: Performing a clean installation of WANJet appliance version 5.0.2.

Verifying the MD5 checksum of the installation file

After you download the installation file and its associated MD5 checksum file, and before you perform the installation, we recommend you test the integrity of the installation file. This verifies that you have downloaded a good copy of the file. To run the test, type the following commands, where local-install-5.0.2.xx.x.im is the name of the file you downloaded, and local-install-5.0.2.xx.x.im.md5 is the name of its associated MD5 checksum file.

md5sum local-install-5.0.2.xx.x.im
cat local-install-5.0.2.xx.x.md5
 

If the output from both commands does not exactly match, download the file again. Repeat the download process until the MD5 checksum of the downloaded file matches the text string in the associated .md5 file.

Getting Started

After you upgrade or install the software, the WANJet appliance is running version 5.0.2. You can log on and get started using it.

To start using the WANJet appliance

Note: We strongly recommend configuring the management port to log on to the WANJet appliance. 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 (if you have not already done so):
   
   • 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 logon 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.
   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 for the first time.

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.

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 browser-based 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, and an optional third section if you have a redundant peer. 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>       <Alias>New York</Alias>       <IP>10.142.1.100</IP>   </WANJet>

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:

 <WANJets>    <WANJet>      <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>  </WANJets>

The second section of the file, the WanLinks section, specifies the links between each of the WANJet appliances. For example:

<WanLinks>
		 	<WanLink>
			<!-- Specify one side of the WANLink 'a' -->
			<IP side="a">1.1.1.1</IP>
			<!-- Specify the other side of the link 'b' -->
			<IP side="b">2.2.2.2</IP>
			<!-- Give the link bandwidth in the direction a -> b -->
			<BandwidthAB units="kbps">300</BandwidthAB>
			<!-- Give the link bandwidth in the direction a -> b -->
			<BandwidthBA units="mbps">29.2</BandwidthBA>
			<!-- Sprcify the RTT for the link -->
			<RTT>50</RTT>
			<!-- This section sets up a remote redundant peer -->
			<SharedKey>Hello</SharedKey>
		</WanLink>
		<WanLink>
			<IP side="a">1.1.1.1</IP>
			<IP side="b">3.3.3.3</IP>
			<SharedKey>Zdravstvuite</SharedKey>
		</WanLink>
		<WanLink>
			<IP side="a">1.1.1.1</IP>
			<IP side="b">4.4.4.4</IP>
			<SharedKey>HowDoYouDo</SharedKey>
		</WanLink>
		<WanLink>
			<IP side="a">1.1.1.1</IP>
			<IP side="b">5.5.5.5</IP>
			<SharedKey>Hi</SharedKey>
		</WanLink>
	</WanLinks>  	

Use the following section to set up a redundant peer:

<RedundantLinks>
		<RedundantLink>
			<LocalIP>1.1.1.1</LocalIP>
			<PrimaryRemoteIP>2.2.2.2</PrimaryRemoteIP>
			<SecondaryRemoteIP>3.3.3.3</SecondaryRemoteIP>
		</RedundantLink>
	</RedundantLinks>
      

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.

Firefox rendering issue
In versions 1.5.0.12 and 2.0.0.4 of the Firefox^® browser-based interface, empty text boxes in the WANJet browser interface may contain XX. This does not affect the WANJet appliance functionality.

Cannot specify MTU in topology file (CR75704)
If using Enterprise Manager to deploy WANJet appliances in a networking environment that includes a LAN router, it is necessary to create a static route for every remote WANJet.  To create a route, you need to specify the Maximum Transmission Unit (MTU), which is the largest allowable packet size. When deploying by using a topology file, there is currently no way to specify the MTU value. The WANJet appliance uses the following default values: 1500 for direct and 1400 for VPN. The workaround is to deploy the WANJet appliances using Enterprise Manager, then configure the MTU values on the WANJet appliances, as needed.

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 browser-based 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.

Limited error checking on SNMP Agent Configuration screen (CR77797)
When you are adding IP addresses into the Client Allow List, the addresses are not validated. Be careful to specify valid IP addresses or subnets in the Client Allow List.

Public access record on SNMP Access (v1, v2c) screen (CR77848)
By default, the system creates a public access record and displays it on the SNMP Access (v1, v2c) screen. Although the system allows you to delete that record, you can still perform SNMP queries as if it were not deleted. We do not recommend deleting the public access record.

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 browser-based 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 browser-based 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 browser-based 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. Set it back to Active after replacing the 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.

Changing WANJet appliance IP address does not change local subnets (CR81563)
When you specify the WANJet appliance IP address, and click Include WANJet Subnet on the Local Subnets screen, the WANJet appliance automatically adds the local subnet to the list. If you change the appliance's IP address, the local subnet does not change. The workaround for this is to select the local subnet if it is no longer valid and remove it.

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.

Optimized Packets on WANJet Links Monitoring screen (CR82457)
The WANJet Links Diagnostics report shows a value for Optimized Packets. For increased clarity, this field should be labeled Optimized Packets Received, because the value does not include optimized packets that were sent from the WANJet appliance.

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.

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.

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 browser-based interface still displayed, you may see the message Configuration Utility Restarting, and the browser-based interface is unavailable. When the system is restarted, you can either refresh the browser-based interface or open a new browser window to display the login prompt.

RMON1 values not available (CR84513)
Only RMON2 values are available if you use a MIB browser to view data in the WANJet appliance MIBs.

Diagnostic reports may not show correct data (CR84544, CR84856)
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.

WANJet 500 LCD netboot command not working (CR84640)
Issuing the netboot command from the LCD on a WANJet 500 reboots the WANJet appliance locally without attempting to load an image from the network.

Set Operational Mode to Active (CR84777)
When you start up a WANJet appliance 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.

Invalid network interface option (CR85562)
On the Network Interface screen, when you click lan, wan, or peer, you display the General Properties screen for the interface. The Requested Media option allows you to select 1000base TX half although this setting is not available for any of the interfaces on the WANJet appliance.

Unable to change Management IP address (CR85614)
If you have routes configured for the management interface in addition to the default management route (System >> Configuration >> Management Routes), you need to delete the additional routes first if you want to change the Management IP address. Currently, attempts to change the Management IP address will fail when you have additional management routes configured, and you receive no warning message.

Cannot change WAN interface speed and duplex settings from the LCD (CR 85673)
On the LCD, the settings to change the WAN interface speed and duplex do not work. The workaround is to change the setting on the Network Interface screen instead.

Create or change Application QoS policies (CR87979, CR88978)
When you create or change Application QoS policies, they may not work as expected until you restart the Traffic Management Microkernel (TMM) process. The workaround for this is to restart TMM after creating or changing an Application QoS policy. At the command line, type bigstart restart tmm.

Saved configuration not fully reinstated on upgrade (CR88077)
When upgrading to version 5.0.1, the saved configuration is not reinstated fully on the WANJet appliance. After upgrading, you need to follow these steps to complete the process:

1. From the command line, run a b load command to load all configuration settings onto the WANJet appliance.
2. On the Local WANJet screen, reconfigure the WAN Gateway setting, and click Save.
3. On the Operational Mode screen, set Mode to Active, and click Save.

Upgrade or installation from Enterprise Manager requires Management IP address (CR88080)
If you want to use Enterprise Manager to install or upgrade WANJet appliances, you must have configured the Management IP address, rather than the Bridge IP address, for communication. The Enterprise Manager can discover the WANJet unit, but when you try to install the image, the WANJet appliance does not appear to be compatible with the install image.

Remote installation requires Management IP address (CR88082)
If you want to perform a remote installation (as described in Remote Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2), you must configure a Management IP address, rather than the Bridge IP address, for communication. A remote installation using the Bridge IP address causes an installation error. If you are using the Bridge IP address to log on to the WANJet appliance, you must use the local installation to upgrade the device. Refer to Local Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.

Connection Intercept requires 5 sec idle connection (CR90627)
Connection Intercept requires the connection to be idle for 5 seconds in order to interrupt and reset it.

Web-based diagnostics shen 32 spokes connect to one hub (CR91193)
When you deploy one WANJet appliance as the hub for 32 spokes and each of the spokes is handling many connections, the hub WANJet appliance is slow to display optimization diagnostics.

WCCP one-arm configuration (CR91371)
When you change and save any of the WCCP settings in a one-arm configuration, the WANJet appliance terminates the tunnel, stops, and then restarts the TMM process, which closes all existing connections and restarts them. We recommend that you make changes to the WCCP configuration when it would be the least disruptive to your users.

WCCP with GRE tunneling in an HSRP environment (CR92395)
If you configure WCCP with generic routing encapsulation (GRE) tunneling as the redirection method in an HSRP (Hot Standby Router Protocol) environment, the WANJet appliance may not be able to optimize traffic connections. A possible workaround for this is to configure all routers in an HSRP cluster so they have the same router identifier. However, this configuration has not been fully tested.

Memory-based storage for TDR-2 with hub and multiple spokes (CR93366)
If you configure memory-based storage on a hub with multiple spokes, TDR-2 optimization performance is limited. F5 recommends using disk-based storage on the hub when configuring more than five spokes. Note that the bandwidth of the hub and spoke links also impacts optimization performance.

Topology changeset link tuning values (CR93772)
When you configure linked tuning through the web-based interface, the Send Bandwidth and Receive Bandwidth settings cannot exceed 62000 kbps (622 mbps), and the RTT (Round Trip Time) setting cannot exceed 2000 msec. When you are configuring linked tuning through the topology changeset, Enterprise Manager allows the deployment of any value, including invalid ones, for these fields without providing an error message. Enterprise Manager needs to do additional error checking for the topology changeset.

Sys-reset command unreliable (CR95158)
Running the sys-reset command to restore factory defaults may render the Configuration utility on the WANJet appliance to be unusable. We recommend that you not use the sys-reset command, and instead perform a clean installation of the software if you need to restore factory defaults.

Redundant WANJet appliance still appears after being removed (CR95230)
If you try to remove a redundant remote WANJet appliance from the Remote WANJet appliance screen by clicking the IP address of the remote appliance and changing the WANJet Type from Redundant to Single, the redundant appliance still appears on the screen. To remove a redundant remote WANJet appliance, click the IP address of the remote appliance, clear the Redundant Peer IP address first, then change the WANJet Type from Redundant to Single. The redundant peer no longer appears on the screen.

[ Top ]

Contacting F5 Networks

For additional information, please visit http://www.f5.com.

Copyright © 2008, F5 Networks, Inc., Seattle, Washington.  All rights reserved. 
F5, F5 Networks, the F5 logo, BIG-IP, 3-DNS, Acopia, Acopia Networks, Application Accelerator, AskF5, Application Security Manager, ASM, ARX, Data Guard, Enterprise Manager, EM, FirePass, FreedomFabric, Global Traffic Manager, GTM, iControl, Intelligent Browser Referencing, Internet Control Architecture, IP Application Switch, iRules, Link Controller, LC, Local Traffic Manager, LTM, Message Security Module, MSM, NetCelera, OneConnect, Packet Velocity, Secure Access Manager, SAM, SSL Accelerator, SYN Check, Traffic Management Operating System, TMOS, TrafficShield, Transparent Data Reduction, uRoam, VIPRION, WANJet, WebAccelerator, and ZoneRunner, are trademarks or service marks of F5 Networks, Inc., in the U.S. and other countries, and may not be used without F5's express written consent.

This product protected by U.S. Patent 6,327,242 and 7,126,955. Other patents pending.