Applies To:

Show Versions Show Versions

Archived Release Note: WANJet version 5.0.1
Release Note

Software Release Date: 12/17/2007
Updated Date: 12/17/2007

This article has been archived, and is no longer maintained.

Summary:

This release note documents the 5.0.1 feature release of the WANJet® appliance. To review the features introduced in this release, see Fixes in this release. For additional information, please refer to the online help on the appliance.
Note: F5 offers both feature releases and maintenance releases. For more information on our new release policies, please see Description of the F5 Networks software version number format.

Contents:

- User documentation for this release
     - Enterprise Manager documentation
- Supported browsers
- Supported platforms
- Installing the software
     - Upgrading the WANJet appliance to version 5.0.1
     - Verifying the MD5 checksum of the installation file
     - Getting Started
- Fixes in this release
- New features and enhancements in the 5.0 release
     - Enhancements to the browser-based interface
     -

Features in release 4.2.x not in this release
- Optional configuration changes
     - Managing WANJet appliances with Enterprise Manager
     - Changeset formats
- Known issues
- Contacting F5 Networks

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.

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 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:

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:

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

[ Top ]


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.1 onto a system that is running 5.0 or 4.2.x. You can upgrade or install version 5.0.1 under several different conditions, as follows:

  • Upgrade WANJet appliance version 5.0 to version 5.0.1
  • Upgrade WANJet appliance version 4.2.x to version 5.0.1 (if your system has a 1 GB CompactFlash)
  • Perform clean installation of WANJet appliance version 5.0.1 (if your system has an 8 GB CompactFlash)
  • Install or upgrade to version 5.0.1 on multiple WANJet appliances using Enterprise Manager

The installation procedure also depends on the size of the CompactFlash® on the WANJet appliance.

Current version Current size of CompactFlash Installation or Upgrade Methods
5.0
8 GB

Upgrade to 5.0.1-- use one of 2 methods:

1. Local install (complete install)
2. Remote install (complete install)

Saved configuration information is maintained.

4.2.x
1 GB
Order 5.0 upgrade kit, install 8 GB CompactFlash (running 5.0), update the BIOS, upgrade to 5.0.1, reconfigure all systems.
4.2.x, 5.0, 5.0.1
8 GB
Perform a PXE (clean) install of 5.0.1 and reconfigure all systems.
5.0
8 GB

If you have Enterprise Manager, update to 5.0.1 using the ISO file. Refer to the Enterprise Manager documentation. Note: You must have configured the WANJet appliance using the Management IP address, not the Bridge IP address to update using Enterprise Manager.

Prerequisites for existing WANJet 400 or 500 appliances

If the WANJet appliances you want to update to 5.0.1 are running version 5.0, they have 8 GB CompactFlash® and their BIOS have 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 v4.2.x and want to run version 5.0, unless you have ordered an 8 GB CompactFlash® with 4.2.4/4.2.14 installed, 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 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. 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 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.1

If your system is running WANJet software version 5.0, you can perform a local, remote, or a clean installation of version 5.0.1. 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.1.

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 to version 5.0.1.

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). For details about downloading the software and using this installation method, see Remote Installation: Upgrading from WANJet appliance version 5.0 to version 5.0.1.

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

[ Top ]


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.1.xx.x.im is the name of the file you downloaded, and local-install-5.0.1.xx.x.im.md5 is the name of its associated MD5 checksum file.

md5sum local-install-5.0.1.xx.x.im
cat local-install-5.0.1.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.

[ Top ]


Getting Started

After you upgrade or install the software, the WANJet appliance is running version 5.0.1. 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 haven't 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 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.
    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.

[ Top ]


Fixes in this release

This release includes the following fixes.

WANJet appliance configuration in a series (CR82707)
In release 5.0, we did not support deploying WANJet appliances in a series on either side of the WAN. In this release, we support deploying two WANJet appliances in a series on both sides of the WAN.

Local WANJet appliance screen values validated (CR83543)
In release 5.0, the validity of the IP addresses on the Local WANJet appliance screen was not verified, only the syntax was checked. In this release, the WANJet appliance checks both the syntax and the validity of the IP addresses on the network.

Application QoS policies for passthrough data (CR84651)
In release 5.0, we did not recommend creating Application QoS policies for passthrough traffic due to performance limitations. You can now successfully create Application QoS policies for passthrough traffic.

TDR-2 Storage Mode change no longer requires reboot (CR84725)
In release 5.0, you needed to reboot the WANJet appliance if you changed the TDR-2 Storage Mode from Disk Based Storage to Memory Based Storage, or the reverse. In this release, a reboot is no longer required when changing the TDR-2 Storage Mode.

Real Time Traffic report (CR84857)
The amount of network traffic shown in the Real Time Traffic report incorrectly showed occasional spikes to 1.5 GB in release 5.0. The Real Time Traffic report now accurately depicts throughput data.

