Veritas CommandCentral™ Storage Release Notes · The product described in this document is...

Veritas CommandCentral™Storage Release Notes

for Microsoft Windows and UNIX

5.1.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.0

Legal NoticeCopyright © 2009 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 Corporation350 Ellis StreetMountain View, CA 94043

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 theproblemoccurred, 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 5.1.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported versions of CommandCentral Storage for rolling up data

to Enterprise Reporter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Preinstallation configuration requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Supported locales ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Solaris updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . 24Windows updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . 28HP-UX updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . 28AIX updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Red Hat Linux updates required for CommandCentral ... . . . . . . . . . . . . . . . . 29

System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Solaris system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Windows system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33HP-UX system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36AIX system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Linux system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

CommandCentral Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Co-existence of CommandCentral components with other Symantec

products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 3 No longer supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Activemanagement featureswill be removed fromCommandCentralStorage 5.2 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4 Fixed issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Issues fixed in CommandCentral Storage 5.1.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents

Chapter 5 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

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

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

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

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

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

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

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

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

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

DMX-4 storage arrays (1404832) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Cannot discover storage pools that do not have names

(1435403) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Size of a Celerra disk volume does not match Celerra Manager

(1747844) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60CommandCentral Storage does not discover NetBackup media

changers on Windows (1810148) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Discovery of HBAs fails on an AIX host (1839014) ... . . . . . . . . . . . . . . . . . . . . . 60

Console and report limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Reports ToolTips are truncated in Firefox .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Cannot log in to the Console using Internet Explorer when the

host name includes an underscore (1447601) ... . . . . . . . . . . . . . . . . . . . . . 61Dialogs overwritten when new dialogs are opened (606871) ... . . . . . . . . 61

4.x Agent limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Volumes and disk groups duplicated .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Incorrect data displayed for Oracle RAC applications .... . . . . . . . . . . . . . . . . 62Data displayed for unsupported applications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Discovered objects deleted from the database after 24

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

not available for 4.x Agent hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Contents8

Data Module collection of all files not supported for 4.x Agenthosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

DataModule Importer doesnot support secure (https) connectionto 4.x Agent hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 6 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

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

(542244) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Default agent password cannot be changed using

CommandCentral product installer on UNIX (859670) ... . . . . . . . . . . 66Managedhost fails to installwhen shell on remoteUNIXmanaged

host is configured as tcsh or csh (1170715) ... . . . . . . . . . . . . . . . . . . . . . . . . 66Summary file not created during managed host installation on

UNIX (1143138) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Erroneous reference to response file at end of Management

Server install on Solaris (1140473) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67CommandCentral installationsonWindows failwhile configuring

SICL (1171143) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Mistyped Management Server name cannot be corrected in the

Windows managed host installer (1449432) ... . . . . . . . . . . . . . . . . . . . . . . . 67Error message appears during uninstall of the Management

Server from a Windows host (1432751) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Authentication Service fails to upgrade during Management

Server installation on Windows (1427441) ... . . . . . . . . . . . . . . . . . . . . . . . . . 68VRTSWeb folder remains after uninstalling the Management

Server on Windows (1292780) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Error message about inability to copy files to /var/tmp displays

during install (1438157) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69HAL configuration fails during managed host install on AIX 5.3

TL06 or TL07 (1431432) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Windows’ServiceControlManager displays errorwhen selecting

the Symantec Product Authentication Service(1368976) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

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

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

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

host name (1423059) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

9Contents

Data and configuration files remain after uninstalling themanaged host from a Linux host (1397051) ... . . . . . . . . . . . . . . . . . . . . . . . . 71

NetBackup 6.5 does not run properly after installingCommandCentral 5.1.1 (1407023) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

Array explorers stop after upgrading Linux managed host to5.1.1 (1318748) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

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

CommandCentral Storage installations fail on UNIX hosts ifinstalled on auto-mounted volumes (1173776) ... . . . . . . . . . . . . . . . . . . . . 73

Uninstalling the Management Server or managed host fromUNIX fails (1673272) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Installer freezes during install of the Management Server on aWindows host that runs Storage Foundation (1800374) ... . . . . . . . . 74

Install on aHP-UXhostmay fail if run froma LinuxNFS server'smounted volume (1742038) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Installation of the Management Server fails on a Solaris 10 hostwith local zones and Storage Foundation 5.1 (1843473) ... . . . . . . . . 76

Some explorers not configured on a managed host upgradedfrom 5.0 MP1 (1844084) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

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

can no longer contact managed host (604446) ... . . . . . . . . . . . . . . . . . . . . 77Shared components stop-start order (856750) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 78Status of user-created HAL process does not display when

running vxccs status (1437246) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Array andCIMVAIL log files consume large amount of disk space

(1458508) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Oracle ASM Disk Group's ASM DG Used by Other Hosts value

misplaced (1795293) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79The command "net start VRTSsmweb" fails (1806029) ... . . . . . . . . . . . . . . . 79The halnetcheck utility fails (1795572) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Managed host issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80CommandCentral services do not start after you reboot a

Windows managed host (1799326) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Console and report issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

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

Emailed report does not reflect column sorting (615330) ... . . . . . . . . . . . . 82

Contents10

Incorrect name displayed for file systems on unmounted orunnamed volumes (864757) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Mismatch between time on Management Server and timedisplayed in scheduling dialogs (851525) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Port Bundle Builder Tool displays only one fabric (629557) ... . . . . . . . . . 82The Topology Map’s Print Preview displays a blank page

(1206846) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Table filter does not disable in a custom report (1445762) ... . . . . . . . . . . . 83Total values do not display for tables in ad hoc reports

(1446963) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Favorites link for the Host Editor no longer works

(1456338) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Array Storage Summary report displays incorrect capacity for

IBM DS6000 and DS8000 storage arrays (1437378) ... . . . . . . . . . . . . . . 84Virtualization Server Claimed Capacity attribute displays

incorrect value (1447060) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Unknown storage capacity used by Celerra's storage hierarchy

(1800033) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Incorrect masking status for the LUNs for a Celerra unified

storage system (1786011) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Console shows disk as part of an Oracle ASM disk group after it

was removed from the disk group (1823721) ... . . . . . . . . . . . . . . . . . . . . . . 85Table column values that contain plus signs are not saved

(1795869) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Distribution of Storage by Interface is displaying "Fibre" for

unmasked LUNs (1832384) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Allocation of Array Storage by Vendor for EMC displays NetApp

arrays (1832996) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Reported 3PAR storage capacity numbers do not match

(1834265) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87User management issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Domains not available for user accounts and user groups(1792352) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

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

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

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

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

runs on a Linux managed host (1386606) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

11Contents

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

IBMSANVolumeController (SVC) SICLStatus valueunavailable(1743398) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Refreshing the storage explorer fails on a host with no physicalFibre Channel HBAs (1798710) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Visualization issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Incorrect LUN capacity estimates when CX Meta LUNs created

from mixed RAID groups (1016679) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Attributes and group memberships not migrated for Hitachi

RAID groups (859638) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Incomplete information displayed for newly discovered objects

(865845) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Duplicatedevicehandles appear for anESXserver aftermigrating

discovery from SMI-S to VI SDK (1451189) ... . . . . . . . . . . . . . . . . . . . . . . . . 91Monitoring issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

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

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

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

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

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

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

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

Monitoring not available for Cisco switches configured in 5.1.1(1435097) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

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

Monitoring favorites not available after an upgrade(1781686) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Monitoring data for Cisco ports does not appear after upgradeto 5.1.1 (1834204) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Alarm Service configuration reverts to default values afterupgrading Solaris Management Server to 5.1.1(1714407) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Discovery and management issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Disk state not discovered (859207) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Contents12

Incomplete discoverywhen two versions of DB2 are on the samehost (605860) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

HPEVA:Disabling discovery ofManagementAppliance does notdisable discovery of arrays (614523) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Manually configured database instances not coming upautomatically after upgrade (900677) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

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

Discovery failure for storage arrays configuredasSMI-Smanagedarrays (1185347) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

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

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

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

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

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

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

Wrong operating system displays for a storage view(1232117) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Explorers do not start after rebooting a SUSE Linux managedhost (1469398) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

LUNs not masked to array ports for Celerra unified storagedevices do not appear (1810799) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Celerra explorer does not discover all file systems(1802239) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Hitachi HiCommand WMS storage array appears twice afterupgrade (1796494) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Discovery error for EMCCelerra unified storage system if debuglevel is not 1 (1835013) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

No correlation between storage pool and associated disk volumefor an EMC Celerra unified storage system (1785031) ... . . . . . . . . . 103

Incorrect number of file systems for an EMC Celerra unifiedstorage system (1803708) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

The available capacity for anOracle ASMdisk group is incorrect(1835478) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13Contents

IP address may not display for a Celerra unified storage system(1798405) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Data Module issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Data Module alternate auto rule for an alternate scan not

assigned to objects (1436439) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Core file indicates that the dmexplorer process cored on AIX

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

managed host (1435940) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 7 Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

About CommandCentral Storage documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . 107Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Displaying online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Contacting Symantec ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

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

Contents14

Overview of this release

This chapter includes the following topics:

■ Introduction to Veritas CommandCentral Storage

■ What’s new in CommandCentral Storage 5.1.1

■ Supported versions of CommandCentral Storage for rolling up data toEnterprise Reporter

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.

1Chapter

