Veritas CommandCentral™ Release Notes · CommandCentral Storage Release Notes ... Requirements to...

Veritas CommandCentral™Release Notes

for Microsoft Windows and UNIX

5.1.2

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

Installation overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Issues fixed in CommandCentral 5.1.2 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10What’s new in CommandCentral 5.1.2 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Configuringout-of-banddiscoveryofBrocade switches throughSNMP

and telnet ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12DeviceCredentials panel options forBrocade switches discovered

through SNMP and telnet ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Configuring out-of-band discovery of McDATA switches through

SNMP and telnet ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Device Credentials panel options for McDATA switches

discovered through SNMP and telnet ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Requirements to discover TrueCopy pairs for Hitachi HiCommand

arrays ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Requirements to discover masking information for V-Max

arrays ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Sample SQL query to view information about all devices associated

with EMC Symmetrix thin pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Sample SQL query to view information about Dynamic Provisioning

pool IDs for HDS USP-V LDEVs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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

Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Supported locales ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Solaris updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . 23Windows updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . 27HP-UX updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . 27AIX updates required for CommandCentral ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Red Hat Linux updates required for CommandCentral ... . . . . . . . . . . . . . . . . 29

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

products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Contents

Supported versions of CommandCentral Storage for rolling up datato Enterprise Reporter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Software limitations in this release ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 4 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Known issues in this release ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Device mapping only discovered for port 0 of directors for EMC

Symmetrix V-Max arrays (1926195) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 5 Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About CommandCentral Storage documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Displaying online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Contacting Symantec ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

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

Contents8

Overview of this release

This chapter includes the following topics:

■ Installation overview

■ Issues fixed in CommandCentral 5.1.2

■ What’s new in CommandCentral 5.1.2

■ Configuring out-of-band discovery of Brocade switches through SNMP andtelnet

■ Configuring out-of-band discovery of McDATA switches through SNMP andtelnet

■ Requirements to discover TrueCopy pairs for Hitachi HiCommand arrays

■ Requirements to discover masking information for V-Max arrays

■ Sample SQL query to view information about all devices associated with EMCSymmetrix thin pools

■ Sample SQL query to view information about Dynamic Provisioning pool IDsfor HDS USP-V LDEVs

Installation overviewCommandCentral 5.1.2 is an update to the CommandCentral 5.1.1 release. The5.1.2 release includes updates to CommandCentral Storage andCommandCentralStorage Change Manager. You can update the following components to 5.1.2:

■ Management Server

■ Managed host

■ Managed host with array and switch explorers (also known as the "controlhost")

1Chapter

You can only upgrade to CommandCentral 5.1.2 from5.1.1. If you have a previousversion, you need to upgrade to 5.1.1 first.

You can find installation instructions in the 5.1.2 readme. You can find the readmein the 5.1.2 installation file that you download from FileConnect.

Issues fixed in CommandCentral 5.1.2You can find the list of issues fixed in this release in the 5.1.2 readme. You canfind the readme in the 5.1.2 installation file that you download from FileConnect.

What’s new in CommandCentral 5.1.2CommandCentral 5.1.2 contains and builds upon 5.1.1 functionality, providingseveral new features and enhancements.

For information about support for the devices that are listed in the following table,see the CommandCentral Hardware and Software Compatibility List.

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

Table 1-1 New features and enhancements

DescriptionFeature

CommandCentral cannowdiscoverBrocadeandMcDATAswitchesthroughSNMPand telnet. CommandCentral uses SNMP for fabricdiscovery and telnet for zone discovery.

For information about configuring CommandCentral to discoverBrocade and McDATA switches through SNMP and telnet, referto the following:

See “Configuring out-of-band discovery of Brocade switchesthrough SNMP and telnet” on page 12.

See “Configuring out-of-band discovery of McDATA switchesthrough SNMP and telnet” on page 15.

Brocade and McDATAswitch discovery andzone discoverythrough SNMP andtelnet

CommandCentral can now discover IBM DB2 9.x databases. Thisincludes the EEE version and standalone version.

Discovery of IBM DB29.x databases

Overview of this releaseIssues fixed in CommandCentral 5.1.2

10

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

Table 1-1 New features and enhancements (continued)

DescriptionFeature

CommandCentral can now discover Hitachi HiCommandreplication objects that you create with the following Hitachisoftware:

■ TrueCopy

■ Copy-on-Write Snapshot (COW)

You can view the replication objects in the Replication pane for aHitachi HiCommand storage array.

For device setup requirements to discover TrueCopy pairs, referto the following:

See “Requirements to discover TrueCopy pairs for HitachiHiCommand arrays” on page 18.

Discovery ofreplication objects forHitachi HiCommandstorage arrays

CommandCentral can now discover VMware ESX 4.0.Discovery of VMwareESX 4.0

CommandCentral cannowdiscoverEMCSymmetrixV-Maxarrays.Support includes discovery of SE and ME models.

For device setup requirements to discover masking information,refer to the following:

See “Requirements to discover masking information for V-Maxarrays” on page 19.

Discovery of EMCSymmetrix V-Maxarrays

CommandCentral cannow identify regular thin devices by vendorlayout for EMC Symmetrix storage arrays.

When you view an EMC Symmetrix storage array in the Console,the Vendor Layout attribute for thin devices appears as TDEV inthe tables that display the devices.

Note:A thin device (TDEV) does not have any associated physicaldisks. Because there are no associated physical disks, the Diskstable does not display any data in the device’s Overview pane.

Note: We do not support discovery of vendor layout for thindevices used in SRDF configurations.

Discovery of EMCSymmetrix thindevices

11Overview of this releaseWhat’s new in CommandCentral 5.1.2

Table 1-1 New features and enhancements (continued)

DescriptionFeature

CommandCentral can now discover thin pool names for EMCSymmetrix devices.

When you view an EMC Symmetrix storage array in the Console,the thin pool name appears in the Attributes pane for the device.The attribute is titled PoolId.

You can also create an ad-hoc report to view information aboutall devices associated with thin pools. You can do this with asample SQL query.

See “Sample SQL query to view information about all devicesassociated with EMC Symmetrix thin pools” on page 19.

Discovery of thin poolnames for EMCSymmetrix devices

CommandCentral can now discover RAID-6 devices for EMCSymmetrix arrays.

Discovery of RAID-6devices for EMCSymmetrix arrays

In previous releases, CommandCentral required NaviCLI todiscover EMC CLARiiON storage arrays. CommandCentral nowsupports discovery of CLARiiON arrays if only NaviSecCLI isinstalled.

Discovery of EMCCLARiiON arraysthrough NaviSecCLI

CommandCentral can now discover the Dynamic Provisioningpool IDs forHDSUSP-V LDEVs that are associatedwith the pools.

You can create an ad-hoc report to view information about poolIDs for LDEVs. You can do this with a sample SQL query.

See “Sample SQL query to view information about DynamicProvisioning pool IDs for HDS USP-V LDEVs” on page 19.

Discovery of DynamicProvisioning pool IDsfor HDS USP-V LDEVs

Configuring out-of-band discovery of Brocadeswitches through SNMP and telnet

You can discover Brocade switches through SNMP and telnet. CommandCentraluses SNMP for fabric discovery and telnet for zone discovery.

When you configure discovery of a Brocade switch, CommandCentral discoversall other Brocade switches in the fabric. You can, however, configure discoveryof more than one switch to provide failover. For example, you might configurediscovery of two Brocade switches in the fabric. If one of the configured switchesgoes down, CommandCentral can continue to discover all switches in the fabric.

Overview of this releaseConfiguring out-of-band discovery of Brocade switches through SNMP and telnet

12

To configure a Brocade switch for discovery through SNMP and telnet

1 Click Tools > Configure a New Device.

2 In the Configure Device - Select Device Type panel, select the device that youwant to configure. Then, click Next.

3 In the Configure Device - Select Explorer panel, select the host that youwantto discover the device. Then, click Next.

This panel displays only if youhavemore than onehost that runs the explorerthat discovers the selected device.

4 In the Configure Device - Device Credentials panel, enter the requiredinformation. Then, click Next.

See “DeviceCredentials panel options forBrocade switchesdiscovered throughSNMP and telnet” on page 13.

5 In the Configure Device - Status panel, click Finish.

Device configuration completes.

Device Credentials panel options for Brocade switches discoveredthrough SNMP and telnet

Use this panel to enter information about the Brocade switch that you wantCommandCentral to discover through SNMP and telnet.

