veritas commandcentral™ storage release notes

Veritas CommandCentral™Storage Release Notes

for Microsoft Windows and UNIX

5.1

CommandCentral Storage Release NotesThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version 5.1.1

Legal NoticeCopyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPointControl, and Storage Foundation are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Noticedocumentation accompanying this Symantec product for more information on the ThirdParty Programs.

■ AIX is a registered trademark of IBM Corporation.

■ HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P.

■ Linux is a registered trademark of Linus Torvalds.

■ Solaris is a trademark of Sun Microsystems, Inc.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,

performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich the problemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Overview of this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Introduction to Veritas CommandCentral Storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . 15What’s new in CommandCentral Storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Management and discovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Other enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preinstallation configuration requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Solaris updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Windows updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28HP-UX updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28AIX updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Red Hat Linux updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Solaris system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Windows system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35HP-UX system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39AIX system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Linux system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

CommandCentral web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Co-existence of CommandCentral components with other Symantec

products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 3 No longer supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Hardware that is no longer supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Reporting features that are no longer supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Console features that are no longer supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Contents

Chapter 4 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Install, uninstall, and upgrade limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51NAT firewalls not supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Discovery and management limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Reports show incorrect capacity for NetApp LUNs with space

reservation turned off ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Volume layout not discovered for LDM-managed volumes

mounted without a drive letter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Capacity not discovered for LDM-managed volumes without file

systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Restoring Brocade switch configuration may fail when reboot

required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Unable to remove disk groups via HP EVA SSSU version 4.0 and

4.1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Detect Devices command applies only to objects that use device

managers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Management operations not supported for EMC DMX-4 storage

arrays (1404833) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Discovery of RAID-6 and SSD devices not supported for EMC

DMX-4 storage arrays (1404832) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Console and report limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Reports ToolTips are truncated in Firefox .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.x Agent limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Volumes and disk groups duplicated .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Incorrect data displayed for Oracle RAC applications .... . . . . . . . . . . . . . . . . 54Data displayed for unsupported applications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Discovered objects deleted from the database after 24

hours .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Some Veritas NetBackup objects not displayed .... . . . . . . . . . . . . . . . . . . . . . . . . 56Directory Usage, Directory Aging, and Stale Directories reports

not available for 4.x Agent hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Data Module collection of all files not supported for 4.x Agent

hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56DataModule Importer doesnot support secure (https) connection

to 4.x Agent hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 5 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Install, uninstall, and upgrade issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Error message about VRTSweb during upgrade on Windows

(542244) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Cannot connect to Veritas Enterprise Administrator Console

after installing managed host on Linux (865052) ... . . . . . . . . . . . . . . . . . 58

Contents8

Shared components restarted during CommandCentral install(1051607) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Default agent password cannot be changed usingCommandCentral product installer on UNIX (859670) ... . . . . . . . . . . 58

Managedhost fails to installwhen shell on remoteUNIXmanagedhost is configured as tcsh or csh (1170715) ... . . . . . . . . . . . . . . . . . . . . . . . . 59

Summary file not created during managed host installation onUNIX (1143138) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Erroneous reference to response file at end of ManagementServer install on Solaris (1140473) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

CommandCentral installationsonWindows failwhile configuringSICL (1171143) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Array andCIMVAIL explorers donot runafter installingStorageFoundation 5.1 for Windows (1401940) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

CPI warning displays during reconfiguration of an HP-UXmanaged host (1439576) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

During managed host upgrade from 4.x to 5.1, VRTSob packagefails to uninstall (1407579) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Mistyped Management Server name cannot be corrected in theWindows managed host installer (1449432) ... . . . . . . . . . . . . . . . . . . . . . . . 61

Error message appears during uninstall of the ManagementServer from a Windows host (1432751) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Authentication Service fails to upgrade during ManagementServer installation on Windows (1427441) ... . . . . . . . . . . . . . . . . . . . . . . . . . 62

VRTSWeb folder remains after uninstalling the ManagementServer on Windows (1292780) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Error message about inability to copy files to /var/tmp displaysduring install (1438157) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

HAL configuration fails during managed host install on AIX 5.3TL06 or TL07 (1431432) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Windows’ServiceControlManager displays errorwhen selectingthe Symantec Product Authentication Service(1368976) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

installccstor command lists unsupported options (1402292) ... . . . . . . . 63Incorrect folder appearswhen clickingViewReadMe inWindows

installer (1449592) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Managed host silent install fails with message about inability to

open log file at line 966 (1363772) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64In Push Install Utility, Add IP button not enabled after pasting

host name (1423059) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Data and configuration files remain after uninstalling the

managed host from a Linux host (1397051) ... . . . . . . . . . . . . . . . . . . . . . . . . 65

9Contents

NetBackup 6.5 does not run properly after installingCommandCentral 5.1 (1407023) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Error message appears when uninstalling Symantec ProductAuthentication Service on a Windows managed host(1368709) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Array explorers stop after upgrading Linuxmanaged host to 5.1(1318748) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Symantec Production Authorization Service stops afteruninstalling CommandCentral from a Windows host(1465585) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Management Server and database issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Management tasks not terminated when Management Server

can no longer contact managed host (604446) ... . . . . . . . . . . . . . . . . . . . . 66Operations failwith authentication error onWindows200364-bit

managed host (1042801) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Shared components stop-start order (856750) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 67Status of user-created HAL process does not display when

running vxccs status (1437246) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Incorrect count of managed host licenses in use (1453145) ... . . . . . . . . . 68Hotfix required for a 5.1 Management Server that manages 4.x

managed hosts (1459081) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Array andCIMVAIL log files consume large amount of disk space

(1458508) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69CommandCentral database creates large temporary files

(1446560) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Console and report issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

LUN capacity displayed as "Assigned to VM" for Sun VM diskslice (637435) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Emailed report does not reflect column sorting (615330) ... . . . . . . . . . . . . 70Incorrect name displayed for file systems on unmounted or

unnamed volumes (864757) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Dialogs overwritten when new dialogs are opened (606871) ... . . . . . . . . 70Mismatch between time on Management Server and time

displayed in scheduling dialogs (851525) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Port Bundle Builder Tool displays only one fabric (629557) ... . . . . . . . . . 71The Topology Map’s Print Preview displays a blank page

(1206846) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Table filter does not disable in a custom report (1445762) ... . . . . . . . . . . . 72Custom report created from File or Directory Aging Summary

report does not display data (1435770) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Some reports continue to include data fromanESX serverwhose

device configuration was removed (1452265) ... . . . . . . . . . . . . . . . . . . . . . 72

Contents10

The Switch Port PerformanceDetail report does not display datafor a Cisco switch (1435130) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Total values do not display for tables in ad hoc reports(1446963) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Favorites link for the Host Editor no longer works(1456338) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Array Storage Summary report displays incorrect capacity forIBM DS6000 and DS8000 storage arrays (1437378) ... . . . . . . . . . . . . . . 73

Virtualization Server Claimed Capacity attribute displaysincorrect value (1447060) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

For Cisco switches, the Switch Port Usage Summary report doesnot display port count for unenclosed devices andunidentified adapters (1436270) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

WWN’s of zone members do not display in Zone Builder tool(1440661) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Email addresses for user accountsno longer appear after upgrade(1430275) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Value does not display for the CSV delimiter setting(1450085) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

After upgrade, somepages in the Console take a long time to load(1457768) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Device and device configuration issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Device configuration name does not change after modification

(853400) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Do not use an existing IP address for array configuration

(582094) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Errormessage displayswhen configuring an array explorer from

a 5.0 or 5.0 MP1 managed host (1379639) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 76Change detection does not work for a Symmetrix explorer that

runs on a Linux managed host (1386606) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Product name and version do not display for Sybase 15 instance

(1439468) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Visualization issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Incorrect LUN capacity estimates when CX Meta LUNs createdfrom mixed RAID groups (1016679) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Attributes and group memberships not migrated for HitachiRAID groups (859638) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Incomplete information displayed for newly discovered objects(865845) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Duplicate devicehandles appear for anESXserver aftermigratingdiscovery from SMI-S to VI SDK (1451189) ... . . . . . . . . . . . . . . . . . . . . . . . . 77

Physical memory and number of processors display as 0 for aNetApp unified storage device (1449596) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

11Contents

Incorrect icons appear for virtualization servers and NetAppunified storage devices (1453274) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Inaccurate port names display for FL ports (1450141) ... . . . . . . . . . . . . . . . . 78Monitoring issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Monitoring data not displayed for SnapMirror destination(621024) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Monitoring status not available for ESX server (1122802) ... . . . . . . . . . . . 79Monitoring ofMcDATAswitch is not automatically enabled after

the switch is added to CommandCentral Storage(1159617) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Alerts about CommandCentral Storage processes may displayafter reboot or upgrade (1183630) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Multiple alerts display for offline Veritas Cluster Server servicegroup (1212311) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

After upgrade to 5.1, alerts display in the Console as unknown(1241474) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Alerts display for devices for which monitoring is disabled(1300864) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Numeric collector "Hitachi DKCCSW Moderate Count" does notdisplay a value (1439498) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Monitoring not available for Cisco switches configured in 5.1(1435097) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Monitoring not available for McDATA switches discoveredthrough SMI-S after upgrading to 5.1 (1447971) ... . . . . . . . . . . . . . . . . . 82

SNMPbasedmonitoringof arrays and switchesusingnon-defaultcommunity name does not work (1452092) ... . . . . . . . . . . . . . . . . . . . . . . . . 82

Incorrect or no values display for state collectors "Device Status"and "HitachiDfArrayStatus" (1439527) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Resetting alerts does not always clear alerts (1456719) ... . . . . . . . . . . . . . . 83Exception displays when adding a trap notification to a global

policy (1454720) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83"Port Speed" numeric collector displays incorrect value for a

Cisco switch (1435104) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Some numeric collectors display incorrect values for a Hitachi

storage array (1439495) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Discovery and management issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Disk state not discovered (859207) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Incomplete discoverywhen two versions of DB2 are on the same

host (605860) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84HPEVA:Disabling discovery ofManagementAppliance does not

disable discovery of arrays (614523) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Manually configured database instances not coming up

automatically after upgrade (900677) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Contents12

ESX Server no longer discovered aftermodifying shared storagepool (1184188) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Discovery failure for storagearrays configuredasSMI-Smanagedarrays (1185347) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Windows Logical Manager not discovered on Windows Server2008 host that includes Veritas Volume Manager(1402934) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Consumption information missing for shares mounted on aWindows host (1169224) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

No information about Oracle file whose name ends in a specialcharacter (1413999) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

After migrating discovery of aMcDATA switch from the SWAPIinterface to SMI-S, some zones are no longer discovered(1454063) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Vendor name does not display for EmulexHBAs connected to anESX server (1450813) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Discovery of NetApp unified storage devices fail if NetAppexplorer debug level is set to 6 (1449979) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Correlationmissing between the physical disks and the backendarray LUNs of a Netapp V-series unified storage device(1232692) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Inactive Oracle instances display in the Console after settingActiveInstanceOnly flag (1450915) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Processes in failed state after rebooting SUSE 9 or SUSE 10 host(1458653) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

VMware explorer leaks thread handles on Windows hosts(1460805) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

User management issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Password changes successfully even though New Password and

Re-type password are different (1450916) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 88After editing a user account, the task’s status displays as "Failed"

(1430639) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Data Module issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Data Module alternate auto rule for an alternate scan notassigned to objects (1436439) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Incorrect number of messages in a mailbox (1437400) ... . . . . . . . . . . . . . . . 89Error 7304 appears when scanning NetApp MultiStore Virtual

Systems on Windows (1456054) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Core file indicates that the dmexplorer process cored on AIX

managed host (1449688) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89File scan of a NetApp Storage System fails on a Windows 2000

managed host (1435940) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

13Contents

Chapter 6 Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

About CommandCentral Storage documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Displaying online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Contacting Symantec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Using the support web site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Subscribing to email notification service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Accessing telephone support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Obtaining support by email ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Obtaining license information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Purchasing products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Contents14

Overview of this release

This chapter includes the following topics:

■ Introduction to Veritas CommandCentral Storage

■ What’s new in CommandCentral Storage

Introduction to Veritas CommandCentral StorageVeritas CommandCentral Storage by Symantec represents an entire storageresource management (SRM) solution, giving you what you need to manage yourstorage infrastructure more effectively. It gives you the following capabilities:

■ Offers a single console fromwhich data center administrators deploy,manage,and expand a multi-vendor networked storage environment. TheCommandCentral Storage Console seamlessly integrates performance andpolicy management, storage provisioning, and zoning capabilities to ensurethat the storage infrastructure runs as efficiently as possible. The Consoleenables users to set policies that automate notification, recovery, and otheruser-definable actions.

■ Discovers and tracks the utilization and allocation of storage resources downto the disk level. The reporting features in CommandCentral Storage providea complete and detailed view into precisely how and where storage—for officedocuments, files, applications, email, anddatabases—is used in your enterprise.

■ Shows usage trends andmakes forward projections. You can gather data bothlocally and remotely (throughamanagedhost). Thismeansyou canget baselineinformation without huge deployment costs. Armed with this data, you cando predictivemodeling to analyze the return on your storage investment. Youalsohavewhat youneed to implement aprogramof departmental chargeback.

Using CommandCentral Storage together with other Symantec software, ITmanagers have the tools they need to perform real, active, end-to-end storage

1Chapter

resource management and make strategic decisions about their future storageneeds.

