|
|
Table Of Contents
Release Notes for ActaStor Release 2.5.2
Determining the Software Version
Settings up Windows Authentication
New and Changed Features in ActaStor Release 2.5.2
Caveats in ActaStor Release 2.5.2
Obtaining Technical Assistance
Definitions of Service Request Severity
Release Notes for ActaStor Release 2.5.2
Released Date: January 14, 2005
Text Part Number: OL-6557-02
This document describes caveats for ActaStor Release 2.5.2.
Contents
This document includes the following information:
•
Determining the Software Version
•
•
Introduction
ActaStor software functionality offers distributed enterprises and organizations, with dozens or hundreds of branch offices, the benefits of centralized storage with local file services. ActaStor is a plug-and-play file caching solution that significantly improves how a company stores, protects, and manages the data accessed at the corporate network edge. The ActaStor software enables companies to consolidate servers and storage and centralize backup and disaster recovery processes. The end result is a significantly lower TCO (total cost of ownership), enhanced protection of branch office data with reduced administration, and low latency access across the WAN.
The Cisco Edge File Engines (FE) deployed at the branch offices present a cached view of centralized storage to local clients, providing fast, near-local LAN read and write access to the file system. At the data center, the core FE connects directly to one or more network attached storage (NAS) gateways or file servers, performing file requests on behalf of the remote edge FEs and the clients they represent. Central management and monitoring provided by the Central Manager allows the FE to be managed easily and remotely.
Determining the Software Version
To determine the software version currently running on ActaStor, open the Gateway Management GUI and select Gateway and then Utilities. You see the ActaStor version number.
Upgrading the System Image
To upgrade ActaStor build 2.5.1x to 2.5.2, follow these steps:
Step 1
•
•
•
•
•
•
•
•
•
•
•
•
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Settings up Windows Authentication
If you have installed the latest security patches for your Windows 2000 (with SP4) domain controllers, do the following to add a required setting to the file engine:
Step 1
Step 2
Step 3
client schannel = no, write and quit.
Step 4
Step 5
Step 6
wafs30-edge# win diag wbinfo "--sequence"
Step 7
[root@xp-FE1 root]# wbinfo --sequence AC-XP-PRT-SVR : 1 BUILTIN : 1 TREE1 : 82 BXB-ESC : 411 [root@xp-FE1 root]#
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
Feature Table
lists the software features supported by the ActaStor software.
Note
New and Changed Features in ActaStor Release 2.5.2
This section lists new features that are supported by ActaStor Release 2.5.2.
•
A single user open operation (for example, opening a Microsoft Office document) often results in multiple CIFS protocol level opens (and hence roundtrips). The CSO feature performs the first open across the WAN to validate sharing and authorization. Then, any subsequent opens are performed locally.
•
This release provides full support for both long and short file names. Short file names (for example, 8.3 or DOS filenames) are required by some applications.
•
Changes in the ActaStor application and transport level can provide a better balance between control and data operations. This typically yields better interactive user experience.
•
This release includes updated versions of the following:
–
–
–
–
To Upgrade to RSYNC 2.6.3:
–
> rpm -Uvh rsync-2.6.3-1.i386-K9.rpmTo Upgrade to OPENSSH 3.9pl:
–
openssh-3.9p1-1ac1.i386.rpm
openssh-clients-3.9p1-1ac1.i386.rpm
openssh-server-3.9p1-1ac1.i386.rpm–
> rpm -Uvh openssh-*The new Samba version solves the following issue:
–
To Upgrade to Samba 3.0.9:
–
> rpm -Uvh samba-*
Note
To Upgrade to Kerberos 1.3.1:
This release includes a Kerberos upgrade if you cannot authenticate using Win200* DC:
–
> rpm -Uvh krb5-libs-1.3.5-ac4.2.i386-K9.rpm–
Note
•
An error message is displayed if the network interface does not provide a 100-FD (full-duplex) link.
•
NTLM v2 and LM v2 are supported for pre-position and site map.
To implement NTLM v2 and LM v2:
–
–
Note
Caveats in ActaStor Release 2.5.2
Table 1 lists the caveats resolved for ActaStor Release 2.5.2. Each caveat is listed in detail in the Resolved Caveats section.
Table 1 ActaStor Release 2.5.2 Resolved Caveats
Severity 3
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Resolved Caveats
Installation Components
•
Symptom: The Watchdog log does not report the reason why services failed to start.
Workaround: None.
Gateway
•
Symptom: The edge server appears to be out of service and displays a "path not found" error to other users while you are copying a large file (380 MB) into cache.
Workaround: None.
•
Symptom: When synchronizing, some of the files fail to synchronize and the user gets an error message to those files while the synch process is being performed.
Workaround: None.
•
Symptom: Client requests with short names (8.3) can bring the edge server into an incorrect state.
Workaround: None.
•
Symptom: When opening an Access 97 application through ActaStor, the user receives an error that the application cannot be opened.
Workaround: None.
•
Symptom: The WINS server has a Time to Live (TTL) parameter that indicates the rate in which records are being renewed. The edge server disregards this parameter, which can lead to failure in accessing exported servers.
Workaround: None
•
Symptom: Sometimes the RETROSPECT software stops functioning when Office is migrated to WAFS. This can cause the Edge FE to crash with a fatal (out of memory) error due to a parsing error of a client request.
Workaround: None.
•
Symptom: Core FE CIFS client (pre-position and site map) cannot connect to the Windows 2003 File Server (W2K3FS).
Workaround: None.
•
Symptom: Win98 clients are unable to open zip files using version 9 of WinZip.
Workaround: None.
Manager
•
Symptom: Multi Router Traffic Grapher (MRTG) cache hit ratio is erroneous.
Workaround: None
•
Symptom: The SNMPD process causes performance degradation by taking up 100% of the CPU usage.
Workaround: None.
•
Symptom: User and group lookups and authentication against Windows domain controller do not work.
Workaround: None.
•
Symptom: Port 2000 was hard coded during any distribution from the Central Manager because the edge FE and the core FE were connected to it and you were not allowed to change the port.
Workaround: None.
Print Services
•
Symptom: The print server steals browse master elections from Windows 2000 and NT domain controllers.
Workaround: None.
•
Symptom: WAFS edge print server cannot map Service ID (SID) to name if you have 10,000 users.
Workaround: None.
•
Symptom: Print server cannot authenticate against Windows 2003 server (W2K3DC).
Workaround: None.
Replication Services
•
Symptom: Cannot create a replication task with a user name that contains spaces.
Workaround: None
Other Components
•
Symptom: The appliance selects a default of half-duplex if there is no autonegotiation with the switch. This should be changed to a default of full-duplex in the installation script.
Workaround: None
Open Caveats
Table 2 lists the caveats opened for ActaStor Release 2.5.2 or earlier. Each caveat is listed in detail in the Open Caveats section.
Table 2 ActaStor Release 2.5.2 Open Caveats
Severity 3
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
Central Manager
•
Symptom: Site map is limited to displaying share names of 12 characters or fewer because of system limitations.
Workaround: None.
•
Symptom: When starting or restarting the edge server and the core server on the same gateway without waiting long enough, only the latter component starts.
Workaround: Wait until the first component returns a green check mark, and then start the second one.
•
Symptom: Null pointer exception occurs for all pages except Gateway > Control.
Workaround: Close the current browser and open a new instance of the browser.
•
Symptom: When you download a log file from the Central Manager, you see a pop-up window with the following options: Open, Save, and Cancel. If you select Open, you see another pop-up window that lets you create a file. At this point, irrespective of the option you choose, the log file cannot be acquired.
Workaround: Select Save at the first pop-up window.
Gateway
•
Symptom: When working with Win98 applications (Word, Excel, PowerPoint), the performance of these applications is lower than it would be with Windows 2000 or Windows XP.
Workaround: None.
•
Symptom: You can concurrently open the same Word doc from an NT client and an XP client without any warning messages.
Workaround: None.
•
Symptom: Wrong calculation of the file sizes of cached files.
Workaround: None.
•
Symptom: Because of an incorrect function, synchronization fails on one of the files when you first synchronize offline folders.
Workaround: Close synchronization and try again.
•
Symptom: Pre-position does not fetch files with Unicode or enhanced names.
Workaround: None.
•
Symptom: From Win98 and Win95 clients, File Manager (winfile) cannot access mapped cache drives.
Workaround: None.
•
Symptom: Although the recurse into subdirectories option was checked and the final status was "finished successfully," subfolders were not pre-positioned in certain scenarios.
Workaround: Delete the directive and re-create it; make sure that you have selected the recurse into subdirectories option. Then publish the directive to corresponding edges.
•
Symptom: When core FE failover occurs, a Remote Procedure Call (RPC) exception is found.
Workaround: None.
•
Symptom: An exception error is thrown in the core server when a task is terminated by the user.
Workaround: None.
•
Symptom: The transport session gets stuck when trying to connect through a blocked port.
Workaround: Unblock the port or change the system to work over an unblocked port.
•
Symptom: CompressionLevel is being overridden by Central Manager distribution.
Condition: Changing the CompressionLevel in the expert mode of an FE and performing a distribution afterwards.
Workaround: Change the CompressionLevel directly in the Central Manager Database. An administrator can enter the MySQL application and perform the following SQL command:
update connection set compressionLevel='0'where
connection_ID='<selected connection>.'Replication Services
•
Symptom: Replication task status is not available in Central Manager.
Workaround: Get the task status from EdgeServer.
•
Symptom: Restarting of Replication Services sets previously inactive tasks to be active.
Workaround: None.
•
Symptom: You cannot replicate to or from hidden shares.
Workaround: None.
•
Symptom: Replication fails after an RPM upgrade from ActaStor version 2.5.1 to 2.5.2. This happens because the autofs service continues to run even after the RPM is upgraded, and version 2.5.2 does not use the autofs service for replication directives.
Workaround: Login to the Core and Edge FEs that are being set up for replication through the SSH and disable the autofs service using the following command:
service autofs stop
Remove the autofs service from the startup procedure by using the following command:
chkconfig --level 345 autofs off
The chkconfig command ensures that the service does not activate again after a reboot.
Print Services
•
Symptom: When you print using the ActaStor Print Services version 2.5.1(13), print jobs may remain in Windows print queue window even though the print job completed successfully.
Workaround: None.
Related Documentation
Refer to the following documents for more information about ActaStor:
•
•
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. Cisco has a special technical support team trained to support File Engine products. For assistance, you can contact this team using one of the following numbers:
•
•
•
•
You can also contact the File Engine support team using the following e-mail alias:
tac@cisco.com
Please provide the following information in your email:
•
•
•
•
•
•
•
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0501R)
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
Posted: Wed Sep 14 11:59:46 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
