Release Notes for Cisco WAFS 3.0.11

Note The most current Cisco documentation for released products is available at Cisco.com at http://www.cisco.com. The online documents may contain updates and modifications made after the hardcopy documents were printed.

This release note contains information about the Cisco Wide Area File Services (WAFS) Release 3.0.11. This release note describe the following topics:

Introduction

The Cisco WAFS solution facilitates the consolidation of all branch-office data into central file servers that reside at the data center. WAFS overcomes WAN latency and bandwidth limitation with the Cisco Systems proprietary optimization technologies, offering users at branch offices a LAN-like experience when accessing centralized files over the WAN.

The WAFS solution includes ready-to-use appliances with the following components:

•

The Cisco Edge File Engine (Edge FE) is deployed at each branch office or remote campus, replacing file and print services and giving local clients fast, near-LAN read and write access to a cached view of the centralized storage.

•

The Cisco Core File Engine (Core FE) resides at the data center and connects directly to one or more file servers or network attached storage (NAS) gateways, performing WAN-optimized file requests on behalf of the remote Edge FEs.

•

The Cisco WAFS Central Manager provides remote management and monitoring of all the Wide Area Application Engines (WAEs).

The WAFS solution includes the Cisco WAFS software running on the Cisco FE-511, WAE-511, WAE-611, or WAE-7326. Each WAE can be configured to be an Edge FE, a Core FE, or a WAFS Central Manager. These components can also run concurrently on the same appliance if resources and capacity are sized appropriately. For more information on the WAFS solution, see the Cisco WAFS 3.0 Users Guide.

System Requirements

This section lists the supported hardware components (FEs and WAEs, routers, and switches) for the WAFS releases and contains the following topics:

Supported FE or WAE Components

New hardware supplied by Cisco is called WAE (Wide Area Application Engine). The old models are called FE (File Engine). Table 1 lists the FE and WAE components that WAFS supports, and the minimum software release required.

Table 1 Supported Hardware and Minimum Software Requirements
Component	Part Number	Description	Minimum Software Release Supported
Cisco File Engine	FE-511-K9	FE-511 with chassis and motherboard with 512-MB DRAM—AC power supply, hardware accessory kit, two 250-GB hard drives	ActaStor Release 2.5.1
Cisco Wide Area Application Engine 511	WAE-511-K9	WAE-511 with chassis and motherboard with 512-MB or 1-GB DRAM —AC power supply, hardware accessory kit, two 80 or 250-GB hard drives	WAFS Release 3.0
Cisco Wide Area Application Engine 611	WAE-611-K9	WAE-611 with chassis and motherboard with 2-GB DRAM—AC power supply, hardware accessory kit, two fixed 146-GB SCSI hard disk drives	WAFS Release 3.0
Cisco Wide Area Application Engine 7326	WAE-7326-K9	WAE-7326 with chassis and motherboard with 4-GB DDR-II RAM—dual processors, redundant AC power supplies, hardware accessory kit, up to two 73-GB or 146-GB SCSI hard disk drives	WAFS Release 3.0
Cisco Network Module	NM-CE-BP-80G-K9	Content engine (CE) network module with an 80-GB Disk Expansion Module.	WAFS Release 3.0.5
Cisco Wide Area Application Engine 512	WAE-512	Wide Area Application Engine with 3.0-GHz Pentium 4 processor, 1-MB Layer 2 cache and 800-MHz front side bus (FSB)	WAFS Release 3.0.7
Cisco Wide Area Application Engine 612	WAE-612	Wide Area Application Engine with 3.0-GHz Pentium D (dual-core) processor, 1-MB Layer 2 cache per core and 800-MHz FSB	WAFS Release 3.0.7

Supported Routers and Switches

New and Changed Information

Table 2 lists the new and changed WAFS software features that are described in this section.