What’s new in CommandCentral StorageVeritas CommandCentral Storage 5.1 contains and builds upon CommandCentralStorage 5.0 functionality, providing several new features.

Management and discoveryCommandCentral Storage5.1 introduces the followingmanagement anddiscoveryfeatures.

Enhanced agentless discovery of storage resourcesIf you do not install the CommandCentral managed host on hosts in your storagenetwork, the CommandCentral Management Server can discover those hosts andtheir connections to storage resources through agentless discovery.

The process involves creating a user-created host in order to associate theunidentified adapter (HBA) discovered through switch discovery to the host towhich it connects. In previous versions of CommandCentral, you could do thisone host at a time. Now, CommandCentral 5.1 provides you with the ability tocreate multiple hosts at once and to automate the process by creating rules andimporting information from a CSV file.

Formore information about this feature, see the CommandCentral StorageUser’sGuide.

Detection of configuration related changes to storage arraysIn CommandCentral Storage 5.0MP1, explorers initiate discovery of devices basedon the explorer’s polling interval. The polling interval is the amount of time thatthe explorer waits to initiate discovery of the device. For example, the pollinginterval might be 180 minutes.

InCommandCentral Storage 5.1, explorers continue to initiate discovery of devicesbased on the explorer’s polling interval; however, for certain array explorers, youcan also enable change detection. When you enable change detection, explorerslisten to SNMP traps or frequently poll storage arrays—for example, every 15minutes—in order to detect configuration related changes to that array—forexample, masking changes. When the explorer detects configuration relatedchanges to the storage array, the explorer initiates a full discovery of the array.

Overview of this releaseWhat’s new in CommandCentral Storage

16

For example, if you enable change detection for EMC CLARiiON storage arrays,by default, the explorer listens for SNMP traps from CLARiiON storage arrays.When the explorer detects changes, it initiates discovery of the array. Becausethe explorer discovers the changes in near real-time, CommandCentral Storagecan provide you with more up-to-date information about the storage array. Incontrast, if you do not enable change detection, discovery occurs only when theexplorer polls the storage array using the polling interval—for example, a pollinginterval of 180 minutes.

Change detection is available for the following storage arrays:

■ EMC CLARiiON

■ EMC Symmetrix

■ Hitachi HiCommand

■ HP EVA

■ NetApp unified storage devices

For information about enabling change detection, see the CommandCentralHardware and Software Configuration Guide.

Improved Data Module file scanningIn CommandCentral Storage 5.0 MP1, the Data Module file scanner determines afile’s size by its logical size. Now, in CommandCentral Storage 5.1, the file scanneralso collects a file’s physical size. A file’s physical size provides you with a moreaccurate account of space consumption over the logical size. You can use theDataModule Importer settings and Data Module rules to specify whether you wantsummary reports that report on directory size, user consumption, file type usage,and aging data to display a file’s size by its logical size or physical size.Additionally, you can drill down into detail reports to display both the logical sizeand physical size.

For more information, see the CommandCentral Administrator’s Guide.

Discovery of device groups and composite groups for EMCSymmetrix storage arraysCommandCentral Storage now discovers the name of the device groups andcomposite groups to which devices from EMC Symmetrix storage arrays belong.ThegroupnamesappearwhenyouviewanEMCSymmetrix storagearray’sDevicespane.

17Overview of this releaseWhat’s new in CommandCentral Storage

Discovery of replication objects for HP EVA storage arraysCommandCentral Storage now discovers the following replication objects for HPEVA storage arrays:

■ Snapshots

■ Vsnaps

■ Snapclones

Added support for discovery of ESX servers through theVMware Infrastructure SDKIn CommandCentral Storage 5.1, you can now configure discovery of ESX serversthrough the VMware Infrastructure SDK (VI SDK). This allows you to discoverindividual ESX servers through VI SDK or a VirtualCenter that manages multipleESX servers through VI SDK.

For information about configuring discovery through VI SDK, see theCommandCentral Hardware and Software Configuration Guide.

Sybase ASE 15 supportCommandCentral now supports discovery of Sybase Adaptive Server Enterprise(ASE) 15.

Added support for the correlation of non-HDS backend arrayvolumes for HDS Tagma USP and USP-V series arraysCommandCentral nowsupports the correlationof thephysical disks ofHDSTagmaUSP and USP-V series arrays and their backend array volumes (LUNs) when thebackend arrays are from other vendors that are listed in the CommandCentralHardware and Software Compatibility List.

Added support for the correlation of backend array volumesfor NetApp V-Series storage systemsCommandCentral now supports the correlation of the physical disks of NetAppV-Series storage systems and their backend array volumes (LUNs).

ReportingCommandCentral Storage 5.1 introduces the following reporting features.


18

Added in-context performance reports for certain objectsWhen you use the Managing Summary section of the CommandCentral StorageConsole to navigate to an object's Reporting pane, you cannow select performancereports that are scoped for the following objects:

■ Fibre channel adapters

■ Fibre channel controllers

■ LUNs

■ Physical disks

■ RAID groups for Hitachi HDS storage arrays

■ Switch ports

■ VxVM volumes

Added the Switch Port Usage Trend reportYou can now view the Switch Port Usage Trend report, which allows you to trackused and unused ports over a specified time frame.

New sample ad hoc reportsCommandCentral Storage now includes the following sample ad hoc reports:

■ Application Access Path Inventory Report: Presents all the combinations ofend-to-end access path inventory (for the logical objects) from application tothe LUN (and the associated array).

■ FibreAttached Storage ConsumptionReport: Displays information about fibreattached storage given to hosts and how that capacity is utilized by the filesystems.

■ Local vs RemoteReplicationReport: Depicts howmuch of the primary (source)capacity is replicated locally vs replicated remotely.

■ NetAppQuotaOver-ProvisioningReport: Providesdetails aboutquotaallocationon a NetApp volume and the % over-provisioning.

■ SANStorageReport: Details array andhost utilization of SANstorage and alsothe shared claimed capacity between hosts.

For informationaboutworkingwith these customreports, see theCommandCentralStorage User’s Guide.


InstallationCommandCentral Storage 5.1 introduces the following installation features.

New licensing optionsIn previous versions of CommandCentral Storage, you could purchase licenses toenable the following modules:

■ Operations Module

■ Data Module

■ Operations Module and Data Module

In CommandCentral Storage 5.1, both the Operations Module and Data Moduleinstall by default. CommandCentral Storage now includes the following types oflicenses:

■ Management Server

■ Managed host

■ Switch port

■ NAS (TB)

Because of these new licensing options, you need to obtain new licenseswhen youupgrade to CommandCentral 5.1. When you upgrade to 5.1, an evaluation licenseinstalls. The evaluation license is valid for 60 days. Obtain new licenses beforethe evaluation license expires.

Formore information about obtainingnew licenses, go to the Symantec LicensingPortal: www.symantec.com/business/products/licensing/activation/

For more information about CommandCentral licensing, refer to theCommandCentral Administrator’s Guide.

Ability to install a managed host and then configure it laterIn CommandCentral Storage 5.1, you can now choose to install the managed hostwithout configuring it. You can then configure thehost at a later time. For example,youmight use this feature to clone themanagedhost onmultiple hosts for a fasterdeployment.

For more information, see the CommandCentral Installation Guide.

Reduced media and install footprint for the managed hostBoth the media footprint and installation footprint of the CommandCentralmanaged host was reduced. As a result, the managed host occupies less space.


20

http://www.symantec.com/business/products/licensing/activation/

Other enhancementsCommandCentral Storage 5.1 introduces the following features.

Windows Server 2008 supportYou can now install the CommandCentral managed host and Push Install Utilityon Windows Server 2008 hosts.

Red Hat Linux 5.0 supportYou can now install the CommandCentral managed host on Red Hat Linux 5.0hosts.

SUSE Linux Enterprise server 9 and 10 supportYou cannow install theCommandCentralmanagedhost onSUSELinuxEnterpriseserver 9 and 10 hosts.

Added links to access the CommandCentral Storage ChangeManager ConsoleIf you enable CommandCentral Storage Change Manager on your ManagementServer, you can load theCommandCentral StorageChangeManagerConsole fromthe CommandCentral Storage Console. To do this, you can use the following links:

■ Storage Change Manager—this link appears in the header of theCommandCentral Storage Console. When you click this link, theCommandCentral Storage Change Manager Console loads in a new browserwindow and the Home pane (Dashboard) displays.

■ Change History—this link appears in the Overview pane for storage resourcesforwhichCommandCentral StorageChangeManager tracks the changehistory.When you click this link, the CommandCentral Storage Change ManagerConsole loads in a newbrowserwindow, displays the Changes pane, and filtersthe pane to display the change history for the specific storage resource.

For more information, see the CommandCentral Storage User’s Guide.

Name of devicemanagers display when viewing list of devicesWhenyouview the list of configureddevices in theConsole, theConfiguredDevicesSummarynowdisplays thenameof thedevicemanager thatmanages yourdevices.This is helpful when you want to identify the device manager that manages aspecific device. For example, you may want to identify the CIMOM that manageseach of your storage arrays.



Ability to set new managed hosts in unmanaged stateIn CommandCentral Storage 5.1, you can configure the Management Server todetect new managed hosts, but not automatically manage those hosts. When thishappens, the Management Server does not collect any data from the managedhost and it does not monitor the managed host. When you are ready for theManagement Server to manage an unmanaged host, you can simply refresh themanaged host in the Console.

For example, you might do this if you have a standard system image policy or ifyou need to take advantage of an available installation window.


Hotfix deployment mechanismCommandCentral introduces a new hotfix deployment mechanism that allowsyou to push and install hotfixes on remote hosts. The mechanism also allows youto determine the current version of a CommandCentral component so that youcan better manage the deployment of hotfixes.

For more information about the hotfix deployment mechanism, see theCommandCentral Administrator’s Guide.


22

System requirements


■ Preinstallation configuration requirements

■ Operating system requirements

■ System resource requirements

■ CommandCentral web browser requirements

■ Co-existence of CommandCentral components with other Symantec products

Preinstallation configuration requirementsThe largest share of configuration occurs prior to installing CommandCentralStorage. This configuration typically comprises a number of activities performedin this order:

■ Making sure that your storage network devices and their firmware levels aresupported by CommandCentral Storage

■ Verifying that the device is physically connected to the storage network in asupported manner

■ Configuring thedevice to the vendor’s specifications andmakinganyadditionalmodifications required by CommandCentral Storage

For the latest support information, see the CommandCentral Hardware andSoftware Compatibility List. This document is updated regularly at:

http://seer.entsupport.symantec.com/docs/311599.htm

2Chapter


Operating system requirementsTable 2-1 provides operating system requirements for CommandCentral 5.1components.

Table 2-1 Operating system requirements for CommandCentral 5.1components

Operating systems supportedComponent

■ Solaris 8, 9, 10

■ Windows Server 2003 64-bit (Xeon/Opteron) for the following editions:Datacenter and Enterprise

■ Windows Server 2003 32-bit for the following editions: Standard, Web,Datacenter, and Enterprise

■ Windows Server 2000 (Service Pack 3) for the following editions: Server,Advanced Server, and Datacenter Server

Note:OnWindowshosts, installWindowsManagement Instrumentation.To install this Windows component, use Windows' Add or RemovePrograms tool.

ManagementServer

System requirementsOperating system requirements

24

Table 2-1 Operating system requirements for CommandCentral 5.1components (continued)


■ Solaris 8, 9, 10 with GSS package (SUNWgss)

■ HP-UX 11i v1 (11.11), 11i v2 (11.23), 11i v2 0904 (11.23 PI), 11i v3 (11.31and 11.31 PI)

Note: ForHP-UX11i v3, arraymanagement andNetApp unified storagediscovery are not supported.

■ AIX 5.2, 5.3

Note: For AIX 5.3 ML5, install all IY92292 filesets on the host. Verifythat the filesets are installed by typing the following command: "instfix-ik IY92292". The following message confirms that all filesets areinstalled: "All filesets for IY92292 were found".

■ Red Hat Linux 3.0 Advanced Server and Enterprise Server (32-bit), 4.0Advanced Server (32-bit) and Enterprise Server (32-bit and 64-bit), and5.0 Enterprise Server (32-bit and 64-bit)

Note: For Red Hat Linux 5.0, array management and NetApp unifiedstorage discovery are not supported.

Note: Install not supported if SELinux is enabled.

Note:Werecommend that you create themaximumnumber of /dev/sgndevice paths (255) using the following command: dev/MAKEDEV -v -m255 sg. The host uses these paths to gather information about LUNs. Bychanging the setting before you install CommandCentral, you enable thehost to gather information for more LUNs than the default number ofpaths (15).

■ SUSE Linux Enterprise server 9 and 10 (32-bit and 64-bit)

Note: Arraymanagement andNetApp unified storage discovery are notsupported.

Note: Install not supported if SELinux is enabled.

■ Windows Server 2008 32-bit and 64-bit for the following editions:Standard, Datacenter, Enterprise, and Web

■ Windows Server 2003 64-bit (Xeon/Opteron) for the following editions:Datacenter and Enterprise

■ Windows Server 2003 32-bit for the following editions: Datacenter,Enterprise, Standard, and Web


Note: ForWindowshosts, installWindowsManagement Instrumentationusing Windows' Add or Remove Programs tool.

managedhost

25System requirementsOperating system requirements

Table 2-1 Operating system requirements for CommandCentral 5.1components (continued)


ESX virtualization server 3.0.0, 3.0.1, 3.1.0, 3.5.0, 3.5.1, and 3.5.2

Note: There is no support for ESX servers which have QLogic HBAs.

