Downloads |
Table Of Contents
Release Notes for Cisco WAFS 3.0
Supported FE or WAE Components
Supported Routers and Switches
Determining the Software Version
Settings up Windows Authentication
New and Changed Features in WAFS Release 3.0
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco WAFS 3.0
Released Date: July 11, 2005
Text Part Number: OL-7774-01
This document describes caveats for the Cisco Wide Area File Services (WAFS) Release 3.0.
Contents
This document includes the following information:
•
Determining the Software Version
•
•
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 WAFS solution includes the Cisco WAFS software running on Cisco FE-511, WAE-611, or 7326-WAE. 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, refer to the Cisco WAFS 3.0 Users Guide.
Hardware Supported
This section lists the hardware components (FEs and WAEs, routers, and switches) that WAFS supports.
Supported FE or WAE Components
Table 1 lists the FE and WAE components that WAFS supports, and the minimum software version required. See the Determining the Software Version.
Supported Routers and Switches
The following routers support WCCP version 2:
•
•
•
•
•
The Catalyst 6000 and Catalyst 6500 Series switches also support WCCP v2.
Determining the Software Version
To determine the WAFS software version currently running on your FE or WAE, open the File Engine Management GUI and select File Engine > Utilities > Support tab. You see the WAFS version number. Alternatively, log into the File Engine CLI and issue the "show version" command. The shortcut CLI command "sh v" also displays the version.
Upgrading the System Image
A CD-ROM came with your FE or WAE, and is used to upgrade the software. To upgrade from ActaStor 2.5.2 to WAFS 3.0, follow these steps:
Step 1
Step 2
Step 3
Installer Main Menu:
1.
2.
3.
4.
5.
6.
7.
8.
Step 4
This prepares a cookie for the WAE 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 5
This installs the Flash cookie that you prepared in the previous step.
Step 6
Step 7
This will prepare the disks by erasing the ActaStor code and associated data from the disks. The WAFS 3.0 image is then installed.
Step 8
Step 9
After the WAE reboots, it is running the WAFS 3.0 software. The WAE has minimal network configuration and is accessible through Telnet (only if it was accessible through the network when it was running the ActaStor software).
Settings up Windows Authentication
If you have installed the latest security patches from Microsoft (Win 2000 SP4 SR1 and further releases, Win 2003 SP1 and further releases), do the following to add a required setting to the file engine:
Step 1
Step 2
Step 3
wafs30-edge(config)# smb-conf section global name "client schannel" value no
Step 4
wafs30-edge(config)# exit
wafs30-edge# write
Step 5
wafs30-edge#service restart winbindd
Step 6
wafs30-edge#windows-domain diagnostics wbinfo "--set-auth-user=AdminstratorUsername%AdminstratorPassword"
where AdminstratorUsername and AdminstratorPassword are the username and password for the user account configured in the Active Directory database.
Verify the command execution result by entering the following CLI command:
wafs30-edge#windows-domain diagnostics wbinfo "--get-auth-user"
The CLI command output should consist of "AdminstratorUsername%AdminstratorPassword" substring.
Step 7
wafs30-edge#windows-domain diagnostics wbinfo -D
Then execute: wafs30-edge#windows-domain diagnostics wbinfo -- sequence
Step 8
wafs30-edge#windows-domain diagnostics wbinfo "--sequence" WAFS30-EDGE : 1 BUILTIN : 1 FE-DEMO : 601
Distributing Licenses
A license key file is on the CD-ROM included in the accessory kit shipped to you with the system. To distribute licenses, follow these steps:
Step 1
Step 2
Step 3
Note
New and Changed Features in WAFS Release 3.0
Table 2 lists the new and changed software features introduced in WAFS Release 3.0. For more information about the features listed, see the Related Documentation.
•
A license key file is on the CD-ROM that is included in the accessory kit shipped with the system.
•
Cisco WAFS supports the full functionality of SNMPv3 MIBs, including the setting of traps.
•
The WAFS CLI allows you to configure, manage, and monitor selected features not available through the WAFS Central Manager GUI, and to perform advanced configuration of WAEs through a console connection or a terminal emulation program.
•
Cisco WAFS can use two disk drives either for storage capacity increase or for increased reliability. RAID is automatically applied to any WAFS appliance with two or more disk drives. Cisco WAFS uses two types of RAID:
–
–
Note
•
–
–
–
–
–
•
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 features include:
–
–
–
–
•
The tcpdump utility allows you to intercept and capture packets passing through a network interface, making it useful for troubleshooting network applications.
•
The 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.
Known Critical Issues
•
Symptom: FE goes to the kernel debugger (kdb) if the maximum transmission unit (MTU) size of the interface is configured as 68.
Condition: Configure MTU size of the interface as 68. After 5 to 10 minutes, FE goes to kdb mode.
Workaround: None
•
Symptom: A CE-511/FE-511 system may enter into a failure mode under some rare circumstances where it can keep falling into kdb (kernel debugger) mode during bootup. Power cycle because reboot does not help.
Condition: The exact conditions under which the problem gets triggered is unknown at this time.
Workaround: Power cycle or reboot the system and when BIOS is active, press the F1 key to enter into BIOS setup mode. Browse to the Devices and I/O ports window and confirm that the Native Mode Operation entry is blank. Move the cursor over this entry and change it to Native. Save the settings and exit.
Limitations and Restrictions
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.
Caveats in WAFS Release 3.0
Table 3 lists the resolved caveats for WAFS Release 3.0. For more information on resolved caveats, see Resolved Caveats.
Table 3 WAFS Release 3.0 Caveats
Severity 3
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Resolved Caveats
Central Manager
•
Symptom: User distribution hangs and the Users tab in Central Manager becomes inaccessible.
Condition: Create more than two users of type "gateway" with different gateways defined for each user.
Workaround: Restart WAFS.
•
Symptom: Invalid NetBIOS name format error.
Workaround: None.
CIFS
•
Symptom: When browsing to a FE through My Network Places, the WAFS exported share still shows ActaStor exported server.
Workaround: None. This is an informational message.
•
Symptom: The system cannot find the file specified error message is displayed while deleting tree.
Condition: When using the rmdir /s /q DOS command with EMC and Netapp filers.
Workaround: Delete tree using Windows Explorer.
•
Symptom: Access control entries (ACEs) do not match after file creation through WAFS. For a Get_Security_descriptor request, a wrong ACE was returned for files.
Condition: Change ACEs through Edge FE and use "Generic" bits instead of specific.
Workaround: None.
CLI
•
Symptom: User cannot remove Samba *.tdb file from the appropriate directories. The CLI command is missing.
Condition: Windows domain-authentication is enabled.
Workaround: None.
•
Symptom: A non-admin user can see the system's file contents.
Condition: A non-admin user logged into the system and executed the #windows-domain diagnostic getent CLI command.
Workaround: None.
•
Symptom: The Linux file system is exposed through the Windows Diagnostics.
Workaround: None.
•
Symptom: Executing a clear statistics all command does not clear SNMP related statistics.
Condition: Any CE device running ACNS version 5.3 or earlier or any FE device running WAFS version 3.0 image.
Workaround: None.
Core Component
•
Symptom: DNS is used last in a Core FE server name resolution sequence.
Condition: The Core FE is using DNS resolution last in the sequence of resolving a file server name. This contrasts the sequence used by Microsoft and, therefore, does not work in Windows environments where the server is multi-homed (several network interfaces).
Workaround: None.
File Replication
•
Symptom: Replication fails when you delete files that do not exist at the source.
Condition: If the 'delete files that don't exist at the source' option is selected when specifying a replication the file replicaton fails.
Workaround: Do not use the 'delete files that don't exist at the source' option.
Logging
•
Symptom: When you use AAA accounting command, the FE logs the actual commands typed in the priv-lvl field (as opposed to the cmd field or the cmd-arg field).
Workaround: None
Print Services
•
Symptom: When you upload the printer driver, the printer name is changed.
Workaround: None
•
Symptom: Permission rights for viewing print job titles do not work properly. When the user goes to the CUPS printer page and uses show completed jobs, the user can see a list of all completed print jobs.
Workaround: None.
•
Symptom: Cannot log into CUPS using domain+user.
Workaround: Log into the CUPS GUI using the username only and do not use domain+username method.
SNMP
•
Symptom: Bad default trigger for 'esConTabIsConnected' (trigger on disconnection).
Condition: Can be seen running the wafs30-edge#show snmp event command.
Workaround: None.
Open Caveats
Table 4 lists the caveats opened for WAFS Release 3.0 or earlier. Each caveat is listed in detail in the Open Caveats section.
Table 4 WAFS Release 3.0 Open Caveats
Severity 3
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
Authentication
•
Symptom: Password change for a local user failed.
Condition: Windows-Domain service is running (either for logged in user authentication or for print-services authentication). Active Directory database has a user account with the same username as the local user account. Upon editing, the local user account properties failed.
Workaround: Stop the Windows-Domain authentication and modify the local user account. Restart Windows-Domain authentication.
Central Manager
•
Symptom: Cannot modify connectivity compression online.
Workaround: Delete connectivity in the Central Manager and create another (modified) one and distribute.
•
Symptom: Image distribution fails and the following error message is received, "download failed - missing size parameter."
Condition: When any or all of the gateways registered to the Central Manager are running a version > 260 but Central manager is at a lower version (that is, < 260 build).
Workaround: Upgrade the FEs/WAEs to a new version (260 or higher). Activate that version on the FEs/WAEs. Finally, upgrade the Central Manager to the same version (before trying to upgrade the FEs further).
CIFS
•
Symptom: An illegal state exception occurred when performing a stress test.
Workaround: None.
•
Symptom: Wrong file server (FS) configuration to connectivity process results in trash shares that are registered to WINS servers and not accessible. When you configure a file server using its full name (for example, win6srv.lab.actona.com) within the CoreServer (CS) and issue a save, the Edge FEs register the wrong share names to WINS.
Condition: When a file server is configured using a full name and then saved.
Workaround: None.
Core Component
•
Symptom: Site-map fails for multi-homed file servers because the Core FE takes the wrong IP address from the NBNS response.
Workaround: Place the Core-FE in a different subnet than the File server or edit the path to the files manually.
Disk
•
Symptom: Config backup failed with an exception in the Central Manager. A file not found error was given for a valid file. Under very rare circumstances, the CE may report errors of the following type:
kernel: %CE-SYS-2-900000: EXT3-fs error (device md(9,5)): ext3_new_inode:reserved inode or inode > inodes count - block_group = 0,inode=1 kernel: %CE-SYS-2-900000: EXT3-fs error (device md(9,5)) in ext3_new_inode: IO failureThis may lead to the referenced file system as not accessible and may cause other failures.
Condition: Not known.
Workaround: Reload the system to bring it into a normal operation mode.
Installation
•
Symptom: When installing Flash image from the CD, an unexpected error was printed out.
Workaround: None.
Interfaces
•
Symptom: In a specific scenario, the Sh interface gi 2/0 cli failed on one FE.
Condition: When the CLI sh interface gi 2/0 command is executed on the FE connected to two interfaces after the clear stat all cli is executed.
Workaround: None.
NFS
•
Symptom: An Edge FE internal log contains an NFS-related ClassCastException error message.
Condition: Some not so well defined scenario of using Edge FE for CIFS and NFS.
Workaround: None.
Print Services
•
Symptom: User administrator is set as privileged by default in print services.
Condition: When you log into a Windows client as built-in Administrator account (belonging to Administrators built-in domain group), your access is set as privileged by default.
Workaround: The administrator should uncheck the check box for Manage Printers/Documents to disable it for the shared printer and click OK. This disables all the Advanced tab settings for the shared printer.
•
Symptom: Security tab settings are enforced only after you click OK.
Condition: When you modify security settings for a printer shared from WAFS FE, the settings are enforced only after you click OK.
Workaround: Click OK for each change applied in the Security tab.
•
Symptom: Print services keep running even after the Edge FE role is removed.
Condition: Configure an Edge FE and Print Services, then remove the Edge FE role from the GUI. Print Services is still running.
•
•
Symptom: The print job is not re-routed to another printer in the cluster when a print job does not print from a clustered printer that is not functioning correctly. CUPS failover does not process jobs that have already been sent; it only knows not to send new jobs to a non-functioning printer.
Condition: Print job not re-routed when a cluster printer is not functioning correctly.
Workaround: Resend the job to the cluster.
•
Symptom: Cannot upload a printer's driver from an NT client when the driver is located on the network.
Condition: When the drivers are copied from the manufacturer disk to a network location without running the disk from the client machine. Use the 'Have Disk' option from the Windows Add Driver Wizard, occasionally the driver will not be installed correctly into the FE.
Workaround: Follow the Add Driver wizard and select the model of the printer. If there is a valid driver in the list (displayed in the right-hand side of the dialog), select the driver and put the NT CD in the client when Windows prompts you to do so.
The driver will then be installed correctly. If the specific driver is not in list, run the driver installation CD on the client machine. Once the installation is completed, the driver should show up under the manufacturer. Follow the Add Printer wizard to install the driver.
•
Symptom: When you type username and password from the CUPS GUI, an error 'You are not authorized to view this page' is displayed.
Condition: You may have entered an incorrect CUPS admin group name in the WAFS GUI so that CUPS cannot validate if you are part of the CUPS admin group.
Workaround: None. This is an user input error. You should correct the CUPS admin group name from the WAFS GUI, save the change, and then retry to login into CUPS GUI.
•
Symptom: Cannot print a test page after installing a driver (before clicking the OK button).
Workaround: After you install the driver, click the 'Apply' button so that the driver will be configured correctly with the printer.
•
Symptom: User cannot use AD Domain Local Group for printer and CUPS administration.
Workaround: When setting printer admin group, make sure the administrative group for WAFS print services is either Global or Universal and NOT Local.
Upgrade or Downgrade Software
•
Symptom: When Windows-Domain authentication is enabled, the copy cifs central CLI command fails.
Workaround: Use the copy ftp central command or the copy http central command.
Related Documentation
Refer to the following documents for more information about WAFS:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Release Notes for Cisco WAFS 3.0
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
