Updated Date: 03/13/2008
In addition to these release notes, the following user documentation is available for this release.
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 Knowledge Base on the AskF5 Technical Support web site.
Because the WANJet appliance 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:
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 ]
The supported browsers for the WANJet appliance browser-based interface are:
This release supports the following platforms:
[ Top ]
The installation instructions vary, depending on whether you are installing the WANJet appliance version 5.0.2 onto a system that is running version 5.0.1, 5.0, or 4.2.x. You can upgrade or install version 5.0.2 under several different conditions as shown in the table that follows.
Note: You cannot upgrade from version 5.0. However, you can perform a PXE (clean) install of version 5.0.2.
|Current version||Current size of CompactFlash||Installation or Upgrade Methods|
Upgrade to version 5.0.2--Use one of two methods:
Note: Saved configuration information is maintained if needed.
|Order upgrade kit, back up version 4.2.x configuration data, install 8 GB CompactFlash (running version 5.0.1), update the BIOS, upgrade/install version 5.0.2, restore the version 4.2.x configuration (run the restore42xConfig command), complete configuration of the system.|
4.2.x, 5.0, 5.0.1
|Install version 5.0.2--Perform a PXE (clean) installation of v5.0.2. For versions 5.0 and 5.0.1, restore the configuration using the archive (UCS file). For version 4.2.x, restore the version 4.2.x configuration (run the restore42xConfig command), and complete configuration of the system.|
If you have Enterprise Manager, update to version 5.0.2 using the ISO file. Refer to the Enterprise Manager documentation.
If the WANJet appliances you want to update to version 5.0.2 are running version 5.0.1, they already have an 8 GB CompactFlash® and their BIOS has already been upgraded. You can proceed to install or update the software using any of the methods described here.
If you have existing WANJet 400 or 500 appliances running version 4.2.x and want to run version 5.0.2, unless the appliance already has an 8 GB CompactFlash®, you must order an upgrade kit through your F5 Sales Representative. The upgrade kit contains
You need to replace the 1 GB CompactFlash® with the 8 GB CompactFlash card on which version 5.0.1 is installed. Existing WANJet 500 appliances also require a BIOS upgrade to OBJ-0200-03 Rev A. Refer to the WANJet Appliance CompactFlash Card and BIOS Upgrade Instructions for information on how to upgrade the BIOS (WANJet 500 only) and replace the CompactFlash card (WANJet 400 and 500). After you update the CompactFlash and the BIOS, the system will be running version 5.0.1. You can proceed to install or update the software using any of the methods described here.
Important: For the WANJet appliance to function properly, any firewalls separating the WANJet appliances must have TCP ports 3702 and 3701 open on the firewall. For additional information, refer to the WANJet Appliance Administrator Guide.
If you plan to use disk-based storage for TDR-2, WANJet 500 appliances have an optional hard drive upgrade kit available. The kit allows you to upgrade existing 7200 RPM hard drives to 10K RPM hard drives. The upgraded disk drives provide the best possible TDR-2 disk caching performance when using storage on disk. You can order upgrade kits to replace the 7200 PRM drives on existing appliances. New WANJet 500 appliances come with one 10K RPM drive. Ask your F5 Networks representative if it would be to your advantage to use disk-based storage, as opposed to memory-based storage.
If your system is running WANJet software version 5.0.1, you can perform a local, remote, or a clean installation of version 5.0.2. If you are running WANJet software version 4.2.x on an appliance with an 8 GB CompactFlash, you must perform a clean installation of version 5.0.2.
For a local upgrade, you copy an IM package onto the system you intend to upgrade. For details about downloading the software and using this installation method, see Local Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.
For a remote upgrade, you run the upgrade from a management workstation that is not directly connected to the system you intend to upgrade. A remote upgrade requires that the Management IP address has been configured (rather than the Bridge IP address). For details about downloading the software and using this installation method, see Remote Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.
If you do not plan to roll forward a configuration, you can perform a clean installation on the system. For details about downloading the software and using this installation method, see PXE Installation: Performing a clean installation of WANJet appliance version 5.0.2.
After you download the installation file and its associated MD5 checksum file, and before you perform the installation, we recommend you test the integrity of the installation file. This verifies that you have downloaded a good copy of the file. To run the test, type the following commands, where local-install-5.0.2.xx.x.im is the name of the file you downloaded, and local-install-5.0.2.xx.x.im.md5 is the name of its associated MD5 checksum file.
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.
After you upgrade or install the software, the WANJet appliance is running version 5.0.2. You can log on and get started using it.
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.
Important: You must reboot the WANJet appliance at this time if you activated the license for the first time.
This release includes the following new features and fixes.
Transparent proxy with WCCP L2 Redirect and GRE tunneling support
You can use Web Cache Control Protocol (WCCP) in a deployment where the WANJet appliance is located out-of-path, that is, not inline. The benefit is that if the device fails, WCCP automatically bypasses the failed device. WCCP is implemented in the router using
The WANJet appliance now supports WCCP redirection from multiple routers.
Remote redundancy and load balancing
You can set up a WANJet appliance with a remote redundant pair on the other end of the WAN. The single WANJet appliance load balances connections between the two remote redundant WANJet appliances (using round robin scheduling). If one of the remote WANJet appliances fails, the local WANJet appliance sends all connections to the one that is still operational. The remote pair can be set up as peers through the peer port, but it is not required.
Tuning for asymmetric links
You can now configure asymmetric link bandwidth and round trip time values. You can specify distinct Send Bandwidth, Receive Bandwidth, and RTT for links between the local WANJet appliance and each remote WANJet appliance. If the remote WANJet appliance has a redundant peer, you can also specify the Peer Send Bandwidth, Peer Receive Bandwidth, and Peer RTT.
4.2.x Migration script (Restore42xConfig)
You can now migrate many of the version 4.2.x configuration settings to a WANJet appliance running version 5.0.2. After you copy the backed up version 4.2.x configuration setting onto the version 5.0.2 system, you run the Restore42xConfig script, which migrates most of the configuration settings onto the version 5.0.2 system. Refer to the WANJet® Appliance 4.2.x to 5.0.2 Migration Guide for details.
This release addresses Common Internet File System (CIFS) performance issues related to opening and saving files when using Microsoft Excel® and Microsoft Word, and issues related to Microsoft AccessTM when opening and saving database tables. These enhancements improve CIFS optimization performance.
End-User Diagnostics (EUD) version update
This release includes EUD version 10.0.8, which is the latest version.
TOS/DSCP bits preserved
The WANJet appliance preserves Type of Service (TOS) priorities or Differentiated Services Codepoint (DSCP) values for traffic moving through the tunnel.
This release includes the following fixes.
SNMPwalk function CR84638)
Many Management Information Base (MIB) browsers use the SNMPwalk function while reading values from an SNMP agent. In past releases, this function may have failed after reading the RMON2 MIB. The SNMPwalk function no longer fails in this situation.
WCCP L2 redirect support (CR87005, CR87008)
In this release, the WANJet appliance supports the WCCP v2 protocol. (Primarily used as transparent proxy for one-arm configuration.)
Transparent proxy with GRE tunneling: (CR87007, CR87009)
In this release, you can configure WANJet appliances in a one-arm configuration that sends passthrough traffic through a Generic Routing Encapsulation (GRE) tunnel.
Remote redundancy and load balancing support (CR87014)
This release supports remote redundancy and load balancing of WANJet appliances.
Passthrough traffic graph mislabeled (CR87720)
In previous releases, the Passthrough Traffic graph mislabeled the data rate as bytes. The data rate is now correctly labeled as bits.
New Zealand Daylight Saving Time changes (CR88345)
New Zealand has implemented new dates for Daylight Saving Time starting this year. When you set the time zone on the WANJet appliance to Pacific - Auckland, the time is reset according to the new dates.
Peer port status when WAN Links are disconnected (CR89265)
In release 5.0.1, the peer port remained active when the WAN Links were disconnected. In this release, the peer port is disabled if the WAN links are down.
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 either:
In releases 5.0 and 5.0.1, delayed acknowledgement settings were enabled by default. In this release, delayed acknowledgement settings for the LAN, WAN, and VNIC are now set in the TCP profile according to the bandwidth of the link. For low bandwidth links of 45 mbps or less, the TCP profile enables delayed acknowledgement; for high bandwidth links of 45 mbps or greater, the TCP profile disables delayed acknowledgement.
CIFS performance (CR92742)
In this release, the system has improved Common Internet File System (CIFS) performance when opening large documents.
WANJet 500 running in Inactive mode (CR93992)
In release 5.0.1, WANJet 500 appliances running in Inactive mode can bridge traffic only if it is from within the appliance's own subnet; WANJet 500s block traffic from other networks. As of this release, when WANJet 500 appliances are set to Inactive mode, the WANJet appliance allows traffic from any subnet to pass through.
The following release 4.2.x features are not in this release:
If you have installed and configured Enterprise Manager, the following configuration information is relevant to you.
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 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.
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.
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).
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.
Tip: When the popup screen opens, click the Help tab to view details on the screen.
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.
Tip: When the popup screen opens, click the Help tab to view details on the screen.
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.
Note: You need to deploy optimization policies separately from QoS policies.
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:
The Enterprise Manager lets you access three files for each area:
The topology changeset allows you to specify the topology of all the WANJet appliances on their network. When you deploy this file to the devices, all of the connections between the WANJet appliances are automatically created.
The file has two distinct sections, and an optional third section if you have a redundant peer. In the first section (the WANJet appliance section), you describe all of the WANJet appliances that form part of the topology. Minimally, you must assign an alias and a WANJet IP (Bridge IP) address to each WANJet appliance. For example:
<WANJet> <Alias>New York</Alias> <IP>10.142.1.100</IP> </WANJet>
Additionally, for each WANJet appliance, you can associate one or more subnets in the Subnets section. Each Subnet entry includes the following information:
<WANJets> <WANJet> <Alias>Paris</Alias> <IP>10.142.5.100</IP> <Subnets> <Subnet> <subnetIP>22.214.171.124</subnetIP> <subnetMask>255.255.255.0</subnetMask> <subnetAlias>Sarkozy</subnetAlias> <subnetStatus>1</subnetStatus> </Subnet> <Subnet> <subnetIP>126.96.36.199</subnetIP> <subnetMask>255.255.255.0</subnetMask> <subnetAlias>Royal</subnetAlias> <subnetStatus>1</subnetStatus> </Subnet> </Subnets> <WANJet> </WANJets>
The second section of the file, the WanLinks section, specifies the links between each of the WANJet appliances. For example:
<!-- Specify one side of the WANLink 'a' -->
<!-- Specify the other side of the link 'b' -->
<!-- Give the link bandwidth in the direction a -> b -->
<!-- Give the link bandwidth in the direction a -> b -->
<!-- Sprcify the RTT for the link -->
<!-- This section sets up a remote redundant peer -->
Use the following section to set up a redundant peer:
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>
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 ]
The following items are known issues in the current release.
Firefox rendering issue
In versions 188.8.131.52 and 184.108.40.206 of the Firefox® browser-based interface, empty text boxes in the WANJet browser interface may contain XX. This does not affect the WANJet appliance functionality.
Cannot specify MTU in topology file (CR75704)
If using Enterprise Manager to deploy WANJet appliances in a networking environment that includes a LAN router, it is necessary to create a static route for every remote WANJet. To create a route, you need to specify the Maximum Transmission Unit (MTU), which is the largest allowable packet size. When deploying by using a topology file, there is currently no way to specify the MTU value. The WANJet appliance uses the following default values: 1500 for direct and 1400 for VPN. The workaround is to deploy the WANJet appliances using Enterprise Manager, then configure the MTU values on the WANJet appliances, as needed.
Sending data to a syslog server (CR76877)
Although the WANJet appliance does not provide a way to send logs to a syslog server from the browser-based interface, you can manually edit the /etc/syslog-ng/syslog-ng.conf file and use the HUP syslog-ng command to allow logging to a remote server, and this is consistent with how TMOS-based products work. For example:
user.* @my_remote_server_IP # log all user messages to a remote server
kern.crit @my_remote_server_IP # log only the critical kernel messages to a remote server
*.* @my_remote_server_IP # log everything to remote server
Refer to SOL5527: Configuring BIG-IP to log to a remote syslog server and the syslog-ng and syslog-ng.conf man pages for additional information.
Limited error checking on SNMP Agent Configuration screen (CR77797)
When you are adding IP addresses into the Client Allow List, the addresses are not validated. Be careful to specify valid IP addresses or subnets in the Client Allow List.
Public access record on SNMP Access (v1, v2c) screen (CR77848)
By default, the system creates a public access record and displays it on the SNMP Access (v1, v2c) screen. Although the system allows you to delete that record, you can still perform SNMP queries as if it were not deleted. We do not recommend deleting the public access record.
LCD shutdown does not power down (CR78158)
Attempting to shut down the WANJet appliance from the LCD causes the operating system to halt, and does not physically power down the hardware. The workaround is to press the On/Off switch after the system halts.
Remote WANJet appliance with redundant peer (CR78462)
When a local WANJet appliance pings a remote WANJet appliance that has a redundant peer, the local WANJet appliance can contact only the first remote WANJet appliance, not the second one.
Internet Explorer 7 not supported (CR78511, CR83783)
If you log on to the WANJet appliance browser-based interface using Internet Explorer® 7, you see alignment problems and possible error messages, and the online Help is not displayed. We recommend using Internet Explorer 6 or Firefox®, which are fully supported.
Dashboard statistics not updating (CR78655)
In certain cases, the dashboard in the browser-based interface may not show the latest statistics. To be sure that the dashboard statistics are up to date, click the Refresh button in the browser.
Expired or missing license (CR79535)
The WANJet appliance gives no warning in the browser-based interface if the license is expired or missing. You should periodically check the License screen (System >> License) to be sure it is valid.
Removing disk drive stops traffic (CR79928)
Removing a disk drive while the WANJet 500 is actively passing traffic using Disk Based Storage for the TDR-2 Storage Mode stops traffic. If you need to replace the disk drive, set the WANJet appliance Operational Mode to Inactive before removing the disk drive. Set it back to Active after replacing the drive.
System Statistics Memory information (CR80371)
The information displayed in the System Memory Used column on the System Statistics screen may not be accurate on WANJet 500s. It shows 15.9S.
SOD service description (CR80973)
On the High Availability screen (System >> High Availability), the SOD service description reads Failover, but should say High availability management.
Default optimization policy shows different values on popup screen (CR81060)
When you first start a WANJet appliance, the default optimization policy for all ports is that all traffic is set to passthrough and TDR-1 and TDR-2 optimization is not enabled. However, when you click the Service Name of the default optimization policy, the Edit Port/Service Name popup screen shows TDR-1 and TDR-2 as selected but grayed out. They are not enabled and should not appear selected, and can be ignored.
WANJet 300 appliance does not shut down using ACPI (CR81349)
You need to press the power switch on the WANJet 300 to turn off the power after the shutdown sequence completes.
Changing WANJet appliance IP address does not change local subnets (CR81563)
When you specify the WANJet appliance IP address, and click Include WANJet Subnet on the Local Subnets screen, the WANJet appliance automatically adds the local subnet to the list. If you change the appliance's IP address, the local subnet does not change. The workaround for this is to select the local subnet if it is no longer valid and remove it.
Re-enabling a disabled interface (CR82218)
On the Interface screen (Network >> Interfaces), you must click Enable twice to re-enable an interface that has been disabled.
Disabling the WAN interface on a WANJet 400 (CR82291)
Disabling the WAN Interface on a WANJet 400 brings down the LAN interface and restarts the tmm process. We do not recommend disabling the WAN interface on a WANJet 400.
Optimized Packets on WANJet Links Monitoring screen (CR82457)
The WANJet Links Diagnostics report shows a value for Optimized Packets. For increased clarity, this field should be labeled Optimized Packets Received, because the value does not include optimized packets that were sent from the WANJet appliance.
Application QoS: Adding subnets to WAN links (CR82905)
When you are adding subnets on the Manage the Application QoS Settings of a WAN Link popup screen, the added subnet does not initially show on the screen. However, the subnet has been added, as you can see if you edit the WAN link from the main Application QoS screen.
Inconsistent data on Passthrough Sessions screen (CR83331, CR83717)
The number of passthrough sessions reported on the Passthrough Sessions screen (WAN Optimization >> Diagnostics >> Monitoring >> Passthrough Sessions) may not accurately reflect current system activity.
Fedora Core 3 and optimization performance (CR83500)
Using the Fedora Core 3 client or server produces some illegal IP packets that degrade optimization performance significantly, especially with TDR-2 enabled.
Topology changeset validation in Enterprise Manager (CR84195)
When you deploy a topology changeset from Enterprise Manager, it is important to be accurate about IP addresses, subnets, and netmasks. Information within changesets is not fully validated in this release. If you deploy a changeset with invalid values, you will not receive an error message.
System reboot displays message (CR84296)
If you reboot the WANJet appliance with the browser-based interface still displayed, you may see the message Configuration Utility Restarting, and the browser-based interface is unavailable. When the system is restarted, you can either refresh the browser-based interface or open a new browser window to display the login prompt.
RMON1 values not available (CR84513)
Only RMON2 values are available if you use a MIB browser to view data in the WANJet appliance MIBs.
Diagnostic reports may not show correct data (CR84544, CR84856)
The information displayed in the Optimized Sessions report may not show accurate data, or the report may be blank. The workaround is to refresh the screen.
WANJet 500 LCD netboot command not working (CR84640)
Issuing the netboot command from the LCD on a WANJet 500 reboots the WANJet appliance locally without attempting to load an image from the network.
Set Operational Mode to Active (CR84777)
When you start up a WANJet appliance and configure remote WANJet appliances, you may need to set the Operational Mode to Inactive, click Save, then set Operational Mode to Active, and click Save again to bring all WAN links up and establish links between all appliances.
Invalid network interface option (CR85562)
On the Network Interface screen, when you click lan, wan, or peer, you display the General Properties screen for the interface. The Requested Media option allows you to select 1000base TX half although this setting is not available for any of the interfaces on the WANJet appliance.
Unable to change Management IP address (CR85614)
If you have routes configured for the management interface in addition to the default management route (System >> Configuration >> Management Routes), you need to delete the additional routes first if you want to change the Management IP address. Currently, attempts to change the Management IP address will fail when you have additional management routes configured, and you receive no warning message.
Cannot change WAN interface speed and duplex settings from the LCD (CR 85673)
On the LCD, the settings to change the WAN interface speed and duplex do not work. The workaround is to change the setting on the Network Interface screen instead.
Create or change Application QoS policies (CR87979, CR88978)
When you create or change Application QoS policies, they may not work as expected until you restart the Traffic Management Microkernel (TMM) process. The workaround for this is to restart TMM after creating or changing an Application QoS policy. At the command line, type bigstart restart tmm.
Saved configuration not fully reinstated on upgrade (CR88077)
When upgrading to version 5.0.1, the saved configuration is not reinstated fully on the WANJet appliance. After upgrading, you need to follow these steps to complete the process:
Upgrade or installation from Enterprise Manager requires Management IP address (CR88080)
If you want to use Enterprise Manager to install or upgrade WANJet appliances, you must have configured the Management IP address, rather than the Bridge IP address, for communication. The Enterprise Manager can discover the WANJet unit, but when you try to install the image, the WANJet appliance does not appear to be compatible with the install image.
Remote installation requires Management IP address (CR88082)
If you want to perform a remote installation (as described in Remote Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2), you must configure a Management IP address, rather than the Bridge IP address, for communication. A remote installation using the Bridge IP address causes an installation error. If you are using the Bridge IP address to log on to the WANJet appliance, you must use the local installation to upgrade the device. Refer to Local Installation: Upgrading from WANJet appliance version 5.0.1 to version 5.0.2.
Connection Intercept requires 5 sec idle connection (CR90627)
Connection Intercept requires the connection to be idle for 5 seconds in order to interrupt and reset it.
Web-based diagnostics shen 32 spokes connect to one hub (CR91193)
When you deploy one WANJet appliance as the hub for 32 spokes and each of the spokes is handling many connections, the hub WANJet appliance is slow to display optimization diagnostics.
WCCP one-arm configuration (CR91371)
When you change and save any of the WCCP settings in a one-arm configuration, the WANJet appliance terminates the tunnel, stops, and then restarts the TMM process, which closes all existing connections and restarts them. We recommend that you make changes to the WCCP configuration when it would be the least disruptive to your users.
WCCP with GRE tunneling in an HSRP environment (CR92395)
If you configure WCCP with generic routing encapsulation (GRE) tunneling as the redirection method in an HSRP (Hot Standby Router Protocol) environment, the WANJet appliance may not be able to optimize traffic connections. A possible workaround for this is to configure all routers in an HSRP cluster so they have the same router identifier. However, this configuration has not been fully tested.
Memory-based storage for TDR-2 with hub and multiple spokes (CR93366)
If you configure memory-based storage on a hub with multiple spokes, TDR-2 optimization performance is limited. F5 recommends using disk-based storage on the hub when configuring more than five spokes. Note that the bandwidth of the hub and spoke links also impacts optimization performance.
Topology changeset link tuning values (CR93772)
When you configure linked tuning through the web-based interface, the Send Bandwidth and Receive Bandwidth settings cannot exceed 62000 kbps (622 mbps), and the RTT (Round Trip Time) setting cannot exceed 2000 msec. When you are configuring linked tuning through the topology changeset, Enterprise Manager allows the deployment of any value, including invalid ones, for these fields without providing an error message. Enterprise Manager needs to do additional error checking for the topology changeset.
Sys-reset command unreliable (CR95158)
Running the sys-reset command to restore factory defaults may render the Configuration utility on the WANJet appliance to be unusable. We recommend that you not use the sys-reset command, and instead perform a clean installation of the software if you need to restore factory defaults.
Redundant WANJet appliance still appears after being removed (CR95230)
If you try to remove a redundant remote WANJet appliance from the Remote WANJet appliance screen by clicking the IP address of the remote appliance and changing the WANJet Type from Redundant to Single, the redundant appliance still appears on the screen. To remove a redundant remote WANJet appliance, click the IP address of the remote appliance, clear the Redundant Peer IP address first, then change the WANJet Type from Redundant to Single. The redundant peer no longer appears on the screen.
[ Top ]
For additional information, please visit http://www.f5.com.