Virtual managed hosts are supported on the following guest operatingsystems:

■ Red Hat Linux 3.0 and 4.0

■ Windows Server 2008 32-bit and 64-bit

■ Windows Server 2003 64-bit (Xeon/Opteron)

■ Windows Server 2003 32-bit

■ Windows Server 2000 (Service Pack 3)

Note: The virtualmachine does not require any FibreChannel HBA drivers.

virtualmanagedhosts

The minimum recommended resolution for the Console is 1024 x 768.

See “CommandCentral web browser requirements” on page 44.

Console

■ Windows Server 2008 32-bit and 64-bit for the following editions:Standard, Datacenter, Enterprise, Web

■ Windows Server 2003 for the following editions: Datacenter (32-bit and64-bit), Enterprise (32-bit and 64-bit), Standard (32-bit), andWeb (32-bit)


Agent PushInstallUtility

Solaris updates requiredThis section lists patches required to run CommandCentral on Solaris.

In addition to the required patches listed here, you may want to install the latestfull patch cluster for your version of Solaris. Patch clusters include additionalrecommended and security patches.

Download Solaris patches and patch clusters from the following Web site:

http://sunsolve.sun.com

The GSS package (SUNWgss) is required on all CommandCentral ManagementServers running on Solaris.


26

http://sunsolve.sun.com

To list the patches currently installed on your Solaris system

◆ Use the showrev command:

showrev -p

To checkwhether a particular patch is installed, use the command as follows:

showrev -p | grep patch-id

where patch-id is the patch number in the format xxxxxx-xx.

When updating Solaris patches, you should apply the Libthread patch last.

Solaris 8Following are the required patches to run CommandCentral on Solaris 8:

Note: An asterisk (*) indicates that the patch is required for array managementfunctionality.

108652-78*108528-29108435-14108435108434-14108434 *

108993-18108989-02108987-13108940-60108921-19108773-18

111023-03110615-10110386-03109326-13109147-27108993-32

112003-03111721*111317-05111310-01111308-04111111-03

116602-01115827-01113648-03112472-01112438-02112396-02

112438

Solaris 9The SUNWscpux package is required on Solaris 9 hosts.

Following are the required patches to run CommandCentral on Solaris 9 requiredfor array management:

112785-30113096-03111703111722-04

Solaris 10The SUNWscpu package is required on Solaris 10 hosts.


Increasing semaphore limits on SolarisThe Veritas Provider Access Layer (VxPAL) and the Veritas EnterpriseAdministratorService requiremoreoperating systemsemaphores thanareusuallyset by default on Solaris. This can also be a problem on the otherUNIXs; however,the Solaris default semaphore limit is small.

To increase semaphore limits on Solaris

1 Open a UNIX console and log in as root on the target host.

2 Using a text editor, open: /etc/system

3 Locate a line similar to the following. If the line is not there, add it:

set semsys:seminfo_semmni=0x10

4 Make sure that the value is something larger than what is currently there.For example, set sminfo_semmni to 0x10.

5 Save the file and reboot the host.

Windows updates requiredDownload and apply Windows updates from the following Web site:

http://windowsupdate.microsoft.com

Windows 2000

Table 2-2 Required Updates for Windows 2000

Required UpdatesComponent

Windows 2000 Service Pack 3ManagementServer

Windows 2000 Service Pack 3managed host

Windows 2000 Service Pack 3Agent Push InstallUtility

HP-UX updates requiredThis section lists the patches required to run CommandCentral on differentversions of HP-UX. Only the CommandCentral managed host is supported onHP-UX.

You can download HP-UX patches from the following Web site:


28

http://windowsupdate.microsoft.com

http://www2.itrc.hp.com/service/home/hpMaint.do?admit=-1335382922+1146593773343+28353475

HP-UX 11i v1Following are the required patches to run the CommandCentralmanaged host onHP-UX 11.i v1:

Note: An asterisk (*) indicates that the patch is required for array managementfunctionality.

PHSS_30968*PHSS_28880*PHSS_28509*PHSS_31326

HP-UX 11i v2Following are the required patches to run the CommandCentralmanaged host onHP-UX 11.i v2:

PHSS_34445PHSS_34444PHSS_34853PHSS_35055PHSS_36336PHSS_34859

PHSS_32231PHSS_35978PHSS_33903PHSS_35528

Increase the stack size for the vxpal process by following the procedure forincreasing the application stack size at the following Web site:

http://docs.hp.com/en/B2355-60105/Aries.5.html

AIX updates requiredThis section lists the patches required to run CommandCentral on differentversions of AIX. Only the CommandCentral managed host is supported on AIX.

To list the patches currently installed on your AIX system

◆ Use the instfix command:

instfix -ia

To checkwhether a particular patch is installed, use the command as follows:

instfix -ia | grep patch-id

where patch-id is the patch number in the format IYxxxxx.




http://docs.hp.com/en/B2355-60105/Aries.5.html

AIX 5.2Following are the required patches to run the CommandCentralmanaged host onAIX Version 5.2 with Maintenance Level 7 (ML7) or higher:

■ xlC.rte-6.0.0.0

■ xlC.aix50.rte-6.0.0.0

AIX 5.3Following are the required patches to run the CommandCentralmanaged host onAIX version 5.3 with Technology Level 3 (TL3) or higher.

■ xlC.rte-6.0.0.0

■ xlC.aix50.rte-6.0.0.0

Red Hat Linux updates requiredThis section lists the patches required to run CommandCentral on differentversions of RedHat Linux. Only the CommandCentralmanaged host is supportedon Red Hat Linux.

Advanced Server 3.0Following are the required patches to run the CommandCentralmanaged host onRed Hat Linux Advanced Server 3.0:

■ openssl096b-0.9.6b-16

■ libstdc++-libc6.2-2.so.3

Advanced Server 4.0Following are the required patches to run the CommandCentralmanaged host onRed Hat Linux Advanced Server 4.0:

■ openssl096b-0.9.6b-16


Enterprise Server 3.0Following are the required patches to run the CommandCentralmanaged host onRed Hat Linux Enterprise Server 3.0:

■ openssl096b-0.9.6b-16



30

Enterprise Server 4.0Following are the required patches to run the CommandCentralmanaged host onRed Hat Linux Enterprise Server 4.0:

■ openssl096b-0.9.6b-16


System resource requirementsThe tables below provide memory and disk space specifications forCommandCentral components. The amounts of memory and disk space are inaddition to the resources already consumed by other software on the host.

Note: Disk space requirements are only for installation of the product itself. Onthe Management Server, disk space requirements (as well as memory and CPU)increase as you add switches, storage devices, and file usage information to theCommandCentral database. On managed hosts, used disk space increases as thenumber of files that you scan with the Data Module increases.

For the latest Management Server and managed host processor requirements,see theCommandCentralHardwareandSoftwareCompatibilityList. This documentis updated regularly at:


Note: On UNIX hosts, although you can specify user-defined install directoriesfor CommandCentral components, you cannot specify user-defined installdirectories for shared components. TheCommandCentral installer installs sharedcomponents (such as the Authentication Service and the Authorization Service)under the /optdirectory only. Approximately 160MBof free disk space is requiredfor these components.

■ Solaris system requirements

■ Windows system requirements

■ HP-UX system requirements

■ AIX system requirements

■ Linux system requirements

31System requirementsSystem resource requirements


Solaris system requirementsThe following tables provide memory and disk space requirements for installingand upgrading CommandCentral components on Solaris hosts:

■ Table 2-3 provides system resource requirements for installingCommandCentral 5.1 components.

■ Table 2-4 provides system resource requirements for upgradingCommandCentral 5.0 components to 5.1.

■ Table 2-5 provides system resource requirements for upgradingCommandCentral 5.0 MP1-RP3 components to 5.1.

The amounts of memory and disk space are in addition to the resources alreadyconsumed by other software on the host.

Disk space requirements for the CommandCentral Management Server are onlyfor installationof the component itself.Disk space, CPU, andmemory requirementsincrease as you add switches, storage devices, and file usage information to theCommandCentral database.

Note:When you install or upgrade to CommandCentral 5.1, you need to ensurethat there is sufficient space to create a backup of the binaries. On Solaris, thebackups are created in /var/sadm/patch and /var/sadm/pkg

Table 2-3 System resource requirements for installing CommandCentral 5.1on Solaris hosts

Dual CPUrequired?

Temp spacerequired

Disk space requiredPhysicalmemoryrequired

Component

Yes313MBTotal: 2022MB

■ Relocatable: 1072MB

■ Non-relocatable: 769MB

■ Binaries backup: 35MB

CCS: 2GB(4GBrecommended)

SCM: 4GB(8GBrecommended)

CCS + SCM:4GB (8GBrecommended)

ManagementServer

System requirementsSystem resource requirements

32

Table 2-3 System resource requirements for installing CommandCentral 5.1on Solaris hosts (continued)

Dual CPUrequired?

Temp spacerequired


Component

No186MBTotal: 393MB




256MBManagedhost

No186MBTotal: 962MB




256MB(512MBrecommended)

Managedhost(with arraymanagement)

Table 2-4 System resource requirements for upgrading CommandCentral 5.0to 5.1 on Solaris hosts

Dual CPUrequired?

Temp spacerequired


Component








ManagementServer

No186MBTotal: -54MB

■ Relocatable: -54MB

256MBManagedhost

No186MBTotal: -13MB







Table 2-5 System resource requirements for upgrading CommandCentral 5.0MP1-RP3 to 5.1 on Solaris hosts

Dual CPUrequired?

Temp spacerequired


Component

Yes313MBTotal: 61MB



■ Binariesbackup: -180MB




ManagementServer

No186MBTotal: -119MB



■ Binaries backup: -64MB

256MBManagedhost







Temporary space shows the additional space thatmust be in /var/tmp for tar.gzpackages.

Consider the following calculations:

■ Disk space calculation: Thedisk space requiredvaries dependingon thenumberof components you choose to install. The installer sums the space required forall the components you are installing.

■ Temp space calculation: The installer copies all tar.gz files to /var/tmp fromwhere it installs the component and then deletes the tar.gz files. The tempspace required equals the size of the largest component package you areinstalling, plus the size of the associated tar file. The install script calculatesthe package and the tar file sizes and reports this sum as the required tempspace.


34

Windows system requirementsThe following tables provide memory and disk space requirements for installingand upgrading CommandCentral components on Windows hosts:





Disk space requirements for the Management Server are only for installation ofthe component itself. Disk space, CPU, andmemory requirements increase as youadd switches, storage devices, and file usage information to the CommandCentraldatabase.

Consider the following while provisioning disk space:

■ When you install CommandCentral 5.1, the non-relocatable space is requiredon the system drive where the operating system is installed. If you areupgrading to 5.1, the non-relocatable space is required on the drive where theCommandCentral component is installed.

■ When you upgrade to CommandCentral 5.1, you need to ensure that there issufficient space to create a backup of the binaries. On Windows, the backupis created on the system drive.

Table 2-6 System resource requirements for installing CommandCentral 5.1on Windows hosts

Dual CPUrequired?

Temp spacerequired


Component







ManagementServer


Table 2-6 System resource requirements for installing CommandCentral 5.1on Windows hosts (continued)

Dual CPUrequired?

Temp spacerequired


Component

No115MBTotal: 185MB



256MBManagedhost(local install)

No150MBTotal: 185MB



256MBManagedhost(remoteinstall usingAgent PushInstallUtility)

No115MBTotal: 344MB




Managedhostwith arraymanagement(local install)

No150MBTotal: 344MB




Managedhostwith arraymanagement(remoteinstall usingAgent PushInstallUtility)

No150MBTotal: 147MB




Agent PushInstall Utility


36

Table 2-7 System resource requirements for upgrading CommandCentral 5.0to 5.1 on Windows hosts

Dual CPUrequired?

Temp spacerequired


Component

Yes260MBTotal: 440MB + twice thedatabase size

■ Relocatable: 90MB +database size

■ Non-relocatable: 350MB+ database size




ManagementServer

No115MBTotal: 1MB



No150MBTotal: 1MB



No115MBTotal: 5MB





No150MBTotal: 5MB





No150MBTotal: 5MB





Table 2-8 System resource requirements for upgrading CommandCentral 5.0MP1-RP3 to 5.1 on Windows hosts

Dual CPUrequired?

Temp spacerequired


Component

Yes260MBTotal: 90MB + twice thedatabase size

■ Relocatable: 90MB +database size




ManagementServer

No115MBTotal: -99MB


■ Non-relocatable: -100MB


No150MBTotal: -99MB




















38

HP-UX system requirementsThe following tables provide memory and disk space requirements for installingand upgrading CommandCentral components on HP-UX hosts:





Note:When you install or upgrade to CommandCentral 5.1, you need to ensurethat there is sufficient space to create a backup of the binaries. On HP-UX, thebackup is created in /var/adm/sw/save.

Table 2-9 System resource requirements for installing CommandCentral 5.1on HP-UX hosts

Dual CPUrequired?

Temp spacerequired


Component

No185MBTotal: 466MB




256MBManagedhost

No185MBTotal: 924MB







Table 2-10 System resource requirements for upgrading CommandCentral 5.0to 5.1 on HP-UX hosts

Dual CPUrequired?

Temp spacerequired


Component

No185MBTotal: 6MB

■ Relocatable: - 86MB


256MBManagedhost

No185MBTotal: 164MB






Table 2-11 System resource requirements for upgrading CommandCentral 5.0MP1-RP3 to 5.1 on HP-UX hosts

Dual CPUrequired?

Temp spacerequired