Table 1-2 Configure Device - Device Credentials panel options for Brocadeswitches

DescriptionField

Enter the IP address or nameof the Brocade switch that youwantCommandCentral to discover.

When CommandCentral discovers this switch, it discovers allother Brocade switches in the fabric.

Brocade, McDATASwitch or EFCM IPAddress or Name

Select the SNMP version (1, 2c, or 3) used by the switch. Thedefault is 2c.

If the switch’s firmware is FOS 5.0.4 or greater, we recommendSNMP version 2c or 3.

If the switch’s firmware is less than FOS 5.0.4, we recommendSNMP version 1.

SNMP Version

13Overview of this releaseConfiguring out-of-band discovery of Brocade switches through SNMP and telnet

Table 1-2 Configure Device - Device Credentials panel options for Brocadeswitches (continued)

DescriptionField

If you chose SNMP version 3, select the security level associatedwith the SNMP user name for the account in the switch. This isthe user name that you enter in the SNMP Username field.

You can choose from the following security levels:

■ noAuthNoPriv (no authentication and no privacy)

■ authNoPriv (authentication and no privacy)

■ authPriv (authentication and privacy)

SNMP Security Level

If you chose SNMPversion 3, enter the user name for the accountin the switch. The account can have read-only permissions.

SNMP Username

If you chose SNMP version 3 and the SNMP security level isauthNoPriv or authPriv, enter the password for the SNMP username.

Configuration may fail if the authentication password phrase isless than 10 characters. Configure a password longer than 10characters for SNMP version 3 on the switch.

SNMP AuthenticationPassword Phrase

If you chose SNMP version 3 and the SNMP security level isauthPriv, enter the privacy password phrase for the SNMP username.

SNMPPrivacyPasswordPhrase

If you chose SNMP version 3 and the SNMP security level isauthNoPriv or authPriv, select the authentication protocolassociated with the SNMP user.

SNMP AuthenticationProtocol

This field is read-only. The field exists for legacy compatibilitypurposes.

SNMP Privacy Protocol

If you chose SNMP version 1 or 2c, enter the SNMP Communityname for the switch. The default community string is public. AnSNMP Community is an authentication scheme that enables anintelligent network device to validate SNMP requests. Do notleave this field blank.

SNMP CommunityString

Enter the telnet login for the switch. The account can haveread-only permissions. CommandCentral uses telnet for zonediscovery.

Switch Telnet Login

Enter the telnet password for the switch.SwitchTelnet Password

(Optional) Enter a user-friendly name to identify the switch.Configuration Name

Overview of this releaseConfiguring out-of-band discovery of Brocade switches through SNMP and telnet

14

Table 1-2 Configure Device - Device Credentials panel options for Brocadeswitches (continued)

DescriptionField

Check to enable zonediscovery of the switch. This field is checkedby default.

Enable ZoningDiscovery

Check to enable discovery of the switch. This field is checked bydefault.

Enable Discovery


Device Manager

Check to enable retry of a failed command. This field is checkedby default.

AttemptErrorRecovery

Enter the amount of time to wait before retrying a command.The default is 1 minute.

ErrorRecoveryTimeout(minutes)

Check to verify that CommandCentral can contact the switchwith the information that you entered.

Verify DeviceConfiguration

Configuring out-of-band discovery of McDATAswitches through SNMP and telnet

You can discover McDATA switches through SNMP and telnet. CommandCentraluses SNMP for switch discovery and telnet for active zone discovery.

To configure discovery of McDATA switches you can do either of the following:

■ ConfigureCommandCentral todiscoverEnterpriseFabricConnectivityManager(EFCM).WhenCommandCentral discoversEFCM, it discoversall of theMcDATAswitches that EFCM manages.

■ Configure CommandCentral to discover each individual McDATA switch.

To configure a McDATA switch for discovery through SNMP and telnet

1 Click Tools > Configure a New Device.

2 In the Configure Device - Select Device Type panel, select the device that youwant to configure. Then, click Next.

3 In the Configure Device - Select Explorer panel, select the host that youwantto discover the device. Then, click Next.

This panel displays only if youhavemore than onehost that runs the explorerthat discovers the selected device.

15Overview of this releaseConfiguring out-of-band discovery of McDATA switches through SNMP and telnet

4 In the Configure Device - Device Credentials panel, enter the requiredinformation. Then, click Next.