Using CommandCentral Storage together with other Symantec software, ITmanagers have the tools they need to perform real, active, end-to-end storageresource management and make strategic decisions about their future storageneeds.

What’s new in CommandCentral Storage 5.1.1CommandCentral Storage 5.1.1 contains and builds upon 5.1 functionality,providing several new features and enhancements.

Table 1-1 New features and enhancements

DescriptionFeature

CommandCentral Storage now supports discovery of EMCCelerraNetwork Servers.

For information about the specific models that we support, seethe CommandCentral Hardware and Software Compatibility List.

www.symantec.com/business/support/documentation.jsp?view=comp&pid=50379

EMC Celerra support

CommandCentral Storage now supports discovery of OracleAutomatic Storage Management (ASM) instances.

For information about the specific versions that we support, seethe CommandCentral Hardware and Software Compatibility List.

Oracle AutomaticStorage Management(ASM) support

You can now add user groups to CommandCentral Storage.Whenyou add a user group, you specify an existing group within anoperating system network domain. You also select a role for thisgroup, which lets you set permissions at the group level.

For more information, see the CommandCentral Administrator’sGuide.

User group support

In previous releases, CommandCentral Storage can only discoverMicrosoft SQLServerswith an explorer that runs as a local systemuser and connects to the server without credentials. Starting inCommandCentral 5.1.1, you can now configure CommandCentralStorage to use a specific user account to discover Microsoft SQLServers.

For more information, see the CommandCentral Hardware andSoftware Configuration Guide.

Non-system userdiscovery of MicrosoftSQL Servers

Overview of this releaseWhat’s new in CommandCentral Storage 5.1.1

16

http://www.symantec.com/business/support/documentation.jsp?view=comp&pid=50379

http://www.symantec.com/business/support/documentation.jsp?view=comp&pid=50379

Table 1-1 New features and enhancements (continued)

DescriptionFeature

The default discovery method that CommandCentral uses todiscover ESX servers is now through the VMware InfrastructureSDK (VI SDK). If you currently discover an ESX server throughSMI-S and you upgrade to 5.1.1, CommandCentral automaticallychanges the discovery method to VI SDK. There is nothing thatyou need to do to prepare for this transition.

Default discovery ofESX servers is throughVI SDK

CommandCentral Storage now supports discovery of MicrosoftSQL 2008 instances.

CommandCentral Storage also supports monitoring of MicrosoftSQL 2008 instances. This includes support ofMicrosoft SQL 2008instances that run on a Storage Foundation 5.1 forWindowshost.

Microsoft SQL 2008support

CommandCentral Storage now supports discovery of MicrosoftExchange Server 2007 instances.

CommandCentral Storage also supports monitoring of MicrosoftExchange Server 2007 instances. This includes support ofMicrosoft Exchange Server 2007 instances that run on a VeritasCluster Server (VCS) cluster and aMicrosoft Cluster Server (MSCS)cluster.

CommandCentral Storage does not support scanning ExchangeServer 2007 instances with the Data Module.

Microsoft ExchangeServer 2007 support

The discovery of switches and storage arrays is nowqualifiedwithSMI-S 1.2.

For information about the specific device support, see theCommandCentral Hardware and Software Compatibility List.

SMI-S 1.2 qualified

CommandCentral Storage now supports performancemonitoringfor the following devices that use SMI-S:

■ IBM DS6000 series storage arrays

■ IBM DS8000 series storage arrays

■ IBM ESS (Shark) storage arrays

■ IBM SAN volume controllers

Performancemonitoring support

CommandCentral Storage now discovers the clones and snaps ofEMCSymmetrix andDMX storage arrays that you create with theTimeFinder/Clone and TimeFinder/Snap software.

EMCTimeFinder cloneand snap support

CommandCentral now discovers PCI-E HBAs on AIX hosts.PCI-E HBA support

17Overview of this releaseWhat’s new in CommandCentral Storage 5.1.1


DescriptionFeature

CommandCentral now supports the Data Center Fabric Manager(DCFM) with Brocade and McDATA switches in a mixed fabricconfiguration.

Brocade and McDATAmixed fabricinteroperability

CommandCentral now discovers Linux Logical Volume Managerfor Red Hat Linux 4 and 5 and SUSE Linux 10.

Linux Logical VolumeManager (LVM)support

CommandCentral Storage 5.1.1 introduces the following ad hocreports:

■ CommandCentral Storage Health Report

This report helps you identify the managed hosts and devicesthat require attention.

■ Generic Group Array Storage Usage Report

This report details array usage at different levels ofvirtualization, from physical storage to the host's file system.A generic group appears in this report if the group includesone or more storage arrays. This report does not include NASand unified storage systems.

■ SAN Waterfall Array Storage Usage Report

This report shows the use of array storage at different levelsof virtualization.

■ Shared Storage Report

This report details the storage that a host shares with otherhosts.

For more information about these sample ad hoc reports, see theCommandCentral Storage User’s Guide.

New sample ad hocreports

Reports now appear in 3D.

In CommandCentral Storage, you can adjust a global setting todisplay reports in either 2D or 3D.

For more information, see the CommandCentral Administrator’sGuide.

3D reports

TheAgentless Settings panewas redesigned to enhance usability.Usabilityimprovements foragentless settings

Overview of this releaseWhat’s new in CommandCentral Storage 5.1.1

18


DescriptionFeature

VMware improvements include the following changes:

■ In the Managing Summary pane, the term Virtual Hostschanges to Virtual Machines.

■ In theVirtualMachinespane, the list of your virtualmachinesnow appear in the following two tables:

■ Virtual Machine Summary table

This table includes the virtual machines that run on theESX servers that CommandCentral discovers.

■ Virtual Hosts Summary table

This table includes the virtual machines that run theCommandCentral managed host.

■ When you view the Overview pane for a virtual machine, thevirtual disks that are associated with that virtual machineappear.

■ The object dependency group (ODG) page for a virtualizationserver nowdisplays associated storagepools, virtualmachines,and virtual machine disks.

For more information, see the CommandCentral Storage User’sGuide.

VMwareimprovements

You can install this release on English, Chinese (Simplified andTraditional), Japanese, andGermanoperating systems.This releaseis available in an English version only.

We support these locales on supported Windows and UNIXoperating systems. We have tested the locales on Windows andSolaris.

New suported locales

You can now install theManagement Server on hosts that run theWindows Server 2008 operating system.

Windows Server 2008support for theManagement Server

You can now install the Management Server on virtual machinesthat run supported versions of the Windows Server operatingsystem.

VMware support forthe ManagementServer

You can now install the managed host on hosts that run the AIX6.1 operating system.

AIX 6.1 support for themanaged host

19Overview of this releaseWhat’s new in CommandCentral Storage 5.1.1

Supported versions of CommandCentral Storage forrolling up data to Enterprise Reporter

Table 1-2 identifies the supported versions of CommandCentral Storage fromwhich Enterprise Reporter can roll up data.

Table 1-2 Supported versions of CommandCentral Storage from whichEnterprise Reporter can roll up data

EnterpriseReporter 5.1

EnterpriseReporter 5.0 MP1

EnterpriseReporter 5.0

CommandCentralStorage version

XX4.x

XXX5.0

XX5.0 MP1

XX ¹5.1

²5.1.1

¹ Requires Rolling Patch 1 for Enterprise Reporter 5.0 MP1 (5.0 MP1-RP1). Visitthe Symantec Patch Central Web site to download 5.0 MP1-RP1.vias.symantec.com/labs/patch/

²Wedonot support data rollup fromaCommandCentral Storage5.1.1ManagementServer to Enterprise Reporter 5.1.Wewill release a hotfix for Enterprise Reporter5.1 to provide support.

Overview of this releaseSupported versions of CommandCentral Storage for rolling up data to Enterprise Reporter

20

https://vias.symantec.com/labs/patch/

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:

www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=50379

2Chapter

http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=50379


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

Table 2-1 CommandCentral Storage operating system requirements

Operating systems supportedComponent

■ Solaris 8, 9, 10

■ 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: Standard, Web,Datacenter, and Enterprise

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

You can install the Management Server on virtual machines that runsupported versions of the Windows Server operating system.

ManagementServer

System requirementsOperating system requirements

22

Table 2-1 CommandCentral Storage operating system requirements(continued)


■ Solaris 8, 9, 10

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

Note: Arraymanagement andNetApp unified storage discovery are notsupported for 11.31.

■ AIX 5.2, 5.3, 6.1

Note: For AIX 5.3 ML5, install all IY92292 filesets on the host. To verifythat the filesets are installed, type the following command: "instfix -ikIY92292".

■ 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: Arraymanagement andNetApp unified storage discovery are notsupported for Red Hat Linux 5.0. Install not supported if SE Linux isenabled. Itanium processor not supported for Red Hat Linux.

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 Storage, youenable the host to gather information for more LUNs than the defaultnumber of paths (15).

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

Note: Arraymanagement andNetApp unified storage discovery are notsupported. Install not supported if SE Linux is enabled.

■ Windows Server 2008 32-bit and 64-bit for the following editions:Standard, Datacenter, Enterprise, and Web (array management andNetApp unified storage discovery capabilities are not supported)

■ 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


managedhost

23System requirementsOperating system requirements

Table 2-1 CommandCentral Storage operating system requirements(continued)


ESX virtualization server 3.0.0, 3.0.1, 3.1, 3.5, 3.5.1, and 3.5.2

Note: If the virtualization server uses QLogic's HBA, install the VMwareversion of QLogic's HBA API library. The guest OS requires installation ofVMware Tools.

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 42.

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