Component





256MBManagedhost








CommandCentralmanagedhosts requireminimumvalues for the followingHP-UXvariables:

■ maxssiz—80MB (process maximum stack size)

■ maxdsiz—1.9GB (data segment)

Formore information about these variables, refer to yourHP-UX documentation.


40

AIX system requirementsThe following tables provide memory and disk space requirements for installingand upgrading CommandCentral components on AIX hosts:





Note:When you install or upgrade to CommandCentral 5.1, you need to ensurethat there is sufficient space to create a backup of the binaries. OnAIX, the backupis created in /usr/lpp.

Table 2-12 System resource requirements for installing CommandCentral 5.1on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component

No153MBTotal: 394MB



256MBManagedhost

No153MBTotal: 699MB





Table 2-13 System resource requirements for upgrading CommandCentral 5.0to 5.1 on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component

No153MBTotal: - 553MB



256MBManagedhost


Table 2-13 System resource requirements for upgrading CommandCentral 5.0to 5.1 on AIX hosts (continued)

Dual CPUrequired?

Temp spacerequired


Component






Table 2-14 System resource requirements for upgrading CommandCentral 5.0MP1-RP3 to 5.1 on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component

No153MBTotal: - 553MB



256MBManagedhost







Linux system requirementsThe following tables provide memory and disk space requirements for installingand upgrading CommandCentral components on Red Hat Linux and SUSE Linuxhosts:






42

Table 2-15 System resource requirements for installing CommandCentral 5.1on Linux hosts

Dual CPUrequired?

Temp spacerequired


Component

No29MBTotal: 231MB




256MBManagedhost

No29MBTotal: 347MB






Table 2-16 System resources for upgrading CommandCentral 5.0 to 5.1 onLinux hosts

Dual CPUrequired?

Temp spacerequired


Component

No29MBTotal: -47MB



256MBManagedhost

No29MBTotal: -97MB





Table 2-17 System resources for upgrading CommandCentral 5.0 MP1-RP3 to5.1 on Linux hosts

Dual CPUrequired?

Temp spacerequired


Component

No29MBTotal: -51MB



256MBManagedhost


Table 2-17 System resources for upgrading CommandCentral 5.0 MP1-RP3 to5.1 on Linux hosts (continued)

Dual CPUrequired?

Temp spacerequired


Component

No29MBTotal: -81MB






CommandCentral web browser requirementsOne of the following Web browsers is required to run the Console:

■ Microsoft Internet Explorer 6.x or 7.x (Windows only)

■ Mozilla 1.7 (Solaris only)

■ Mozilla Firefox 1.07*, 1.5*, 2.0.0.x, or 3.0 (Windows only)* For CommandCentral Storage only.

Your browser must support either JScript 5.5 (provided with Microsoft InternetExplorer 6 or later) or JavaScript 1.2 . Additionally, for Internet Explorer, SecureSockets Layer (SSL) 3.0 ActiveX scripting must be enabled.

If you are using pop-up blockers, either disable them or configure them to acceptpop-ups fromtheCommandCentralManagementServers towhichyouwill connect.

To display the CommandCentral Storage Topology Map in a Web browser, yourworkstation must have at least Java 5 (version 1.5) installed.

Note: For Internet Explorer 6.0 on Windows 2000 (Server, Advanced Server, orDatacenter Server) and Windows 2003 Server (Standard Edition, DatacenterEdition, Enterprise Edition, orWeb Edition), set the default Intranet zone securitylevel to MEDIUM or lower.

System requirementsCommandCentral web browser requirements

44

Co-existence of CommandCentral components withother Symantec products

Several Symantec productsmay be required in a typical data storagemanagementenvironment.

Table 2-18 describes the products (or product components) that can co-exist ona host where CommandCentral 5.1 components are installed.

Note: In the following table, the CommandCentral Management Server includesthe CommandCentral Storage and CommandCentral Storage Change Managermodules only. It does not pertain to CommandCentral Enterprise Reporter.

Note: Co-existence between Management Servers has been tested on Solaris withSF 5.0MP3. Co-existence of Management Servers and managed hosts has beentested on Solaris with SF 5.0MP3/SFRAC 5.0MP3.

Table 2-18 CommandCentral co-existence with other Symantec products

Co-install possible?Symantec productcomponent

CommandCentralcomponent

YesCommandCentral EnterpriseReporter

Management Server

Yes, if you enabled theCommandCentral Storagemodule only

No, if you enabled theCommandCentral StorageChange Manager module

Veritas SF Manager 1.1 (orhigher) Management Server

Management Server

YesSymantec License InventoryManager 4.0 agent

Management Server

NoVeritas Backup ReporterManagement Server

NoVeritas Application DirectorManagement Server

No (no support for highavailability)

Veritas Cluster Server (VCS)cluster node

Management Server

No (no support for highavailability)

Microsoft Cluster Server(MSCS)

Management Server

45System requirementsCo-existence of CommandCentral components with other Symantec products

Table 2-18 CommandCentral co-existence with other Symantec products(continued)



NoNetBackup OperationsManager

Management Server

NoNetBackup Master/MediaServer

Management Server

YesVeritas Cluster Server 5.1Management Console(VCSMC)

Management Server ormanaged host

YesVeritas SF Manager 1.1 (orhigher) managed host


YesVeritas NetBackup 6.5 agentManagement Server ormanaged host

Yes—youmust install StorageFoundation for Windows 5.1first and then install theCommandCentralManagement Server ormanaged host

Veritas Storage Foundationfor Windows 5.1

Management Server ormanaged host with arraymanagement and NetAppdiscovery capabilities

NoCommandCentral ServiceManagement Server


NoCommandCentral ServiceMeter Controller


NoCommandCentral ServiceCollection Server


YesVeritas SF Manager 1.1 (orhigher) Management Server

Managed host

YesClusterManagementConsole6.0 Server

Managed host

YesSymantec License InventoryManager 4.0 Server

Managed host

YesVeritasNetBackup6.5ServerManaged host

System requirementsCo-existence of CommandCentral components with other Symantec products

46

Table 2-18 CommandCentral co-existence with other Symantec products(continued)



YesNetBackup Master/MediaServer 6.5.2

Managed host

NoVeritas Storage Foundation5.0 HP-UX 11.23 host

Managed host

47System requirementsCo-existence of CommandCentral components with other Symantec products

System requirementsCo-existence of CommandCentral components with other Symantec products

48

No longer supported


■ Hardware that is no longer supported

■ Reporting features that are no longer supported

■ Console features that are no longer supported

Hardware that is no longer supportedThe following hardware changes have been incorporated into CommandCentralStorage 5.1:

■ CommandCentral Storage no longer discovers Brocade switches through theBrocade API

Note: If you previously discovered Brocade switches through the Brocade API,you need to configure CommandCentral Storage to discover the switch usingSMI-S before you upgrade to CommandCentral 5.1. For more information, seethe CommandCentral Installation Guide and CommandCentral Hardware andSoftware Configuration Guide.

■ CommandCentral Storage no longer discovers McDATA switches through theEnterprise Fabric Connectivity Manager (EFCM)

Note: If you previously discovered McDATA switches through the EFCM, youneed to configure CommandCentral Storage to discover the switchusing SMI-Sbefore you upgrade to CommandCentral 5.1. For more information, see theCommandCentral Installation Guide and CommandCentral Hardware andSoftware Configuration Guide.

3Chapter

Reporting features that are no longer supportedThe following reporting changes have been incorporated into CommandCentralStorage 5.1:

■ The following reports were removed:

■ Change History Summary report

■ Change History Detail report

■ Global History report

Note: For change history capabilities, you can use CommandCentral StorageChange Manager.

Console features that are no longer supportedThe following Console changes have been incorporated into CommandCentralStorage 5.1:

■ In the Console header, the Veritas Backup Reporter link was removed

No longer supportedReporting features that are no longer supported

50

Software limitations


■ Install, uninstall, and upgrade limitations

■ Discovery and management limitations

■ Console and report limitations

■ 4.x Agent limitations

Install, uninstall, and upgrade limitationsThe following notes pertain to limitations youmight encounter when you install,uninstall, or upgrade CommandCentral 5.1.

NAT firewalls not supportedCommandCentral 5.1doesnot supportNAT (networkaddress translation) firewalls.NAT firewalls configured between managed hosts and the Management Servermay cause communication failures between the CORBA services running on themanaged host and the Central HALManager running on theManagement Server.

Discovery and management limitationsThe following notes pertain to discovery and management-related limitationsthat you might encounter when you use CommandCentral 5.1.

4Chapter

Reports show incorrect capacity for NetApp LUNs with spacereservation turned off

If thin (over) provisioning is used inNetAppMultiStore Virtual Systems, the totalLUN capacity displayed in the Storage Capacity reportsmight be greater than theactual logical capacity of the volume. This can occur when a LUN is created withspace reservation turned OFF.

This option allows the creation of LUNs that are larger than the volume capacity.

NetApp does not provide a way to identify the used capacity in a LUNwhen spacereservation is turned off. As a result, there may be inconsistencies whenCommandCentral Storage calculates LUN capacity.

For the same reason, the NASUsed value for a NetAppMultiStore Virtual Systemmight display as a negative number.

Example: On a 50 GB volume, create a LUN of 40 GB with space reservation OFF.At first, the Used Logical capacity is approximately zero but the LUN capacity is40 GB. If you subsequently create another 40 GB LUN with space reservation on,the resulting LUN capacity for the volume is 80 GB but the Used Logical capacityis—40GB. TheUsed Logical capacity will increase as youwrite data onto the LUNwith space reservation OFF or onto a file system in NAS mode.

NASUsed equalsUsedLogical capacityminusTotal LUNCapacity. In the example,this is 40 GB minus 80 GB, yielding the result of –40 GB.

Because reports ignore negative values, they will display NAS Used as zero andLUN capacity as 80 GB. Thus, in the Storage Capacity reports, the total LUNcapacity displayed will be greater than the actual logical capacity of the volume.

The problemdoes not occurwhen you are using other thin provisioning scenariossuch as FlexVols.

Volume layout not discovered for LDM-managed volumes mountedwithout a drive letter

CommandCentral does not discover the volume layout for volumes mountedwithout a drive letter on a Windows host when the volume manager type isMicrosoft LDM. As a result, the Volume Layout column is blank when you displaysuch volumes in the Console.

There is no workaround.

Software limitationsDiscovery and management limitations

52

Capacity not discovered for LDM-managedvolumeswithout file systemsCommandCentral does not discover the capacity for volumes on a Windows hostwhen the volumemanager type isMicrosoft LDM and the volume contains no filesystems. In this instance, the volume capacity displays incorrectly as zero.


Restoring Brocade switch configuration may fail when reboot requiredRestoring the switch configuration for a Brocade switch may fail if the restoredconfiguration requires a switch reboot. Toworkaround this issue, we recommendthat you initiate the switch restoration through a Brocade switch Telnet sessionwith the saved configuration file.

Unable to remove disk groups via HP EVA SSSU version 4.0 and 4.1Versions 4.0 and 4.1 of the HP EVA Storage System Scripting Utility (SSSU) CLIdo not remove disk groups when specified from the CommandCentral StorageConsole (Managing Summary>Array >EVA>DiskGroups >DestroyDiskGroup).

There is no workaround. Contact your HP support representative.

Detect Devices command applies only to objects that use devicemanagers

The CommandCentral Console Detect Devices command does not apply to objectsthat do not rely on device managers for their operation. For example, if you runthe Detect Devices command on Cisco switches using SNMP (Settings > Devices> Detect Devices), the Console does not output an error message.

Management operations not supported for EMC DMX-4 storage arrays(1404833)

CommandCentral Storage does not support performing management operationson EMC DMX-4 storage arrays. For example, you cannot mask or bind LUNs.

Discovery of RAID-6 and SSD devices not supported for EMC DMX-4storage arrays (1404832)

When CommandCentral Storage discovers information about your EMC DMX-4storage arrays, it does not discover information about RAID-6 and SSD devices.

53Software limitationsDiscovery and management limitations

Console and report limitationsThe following notes pertain to limitations that you might encounter when youuse the Console and its reports.

Reports ToolTips are truncated in FirefoxIn theCommandCentral Storage reports, columnheaders in tables displayToolTipswhenyoupoint yourmouse cursor over them. EachToolTip contains a descriptionfor the column.

In Firefox, the ToolTip text is truncated after about 70 characters, and an ellipsis(...) is substituted for the remaining text. This is a browser limitation. For moredetails, refer to the following Web site:

https://bugzilla.mozilla.org/show_bug.cgi?id=45375

4.x Agent limitationsThe following limitations apply to situations in which a CommandCentral 5.1Management Server manages version 4.x Agent hosts that have not yet beenupgraded.

Because of these limitations, we recommend that you give priority to upgradingAgent hosts that might be performing critical functions such as array discoveryandmanagement.These latter functionsarenotprovidedby themigrationexploreron the Management Server.

Refer to the CommandCentral Storage Migration Guide for additionalrecommendations.

Volumes and disk groups duplicatedWhen a CommandCentral Storage 4.x Agent host discovers volumes and diskgroups that aremanaged byVeritasVolumeManager 5.0 andpasses the discoverydata to a CommandCentral Storage 5.1 Management Server, the objects will beduplicated in the database after the Agent host is upgraded.

We recommend that you upgrade all such Agent hosts before you allow them tobe managed by a CommandCentral Storage 5.1 Management Server.

Incorrect data displayed for Oracle RAC applicationsThe version 5.1 CommandCentral Storage Console does not accurately representdata from Oracle RAC applications discovered by 4.x Agent hosts.