See “Device Credentials panel options for McDATA switches discoveredthrough SNMP and telnet” on page 16.

5 In the Configure Device - Status panel, click Finish.

Device configuration completes.

Device Credentials panel options for McDATA switches discoveredthrough SNMP and telnet

Use this panel to enter information about the McDATA switch that you wantCommandCentral to discover through SNMP and telnet.

Table 1-3 Configure Device - Device Credentials panel options for McDATAswitches

DescriptionField

Enter one of the following:

■ The IP address or name for theEnterprise Fabric ConnectivityManager (EFCM).

When CommandCentral discovers EFCM, it discovers all ofthe McDATA switches that EFCM manages.

■ The IP address or name of a McDATA switch.

This enables CommandCentral to discover this switch only.

Brocade, McDATASwitch or EFCM IPAddress or Name

Select the SNMP version (1, 2c, or 3) used by the switch. Thedefault and recommended version is 2c.

SNMP Version

If you chose SNMP version 3, select the security level associatedwith the SNMP user name for the account in the switch. This isthe user name that you enter in the SNMP Username field.

You can choose from the following security levels:

■ noAuthNoPriv (no authentication and no privacy)

■ authNoPriv (authentication and no privacy)

■ authPriv (authentication and privacy)

SNMP Security Level

If you chose SNMPversion 3, enter the user name for the accountin the switch. The account can have read-only permissions.

SNMP Username

If you chose SNMP version 3 and the SNMP security level isauthNoPriv or authPriv, enter the password for the SNMP username.

SNMP AuthenticationPassword Phrase

Overview of this releaseConfiguring out-of-band discovery of McDATA switches through SNMP and telnet

16

Table 1-3 Configure Device - Device Credentials panel options for McDATAswitches (continued)

DescriptionField

If you chose SNMP version 3 and the SNMP security level isauthPriv, enter the privacy password phrase for the SNMP username.

SNMPPrivacyPasswordPhrase

If you chose SNMP version 3 and the SNMP security level isauthNoPriv or authPriv, select the authentication protocol thatis associated with the SNMP user.

SNMP AuthenticationProtocol


SNMP Privacy Protocol

If you chose SNMP version 1 or 2c, enter the SNMP Communityname for the switch. The default community string is public. AnSNMP Community is an authentication scheme that enables anintelligent network device to validate SNMP requests. Do notleave this field blank.

SNMP CommunityString

Enter one of the following:

■ If you entered the IP address or name of a McDATA switch,enter the telnet login for the switch.

■ If you entered the IP address or name of EFCM, enter thetelnet login for a switch that EFCM manages.

The account can have read-only permissions. CommandCentraluses telnet for zone discovery in a fabric.

If you configure discovery of severalMcDATA switches, you onlyneed to supply telnet credentials for at least one switch in thefabric. CommandCentral can perform zone discovery throughone switch. However, we recommend that you supply telnetcredentials for more than one switch in a fabric. This providesfailover as CommandCentral can still discover zoning if the firstswitch goes down.

If you configure discovery of EFCMand EFCMmanages switchesinmultiple fabrics, enter telnet credentials that work for at leastone switch per fabric. Otherwise, CommandCentral cannotdiscover active zoning information for the fabrics that haveswitches that do not use the supplied telnet credentials.

Switch Telnet Login

Enter the telnet password for the switch.SwitchTelnet Password

(Optional) Enter a user-friendly name to identify the switch.Configuration Name

17Overview of this releaseConfiguring out-of-band discovery of McDATA switches through SNMP and telnet

Table 1-3 Configure Device - Device Credentials panel options for McDATAswitches (continued)

DescriptionField

Check to enable zonediscovery of the switch. This field is checkedby default.

If you do not provide telnet credentials, disable this option.

Enable ZoningDiscovery

Check to enable discovery of the switch. This field is checked bydefault.

Enable Discovery


Device Manager

Check to enable retry of a failed command. This field is checkedby default.

AttemptErrorRecovery

Enter the amount of time to wait before retrying a command.The default is 1 minute.

ErrorRecoveryTimeout(minutes)

Check to verify that CommandCentral can contact the switchwith the information that you entered.

Verify DeviceConfiguration

Requirements to discover TrueCopy pairs for HitachiHiCommand arrays