Supported localesYou can install this release on English, Chinese (Simplified and Traditional),Japanese, and German operating systems. This release is available in an Englishversion only.

We support these locales on supported Windows and UNIX operating systems.We have tested the locales on Windows and Solaris.

Solaris updates required for CommandCentralThis section lists the packages and patches required to run CommandCentral onSolaris.

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 additional


24

recommended and security patches. Download Solaris patches and patch clustersfrom the following Web site:

http://sunsolve.sun.com

The following table lists the packages and patches required for Solaris hosts.


http://sunsolve.sun.com

Table 2-2 Packages and patches required to run CommandCentral on Solaris

Required patchesRequired packagesOS version

■ 108434 *

■ 108434-14

■ 108435

■ 108435-14

■ 108528-29

■ 108652-78*

■ 108773-18

■ 108921-19

■ 108940-60

■ 108987-13

■ 108989-02

■ 108993-18

■ 108993-32

■ 109147-27

■ 109326-13

■ 110386-03

■ 110615-10

■ 111023-03

■ 111111-03

■ 111308-04

■ 111310-01

■ 111317-05

■ 111721*

■ 112003-03

■ 112396-02

■ 112438-02

■ 112472-01

■ 113648-03

■ 115827-01

■ 116602-01

■ 112438

An asterisk (*) indicates that the patchis required for array managementfunctionality.

SUNWgss (for theManagementServer only)

Solaris 8


26

Table 2-2 Packages and patches required to run CommandCentral on Solaris(continued)

Required patchesRequired packagesOS version

■ 111722-04

■ 111703

■ 112785-30

■ 112963-25

■ 113096-03

■ SUNWgss (for theManagement Server only)

■ SUNWscpux

Solaris 9

None required.■ SUNWgss (for theManagement Server only)

■ SUNWscpu

Solaris 10

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.

Increasing semaphore limits on SolarisThe Veritas Provider Access Layer (VxPAL) and the Veritas EnterpriseAdministrator Service requiremoreoperating systemsemaphores thanareusuallyset by default on Solaris.

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 required for CommandCentralTo run CommandCentral components on Windows 2000, install Service Pack 3.

Download and apply Windows updates from the following Web site:

http://windowsupdate.microsoft.com

HP-UX updates required for CommandCentralThis section lists the patches required to run the CommandCentralmanaged hoston different versions of HP-UX.

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

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

The following table lists the required patches for HP-UX.

Table 2-3 Patches required for HP-UX

Required patchesOS version

■ PHSS_28509*

■ PHSS_28880*

■ PHSS_30968*

■ PHSS_31326

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

HP-UX 11i v1

■ PHSS_32231

■ PHSS_33903

■ PHSS_34444

■ PHSS_34445

■ PHSS_34853

■ PHSS_34859

■ PHSS_35055

■ PHSS_35528

■ PHSS_35978

■ PHSS_36336

HP-UX 11i v2

AIX updates required for CommandCentralThe following patches are the required to run the CommandCentralmanagedhoston AIX version 5.2 with Maintenance Level 7 (ML7) or higher and AIX version 5.3with Technology Level 3 (TL3) or higher:


28

http://windowsupdate.microsoft.com



■ xlC.rte-6.0.0.0

■ xlC.aix50.rte-6.0.0.0

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.

Red Hat Linux updates required for CommandCentralThe following patches are required to run the CommandCentralmanaged host onRed Hat Linux:

■ openssl096b-0.9.6b-16

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

System resource requirementsThe sections listed 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:

www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=50379

29System requirementsSystem resource requirements



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.

You can view system requirements for various operating systems in the following:

■ See “Solaris system requirements” on page 30.

■ See “Windows system requirements ” on page 33.

■ See “HP-UX system requirements” on page 36.

■ See “AIX system requirements” on page 38.

■ See “Linux system requirements” on page 40.

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

■ Table 2-4 provides system resource requirements for installingCommandCentral 5.1.1 components.

■ Table 2-5 provides system resource requirements for upgradingCommandCentral 5.1 components to 5.1.1.

■ Table 2-6 provides system resource requirements for upgradingCommandCentral 5.0 MP1-RP6 components to 5.1.1.

The required amounts of memory and disk space are in addition to the resourcesalready consumed 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.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

System requirementsSystem resource requirements

30

Table 2-4 System resource requirements for installing CommandCentral 5.1.1on Solaris hosts

Dual CPUrequired

Temp spacerequired

Disk space requiredPhysicalmemoryrequired

Component

Yes313 MBTotal: 1902 MB

■ Relocatable: 1107 MB

■ Non-relocatable in /opt: 761 MB

■ Binaries backup: 34 MB

■ Package: 1741 MB

■ Patch: 94 MB

8 GB (16 GB forCommandCentralStorage +CommandCentralStorage ChangeManager)

ManagementServer

No187 MBTotal: 436 MB




■ Package: 387 MB

■ Patch: N/A

256 MBManaged host





■ Package: 753 MB

■ Patch: 69 MB

512 MBManaged host(with arraymanagement)

Table 2-5 System resource requirements for upgrading CommandCentral 5.1to 5.1.1 on Solaris hosts

Dual CPUrequired?

Temp spacerequired


Component






ManagementServer


Table 2-5 System resource requirements for upgrading CommandCentral 5.1to 5.1.1 on Solaris hosts (continued)

Dual CPUrequired?

Temp spacerequired


Component




256 MBManaged host





Table 2-6 System resource requirements for upgrading CommandCentral 5.0MP1-RP6 to 5.1.1 on Solaris hosts

Dual CPUrequired?

Temp spacerequired


Component

No187 MBTotal: -106 MB

■ Relocatable: -56 MB


■ Binaries backup: -65 MB

256 MBManaged host




■ Binaries backups: -121 MP


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 calculates


32

the package and the tar file sizes and reports this sum as the required tempspace.

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




The system resource requirements for the Management Server apply to virtualmachines and physical machines. That is, the system resource requirements toinstall the Management Server are the same for virtual machines and physicalmachines.

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.1, the relocatable space is required onthe system drive where the operating system is installed, and thenon-relocatable space is required on the drive where the CommandCentralcomponent is installed.

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

Note:When installing CommandCentral 5.1.1, the relocatable space is the installdrive space, the non-relocatable space is the system drive space, and no backupspace is required.


Table 2-7 System resource requirements for installing CommandCentral 5.1.1on Windows hosts

Dual CPUrequired?

Temp spacerequired

Disk space requiredPhysical memoryrequired

Component



■ Non-relocatable: 190 MB


ManagementServer




256 MBManagedhost (localinstall)




256 MBManaged host(remote installusing Agent PushInstall Utility)




512 MBManaged host witharray management(local install)