Software limitationsConsole and report limitations

54

https://bugzilla.mozilla.org/show_bug.cgi?id=45375

We recommend that you upgrade all such Agent hosts before you allow them tobe managed by a CommandCentral Storage 5.1 Management Server.

Data displayed for unsupported applicationsApplications no longer supported in version 5.1, such as Microsoft Exchange 5.5,will display in the version 5.1 CommandCentral Storage Console while the Agenthost is still running version 4.x. However, after the Agent host is upgraded toversion 5.1, the applications are no longer discovered.

Discovered objects deleted from the database after 24 hoursIf a 4.x Agent host cannot be contacted by the migration explorer for a 24-hourperiod, and if reverse DNS lookup from the CommandCentral Storage 5.1Management Server to the Agent host is properly set, then all objects discoveredby the Agent are marked as missing. User-defined annotations and groupassignments for the objects are lost after the purge period (by default, 24 hours).The purge period is set in the Server host’s registry.

JBOD disks that are visible to the Agent will also be deleted from the database,even if they are shared with other Agent hosts.

This is most likely to occur when the Agent host is stopped so that it can beupgraded to CommandCentral Storage 5.1 or when its network connection to theManagement Server is broken. If you stop theAgent host so that it canbeupgradedto 5.1, perform the upgrade within 24 hours. Otherwise, you will need to recreateuser-defined annotations and group assignments for discovered objects.

Workaround: Adjusting the 24-hour interval

You can increase the default 24-hour interval by editing the registry settings forthe SALToHALMigration explorer on the Server host. Edit theFailedRemotesProcessingIntervalInHours key to reset the interval.

See theCommandCentralAdministrator’sGuide for details about how to editHALexplorer registry settings. Note that registry entries should be edited only by aperson familiar with the registry settings and who understands their use andimpact.

Workaround: Preventing shared JBOD disks from being deleted

To prevent shared JBOD disks from being deleted from the database, edit themigration explorer cache on the Server host and delete SAL responses fromotherhosts that share the disks with the failed v4.x Agent host.

The migration explorer cache is a file namedRE-<remotehostname>-<explorername>-<TimeStamp>.xml in oneof the followingdefault locations:

55Software limitations4.x Agent limitations

Solaris—/var/VRTSccs/data/VRTShal/migration/ru_cache

Windows—\Program Files\CommandCentral Storage

Data\Data\HAL\migration\ru_cache

Some Veritas NetBackup objects not displayedSome Veritas NetBackup objects that are discovered by version 4.x Agent hosts,for example media changers and tape drives, are not displayed in the version 5.1Console if either of the following is true:

■ The Veritas NetBackup explorer writes data to a different directory than theHBA explorer for the same host

■ The HBA explorer gathers data after the Veritas NetBackup explorer andoverwrites the NetBackup data

Directory Usage, Directory Aging, and Stale Directories reports notavailable for 4.x Agent hosts

The following reports, which are based on data collected by theDataModule (DM),cannot display data for objects attached to 4.x Agent hosts: Directory Usage,Directory Aging, Stale Directories.

Data Module collection of all files not supported for 4.x Agent hosts4.x Agent hosts cannot be used to collect all files in a DM file scan. To do this, a5.1 managed host is required.

Data Module Importer does not support secure (https) connection to4.x Agent hosts

The version 5.1 DM Importer cannot establish an https connection with a 4.xAgent host. Secure communication is possible only between the Importer and a5.1 managed host.

Software limitations4.x Agent limitations

56

Known issues


■ Install, uninstall, and upgrade issues

■ Management Server and database issues

■ Console and report issues

■ Device and device configuration issues

■ Visualization issues

■ Monitoring issues

■ Discovery and management issues

■ User management issues

■ Data Module issues

Install, uninstall, and upgrade issuesThe following notes pertain to known issues that you might encounter when youinstall, uninstall, or upgrade CommandCentral Storage 5.1.

Error message about VRTSweb during upgrade on Windows (542244)If the Symantec Web Server (VRTSweb) is running when you perform an upgrade,you may receive the following error message:

Executed the command("C:\WINDOWS\system32\net.exe" start

VRTSweb). Return code (2)!!!

Workaround

5Chapter

If you encounter this error message, restart VRTSweb and its dependentservices—includingVeritasCommandCentralCommonLoginService (VRTScclogin)and Veritas CommandCentral Storage Web Engine (VRTSccsweb). Then click OKto continue the upgrade.

Alternatively, you can wait and restart VRTSweb and its dependent services afterthe upgrade completes.

Cannot connect to Veritas Enterprise Administrator Console afterinstalling managed host on Linux (865052)

If you install the CommandCentral managed host with array management on aLinuxhost that hasStorageFoundation5.0 installed, youwill not be able to connectto the host with the Java-based Veritas Enterprise Administrator Console.

Workaround

You have two options:

■ Upgrade the Linux host from Storage Foundation 5.0 to Storage Foundation5.0 MP1

■ If you cannot upgrade to Storage Foundation 5.0 MP1, contact SymantecTechnical Support for instructions on how to obtain the following patch:VRTSob-3.3.766.0-0.i686.rpm

Shared components restarted during CommandCentral install(1051607)

When you install CommandCentral 5.1, the Symantec Product AuthenticationService (VRTSat), the Symantec ProductAuthorization Service (VRTSaz), and theSymantec Private Branch Exchange (PBX) will be restarted. This may disrupt theperformance of other Symantec products that use these shared components.

Workaround

Before you install CommandCentral 5.1, stop all services for the other Symantecproducts that use these shared components.

Default agent password cannot be changed using CommandCentralproduct installer on UNIX (859670)

When you install the CommandCentral 5.1 managed host on UNIX, the productinstaller does not provide an option for changing the default agent password. Ifyou have changed the default password on theManagement Server, thismay leadto an authentication failure during the managed host install.

Known issuesInstall, uninstall, and upgrade issues

58

Workaround

Before you install a managed host, you have to reset the password on theManagement Server to thedefault password. Contact SymantecTechnical Supportfor the procedure to reset the password.

Managed host fails to install when shell on remote UNIX managed hostis configured as tcsh or csh (1170715)

Managed host installation fails if you try to install on a remote host on which thedefault shell for root is configured as tcsh or csh.

Workaround

You have two options. Rather than performing a remote installation, install themanaged host locally. Or, if youwant to install remotely, youmust set the defaultshell for root on the remote host to sh, bash, or ksh. To change the default shellconfiguration, edit /etc/passwd on the remote host to ensure that it is set to sh,bash, or ksh. After you change the default shell on the remote host, re-run theinstall.

Summary file not created during managed host installation on UNIX(1143138)

At the end of a managed host installation on a UNIX host, you see a messagesimilar to the following:

Installation log files, summary file, and response file are saved

at:

/opt/VRTS/install/logs/installccstor-qvChRb

However, the summary file is not created.

Workaround

Use the installation log files to view the summary of themanagedhost installation.

Erroneous reference to response file at end of Management Serverinstall on Solaris (1140473)

At the end of the Management Server install on a Solaris host, a message similarto the following displays:

Installation log files, summary file, and response file are saved

at:

59Known issuesInstall, uninstall, and upgrade issues

/opt/VRTS/install/logs/installccstor-qvChRb

The reference to the response file is erroneous. No such file is created when youinstall the Management Server. You should disregard this reference.

CommandCentral installations on Windows fail while configuring SICL(1171143)

Management Server and managed host installations on Windows hosts may failwhile configuring SICL. The installations may fail if you have multiple directorypaths defined in the TEMP environment variable.

Workaround

First, uninstall CommandCentral. Then, set a single directory path in the TEMPenvironment variable and re-run the installation.

Array and CIMVAIL explorers do not run after installing StorageFoundation 5.1 for Windows (1401940)

If you install Storage Foundation 5.1 for Windows on a host that includes eitherof the followingCommandCentral components, array andCIMVAIL explorersmaynot function properly:

■ Management Server

■ managed host with array management capabilities

If you want to install CommandCentral and Storage Foundation 5.1 for Windowson the samehost, install Storage Foundation 5.1 forWindows first and then installCommandCentral.

To identify if this problem impacts you, contact Symantec Technical Support.

www.symantec.com/support

CPI warning displays during reconfiguration of an HP-UX managedhost (1439576)

When you reconfigure an HP-UX managed host by running the installccstorcommand from the /opt/VRTS/install directory, the following message maydisplay:

CPI WARNING V-9-0-0 Cannot determine VRTSccsta depot version on media

You can ignore this message and proceed with reconfiguration of the managedhost.


60

http://www.symantec.com/support

During managed host upgrade from 4.x to 5.1, VRTSob package failsto uninstall (1407579)

When you upgrade the 4.x managed host to 5.1, the installer may display thefollowing message:

Removal of <VRTSob> failed.

Even though the removal of the package fails, the upgrade completes successfully.You can safely ignore this message.

Mistyped Management Server name cannot be corrected in theWindows managed host installer (1449432)

Whenyou install themanagedhost onWindows, in theTargetManagementServerpanel of the installer, if you type an incorrect host name or IP address for theManagement Server, the installer may display the following message:

The Symantec Private Branch Exchange (PBX) is not running on the

Management Sever host: <hostname>. This condition will prevent

CommandCentral Storage from functioning properly. You must fix this

issue before proceeding.

To correct this problem, the installer prompts you to either retry the connectionto theManagement Server or to cancel the installation. You donot have the optionto retype the host name or IP address of theManagement Server. If this happens,you need to click Cancel and restart the installation.

Error message appears during uninstall of the Management Serverfrom a Windows host (1432751)

When you uninstall the Management Server from a Windows host, the followingerror message may appear:

ERROR: RemoveDirectory(E:\ccs_nondef\CommandCentral Storage\Web

Engine\spc\tasks) failed.

Error=0x00000020!!!

The error message appears because there is an active connection to theCommandCentral Console.

Before you proceed with the uninstall, log out of the Console and close your webbrowser. Then, click OK to proceed with the uninstall.


Authentication Service fails to upgrade during Management Serverinstallation on Windows (1427441)

When you install the CommandCentral Management Server on Windows, theinstaller may detect that a previous version of the Symantec ProductAuthentication Service exists on the host. During installation of theManagementServer, the installer upgrades the Authentication Service. If the previous versionof the Authentication Service was installed in Client mode, upgrade of theAuthentication Service fails and the CommandCentral installer closes with anerror.

Workaround

To correct the issue, do one of the following:

■ If no other Symantec products are using the Authentication Service, uninstallit before installing the Management Server. To remove the AuthenticationService, use Windows’ Add or Remove Programs tool.

■ If there are other Symantec products using the Authentication Service, runthe following command:msiexec /qn /i "VERITAS Authentication Service.msi" /l*v "At.log"

INSTALLDIR="C:\Program Files\VERITAS\Security"

UUIDINSTALLDIR="C:\Program Files\Veritas" INSTALLLEVEL=2

ADDLOCAL=Server REINSTALL=Client REINSTALLMODE=vomus BROKERMODE=rab

PASSWORD1=Vxadmin PASSWORD2=Vxadmin STARTSERVICE=NO DOUPGRADE=YES

REBOOT=ReallySuppress

where the values of INSTALLDIR and UUIDINSTALLDIR can be differentdepending on the default and non-default install location of the existing ATclient.

VRTSWeb folder remains after uninstalling the Management Serveron Windows (1292780)

After you uninstall the Management Server from a Windows host, the VRTSWebfolder remains in the directory in which you installed CommandCentral. You cansafely delete this folder.

Error message about inability to copy files to /var/tmp displays duringinstall (1438157)

When you install the Management Server or managed host on UNIX, an errormessage similar to the following may display:


62

CPI ERROR V-9-0-0 Cannot copy ./Support/platform to

/var/tmp/installccstor-Unique_ID on hostname installccstor log files

are saved at /opt/VRTS/install/logs/installccstor-Unique_ID

The error message displays because there is insufficient space in /var/tmp

Before you proceed with installation, create more space in /var/tmp

HAL configuration fails during managed host install on AIX 5.3 TL06or TL07 (1431432)

When you install the managed host on an AIX 5.3 host with Technology Level 6(TL06) or Technology Level 7 (TL07), configuration of the Hardware AbstractionLayer (HAL) may fail with the following error message:

System error: bad address

Workaround

For AIX 5.3 TL06, install the following patch: IZ05077

For AIX 5.3 TL07, install the following patch: IZ06832

After you install thepatch, use the following command to reconfigure themanagedhost:

./installccstor -configure

For more information about reconfiguring the managed host, see theCommandCentral Installation Guide.

Windows’ Service Control Manager displays error when selecting theSymantec Product Authentication Service (1368976)

After you upgrade the Management Server from 5.0 to 5.1, in Windows’ ServiceControl Manager, when you click the Symantec Product Authentication Service,the following message displays:

Configuration Manager: The specified device instance handle does not

correspond to a present device

You can ignore this message.

installccstor command lists unsupported options (1402292)On a UNIX managed host, when you run the installccstor command from/opt/VRTS/istall the following usage message displays:


The -configure, -license, or -security option is required when

installccstor is not run from the install media.

This message is incorrect. The -license and -security options are not requiredand are not supported.

Incorrect folder appears when clicking View ReadMe in Windowsinstaller (1449592)

When you install or upgrade a managed host on Windows, in the final panel ofthe installation wizard, if you click the View ReadMe link, an incorrect folderappears.

Workaround

Select (check) the View ReadMe checkbox and click Finish. The correct READMEfile displays.

Managed host silent install fails with message about inability to openlog file at line 966 (1363772)

