 Feedback
|
Table Of Contents
Release Notes for ActaStor Release 2.5.2.1
Determining the Software Version
Upgrade from 2.5.1x to 2.5.2.1
Upgrade from 2.5.2.21 to 2.5.2..27
Settings up Windows Authentication
New and Changed Features in ActaStor Release 2.5.2.1
Caveats in ActaStor Release 2.5.2.1
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for ActaStor Release 2.5.2.1
Released Date: June 30, 2005
Text Part Number: OL-6557-03
This document describes caveats for ActaStor Release 2.5.2.1.
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
This section contains the following sections:
•
•
Upgrade from 2.5.1x to 2.5.2.1
To upgrade ActaStor build 2.5.1x to 2.5.2.1, follow these steps:
Step 1
•
•
•
•
•
•
•
•
•
•
•
•
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Upgrade from 2.5.2.21 to 2.5.2..27
For customers upgrading from ActaStor build 2.5.2.21 to 2.5.2.27, follow these steps:
Step 1
•
Step 2
Step 3
Step 4
Step 5
Step 6
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.1
This section lists new features that are supported by ActaStor Release 2.5.2.1.
•
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.1
Table 1 lists the caveats resolved for ActaStor Release 2.5.2.1. Each caveat is listed in detail in the Resolved Caveats section.
Table 1 ActaStor Release 2.5.2.1 Resolved Caveats
Severity 3
R
R
R
R
R
R
R
R
R
R
R
Resolved Caveats
Central Manager
•
Symptom: The Edge FE configuration gets deleted after distribution from the Central Manager.
Condition: When the Edge FE groups and Core FE clusters are configured and the distribute function is performed from the Central Manager.
Workaround: Use the Distribute All function from the Central Manager >Operations tab.
•
Symptom: FE liveness problem. The GUI displays a red checkmark.
Workaround: None.
•
Symptom: Problems in Central Manager when adding or removing a user.
Workaround: None.
•
Symptom: There is a broken image link in the policy definition window of the Central Manager.
Workaround: None.
CIFS
•
Symptom: There are some random and unexplained Edge FE restarts.
Condition: The restart usually occurs when the Edge FE is heavily loaded.
Workaround: Disabling CSO may reduce the problem, but not eliminate it.
•
Symptom: The Rx.internal.log contains an index out of bounds exception during the NT_CREATE_INDX processing.
Workaround: None.
•
Symptom: An out of memory exception occurred in the Edge FE.
Workaround: None.
Data Server
•
Symptom: Site has a network outage for some reason; the switch could be offline for an upgrade or there could be a network problem. All other network devices in the location come back on-line, except the WAFS device, FE-511 running 2.5.2 build 21. When you go to the GUI interface, the Edge FE has a green checkmark but you are unable to browse through the server and see the alias/sharename or shared devices.
Workaround: Go to the GUI, Gateway > Control > Components, select the Edge FE and click Restart. The device restarts and is functional.
Infrastructure
•
Symptom: The Core FE dumps and reboots every five minutes.
Workaround: None
•
Symptom: The open file descriptor defaults to 1024 per process; it should be higher.
Workaround: None.
•
Symptom: During stress testing, the Tx inflator flows the log and crashes the system.
Workaround: None.
Open Caveats
Table 2 lists the caveats opened for ActaStor Release 2.5.2.1 or earlier. Each caveat is listed in detail in the Open Caveats section.
Table 2 ActaStor Release 2.5.2.1 Open Caveats
Severity 3
O
O
O
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.
•
Symptom: An exception occurred while distributing Preposition/Coherency policies.
Condition: When the Core FE version is lower than the Central Manager's version, an exception occurs.
Workaround: Redistribute from the Gateway page.
•
Symptom: Site map does not work when the Core FE version is lower than the Central Manager's version.
Workaround: Enter the root directory manually instead of using site map.
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>.'
Preposition
•
Symptom: A preposition task is terminated if the Edge Server is restarted during the task execution.
Condition: Edge Server is restarted while the preposition task is executing.
Workaround: Rerun the preposition task.
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.
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.1. This happens because the autofs service continues to run even after the RPM is upgraded, and version 2.5.2.1 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.
Related Documentation
Refer to the following documents for more information about ActaStor:
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
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.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Release Notes for ActaStor Release 2.5.2.1
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
