Veritas OperationsManager Release Notes · Veritas™ Operations Manager Release Notes...

Veritas™ Operations ManagerRelease Notes

3.1

Veritas™ Operations Manager Release NotesThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Product version: 3.1

Documentation version: 3.1.2

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, and Veritas Storage Foundation are trademarks orregistered trademarks of Symantec Corporation or its affiliates in the U.S. and othercountries. Other names may be trademarks of 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 theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

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

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 support 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/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may 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

www.symantec.com/business/support/www.symantec.com/business/support/

■ 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 non-technical questions, such as thefollowing 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 support 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

www.symantec.com/business/support/www.symantec.com/business/support/

Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

About Symantec ConnectSymantec Connect is the peer-to-peer technical community site for Symantec’senterprise customers. Participants can connect and share informationwith otherproduct users, including creating forum posts, articles, videos, downloads, blogsand suggesting ideas, as well as interact with Symantec product teams andTechnical Support. Content is rated by the community, and members receivereward points for their contributions.

http://www.symantec.com/connect/storage-management

mailto:[email protected]:[email protected]:[email protected]://www.symantec.com/connect/storage-management

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

Chapter 1 Overview of this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13About Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Managed host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Standalone (unmanaged) host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Veritas Operations Manager installation options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 15What’s new in Veritas Operations Manager 3.1? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Business entity enhancements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Deployment Management (Solutions) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Veritas Operations Manager Thin Provisioning Reclamation

Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Deeper insight into the storage enclosures and better

management of LUNs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16High availability and disaster recovery fire drills ... . . . . . . . . . . . . . . . . . . . . . . 17Support for Symantec ApplicationHA hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Enhanced file system monitoring and automatic growth .... . . . . . . . . . . . 17Enhanced management of the DMP paths .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18New reports in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18License and Entitlement Reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Extended attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19VCS configuration analysis policy checks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19CommandCentral™ Storage 5.2 Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19CommandCentral™ Storage 5.2 RU1 Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Upgrading to CommandCentral 5.2 RU1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Business Entity Operations Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Distribution Manager Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Third-party required libraries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

32-bit SNIA Common HBA API on Windows hosts ... . . . . . . . . . . . . . . . . . . . . . 47System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Contents

System resource requirements for the CommandCentral StorageAdd-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Supported hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Network and firewall requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51About the consumption of the managed host components ... . . . . . . . . . . . . . . . . 52

Chapter 3 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55No coexistence of managed host and CommandCentral Storage

Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Live statistics for initiators are not supported on HP-UX

(2001078) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Performance charts are not supported in certain cases for multiple

objects that belong to different hosts (2023666) ... . . . . . . . . . . . . . . . . . . . . . . . . 56Features that are not supported for Windows managed host ... . . . . . . . . . . . . . 56

Chapter 4 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installation and upgrade issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

After uninstalling Storage Foundation for Windows 5.1 (SP1,SP2), the managed host is no longer present in theManagement Server's database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Erroneous CommandCentral Storage uninstallation failurewarning (2231550) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

CommandCentral 5.2 RU1 Add-on Control Host installationissues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Management Server issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Inconsistent behavior when you configure the LDAP domain if

the LDAP server does not respond or server name is invalid(2024598) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Managed host issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Policy template fails to run on all the managed hosts that are

upgraded from 2.x to 3.x ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Cannot add a managed host with pure IPv6 address to

Management Server that supports IPv4 and IPv6(2137308) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Console display issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Updated information is not displayed immediately in the console

after resource-level operations are performed .... . . . . . . . . . . . . . . . . . . . 60Status of all SF Manager 2.x hosts is shown as healthy on an

upgraded Veritas Operations Manager 3.1 setup(2009372) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Contents8

Console does not display a service group with a name thatcontains more than 100 characters approximately(1982548) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Console does not display the second service group created withthe same name as an existing one (1934795) ... . . . . . . . . . . . . . . . . . . . . . . 61

All the associated hosts are not displayed on the service groupand resource details page and resource dependency view(1939786) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Duplicate entries displayed for a cluster after it is renamed(1929454) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Console displays the EMC PowerPath controller as disabled(1735257) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Initiator statistics are not supported on the hosts that haveStorage Foundation releases earlier than 5.0 MP3 .... . . . . . . . . . . . . . . 62

Columns may be truncated when you view emailed reports inOutlook 2003 (1937908) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Reports archived in the earlier versions are not available afteryou upgrade to Veritas Operations Manager 3.0(1997050) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Exchange service group is not listed in the Exchange Serverstable (1976615) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Certain views in Veritas Operations Manager are not displayedproperly after upgrading Management Server to the 3.1version (2133867) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Storage Foundation Administration for Windows Add-on issues ... . . . . . . . . 64Two versions of the Storage Foundation Administration for

Windows Add-on appear as enabled in the repository(2147102) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

On theVeritas OperationsManager (VOM) 3.1 console summarypage, though VSS snapshot schedules are created, correctdata is not displayed and schedule count is found to be zero(2144787) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

For SQL Application, under SQL Log and Database volumes,correct data is not displayed (2148673) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Storage Insight Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64The displayed total size of array group for HITACHI storage

arrays is not correct ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64For EMCSymmetrix arrays, inDevice details page, incorrect LUN

size is displayed under Disk tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Difference observed in NetApp enclosure’s Traditional Volume

storage size computation (2219312) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Cannot configure the enclosurewith the credentials that contain

certain special characters (2219916) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

9Contents

The tabs of an enclosure displays an error message(2209259) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Mismatchbetween the total available size of theRAIDgroupandthe total available size of the physical disk (2219669) ... . . . . . . . . . . 66

Storage Insight Add-on does not appear in the DeploymentManagement view after its successful upload to therepository (2219282) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

The informationon the storage inventories that are createdusingthe virtual filers over a NetApp enclosure is not displayedon the Storage Insight Add-on console (2113847) ... . . . . . . . . . . . . . . . . 67

The overview chart for an EMC CLARiiON enclosure capacitycontains incorrect information on the total capacity(2215684) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

The vxlist utility does not display the information on the physicaldisks for the LUNs (2219286) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

The information on the Storage distribution by RAID levelcapacitymay notmatch the capacity of the addressable sizeof the RAID groups (2219668) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Cannot configure an EMC CLARiiON enclosure on a Windowscontrol host using a security file (2221574) ... . . . . . . . . . . . . . . . . . . . . . . . . 68

Storage Provisioning Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Quick I/O cache value is not enabled after performing the storage

provisioning operation on AIX managed hosts(2131183) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Inconsistent identification of the replicated disks by the storageprovisioning template wizard (2132672) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Volume migration operation fails on unmounted volumes withThin disks (2139046) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Incorrect number of paths are displayed on the view that displaysthe status of the volume migration (2143013) ... . . . . . . . . . . . . . . . . . . . . . 69

No value is displayed in the Target array column in the view thatdisplays the status of volume migration operations(2143010) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

With the older version of DCLI on themanaged host, the storageprovisioning operation fails when using the same storageprovisioning template multiple times to create volumes(2126018) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

CommandCentral Storage Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Management Server and database issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Standard Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Unified Agent issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Console issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Discovery and data issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Contents10

Report issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Documentation issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Distribution Manager Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98The uploaded files remain in the temporary file locations after