When you perform a silent install of themanaged host onUNIX, installationmayfail with the following message:

pl_log cannot open <location of log> at CPI/common/misc.pl line 966

Thismessagedisplays if youomitted the-responsefileoption fromthecommand.

For more information about managed host silent installs, see the .

In Push Install Utility, Add IP button not enabled after pasting hostname (1423059)

In the Push Install Utility, in the Select Hosts for Managing Installations dialogbox, if you use your mouse to paste the name or IP address of a host in the HostName or IP Address field, the Push Install Utility does not enable the Add IPbutton.

Workaround

In the Host Name or IP Address field, either paste the text using your keyboardor, if you already used yourmouse to paste the text, press a key on your keyboard.The Push Install Utility enables the button.


64

Data and configuration files remain after uninstalling the managedhost from a Linux host (1397051)

If you uninstall the managed host from a Linux host and do not choose to savedata and configuration files, after the managed host uninstalls, files remain inthe /opt/VRTSccs folder. You can safely delete these files.

NetBackup 6.5 does not run properly after installing CommandCentral5.1 (1407023)

After you install the CommandCentral 5.1 Management Server or managed hoston a host that includes NetBackup 6.5, NetBackup does not run properly.

Workaround

Restart NetBackup services.

Error message appears when uninstalling Symantec ProductAuthentication Service on a Windows managed host (1368709)

On a Windows host, after you upgrade a CommandCentral managed host witharray management and NetApp unified storage capabilities to version 5.1, if youtry to uninstall the Symantec ProductAuthentication Service, the following errormessage appears:

Another application has exclusive access to file -

"Install_directory\Security\Authentication\systemprofile\certstore\keystore\KeyStore.lock

file"

The Authentication Service was used by your previous version of the managedhost. The 5.1 managed host does not depend on the Authentication Service.

If you need to uninstall the Authentication Service, then you need to uninstallthe managed host first.

Array explorers stop after upgrading Linux managed host to 5.1(1318748)

After you upgrade a Linux managed host to 5.1, the ArrayExplorers process maystop.

Workaround

Restart the ArrayExplorers process.


To restart the ArrayExplorers process

1 On the managed host, open an operating system console and log in as root.

2 Change to the Hardware Abstraction Layer bin directory. By default, thedirectory is:

/opt/VRTSccs/VRTShal/bin

3 Type the following command:

halagentcfg start-process -p ArrayExplorers

The ArrayExplorers process starts.

Symantec Production Authorization Service stops after uninstallingCommandCentral from a Windows host (1465585)

When you uninstall CommandCentral 5.1 from a Windows host, the SymantecProduction Authorization Service stops.

Workaround

If there are other Symantec products that use the Authorization Service, openWindows Service Control Manager and start the Symantec ProductionAuthorization Service.

Management Server and database issuesThe following notes pertain to known issues that you might encounter with theManagement Server or database.

Management tasks not terminated when Management Server can nolonger contact managed host (604446)

If amanagement task (for example, a create LUN operation) is in process, and theManagement Server loses contact with the managed host, the process may takeup to 60 minutes to terminate.

Operations fail with authentication error on Windows 2003 64-bitmanaged host (1042801)

When you install the CommandCentral managed host on a Windows 2003 64-bithost, a credential store for the Authentication Service (AT) creates to a defaultdirectory. If a version of the sharedAT runtime installs on the samehost, a second

Known issuesManagement Server and database issues

66

credential store creates to a different directory. As a result, all subsequentoperations that require Hardware Abstraction Layer (HAL) AT credentials fail.

Workaround

Re-authenticate the HAL account on the managed host.

To re-authenticate the HAL account on the managed host

1 On the managed host, open an operating system console.

2 At the command prompt, type the following commands:

lhm --stop service

halvssat setuptrust --broker MS host --securitylevel high

When prompted to confirm, type y

halvssat authenticate --domain vx:HAL --prplname Agent --password

agent password --broker MS host

lhm --start service

You may now restart local HAL processes or issue new HAL commands.

Shared components stop-start order (856750)If the Symantec Private Branch Exchange (PBX) is stopped and restarted, thenthe Symantec Product Authentication and Authorization Services need to bestopped and restarted in the correct order.

Here is the proper stop-start order for these shared processes:

1. Stop the Authorization Service.

2. Stop the Authentication Service.

3. Stop PBX.

4. Restart PBX.

5. Restart the Authentication Service.

6. Restart the Authorization Service.

Status of user-created HAL process does not display when runningvxccs status (1437246)

After you create a new Hardware Abstraction Layer (HAL) process—for example,a processunderwhichyouwant to runanewexplorer—whenyou run the commandvxccs status, the status of that new process does not display.

67Known issuesManagement Server and database issues

Workaround

Use the command halagentcfg list-processes to verify the status of theuser-created process.

To use the command halagentcfg list-processes

1 OntheManagementServer ormanagedhost onwhichyoucreated theprocess,open an operating system console and log in as root (UNIX) or as a user withadministrator-level privileges (Windows).

2 Change to the Hardware Abstraction Layer (HAL) bin directory. By default,the directory is:

■ HP-UX, Linux, Solaris: /opt/VRTSccs/VRTShal/bin

■ AIX: /opt/VRTShal/bin

■ Windows: \Program Files\VERITAS\CommandCentral Storage\HAL\bin

3 To see the status of HAL processes, type the following command:

halagentcfg list-processes

The status of the processes display.

Incorrect count of managed host licenses in use (1453145)When you view the Licenses Pane (Settings > Management Server > Licenses), inthe Licenses table, the license type "Managed Hosts for CC" may display anincorrect count of the "Licenses in Use."

This occurs when the count for any two of the following are the same:

■ The number of 5.x managed hosts

■ The number of 4.x managed hosts

■ The number of ESX servers

For example, the issue occurs if you have same number of 5.x managed hosts asyou do 4.x managed hosts.

Hotfix required for a 5.1 Management Server that manages 4.xmanaged hosts (1459081)

After you upgrade yourManagement Server to 5.1, if you have 4.xmanaged hoststhat report to that 5.1 Management Server, you need to apply a hotfix to theManagement Server so that it can update the data collected from those 4.xmanaged hosts.

Contact Symantec Technical Support to obtain the hotfix.

Known issuesManagement Server and database issues

68

Array and CIMVAIL log files consume large amount of disk space(1458508)

You may notice a decrease in disk space due to the array and CIMVAIL log filesgrowing to large sizes. This occurs if you change the debug level of the array andCIMVAIL explorers to a level higher than 1.

Workaround

Do the following:

■ Delete the log files

■ Change the explorer’s debug levels to either 0 or 1For information about configuring explorers, see the CommandCentralAdministrator’s Guide.

CommandCentral database creates large temporary files (1446560)As you use CommandCentral, the CommandCentral database creates temporaryfiles inwhich it stores temporary data. TheCommandCentral databasemay createlarge temporary files if both CommandCentral Storage and CommandCentralStorage Change Manager are enabled.

For more information about the temporary files that CommandCentral databasecreates, see the CommandCentral Administrator’s Guide.

Console and report issuesThe following notes pertain to known issues that you might encounter when youuse the CommandCentral Storage Console and reports.

LUN capacity displayed as "Assigned to VM" for Sun VM disk slice(637435)

If a Sun disk slice is created on a LUN and the disk slice is given to Sun VolumeManager, then the Storage Consumption reports list the entire LUN capacity as"Assigned To VM"—whether or not other slices are used by file systems ordatabases.

The assignment capacity is the LUN capacity and not the actual usage capacityof a slice. The assignment also assumes single ownership—meaning that a devicehandle can be owned by a disk group, a file system, or a database. If the disk sliceis used bymore than one source, then the report categorizes it asVM, a file system,or a database in the order given.

69Known issuesConsole and report issues

Example: Three Sun disk slices (A, B and C) are created, each of 1 GB on a LUN of3 GB. Slice A is used for Volume creation, sliced is used B for directly creating afile system, and slice C is used for directly creating a tablespace. The StorageConsumption reports will display the following:

■ 3 GB Assigned to VM

■ 0 GB Directly Assigned to File Systems

■ 0 GB Directly Assigned to Databases

Emailed report does not reflect column sorting (615330)If you sort a report on any column other than the default sorted column and thensend the report by email, the sorting is not preserved. Only the default sorting isreflected in the emailed report.


Incorrect name displayed for file systems on unmounted or unnamedvolumes (864757)

When a managed host has unmounted and/or unnamed VxVM volumes thatcontain file systems, then the file systems’ names might display incorrectly inthe CommandCentral Storage Console. Specifically, the error occurs in the host'sobject view, Volumes tab, Volumes table, File System column.

The name displayed might be the name of the volume itself, or it might be thestring Volume-GUID on fully-qualified-managed-host-name.

Example:

\?\Volume{75a7abe6-ff5a-4398-8de7-a99b26306fe0}\ on

host1.example.com


Dialogs overwritten when new dialogs are opened (606871)If a Console user launches a dialog (either a wizard or a standalone dialog box)while another dialog is already open, the second dialog overwrites the first one.

Workaround

Ensure that all dialogs are closed before opening a new one.

Known issuesConsole and report issues

70

Mismatch between time on Management Server and time displayed inscheduling dialogs (851525)

The Schedule Task controls in dialog windows display date and time valuesaccording to the clock on the local computer. However, the scheduling of tasks isactually based on the clock on the CommandCentral Management Server. If theConsole user is in a different time zone from the Management Server, therefore,the time displayed might not match the time on the Management Server.

Workaround

Be sure to specify dates and times with regard to the Management Server host,not the local client.

Port Bundle Builder Tool displays only one fabric (629557)The Port Bundle Builder tool is a feature that involves two switches that are E/TEported together. The Port Bundle Builder tool should list E/TE ports, even if theirAdmin status is down. Upon selecting the E/TE port pairs to be bundled, theCommandCentral Storage Port Bundle creation wizard should first complete theoperation on the first switch, and then on the second. Both ports should comeonline. If the operation fails, an error message is returned.

Currently the Port Bundle creation wizard only displays the E/TE port that isOnline. Upon selecting the E/TE port pairs to be bundled, the switch performs aport bundle creation for the first switch. The ports go Offline on the switch andthe CommandCentral Storage GUI stops. It does not complete the operation onthe second switch. This results in an incomplete operation. Since the ports aredown, there is no other way to complete the Port Bundle operation usingCommandCentral Storage.

There is currently noworkaround.Donot use thePort Bundle creation/edit featurein 5.1.

The Topology Map’s Print Preview displays a blank page (1206846)TheTopologyMap's Print Previewdisplays ablankpage in the following situations:

■ In Internet Explorer, when you open the Topology Map in a new browserwindow and click the Print Preview icon

■ In Firefox, when you click the Print Preview icon either from the Console orafter you open the Topology Map in a new browser window

Workaround

If you want to print the Topology Map in Internet Explorer, do either of thefollowing:


■ Without opening the Topology Map in a new browser window, click PrintPreview

■ Save the Topology Map as an image and then print the saved image

If you want to print the Topology Map in Firefox, you can save the Topology Mapas an image and then print the saved image.

For more information about saving the Topology Map as an image, see theCommandCentral Storage User’s Guide.

Table filter does not disable in a custom report (1445762)If you enable a table filter in a custom report and then try to disable that filter,the filter does not disable.

Workaround

Uncheck the checkbox on which the filter is set.

To uncheck the checkbox on which the filter is set

1 In the Console, click Reporting > Custom.

2 In the Custom Reports table, click the name of the report on which you wantto remove the filter.

3 In the table that has the filter set, click the Filter Table icon.

4 In the Filter Table dialog box, select (uncheck) the checkbox(es) for whichyou want to remove the filter.

5 Click OK.

The filter disables.

Custom report created from File or Directory Aging Summary reportdoes not display data (1435770)

After you customize the File Aging Summary report or the Directory AgingSummary report, when you view the customreport, someof the graphs and tableswithin the custom report may not display data.


Some reports continue to include data from an ESX server whose deviceconfiguration was removed (1452265)

After you remove thedevice configuration for anESXserver thatCommandCentraldiscovers through VI-SDK, the Host Virtualization Summary report and the


72

Storage Capacity Summary report continue to include data from that ESX serveruntil the database purges the data. This period typically lasts 7 days.

The Switch Port Performance Detail report does not display data fora Cisco switch (1435130)

For Cisco switches, when you navigate to the Switch Port Performance Detailreport as follows, the charts do not display data: Managing > SAN > Switches >click a Cisco switch > Reporting > Switch Port Performance Detail Report.

Workaround

Access the report from the Reporting pane.

To access the report from the Reporting pane

1 In the Console, click Reporting > Performance > Switch Port Performance.

2 In the Switch Port Performance Summary report, click the name of the Ciscoswitch.

The Switch Port Performance Detail report appears.

Total values do not display for tables in ad hoc reports (1446963)In an ad hoc report that contains a table, if youmodify the table’s settings or filterthe table, after the table refreshes, total values does not display in the table’sfooter.


Favorites link for the Host Editor no longer works (1456338)If you had a favorites link for the Host Editor in your previous version ofCommandCentral Storage, the link no longer works after you upgrade toCommandCentral 5.1. The link no longer works because the Host Editor wasreplaced by the Pattern Based Correlation Wizard and the CSV Based CorrelationWizard. You should edit your favorites to remove the link to the Host Editor.

Array Storage Summary report displays incorrect capacity for IBMDS6000 and DS8000 storage arrays (1437378)