Table 2 New and Changed Features Supported by WAFS Release 3.0
Features	Introduced in
Daylight Savings Time Compliance for 2007	WAFS Release 3.0.9
Print Jobs Removed from Spool Area	WAFS Release 3.0.7
Restarting the Print Server After Adding Printers	WAFS Release 3.0.7
NM-CE-BP-80G-K9 Network Module Support	WAFS Release 3.0.5
LDAP Server Signing	WAFS Release 3.0.5
Automatic Resolution of File Server IP Changes	WAFS Release 3.0.3
CIFS over TCP	WAFS Release 3.0.3
Dynamic Shares Support	WAFS Release 3.0.3
Enhanced Sys Report	WAFS Release 3.0.3
File Server Support	WAFS Release 3.0.3
Kerberos Support for Authentication	WAFS Release 3.0.3
Unicode Support	WAFS Release 3.0.3
Windows Shadow Copy for Shared Folders	WAFS Release 3.0.3
WAFS CLI	WAFS Release 3.0
RAID	WAFS Release 3.0
WAFS Central Manager Enhancements	WAFS Release 3.0
Print Service Enhancements	WAFS Release 3.0
tcpdump Viewer	WAFS Release 3.0
WCCPv2	WAFS Release 3.0
License Key File	WAFS Release 2.5
SNMP MIB	WAFS Release 2.5

Daylight Savings Time Compliance for 2007

WAFS 3.0.9 adds daylight savings time compliance for the year 2007. Beginning in the year 2007, daylight savings time will start on March 11th (instead of early April) and will end on November 4th (instead of late October). The WAFS 3.0.9 release contains a new rule that adjusts the time on the device for the daylight savings time changes in the year 2007.

Print Jobs Removed from Spool Area

In previous releases, a cron job periodically cleaned the spool area, which caused some jobs to be removed from the printer spool before printing. In WAFS 3.0.7, the cron job has been removed. The spool area retains the last 500 completed jobs and has a 1-GB size limitation. Once the completed job limit is reached, the oldest job is removed to make room for the latest completed job. When a job is removed from the spool area, it is no longer listed in the Completed Job Listing window.

Restarting the Print Server After Adding Printers

In previous releases, when a printer was added to the print queue, you had to restart the print server before the change would be recognized. In WAFS 3.0.7, you no longer need to restart the print server. After adding a printer in the Print Services Administration GUI, the new print queue appears on the Windows client system within one minute.

NM-CE-BP-80G-K9 Network Module Support

Edge FEs can now run on the network module NM-CE-BP-80G-K9. The WAFS Central Manager and all Core FEs must run on a dedicated Cisco appliance, such as the WAE-611. The WAFS network module supports a maximum of 30 users at a branch office. For more information about Network Module guidelines, see the Cisco WAFS 3.0 User Guide.

LDAP Server Signing

You can configure a security setting on Windows 2003 domain controllers to require clients (such as file engines) to sign LDAP requests. Because unsigned network traffic can be intercepted and manipulated by outside parties, some organizations require LDAP server signing to prevent man-in-the-middle attacks on their LDAP servers. For more information about LDAP signing and setting up LDAP signing, see the Cisco WAFS 3.0 User Guide.

Automatic Resolution of File Server IP Changes

The Core FE uses DNS (or WINS, or broadcasts as a backup) to resolve the file server names to IP addresses. After this initial name-to-IP address resolution, the Core FE continues to resolve the file server names in its list into IP addressees on a regular basis. If the IP list changes, the Core FE automatically updates all Edge FEs with the new list. Each Edge FE then updates the change in its WCCP accept list.

This process ensures that the Edge FEs continue to serve clients from the cache when the IP address of a file server changes. Without this automatic update, clients could connect directly to a file server when it changes its address and bypass the Edge FEs that contain the cached data.

CIFS over TCP

WAFS network always tries to use the same port to communicate end-to-end, so if a client uses CIFS port 445 to connect to an Edge FE, the associated Core FE tries to use the same port to connect to the file server. If port 445 is unavailable, the Core FE then tries port 139.

Dynamic Shares Support

Many file servers use dynamic shares, which allow multiple users to access the same share and allow each share to be mapped automatically to a different directory based on the user's credentials. Dynamic shares are most commonly used on file servers to set up user home directories.

Enhanced Sys Report

The Support tab enables you to download a system report that provides a snapshot of the current state of the File Engine and its operation, including the configuration log files of various components. You can send this report to Cisco Technical Support (TAC) when you need assistance.