512 MBManaged host witharray management(remote installusing Agent PushInstall Utility




512 MBAgent Push InstallUtility

Note:WhenupgradingCommandCentral 5.1.1, the relocatable space is the backupdrive space, and the non-relocatable space is the install drive and system drivespaces combined.


34

Table 2-8 System resource requirements for upgrading CommandCentral 5.1to 5.1.1 on Windows hosts

Dual CPUrequired?

Temp spacerquired


Component

Yes275 MBTotal: 345 MB + twice thedatabase size

■ Relocatable: 90 MB +database size

■ Non-relocatable: 255 MB +database size


ManagementServer



256MBManagedhost (localinstall)



256MBManaged host(remote installusing Agent PushInstall Utility)



512MBManaged host witharray management(local install)



512MBManaged host witharray management(remote installusing Agent PushInstall Utility



512MBAgent Push InstallUtility

Note: For upgrading, the relocatable space is the backup drive space, and thenon-relocatable space is the install drive and system drive spaces combined.


Table 2-9 System resource requirements for upgrading CommandCentral 5.0MP1-RP6 to 5.1.1 on Windows managed hosts

Dual CPUrequired?

Temp spacerequired


Component



■ Non-relocatable: -90 MB

256MBManagedhost (localinstall)


■ Relocatable: 1MB

■ Non-relocatable: -90MB

256MBManaged host(remote installusing Agent PushInstall Utility)




512MBManaged host witharray management(local install)


■ Relocatable: 1MB


512MBManaged host witharray management(remote installusing Agent PushInstall Utility)

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.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.


36

Table 2-10 System resource requirements for installing CommandCentral 5.1.1on HP-UX hosts

Dual CPUrequired?

Temp spacerequired


Component

No186MBTotal: 478 MB




■ Package: 455 MB

■ Patch: N/A

256 MBManaged host

No186MBTotal: 710 MB




■ Package: 587 MB

■ Patch: 111 MB


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

Dual CPUrequired?

Temp spacerequired


Component




256 MBManaged host






Table 2-12 System resource requirements for upgrading CommandCentral 5.0MP1-RP6 to 5.1.1 on HP-UX hosts

Dual CPUrequired?

Temp spacerequired


Component





256 MBManaged host







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.

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






38

Note:When you install or upgrade to CommandCentral 5.1.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-13 System resource requirements for installing CommandCentral 5.1.1on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component




■ Package: 367 MB

■ Patch: N/A

256 MBManaged host




■ Package: 483 MB

■ Patch: 117 MB


Table 2-14 System resource requirements for upgrading CommandCentral 5.1to 5.1.1 on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component



256 MBManaged host

No154 MBTotal: 4 MB




Table 2-15 System resource requirements for upgrading CommandCentral 5.0MP1-RP6 to 5.1.1 on AIX hosts

Dual CPUrequired?

Temp spacerequired


Component


■ Non-relocatable in /opt: -500 MB


256 MBManaged host






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






40

Table 2-16 System resource requirements for installing CommandCentral 5.1.1on Linux hosts

Dual CPUrequired?

Temp spacerequired


Component





■ Package: 211 MB

■ Patch: N/A

256 MBManaged host





■ Package: 299 MB

■ Patch: N/A


Table 2-17 System resource requirements for upgrading CommandCentral 5.1to 5.1.1 on Linux hosts

Dual spacerequired

Temp spacerequired


Component

No29 MBTotal: 17 MB



256 MBManaged host

No29 MBTotal: 17 MB





Table 2-18 System resources for upgrading CommandCentral 5.0 MP1-RP6 to5.1.1 on Linux hosts

Dual spacerequired

Temp spacerequired


Component




256 MBManaged host






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 2.0.0.x or 3.x (Windows 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

42

Co-existence of CommandCentral components withother Symantec products

Several Symantec products may be installed on the same host in a typical datastorage management environment.

The following table describes the products (or product components) that canco-exist on a host where the CommandCentral 5.1.1 Management Server isinstalled.

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.

Table 2-19 CommandCentral Management Server co-existence with otherSymantec products

Co-installwith theManagementServer?Symantec product component

Yes

On Windows hosts, if you install theCommandCentral 5.1.1ManagementServeron ahost that includes EnterpriseReporter5.1, a known issue occurs in theCommandCentral StorageChangeManagerand Enterprise Reporter Consoles.

See the CommandCentral Storage ChangeManager Release Notes..

CommandCentral Enterprise Reporter 5.1

NoVeritas Backup Reporter 6.6

YesVeritas Cluster Server 5.5.1 ManagementConsole (VCS MC)

No (no support for high availability)Veritas Cluster Server (VCS) cluster node

NoVeritas NetBackup 6.5.5 Client

NoVeritas NetBackup 6.6 Server

Yes on Windows

No on Solaris

VeritasNetBackup 6.5.4OperationsManager

YesVeritas Storage Foundation Manager 2.1Management Server

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

Table 2-19 CommandCentral Management Server co-existence with otherSymantec products (continued)

Co-installwith theManagementServer?Symantec product component

YesVeritas Storage Foundation Manager 2.1managed host

YesVeritas Storage Foundation5.0MP3 forUNIX

YesVeritas Storage Foundation 5.1 for UNIX

YesVeritas Storage Foundation for Windows 5.1

The following table describes the products (or product components) that canco-exist on a host where the CommandCentral 5.1.1 managed host is installed.

Table 2-20 CommandCentral managed host co-existence with other Symantecproducts

Co-install with the managed host?Symantec product component

YesCommandCentral Enterprise Reporter 5.1

YesVeritas Cluster Server 5.5.1 ManagementConsole (VCS MC)

YesVeritas Cluster Server 5.1 for UNIX

YesVeritas NetBackup 6.5.5 Client

YesVeritas NetBackup 6.5.5 Server

YesVeritas Storage Foundation Manager 2.1Management Server

YesVeritas Storage Foundation Manager 2.1managed host

Yes—only formanaged hostswithout arraymanagement capabilities

Veritas Storage Foundation 5.0 on an HP-UX11.23 host


Veritas Storage Foundation 5.0 on an HP-UX11.31 host


Veritas Storage Foundation 5.0 MP1 on anHP-UX 11.23 host

YesVeritas Storage Foundation 5.0 MP2 on anHP-UX 11.23 host

System requirementsCo-existence of CommandCentral components with other Symantec products

44

Table 2-20 CommandCentral managed host co-existence with other Symantecproducts (continued)

Co-install with the managed host?Symantec product component

YesVeritas Storage Foundation5.0MP3 forUNIX

Yes—if a managed host with arraymanagement and NetApp discoverycapabilities, then you must install StorageFoundation for Windows 5.1 first and theninstall the managed host

Veritas Storage Foundation for Windows 5.1

YesVeritas Storage Foundation for Windows 5.1High Availability

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

System requirementsCo-existence of CommandCentral components with other Symantec products

46

No longer supported


■ Active management features will be removed from CommandCentral Storage5.2

Active management features will be removed fromCommandCentral Storage 5.2

We will remove active management features from our next release ofCommandCentral Storage,whichwill beCommandCentral Storage 5.2. The activemanagement features that we will remove include the following:

■ Fabric and zoning management

■ LUN binding

■ LUN creation and deletion

■ LUN masking

■ Multi LUN binding

■ Multi LUN masking

■ Port enabling and disabling

■ Zoning

3Chapter

No longer supportedActive management features will be removed from CommandCentral Storage 5.2

48

Fixed issues


■ Issues fixed in CommandCentral Storage 5.1.1

Issues fixed in CommandCentral Storage 5.1.1The following tables list the known issues that are fixed in this release ofCommandCentral Storage.

Table 4-1 lists the fixed issues that affect the Management Server.

Table 4-1 Fixed issues that affect the Management Server

DescriptionIncident

Whenyouview theOverviewpane for anExchange Server, the StorageGroupstable displays incorrect used capacity for a storage group.

893962

For the hot spare drives of EMC Symmetrix arrays, the Console incorrectlydisplays "NO" in the Spare column.

1394219

Whenmultiple users access theConsole, an "OutofMemory" exception appearsin the Console.

1414531

In the NetApp Overview pane, the Shares/Exports table does not displayinformation about the consumer host name and mount point.

1426708

In the Configured Devices Summary table, in the Object column, the name ofa McDATA switch may not appear.

1439179

Cannot add an unidentified adapter to a generic group.1440651

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

4Chapter

Table 4-1 Fixed issues that affect the Management Server (continued)

DescriptionIncident

In the cluster Overview pane, the Resources table shows an SQL databaseinstance instead of the SQL server name.

1451132

Incorrect icons appear for virtualization servers and NetApp unified storagedevices.

1453274

Resetting alerts does not always clear alerts.1456719

The Console identifies the Simple Instrumentation Collection Layer (SICL) asdisconnected onmanaged hosts or alertsmay state that SICL is disconnected.

1456763

Incorrect overhead capacity appears for a managed disk group from an IBMvolume controller.

1465081

You cannot view any information in the object dependency group for anagentless host.

1478831

Ona64-bitWindowshost, you cannot install the 64-bit Authentication Serviceafter installing or uninstalling the CommandCentral Management Server.

1485188

During installation, database upgrade may fail if the database takes too longto stop.

1519957

Cannot use the Edit Host operation to remove an unidentified adapter thatwas correlated to a host.

1523854

Email addresses for user accounts disappear after the Console restarts.1527433

Unidentified adapters appear as non-clickable node objects.1530158

Due to the large size of the CommandCentral Storage database, the highnumber of objects that CommandCentral Storage monitors, and the highnumber of alerts present, the following issues may occur: when you attemptto log in to the Console, the log in takes longer than usual or is unsuccessful;a licensing error appears in the Console; and pages in the Console take a longtime to load. If you restart the database and the Alert Manager, the issues goaway and then reappear after a few days.

1538116

Alerts state that the "vrtsweb" process is not running even though the processis running correctly. Additionally, alerts state that the "webappsvc" is notrunning, which is erroneous because the process no longer runs inCommandCentral Storage.

1538274

Enclosure port information is not available for an object dependency group.1540525

Monitoring of physical disks is not available for Fujitsu arrays that arediscovered through an embedded CIMOM.

1542004

Fixed issuesIssues fixed in CommandCentral Storage 5.1.1

50


DescriptionIncident

Port faults do not show up for all Brocade firmware versions.1556671

User reports do not include the "NetApp Unified Storage Volume" scope. ForFiles and Directories reports, the list of objects for the scope incorrectlyincludes NetApp aggregates.

1557783

CommandCentral Storage doesnot discover the switch ID for aBrocade switch.1586282

The VMware explorer does not work properly if more than 20 ESX servers areconfigured or if ESX 2.x servers are configured.

1595054

After you edit projection settings ("Number of projection points to display"and "Number of historical points to use"), the projection charts do not displaythe number of data points entered in the projection settings.

1598200

The array explorer process might crash when it discovers HP EVA storagearrays.

1598566

CommandCentral Storagedoesnot supportRAID6LUNdiscovery and capacitycalculation for HP EVA 8400/4400/6400 storage arrays and does not discoverrack information and device ports for HP EVA 8400 storage arrays.

1631968

If a quota on a volume or qtree has multiple users associated with it, thenCommandCentral Storage displays only one quota user.

1632051

The classification of ports as target ports or initiator ports is not available forsome device ports.

1636465

Switches with multiple IP addresses appear multiple times in the Switchestable.

1636613

If you view the Directory Aging Detail report and click any of the links thatappear in the tables, an error appears.

1651772

For 3PAR storage arrays, there is a capacity mismatch between physicalconfigured capacity and total storage pool capacity.

1652156

Due tomemory leaks, thememory consumption of theBrocade explorermightincrease.

1652454

On Windows, the installer fails with the following error: "MSI Error 1720.There is a problem with this Windows Installer package."

1652963

Incorrect icons appear in the generic group topology page for a virtualizationserver.

1653527

51Fixed issuesIssues fixed in CommandCentral Storage 5.1.1


DescriptionIncident

For 3PAR storage arrays, reports display Available and Overhead capacity aszero. The capacity for Available and Overhead appear in Logical: Unknown.

1654408

CommandCentral Storage does not report spare capacity for 3PAR storagearrays.

1654660

On a policy's overview pane, when you click the Status hyperlink, theEnable/Disable policy operation does notwork from the Edit Policy dialog box.

1654783

TheEMCCLARiiONexplorer does not set the LUNbindingswith ports on bothstorage processors so that the path availability is shown through both storageprocessors.

1662647

CommandCentral Storage cannot monitor multiple disk enclosures for EMCCLARiiON storage arrays.

1671824

Due tomemory leaks, thememory consumption of theNetApp explorermightincrease.

1671882

The Topology Map for a generic group or object dependency group takes along time to load.

1674262

Due to memory leaks, the memory consumption of the McDATA explorermight increase.

1675269

When CommandCentral Storage discovers Brocade switches through SMI-S,it reports 8GB switch ports as 4GB switch ports.

1677573

Cannot install theManagement Server on aWindows hostwhere short namesare disabled.

1677639

For SMI-S discovered arrays, CommandCentral Storage does not report drivetype and disk rpm for physical disks.

1679149

For 3-PAR storage arrays, the configured raw capacity for volumes is blank.1703042

The global Topology Map does not display if a Cisco switch does not have avirtual switch associated with it.

1710362

Masking information does not appear for an IBM DS volume group whendiscovered through the CLI.

1722418

Adiscovery error appears in the ConfiguredDevices pane for IBMSANvolumecontrollers.

1723138

The Central HAL Manager crashed after the system clock was reset.1736648


52


DescriptionIncident

In theSettings >Diagnostics pane, theCCResourceUsage graphonly displaysthe top 16 processes.

1737435

If you add multiple charts and tables in an ad-hoc report, some of the chartsand tables may not appear.

1740214

TheCentralHALManager (CHM) crasheswhen its database credentials becomeinvalid due to a host OS UUID change.

1741205

An error displays when you click the To Table link on the Oracle tablespacesgraph.

1743338

A discovery error appears in the Configured Devices pane for HP EVA storagearrays.

1743666

For CLARiiON storage arrays, LUN masking details do not display for asnapshot LUN.

1779632

The installer does not upgrade the database if the database was relocated toa new location.

1779916

Improved the performance of the McDATA SMI-S explorer.1788095

Improved the performance of the Brocade SMI-S explorer.1788098

The Cisco explorer consumes a large amount of memory and then crashes.1802262

Cross-site scripting vulnerabilities in the CommandCentral Storage Console.1804244

To help reduce the likelihood of database growth, increased the monitoringintervals for the following: applicationmonitoring to sixhours, self-monitoringto one hour, VCS monitoring to six hours, and SICL monitoring to six hours.

1808914

The Edit Device Configuration wizard shows an incorrect selection for theEnable Monitoring checkbox if the device's configuration name is differentthan the IP address or fully qualified host name.

1809708

If you export the CCResource Usage report, the date column heading does notdisplay correctly.

1810070

The Storage Consumption Detail reports take a long time to load.1823295

Unable to configure an EMC CLARiiON CX400 storage array.1828590

Monitoring and trending of array capacity does not work if you use auser-defined explorer for device discovery.

1834182



DescriptionIncident

The Switch Port Performance Summary report does not showdata for the lastseven days, one month, and three months.

1835134

Table 4-2 lists the fixed issues that affect the managed host.

Table 4-2 Fixed issues that affect the managed host

DescriptionIncident

Installationof themanagedhost ona remoteAIXhost fails fromanNFSmount.1154254

CPI warning displays during reconfiguration of an HP-UX managed host.1439576

Error 7304appearswhenCommandCentral Storage scans aNetAppMultiStoreVirtual System on Windows.

1456054

Data Module scan of a NetApp filer fails when it scans a very deep directorystructure (the .rlg file for a scanwith a high debug level contains the long pathas a last message).

1456057

The vxsicld process consumes a large amount of CPU and memory.1509218

A file scanmay fail on aWindowsmanaged host with the followingmessages:"Disk Not shared," "In Use," or "EOF reached."

1516952

Push install upgrade of the managed host fails.1526486

Alerts do not appear when there is a dynamic multi-pathing failure.1531478

Rebooting aManagement Server that doesnot have any enablednetwork cardscauses CommandCentral services to be unreachable frommanagedhosts evenafter network cards are re-enabled.

1535219

On Windows hosts, alerts state that "PBX is not running" even if the serviceis running.

1538284

Security vulnerabilities in HAL\bin\Krb5_32.dll1539764

Whenmanagedhost services start, theWindowsEventViewerdisplayswarningmessages.

1542385

CommandCentral Storage cannot correlate an Oracle tablespace's file nameto the underlying storage when the file name includes special characters. Asa result, LUNs and device handles do not display in the Console.

1557885


54

Table 4-2 Fixed issues that affect the managed host (continued)

DescriptionIncident

File scans andNetApp scansmay fail because the "Profiling" and "PerformanceMonitoring" options are enabled by default in theDataModule's configurationfile (dmexplorer.conf).

1587651

In the Explorers table, an incorrect version numbermay display for explorersthat run on Linux managed hosts.

1589406

Attaching amanaged host to aManagement Server fails if themanaged host'shost name does not resolve.

1595031

Cannot run "halagentcfgmove-explorer" remotely fromaManagement Serverto a managed host.

1634096

IfCommandCentral Storage tries touseSNIAAPI todiscoverHBAs, it generatesa link error in the system log.

1635973

The installer fails to check free disk space on long file system names.1639060

If you restart the Local HAL Manager (LHM) while agents are still running, itcan result in the Duplicate Agent UUID condition.

1639792

ACSLS robots do not appear when you view information about a NetBackupinstance.

1664844

Cannot discover EMCPowerPathwhen there aremore than twopaths for eachdisk.

1676934

The Enterprise Reporter Console does not work after you install theCommandCentral managed host.

1678305

Application errors and system crashes occur on Windows hosts with QLogicHBAs.

1679775

TheHBAexplorer causes theAIXSCSI driver to log the error FSCI_ERR6whenthe explorer tries to obtain a list of target ports.

1733245

When you install themanaged host on Linux, the following errormay appear:"Error: V-1-6 Unable to load configuration"

1737207

When you view the Device Handles table, you cannot view the name of anassociated NetBackup instance.

1738595

The used capacity for a Microsoft SQL Server is incorrect.1764066

Installation of the managed host fails on a Windows 2003 64-bit host thatincludes NetBackup 6.5.1.

1766128


Table 4-2 Fixed issues that affect the managed host (continued)

DescriptionIncident

Devices unclaimed by the SCSI Generic (sg) driver on Red Hat Linux 4 and 5and SUSE Linux 9 and 10 are not discovered.

1768488

Array controller devices like /dev/dac# on AIX causes the operating systemto hang.

1787708

CommandCentral Storage reports inaccurate LUN serial numbers on HP-UXhosts.

1787716

The Storage Explorer script, hbaapp.exe crashes after you reboot a Windows2003 32-bit host that includes EMC PowerPath 5.3.

1796449

During a silent install, the installer does not report any missing operatingsystem patches.

1824266

File system monitoring causes Perl to core if the file system is corrupted. Forexample, if the file system is populated with wrong or negative values.

1824480

Table 4-3 lists the fixed issues that affect the Management Server and managedhost.

Table 4-3 Fixed issues that affect the Management Server and managed host

DescriptionIncident

The vxccs script fails to detect components.1540019

The installer does not correctly check permissions for symbolic links.1598521

The installer logs warning messages in the Windows system event log.1635831

When you install the Management Server or managed host on a non-defaultpath that includes a space, the installer fails to configure the HardwareAbstraction Layer (HAL).

1706404

The Central HAL Manager (CHM) and halcmd crash when they try to contactan explorer with a long CORBA IOR.

1726285

The installer does not check the list of operating system patches beforeinstallation on a UNIX host.

1765394

Rolling patches fail to install on a Solaris 10 host with the errormessage "exitcode 48 is unable to update the patch-finish service."

1781466


56

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.1.

NAT firewalls not supportedCommandCentral 5.1.1 does not support NAT (network address translation)firewalls. NAT firewalls configured betweenmanagedhosts and theManagementServer may cause communication failures between the CORBA services runningon the managed host and the Central HAL Manager running on the ManagementServer.

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

5Chapter

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

58

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 > Disk Groups > Destroy DiskGroup).

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.

59Software limitationsDiscovery and management limitations

Cannot discover storage pools that do not have names (1435403)If a storage pool does not have a name, CommandCentral does not discover thatstorage pool.

Size of a Celerra disk volume does not match Celerra Manager(1747844)

CommandCentral Storage reports a different size for a Celerra disk volume thanCelerra Manager does. This difference occurs because Celerra Manager roundsthe values where as CommandCentral Storage does not.

CommandCentral StoragedoesnotdiscoverNetBackupmedia changerson Windows (1810148)

By default, the Windows operating system does not include a device driver thatcan handlemedia changers. Because of this, aWindows host cannot create devicepaths for media changers.

If CommandCentral Storagediscovers aNetBackup instance that runs onWindowsand an associatedmedia changer does not have a device handle, CommandCentralStorage cannot discover the media changer.

Discovery of HBAs fails on an AIX host (1839014)Discovery of HBAs may fail on an AIX host that has stale device handles. A staledevice handle occurs when the host had access to the LUNs, but the access waslost. For example, this might occur if you unzone the array port from the HBAport or unmask a LUN that was masked earlier.

Workaround

Run the appropriate operating system tools on AIX to purge the stale devicehandles. Then, refresh the storage explorer.

To refresh the storage explorer

1 In the CommandCentral Console, click Settings > Managed Hosts.

2 In the Managed Hosts table, click the AIX host for which discovery failed.

3 In the Explorers table, check StorageExplorer.

4 In the drop-down list, click Refresh Explorer. Then, click Go.

5 In the Refresh Selected Explorer(s) dialog box, click OK.

Software limitationsDiscovery and management limitations

60

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

Cannot log in to the Console using Internet Explorer when the hostname includes an underscore (1447601)

If the Management Server’s host name includes an underscore, you cannot log into the Console using Internet Explorer. This occurs because of a limitation inInternet Explorer.

Workaround

Do one of the following:

■ If you use Internet Explorer, connect to the Console using the ManagementServer’s IP address. For example, type https://ipaddress:8443 in thebrowser’s address field.

■ Use Firefox to connect to the Console.

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.

61Software limitationsConsole and report limitations

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

4.x Agent limitationsThe following limitations apply to situations in which a CommandCentral 5.1.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.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.1 Management Server.

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

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

Data displayed for unsupported applicationsApplications no longer supported in version 5.1.1, such as Microsoft Exchange5.5, will display in the version 5.1.1 CommandCentral Storage Console while theAgent host is still running version 4.x. However, after the Agent host is upgradedto version 5.1.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.1.1Management Server to the Agent host is properly set, then all objects discoveredby the Agent are marked as missing. User-defined annotations and group

Software limitations4.x Agent limitations

62

assignments 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.1 or when its network connection tothe Management Server is broken. If you stop the Agent host so that it can beupgraded to 5.1.1, perform the upgradewithin 24 hours. Otherwise, youwill needto recreateuser-definedannotations andgroupassignments for discoveredobjects.

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:

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 examplemedia changers and tape drives, are not displayed in the version5.1.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

63Software limitations4.x Agent limitations

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.1 managed host is required.

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

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

Software limitations4.x Agent limitations

64

Known issues


■ Install, uninstall, and upgrade issues

■ Management Server and database issues

■ Managed host issues

■ Console and report issues

■ User management issues

■ Device and device configuration issues

■ Visualization issues

■ Monitoring issues

■ Discovery and management issues

■ Data Module issues

Install, uninstall, and upgrade issuesThe following are known issues that you might encounter when you install,uninstall, or upgrade CommandCentral Storage.

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)!!!

6Chapter

Workaround

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.

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

When you install the CommandCentral 5.1.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.

Workaround

Before you install a managed host, you have to reset the password on theManagementServer 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:

Known issuesInstall, uninstall, and upgrade issues

66

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:

/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.

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

67Known issuesInstall, uninstall, and upgrade issues

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:


68

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:

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.


70

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.

Formore information aboutmanagedhost silent installs, see theCommandCentralInstallation Guide.

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.

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.1 (1407023)

After you install theCommandCentral 5.1.1ManagementServer ormanagedhoston 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 witharraymanagement andNetAppunified storage capabilities to version 5.1.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.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.1(1318748)

After youupgrade aLinuxmanagedhost to 5.1.1, theArrayExplorers processmaystop.

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.1 from a Windows host, the SymantecProduction Authorization Service stops.

Workaround


72

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

CommandCentral Storage installations fail on UNIX hosts if installedon auto-mounted volumes (1173776)

If you install the Management Server or the managed host on UNIX from anauto-mounted volume, the installation fails with the message that the requireddisk space is not available. The installation fails evenwhen you have the requireddisk space for the installation.

Workaround

Ensure that you have the required disk space.

See “System resource requirements” on page 29.

Use the -nospacecheck option of the installer.

./installccstor -nospacecheck

The -nospacecheck option skips the disk space check and lets you proceed withthe installation.

Uninstalling the Management Server or managed host from UNIX fails(1673272)

When you use the uninstall script from /opt/VRTS/install to uninstall theCommandCentral Management Server or managed host, an error message thatincludes the following might appear:

Couldn't load Crypt::Blowfish_PP: Can't locate Crypt/Blowfish_PP.pm

This error occurs when the host runs a version of VRTSperl that is higher thanthe version that CommandCentral shipswith. Because of this error, uninstallationfails.

Workaround

Uninstall the Management Server or managed host with the product installer.

To uninstall the Management Server with the product installer

1 Log on to the host fromwhich youwant to uninstall theManagement Server.

2 In an operating system console, navigate to the following directory:

installer_location/MS/sol_sparc

Where installer_location is one of the following:


■ The directory in which you extracted the tar file

■ The location in which the DVD is mounted


./installer

4 At the Task Menu, type U and press Enter.

Follow the prompts to uninstall the Management Server.

To uninstall the managed host with the product installer

1 Log on to the host from which you want to uninstall the managed host.

2 In an operating system console, navigate to the following directory:

installer_location/MH/platform

Where:

is one of the following:

■ The directory in which you extracted the tar file

■ The location in which the DVD is mounted

installer_location


■ aix

■ hpux

■ linux_i686

■ sol_sparc

platform

3 To uninstall the managed host, type the following command:

./uninstallccsmh

Follow the prompts to uninstall the managed host.

Installer freezes during install of the Management Server on a Windowshost that runs Storage Foundation (1800374)

When you install the Management Server on a host that includes StorageFoundation for Windows, the CommandCentral installer may freeze.

Workaround

Before you proceed with installation, stop the following services:

■ Veritas Action Agent (actionagent)


74

■ Veritas GridNote (vxgn)

■ Veritas Storage Agent (vxvm)

■ Veritas Enterprise Administrator Service (vxob)

In Windows' Task Manager, ensure that the vxsvc.exe process is not running.vxsvc.exe is the process name for the Veritas Enterprise Administrator Service.

Install on a HP-UX host may fail if run from a Linux NFS server'smounted volume (1742038)

Installation (clean install or upgrade) of the CommandCentral Storage packageon a host that is running the HP-UX operating system may fail. This issue relatesto NFS and occurs if you run the installer from a mount volume that is located ona Linux NFS server.

The LinuxNFS servermaynot be providing a lock to theHP-UXadmin commands,such asswinstall and swcopy. If so, it is possible that the Linux NFS server wascreated without the insecure_lock lock option being provided. When this issueoccurs, the following lock creation error displays:

ERROR: <host_name>:/<mount_location>:

This target or source is already in use either within this same

session or by another session. A read or write lock was denied.

* Source connection failed for <host_name>:<mount_location>

Workarounds: Use either workaround A or B as appropriate for your situation:

A. Run the installer from a host that is running an operating system other thanLinux, and mount that host on the HP-UX host.

B. Edit the /etc/exports file to add the two required options, insecure_locksand insecure (if they are missing).

These options allow the HP-UX admin commands to create a read lock on the filesystem. You want the following entry in /etc/exports file on the Linux host toappear as follows:

/cc_downloads/cc_builds *.*(rw)

To edit the /etc/exports file

1 On the Linux host, open the /etc/exports file in a text editor.

2 Add the two required options, insecure_locks and insecure (if needed).


3 Edit the /etc/exports file as follows:

</cc_downloads/cc_builds> *.*(rw,sync,insecure_locks,insecure)

where

</cc_downloads/cc_builds> is theNFSnameyouused to create theNFS server,

*.* represents any machine can use this NFS server, and

data in the () are the options provided to the NFS.

4 Run the following command:

`exportfs -ra`

5 Run the installer again.

Installation of the Management Server fails on a Solaris 10 host withlocal zones and Storage Foundation 5.1 (1843473)

If you try to install the Management Server on a Solaris 10 host that has one ormore local zones configured and Storage Foundation 5.1 installed, installationfails with the following message:

Installation will terminate now on <hostname> due to the presence of

modified Symantec packages.

Workaround

Do one of the following:

■ Use a CPI patch

■ Change the value of SUNW_PKG_ALLZONES from false to true

To use a CPI patch

1 Go to the Symantec Patch Central Web site to download the CPI patch.

vias.symantec.com/labs/patch/

2 Follow the instructions in the patch's readme.

To change the value of SUNW_PKG_ALLZONES from false to true

1 On the host where you want to install the Management Server, go to/var/sadm/pkg/VRTSat

2 Open the file pkginfo

3 Change the value of SUNW_PGK_ALLZONES from false to true.


76

https://vias.symantec.com/labs/patch/

4 Install the Management Server.

5 After installation completes, change the value of SUNW_PGK_ALLZONESfrom true to false.

Some explorers not configured on a managed host upgraded from 5.0MP1 (1844084)

If you upgrade a 5.0 MP1 managed host with data module only configuration to5.1, the installer does not configure some of the CommandCentral explorers. Ifyou only want to use thismanaged host to scan file systems andmail servers, thisis not an issue. However, if you want to discover applications with the managedhost, it cannot do so because the explorers are not configured.

This issue does not occur when you upgrade a 5.0 MP1 managed host with datamodule only configuration directly to 5.1.1. It does occur when you upgrade a 5.0MP1 managed host with data module only configuration to 5.1 and then to 5.1.1.

Workaround

To configure the explorers, do the following:

■ Uninstall the managed host. When you uninstall the managed host, backupdata and configuration files.

■ Install the 5.1.1 managed host.

■ Restore the configuration. For example, you may have configured a database(Sybase or Oracle) or youmay have changed polling intervals, debug levels, ortimeout intervals.

Management Server and database issuesThe following are known issues that you might encounter with the ManagementServer 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.

77Known issuesManagement Server and database issues

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.

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.

Known issuesManagement Server and database issues

78

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.

Oracle ASM Disk Group's ASM DG Used by Other Hosts value misplaced(1795293)

When you view the Host Storage Usage table, on the Reporting > Storage >Storage Consumption Detail pane, a capacity value for a particular host canappear in the wrong table cell. In certain circumstances, the value for the ASMDG Used by Other Hosts (GB) column appears in the ASM DG Used: Unknown(GB) column.

The misplaced table value occurs with a host that contains a standalone Oracledatabase, which is consuming storage from a shared ASM Disk Group (DG), andwhen the shared ASM DG has following characteristics:

■ It is shared across at least three hosts

■ It bears a RAC instance on other hosts


The command "net start VRTSsmweb" fails (1806029)If you run the command "net start VRTSsmweb" on a Windows ManagementServer, the command may fail:

The Veritas Storage Management Web Console service is starting........

The Veritas Storage Management Web Console service could not be

started.

Workaround

79Known issuesManagement Server and database issues

UseWindows' Service Control Manager to start the Veritas StorageManagementWeb Console service.

The halnetcheck utility fails (1795572)If you run the halnetcheck utility, an error may appear. For example, if you runthe command "halnetcheck check-connectivity -hhost_name" the following errormay appear:

Failed to contact host_name halnetcheck.

Segmentation fault

This error occurs when the current working directory from which you run theutility is not writable by the login user. The utility attempts to open and write toa log file in the current working directory. If that directory is not writable,halnetcheck cannot create the file, and the utility fails.

Workaround

Run the command from a writable directory.

Managed host issuesThe following are known issues that youmight encounterwith themanaged host.

CommandCentral services do not start after you reboot a Windowsmanaged host (1799326)

After you reboot a Windows managed host, CommandCentral services may notstart.

Workaround

You can use the vxccs script to restart the services. However, to ensure that theservices start after you reboot the host, you need to create or modify theServicesPipeTimeout registry setting.

To modify the ServicesPipeTimeout registry setting

1 Click Start > Run.

2 In the Run dialog box, type regedit and click OK.

3 In Registry Editor, navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

4 Do one of the following:

Known issuesManaged host issues

80

Proceed to step 5.If theServicesPipeTimeoutvalue is present

Do the following:

■ Click Edit > New > DWORD Value.■ Type ServicesPipeTimeout and press Enter.

If theServicesPipeTimeoutvalue is not present

5 Right click ServicesPipeTimeout and click Modify.

6 In the Base field, select Decimal.

7 In the Value data field, enter 300000 and click OK.

The value 300000 is in milliseconds and is equivalent to five minutes.

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.

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

81Known issuesConsole and report issues

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


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 the

Known issuesConsole and report issues

82

operation 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.1.

The Topology Map’s Print Preview displays a blank page (1206846)TheTopologyMap's Print Previewdisplays a blankpage 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.

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.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."


84

Workaround

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

Unknown storage capacity used by Celerra's storage hierarchy(1800033)

A gap exists between the reported capacity values that are shown for PhysicalandLogical storage. You can view this issue in theTotalUnifiedStorage bar chartin the Online Storage Capacity Summary pane at Reporting > Storage. TheCelerra's storage hierarchy uses the unknown storage capacity within that gap.The Logical Unknown category accounts for this capacity.


Incorrect masking status for the LUNs for a Celerra unified storagesystem (1786011)

When you view the LUNs for a Celerra unified storage system, themasking statusfor a LUN may display as unmasked when it should be masked. This incorrectstatus occurs when multiple LUNs are masked to an initiator and the LUNs arenot in a range that is continuous.

For example, if you mask a set of LUNs in the range of 1 to 5, and then maskanother set of LUNs in the range of 15 to 20, CommandCentral Storage showsonly those LUNs in the first range or second range, but not both of the ranges. Asa result, the masking status for the LUNs appears as unmasked.

This incorrect masking status affects the Online Storage Capacity Detail report.If you compare the allocated, unallocated, and claimed capacities that appear inthe LUNs table in the Online Storage Capacity Detail report, they will not matchthe capacities that appear in the Online Storage Capacity Summary report.

Console shows disk as part of an Oracle ASM disk group after it wasremoved from the disk group (1823721)

If you remove a disk from an Oracle ASM disk group, the Console continues toshow the disk as part of that disk group until one of the following occurs:

■ You add the disk to another disk group

■ The disk is no longer accessible to the ASM instance


Even though the Console continues to show the disk as part of the disk group, thecapacity values for the disk group do not include the disk.

Table column values that contain plus signs are not saved (1795869)When you save any table that contains a plus sign (+) in any value in the tablecolumns, the value appears as "#NAME" in the exported file. For example, Oracledatabase instances contain a plus sign in their display names, so they exhibit thisissue.


Distribution of Storage by Interface is displaying "Fibre" for unmaskedLUNs (1832384)

Unmasked iSCSI LUNs appear under the Fibre category in the Online StorageCapacity Summary's Distribution of Storage by Interface pie chart.

Also,whenyou click theFibre category in theDistributionofStoragebyInterfacepie chart, theOnlineStorageCapacityDetail report appears with its LUNs table.In the LUNs table's Interface column, the unmasked iSCSI LUNs are marked asFibre.

Workaround: None available.

Allocation of Array Storage by Vendor for EMC displays NetApp arrays(1832996)

This issue is visible if you drill down in Reporting > Online Storage Capacity >Summary >Allocation of Array Storage byVendor" bar chart, and click a capacityvalue (other than Logical Virtualizer Source Capacity) for a particular vendor.

For vendors (other thanNetApp), theOnlineStorageCapacityDetail report appearswith its NAS and Unified Storage table and Arrays table. The data in the NAS andUnified Storage table is not filtered according to the vendor that was clicked intheSummarypane, so the table'sVendor column includesnot only theNASdevicesfor the arrays for the vendor selected, but also those for other vendor's NASdevices.

Workaround: Use the NAS and Unified Storage table's table-settings to filter sothat the vendor column shows only the applicable vendor.


86

Reported 3PAR storage capacity numbers do not match (1834265)If your environment contains configured 3PAR arrays aswell as other arrays thathave the same RAID configuration as the 3PAR arrays, two entries for that RAIDconfiguration appear in the Online Storage Capacity Summary pane'sDistribution of Storage by RAID Level pie chart. The capacity numbers shownin the Summary pane will not match those shown in the Detail pane's report.

Workaround: None exists.

User management issuesThe following issues relate to user management.

Domains not available for user accounts and user groups (1792352)If you install theManagement Server on ahost that includesVeritas Cluster ServerOne, you may experience problems with domains. For example, if you add a newuser account or user group, domains may not appear when you try to select adomain from the drop-down list.

Workaround

Use the commandaddbrokerdomain tomapadomain to theAuthenticationBroker.

To use the command addbrokerdomain to map a domain to a broker

1 Log on to the Authentication Broker host and open an operating systemconsole. For example, if you run theManagement Server inRB+ABmode (thedefault mode when you install), log on to the Management Server.

2 Change to the Authentication Service CLI (vssat) directory. By default, thedirectory is:

/opt/VRTSat/binSolaris

\Program

Files\VERITAS\Security\Authentication\bin

Windows


vssat addbrokerdomain -b host:port -d domain_type:domain_name

Where:

87Known issuesUser management issues

is the host nameof theAuthenticationBroker host. For example,if you run the Management Server in RB+AB mode (the defaultmodewhen you install), enter the host name of theManagementServer.

host

is the port for authentication. By default, the port is 2821.port


■ GSS

■ ldap

■ nis

■ nisplus

■ nt

■ pam

■ unixpwd

■ vx

domain_type

is the name of the domain.domain_name

After you run the command, you can select the domain in CommandCentral.

Device and device configuration issuesThe following are known issues that youmight encounter with supported devicesand device configuration in CommandCentral Storage.

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.

Known issuesDevice and device configuration issues

88

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.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.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.

89Known issuesDevice and device configuration issues

IBM SAN Volume Controller (SVC) SICL Status value unavailable(1743398)

When you select an IBM SVC object on the Managing Summary > Arrays pane,and then select the Monitoring tab, no value apears for the object's SICL Statusin the State Collectors table.

Workaround: None currently available.

Refreshing the storage explorer fails on a host with no physical FibreChannel HBAs (1798710)

If you run theManagement Server ormanaged host on a host that has no physicalHBAs and you refresh the storage explorer, the task fails. If you view the TaskStatus pane, the status detail for the task is as follows:

Detect Devices for Devices failed. Explorer Name: StorageExplorer.

ExplorerID: StorageExplorer@host_name.com.

StorageExplorer SNIA Common HBA API library is not properly

installed on this computer (V-32-35-73)

Request Failed

You can ignore this error. Even though the error appears, rediscovery completedsuccessfully.

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

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 asamixedMeta. Due to an issue inCommandCentral Storage 5.1.1, suchmixedMetaLUNs 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.

Known issuesVisualization issues

90

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

ForRAIDgroupsonHitachi arrays, user-definedattributes andgroupmembershipsare notmigrated from version 4.x to version 5.1.1. Youwill 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.

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

91Known issuesMonitoring issues

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

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.

Known issuesMonitoring issues

92

■ 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.

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.

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).

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.1(1435097)