When you view the Overview pane for a IBM DS6000 or DS8000 storage array, inthe Array Storage Summary report, the total capacity of the extent pool may notequal the total physical configured capacity. This occurs due to themultiple levelsof virtualization involved in IBM DS storage arrays.


Virtualization Server Claimed Capacity attribute displays incorrectvalue (1447060)

When you view a virtualization server’s Attributes pane (Managing > Hosts andHBAs > Virtualization Servers > click a server > Attributes), the Attributes tableincludes the attribute "Virtualization Server Claimed Capacity (GB)." The valueof this attribute always displays "0."

Workaround

If you want to view a virtualization server’s claimed capacity, scope the HostVirtualization Summary report (Reporting > Storage >Host Virtualization) to thevirtualization server.

For Cisco switches, the Switch Port Usage Summary report does notdisplay port count for unenclosed devices and unidentified adapters(1436270)

If youhaveCisco switches that are connected to anydevices that CommandCentralidentifies as an unenclosed device or unidentified adapter, when you scope theSwitch PortUsage Summary report to that switch, the count of those connectionsdo not display in the Distribution of Used Switch Ports by Connection graph.

Workaround

Display the Switch Port Usage Detail report. The connections display in the UsedSwitch Ports table.

WWN’s of zone members do not display in Zone Builder tool (1440661)When you use the Zone Builder to create or edit a zone, in the Confirm Selectionpanel, the WWN column does not display any values.


Email addresses for user accounts no longer appear after upgrade(1430275)

If you configured email addresses for user accounts in CommandCentral Storage5.0MP1 that are not part of the cc_users domain—for example, NT or LDAP—afteryou upgrade to 5.1, those email addresses are no longer associated with the useraccounts.

To restore the email addresses, edit the user account.


74

Value does not display for the CSV delimiter setting (1450085)When you navigate to Settings > Management Server > Web Engine Settings, avalue may not display for CSV delimiter. Even though a value does not display, avalue is set for the CSVdelimiter—youwill not experience any problems exportingdata to a CSV file. If you edit any of the Web Engine settings, the value for theCSV delimiter updates in the Web Engine Settings pane.

After upgrade, some pages in the Console take a long time to load(1457768)

After you upgrade from CommandCentral Storage 5.0 MP1 to 5.1, some pages intheConsolemay take a long time to load. For example, youmaynotice this problemwhen you navigate to a host’s Storage pane and when you navigate to the HostConsumption Detail report.

Workaround

This issue is corrected in a hotfix. Contact Symantec Technical Support to obtainthe hotfix.

Device and device configuration issuesThe following notes pertain to known issues that you might encounter withsupported devices and device configuration in CommandCentral Storage 5.1.

Device configuration name does not change after modification (853400)The Console’ Edit Device Configuration command does not change the deviceconfiguration name.

Workaround

First remove the device manager, then remove the arrays managed by the devicemanager. Then re-add the device.

Do not use an existing IP address for array configuration (582094)The array configuration dialogs do not check whether a specified IP address isalready in use.When configuring a newarray or editing an existing configuration,care should be taken not to specify an IP address that is already in use for aconfigured array.

75Known issuesDevice and device configuration issues

Error message displays when configuring an array explorer from a 5.0or 5.0 MP1 managed host (1379639)

For 5.0 or 5.0MP1managedhostswith arraymanagement capabilities that reportto a 5.1 Management Server, if you attempt to configure an array explorer thatruns on that managed host, the following error message may display:

Property ChangeDetectionIntervalInMins is not supported in device

information (V-31-1052-386)

We recommend that you upgrade this managed host to 5.1.

Change detection does not work for a Symmetrix explorer that runson a Linux managed host (1386606)

If you enable change detection for a Symmetrix explorer that runs on a Linuxmanaged host, the explorer does not detect near real-time changes to EMCSymmetrix storage arrays.


Product name and version do not display for Sybase 15 instance(1439468)

When you view the Overview pane for a Sybase 15 instance, the product nameand version of that instancemaynot appear. This occurswhen the instance’sASEdirectory name andOCS directory namewere either not supplied or were enteredincorrectly when you configured the instance for discovery.

Workaround

Edit the device’s configuration to supply the instance’s ASE directory name andOCS directory name.

For more information about editing a device’s configuration, see theCommandCentral Administrator’s Guide.

Note: Enter the directory name without the trailing slash. For example,/xyz/ASE-15_0/bin/ is incorrect where as /xyz/ASE-15_0/bin is correct.

Visualization issuesThe following notes pertain to known issues related to the visualization of yourstorage network.

Known issuesVisualization issues

76

Incorrect LUN capacity estimates when CX Meta LUNs created frommixed RAID groups (1016679)

If you create a CX Meta LUN from mixed RAID groups, the LUN is referred to asa mixed Meta. Due to an issue in CommandCentral Storage 5.1, such mixed MetaLUNs appear within both RAID groups. This causes incorrect LUN capacityestimates for both RAID groups. The LUN capacity total in both RAID groups willbe higher than expected.

There is no workaround. If the production environment contains mixed MetaLUNs, then you should be aware that such a discrepancy in existing LUN capacitycan occur.

Attributes and group memberships not migrated for Hitachi RAIDgroups (859638)

ForRAIDgroupsonHitachi arrays, user-definedattributes andgroupmembershipsare not migrated from version 4.x to version 5.1. You will need to redefine theseitems after migrating.

Incomplete information displayed for newly discovered objects(865845)

When an object is discovered for the first time, there is a brief period of timeduring which the CommandCentral Storage Console displays incompleteinformation about the object. The incomplete information is reflected in the objectview and also may be reflected in reports and other views where informationabout multiple objects is rolled up. Currently there is no indication that theinformation being displayed is incomplete.

Duplicate device handles appear for an ESX server after migratingdiscovery from SMI-S to VI SDK (1451189)

If you migrate discovery of an ESX server from SMI-S to VI SDK and you have amanaged host installed on the ESX server, when you view the ESX server’s devicehandles, duplicate device handles appear.

Workaround

If you remove the managed host from the ESX server, CommandCentral Storageremoves the duplicate device handles once the database purge runs.

77Known issuesVisualization issues

Physical memory and number of processors display as 0 for a NetAppunified storage device (1449596)

Whenyouview theOverviewpane for aNetAppunified storagedevice, thephysicalmemory size and number of processors incorrectly display as 0.


Incorrect icons appear for virtualization servers and NetApp unifiedstorage devices (1453274)

When you view the Configured Devices pane, in the Object column, the icons forvirtualization servers and NetApp unified storage devices are incorrect. Forvirtualization servers, the host icon displays and for NetApp unified storagedevices, the storage array icon displays.

If you want to find devices based on their device type, you can sort the explorercolumn.

Inaccurate port names display for FL ports (1450141)If a switch has FL port connections that are connected to multiple ports, whenyou view the switch’s Connectivity pane, the switch port names are inaccurate.

Workaround

To identify the switch port, in the Connectivity pane, view the WWN column.

Monitoring issuesThe following issues relate to monitoring your storage network.

Monitoring data not displayed for SnapMirror destination (621024)The CommandCentral Storage Console may fail to display monitoring data for aNetApp volume that is a destination for SnapMirror operations.

This happens because NetApp SnapMirror monitoring requires that theCommandCentral Storage managed host be capable of resolving the host nameof the destination Storage System.

Workaround

To enable monitoring for the SnapMirror destination volume, perform thefollowing operation on the managed host that is discovering the destinationStorage System:

Known issuesMonitoring issues

78

UNIX: Edit the file /etc/resolv.conf and add the domainnameof the destinationStorage System to the search line.

Example: search mynetappdomain.example.com

Windows: From the Control Panel, go to Network Connections. In the AdvancedIP properties window, add the domain name of the destination Storage System tothe DNS suffixes list.

Monitoring status not available for ESX server (1122802)In the CommandCentral Storage Console, the host status details of an ESX serverdoes not display in the monitoring views.


Monitoring of McDATA switch is not automatically enabled after theswitch is added to CommandCentral Storage (1159617)

In the CommandCentral Storage Console, in the Monitoring pane, the collectortable does not show any values for a newly added McDATA switch.

Workaround

You need to restart Alarm Service after adding the McDATA switch toCommandCentral Storage.OnWindows, go toServiceControlManager and restartVeritas CommandCentral Storage Alarm Service. On Solaris, use the/opt/VRTS/bin/vxccs command to stop and start vxasd process.

Alerts about CommandCentral Storage processes may display afterreboot or upgrade (1183630)

When you shutdown your Management Server or managed host—for example, toreboot or upgrade—the following may occur:

■ If CommandCentral Storage processes stop before the Simple InstrumentationCollection Layer (SICL) stops, an alert displays in the Console for eachCommandCentral Storage process that is not running.For example, the following alert may display: CommandCentral process not

running: vxtrapd

After SICL shuts down, the alert may display with a status of Unknown.

■ When SICL shuts down, an alert displays in the Console to inform you thatSICL is disconnected.For example, the following alertmay display: SICL (CC Storage monitoring

service) on host myhost.example.com is Disconnected.

79Known issuesMonitoring issues

If you receive these alerts during a planned shutdownof yourManagement Serveror managed host, you can reset the alerts to remove them from the Console.

For more information about resetting alerts, see the CommandCentralAdministrator’s Guide.

Multiple alerts display for offline Veritas Cluster Server service group(1212311)

If you install the CommandCentral managed host on more than one node withinaVeritas Cluster Server cluster that hosts a service group and that service group’sstate changes toOFFLINE,multiple alerts for the offline service groupwill displayin the CommandCentral Storage Console.

If you receivemultiple alerts about an offlineVeritas Cluster Server service group,you can reset the multiple alerts to remove them from the Console.

For more information about resetting alerts, see the CommandCentralAdministrator’s Guide.

After upgrade to 5.1, alerts display in the Console as unknown(1241474)

After youupgrade theManagement Server from5.0MP1 to 5.1, someof the activealerts that were present in MP1 at the time that you upgraded will display in theConsole as unknown. This is caused by a lag in the monitoring interval for eachmonitored object. The alerts will refresh 2 to 6 hours after the upgrade.

Alerts display for devices for which monitoring is disabled (1300864)If youdisablemonitoring for a device (for example, a storage array) that amanagedhost discovers, and a policy exists for a child object of that device (for example, aLUN), alerts will generate for that device, even though you disabled monitoring.

Workaround

On themanagedhost, restart the Simple InstrumentationCollectionLayer (SICL).


80

To restart SICL

1 On the managed host, open an operating system console and log on as root(UNIX) or as a user with administrator-level privileges (Windows).

2 Change to the directory where the script vxccs resides. By default, this is:

UNIX: /opt/VRTSccs/VRTSccsta/bin

Windows: /Program Files/Veritas/CommandCentral

Storage/Support/Tools/Vxccs

3 Type the following command to stop SICL:

UNIX: vxccs stop vxsicld

Windows: vxccs stop VRTSsicls

4 Type the following command to start SICL:

UNIX: vxccs start vxsicld

Windows: vxccs start VRTSsicls

5 Do the following to verify that SICL is running:

UNIX: Type the following command: vxccs status vxsicld

Windows:Use theWindowsServiceControlManager to verify that theprocessVeritas CommandCentral Storage SICL is STARTED.

The managed host now has an updating status of monitoring for the devicesthat it discovers.

Numeric collector "Hitachi DKCCSW Moderate Count" does not displaya value (1439498)

Whenyouviewmonitoring information for aHitachi storage array, in theNumericCollectors table, the collector "Hitachi DKCCSWModerate Count"maynot displaya value. This collector determines the number of Hitachi disk controllers that areexperiencing moderate internal bus errors.


Monitoring not available for Cisco switches configured in 5.1 (1435097)If you configure a Cisco switch for discovery in CommandCentral 5.1, monitoringmay not be available for that switch. This does not affect Cisco switches that wereconfigured in previous versions of CommandCentral Storage.

81Known issuesMonitoring issues

To find out of monitoring is available for a Cisco switch, in the Cisco switch’sOverview pane, click Monitoring. If monitoring is not available, the followingmessage displays:

Monitoring is not available for this object

To correct the problem, you can try to delete the configuration and then configurethe switch again.

Monitoring not available for McDATA switches discovered throughSMI-S after upgrading to 5.1 (1447971)

After you upgrade from CommandCentral 5.x to 5.1, monitoring is not availablefor McDATA switches that you configured for discovery through SMI-S in theprevious version of CommandCentral Storage.

To find out of monitoring is not available for a McDATA switch, in the McDATAswitch’s Overview pane, click Monitoring. If monitoring is not available, thefollowing message displays:

Monitoring is not available for this object

Workaround

Please contact Symantec Technical Support.

SNMP based monitoring of arrays and switches using non-defaultcommunity name does not work (1452092)

SNMPbasedmonitoring of arrays and switches doesnotwork inCommandCentralStorage 5.1 if you do either of the following:

■ Configure SNMP based monitoring by creating the attributeXt_SnmpReadCommunity (a non-default community name)

■ Modify SNMP based monitoring by changing the community name

If you configured SNMP based monitoring in a previous version ofCommandCentral Storage and do not modify the community name after youupgrade, monitoring continues to work in 5.1.


Note: This does not affect Cisco switches.


82

Incorrect or no values display for state collectors "Device Status" and"HitachiDfArrayStatus" (1439527)

When you view monitoring information for a Hitachi storage array, in the StateCollectors table, the collectors "Device Status" and "HitachiDfArrayStatus" maydisplay incorrect values or they may not display a value.


Resetting alerts does not always clear alerts (1456719)When you reset alerts, the Console may not always clear the alerts. When thishappens, the Console may display a blank screen.