File Server Support

Table 3 lists the file servers that interoperate with the WAFS software running on the Core FE.

Table 3 Supported File Servers
Vendor	Product	Version	Protocol
Dell	PowerVault	715N	CIFS
Network Appliance	FAS250 F760	7.01.R1 6.5.2R1P16	CIFS/NFS
EMC	NS 501 NS 702	5.3.12-3 5.4.14-3	CIFS/NFS
Microsoft	Windows NT 4.0 Windows Server 2000 Windows Server 2003	SP3 and SP4 No service pack, and SP1	CIFS
Sun	Solaris	2.7 and 2.8	NFS
Novell¹	6.5	SP-3	CIFS
Samba	Samba	3.0.14a	CIFS
RedHat	Linux		NFS
Spinnaker	3300 build 410797 2	.5.5p2	CIFS/NFS

¹WAFS supports Novell 6.5 for CIFS optimization and server consolidation. WAFS does not break or optimize access to eDirectory, NDS, iPrint, or NCP usage

Kerberos Support for Authentication

The WAFS Central Manager GUI uses PAM (Pluggable Authentication Modules) for user login authentication. Administrative users defined in the WAFS Central Manager are distributed to the File Engine Managers and are granted CLI access upon selection.

The Current Status field shows whether the Windows authentication for WAFS Management login option is enabled or disabled. To use Kerberos authentication, check the Kerberos enabled check box, and then specify the following information:

•

The fully qualified name of the Kerberos realm. All Windows 2000 domains are also Kerberos realms, but the realm name is always the domain name in all uppercase letters.

•

The fully qualified name or IP address of the Key Distribution Center. You can also specify a port using the following format: ip address or name:port number. An example would be, 10.10.10.2:88.

(For more information about Kerberos support for authentication, see the Cisco WAFS 3.0 User Guide.)

Unicode Support

The WAFS software supports Unicode in the WAFS Central Manager and the File Engine Manager, with the following limitations:

When you use Unicode characters in policies, we recommend that all of your file engines be running WAFS release 3.0.3 because file engines running a previous release will not be able to interpret the Unicode policies that you define.

Note If you have a Central Manager that uses WAFS 3.0.11 software and a Core FE that uses 3.0.1 software and you define a coherency or pre-position policy, you cannot use the browse button to select a root directory that contains Unicode characters. If you use the browse functionality, Unicode directories will display "???" in place of Unicode characters. The workaround is to manually enter the root directory with the Unicode characters instead of browsing to the directory. However, even if you manually enter an Unicode directory, the Core FE that uses 3.0.1 software will not be able to provide the Edge FEs with the correct content because 3.0.1 software does not support Unicode. If you have a Central Manager and Core FE running 3.0.11 software, but your Edge FE is running 3.0.1 software, the Edge FE will be unable to cache directories and files that contain Unicode characters.

Windows Shadow Copy for Shared Folders

WAFS supports the Shadow Copy for Shared Folders feature that is part of the Windows Server 2003 operating system. This feature uses the Microsoft Volume Shadow Copy Service to create snapshots of file systems so that users can easily view previous versions of folders and files.

WAFS CLI

The WAFS CLI allows you to configure, manage, and monitor selected features that are not available through the WAFS Central Manager GUI. You can also perform advanced configuration of WAEs through a console connection or a terminal emulation program.

RAID

Cisco WAFS can use two disk drives, either for increased storage capacity or increased reliability. RAID is automatically applied to any WAFS appliance with two or more disk drives. Cisco WAFS uses two types of RAID:

•

RAID-0: Provides data striping (treats multiple disks as a single larger disk drive).

Note

RAID-1 is automatically enabled on WAFS appliances with two or more disk drives. We recommend that you do not change to RAID-0 unless your cache performance is inadequate; there can be reliability implications with RAID-0.

WAFS Central Manager Enhancements

The following list describes the WAFS Central Manager enhancements beginning with the WAFS 3.0 release:

•

The Cisco WAFS software upgrade process includes four steps—image acquisition, image distribution, installation, and switchover. Only the last three steps are controlled from the Central Manager. New software images will be downloaded by the administrator over HTTP or FTP and placed in a location that is accessible by the Central Manager.

