Applies To:

Show Versions Show Versions

Archived Release Note: WANJet version 3.1.16
Release Note

Software Release Date: 12/04/2005
Updated Date: 12/04/2005

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

Summary:

This release note documents the version 3.1.16 release of the WANJet software. This maintenance release is cumulative. You can apply the software upgrade to version 3.1.1 and later. For information about installing the software, please refer to the WANJet User Guide.

Contents:

- Supported platforms
- Backing up your current configuration
- Installing the software
- New features and fixes in this release
     - New features
     - Fixes in this release
- Fixes and enhancements in prior releases
- Known issues


Supported platforms

This release supports the following platforms:

  • WANJet 200
  • WANJet 400

If you are unsure which platform you have, look on the About screen of the WANJet system user interface.

[ Top ]

Backing up your current configuration

If you want to back up your current configuration before installing this software, complete the following steps:

  1. Log in to the WANJet web utility.

    https://<your WANJet 200 or WANJet 400 appliance IP address>:10000

  2. On the System area, click the Backup link.

  3. Save the backup file to your local hard disk.

 

[ Top ]

Installing the software

For instructions on how to install the WANJet 3.1.16 software, please refer to the WANJet User Guide.

[ Top ]

New features and fixes in this release

This release includes the following new features and fixes.

New features

Transparent Data Reduction (TDR)
The WANJet system now includes data reduction technology that provides a dramatic decrease in the amount of bandwidth consumed across a WAN link for repeated data transfers.

SSL encryption
Using the Secure Sockets Layer (SSL) protocol, the WANJet system can encrypt the TCP traffic that the system is optimizing before the traffic travels across a WAN link.

UDP tunneling
Due to the WANJet system's TCP-based tunneling architecture, certain applications such as file sharing (for example, NFS), data replication (for example, Veritas Volume Replicator), SYSLOG, and network backup (all of which have User Datagram Protocol (UDP) as their underlying transport) can now benefit from reliable delivery across a WAN. In addition, ACM5's powerful data compression engine can significantly reduce UDP traffic volume. UDP applications that require real-time delivery (for example, VOIP, video, and more), do not benefit from the compression and reliable delivery provided by this feature.

RADIUS support
A WANJet 200 or WANJet 400 appliance can now be seamlessly integrated into a Remote Authentication Dial-In User Service (RADIUS) authentication infrastructure. RADIUS is a widely-used, standards-based (RFC 2865) authentication protocol. It is commonly used for centralized user administration on embedded network devices such as routers and switches. Users who need administrative access to a WANJet 200 or WANJet 400 appliance can now log in using the same user name and password they use for other elements (for example, routers, servers, and so on) in the network, thereby greatly simplifying overall device-level administration.

Dual software version and configuration
All WANJet 200 and WANJet 400 appliances can now simultaneously hold two separate software versions (one active and one inactive -- for example 3.0, and 3.1) and corresponding user configuration files. This capability is very useful during software upgrades. You can place a new software version in the inactive area and then load the software by restarting the system. Meanwhile, the previous version is saved and the network administrator can revert back to the previous version at any time.

Statistics export to CSV format
The WANJet system statistics data can now be saved in comma separated value (CSV) format for logging purposes, and can be viewed later with a spreadsheet or database program. CSV is a common data format that applications such as Microsoft® Excel® recognize.

Real-time reporting
This feature gives you an immediate, up-to-date, graphical view of the traffic traversing the WANJet system.

Auto-generated email
You can configure the WANJet system to automatically generate an email alert when an error condition occurs that causes the WANJet system to restart.

Fixes in this release

This release includes the following fixes.

WANJet 200 performance (24392)
We have made improvements to the WANJet 200 performance.

Application QoS user interface screen (24400)
We have made cosmetic improvements to the Application QoS user interface screen.

TCP tuning for multiple, unlike WAN links (24406)
TCP tuning for multiple, unlike WAN links now functions correctly.

Redundant peer configuration on WANJET 200 platform (24459)
You can now have a redundant peer configuration on the WANJet 200 platform.

SNMP reporting errors (BUG3100, 3002)
There are no longer errors in SNMP reporting.

Support for 802.3x Ethernet flow control to WANJet 200 platform (24517)
We have added support for 802.3x Ethernet flow control to the WANJet 200 platform.

Support email address on Alert user interface screen (BUG3108)
The support email address on the Alert user interface screen is now correct.

Traffic blockage under heavy load and unstable link conditions (BUG3080)
Traffic blockage no longer occurs when the system is under heavy load and has unstable link conditions.

Queue length on Tuning user interface screen (BUG3115)
We have fixed the queue lentgh on the tuning user interface screen.

[ Top ]

Fixes and enhancements in prior releases

The current release includes the fixes and enhancements that were distributed in prior releases, as listed below. (Prior releases are listed with the most recent first.)

Version 3.1.15

The 3.1.15 release included the following fixes and enhancements.

TCP Westwood taking effect
We have fixed the problem that prevented TCP Westwood from taking effect, and it now functions properly.

Version 3.1.14

The 3.1.14 release included the following fixes and enhancements.

Effectiveness of TDR-2 (p24259)
TDR-2 has been re-synchronized and has regained its effectiveness.