Exception displays when adding a trap notification to a global policy(1454720)

When you try to add a trap notification to a global policy, an exception displaysin the Console.

"Port Speed" numeric collector displays incorrect value for a Ciscoswitch (1435104)

When you view a Cisco switch’s Monitoring pane, the value for the numericcollector "Port Speed" does notmatch the unit. For example, the valuemaydisplayas 2,000,000,000 when the value should display as 2.

Some numeric collectors display incorrect values for a Hitachi storagearray (1439495)

WhenyouviewaHitachi storagearray’sMonitoringpane, thevalue for "DKU/DKC"numeric collectors (for example, "Hitachi DKC Battery No Error Count") maydisplay as 0 when they should display as 1. When the wrong values display, itoccurs for short durations—the values immediately switch back to the correctvalues.

Discovery and management issuesThe following issues relate to discovery and management.

83Known issuesDiscovery and management issues

Disk state not discovered (859207)On UNIX hosts, CommandCentral does not discover the state of disks in VxVMvolumes.

Incomplete discovery when two versions of DB2 are on the same host(605860)

When two different versions of DB2 are installed on the same host,CommandCentral will sometimes display incomplete information about the DB2objects on the host.

HP EVA: Disabling discovery of Management Appliance does not disablediscovery of arrays (614523)

If you edit the configuration for a Management Appliance host that manages HPEVA arrays and deselect Enable Discovery, the Management Appliance changesto the inactive state. However, CommandCentral continues to discover the arraysit manages.

Workaround

Disable discovery for each managed array individually.

Manually configured database instances not coming up automaticallyafter upgrade (900677)

After you upgrade a Solaris managed host to 5.1, the CommandCentral StorageConsole does not display (on the Settings tab) configuration settings for theOracle,DB2 and Sybase explorers if they were configured manually in 4.x.

Workaround

Manually configure Oracle, DB2, and Sybase instances with the appropriatecredentials and save the configuration.

ESX Server no longer discovered after modifying shared storage pool(1184188)

When ESX servers are sharing the same storage pool and that storage pool iseithermodified or deleted on one of the servers, the CIMOMson other ESX serverswill hangwhen they are trying to access the storage pool. Youwill know the otherESX servers arehangingwhenyou run theVMware explorer and it cannot discoverthose ESX servers.

Known issuesDiscovery and management issues

84

Workaround

Youwill need to refresh the storage pool from the other ESX servers usingVMwareVI Client GUI.

To refresh the ESX server using the VMware VI Client GUI

◆ From the VMware VI Client menu click ESX Server > Configuration >Hardware/Storage > Refresh

Discovery failure for storage arrays configured as SMI-S managedarrays (1185347)

Device discovery of SMI-S managed arrays may fail if the operational state of thearray is in either an attention or a failed state.

To determine an array's state

1 Click on an array to go to the array's overview pane.

2 Click the Monitoring tab.

3 Under State Collectors, check the "OperationalState" collector value.

There is no workaround for this issue.

Windows Logical Manager not discovered on Windows Server 2008host that includes Veritas Volume Manager (1402934)

If a Windows Server 2008 host in your storage network includes both WindowsLogical DiskManager andVeritasVolumeManager 5.1, CommandCentral Storagewill not discover the Windows Logical Disk Manager instance.

Consumption information missing for shares mounted on a Windowshost (1169224)

CommandCentral does not discover consumption information for sharesmountedon a Windows host. Because of this, the following occurs in the Console:

■ In the StorageCapacityDetail report, the Shares/Exports table does not displayvalues for consumer and consumer mount points when the share is mountedon a Windows host.

■ In a hosts’ overviewpane, theRemote Shares Consumed table does not displaydata for Windows hosts when the host has mounted a share.

■ In the overviewpane for aNetApp share, theConsumers table does not displaydata for NetApp shares mounted on a Windows host.

85Known issuesDiscovery and management issues

No information about Oracle file whose name ends in a specialcharacter (1413999)

If the name of an Oracle file ends in a special character or ^M, CommandCentralmaynot discover any informationabout that file, other than its name.Additionally,object dependency groups do not exist for such files.

After migrating discovery of a McDATA switch from the SWAPI interfaceto SMI-S, some zones are no longer discovered (1454063)

If you configured a McDATA switch for discovery through the SWAPI interfacein CommandCentral Storage 5.0 MP1 and then you upgrade to 5.1 and migratediscovery of the switch to SMI-S, CommandCentral does not discover inactivedefined zones and inactive zone sets.

Workaround

Add the inactive zone sets in the fabric through EFCM.

Vendor name does not display for Emulex HBAs connected to an ESXserver (1450813)

When you view information about an Emulex HBA that is connected to an ESXserver, the vendor name of the HBA does not display.


Discovery of NetApp unified storage devices fail if NetApp explorerdebug level is set to 6 (1449979)

On a Windows host, if you set the NetApp explorer’s debug level to 6, discoveryof NetApp unified storage devices may fail. We recommend that you do not setthe debug level any higher than 3.

Correlation missing between the physical disks and the backend arrayLUNs of a Netapp V-series unified storage device (1232692)

When you view details about a NetApp V-series unified storage device, theassociation between the array's physical disks and the backend array LUNs maybe missing. This occurs when you configure CommandCentral to discover theNetApp unified storage device first and then you configure the backend array.

To correlate the physical disks and the backend array LUNs, you either need towait until the next default polling interval or refresh the explorer.

Known issuesDiscovery and management issues

86

Inactive Oracle instances display in the Console after settingActiveInstanceOnly flag (1450915)

For a 4.x managed host that reports to a 5.1 Management Server, if you enablethe Oracle explorer’s ActiveInstanceOnly flag so that the explorer reports onactive instances only, rather than immediately deleting any inactive instances,the inactive instances display in the Console as missing.

CommandCentral Storage deletes the inactive instances after the standard purgeperiod.

Processes in failed state after rebooting SUSE 9 or SUSE 10 host(1458653)

After you reboot a SUSE 9 or SUSE 10 host, the followingmanaged host processesfail to start:

■ ApplicationExplorers

■ Data Module

■ HostExplorers

■ HALLHM

■ Simple Instrumentation Collection Layer

Workaround


VMware explorer leaks thread handles on Windows hosts (1460805)The VMware explorer leaks thread handles on Windows hosts, which may affectsystemperformance. If you loadWindowsTaskManager, youmaynotice that thehandle count for the explorer process grows after each explorer refresh.


User management issuesThe following issues relate to user management.

87Known issuesUser management issues

Password changes successfully even though New Password and Re-typepassword are different (1450916)

When you use Firefox 3 to change a user’s password, if you enter differentpasswords in the fields "New Password" and "Re-type password" the passwordchanges successfully.

After editing a user account, the task’s status displays as "Failed"(1430639)

When you edit a user account, the "Change Password" checkbox is enabled bydefault. If you connect to the Console using Firefox and attempt to edit a useraccount, if you leave the "Change Password" field enabled, and then click OKwithout entering the old and new passwords, the Console does not display awarning message that states you must enter the old and new passwords. Becauseof this, when you view the Task Status table, the task’s status displays as "Failed."However, the changes that youmade to the user account—for example, the user’semail address or role—were successful.

Data Module issues

Data Module alternate auto rule for an alternate scan not assigned toobjects (1436439)

If you create an alternate auto rule for an alternate scan, CommandCentral Storagedoes not assign that rule to newor existing hosts, NetApp unified storage devices,and rollup objects. Because of this, you may notice that alternate scans are notoccurring as per the auto rule for alternate scan.

Workaround

Associate the alternate scan rule with existing or newly added objects.

To associate the alternate scan rule with existing or newly added objects

1 In the Console, click Settings > DM Configuration > Scan Configuration.

2 Select (check) one or more objects.

3 From the drop-down menu, click Associate Rule.

4 In the Associate Rules dialog box, in the Alternate Rule drop-down list, selectthe rule that you want to associate.

5 Click OK.

Known issuesData Module issues

88

Incorrect number of messages in a mailbox (1437400)When you view details about the mailboxes in a Microsoft Exchange Server, thenumber of messages in the mailbox may be inaccurate.


Error 7304 appears when scanning NetApp MultiStore Virtual Systemson Windows (1456054)

OnWindows hosts, scans of NetAppMultiStore Virtual Systemsmay fail with thefollowing error message:

filescanner (7304): ERROR: A fatal error was detected in the thread

scanning directory 'directory_name'. Message: 'class

ConversionException EXCEPTION Error


Core file indicates that the dmexplorer process cored on AIX managedhost (1449688)

On AIX managed hosts, when you view the Data Module configuration and datadirectory, you may find a core file which indicates that the dmexplorer processcored. This occurs when the dmexplorer stops and then restarts—for example,during shutdown of CommandCentral Storage. The core does not cause anyproblems to the dmexplorer process. You can safely ignore the messages.

File scan of a NetApp Storage System fails on a Windows 2000 managedhost (1435940)

Whenyou runa file scan of aNetAppStorage SystemonaWindows2000managedhost, the scan of the NetApp device fails.

Workaround

Scan NetApp Storage Systems with a Windows 2003 host.

89Known issuesData Module issues

Known issuesData Module issues

90

Getting help


■ About CommandCentral Storage documentation

■ Displaying online help

■ Contacting Symantec

About CommandCentral Storage documentationThe following guides provide information about CommandCentral Storage:

Provides information about administering theproduct—for example, managing licenses and useraccounts, configuringproduct components, andworkingwith diagnostic information.

CommandCentralAdministrator’sGuide

Provides a high level overview of how you can useCommandCentral Storage.

CommandCentralGettingStartedGuide

Provides setup requirements for applications anddevices and instructs you how to configureCommandCentral Storage to discover them.

CommandCentral Hardware andSoftware Configuration Guide

Lists thedevices andapplications thatCommandCentralStorage supports.

CommandCentral Hardware andSoftware Compatibility List

Instructs you how to install CommandCentral Storage.CommandCentral InstallationGuide

Instructs you how to upgrade 4.xmanaged hosts to 5.x.CommandCentral StorageMigration Guide

6Chapter

Provides information about supported operatingsystems, host resource requirements, softwarelimitations, and known issues.

CommandCentralStorageReleaseNotes

Describes how you can use CommandCentral Storageto monitor, manage, and report on your storageinfrastructure.

CommandCentral Storage User’sGuide

Provides information about third-party software thatis used in CommandCentral Storage.

CommandCentral Third-PartyLicense Agreements

Product documentation is available on the Symantec Technical Support web site:

http://www.symantec.com/enterprise/support/documentation.jsp?pid=50379

Commenting on product documentationSubmit comments about theproductdocumentation to the followingemail address:

[email protected]

Please include the following information with your documentation comments:

■ The title and product version of the guide you are commenting on

■ The topic (if relevant) you are commenting on

■ Your comment

■ Your name

Displaying online helpCommandCentral includes online help as well as UNIX manual pages.

To display online help

1 Do one of the following:

■ In the Console, click the appropriate Help link or menu item.

■ In any dialog window, click the Help button.

2 On UNIX systems, you can use manual pages to find reference and usageinformation about product-specific commands.Whenyou install the product,thepkgadd command installs thenroff-taggedmanualpages in theappropriatedirectories under /opt/VRTS/man. However, the install does not update thewindex database.

Getting helpDisplaying online help

92

http://www.symantec.com/enterprise/support/documentation.jsp?pid=50379


To ensure that new manual pages display correctly

1 Update your:

■ MANPATH environment variable to point to /opt/VRTS/man

■ windex database

2 Refer to the catman(1M) manual page for more information about updatingwindex.

Contacting SymantecYou can contact Symantec on the Web, by email, or by telephone.

Using the support web siteFor technical assistance with any Symantec product, visit the Symantec SupportWeb site:

http://www.symantec.com/enterprise/support/assistance_care.jsp

From there you can:

■ Contact the Symantec Support staff and post questions to them

■ Get the latest software patches, upgrades, and utilities

■ View updated hardware and software compatibility lists

■ View Frequently Asked Questions (FAQ) pages for the products you are using

■ Search the knowledge base for answers to technical support questions

■ Receive automatic notice of product updates

■ Find out about training in the Storage Foundation products

■ Read current white papers related to the Storage Foundation products

Subscribing to email notification serviceSubscribe to the Symantec Email notification service to be informed of softwarealerts, newly published documentation, Beta programs, and other services.

Go to the following Web site:


93Getting helpContacting Symantec



Select a product and click E-mail Support at the bottomof the page. Your customerprofile ensures that you receive the latest Symantec technical informationpertaining to your specific interests.

Accessing telephone supportTelephone support is availablewith a valid support contract. To contact Symantecfor technical support, dial the appropriate phone number listed on the SupportGuide included in the product box and have your product license informationready for quick navigation to the proper support group.

Obtaining support by emailLicensed customers can use the following email address to obtain help withtechnical questions:

[email protected]

To obtain software updates by email, send your requests to the following emailaddress:

[email protected]

Obtaining license informationTo obtain license information, contact Symantec in one of the following ways:

■ U.S. and Canada telephone: 1-800-634-4747 option 3

■ Worldwide fax: +1-650-527-0952

■ Email:[email protected]

Purchasing productsFor help with purchasing Symantec products, visit the Symantec Web site:


where you can chatwith product experts or link to information about the products.

You can also contact a Symantec product representative by email at the followingaddress:

[email protected]

To speak with a Symantec product representative by telephone, customers in theU.S. and Canada can call 1-800-327-2232.

Getting helpContacting Symantec

94


veritas commandcentral™ storage release notes

Documents