Redundant peer configuration populates Lan Router field (CR85044)
In the last release, checking Enable Redundant Peer and entering Peer values on the Local WANJet appliance screen copied the WAN Gateway value into the Lan Router field. No value is erroneously copied into the LAN Router field in this release.

Application QoS policy implementation (CR85260, CR88218)
When you first created an Application QoS policy in release 5.0, it did not always perform traffic shaping until you edited and resaved the policy. In this release, the Application QoS policy works as configured when initially implemented.

Operational Mode change after reboot (CR85308)
When you rebooted a system running release 5.0, the Mode may have changed from Active to Inactive. In this release, the Mode of a WANJet appliance remains Active after it is rebooted.

Application QoS policies remain in effect (CR85380)
In release 5.0, losing a link with a redundant peer could disable Application QoS policies. In this release, Application QoS policies remain in effect even if the WANJet appliance loses a link connection to a redundant peer or if the operational mode is set to Inactive.

WAN Gateway lost after licensing (CR85442)
In release 5.0, if you were using the WANJet IP (Bridge IP) address for managing the WANJet appliance, the information configured for the WAN gateway was lost after you licensed the system. The WAN gateway value is not lost after licensing in this release.

End User Diagnostics (EUD) updated to version 10.0.6 (CR85557)
Release 5.0.1 includes version 10.0.6, the latest version of the EUD.

MIB OIDs for WANJet 300, 400, and 500 Platforms (CR85575)
In release 5.0, the SNMP MIB file did not list WANJet appliance platforms. The SNMP MIB file now fully supports the WANJet 300, 400, and 500 platforms.

Default gateway change no longer erases static routes (CR85623)
When you changed the WANJet IP setting or the gateway (WAN Gateway or LAN Router settings) in release 5.0, all static routes would be lost. In this release, changing these settings has no impact on the static routes.

Configuration changes (CR85676)
In release 5.0, changing the WANJet appliance configuration could cause the Operational Mode to change from Active to Inactive. In this release, configuration changes to WANJet appliances do not change the Operational Mode.

ICMP and UDP packets in One Arm mode (CR86879)
When configured in One Arm mode in release 5.0, the WANJet appliance could not forward ICMP or UDP packets. In this release, WANJet appliances deployed in a one arm configuration can forward ICMP and UDP packets as needed.

Passthrough traffic failure (CR88218)
In the last release, if you used the WANJet appliance primarily for passthrough traffic rather than optimized traffic, some passthrough traffic would fail to transfer correctly. In release 5.0.1, all passthrough traffic transfers correctly.


[ Top ]


New features and enhancements in the 5.0 release

The 5.0 release included 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 TMOSTM (Traffic Management Operating System) architecture. TMOS provides a unified system for application delivery and network adaptability.

Browser-based interface redesign
The WANJet appliance has a new streamlined browser-based 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 browser-based interface for more details.

Some functions are no longer available in the browser-based 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 browser-based 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 browser-based interface

The following table describes changes to features of the WANJet appliance browser-based interface as of the 5.0 release and as a result of TMOS integration.

Feature Description
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.
Dashboard

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)
Operational Mode: Active

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 ]


Features in release 4.2.x not in this release

The following 4.2.x 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 browser-based 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.

[ Top ]


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

One Arm and Settings for Delayed Connection Acceptance
Do not configure the Settings for Delayed Connection Acceptance on the client side of a WANJet appliance that is configured in a one arm configuration. Configuring these settings could block connections from the client side.

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.

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.

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.

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.

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 to version 5.0.1), 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 to version 5.0.1.

Disable delayed acknowledgement setting (CR89926)
A delayed acknowledgement setting in the TCP profile causes the WANJet appliance to briefly delay sending an acknowledgement to a TCP transfer:

  • Until TCP encounters another packet being sent in the opposite direction within the same TCP connection, at which time the appliance "piggybacks" the acknowledgement onto the packet, or
  • Until the Delayed Acknowledgement timer expires (typically, 200 milliseconds), at which time the appliance sends an acknowledgement by itself.

In this release, delayed acknowledgements are enabled by default. When enabled, optimized session throughput may be limited to 100 mbps per session. This behavior is on a single session basis and may not affect normal multi-user multi-session usage.

We recommend disabling the delayed acknowledgement settings for the LAN, WAN, and VNIC in the TCP profile so that the WANJet appliance achieves the full optimized per session throughput. To disable delayed acknowledgement, run the following commands from the command line:

   b profile tcp wj-tcp-lan-optimized delayed acks disable 
b profile tcp wj-tcp-wan-optimized delayed acks disable
b profile tcp wj-tcp-vnic-optimized delayed acks disable

[ Top ]

 

Contacting F5 Networks

  Phone: (206) 272-6888
Fax: (206) 272-6802
Web: http://support.f5.com
Email: support@f5.com

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


Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)