F5 re-branding (p24261)
The WANJet software and documentation have been re-branded with F5 branding.

Diagnostic message (p24263)
We have improved the diagnostic message.

TDR-2 linkup synchronization (p24265)
The TDR-2 linkup synchronization issue has been resolved.

TCP Vegas congestion control replaced (p24349)
We have replaced the TCP Vegas congestion control with TCP Westwood.

SNMP reporting errors (BUG3024)
There are no longer errors in SNMP reporting.

Optimized tunnel statistics reporting (BUG3039)
Optimized tunnel statistics reporting is now functioning correctly.

Version 3.1.13

The 3.1.13 release included the following fixes and enhancements.

Low bandwidth tuning memory issues
The system no longer runs out of memory at low bandwidth tuning settings.

Dropped tunnels and saturated link
The tunnels are no longer dropped when the link is saturated.

Performance at high link bandwidths
We changed the congestion control algorithm to get higher performance at high link bandwidths.

Hardware bypass failover on WANJet 200 platform
The hardware bypass failover on the WANJet 200 platform now functions properly.

Low bandwidth tuning memory issues
The system no longer runs out of memory at low bandwidth tuning settings.

Version number in the WANJet system user interface and snapshot (BUG3048)
The WANJet system user interface and snapshot now have the correct version number.

F5 dossier generator
We have added the F5 dossier generator for F5 manufacturing.

Low bandwidth network instability
We made the low bandwidth network stable by reducing QoS output queusize to a function of bandwidth and rtt.

Inefficient network utilization
We fixed the problem that caused inefficient network utilization (many small packets).

Web-based remote upgrade facility
We have added a web-based remote upgrade facility.

Version 3.1.12

The 3.1.12 release included the following fixes and enhancements.

Setting NIC parameters (BUG3303)
Setting NIC parameters now works properly.

Version 3.1.11

The 3.1.11 release included the following fixes and enhancements.

Blocked traffic due to TDR-2
Traffic is no longer blocked if TDR-2 is enabled on one end of a link and disabled on the other.

Version 3.1.10

The 3.1.10 release included the following fixes and enhancements.

Optimized connections count (BUG2989)
The optimized connections count is now correct.

Performance on low bandwidth links (BUG2992)
We have improved the performance of the very low bandwidth links by setting a floor on the TCP window of four full-size packets. Note that this change could increase the likelihood of overrunning low-capacity routers on low speed links and causing packet loss. The best mechanism to create an even, non-bursty, low rate of traffic is to set an overall bandwidth slightly below the link bandwidth on the application QoS screen.

NIC settings reset to Auto Negotiate (BUG2932)
The NIC settings no longer reset to Auto Negotiate after a remote upgrade.

Timestamp on system diagnostic messages
We have added a timestamp to the system diagnostic messages.

High memory use reboot condition on WANJet 200 platform
The high memory use reboot condition no longer exists on the WANJet 200 platform.

[ Top ]

Known issues

The following items are known issues in the current release.

Performing a remote upgrade from versions 3.1.1 or 3.1.2
You can perform a remote upgrade to version 3.1.16 from any 3.1.x release. However, if performing an upgrade from version 3.1.1 or 3.1.2, you must perform the following procedure.

  1. Make all WANJet systems inactive (on the operational mode page).

  2. Upgrade all of the WANJet systems.

  3. Bring all of the WANJet systems back to active status, one at a time.

 

Migrating configuration settings from version 3.0 to 3.1
You cannot migrate configuration settings from version 3.0 to version 3.1. You must create all 3.1 configurations from scratch.

Migrating configuration settings from version 3.1.0 (b88) to 3.1
You cannot migrate configuration settings from version 3.1.0 (b88) to version 3.1. You must create all 3.1.0 configurations from scratch.

Required open TCP ports on a firewall
For the WANJet system to function properly, TCP ports 3703, 3702, and 3701 must all be open on a firewall.

Default user name and password
The default user name is admin, and the default password is swanlabs.

SSL encryption implementation
SSL encryption is currently implemented only for optimized TCP traffic. In future releases, we plan to support other protocols such as UDP, ICMP, and others, for SSL encryption.

VLAN traffic and LAN router value configuration
If you want to process VLAN traffic, do not configure a LAN Router value in the Local WANJet link of the web user interface.

Management Ethernet port issues
Both the WANJet 200 and WANJet 400 appliances have a management Ethernet port; however, this port is not currently functional.

TDR-2 performance enhancements (TT2869)
Full TDR-2 performance enhancements are not realized with some text files.

Link down entries in diagnostic log (TT2926)
There are occasional unexplained link down entries in the diagnostic log, however, connectivity is not affected.

Optimizable connections issues (TT2930)
Some optimizable connections are not optimized. This might be related to local configuration of remote subnets.

WANJet 200 platform and hardware bypass mode (TT3079)
Occasionally, when the WANJet system on the WANJet 200 platform is under sustained, heavy load, it has entered hardware bypass mode, where traffic is passed through and not optimized. To resolve this issue, reset the WANJet system.

Blocked traffic due to extremely heavy load (TT3102)
Occasionally, when the WANJet system is under sustained, extremely heavy load, consisting of high request per second rate, the system has entered a state in which traffic is blocked. To resolve this issue, reset the WANJet system.

[ Top ]

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)