•

The WAFS Central Manager fully integrates with external authentication systems (RADIUS, TACACS+, Windows Active Directory) for user access to the management interfaces.

•

Intuitive, yet simplified, print services are available only on a configured Edge FE.

•

File Engine configuration includes appliance integration with Windows authentication mechanisms.

•

When you add Windows file servers, the Core FE resolves the server name and displays its IP address.

Print Service Enhancements

All Edge FEs can be configured to provide a full range of print services to the clients they serve. Printer configuration is performed through the third-party CUPS application. Cisco WAFS supports Point and Print, which provides easy connection to remote printers without the need for installation disks. WAFS Print Services includes these features:

•

Generic printer support through the File Engine that acts as a print server for networked printers in the branch.

•

Printer security supports standard printer ACL that is fully integrated with Active Directory or NT Domain authentication.

tcpdump Viewer

The tcpdump utility allows you to intercept and capture packets that pass through a network interface, making this utility useful for troubleshooting network applications.

WCCPv2

Web Cache Communication Protocol version 2 (WCCPv2), developed by Cisco Systems, specifies interactions between one or more routers (or Layer 3 switches) and one or more application appliances, web caches, and caches of other application protocols. The purpose of the interaction is to establish and maintain the transparent redirection of selected types of traffic flowing through a group of routers. The selected traffic is then redirected to a group of appliances.

High-end routers (Catalyst 6000 and Catalyst 6500) also support Layer 2 redirection.

License Key File

A license key file is on the CD-ROM in the accessory kit that shipped with your system.

SNMP MIB

Cisco WAFS supports the full functionality of SNMPv3 MIBs, including the setting of traps.

Installation Notes

This section provides the following important information about installing the software and configuring the print services:

Determining the Software Version

To determine which WAFS software version is currently running on your FE or WAE, open the File Engine Management GUI and select File Engine > Utilities > Support tab. From WAFS Release 3.0.3 and later, the current running version can also be determined by selecting File Engines from the Central Management GUI. Alternatively, log into the File Engine CLI, and enter the show version command. The shortcut CLI command sh v also displays the version.

Upgrading WAFS Software

Depending on which software version the device is currently using, use one of the following upgrade procedures to upgrade to WAFS release 3.0.11:

Upgrading from ActaStor Release 2.5.2 to WAFS Release 3.0.11

Your FE or WAE has a CD-ROM drive that you can use to upgrade the software. To upgrade from ActaStor release 2.5.2 to WAFS release 3.0.11, you must first obtain the WAFS 3.0.11 rescue CD-ROM image from CCO. Download the image, burn it to a CD (using software such as Nero Burning ROM), and then follow these steps:

Step 1

Connect a serial console to the FE to be upgraded, and use this console connection for subsequent steps.

Step 2

Insert the WAFS 3.0.11 Rescue CD into the CD-ROM drive, and reboot the FE.

This option prepares a cookie for the FE and also retrieves the network configuration that was being used by the ActaStor code. This network configuration is stored in Flash memory and is used to configure the network when the WAFS code boots up after installation.

Step 6

Select Install Flash image from cdrom to install the flash image from the CD-ROM.

Step 7

Select Wipe out disks and install .bin image to wipe the disks and install the binary image.

This option prepares the disks by erasing the ActaStor code and associated data from the disks. The WAFS release 3.0 image is then installed.

Step 8

Manually remove the CD-ROM from the drive before rebooting the FE, and then select option 8 to reboot the FE.

Note The device will now have the WAFS release 3.0.11 image with basic network configurations (if the configurations were present when the device was running ActaStor release 2.5.2).

Upgrading from WAFS Release 3.0 to WAFS Release 3.0.11

Step 1

Acquire the 3.0.11 image from an external HTTP/FTP server to a predefined location on the local1 partition of the WAFS Central Manager by entering the copy {http|ftp|cifs} central command from the exec CLI mode of the Central Manager. Make sure that you specify the MD5 signature of the image in the copy {http|ftp|cifs} central <server-ip/hostname> <remote-directory> <image-file-name> <repository-slot-number> md5 <md5signature> command. For upgrade from WAFS Release 3.0.1, if the MD5 signature is not specified during the acquisition stage, you will not be able to Distribute/Install/Activate the image from the Central Manager.