you close the Create New Solution wizard panel(2194976) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Other issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Package check on Management Server shows errors after

installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Log on to the Veritas Operations Manager console may fail on

Firefox (1939352) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Logon to console fails on InternetExplorer ifManagementServer

host name has the underscore (_) character ... . . . . . . . . . . . . . . . . . . . . . . 100Add host operation fails after Storage Foundation is uninstalled

from Management Server or managed host (1755861) ... . . . . . . . . 100Trailing zeroes after the decimal point in product versions are

truncated when CSV data is viewed in Excel ... . . . . . . . . . . . . . . . . . . . . . 101Log on using LDAP/AD fails on Management Server that is

upgraded from 2.x to 3.1 (1993211) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Authentication broker crashes while LDAP authentication

(2017319) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Creation of a storage template is not supported for Windows

hosts (2024296) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Erroneous cluster informationdisplayed if two clusters have the

same name and ID .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102VCS configuration check reports violations only if at least one

node in the cluster is running Veritas Cluster Server(2117417) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

The Paths Re-enabled panel does not display the list of DMPpaths after you resume a DMP maintenance waiting casecreated using Veritas Operations Manager 3.0(2131163) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Alerts on file system usage and the automatic growth of filesystem are not supported on HP-UX 11.11 (2143595) ... . . . . . . . . . 103

The buttons on the bottom of the Mirror Selection panel are notdisplayed when viewed in Internet Explorer (2145006) ... . . . . . . . 103

The options in the Set Attributes Value panel are disabled forStorage Foundation versions 5.1 and later (2135540) ... . . . . . . . . . 104

The volume that has been added to an existing volume set is notadded to the file system mounted on the volume set(2141621) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

11Contents

The service groups of an unconfigured SymantecApplicationHAhost are displayed on the Veritas Operations Managerconsole (2143510) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

In a large cluster, the Veritas Operations Manager is not able tocreate cfsmounts on all the 32 nodes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

LDR discovery fails to run on few managed hosts ... . . . . . . . . . . . . . . . . . . . . 105Any array information that has changedwithin the last one hour

of running the vxlist lun command is not displayed in theoutput of the command(2129449) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Storage Foundation products discovery fails on certainmanagedhosts on AIX platform (2149227) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

The XPRTLD daemon fails at the start-up because of the corruptAT pem files in the VRTSsfmh package (2145925) ... . . . . . . . . . . . . . 106

Appendix A Documentation addenda and errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Errata for Veritas Operations Manager Storage Insight Add-on for

Deep Array Discovery and Mapping 3.1.251.0 Online Help .... . . . . . . . 109Configuring deep discovery for NetApp storage enclosures ... . . . . . . . 109Configure Device panel for deep discovery of enclosures ... . . . . . . . . . . . 111

Appendix B Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Veritas Operations Manager on the Web .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Getting help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Contents12

Overview of this release

This chapter includes the following topics:

■ About Veritas Operations Manager

■ Veritas Operations Manager installation options

■ What’s new in Veritas Operations Manager 3.1?

About Veritas Operations ManagerVeritas Operations Manager by Symantec gives you a single, centralizedmanagement console for the Veritas Storage Foundation and High Availabilityproducts. You can use it to monitor, visualize, and manage storage and clusterresources, and generate reports about them. Veritas Operations Manager letsadministrators centrally manage diverse datacenter environments.

A typical Veritas Operations Manager deployment consists of the following:

■ Management ServerSee “Management Server” on page 13.

■ Managed hostsSee “Managed host” on page 14.

Management ServerIn a centrallymanaged deployment, youmust configure one host asManagementServer. Management Server receives information about all the resources in itsdomain. When you log on to Management Server, you can gain access to theresources on different hosts within the centrally-managed deployment.

When you install Management Server, the Web Server component is installedautomatically.

1Chapter