If you configure aCisco switch for discovery inCommandCentral 5.1.1,monitoringmay not be available for that switch. This does not affect Cisco switches that wereconfigured in previous versions of CommandCentral Storage.

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.


94

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.


Monitoring favorites not available after an upgrade (1781686)Monitoring favorites that are set before upgrading CommandCentral Storage areunavailable following the upgrade. The upgrade process intentionally discardsthemonitoring links' session ID as part of the upgrade,which causes the favoritesto also be discarded. The upgrade does not cause this issue, and the upgrade isunaffected.

Workaround

Reset the monitoring favorites following an upgrade.

Monitoring data for Cisco ports does not appear after upgrade to 5.1.1(1834204)

After you upgrade to CommandCentral 5.1.1,monitoring data for Cisco portsmaynot appear in the Console.

Workaround

After you upgrade to 5.1.1, wait a few hours for the data to appear. If the datadoes not appear after a few hours, restart the Alarm Service.

To restart the Alarm Service (Solaris)

1 Log on to the Management Server and open an operating system console.

2 Change to the following directory:

/opt/VRTSccs/VRTSccsts/bin

3 Type the following commands:

./vxccs stop vxasd

./vxccs start vxasd


To restart the Alarm Service (Windows)

1 Log on to the Management Server and open Windows' Services utility.