Note

The MD5 signature is available from the external HTTP/FTP server when you download the image.

Step 2

Step 3

Select the image, and click Distribute to distribute the image to all registered File Engines of the Central Manager.

Step 4

Check the status of the image in the detailed status page, or use the Status button.

Step 5

When the image has been distributed completely to all the FEs, click Install. This action installs the image to the Flash on all the registered FEs but not on the device that acts as the Central Manager.

Step 6

Check the status of the image again. When the Flash installation is complete, the image is listed in the Pending version. When all devices, except the Central Manager, show the current image as the pending image, click Activate to switch over to the new image. Activating the image reloads all devices.

Step 7

After all of the registered devices are operating with the new image, select the image, and click Install to install the image in the Central Manager.

Step 8

Once installation is complete, click Activate to activate the new image in the Central Manager.

Note When an image is distributed, installed, or activated, the distribution status window shows the status as complete while initiating the process in the background. Be sure to check the actual status of the image by clicking the Status button or viewing the Detailed Status Page before proceeding with the next step.

WAFS Software Rollback

Note Downgrading from WAFS release 3.0.11 to release 3.0 or release 3.0.3 requires an explicit and manual cache deletion (using WAFS Manager GUI services).

Software rollback is possible from WAFS release 3.0.11 to a designated and previously installed WAFS release 3.0. General version rollback (ActaStor release 2.5.2) is not supported in WAFS 3.0. You can perform a software downgrade in two ways: by using the command-line interface (CLI) or by using the graphical user interface (GUI).

Performing a Software Rollback Using the CLI

To perform a software downgrade (rollback) by using the CLI, follow these steps:

Step 1

Enter the restore rollback command. This command installs the previously saved version to Flash.

Step 2

Enter the reload command. This command activates the installed version.

Performing a Software Rollback Using the GUI

To perform a software downgrade (rollback) by using the GUI, follow these steps:

Step 4

Select the active version to be downgraded to the previously saved version.

This action sends the rollback command to all File Engines that are registered with this Central Manager and that are currently running the selected version. File engines are also reloaded when the rollback is performed. File Engines that do not have a previously installed version of the software are not affected.

Distributing Licenses

A license key file is on the CD-ROM in the accessory kit that shipped with your system. To distribute licenses, follow these steps:

Step 1

Click the License button in the Central Manager File Engine (FE) window. The License Installation dialog box appears.

Step 2

Click the Browse button to browse the directory tree, and select the license key file (for example, *.lic) from the CD-ROM. You can view the license properties such as expiration date and licensed components in this window when a license file is loaded.

Step 3

Distribute the license by checking the FE or WAE names and clicking the Install License button. A Distribution Status window appears with the status of this operation.

Note If the licensing distribution process fails, verify that all pop-up blockers are disabled. Refer to the Cisco WAFS 3.0 Users Guide for troubleshooting information. You can also contact the WAE support team using the following e-mail alias: tac@cisco.com.

Operational Notes for For Print Services

This section contains the following operational notes and guidelines for print services:

Print Services Set Up and Operation

This section provides recommendations for setting up and operating print services using WAFS 3.0.11.

The default setting for the winbind cache validity time is 10 seconds. We recommend that you change the default setting to 15 minutes (900 seconds).

Each time an admin user accesses the printer properties, the printer object is marked as updated and all clients are forced to update their copy of the printer object during their next session. If admin users are accessing printers frequently, you might experience printing delays caused by the increased traffic.

•

We recommend that you use Kerberos for authentication because it is faster than NTLM.

–

When using Kerberos, you must increase the default winbind cache validity time to 15 minutes (900 seconds) for efficient operation.

–

When using Kerberos, you must have the WAE host name or the print server NETBIOS name registered properly in DNS. Clients should be using the print server FQDN to map printers to print servers.

