Software Release Date: 11/02/2006
Updated Date: 12/04/2006
This release note documents the version 4.2.8 feature release of the WANJet appliance, and documents changes since the last feature release, version 4.2.5. To review the features introduced in versions 4.2.6, 4.2.7, and 4.2.8, see New features and fixes in this release. For new customers, the software is preinstalled on the WANJet appliance. For existing customers, you can apply the software upgrade to 3.1.1 and later. For information about installing the software upgrade, please refer to Upgrading the software. For additional information, please refer to the WANJet Appliance Administrator Guide.
Note: F5 now 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.
In addition to these release notes, the following user documentation is relevant to this release (depending on your platform).
You can find the product documentation and the solutions database on the AskF5 Technical Support web site, http://login.f5.com.
The supported browsers for the Web UI are:
This release supports the following platforms:
If you are unsure which platform you have, click the About link from any screen in the WANJet appliance's Web UI.
To back up your current configuration before installing the software upgrade, complete the following steps.
https://<WANJet IP address>:10000
To upgrade the WANJet appliance to version 4.2.8, complete these tasks:
Important: For the WANJet appliance to function properly, TCP ports 3703, 3702, 3701, 10000, and 10001 must all be open on a firewall. Any firewalls separating the WANJet appliances must have these ports open. For specific information about configuring ports, refer to the WANJet Appliance Administrator Guide.
Important: Version 4.0 introduced a new licensing procedure. If you are upgrading from version 3.1.x, you must first obtain a Base Registration Key. Do not proceed with the upgrade until you have the Base Registration Key. If you did not receive an email with a Base Registration Key, contact F5 Networks Technical Support (and be sure to have the WANJet appliance serial number) before attempting to install the software upgrade.
https://<WANJet IP address>:10000
The WANJet Status screen opens.
If you have not activated the license of the WANJet appliance you plan to upgrade, activate it now (before upgrading). See To activate the license later in this document for details. (If you do not know if the license has been activated, check on the WANJet Status screen, next to License. If it says Not Entered, it is not activated.)
You can perform a remote upgrade to version 4.2.8 from version 3.1.1 or later. If you are upgrading remotely from version 3.1.1 or 3.1.2, you must also complete the following tasks.
Note: You need to perform this procedure only if you have not previously activated the WANJet appliance license.
Note: You need to perform this procedure only if you have not previously saved the chassis serial number in the About box.
This release includes the following new features and fixes.
Configuring the WANJet appliance as part of a trunked VLAN (CR62643)
You can now set up a WANJet appliance as part of a trunked VLAN if this is required in your networking environment (although this is not a common setup). In a trunked VLAN, all frames require VLAN tags.
To include the WANJet appliance in a trunked VLAN, you need to specify the trunked VLAN ID that you want the WANJet appliance to include in the frames. This configuration change requires a reboot of the WANJet appliance. Refer to Configuring the trunked VLAN ID setting in the Optional configuration changes section for details on how to add the trunked VLAN ID to the WANJet appliance.
Dynamic configuration of optimization policies (CR63327)
You can now change optimization policies while the WANJet appliance is optimizing traffic without having to restart the appliance or interrupt your users. Refer to Adding or reconfiguring optimization policies in the Optional configuration changes section for details on changing optimization policies.
24 spokes in hub and spoke configuration (CR69591)
For large deployments, the WANJet appliance supports hub and spoke configurations with up to 24 spokes. We have successfully tested this configuration.
This release includes the following fixes.
VLAN traffic and LAN router value configuration (CR64021)
Previously, when processing VLAN traffic, you could not configure a LAN Router to work with the local WANJet appliance. In this release, we have removed this restriction. If the WANJet appliance processes VLAN traffic, you can configure a LAN Router value in the Local WANJet link of the Web UI, as needed.
Application QoS bandwidth (CR64742)
In previous releases, when configuring an Application QoS Policy, setting the Link Bandwidth to 128 Kb/s or less might reduce FTP download speed. With this release, a low bandwidth size no longer impacts FTP download speed.
WANJet 200: NIC speed and duplex settings (CR65386)
In previous releases, if you changed the NIC speed and duplex settings on a WANJet 200, then rebooted the appliance, the setting could be lost and revert to the default settings. The WANJet 200 now correctly changes the settings and maintains the changes after being rebooted.
Connections remain in passthrough with Connection Intercept (CR66698)
In previous releases, some connections that should have been reset because of the Connection Intercept option, were set to passthough mode. When you set the Connection Intercept option now, the WANJet appliance resets any connections that were initiated before it became active on the network and optimizes appropriate connections.
Connection Intercept and one-arm configuration (CR70289)
In previous releases, you could not use the Connection Intercept option in some one-arm configurations. You can now use Connection Intercept with all configurations to reset connections that were initiated before starting the WANJet appliance.
UDP proxy disabled unless required by optimization policy (CR70549)
Previously, the UDP proxy was run automatically when the WANJet appliance started up. The UDP proxy is now run only if it is required by the optimization policy.
Error conditions cause peer WANJet appliances to block traffic (CR70550)
In previous releases, a complex set of error conditions occurring on WANJet appliances that were set up as peers could block traffic. Peer WANJet appliances no longer block traffic when this set of error conditions occurs.
Reset connections and WANJet appliance response (CR70551)
The WANJet appliance maintains a control connection between itself and its remote peer(s). Previously, it took no explicit action when this connection failed, and this led to a performance degradation in some situations. Now, as a result of a failed connection, the WANJet appliance logs a message to the diagnostic log, and disconnects, then reconnects the link to the remote WANJet appliance.
Error message about missing network interface was removed (CR71231)
In past releases, you might have seen a message that said, Can't locate module eth5-9, although the WANJet appliance did not have network interfaces on eth5 through eth9. The WANJet appliance no longer reports error messages concerning network interfaces that are not present on the appliance.
[ Top ]
Once you have installed the software, you can use any of the following new configuration options to update your configuration.
You can change optimization policies while the WANJet appliance is optimizing traffic without having to restart the appliance or interrupt your users.
To add or reconfigure optimization policies
Refer to Chapter 7 of the WANJet Appliance Administrator Guide for more information about optimization policies.
[ Top ]
You can configure the WANJet appliance as part of a trunked VLAN if this is required in your networking environment (although this is not a common setup). In this configuration, the WAN port on the WANJet appliance connects to a VLAN trunk, and you want the WANJet to optimize traffic that originates from one of the VLANs on the trunk. The VLAN trunk connects to a switch that supports VLAN trunking, such as the Cisco Catalyst. F5 Networks supports 802.1q.
To add a trunked VLAN ID
Refer to Chapter 7 of the WANJet Appliance Administrator Guide for more information about configuring VLANs.
You can now restore the factory default values on the WANJet appliance.
Warning: You should restore the factory defaults only in extreme cases when you want to discard all configuration changes that you have made, and start configuration all over again.
When you use this option, the values in all fields on all screens are reset to the default values and all configuration changes are lost. The WANJet appliance retains the licensing information, so you do not have to revalidate the license. You do have to reconfigure the rest of the settings and policies.
To restore factory default values
[ Top ]
The following items are known issues in the current release.
Passthrough sessions (CR60178)
After a high volume of traffic passes through the WANJet appliance, the dashboard may temporarily display more passthrough sessions than are actually occurring.
Real Time Traffic report (CR61437)
The amount of network traffic shown in the Real Time Traffic report appears to repeatedly spike to twice the actual amount, in 30-second intervals.
SSL encryption implementation (CR64020)
SSL encryption is currently implemented only for optimized TCP traffic. In future releases, we plan to support TCP and UDP protocols for SSL encryption.
GRE packets captured by tcpdump (CR64731)
When the tcpdump diagnostic tool captures Generic Routing Encapsulation (GRE) packets on the WANJet appliance, it does not decode the packets correctly.
TDR-2 efficiency impacted by slow servers (CR65171)
TDR-2 efficiency may be degraded when transmitting data from low-performance servers.
UDP port optimization may cause problems on port 53 (CR70172)
When all UDP ports are optimized, DNS services over port 53 may fail. The workaround is to put all UDP ports into passthrough mode and to specifically open those UDP ports you want to optimize.
[ Top ]
Implementing specific WANJet appliance configuration changes (CR71549)
When you perform the following changes on the WANJet appliance, the configuration changes do not take effect immediately:
Adding or removing a remote WANJet appliance
Changing the properties of a remote WANJet appliance
Adding or changing an Application QoS policy
The workaround is to perform the following steps to implement the changes.
The Operational Mode screen opens.
The WANJet appliance status changes to Inactive.
The WANJet appliance status changes to Active, and the remote appliance configuration changes take effect.
Daylight Saving Time implementation (CR71811)
Due to the Energy Policy Act of 2005, in 2007, Daylight Saving Time begins at 2:00 a.m. on the second Sunday in March and reverts to standard time on the first Sunday in November. Version 4.2.8 is not compliant with the Energy Policy Act. We expect to bring the WANJet appliance into compliance in a future release.
If you are using version 4.2.8 in March of 2007, you will need to make the Daylight Saving Time change manually, since the system will not change the time on the correct date. Then on the first Sunday in April, when the system does make its automatic change, the change will be redundant, and you need to correct the time again by reversing out the additional hour change. Refer to Configuring time settings in the WANJet Appliance Administrator Guide for details on adjusting time.
[ Top ]