2 Restart the following process:

Veritas CommandCentral Storage Alarm Service

Alarm Service configuration reverts to default values after upgradingSolaris Management Server to 5.1.1 (1714407)

When you upgrade a Solaris Management Server to CommandCentral 5.1.1,configuration parameters for theAlarmService (VxAS) are reset to default values.In other words, if you had modified any configuration parameters for the AlarmService in a previous release, those changes are not retained. The onlyconfiguration parameters that are retained are those related to internal SNMPpolls and alarms. If you did not modify configuration parameters for the AlarmService, this issue does not affect your Management Server.

For example, some of the common configuration parameters that youmight havechanged are as follows.

Table 6-1 Commonly changed configuration parameters for the Alarm Service

Default valueParameter

10000QueueSizeHighWaterMark

2500QueueSizeLowWaterMark

32604ServerConnPort

120MaxLogEntryAge

5024MaxLogFileSize

1000MaxQueueDepth

161DefaultPort

publicDefaultSnmpCommunity

10SnmpInterval

3SnmpRetry

5431VxAMServerPort

yesRegisterAttributesAsIds


96

Workaround

To change the configuration parameters back to their previous values, contactSymantec Technical Support.

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

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.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.

97Known issuesDiscovery and management issues

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.

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:

Known issuesDiscovery and management issues