Before you install a print driver on a client, you need to initialize the driver so your branch office clients can successfully install the driver and be able to print from applications such as Microsoft Word and PowerPoint. Uninitialized drivers often do not install successfully and can cause errors when clients use them to print from Microsoft Word and PowerPoint.

You must manually initialize a driver because the WAFS print server cannot execute Windows driver code locally to automatically initialize the driver. (See the "Initializing Print Drivers" section.)

•

We recommend that you use postscript (PS) drivers and not Printer Command Language (PCL) drivers because PS drivers load faster and have simpler objects associated with them.

•

We recommend that you use a Windows Domain Controller that is on the same LAN as the clients rather than configuring a remote Domain Controller.

General Known Issues

•

In some cases the Windows Print Queue status may not refresh correctly on a Windows client. If this happens, press F5 to manually refresh.

•

Print problems can be caused by corrupted TDB files. To verify these files, use the windows-domain diagnostics CLI command.

Avoiding Print Problems

To avoid printing problems when using WAFS print services, follow these guidelines:

•

When using a cluster, always use the cluster configuration window and do not configure the cluster members individually. This action may lead to inconsistent behavior, even when it is a cluster of one.

•

Printer clusters should contain printers with similar capabilities. Failure to configure correctly may cause printing error. Deletion of a printer will also remove that printer from its associated clusters.

•

Print test page and banner pages are only supported by PostScript printer. Nonpostscript printers will print unreadable output.

•

If Point and Print does not work, make sure the drivers have been properly installed for the WAFS print servers.

•

Jobs are reprinted from the beginning. If WAFS print services are restarted due to configuration changes, in-process jobs will be reprinted.

–

Make sure the printer is not stopped or rejecting jobs in the WAFS print services configuration.

•

Minimize changes to the NetBIOS name of the WAFS print server. If you need to change NetBIOS name, make sure to the use either the WAFS Gateway Manager GUI or the windows-domain CLI command.

•

If a PostScript job is sent to a nonpostscript printer, you will see a "%!PS-Adobe-3.0..." message. To fix this, configure the printer as nonpostscript, or send the print job to a PostScript printer.

•

If you cannot check the check box for advanced features on a printer on the edge, it may be that "Enable advanced printing features" is allowing the client printer driver to communicate with the print server using Enhanced Metafile Spooling (EMF).

WAFS print services supports only RAW spooling and not EMF because no rendering is done on the WAFS print server. The client renders the print job, and then submits it in a RAW format, as if the printer is going to receive that job.

Note No printer functionality is lost because of RAW spooling. The only functionality lost is the print rendering by the WAFS print server. In RAW spooling, the client is doing the rendering instead of having it done by the print server itself.

Limitations and Restrictions

Rollback Version Incorrectly Displayed

After you upgrade from WAFS 3.0.7-b31 (Special5) to WAFS 3.0.9-b3, the Rollback Version that is displayed in the Central Manager (Software Versions > Detailed Status) does not include the "special" string. The Central Manager displays the version as WAFS 3.0.7-b31; however, the version should be displayed as WAFS 3.0.7-b31 (Special5).

The version that is incorrectly displayed in this case does not have any impact on the rollback functionality. The show version last command displays the rollback version properly, and you can use the CLI as an alternate method to view the rollback version of a specific device.

DFS Support

WAFS 3.x disables DFS support by setting the DFS capability flag to false in the negotiated response and by returning an error on TRANS2_DFS_GET_REFERRAL requests. Therefore, any attempt to use DFS when the DFS root is optimized by WAFS is aborted.

The only DFS capability that is supported in WAFS is the ability to define the WAFS alias for each edge appliance as a DFS leaf when working in non-transparent mode, or to define the leaf as optimized by WAFS, if working in transparent mode.

In transparent mode, we recommend that you define all copies of a DFS leaf as optimized by WAFS. The DFS root sets leaf order based on proximity, and if one of a leaf's copies is not optimized by WAFS, it is possible that the non-optimized leaf will be returned first in the list, causing the rest of the traffic to be sent as not optimized by WAFS.

Important Note About EMCopy for Celerra