CommandCentral can discover TrueCopy pairs for Hitachi HiCommand arrays.Note the following requirements:

■ For complete discovery, configure the same CommandCentral explorer todiscover the HiCommand arrays for which TrueCopy pairs are established.

■ CommandCentral can discover only the target or source VOLs if the followingoccurs:

■ You configure the HiCommand arrays for which TrueCopy pairs areestablished under separate Hitachi HiCommand Servers.

■ You configure CommandCentral to discover only one of the HitachiHiCommand Servers.

Overview of this releaseRequirements to discover TrueCopy pairs for Hitachi HiCommand arrays

18

Requirements to discover masking information forV-Max arrays

CommandCentral can discover masking information for EMC Symmetrix V-Maxarrays if you do the following:

■ Use auto-provisioning groups to perform masking operations.

■ If you enable authorization control on the array, in the Symmetrixconfiguration, assign the StorageAdmin role to the admin account on the hostthat discovers the array.

Note: CommandCentral does not discover the names of the auto-provisioninggroup elements (initiator groups,masking views, port groups, and storage groups).

Sample SQL query to view information about alldevices associated with EMC Symmetrix thin pools

You can create an ad-hoc report to view information about all EMC Symmetrixdevices associated with thin pools. Use the following sample SQL query.

SELECT a.SerialNumber as "Array", d.vendordeviceid as "Symdev",

d.vendorlayout as "Vendor Layout", e.value as "Pool Id"

FROM "HALCHM"."HAL_Disk" d

JOIN "HALCHM"."Hal_StorageArray" a ON

d.array = a.hal_storagearray_num AND a.family = 13

JOIN "HALCHM"."ExtendedAttributes" e ON

e.name = 'PoolId' AND e.objectlink_num = d._objectlink

AND e.value != ''

SampleSQLquery to view information aboutDynamicProvisioning pool IDs for HDS USP-V LDEVs

You can create an ad-hoc report to view information about the DynamicProvisioning pool IDs for HDS USP-V LDEVs that are associated with the pools.Use the following sample SQL query.

SELECT a.SerialNumber as "Array", d.vendordeviceid as "LDEV",

e.value as "Pool Id"

FROM "HALCHM"."HAL_Disk" d

JOIN "HALCHM"."Hal_StorageArray" a ON

19Overview of this releaseRequirements to discover masking information for V-Max arrays

d.array = a.hal_storagearray_num AND a.family = 4

JOIN "HALCHM"."ExtendedAttributes" e ON

e.name = 'PoolId' AND e.objectlink_num = d._objectlink

AND e.value != ''

Overview of this releaseSample SQL query to view information about Dynamic Provisioning pool IDs for HDS USP-V LDEVs

20

System requirements


■ Operating system requirements

■ CommandCentral Web browser requirements

■ Co-existence of CommandCentral components with other Symantec products

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

Operating system requirementsTable 2-1 provides operating system requirements for CommandCentral Storage.AnX indicates that you can install the component (Management Server,managedhost, or Push Install Utility) on the specified operating system.

Table 2-1 CommandCentral Storage operating system requirements

CommentsPush InstallUtility

Managedhost

ManagementServer

Operatingsystem

XAIX 5.2 (ML7or later)

For ML5, install all IY92292 filesets on the host. Toverify that the filesets are installed, type thefollowing command: "instfix -ik IY92292".

XAIX 5.3 (ML3or later)

XAIX 6.1

XHP-UX 11i v1(11.11)

2Chapter

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


Managedhost

ManagementServer

Operatingsystem

XHP-UX 11i v2(11.23 and11.23 PI)

Array management and NetApp unified storagediscovery are not supported.

XHP-UX 11i v3(11.31 and11.31 PI)

■ AS and ES (32-bit) are supported.

■ Install is not supported if SE Linux is enabled.

■ Itanium processors are not supported.

X ²Red HatEnterpriseLinux 3.0

■ AS (32-bit) and ES (32-bit and 64-bit) aresupported.



X ²Red HatEnterpriseLinux 4.0

■ 32-bit and 64-bit are supported.

■ Array management and NetApp unified storagediscovery are not supported.



XRed HatEnterpriseLinux 5.0

XXSolaris 8

XXSolaris 9

XXSolaris 10

■ 32-bit and 64-bit are supported.