You can use the Web Server on Management Server to access the managed hostsin the centrallymanaged deployment. You log on to theManagement Server URLandWeb Server port 14161 (for example, https://myhost.example.com:14161).

Managed hostA managed host runs at least one Storage Foundation and High Availabilityproduct, and belongs to a centralmanagement domain controlled byManagementServer.

Managed hosts include the following:

■ Hosts with Storage Foundation 4.x, or later, on all supported platforms

■ Hosts with Storage Foundation and High Availability 3.5 on HP-UX

■ Hosts with Storage Foundation and High Availability 4.x, or later, on allsupported platforms

Typically, a managed host is a production server (database File Server) on whichyou install and runStorageFoundation andHighAvailability product components.A typical site can have thousands of hosts using some or all of the StorageFoundation and High Availability products. In Veritas Operations Manager,Management Server is also configured as a managed host. You can manageManagement Server itself as part of a central management domain.

In a centrally managed deployment, managed hosts relay information aboutstorage network resources and applications toManagement Server.ManagementServer coalesces the data it receives from the managed hosts within its database.Using this coalesced data, the Veritas Operations Manager Console can presentcentralized views and reports.

Standalone (unmanaged) hostA standalone (unmanaged) host is a Storage Foundation host that has beenconfigured so it does not belong to a central management domain.

To manage individual Storage Foundation hosts, you can install and use theJava-based Veritas Enterprise Administrator. This console lets youmanage hostsusing the Storage Foundation products installed on them.

If you want a standalone host to participate in the central management domain,youmust update it by installing theVeritasOperationsManagerhostmanagementpackage.

Overview of this releaseAbout Veritas Operations Manager

14

Note: You can convert any standalone host to a managed host. However, becauseManagement Server is also a managed host, you cannot configure it to be astandalone host.

Veritas Operations Manager installation optionsYou can install Veritas Operations Manager in the following ways:

■ If you choose to implement centralized management, then a typical fullinstallation of Veritas Operations Manager consists of the following: a singleManagementServer,multiplemanagedhosts, andanynumberofWebConsoles.

■ If you prefer to implement the traditional single host management, then youhave two options: install a "thick" client, the Java-based Veritas EnterpriseAdministrator, or a light-weight Web Server that relies on a standard Webbrowser client; however, only the Java Console supports single hostmanagement of both 5.x and 4.x hosts.

With each installation option, you can establish user credentials such thatauthorized users can access the product to perform sensitive management tasksand other users can perform only a more basic set of functions.

What’s new in Veritas Operations Manager 3.1?This release of Veritas Operations Manager includes the following new featuresand enhancements.

Business entity enhancementsThe 3.1 release introduces two types of business entities: application businessentities, and organization business entities.

■ Application business entities are the same as the business entities that weresupported in version 3.0. You can use application business entities to groupdifferent objects within any application in your organization for the purposeof monitoring. Application business entities are more resource intensive, andso, they should be limited to less than 100 base objects.

■ Organization business entities are a group of logically associated hosts (forexample, by Admin, by Team, by Datacenter or Lab). Organization businessentities are less resource intensive, and can include thousands of base hosts.

You can use both the types of business entities to define security groups, and toscope reports and operations.

15Overview of this releaseVeritas Operations Manager installation options

Deployment Management (Solutions)In this release of Veritas Operations Manager, the add-ons, packages, patches,and patches are bundled as solutions. The following solutions-relatedenhancements are introduced in Veritas Operations Manager:

■ Add-onManagement and PackageManagement pages of Veritas OperationsManager user interface are merged into a single page -DeploymentManagement.

■ Categorization of solutions as add-on, package, patch, and hotfix.

■ Intelligent filtering of managed hosts based on their compatibility with thesolutions. For example, if the user deploy an add-on that can be installed onlyon Linux managed hosts, the deployment framework displays only Linuxmanaged hosts to the user. Along with platform, these checks are alsoperformed for operating system version, and Veritas Operations Managerversion.

Veritas Operations Manager Thin Provisioning Reclamation Add-onUsing the Veritas Operations Manager Thin Provisioning Reclamation Add-on(which uses the thin reclamation API of Storage Foundation), now, users canautomate the storage space reclamation for thin provisioning storage arrays (andthin LUNs) in heterogeneous environments. It enables users to minimizesunnecessary allocation of physical storage and maximize the value ofthin-provisioned storage environments. Users can schedule the thin reclamationprocess in the context of storage arrays, hosts, and business entities, and viewthe reclaimed space. The add-on takes thin provisioning (storage allocation ondemand) a step further by providing an easy to use application interface and theability to free the unutilized space (without application downtime), thus resultingin greater benefits for the organizations from cost as well environmental impactreduction perspective. Furthermore, the Thin Provisioning Reclamation Add-on,when usedwith Storage Insight Add-on, bringsmore value to the customers sincethe thin pool information (discovered by Storage Insight Add-on) can be used todrive thin reclamation.

Deeper insight into the storage enclosures and better management ofLUNs

TheVeritasOperationsManager Storage InsightAdd-on forDeepArrayDiscoveryand Mapping provides deep visibility into the storage enclosures in yourdatacenter. The add-on helps you configure and discover objects such as physicaldisks, RAID groups or storage pools, and the devices or the LDEVs in theenclosures. It also has capabilities to discover the objects that are related to various

Overview of this releaseWhat’s new in Veritas Operations Manager 3.1?

16

technologies such as mirroring (local or remote, snapshot, and replication) andthin provisioning that are implemented by various vendors of storage enclosures.

Veritas Operations Manager Storage Insight Add-on for Deep Array Discoveryand Mapping supports the EMC Symmetrix, HITACHI, and IBM XIV enclosuresfor deep discovery. On the UNIX-managed hosts that have Veritas OperationsManager 3.1 installed, the Storage Insight Add-on also offers a command lineinterface for querying deeper enclosure information.

Storage Insight Add-on also provides capabilities for defining various levels oftiers for the LUNs based on the information from the deep discovery. VeritasOperations Manager uses this information in template provisioning. Theinformation on the thin pools that Storage Insight Add-on discovers is used toperform thin reclamation.

High availability and disaster recovery fire drillsThis release of Veritas Operations Manager provides you the capabilities forperforming fire drills that, which ensures that the infrastructure is ready whena critical event occurs that requires failing over of themission-critical applications.Fire drills ensure minimal downtime of applications.

Thehigh availability (HA) fire drill checks for any discrepancies in the underlyinginfrastructure on various systems of the cluster with respect to initial VeritasCluster Server configuration settings. A successful HA fire drill indicates that theservice group has a greater chance to successfully failover to another systemwithin the cluster . The disaster recovery (DR) fire drill lets you verify that datareplicationworks in its indentedmanner and the secondary site canbe successfullybrought online in case of a site-wide disaster.

Support for Symantec ApplicationHA hostsVeritas Operations Manager 3.1 provides enhanced monitoring, administration,and reporting capabilities for the applications that run on the virtual machinesthat have Symantec ApplicationHA configured. Through a single operation, youcan enable or disable the Application Heartbeat for a service group and start orstop the applications across the virtual machines in your datacenter.

Enhanced file system monitoring and automatic growthYou can use Veritas OperationsManager to set thresholds formonitoring the filesystemusage andplanpreventivemeasures to avoid file system failures. Adequatealerts are generated if the current usage exceeds these threshold levels. Whenthe file system usage exceeds high usage risk value the rule framework

17Overview of this releaseWhat’s new in Veritas Operations Manager 3.1?

automatically increases the size of the file system by the amount that you havespecified.

This feature prevents the file system from faultingwith little or no administrativeoverhead on threshold monitoring and management.

Enhanced management of the DMP pathsThis release of Veritas Operations Manager lets you manage the DynamicMultipathing (DMP) paths in a deeper level. The enhanced capabilities let youperform the maintenance of the DMP paths from the level of the initiators andarray ports.

New reports in Veritas Operations ManagerThis release ofVeritasOperationsManager introduces the followingnew reports:

■ Failover Summary report

■ Thin Pool Usage report.

■ Patch report

The FailoverSummary report displays information on the failovers that VeritasCluster Server supports to ensure high availability.

The Failover Summary report displays information on the following types offailovers that are associated with a cluster:

■ Failovers that you have planned and executed with the Online or the Switchoperations.

■ Failovers that occurred because of faults in the datacenter, which would haveaffected the high availability adversely. Veritas Cluster Server performs thefailover operation without your interference.

■ Failovers that occurred because of faults in the datacenter. VCS requires yourinterference to clear the faults for performing the failover operation.

The ThinPoolUsage report displays the summary and the details of the thin poolusage information in the datacenter.

The Patch report displays the information on the patches for theStorageFoundation and Storage Foundation for high availability products, which areavailable to each host in the datacenter.


18

License and Entitlement ReportingIn this release ofVeritasOperationsManager, theLicensesdashboard is enhancedto provide a better understanding of the deployment summary of licenses in thedatacenter.

Also, the enhanced License and Entitlement Reporting feature in this release ofVeritas Operations Manager includes the following capabilities:

■ Scope the license views using business entities.

■ Discovery of additional licenses such asApplicationHA, DMP standalone, andCC-StoragealongwithStorageFoundationandStorageFoundationHA licenses.

■ Discovery of CPU Tier for Windows managed host along with its OS Tier.

■ Discovery of the information on the life cycle of a license such as the date andthe time at which a license is installed, detected, and removed from the hostand display these details using the License Life Cycle report.

■ Discovery of the information on a feature on a host such as its recent use, thenumber of times itwas used in a specific period, etc. using the FeatureTrackingfeature and display the information on the relevant views for the License andEntitlement Reporting feature.

Extended attributesExtended attributes are the additional attributes that you can define on a storageobject. Veritas Operations Manager displays the extended attributes along withthe existing attributes of the storage objects that it discovers. Extended attributeslet you add user-specific values and descriptions to the storage objects.

VCS configuration analysis policy checksThis release of VeritasOperationsManager contains eight newVCS configurationanalysis signatures. These new signatures represent the best practices for VCS.You can run these signatures to figure out if any of the VCS cluster configurationin your datacenter violates the best practices policies.

CommandCentral™ Storage 5.2 Add-onThe CommandCentral Storage Add-on for Veritas Operations Manager providescentralized visibility across physical and virtual heterogeneous storageenvironments. CommandCentral Storage lays the foundation for optimizing yourdatacenter by providing you a single viewof the full storage stack fromapplicationto spindle.


CommandCentral Storage includes the following capabilities:

■ Discovers detailed information about your storage infrastructure down to thedisk level. You can discover physical and virtual fabrics, physical and virtualhosts, groups, storage devices (such as arrays and NAS and unified storagedevices), and applications.

■ Offers a single console that lets you visualize your networked storageenvironment through graphical and textual displays. The console lets youvisualize physical resources—such as hosts—and logical resources—such asvirtual fabrics—and the connections and interrelationships between them.

With these capabilities, CommandCentral Storage provides the following keybenefits:

■ Visibility of the entire data path from the application to the spindle, whichhelps to ensure optimal performance and availability of business criticalapplications.

■ Identification of wasted space across enterprise storage and improvedutilization,whichallows for better capacityplanningand reduced expenditures.

If you purchased CommandCentral Storage, you can download the add-on fromthe Symantec FileConnect Web site.

The CommandCentral Storage Add-on, along with the CommandCentral StorageControl Host, are also available to try for 60 days at the following URL:

http://go.symantec.com/vom

Network sizing guideHosts can report to both Veritas Operations Manager (VOM) and theCommandCentral Storage Add-on at the same time. Calculate your network sizeby the total number of hosts that VOM and the CommandCentral Storage Add-oncollectivelymanage. For example, if yournetwork includes 2000hosts that reportto bothVOMand the CommandCentral StorageAdd-on, the total number of hoststhat the two products manage is 4000.

Table 1-1 Network sizing guide

Temporaryspace

Disk spaceSwap spacePhysicalmemory

CPUNetworksize

10 GB10 GB16 GB8 GBQuadSmall (500hosts)

15 GB20 GB24 GB12 GBQuadMedium(1000 hosts)


20

http://go.symantec.com/vom

Table 1-1 Network sizing guide (continued)

Temporaryspace

Disk spaceSwap spacePhysicalmemory

CPUNetworksize

25 GB40 GB32 GB16 GBQuadLarge (2000hosts)

CommandCentral™ Storage 5.2 RU1 Add-onCommandCentral Storage 5.2 RU1 Add-on includes the following new featuresand enhancements.


Table 1-2 New features and enhancements

DescriptionFeature

In the CommandCentral Storage 5.2 RU1Add-on, the default portthat you use to connect to the CommandCentral Storage Add-onConsole has changed.When you upgrade to 5.2 RU1, the installerscans the range of ports between 14191 and 14200 and finds thefirst available port, which then becomes the new port for theConsole.

For example, to connect to the CommandCentral Storage Add-onConsole, enter the following URL in your Web browser:https://myhost.example.com:14191/cc

To connect to CommandCentral Storage Change Manager, youneed to enter the following URL in your Web browser:https://myhost.example.com:14191/sm

If you need to, you can change the default port. For example, youcan change the default port back to 8443.

See “Changing the port for the CommandCentral Storage Add-onConsole” on page 25.

You need to connect to the Console through a new port becausetheCommandCentral StorageAdd-onnowuses an embeddedWebserver. Previous versions of the CommandCentral StorageAdd-onused a Web server that other Symantec products shared. In 5.2RU1, the CommandCentral Storage Add-on is the only Symantecproduct that uses the Web server.

Note: To start and stop the Web server in 5.2 RU1, you can usethe vxccs utility. For Solaris, the process is called esmweb. ForWindows, the process is called CCSGUI. In addition, you can usethe Windows' Services utility to start and stop the Web server. Inthe Services utility, the name of the service is VeritasCommandCentral Web Console.

New default port toconnect to the Console


22

Table 1-2 New features and enhancements (continued)

DescriptionFeature

The CommandCentral Storage Add-on can now discoverinformation about IBM logical partitions (LPARs).

For information on supported versions of IBM LPARs, see theCommandCentralHardwareandSoftwareCompatibilityList. Thisdocument is updated regularly at:

http:/www.symantec.com/docs/TECH148619

See “ IBM logical partition (LPAR) configuration requirements”on page 26.

See “Viewing information about your IBM logical partition (LPAR)environment” on page 33.

Discovery of IBMlogical partitions

The CommandCentral Storage Add-on can now discoverinformation about Solaris Volume Manager when it performsagentless discovery of hosts that runSolaris 9 or 10 (SPARConly).

The CommandCentral Storage Add-on requires root access todiscover information about Solaris Volume Manager disks anddisk slices.

See “Commands that require root access for agentless discoveryof UNIX hosts” on page 36.

Agentless discovery ofSolaris VolumeManager


http:/www.symantec.com/docs/TECH148619


DescriptionFeature

TheCommandCentral StorageAdd-on cannowperformagentlessdiscovery of remote hosts that run the HP-UX operating system.The CommandCentral Storage Add-on supports HP-UX 11.23(IA-64) and HP-UX 11.31 (IA-64 and PA-RISC).

See “What the CommandCentral Storage Add-on can discoverwith agentless discovery of hosts” on page 35.

The requirements to discover HP-UX hosts are the same as theyare for other UNIX hosts. The CommandCentral Storage Add-onrequires:

■ A user account

The CommandCentral Storage Add-on can discover mostinformationwith anon-root user account.However, privilegedaccess is required to discover some information.

See “Commands that require root access for agentlessdiscoveryof UNIX hosts” on page 36.

■ Network access between hosts

■ A shell on the remote host (sh, ksh, or bash)

■ Secure Shell (SSH) on the remote host

If SSH is not installed on the host, you can install OpenSSH.

See “Installing OpenSSH on HP-UX” on page 37.

For more information about requirements to perform agentlessdiscovery, see the CommandCentral Storage Add-onAdministrator's Guide.

Agentless discovery of HP-UX hosts works the same as it does forother UNIX hosts. You can let the CommandCentral StorageAdd-on remotely access the HP-UX host and run the script or youcan manually run the script on the host. To manually run theHP-UX script (RHHPUXScript.sh), run the following command:

/bin/sh ./RHHPUXScript.sh -d directory -ttemp_directory

Formore information about how to configure agentless discoveryof hosts, see theCommandCentral StorageAdd-onAdministrator'sGuide.

Agentless discovery ofHP-UX hosts


24


DescriptionFeature

The CommandCentral Storage Add-on can now discoverinformation aboutHitachi Virtual Storage Platform (VSP) storagearrays.

For device support information, see the CommandCentralHardware and Software Compatibility List. For example, you canidentify supported features and the supported ancillary software.This document is updated regularly at:

http://www.symantec.com/docs/TECH148619

For information about how to configure discovery ofHitachi VSP,see the CommandCentral StorageAdd-onHardware andSoftwareConfiguration Guide. You configure discovery of Hitachi VSP likeother Hitachi arrays that use the HiCommand managementframework.

Discovery of HitachiVirtual StoragePlatforms

The CommandCentral Storage 5.2 RU1 Add-on supports BrocadeData Center Fabric Manager (DCFM) 10.4.x, which includes anintegrated SMI-S agent. The CommandCentral Storage Add-oncan discover all fabrics and switches that the DCFM manages.

See “Configuring theCommandCentral StorageAdd-on todiscoverBrocade andMcDATAswitches throughDCFM10.4.x” onpage 37.

Support for BrocadeData Center FabricManager (DCFM)10.4.x

The CommandCentral Storage 5.2 RU1 Add-on includes a newview that you can use when you create ad hoc reports. The viewprovides information about the deduplication of NetApp flexvolumes with Single Instance Storage (SIS).

See “View V_NETAPP_DEDUPLICATION_BASE” on page 40.

For information about how to create ad hoc reports, see theCommandCentral Storage Add-on User's Guide.

For information about database views, see the CommandCentralStorage Add-on Administrator's Guide.

NetApp deduplicationview

Changing the port for the CommandCentral Storage Add-onConsoleYou can change the port that you use to connect to the CommandCentral StorageAdd-on Console. You can use any port that is not in use by another application.

For example, youmightwant to change the default port from14191 to 8443. 8443was the default port before the 5.2 RU1 release. You can still use port 8443 as long



as no other products use the port. For example, 8443 is the default port for theSymantec Web server (VRTSweb). Other Symantec products might use that port.

To change the port for the CommandCentral Storage Add-on Console

1 Log on to the Management Server.

2 Go to the following directory:

/opt/VRTSsfmcs/VRTSccs/VRTSccstw/esmweb/confSolaris

\Program Files\VERITAS\VRTSsfmcs\ccaddon\CommandCentralStorage\Web Engine\esmweb\conf

Windows

3 Open esmweb.cfg in a text editor.

4 Change the value of the SSLPORT parameter to the desired port number.

5 Save and close esmweb.cfg.

6 In an operating system console, change to the following directory:

/opt/VRTSsfmcs/VRTSccs/VRTS/bin/vxccsSolaris

\Program Files\VERITAS\VRTSsfmcs\ccaddon\CommandCentralStorage\Support\Tools\Vxccs

Windows

7 Type the following commands to restart the Web server:

./vxccs stop esmweb

./vxccs start esmweb

Solaris

vxccs.bat stop CCSGUI

vxccs.bat start CCSGUI

Windows

You can now connect to the Console through the new port.

IBM logical partition (LPAR) configuration requirementsFor the CommandCentral StorageAdd-on to properly discover IBMLPARs, ensurethat your storage network’s physical connections, device settings, and theCommandCentral Storage Add-on settings are properly configured.

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



26


Configuring the CommandCentral Storage Add-on to discover your IBM logicalpartition (LPAR) environment involves several steps.

Table 1-3 Configuring the CommandCentral Storage Add-on to discover yourLPAR environment

DescriptionActionStep

Identify how you need to configure discovery of yourLPAR environment.

See “How the CommandCentral Storage Add-on candiscover your IBM logical partition (LPAR)environment” on page 28.

Review how LPARdiscovery works

Step 1

Identify how you need to set up your LPARenvironment to ensure proper discovery.

See “Setup requirements for IBM logical partitions”on page 30.

Review set uprequirements

Step 2

Configure the CommandCentral Storage Add-on todiscover the HMC using the Configure a New Devicetool.

See “Configuring the CommandCentral StorageAdd-on to discover the Hardware ManagementConsole (HMC)” on page 31.

Configure discovery ofthe HardwareManagement Console(HMC)

Step 3

Configure the CommandCentral Storage Add-on todiscover each LPAR by doing one of the following:

■ Configure agentless discovery of the LPAR.

For information about how to configure agentlessdiscovery, see the CommandCentral StorageAdd-on Administrator's Guide.

■ Install the Standard Agent in the LPAR.

For informationabout installing aStandardAgent,see the CommandCentral Installation Guide.

Configure discovery ofeach LPAR

Step 4


How the CommandCentral Storage Add-on can discover your IBM logicalpartition (LPAR) environment

Note: The CommandCentral Storage Add-on does not support configuring VIOservers as agentless hosts. It also does not support installing a Standard Agenton the VIO server. If you have already installed a Standard Agent on a VIO server,disable the agent so that it does not report to the Management Server before youupgrade the Management Server to version 5.2 RU1. Installing a Standard Agenton aVIO server or configuring it for agentless discovery can lead to unpredictablebehavior.

You can configure the CommandCentral Storage Add-on to discover your LPARenvironment in one of two ways.

Table 1-4 Configuration options to discover your LPAR environment

ProvidesConfigurationOption

■ End-to-end visualization of yourLPAR environment

■ Information to perform capacitymanagement of your LPARenvironment

■ Application to spindle mapping forLPARs

■ Configure the CommandCentralStorage Add-on to discover theHardware Management Console(HMC).

■ In each LPAR, install the StandardAgent with the 5.2 Release Update(RU1)Hotfix forAIXManagedHost,whichaddsLPARdiscovery support.

1

■ End-to-end visualization of yourLPAR environment

■ Information to perform capacitymanagement of your LPARenvironment

■ File system to spindle mapping forLPARs

■ Configure the CommandCentralStorage Add-on to discover theHardware Management Console(HMC).

■ Configure agentless discovery ofeach LPAR.

2

The following table provides further information about the discovery of theHMC,LPARs, and VIO servers.


28

Table 1-5 Discovery information from the HMC, LPAR, and VIO server

Discovery informationObject

To communicate with the HMC using HMC CLIs, the CommandCentralStorage Add-on uses ssh and a user account that is assigned thehmcoperator role orhmcsuperadmin role. TheCommandCentral StorageAdd-on Management Server and Control Host can communicate withthe HMC, as they both run the LPAR explorer.

Through this communication, the CommandCentral Storage Add-oncan discover the following:

■ The managed systems that the HMC manages

■ LPARs and their associations to managed systems and VIO servers

■ VIO servers, which includes the following information:

■ Their association to LPARs

■ Their associations to managed systems

■ HBAs

■ OS handles

■ Storage that is exported from VIO servers to LPARs (noinformation about the OS handles inside the LPARs)

The CommandCentral Storage Add-on supports native devicehandles only, as backing devices for the virtual target devicesexported from the VIO server to an LPAR. The CommandCentralStorage Add-on does not support logical volumes, Veritas DMPdevices, file devices, or any device type except the native device,as the virtual target device's backing device.

The LPAR-VIOServer association is discovered onlywhenat leastone virtual target device (exported from the VIO server to theLPAR) is backed by native device handle. If there are no virtualtarget devices exported to the LPARs that are backed by nativedevice handles, the LPAR-VIO Server association is absent.

Note:TheCommandCentral StorageAdd-ondoesnot support discoveryof LPARs through the Integrated Virtualization Manager (IVM).

HardwareManagementConsole (HMC)


Table 1-5 Discovery information from the HMC, LPAR, and VIO server(continued)

Discovery informationObject

You need to either install the CommandCentral Storage 5.2 StandardAgent with the 5.2 Release Update (RU1) Hotfix for AIX Managed Host,which adds LPAR discovery support in the LPAR or configure the LPARfor agentless discovery. This step is required to discover informationabout the storage resources in the LPAR.

For discovering LPARs agentlessly, the same requirements as for anormal AIX host apply here.

Discovery provides the following:

■ Basic host information

■ HBAs (only when they are directly assigned to LPARs as slots on themanaged system)

■ OShandles, includingVSCSIOShandles (provides correlation to thestorage that is exported from VIO servers when you configurediscovery through the HMC, and if the backing device in the VIOserver is a native device handle)

■ Logical volume manager (LVM) volumes

■ File systems

■ Applications and databases (not available if you use agentlessdiscovery)

If you configured LPARhosts for agentless discovery prior to upgradingto the CommandCentral 5.2 RU1 Add-on, refresh the hosts so that youcan see the correlated data immediately.

LPAR

Setup requirements for IBM logical partitions

The CommandCentral Storage Add-on uses Secure Shell (ssh) to discover logicalpartitions (LPARs) through the Hardware Management Console (HMC).

See “How the CommandCentral Storage Add-on can discover your IBM logicalpartition (LPAR) environment” on page 28.

Make sure that theHMCallows ssh access from theManagement Server or ControlHost for an account that has the hmcoperator role or hmcsuperadmin role. Also,make sure that the account has visibility into the LPARs andVIO servers forwhichyou need discovery.

Meet the requirements for device handle discovery inside LPARs. For details, seethe CommandCentral Storage Hardware and Software Configuration Guide.


30

Configuring theCommandCentral StorageAdd-on to discover theHardwareManagement Console (HMC)

Configuring the CommandCentral Storage Add-on to discover the HardwareManagement Console (HMC) is required to discover your IBM logical partition(LPAR) environment.

See “ IBM logical partition (LPAR) configuration requirements” on page 26.

Before you configure the CommandCentral Storage Add-on to discover the HMC,review the setup requirements.

See “Setup requirements for IBM logical partitions” on page 30.

To configure the CommandCentral Storage Add-on to discover the HMC

1 Click Tools > Configure a New Device.

2 In theConfigureDevice-SelectDeviceTypepanel, select the device categoryVirtualization Server and the device type Logical partition (LPAR). Then,click Next.

3 In the Configure Device - Select Explorer panel, select the host from whichyou want to perform discovery. Then, click Next.

This panel displays only if you have more than one host that runs the LPARexplorer.

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

See “Device Credentials panel options for IBM logical partitions” on page 31.

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

Device Credentials panel options for IBM logical partitions

Use this panel to configure the CommandCentral Storage Add-on to discoverinformation about your IBM logical partition (LPAR) environment through theHardware Management Console (HMC).

Table 1-6 Configure Device - Device Credentials panel options for LPARs

DescriptionField

Enter the IP address or host name of theHardwareManagementConsole (HMC).

HMC IPAddress orHostname

Enter the logon for a user account that is assigned thehmcoperator role or hmcsuperadmin role.

Login

Enter the password for the user.Password


Table 1-6 Configure Device - Device Credentials panel options for LPARs(continued)

DescriptionField

Check this field to enable discovery of the HMC. This field ischecked by default.

Enable Discovery

Enter a user-friendly name to identify the HMC. This fielddefaults to the value that you enter in the HMC IP Address orHostname field.

Configuration Name

Enter the number of seconds in which the ssh commands thatare issued from the explorer to the HMC should timeout. Thedefault is 1200 seconds.

Click Advanced Settings to display this field.

SSH Timeout (seconds)

Check this field to verify that the CommandCentral StorageAdd-on can contact the HMC with the information that youentered in this panel. This field is checked by default.

Verify DeviceConfiguration

Tuning the LPAR explorer

You can tune the explorer that discovers logical partitions (LPARs).

To tune the LPAR explorer

1 In the CommandCentral Storage Add-on Console, click Settings > HostManagement.

2 In theHosts table, click the host onwhich youwant to configure the explorer.

3 In the Explorers table, check LPARExplorer.

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

5 In the Configure Explorers - Explorer Settings dialog box, modify theexplorer’s settings. Then, click Next.

See “Explorer Settings dialog options for the LPAR explorer” on page 32.

6 Click Finish.

The explorer updates.

Explorer Settings dialog options for the LPAR explorer

Use the Configure Explorers dialog box to tune the explorer.


32

Table 1-7 LPAR explorer options

DescriptionField

Enter the amount of time that you want the explorer to waitbefore it repeats discovery. The default is 360 minutes.

Polling Interval inMinutes

Enter the level of verbosity for which the explorer logsmessages. The verbosity range is 1-6 where 1 is the least and6 is the most verbose. Enter 0 to turn the logging off.

Click Advanced Settings to display this field.

Debug Level

Viewing information about your IBM logical partition (LPAR)environmentAfter the CommandCentral Storage Add-on discovers your LPAR environment,you can view information in theManaging andReporting sections of the Console.This information provides an end-to-end visualization of your LPARenvironmentand the ability to perform capacity management.

You can view information about the following objects:

See “Viewing managed systems” on page 33.Managed systems

See “Viewing IBM logical partitions” on page 34.LPARs

See “Viewing IBM VIO servers” on page 34.VIO servers

Viewing managed systems

When theCommandCentral StorageAdd-ondiscovers theHardwareManagementConsole (HMC), it discovers information about the managed systems (or physicalframes) that the HMC manages. The CommandCentral Storage Add-on identifiesthe managed system as a virtualization server.

You can view information about managed systems in the Managing view. Afteryou select a managed system, you can view information in the following panes:

Informationabout theVIOservers andLPARs that themanagedsystemmanages.

Overview

Links to reports that are scoped to the managed system.Reporting

The managed system’s attributes.Attributes


To view managed systems

1 Click Managing > Hosts and HBAs > Virtualization Servers.

2 In the Virtualization Servers Summary table, click the name of avirtualization server whose virtualization technology is identified as AIXLPAR.

The Overview pane for the managed system appears.

Viewing IBM logical partitions

You can view information about IBM logical partitions (LPARs) in the Managingview. You can use this information to identify how storage is used in the LPAR.After you select an LPAR, you can view information in the following panes:

Information about the LPAR, such as the associated virtualizationserver, the Virtual I/O (VIO) Servers that export storage to the LPAR,and consumed device handles.

Overview

Reports are not available for LPARs.Reporting

The LPARs attributes.Attributes

To view IBM logical partitions

1 Click Managing > Hosts and HBAs > Virtual Machines.

2 In the Virtual Machines table, click the name of a virtual machine whosevirtualization technology is identified as AIX LPAR.

The Overview pane for the LPAR appears.

If the LPAR is configured to be discovered agentlessly, or by the Standard Agent,you can view more information about the LPAR by going to the Hosts page.

To view the Hosts page for IBM Logical Partitions

1 Click Managing > Hosts and HBAs > Hosts.

2 In the Hosts table, click the name of a host whose virtualization technologyis identified as AIX LPAR.

The Overview pane for the LPAR host appears.

Viewing IBM VIO servers

When the CommandCentral Storage Add-on discovers your IBM logical partition(LPAR) environment, it can discover information about Virtual I/O Servers (VIOservers). You can view information about VIO servers in the Managing view. Anew table in the Host Virtualization Detail report, VIO Server Storage Usage,


34

shows all of the VIO servers in your environment. After you select a VIO server,you can view information in the following panes:

Information such as associated LPARs, HBA port groups, and arrayvirtual ports.

Overview

The VIO server’s HBAs, HBA ports, and host connections.Connectivity

Any active zone memberships, defined zone memberships, and zonealias memberships.

Zoning

Masked LUNs, claimed LUNs and device handles.Storage

The device handles that are exported from the VIO server to LPARs.Exported Storage

Information about physical disk groups, volumes, disks, and LUNs.Volumes

Links to reports that are scoped to the VIO server.Reporting

The VIO server’s attributes.Attributes

To view VIO servers

1 Click Managing > Hosts and HBAs > Virtualization Servers.

2 In the Virtualization Servers Summary table, click the name of avirtualization server whose virtualization technology is identified as AIXLPAR.

3 In the VIO Servers table, click the name of a VIO server.

The Overview pane for the VIO server appears.

What the CommandCentral Storage Add-on can discover withagentless discovery of hostsTable 1-8 details what the CommandCentral Storage Add-on can discover froman agentless host by operating system.

Table 1-8 Host level discovery for agentless hosts

WindowsVMwareGOS ¹

SolarisLinuxHP-UXAIXHost information

XXXXXAllocated LUNs

XXXXXClaimed LUNs

Databases (Oracle,Sybase, DB2, MS-SQL)


Table 1-8 Host level discovery for agentless hosts (continued)

WindowsVMwareGOS ¹

SolarisLinuxHP-UXAIXHost information

XXXXXXDevice handles

XXXXXDynamicMultipathing

XXXEMC PowerPath

XXXXXXFile systems

XXXXXHBAs

XXXXXHost connectivity andtopology

Microsoft Exchange

XXXXXNative volumemanagers

XXSolaris zones

XXXXXVeritas Cluster Server

XXXXXXVeritas VolumeManager

XZFS

¹ VMware guest operating systems include Linux, Solaris x86, and Windows.

Commands that require root access for agentless discovery ofUNIX hostsTheCommandCentral StorageAdd-on requires auser account toperformagentlessdiscovery of a remote UNIX host. The minimum requirement is a non-root useraccount. However, there are a few cases where the CommandCentral StorageAdd-on requires a root user account.

Table 1-9 identifies the commands that require root access.

Table 1-9 Commands that require root access for agentless discovery

¹Mandatory indicates that that part of feature discovery fails if you donot provideroot access for the command.Optional indicates thatmost of the feature discoveryworks even if you do not provide root access for the command.


36

Installing OpenSSH on HP-UXHP-UX Secure Shell version A.05.30 is based on OpenSSH 5.3 and supports:

■ HP-UX 11i v1

■ HP-UX 11i v2

■ HP-UX 11i v3

HP-UX Secure Shell version A.05.30 contains the following libraries:

■ OpenSSL

■ Zlib

■ TCP Wrappers

Open SSH 5.3 is linked with OpenSSL A.00.09.81.

To install OpenSSH on HP-UX

1 Download the SSH depot from the following location on the HP Web site:

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA

2 Install the OpenSSH depot using the swinstall command.

Configuring the CommandCentral Storage Add-on to discoverBrocade and McDATA switches through DCFM 10.4.xYou can configure the CommandCentral Storage Add-on to discover the BrocadeandMcDATAswitches that theBrocadeDataCenter FabricManager (DCFM)10.4.xmanages. You configure discovery of the DCFM through theBrocadeSwitchExplorer.

If the CommandCentral Storage Add-on currently discovers your Brocade andMcDATA switches through another method, you can unconfigure thoseconfigurations and configure discovery through DCFM.

To configure theCommandCentral StorageAdd-on to discover Brocade andMcDATAswitches through DCFM 10.4.x

1 Click Tools > Configure a New Device.

2 In theConfigureDevice-SelectDeviceTypepanel, select the device categorySwitch and the device type Brocade Switch. Then, click Next.


https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AAhttps://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA

3 In the Configure Device - Select Explorer panel, select the host from whichyou want to perform discovery. The selected host must have a physicalconnection to the host where DCFM runs. Then, click Next.

This panel displays only if youhavemore than onehost that runs the Brocadeswitch explorer.

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

See “Device Credentials panel options for Brocade and McDATA switchesdiscovered through DCFM 10.4.x” on page 38.

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

Device Credentials panel options for Brocade and McDATA switchesdiscovered through DCFM 10.4.x

Enter information in this panel to discover the Brocade and McDATA switchesthat a Brocade Data Center Fabric Manager (DCFM) 10.4.x manages.

Table 1-10 Configure Device - Device Credentials panel options for Brocadeand McDATA switches discovered through DCFM 10.4.x

DescriptionField

Enter the IP address or nameof thehostwhereDCFM10.4.x runs.SMI-S CIMOM IPAddress or Name

Enter a user name for the DCFM's integrated SMI-S Agent. Theuser name that you enter depends on the authenticationmethodfor the SMI-S Agent.

In the SMIA Configuration Tool, you can set the CIMOM ServerAuthentication to one of the following:

■ No Authentication

■ DCFM Authentication

If you use No Authentication, you still need to enter a user nameand password in the Configure a NewDevice Tool. You can enterany user name and password.

If you use DCFM Authentication, the SMI-S Agent credentialsare equal to the DCFM Administrator credentials. Enter thosecredentials in the Configure a New Device Tool.

Login

Enter the password for the specified user name.Password

This read-only field enables discovery andmanagement throughSMI-S.

Use SMI-S


38

Table 1-10 Configure Device - Device Credentials panel options for Brocadeand McDATA switches discovered through DCFM 10.4.x (continued)

DescriptionField

Enter the interop namespace that the DCFM SMI-S Agent uses.The default isinterop. See vendor documentation to determinewhether this value should be changed.

Interop Namespace

Enter the HTTP port to use for clear text HTTP SMI-S messages.The default is 5988. See vendor documentation to determinewhether this value should be changed. If you configured theDCFMSMIAgent to use a non-default port, enter that value here.

HTTP Port

Enter the HTTPS port to use for SSL HTTP SMI-Smessages. Thedefault is 5989. See vendor documentation to determinewhetherthis value should be changed. If you configured the DCFM SMIAgent to use a non-default port, enter that value here.

HTTPS Port

Check to use SSL encryption instead of clear textHTTP for SMI-Smessages. Ensure that the SMI Agent is configured for SSL.

Use SSL encryption

Check if you want to configure the explorer to attempt mutualauthentication.

Both the explorer and the SMI-S CIMOM send their respectiveSSL certificates during the SSL handshake.

If you select this option, you must manually install theCommandCentral Storage Add-on SMI-S certificate to the SMI-SCIMOM Truststore. Consult your vendor documentation.

If you do not select this option, the SSL authentication mode isset to Client Authentication Only. In this case, only theSMI-S CIMOM is expected to send its SSL certificate forvalidation.

The option is deselected by default. The default setting isClientAuthentication Only.

Use SSL MutualAuthentication


Table 1-10 Configure Device - Device Credentials panel options for Brocadeand McDATA switches discovered through DCFM 10.4.x (continued)

DescriptionField

Check if you want the explorer to trust all SSL certificates.

If you enable this option, the explorer accepts any certificate thatthe CIMOM passes during the SSL handshake.

If not selected, the explorer checks the certificate that theCIMOMpasses against the installedCIMOM’spublic certificate. Thepubliccertificate is in the CommandCentral Storage Add-on SMI-SCIMOM SSL Truststore.

If you deselect this option, you must manually install the SMI-SCIMOMcertificate to theCommandCentral StorageAdd-onSMI-SCIMOM SSL Truststore.

SSL Trust AllCertificates

Check to enable discovery and management of the fabric.Enable Discovery

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

Check to verify that the DCFM can be contacted using theinformation that you have entered.

Verify DeviceConfiguration

View V_NETAPP_DEDUPLICATION_BASEThe database view, V_NETAPP_DEDUPLICATION_BASE, provides informationabout the deduplication of NetApp flex volumes with Single Instance Storage(SIS). You can use this information when you create ad hoc reports (SQL queries).

Table 1-11 Columns included in the view

DescriptionColumn

Unique database number of theNetAppunified storage system.ArrayLink

Name of the NetApp unified storage system.ArrayName

Unique ID of the volume.DBObjectKey

Whether deduplication is enabled or disabled on the volume.DedupState

Used capacity of the volume, if no space was shared. Thiscapacity is calculated as follows: space saved + space used.

EffectiveUsed

Start timestamp of the last SIS operation.Lastsisoperationbegin

End timestamp of the last SIS operation.Lastsisoperationend


40

Table 1-11 Columns included in the view (continued)

DescriptionColumn

Used capacity of the volume.LogicalUsed

Serial number of the volume.SerialNumber

The disk space savings from the shared space.SpaceSaved

Percentage of space savings from the shared space. Thispercentage is calculated as follows: SpaceSaved / EffectiveUsed.This information is available if the SIS volume is online.

SpaceSavedPercent

Used space of the volume that is shared. This information isavailable if the SIS volume is online.

SpaceShared

Percentage of the space that the volume uses with regards tothe logical capacity. The percentage helps to determinewhetherused storagewould outgrow logical storage (over subscription),if no spacewas shared. This percentage is calculated as follows:(EffectiveUsed / TotalLogicalCapacity) * 100.

SubscribedPercent

Total logical capacity of the volume.TotalLogicalCapacity

RAID level of the volume.RAIDLevel

Name of the volume.Volume

Unique database number of the volume.VolumeLink

Upgrading to CommandCentral 5.2 RU1The CommandCentral 5.2 RU1 Add-on is an update to the CommandCentral 5.2Add-on release. You can upgrade the following CommandCentral components to5.2 RU1:

See “Upgrading the Management Server” on page 41.Management Server

See “Upgrading the Control Host” on page 43.Control Host

You can upgrade to CommandCentral 5.2 RU1 from version 5.2 only.

Upgrade your Management Server before you upgrade any Control Hosts.

Upgrading the Management ServerYou can upgrade a CommandCentral 5.2 Management Server to 5.2 RU1.


To upgrade the Management Server (Solaris)

1 Log on to theManagement Server as root or as a userwith an ID equal to zero(UID=0).

2 If you have not already done so, download the installation file from theSymantec FileConnect Web site:

https://fileconnect.symantec.com

The file is named VRTS_CommandCentral_5.2RU1_Solaris_MS.tar.gz.

3 Type the following commands to uncompress the tar file:

gunzip VRTS_CommandCentral_5.2RU1_Solaris_MS.tar.gz

tar -xf VRTS_CommandCentral_5.2RU1_Solaris_MS.tar


installer_location/MS/sol_sparc

Where installer_location is the directory in which you uncompressed the tarfile.

5 Type the following command to start the upgrade:

./installrp host_name

Where host_name is the fully qualified name of the host.

6 Follow the prompts to upgrade the Management Server.

To upgrade the Management Server (Windows)

1 Logon to theManagementServer as auserwith administrator-level privileges.



The file is named VRTS_CommandCentral_5.2RU1_Windows_MS.zip.

3 Extract VRTS_CommandCentral_5.2RU1_Windows_MS.zip.


installer_location\MS\win\patches

Where installer_location is the directory in which you extracted the zip file.

5 Run MSSetup.exe.

6 Follow the instructions in the wizard to upgrade the Management Server.


42

https://fileconnect.symantec.comhttps://fileconnect.symantec.com

Upgrading the Control HostYou can upgrade a CommandCentral 5.2 Control Host to 5.2 RU1.

To upgrade the Control Host (Solaris)

1 Log on to theControlHost as root or as a userwith an ID equal to zero (UID=0).



The file is named VRTS_CommandCentral_5.2RU1_Solaris_CH.tar.gz.

3 Type the following commands to uncompress the tar file:

gunzip VRTS_CommandCentral_5.2RU1_Solaris_CH.tar.gz

tar -xf VRTS_CommandCentral_5.2RU1_Solaris_CH.tar


installer_location/CH/sol_sparc

Where installer_location is the directory in which you uncompressed the tarfile.

5 Type the following command to start the upgrade:

./installrp host_name

Where host_name is the fully qualified name of the host.

6 Follow the prompts to upgrade the Control Host.

To upgrade the Control Host (Windows)

1 Log on to the Control Host as a user with administrator-level privileges.



The file is named VRTS_CommandCentral_5.2RU1_Windows_CH.zip.

3 Extract VRTS_CommandCentral_5.2RU1_Windows_CH.zip.


installer_location\CH\win\patches

Where installer_location is the directory in which you extracted the zip file.

5 Run CHSetup.exe.

6 Follow the instructions in the wizard to upgrade the Control Host.


https://fileconnect.symantec.comhttps://fileconnect.symantec.com

Business Entity Operations Add-onThe Business Entity Operations Add-on enables users to start and stop businessentities using Veritas Operations Manager console; effectively, it is a provisionto online and offline business entity’s constituents service groups in the definedorder without interfering with Veritas Cluster Server-level service groupdependencies.

Furthermore, if a service group is configured onavirtualmachine (VM), the add-onallows its users to configure the virtual machine to automatically start or shutdown, thereby eliminating the need of manual intervention to manage virtualmachines. With VMware® virtualization support, now the users can also managethe service groups that are configured on the node (a virtual machine) of a singlenode cluster (for example, Symantec ApplicationHA). The Business EntityOperationsAdd-on supports industry leadingVirtualization infrastructure vendorVMware®.

Distribution Manager Add-onThe Veritas Operations Manager Distribution Manager Add-on is a centralizedsolution that lets you create customized solutions and prepare them for deployingon the managed hosts that Veritas Operations Manager manages.

A customized solution is different from the conventional Veritas OperationsManager solutions that include Add-ons, patches, packages, and hotfixes. Aconventional Veritas Operations Manager solution, which is available with aVeritas Operations Manager release, can be downloaded from the VeritasOperationsManagerWeb site. Then, you can upload the conventional solution tothe Deployment Management repository and deploy it on the managed hosts.For a customized solution, you must create the script files for installing anduninstalling the solutions on the hosts. You can deploy a customized solution onthe hosts that run on a specific platform or across the supported platforms.


44

System requirements

This chapter includes the following topics:

■ Operating system requirements

■ Third-party required libraries

■ System resource requirements

■ Supported hardware

■ Web browser requirements

■ Network and firewall requirements

■ About the consumption of the managed host components

Operating system requirementsTable 2-1 provides an overview of Veritas Operations Manager operating systemrequirements for Management Server:

2Chapter

Table 2-1 Veritas Operations Manager operating system requirements forManagement Server

NotesOperating system supported

x86 64-bit is the supported architecture.Red Hat Enterprise Linux 4.0 Update 3

Red Hat Enterprise Linux 5.0

Red Hat Enterprise Linux 5.1 Update 1

Red Hat Enterprise Linux 5.2

Date post:	06-Jun-2020
Category:	Documents
Upload:	others
View:	26 times
Download:	0 times

Veritas OperationsManager Release Notes · Veritas™ Operations Manager Release Notes...

Documents