For correct handling of file timestamps, use EMCopy with Celerra instead of Robocopy. While Windows uses timestamps down to nanoseconds, Celerra truncates the timestamp to the seconds that Robocopy cannot handle. The EMCopy.exe tool is available in the EMC NAS application CD.

Open Caveats in WAFS Release 3.0.11

This section describes the Severity 1, 2, and 3 caveats that were opened in the WAFS 3.0.11 release.

Condition: This problem occurs when the GMT offset for one of the time zones (for either the edge or the core File Engine) is not a whole number. For example, if the edge File Engine has a GMT offset of +5.5 hours, the task will start half an hour early. If the core File Engine has a GMT offset of +5.5, then the task will start half an hour late.

Condition: This problem occurs when you set back the clock while a preposition task is in progress. When the recorded start time of the preposition task occurs before the current time, the task duration becomes negative, which is not supported.

Workaround: If the time difference between the recorded start time and the current time exceeds the duration of the preposition task and the problem prevents display of the status page, you can perform one of the following actions:

–

Stop and start the edge process. The status information does not persist and is removed upon restart.

–

Run the preposition task again. If this is done immediately after the problematic run completes, the rerun will be short because not many files are likely to change.

Resolved Caveats in WAFS Release 3.0.11

This section describes the Severity 1, 2, and 3 caveats that have been resolved in the WAFS 3.0.11 release. Caveats in this section are listed alphabetically and numerically by identification number.

When a new WAFS version is installed on a system that was set to "guest printing" by using the local print script, the guest-printing functionality is lost after the upgrade, and the system is not able to print.

The e-mail notifier in WAFS currently defaults to "MAIL FROM: <noreply>" when it is communicating with e-mail servers. Some e-mail servers do not accept a communication unless this field contains a valid e-mail address.

The preposition start time always shows as AM in the preposition status display on the Central Manager. Because most of the preposition run times are scheduled for PM hours, the preposition status that is displayed is off by 12 hours.

If the core File Engine does not return data in the response to the files fetch request (readfiles), the edge File Engine might get an exception.

Packets for existing connections are not returned to the router, but are dropped. The field, "Packets dropped due to bad buckets" is incremented in the output of the show wccp gre command.

The Central Manager GUI should be modified. Allow the user an option in the GUI to request that all devices reregister with the Central Manager. This option would force an update for certain data that is normally sent to the Central Manager only during registration, such as a time zone change.

Documentation Updates

GUI Update

This section includes only those GUI changes that augment the information documented in the Cisco WAFS 3.0 User Guide.

When you press the Authentication Details button on the Windows Authentication screen, a warning dialog appears before the Authentication Details screen is opened. Click OK to continue to the Authentication Details screen, or click Cancel to return to the previous screen.

Also, if you press the Show Authentication Status button from the Authentication screen while the Authentication Details screen is already open, the focus shifts to the already open Details screen. The authentication status is not recalculated.

Installing Print Drivers on a Client

The following sections augment the "Print Services Configuration" chapter, in the "Adding Drivers and Printers" section, of the Cisco WAFS 3.0 User Guide:

Initializing Print Drivers

Before you install a print driver on a client, you need to initialize the driver so your branch office clients can successfully install the driver and be able to print from applications like Microsoft Word and PowerPoint. Uninitialized drivers often do not install successfully and can cause errors when clients use them to print from Microsoft Word and PowerPoint.

Manual initialization of a driver is required because the WAFS print server cannot execute Windows driver code locally to automatically initialize the driver.

Step 1

Use a Windows client to access the WAFS print server as an administrative user.

Step 3

Choose the shared printer. (This step assumes that a driver has been associated with the printer you choose. For information about associating a driver to a printer, see the "Associating a Driver with your Printer" section.)

Step 6

Change the page orientation from Portrait to Landscape and then back to Portrait. Make sure to click Apply and then click OK between each change.

Changing the page orientation back and forth ensures that the setting is applied correctly.

Step 7

(Optional) Set the desired printing defaults, which are then applied to all future client driver installations.

Associating a Driver with your Printer

Step 5

Click the Advanced tab, and in the Driver drop-down list select the appropriate driver.

Step 6

Click Apply to save your changes, and then click OK to close the window.

Table Of Contents