■ Array management and NetApp unified storagediscovery are not supported.


XSUSE LinuxEnterpriseServer 9

XSUSE LinuxEnterpriseServer 10

Supported editions include: Server,AdvancedServer,and Datacenter Server.

XX ²X ¹WindowsServer 2000(SP3 or later)

System requirementsOperating system requirements

22

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


Managedhost

ManagementServer

Operatingsystem

Supported editions include:

■ 32-bit for the following editions: Standard, Web,Datacenter, and Enterprise.

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

XX ²X ¹WindowsServer 2003

Supported editions include (32-bit and 64-bit):Standard, Datacenter, Enterprise, and Web.

XX ²X ¹WindowsServer 2008

¹ You can install the Management Server on virtual machines that run thisoperating system. Run the virtual machine on an ESX server.

² You can install the managed host on virtual machines that run this operatingsystem. Run the virtual machine on an ESX server. If the virtualization serveruses QLogic’s HBA, install the VMware version of QLogic’s HBA API library. Theguest OS requires installation of VMware Tools.

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

23System requirementsOperating system requirements

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

■ 109147-43

■ 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


24

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 *

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

■ SUNWgss (for theManagement Server only)

■ SUNWscpux

Solaris 9

■ 117461-08

■ 119130-09

■ SUNWgss (for theManagement Server only)

■ SUNWscpu

Solaris 10

Some Solaris patches are unsupported. If these are patches installed, you need toinstall a remedy patch. The following table identifies these patches.

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

Remedy patch to install (or a higherequivalent)

Unsupported patchesOS version

109147-40■ 109147-36

■ 109147-37

■ 109147-38

■ 109147-39

Solaris 8

These patches indicate that SAN release4.4.9 is installed. Upgrade the SANrelease to a higher version.

■ 111095-26

■ 111096-14

■ 111097-22

■ 111412-19

■ 114475-06

■ 119913-08


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

Remedy patch to install (or a higherequivalent)

Unsupported patchesOS version

112963-25■ 112963-21

■ 112963-22

■ 112963-23

■ 112963-24

Solaris 9

These patches indicate that SAN release4.4.9 is installed. Upgrade the SANrelease to a higher version.

■ 113039-13

■ 113040-18

■ 113041-11

■ 113042-14

■ 114476-07

■ 119914-08

117461-08■ 117461-03

■ 117461-04

■ 117461-05

■ 117461-06

■ 117461-07

Solaris 10

119254-59■ 119254-42

■ 125978-08

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.


26

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-4 Patches required for HP-UX

Required patchesOS version

■ PHSS_24304

■ PHSS_26560

■ PHSS_26946

■ PHSS_28509*

■ PHSS_28880*

■ PHSS_30968*

■ PHSS_31326

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

HP-UX 11i v1


http://windowsupdate.microsoft.com



Table 2-4 Patches required for HP-UX (continued)

Required patchesOS version

■ PHSS_31855

■ PHSS_32228*

■ PHSS_32231*

■ PHSS_33903

■ PHSS_34444

■ PHSS_34445

■ PHSS_34853

■ PHSS_34859

■ PHSS_35055

■ PHSS_35528

■ PHSS_35978

■ PHSS_36336

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

HP-UX 11i v2

■ PHCO_38048

■ PHCO_38050

■ PHSS_38141

■ PHSS_39102

■ PHSS_38527

■ PHSS_38135

■ PHSS_38861

HP-UX 11i v3

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:

■ xlC.rte-6.0.0.0

■ xlC.aix50.rte-6.0.0.0


28

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

■ libstdc++.so.5.0.7

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)

Note the following requirements:

■ Your browsermust support either JScript 5.5 (providedwithMicrosoft InternetExplorer 6 or later) or JavaScript 1.2 . Additionally, for Internet Explorer,Secure Sockets Layer (SSL) 3.0 ActiveX scripting must be enabled.

■ If you use pop-up blockers, either disable them or configure them to acceptpop-ups from the CommandCentral Management Servers to which you willconnect.

■ To display the CommandCentral Storage Topology Map in a Web browser,install at least Java 5 (version 1.5).

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

