Applies To:Show Versions
This release note documents the version 3.1.17 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.
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.
Backing up your current configuration
To back up your current configuration before installing the software upgrade, complete the following steps.
- Log in to the WANJet Web UI.
https://<your WANJet 200 or WANJet 400 appliance IP address>:10000
- From the menu, click System.
- Click Backup.
The Backup screen displays.
- Click the word, here.
The browser opens a File Download window for you to save the backup file to your local computer. This default backup file is Settings-<ServerName>.NTCL.
- Save the backup file to your local hard disk.
- Rename the backup file to identify the specific WANJet appliance that you are backing up and the current date.
Installing the software
To install the software upgrade, perform the following steps.
- Verify that a disk image of the new version of the WANJet software is accessible from the local computer on which you are viewing the WANJet Web UI (on CD-ROM, for example).
- From the WANJet Web UI menu, click System.
- Click Upgrade.
The Upgrade screen displays.
- Click Stop [Server Name] to stop the current processing session.
A confirmation request displays.
- Click the OK button to continue.
- Click the Browse button and locate the upgrade file on your computer.
- Upload the upgrade file to the WANJet appliance.
- Click Upgrade WANJet.
The WANJet appliance restarts automatically when the upgrade process is complete.
Performing a remote upgrade from versions 3.1.1 or 3.1.2
You can perform a remote upgrade to version 3.1.17 from any 3.1.x release. However, if you are upgrading remotely from version 3.1.1 or 3.1.2, you must also complete the following procedure.
- From the operational mode page, change the status of all WANJet systems to inactive.
- Install the software upgrade on all of the WANJet systems.
- One at a time, change the status for all of the WANJet systems to active.
New features and fixes in this release
This release includes the following new features and fixes.
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.
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.
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.
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
You can now save the WANJet system statistics data in comma-separated value (CSV) format for logging purposes, and you can view the data later with a spreadsheet or database program. CSV is a common data format that applications such as Microsoft® Excel® recognize.
This feature gives you an immediate, up-to-date, graphical view of the traffic traversing the WANJet system.
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
TCP tuning (24611)
We have incorporated additional fixes to TCP tuning for multiple, different WAN links. (These fixes are in conjunction with the fixes incorporated into 24406 for the version 3.1.16 software release.) Data is now properly regulated to the link speed in mesh configurations, where the links are not the same speed.
QoS statistics (BUG3049)
Reports and snapshots now contain QoS statistics.
Email notification (24790)
The email notification destination is now WANJetSupport@f5.com.
Performance under heavy load (24792, 24809, 24813, 24820, 24775/BUG3120)
We have improved system performance when it is under heavy load.
Traffic blockage with mixed platform redundant deployments (24877)
We have fixed the traffic blockage issue that occurred when a WANJet 400 (under heavy load) initiates traffic to a peer WANJet 200.
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.)
The 3.1.16 release included the following fixes and enhancements.
WANJet 200 performance (24392)
WANJet 200 performance is improved.
Real Time Traffic report (24851)
The real Time Traffic applet now works properly with one-arm deployment.
Application QoS screen (24400)
Cosmetic improvements were made to the Application QoS screen.
TCP tuning (24406)
Fixes for TCP tuning for multiple, different WAN links.
WANJet 200 platform redundant configuration (24459)
Redundant peer configurations are now allowed on the WANJet 200 platform.
SNMP reporting (BUG3100, 3002)
SNMP reporting errors are fixed.
Ethernet flow control (24517)
Added support for 802.3x Ethernet flow control to the WANJet 200 platform.
Email alert screen (BUG3108)
The Email alert screen now displays WANJetSupport@f5.com.
Traffic blockage under heavy load on unreliable networks (24551, BUG3080)
Fixed the traffic blockage issue that occurred when mixed WANJet 200/400 platform deployments were under heavy load on unreliable networks.
Tuning screen (BUG3115)
We have fixed the queue length on the Tuning screen.
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.
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.
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 queu size to a function of bandwidth and round trip time.
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.
The 3.1.12 release included the following fixes and enhancements.
Setting NIC parameters (BUG3303)
Setting NIC parameters now works properly.
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.
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 (BUG2904)
The high memory use reboot condition no longer exists on the WANJet 200 platform.
The following items are known issues in the current release.
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.
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 UI.
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 (TT3102)
If the WANJet appliance is under sustained, extremely heavy load of a high rate of requests per second, the WANJet may occasionally block a small percentage of TCP attempts. To resolve this issue, reset the WANJet system.