98

■ 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.

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 a previous version and then you upgrade to 5.1.1 and migrate discovery of theswitch to SMI-S, CommandCentral does not discover inactive defined zones andinactive 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 (1239973)

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.

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

For a 4.x managed host that reports to a 5.1.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.

Wrong operating system displays for a storage view (1232117)After you build a storage view for SMI-S managed IBM DS4000 storage arrays orEngenio (LSI) storage arrays, theOSType for that storage viewdisplays as Solaris,even if that is not the correct operating system.


Explorers do not start after rebooting a SUSE Linux managed host(1469398)

After you reboot a SUSE Linux managed host, the managed host's explorers donot start.

Workaround

Start the explorer processes manually.

To start the explorer processes manually

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


/opt/VRTS/bin/vxccs start

The explorer processes start.

LUNs not masked to array ports for Celerra unified storage devices donot appear (1810799)

When you view details about a Celerra unified storage device, CommandCentralStorage displays the iSCSI LUNs that are masked to a target port. LUNs that arenot masked to a port do not appear.


Celerra explorer does not discover all file systems (1802239)CommandCentral Storagediscovers default file systems (uxfs) and raw file systems(rawfs) for an EMC Celerra unified storage system.

CommandCentral Storage does not discover the following types of file systemsfor an EMC Celerra unified storage system:

■ Mount


100

■ Group

■ Mirrored

■ Migration

Hitachi HiCommand WMS storage array appears twice after upgrade(1796494)

If CommandCentral discovers a Hitachi HiCommand WMS storage array beforeyou upgrade to 5.1.1, the device appears twice in the Console after you upgrade.The discovery state for one of the devices displays as missing. You can eithermanually delete the missing array or you can wait until CommandCentralautomatically purges the array from the database.

Because the device appears twice, the following occurs:

■ In the Configured Devices Summary table, the state of the discovered devicedoes not appear until the following occurs:

■ You manually delete the missing array or CommandCentral automaticallypurges the array from the database.See “To manually delete the missing array” on page 101.

■ You restart the explorer that discovers the device.See “To restart a device explorer or application explorer” on page 102.

■ In CommandCentral Storage Change Manager, if a policy is applied on ahost-to-LUN pair for the array, then you have to remove the policy and thenre-apply it.For information about policies, see the CommandCentral Storage ChangeManager User’s Guide.

■ In CommandCentral Storage Change Manager, if you view the changes thatare associated with the array before you upgraded and click any links thatappear in the change message, an error appears.

■ In CommandCentral Storage, if click the "Change History" link, whenCommandCentral Storage Change Manager loads, the Changes pane does notinclude the changes that were associated with the array before you upgraded.

To manually delete the missing array

1 In the CommandCentral Console, click Managing > Storage > Arrays.

2 In the Arrays pane, select the missing array.

3 In the drop-down list, click Delete Array. Then, click Go.

4 In the Delete dialog box, click OK.


To restart a device explorer or application explorer

1 On the host on which you want to restart the explorer, open an operatingsystemconsole and log in as root (UNIX) or as a userwith administrator-levelprivileges (Windows).

2 Change to the directory where the halagentcfg script resides. By default,the location is as follows:

UNIX: /opt/VRTSccs/VRTShal/bin

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

3 To identify the name of the explorer that youwant to stop, type the followingcommand:

halagentcfg list-explorer-types

For more information about each explorer, see the CommandCentralAdministrator’s Guide.

4 To identify the process under which the explorer runs, type the followingcommand:

halagentcfg list-explorers --explorer-name ExplorerName --details

Where ExplorerName is the name of the explorer that you obtained in theprevious step.

5 To stop the process under which the explorer runs, type the followingcommand:

halagentcfg stop-process --process-name ProcessName

Where ProcessName is the name of the process that you obtained in theprevious step.

6 To start the process under which the explorer runs, type the followingcommand:

halagentcfg start-process --process-name ProcessName

The process restarts.

Discovery error for EMC Celerra unified storage system if debug levelis not 1 (1835013)

If you discover an EMC Celerra unified storage system on a Windows host andchange the debug level for the Celerra explorer to something other than 1, adiscovery error occurs.


102

Toensure that CommandCentral discovers anEMCCelerra unified storage system,keep the explorer's debug level at 1.

No correlation between storage pool and associated disk volume foran EMC Celerra unified storage system (1785031)

When you view details about a storage pool for an EMC Celerra unified storagesystem, the Console does not show the disk volumes from which the storage poolwas created.

Incorrect number of file systems for an EMC Celerra unified storagesystem (1803708)

When you view the Overview pane for an EMC Celerra unified storage system, inthe attributes box next to the Physical Capacity chart, the total for the # of NASFile Systems is incorrect. The count is incorrect because it includes the numberof root file systems. You cannot mount a root file system to a data mover. Thetotal number of file systems should include only those file systems that youmountto a physical data mover or a virtual data mover.

To view the correct number of file systems, view the NAS File Systems table.

The available capacity for an Oracle ASM disk group is incorrect(1835478)

Oracle calculates the available capacity for an ASM disk group based on thecapacity of the failure group that is the smallest. Oracle recommends that allfailure groups have the same capacity for better utilization and performance.

CommandCentral Storage calculates the available capacity for anASMdisk groupby taking the total capacity of all failure groups and dividing it by the redundancylevel. Because of this calculation, if all failure groupsdonothave the same capacity,CommandCentral Storage displays an incorrect available capacity for an OracleASM disk group.

The following example showshowOracle andCommandCentral Storage calculatethe capacity for two failure groups that have different capacities.


10 GB

10 GB

8 GB

8 GB

8 GB

(10+8) / 2=

9 GB

Failuregroup 1

Failuregroup 1

Failuregroup 2

Failuregroup 2

Leastcapacity

Total capacity /RAID level

Oracle:

CommandCentral Storage:

IP address may not display for a Celerra unified storage system(1798405)

If you view the NAS andUnified Storage Systems pane, in the Virtualization NASand Unified Storage Summary table, an IP address may not appear for a Celerraunified storage system.

Workaround

Restart the NASExplorers process.

To restart the NASExplorers process

1 Log on to the host that discovers the Celerra unified storage systemand openan operating system console.

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

/opt/VRTSccs/VRTShal/binSolaris

\Program Files\VERITAS\CommandCentral

Storage\HAL\bin

Windows

3 Type the following commands:

halagentcfg stop-process -p NASExplorers

halagentcfg start-process -p NASExplorers


104

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.

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.

105Known issuesData Module issues

Known issuesData Module issues

106

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

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

CommandCentralStorageReleaseNotes

7Chapter

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.

To ensure that new manual pages display correctly

1 Update your:

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

Getting helpDisplaying online help

108

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


■ 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:


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.

109Getting helpContacting Symantec



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

110


Veritas CommandCentral™ Storage Release Notes · The product described in this document is...

Documents

Transcript of Veritas CommandCentral™ Storage Release Notes · The product described in this document is...