■ For Internet Explorer 6.0 on Windows 2000 (Server, Advanced Server, orDatacenter Server) and Windows 2003 Server (Standard Edition, Datacenter

29System requirementsCommandCentral Web browser requirements

Edition, Enterprise Edition, or Web Edition), set the default Intranet zonesecurity level to MEDIUM or lower.

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.2 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-5 CommandCentral Management Server co-existence with otherSymantec products

Co-installwith theManagementServer?Symantec product component

Yes

On Windows hosts, if you install theCommandCentral 5.1.2ManagementServeron 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

System requirementsCo-existence of CommandCentral components with other Symantec products

30

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

Co-installwith theManagementServer?Symantec product component

Yes on Windows

No on Solaris

VeritasNetBackup 6.5.4OperationsManager

YesVeritas Storage Foundation Manager 2.1Management Server

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.2 managed host is installed.

Table 2-6 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

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

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

Co-install with the managed host?Symantec product component


Veritas Storage Foundation 5.0 MP1 on anHP-UX 11.23 host

YesVeritas Storage Foundation 5.0 MP2 on anHP-UX 11.23 host

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

Supported versions of CommandCentral Storage forrolling up data to Enterprise Reporter

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

Table 2-7 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

X ²5.1.1

X ²5.1.2

System requirementsSupported versions of CommandCentral Storage for rolling up data to Enterprise Reporter

32

¹ Requires Rolling Patch 1 for Enterprise Reporter 5.0 MP1 (5.0 MP1-RP1). Todownload 5.0 MP1-RP1, go to the Veritas Operations Services Web site:https://vos.symantec.com

² Requires Hotfix 1 (HF1) for Enterprise Reporter 5.1. To download the hotfix, goto the Veritas Operations Services Web site: https://vos.symantec.com

33System requirementsSupported versions of CommandCentral Storage for rolling up data to Enterprise Reporter

https://vos.symantec.com

https://vos.symantec.com

System requirementsSupported versions of CommandCentral Storage for rolling up data to Enterprise Reporter

34

Software limitations


■ Software limitations in this release

Software limitations in this releaseNo new software limitations are introduced in the 5.1.2 release.

To view the software limitations that were introduced in previous releases, viewthe following:

■ CommandCentralStorage5.1.1ReleaseNotes, which is available at the followingURL:http://seer.entsupport.symantec.com/docs/vascont/246.html

■ CommandCentral Storage Change Manager 5.1.1 Release Notes, which isavailable at the following URL:http://seer.entsupport.symantec.com/docs/vascont/245.html

3Chapter

http://seer.entsupport.symantec.com/docs/vascont/246.html


Software limitationsSoftware limitations in this release

36

Known issues


■ Known issues in this release

■ Device mapping only discovered for port 0 of directors for EMC SymmetrixV-Max arrays (1926195)

Known issues in this releaseThis chapter lists the known issues that are introduced in the 5.1.2 release.

To view the known issues that were introduced in previous releases, view thefollowing:

■ CommandCentralStorage5.1.1ReleaseNotes, which is available at the followingURL:http://seer.entsupport.symantec.com/docs/vascont/246.html

■ CommandCentral Storage Change Manager 5.1.1 Release Notes, which isavailable at the following URL:http://seer.entsupport.symantec.com/docs/vascont/245.html

Devicemappingonly discovered for port 0 of directorsfor EMC Symmetrix V-Max arrays (1926195)

For EMC Symmetrix V-Max arrays, CommandCentral only discovers devicemapping for port 0 of ESCON and FICON directors. If a device is mapped to otherports of ESCON and FICONdirectors, errors similar to the following appear in theexplorer logs:

ERROR: Port object not found for <symid:director_id:port_num> hence

deleting binding

4Chapter



Error V-31-1057-83 Property Uid not set for object of type

[emc_symmetrix_binding].

Becauseof this issue, the followingoccurs in theCommandCentral StorageConsole:

■ Port 0 is the only port that appears in the Connectivity pane for an array oradapter.

■ In the device's Overview pane, port 0 is the only port that appears in the PortMappings table.

Known issuesDevice mapping only discovered for port 0 of directors for EMC Symmetrix V-Max arrays (1926195)

38

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

5Chapter

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

40

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.

41Getting 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

42


Veritas CommandCentral™ Release Notes · CommandCentral Storage Release Notes ... Requirements to...

Documents

Transcript of Veritas CommandCentral™ Release Notes · CommandCentral Storage Release Notes ... Requirements to...