Veritas™ Operations Manager Management Server 5.0 ... · Connecting to Veritas Operations Manager Management Server ..... 27 Verifying the version of a managed host in the console

Veritas™ Operations ManagerManagement Server 5.0Administrator's Guide

December 2012

Veritas™ Operations Manager Management ServerAdministrator's Guide

The software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Product version: 5.0

Documentation version: 5.0 Rev 3

Legal NoticeCopyright © 2012 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 License Agreementaccompanying 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 Notice Appendixto 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.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,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 TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR 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 and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 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 and Documentation by the U.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. The Technical 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, the Technical Support group works with Product Engineeringand 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 on which the problem occurred, 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 your Symantec product requires registration or a license key, 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, DVDs, or manuals



Support agreement resourcesIf you want 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 information with 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

DocumentationYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:

[email protected]

For information regarding the latest HOWTO articles, documentation updates,or to ask a question regarding product documentation, visit the Storage andClustering Documentation forum on Symantec Connect.

https://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentation

mailto:[email protected]



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




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

Chapter 1 Basic Veritas Operations Manager tasks . . . . . . . . . . . . . . . . . . . . . . . 23

About the communication between the managed hosts andManagement Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23About the frequency of managed host information

discovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Setting up the Web browser for Veritas Operations Manager ... . . . . . . . . . . . . . 26Connecting to Veritas Operations Manager Management Server ... . . . . . . . . 27Verifying the version of a managed host in the console ... . . . . . . . . . . . . . . . . . . . . 28Administering a UNIX or a Windows managed host ... . . . . . . . . . . . . . . . . . . . . . . . . . 28Stopping and starting the Web application .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 2 Configuring Management Server settings . . . . . . . . . . . . . . . . . . . . . 31

About the methods to enhance the availability of ManagementServer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Viewing the Management Server settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Configuring SMTP settings for email notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . 33Enabling the analytics gathering on Management Server ... . . . . . . . . . . . . . . . . . 34About enabling Veritas Operations Manager Advanced features on

Management Server in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . 35Enabling Veritas Operations Manager Advanced features on

Management Server in Veritas Operations Manager ... . . . . . . . . . . . . 35Setting the period for retaining the alert and the task logs in the

database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36About configuring Web server settings in Veritas Operations

Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring the Web server settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Viewing the details of active users logged in to Management

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 3 Managing alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About faults and risks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Viewing faults and risks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Contents

About analyzing faults ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Analyzing faults ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Suppressing faults ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Suppress Faults options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Viewing the faults definitions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Suppressing the fault definitions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Suppress the fault definition panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Activating suppressed fault definitions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Activate the suppressed fault definition panel options .... . . . . . . . . . . . . . . 48Activating suppressed faults ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48About alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48About alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Creating alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Create Rule - Alert Conditions options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Create Rule - Select Alerts options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Create Rule - Trigger Alert Source options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Create Rule - Setup notifications options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Create Rule - Description .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Viewing the overview of a rule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Modifying alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Edit Rule - Alert Conditions options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Edit Rule - Select Alerts options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Edit Rule - Trigger Alert Source options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Edit Rule - Setup notifications options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Edit Rule - Name options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Copying alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Copy Rule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Enabling alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Disabling alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Deleting alert rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Delete an Existing Rule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Viewing alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68About tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Viewing tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71About messages posted on Activity Board .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Viewing the messages posted on the Activity Board .... . . . . . . . . . . . . . . . . . . . . . . . . 72Deleting a message that is posted on Activity Board .... . . . . . . . . . . . . . . . . . . . . . . . . 72About setting alerts for replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Setting the alerts for replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Monitor RVG(s) panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents8

Chapter 4 Deploying Veritas Operations Managersolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

About Veritas Operations Manager solutions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76About deploying Veritas Operations Manager solutions .... . . . . . . . . . . . . . . . . . . 76

About deploying add-ons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77About deploying packages or patches ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78About deploying hotfixes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Viewing solutions in the repository .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Uploading a solution to repository .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Uploading packages or add-ons to repository as a zip file ... . . . . . . . . . . . . . . . . . 81Installing a Veritas Operations Manager 5.0 solution .... . . . . . . . . . . . . . . . . . . . . . . 81

Install solution options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Upgrading add-ons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Uninstalling a Veritas Operations Manager solution .... . . . . . . . . . . . . . . . . . . . . . . . 84Removing a Veritas Operations Manager solution from

repository .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Viewing the solution deployment summary and the hosts to install

solution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Installing solutions on specific managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Uninstalling solutions from specific managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . 87Enabling the add-ons on specific managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Disabling the add-ons on specific managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Viewing the deployment requests for a solution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Viewing deployment request details for a solution .... . . . . . . . . . . . . . . . . . . . 89Canceling deployment request for a solution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Downloading the deployment log for a solution's deployment

request ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 5 Managing databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Performing the database discovery for secure databases ... . . . . . . . . . . . . . . . . . . 93Select database instances options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Provide credentials options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Database Instance Credentials Summary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 6 Managing clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Viewing the fire drill schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Modifying a fire drill schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Select Service Group(s) panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Schedule panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Summary panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

9Contents

Chapter 7 Managing hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Overview of host discovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104How Veritas Operations Manager discovers hosts ... . . . . . . . . . . . . . . . . . . . . 104Supported features for host discovery options .... . . . . . . . . . . . . . . . . . . . . . . . 106

Overview of agentless discovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108About agentless discovery using the Control Host ... . . . . . . . . . . . . . . . . . . . 109About agentless discovery of remote hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Prerequisites for agentless configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110How agentless discovery of a UNIX host works ... . . . . . . . . . . . . . . . . . . . . . . . 110How agentless discovery of a Windows host works ... . . . . . . . . . . . . . . . . . . 111Requirements for agentless discovery of UNIX hosts ... . . . . . . . . . . . . . . . . 112Requirements for agentless discovery of Windows hosts ... . . . . . . . . . . . 114Requirements for deep array discovery for agentless hosts ... . . . . . . . 115Commands that require root access for agentless discovery of

UNIX hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Using the privilege control software with agentless discovery of

UNIX hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118SSH configuration requirements for agentless discovery .... . . . . . . . . . 119About installing OpenSSH on a UNIX host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About managing the hosts from Management Server ... . . . . . . . . . . . . . . . . . . . . . 124Viewing the details of the managed hosts associated with Management

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Adding the managed hosts to Management Server using the Web

console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Add host options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Adding managed hosts to Management Server using the AutoConfigure (gendeploy.pl) script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Refreshing the details of the managed host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Editing the details of an agentless host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Edit agentless host options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Removing the managed hosts from the Management Server

domain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135About monitoring usage and configuring the automatic growth for

file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Setting the threshold for monitoring file system usage .... . . . . . . . . . . . . . . . . . . 137

Monitor Capacity panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Monitor Capacity Summary panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Configuring the automatic growth of the file systems .... . . . . . . . . . . . . . . . . . . . . 140Reclaiming thin storage for file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Reclaiming thin storage for disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Compressing files in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . 142

About file compression in Veritas Operations Manager ... . . . . . . . . . . . . 143

Contents10

Setting up compression schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Compression Schedule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Adding compression directories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Select directory to add for compression options .... . . . . . . . . . . . . . . . . . . . . . 146Removing compression directories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Starting or stopping compression on demand .... . . . . . . . . . . . . . . . . . . . . . . . . 148Compress Now options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Uncompressing directories on demand .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

About using Veritas Operations Manager to manage the hosts withSymantec ApplicationHA .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Enabling application heartbeat for a service group .... . . . . . . . . . . . . . . . . . . . . . . . 151Disabling application heartbeat for a service group .... . . . . . . . . . . . . . . . . . . . . . . . 152

Chapter 8 Discovering the server and storage virtualizationenvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

About the virtualization technologies supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . 156About Control Hosts in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . 157About discovering the VMware Infrastructure using Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Requirements for discovering VirtualCenter and ESX servers

using Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161How Veritas Operations Manager discovers VirtualCenter and

ESX servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Information that Veritas Operations Manager discovers on the

VMware Infrastructure components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162About the datastores in Veritas Operations Manager ... . . . . . . . . . . . . . . . . 163About the multi-pathing discovery in the VMware

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Viewing the Virtualization Management view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Configuring the virtualization discovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Virtualization Configuration panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Select option panel ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Virtualization Configuration progress details panel ... . . . . . . . . . . . . . . . . . 169

Editing a virtualization discovery configuration in Veritas OperationsManager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Virtualization Configuration panel options (Edit) .. . . . . . . . . . . . . . . . . . . . . . 170Select option panel (Edit) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Virtualization Configuration progress details panel (Edit) .. . . . . . . . . . . 172

Refreshing a virtualization discovery configuration .... . . . . . . . . . . . . . . . . . . . . . . 172Removing a virtualization discovery configuration .... . . . . . . . . . . . . . . . . . . . . . . . 173About discovering Solaris zones ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Requirements for discovering Solaris zones ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11Contents

How Veritas Operations Manager discovers Solaris zones ... . . . . . . . . . 176Information that Veritas Operations Manager discovers on

Solaris zones ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Limitations of the discovery of Solaris zones in Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178About discovering Logical domains in Veritas Operations

Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Requirements for discovering Solaris Logical domains using

Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180How Veritas Operations Manager discovers Solaris Logical

domains .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Information on Logical domains that Veritas Operations Manager

discovers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Limitations of the discovery of Logical domains in Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182About discovering LPAR and VIO in Veritas Operations

Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182About LPAR storage correlation supported in Veritas Operations

Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Prerequisites for LPAR storage correlation support in Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185About Microsoft Hyper-V virtualization discovery .... . . . . . . . . . . . . . . . . . . . . . . . . 185

Virtual machine discovery in Microsoft Hyper-V .... . . . . . . . . . . . . . . . . . . . 185Storage mapping discovery in Microsoft Hyper-V .... . . . . . . . . . . . . . . . . . . . 186

About Kernel-based Virtual Machine (KVM) virtualization discoveryin Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

About the reports related to virtualization in Veritas OperationsManager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Viewing the virtual environment summary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Viewing virtualization servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Viewing the virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Chapter 9 Downloading Storage Foundation and StorageFoundation and High Availability patches usingSymantec Operations Readiness Tools . . . . . . . . . . . . . . . . . . . 193

About updating the patch information on Management Server ... . . . . . . . . 194Viewing the patches that are available on SORT for a host ... . . . . . . . . . . . . . . 194Viewing the details of a patch on the SORT Web site ... . . . . . . . . . . . . . . . . . . . . . . 196Updating the patch information automatically using Management

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Updating the patch information automatically using a proxy

server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Contents12

Updating the patch information manually on ManagementServer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 10 Monitoring performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

About performance metering statistics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200About metered resources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200About space estimation for data logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Enable performance metering for a VMware vCenter server ... . . . . . . . . . . . . 205

Configure performance metering panel options .... . . . . . . . . . . . . . . . . . . . . . 206Disable performance metering for a VMware vCenter server ... . . . . . . . . . . . 207Enable performance metering for a VMware ESX server ... . . . . . . . . . . . . . . . . . 207Disable performance metering for a VMware ESX server ... . . . . . . . . . . . . . . . . 208Enable performance metering for a host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Disable performance metering for a host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209About Veritas Operations Manager performance graphs .... . . . . . . . . . . . . . . . . 209

Pre-requisite commands to view performance graphs for aresource ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Viewing the performance graphs for a volume .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Viewing the performance graphs for a host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Viewing the performance graphs for a disk .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Viewing the performance graphs for an initiator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Viewing the performance graph for a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . 216Viewing the performance graphs for a multipathing path .... . . . . . . . . . . . . . . 217Viewing the performance graphs for an enclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 11 Managing security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

About the security model for Veritas Operations Manager ... . . . . . . . . . . . . . . 221About predefined roles in Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . 222Viewing security group details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Adding security groups to the Veritas Operations Manager

domain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230New Security Group options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Modifying security groups in the Veritas Operations Managerdomain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Edit Access Control options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Removing security groups from Veritas Operations Manager ... . . . . . . . . . . 236

Chapter 12 Managing business entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

About managing business entities in Veritas OperationsManager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

About composite business entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

13Contents

About security privileges required to manage business entities ... . . . . . . . . 239About Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Creating Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Virtual Business Service Attributes options for creating a VirtualBusiness Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Select Base Object Types options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Select Base Databases options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Select Base Hosts options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Select Base File Systems options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Select Base Service Groups options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Select Base Enclosures options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Select Base Exchange Servers options for creating a VirtualBusiness Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Select Base Clusters options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Select Base Disk Groups options for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Virtual Business Service summary for creating a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Business Entity Attributes options for creating a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Select Base Object Types options for creating a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Select Base Databases options for creating a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Select Base Hosts options for creating a business entity ... . . . . . . . . . . . . 250Select Base Clusters options for creating a business entity ... . . . . . . . . 250Select Base Disk Groups options for creating a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Select Base File Systems options for creating a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Select Base Service Groups options for creating a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Select Base Enclosures options for creating a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Select Base Exchange Servers options for creating a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Contents14

Business Entity Summary options for creating a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Creating Organization Entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Organization Entity Attributes options for creating an

Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Organization Entity Summary options for creating an

Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Select Base Hosts options for creating an Organization

Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Editing Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Virtual Business Service Attributes options for editing a VirtualBusiness Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Select Base Object Types options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Select Base Databases options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Select Base Hosts options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Select Base Service Groups options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Select Base File Systems options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Select Base Disk Groups options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Select Base Enclosures options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Select Base Clusters options for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Select Base Exchange Servers options for editing a VirtualBusiness Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Virtual Business Service Summary for editing a Virtual BusinessService ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Business entity Attributes options for editing a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Select Base Object Types options for editing a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Select Base Databases options for editing a business entity ... . . . . . . . 264Select Base Hosts options for editing a business entity ... . . . . . . . . . . . . . 264Select Base Service Groups options for editing a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Select Base File Systems options for editing a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

15Contents

Select Base Disk Groups options for editing a businessentity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Select Base Enclosures options for editing a business entity ... . . . . . . 266Select Base Clusters options for editing a business entity ... . . . . . . . . . . 266Select Base Exchange Servers options for editing a business

entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Business Entity Summary for editing a business entity ... . . . . . . . . . . . . . 267

Editing Organization Entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Organization Entity Summary for editing an Organization

Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Select Base Hosts options for editing an Organization

Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Organization Entity Attributes options for editing an

Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Deleting Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Delete Virtual Business Service options for deleting a VirtualBusiness Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Deleting Organization Entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Delete Organization Entity options to delete an Organization

Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Creating composite Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Composite Virtual Business Service Attributes options forcreating a composite Virtual Business Service ... . . . . . . . . . . . . . . . . . . . 273

Select Virtual Business Service panel options for creating acomposite Virtual Business Service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Composite Virtual Business Service Summary panel options forcreating a composite Virtual Business Service ... . . . . . . . . . . . . . . . . . . . 274

Business Entity Attributes options for creating a compositebusiness entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Select Business Entity panel options for creating a compositebusiness entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Composite Business Entity Summary panel options for creatinga composite business entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Creating composite Organization Entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Composite Organization Entity Attributes options for creating

a composite Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Select Organization Entity panel options for creating a composite

Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Composite Organization Entity Summary panel options for

creating a composite Organization Entity ... . . . . . . . . . . . . . . . . . . . . . . . . 278Adding storage or high availability objects to existing business

entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Add to Business Entity options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Contents16

Making business entities available to security groups in VeritasOperations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Change Permissions options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Setting extended attributes for business entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Select base object type options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Select related object types options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Viewing Virtual Business Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Viewing Organization Entities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284About the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Objects used in the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286makeBE script CSV file details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287makeBE script parameters details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Limitations of makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290makeBE script log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Creating business entities using the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . . 290Importing business entities using the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . 291Exporting business entities using the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . 292Updating business entities using the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . 293Deleting business entities using the makeBE script ... . . . . . . . . . . . . . . . . . . . . . . . . 294

Chapter 13 Managing Authentication Brokers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

About managing Authentication Brokers in the Veritas OperationsManager domain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

About managing domains associated with an Authentication Brokerin Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Viewing the details of the Authentication Brokers and the domainsassociated with them .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Adding secondary Authentication Brokers to the Management Serverdomain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Add New Broker options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Refreshing the information associated with the AuthenticationBrokers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Removing the Authentication Brokers from the Veritas OperationsManager domain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Configuring Lightweight Directory Access Protocol-basedauthentication on Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306LDAP/AD Settings - discover attributes and configuration

information panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307LDAP/AD Settings - configure LDAP based authentication

options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Removing Lightweight Directory Access Protocol or Active Directory

configuration from the primary Authentication Broker ... . . . . . . . . . . . . 311

17Contents

Enabling the authentication domains associated with anAuthentication Broker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Enable Domains options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Disabling the authentication domains associated with anAuthentication Broker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Disable Domains options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Chapter 14 Managing licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

About licenses ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316About Symantec licensing and pricing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

About the Symantec Performance Value Unit ... . . . . . . . . . . . . . . . . . . . . . . . . . 319About the Symantec Performance Value Unit for VMware virtual

machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320About the Symantec Performance Value Unit for Solaris LDOM

virtualization server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321About the Symantec Performance Value Unit for kernel-based

virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322About the Symantec Performance Value Unit for IBM LPAR .... . . . . . 323

About assigning price tiers to hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324About updating the price tier information on Management

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Assigning a price tier to a host manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Select Price Tier options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Select hosts to set chosen tier options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Assign price tier summary manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Assigning a price tier to a host automatically ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Assign the price tier summary automatically ... . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Updating the price tier information automatically using ManagementServer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Updating the price tier information automatically using a proxyserver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Updating the price tier information manually on ManagementServer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

About license deployment policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Viewing platform specific licensing and pricing information .... . . . . . . . . . . 332Viewing the details of license deployment policies ... . . . . . . . . . . . . . . . . . . . . . . . . . 333Creating a license deployment policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Create license deployment policy options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Deployment Policy Summary panel ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Modifying a license deployment policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Change thresholds of license deployment policy options .... . . . . . . . . . . 339Deployment Policy Summary (modify) options .... . . . . . . . . . . . . . . . . . . . . . . . 341

Contents18

Updating the default virtual machine count factor ... . . . . . . . . . . . . . . . . . . . . . . . . 341Update counting factor for virtual environment options .... . . . . . . . . . . 341

Removing a license deployment policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Chapter 15 Viewing deployment information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

About License Deployment detailed view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344Viewing the License Deployment Summary view .... . . . . . . . . . . . . . . . . . . . . . . . . . . 345

About accountable deployed licenses ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Viewing the summary of product inventory .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Viewing the Product-Tier Mapping summary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Viewing a product overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Viewing hosts with product license deployed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Viewing the evidence details of a feature ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Viewing the overview of a host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Viewing the overview of the licenses information for a host ... . . . . . . . . . . . . 360Viewing product details by license key .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Viewing license key details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Viewing the details of the mapping between the licenses and

hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Viewing License-Host Mapping details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Viewing the summary of host-level license deployment

exceptions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368Viewing the VOM Entitlement Report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368Scoping a license deployment view using business entities ... . . . . . . . . . . . . . . 370

Scoping License Views options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Chapter 16 Using policy checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

About policy checks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374About policy templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374About creating policy templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Creating policy templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Policy Template Details options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377Select Signatures options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377Select Scope options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Specify Schedule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Policy Template Summary options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Modifying policy templates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380Running a manual policy template scan .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Deleting a policy template ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381About policy violations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Marking policy violations to exclude from the subsequent scans .... . . . . . 382About Installed Signatures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

19Contents

About the customized signature in Veritas Operations Manager foridentifying risks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384About creating a customized signature script ... . . . . . . . . . . . . . . . . . . . . . . . . . 385Sample customized signature script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386About registering the customized signature ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 388About copying the customized signature script ... . . . . . . . . . . . . . . . . . . . . . . . 388About using the Distribution Manager Add-on to bundle a

customized signature in Veritas Operations Manager ... . . . . . . . . . 389About removing a customized signature from Veritas Operations

Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Adding signatures to a policy template ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Setting signature tunables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Set Signature Tunables options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Removing a signature from a policy template ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Deleting a policy template scan .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Viewing scan tunables associated with a policy scan .... . . . . . . . . . . . . . . . . . . . . . 394Removing ignored violations from the ignore list ... . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Chapter 17 Managing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

About reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397About managing reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398Running a report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Select Scope options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400Creating a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Schedule options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Specify Schedule Details options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Editing a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404Enabling a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Disabling a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Removing a report schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406Archiving reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Archive options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407Sending a report through email ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

Email Archived Report options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409Email options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Deleting an archived report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410Exporting report data to a file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Chapter 18 Managing schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

About managing schedules in Veritas Operations Manager ... . . . . . . . . . . . . . 413Enabling schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414Disabling schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Contents20

Deleting schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Chapter 19 Managing Veritas Dynamic Multipathing paths . . . . . . . . . 417

About using the Veritas DMP Maintenance functionality in VeritasOperations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Disabling the DMP paths on an array .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Start panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420Select Enclosure panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421Specify Array Port(s) panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Path Disable Confirmation panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Veritas DMP Maintenance Associations Report ... . . . . . . . . . . . . . . . . . . . . . . . 423Paths Disabled panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Disabling the DMP paths on an initiator ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424Select Host(s) panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426Select Initiators panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Re-enabling the DMP paths on an array or initiator ... . . . . . . . . . . . . . . . . . . . . . . . 427Paths Re-Enable Confirmation panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . 429Paths Enabled panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429Veritas DMP Maintenance Result Summary panel ... . . . . . . . . . . . . . . . . . . . 430

Resuming an incomplete DMP maintenance case ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 431Reviewing the output and results of a completed DMP maintenance

case ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432Removing a completed DMP maintenance case record .... . . . . . . . . . . . . . . . . . . . 433

Chapter 20 Managing extended attributes on storageobjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

About using extended attributes on the objects ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435Viewing the list of extended attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436Creating an extended attribute on one or more storage objects ... . . . . . . . . . 437

Create Extended Attribute options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438Modifying an extended attribute ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Edit Extended Attribute options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Removing an extended attribute ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Setting values to the extended attributes on one or more objects ... . . . . . . 441

Set Extended Attributes option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442Modifying the extended attributes value on an object ... . . . . . . . . . . . . . . . . . . . . . 442

Edit Extended Attributes option (object) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

21Contents

Chapter 21 Veritas Operations Manager command lineinterface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

About the vomadm utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445Listing all configured enclosures using the vomadm utility ... . . . . . . . . . . . . . 446Host management using the vomadm utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446Deployment management using the vomadm utility ... . . . . . . . . . . . . . . . . . . . . . . 447Business entity management using the vomadm utility ... . . . . . . . . . . . . . . . . . . 447Service management using the vomadm utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Appendix A Command file reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

sfmw .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450vomsc .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451vxlist ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453vomadm ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458xdistc ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Appendix B Managing Veritas Operations Manager logging . . . . . . . . . . 467

About log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467About log file locations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

Appendix C VOM pricing model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Veritas Operations Manager Advanced License Requirements ... . . . . . . . . . 471

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

Contents22

Basic Veritas OperationsManager tasks

This chapter includes the following topics:

■ About the communication between the managed hosts and Management Server

■ Setting up the Web browser for Veritas Operations Manager

■ Connecting to Veritas Operations Manager Management Server

■ Verifying the version of a managed host in the console

■ Administering a UNIX or a Windows managed host

■ Stopping and starting the Web application

About thecommunicationbetween themanagedhostsand Management Server

Veritas Operations Manager provides you a single, centralized managementconsole for the Storage Foundation and High Availability products. You can useit to monitor, visualize, and manage storage resources and generate reports aboutthem. Veritas Operations Manager lets administrators centrally manage diversedatacenter environments.

A typical Veritas Operations Manager deployment consists of a ManagementServer and the managed hosts. The managed host can run on any platform thatVeritas Operations Manager supports. In a centrally managed deployment, youmust configure one host as Management Server. Management Server receivesinformation about all the resources in its domain. When you log on to ManagementServer, you can gain access to the resources on different hosts within thecentrally-managed deployment.

1Chapter

The installer installs the VRTSsfmcs (Management Server) and the VRTSsfmh(managed host) packages on the host that is designated as Management Server.The VRTSsfmh package contains the XPRTL component that facilitates thecommunication between the managed hosts and Management Server. TheVRTSsfmh package is installed on the managed host and Management Server.

The XPRTL component consists of the following:

■ The XPRTLD component, which is a light weight and full-featured Web server.

■ The XPRTLC component, which is an HTTP client that is based on commandlines. The XPRTLC component can send information to Web servers .

The XPRTLD and the XPRTLC components are integrated with VeritasAuthentication Services for secure SSL communication over HTTP.

The communication between the managed host and Management Server occursthrough the HTTPS protocol. The XPRTLD Web server running on both themanaged host and Management Server supports the Common Gateway Interface(CGI) standards. The managed hosts use XPRTLC and invoke CGI through theXPRTLD on Management Server to perform several actions such as the VeritasOperations Manager database update. Management Server uses XPRTLC andinvokes CGI through the XPRTLD on the managed hosts to perform various actionsthat include Storage Foundation and high availability operations.

See “About the frequency of managed host information discovery” on page 24.

About the frequency of managed host information discoveryThe following table describes the frequency of the managed host informationupdates in the Management Server database. The discovery on each managedhost is divided into families to focus on a particular functional area:

Discovered informationFrequencyin minutes

Family

The operating system, packages, and networking for the host.

Typically, most of the information that is related to this familydoes not change frequently.

1440Host

Volume Manager, File Systems, and the related storagenetwork.

30SF

Veritas Cluster Server and the related information.60VCS

Oracle, DB2, MSSQL, and Sybase databases and their storagedependencies.

60DB

Basic Veritas Operations Manager tasksAbout the communication between the managed hosts and Management Server

24

Discovered informationFrequencyin minutes

Family

The licenses that are installed on the hosts.1440LDR

Configuration status and external faults.5NR

Third-party volume management information.360Native

Oracle Solaris zones and their storage dependencies.120Zones

Oracle Solaris LDoms, and related CPU and memoryinformation.

120LDoms

KVMs, and their correlation with the host.120KVM

Virtual machines and storage discovery.120Hyper-V

Hosts, guests, and storage information.360LPAR

ESX servers, virtual machines, and their storage dependencies.

Note:This information is discovered only when Control HostAdd-on is installed on a managed host that is designated asthe control host.

360VMware

The following information on the hosts that are configuredon the control host for agentless:

■ The IP addresses, operating system, and the usage of theCPU and memory

■ The host bus adapters (HBAs) on the host

■ The disks on the hosts and their correlation with the arrayLUNs and multipathing

■ The volumes and the volume groups on the native VolumeManager

■ The mount points of the file systems and the correlationof the file systems with the disks

■ In a VMware guest environment, the correlation of theguest with the virtual machine and the correlation of thestorage in the guest with the storage exported from theESX server.

Note:This information is discovered only when Control HostAdd-on is installed on a managed host that is designated asthe control host.

360Agentless

25Basic Veritas Operations Manager tasksAbout the communication between the managed hosts and Management Server

Note:The discovery for the Storage Foundation and Veritas Cluster Server familiesis event driven and scheduled. This means that the discovery is triggered whenconfiguration changes occur on the managed hosts. As a result, this informationmust be updated in the Veritas Operations Manager database in the followingupdate. If configuration changes are not detected on the managed hosts, thecommunication between the managed host and Management Server is restrictedto the heartbeat communication that occurs every five minutes. You can connecta managed host to multiple Management Servers. The performance of a managedhost is not affected in this scenario because the discovery happens only once.Reporting of the state as per the host configuration is done based on the numberof Management Servers to which the managed host reports.

See “About the communication between the managed hosts and ManagementServer” on page 23.

Setting up the Web browser for Veritas OperationsManager

If you use Internet Explorer 7.0, or later, on Windows Server 2008, or Firefox 3.0,or later, the Web pages for configuring and launching Veritas Operations Managerare not displayed. You need to set up the Web browser to display the Web pages.For Internet Explorer 7.0, or later, on Windows Server 2008, if the Web pages arenot automatically displayed, add each Web site to the TrustedSites list. On Firefox3.0, or later, if a security exception is displayed, add the exception to the Webbrowser to override how Firefox identifies the sites.

To set up Internet Explorer 7.0, or later, on Windows Server 2008 for VeritasOperations Manager

1 In Internet Explorer, select Tools > Internet Options.

2 Select the Security tab.

3 Click Sites to add the following Web sites:

■ https://hostname:5634/—URL to configure Veritas Operations Manager

■ https://hostname:14161/—URL to launch Veritas Operations Manager

where, hostname is the name of the Management Server host.

Basic Veritas Operations Manager tasksSetting up the Web browser for Veritas Operations Manager

26

To set up Firefox 3.0, or later, for Veritas Operations Manager

1 On the security exception page that is displayed when you attempt to openan Veritas Operations Manager Web page, click the Or you can add anexception link.

2 Click Add Exception.

For Firefox 3.6.x, or later, the users should first click the I Understand theRisks button before they click the Add Exception button.

3 In the Add Security Exception dialog, verify that the location is one of thefollowing:

■ https://hostname:5634/—URL to configure Veritas Operations Manager

■ https://hostname:14161/—URL to launch Veritas Operations Manager

where, hostname is the name of the Management Server host.

4 Click Get Certificate.

5 Select the Permanently store this exception check box.

6 Click Confirm Security Exception.

The Web page is now displayed.

Connecting to Veritas Operations ManagerManagement Server

After downloading the installation files, you must install and configure VeritasOperations Manager Management Server.

For more information on installation and configuration, refer toVeritasOperationsManager Management Server Installation Guide.

You can use any supported Web browser to connect to Management Server.

27Basic Veritas Operations Manager tasksConnecting to Veritas Operations Manager Management Server

To connect to Veritas Operations Manager Management Server

1 On a client system that has a network connection to the host, open a Webbrowser.

Your browser must be configured to accept cookies. If you are using pop-upblockers, either disable them or configure them to accept pop-ups from thehost.

2 In the browser’s address field, type the following URL and press Enter:

https://hostname:14161/

where hostname is the host name, fully-qualified host name, or IP address ofManagement Server.

Example: https://myhost.example.com:14161/

For Internet Explorer 7.0 on Windows Server 2008, or Firefox 3.0, if the Webpage does not get displayed, you have to set up the browser.

See “Setting up the Web browser for Veritas Operations Manager” on page 26.

3 In the username and password fields, type credentials for a valid operatingsystem network domain account.

The Authentication Service automatically recognizes users in the domain—forexample, unixpwd or NT—on which the Authentication Broker host is amember.

4 Click Login.

You can view the Veritas Operations Manager dashboard.

Verifying the version of amanagedhost in the consoleAfter you have installed or upgraded a managed host, you can verify its versionin the Management Server console.

To verify the version of a managed host in the console

1 In the Management Server console, click Settings > Host.

2 In the Host view that is displayed, verify the managed host version in theMH Version column.

Administering a UNIX or a Windows managed hostYou can perform the Storage Foundation tasks on a UNIX or a Windows managedhost. You can perform the Storage Foundation tasks after you install Storage

Basic Veritas Operations Manager tasksVerifying the version of a managed host in the console

28

Foundation Administration for Unix Add-on and Storage FoundationAdministration for Windows Add-on.

In Veritas Operations Manager, the prebundled Veritas Operations ManagerAdd-on for Storage Foundation Administration lets you do some of the importantStorage Foundation tasks without using the Administer link on the VeritasOperations Manager console. In the Veritas Operations Manager console, you canselect multiple objects to perform operations on them simultaneously in a batch.

Using the Veritas Operations Manager Add-on for Storage FoundationAdministration, you can perform the Storage Foundation operations for thefollowing storage objects:

■ The volumes and the disk groups that are managed by Veritas Volume Manager.

■ The disks that are controlled by Veritas Volume Manager.

■ The native file systems and the Veritas File System that are mounted on theStorage Foundation volumes.

The Veritas Operations Manager Add-on for Storage Foundation Administrationis enabled by default in Veritas Operations Manager.

For more information on using the Veritas Operations Manager Add-on for StorageFoundation Administration, refer to Veritas Operations Manager ManagementServer Add-ons User's Guide.

You must have the administrator privileges on a UNIX or a Windows managedhost to perform the Storage Foundation tasks on them.

Note: In Veritas Operations Manager, the managed hosts on the HP-UX 11.11platform that contain the Storage Foundation 3.5 stack is supported in read-onlymode. The Administer link for these managed hosts is disabled.

To administer a UNIX or a Windows managed host

1 In Veritas Operations Manager console, select Manage > Hosts.

2 In the Hosts view, in the table that lists the hosts, click the name of the hostthat you want to administer.

3 In the details view of the host, at the bottom of the the Breadcrumb bar thatshows the navigation path to the current page, on the task toolbar, clickAdminister.

If the Administer link has a red arrow that is displayed after it, you cannotperform the UNIX or the Windows managed host administration.

See “About Veritas Operations Manager solutions” on page 76.

29Basic Veritas Operations Manager tasksAdministering a UNIX or a Windows managed host

Stopping and starting the Web applicationYou can stop and restart Veritas Operations Manager Web UI framework.

To stop and restart Veritas Operations Manager Web UI framework

1 Open an operating system console and log on as root to Management Server.

2 Depending on the platform of Management Server, use one of the followingto restart Veritas Operations Manager Web UI framework:

■ Solaris and Red Hat Linux: Execute the /opt/VRTSsfmcs/cweb/sfmw

restart command.

■ Windows: Under Service Control Manager (services.msc), restart theStorage Manager Service service.

See “Setting up the Web browser for Veritas Operations Manager” on page 26.

Basic Veritas Operations Manager tasksStopping and starting the Web application

30

Configuring ManagementServer settings


■ About the methods to enhance the availability of Management Server

■ Viewing the Management Server settings

■ Configuring SMTP settings for email notifications

■ Enabling the analytics gathering on Management Server

■ About enabling Veritas Operations Manager Advanced features on ManagementServer in Veritas Operations Manager

■ Setting the period for retaining the alert and the task logs in the database

■ About configuring Web server settings in Veritas Operations Manager

■ Configuring the Web server settings

■ Viewing the details of active users logged in to Management Server

About the methods to enhance the availability ofManagement Server

In Veritas Operations Manager, you have the following three methods to enhancethe availability of Management Server:

■ Configure more than one host as Management Servers in your datacenter:Veritas Operations Manager lets the managed hosts in your datacenter toreport to more than one Management Servers. Therefore, you can configure

2Chapter

more than one host in your datacenter as Management Servers to enhancetheir availability.

■ Configure Veritas Operations Manager in high availability environment:Configuring Veritas Operations Manager in high availability environment(Veritas Operations Manager HA configuration) enhances the availability ofManagement Server. Also, this configuration improves the availability of theapplications and the services that Veritas Operations Manager provides. Forthe Veritas Operations Manager HA configuration, you must use a two-nodeVCS cluster in which Storage Foundation HA 5.0 is installed.For additional information, refer toVeritas OperationsManagerManagementServer Installation Guide.

■ Configure the disaster recovery feature on the Veritas Operations ManagerHA configuration:You can configure the disaster recovery feature on Veritas Operations Managerthat is configured in high availability environment. This configurationenhances the failover support and the availability of Management Server inyour globally distributed datacenter. You must replicate the Veritas OperationsManager database and the domain-wide information that is stored in the sharedstorage to the second site as part of configuring the disaster recovery feature.For additional information, refer toVeritas OperationsManagerManagementServer Installation Guide.

Viewing the Management Server settingsThe Management Server settings view lets you do the following:

■ Configure the SMTP settings for Management Server.

■ Enable the analytics gathering on Management Server.

■ Enable the Veritas Operations Manager Advanced features on ManagementServer.

■ Set the database retention policy.

■ Set log levels and Web server session timeout.

■ View the details of the active users who have logged in to Management Server.

To view the Management Server settings

◆ In Veritas Operations Manager console, select Settings>General to view theManagement Server settings.

See “Configuring SMTP settings for email notifications” on page 33.

See “Enabling the analytics gathering on Management Server” on page 34.

Configuring Management Server settingsViewing the Management Server settings

32

See “Enabling Veritas Operations Manager Advanced features on ManagementServer in Veritas Operations Manager” on page 35.

See “Setting the period for retaining the alert and the task logs in the database”on page 36.

See “Configuring the Web server settings” on page 37.

See “Viewing the details of active users logged in to Management Server”on page 38.

Configuring SMTP settings for email notificationsIn the Settings > General view, you can configure the SMTP settings forManagement Server. Under SMTPSettings, you must enter the following details:

Enter the SMTP mail server host name. Validformats include: Fully Qualified DomainName (FQDN), IP address, or, if the networkhandles DNS resolution for host names, ashortened host name.

Examples:

Host123, Host123.example.com,xxx.yyy.zzz.aaa

SMTP Server

Enter the SMTP mail server port number.SMTP Port

Enter a valid email address for the sender.This email address appears as the sender ofall the emails that a rule sends out.

Example: [email protected]

Sender Account

Note: Before you specify the email notifications for alert rules or policy checkscan completion, or send a report by email, you must configure the SMTP detailsfor Management Server.

Also, you can send a test email to the recipient's account to verify the SMTPsettings that you have configured. To send the test email, you must enter thefollowing details:

Enter a valid email address of the recipient.Recipient Account

Enter the test email message that you wantto send to the recipient.

Test Message

33Configuring Management Server settingsConfiguring SMTP settings for email notifications

To configure SMTP settings for email notifications

1 In the Veritas Operations Manager console, select Settings > General.

2 Under SMTP Settings, enter the SMTP details and click Save Settings.

To verify the SMTP settings

1 Under SMTP Settings, click Test SMTP to display the fields where you mustenter the details for verifying the SMTP settings.

2 Enter the valid email address of the recipient and the test email message.Click Send Test Mail.

See “Viewing the Management Server settings” on page 32.

Enabling the analytics gathering on ManagementServer

Veritas Operations Manager uses Web beacons (also known as single pixel or clearGIFS) to provide statistical information such as the frequency of use of particularfeatures or views of the Veritas Operations Manager user interface in yourorganization to help analyze product usage. The information does not identifythe users. Symantec analyzes this data to understand the information that is ofmost interest to the customers and the features that the customers use most.

In the ManagementServerSettings view, you can enable the analytics gatheringon Management Server.

If the Enable Analytics Gathering option is enabled while you configureManagement Server, the EnableAnalyticsGathering check box appears selected.You can clear the Enable Analytics Gathering option selection to disable theanalytics gathering on Management Server.

To enable analytic gathering on Management Server


2 In the Analytics Gathering Settings section, select the Enable AnalyticsGathering check box and click Save Settings.


Configuring Management Server settingsEnabling the analytics gathering on Management Server

34

About enablingVeritasOperationsManagerAdvancedfeatures onManagementServer inVeritasOperationsManager

Veritas Operations Manager 5.0 has a few paid features that you can use byenabling Veritas Operations Manager Advanced features on Management Server.These features include:

■ Discovery of hosts that do not have Veritas Storage Foundation and HighAvailability (SFHA) products from Symantec installed on them and insteadusing the native operating system vendor’s storage management tools. Thisdiscovery can be done using an agent or an agentless mechanism.

■ Discovery of network-attached storage (NAS)

After Installation or Upgradation to Veritas Operations Manager 5.0, all the VeritasOperations Manager Advanced features are available to the users. You can viewthe VOM Management Entitlement Report on Management Server to be aware ofyour licensing status for the Veritas Operations Manager Advanced features. Toenable or disable the Veritas Operations Manager Advanced features you need toaccept an End Users License Agreement (EULA).

If you do not use the Veritas Operations Manager Advanced features, a messagein the footer of Veritas Operations Manager console displays that the Advancedfeatures are not activated. If you use the Veritas Operations Manager Advancedfeatures without accepting the EULA, the license information is displayed as Demolicense and you are prompted to enable the features by accepting EULA. Once youaccept the EULA, the license information changes to Permanent license.


Enabling Veritas Operations Manager Advanced features onManagement Server in Veritas Operations Manager

In the ManagementServerSettings view, you can enable the Veritas OperationsManager Advanced features on Management Server.

If the Veritas Operations Manager Advanced features on Management Server isenabled, the AcceptLicenseAgreement check box appears selected. You can clearthe AcceptLicenseAgreement option selection to disable the Veritas OperationsManager Advanced features on Management Server.

35Configuring Management Server settingsAbout enabling Veritas OperationsManager Advanced features onManagement Server in Veritas OperationsManager

To enable Veritas Operations Manager Advanced features on Management Server

1 In Veritas Operations Manager console, select Settings > General.

2 In the Veritas Operations Manager Advanced License Agreement section,select the Accept License Agreement check box and click Save Settings.


Setting the period for retaining the alert and the tasklogs in the database

In the Management Server Settings view, you can set the period for retainingthe alert and the task logs. After this period, the alert and the task logs are removedfrom the Veritas Operations Manager database.

You must enter the following details for setting the period for retaining the alertand the task logs:

Select the period for which you want toretain the alert logs in the Veritas OperationsManager database.

You can select one of the following options:

■ 7 days■ 15 days■ 21 days■ 30 days

Alert Log

Select the period for which you want toretain the task logs in the Veritas OperationsManager database.

You can select one of the following options:

■ 7 days■ 15 days■ 21 days■ 30 days

Task Log

To set the period for retaining the alert and the task logs in the Veritas OperationsManager database


2 Under the Database Retention Policy Settings section, set the period forretaining the alert and the task logs and click Save Settings.

Configuring Management Server settingsSetting the period for retaining the alert and the task logs in the database

36


About configuring Web server settings in VeritasOperations Manager

In the Management Server Setting page, Veritas Operations Manager helps youconfigure the following:

■ Log level for the log files in the Web server.

■ User session timeout period for the Web server.

You can set the levels of the Web server log as Severe, Warning, Info, or Debug.By default the log level is set as Info. Also, Veritas Operations Manager lets youspecify whether you need a cumulative log record for all the Web server sessionsthat you have used.

Veritas Operations Manager helps you manage the user session timeout periodfor the Web server. Veritas Operations Manager lets you specify the timeout periodin minutes. By default, the user session time out period in Veritas OperationsManager is 30 minutes. If you want to disable the user session timeout period forthe Web server , you must enter -1 in the Web server session timeout field.

See “Configuring the Web server settings” on page 37.

Configuring the Web server settingsIn the Management Server Settings view, you can set following:

■ Log levels for all the log files that are created in the Web server

■ Timeout period for the Web server session

You must enter the following details to set the log levels for all the log files:

Select the log level that you want to set forall the log files in the Web server .

You can select the following options:

■ Severe

■ Warning

■ Info

■ Debug.

By default, Veritas Operations Manager setsthe log level as Info.

Log level

37Configuring Management Server settingsAbout configuring Web server settings in Veritas Operations Manager

Specify whether you want to allow log rollover in Veritas Operations Manager. If youselect No, the logs for a particular sessionare removed at the end of the session. If youselect Yes, logs for all the sessions are addedtogether to let you access a cumulative logrecord.

By default, Veritas Operations Managerdisplays No in this field.

Enable log roll over

To enable the timeout period for the Web server, you must enter the timeoutperiod in minutes. By default, the timeout period for the Web server is 30 minutes.To disable the Web server timeout, you must enter -1 in the Web server sessiontimeout field.

To configure the Web server settings in Veritas Operations Manager


2 In the ManagementServerSettings view, under WebServerSettings, enterthe details and click Save Settings.


Viewing the details of active users logged in toManagement Server

In the Settings > General view, under Active Users, you can view the followinginformation about active users logged in to Management Server:

■ User name with which the active user has logged in to Management Server

■ Date and time at which the user has logged in to Management Server

■ The time for which the user was idle in Veritas Operations Manager

■ Host name or IP address of the host from which the user logs in

To view the details of active users logged in to Management Server


2 In the Active Users section, you can view the details of the active users whohave logged in to Management Server.


Configuring Management Server settingsViewing the details of active users logged in to Management Server

38

Managing alerts


■ About faults and risks

■ Viewing faults and risks

■ About analyzing faults

■ Analyzing faults

■ Suppressing faults

■ Viewing the faults definitions

■ Suppressing the fault definitions

■ Activating suppressed fault definitions

■ Activating suppressed faults

■ About alerts

■ About alert rules

■ Creating alert rules

■ Viewing the overview of a rule

■ Modifying alert rules

■ Copying alert rules

■ Enabling alert rules

■ Disabling alert rules

■ Deleting alert rules

3Chapter

■ Viewing alerts

■ About tasks

■ Viewing tasks

■ About messages posted on Activity Board

■ Viewing the messages posted on the Activity Board

■ Deleting a message that is posted on Activity Board

■ About setting alerts for replication

■ Setting the alerts for replication

About faults and risksVeritas Operations Manager enables you to view all possible problems in theenvironment that it manages at several levels in the user interface.

You can monitor the faulty status and possible risks to the managed resourcesand also analyze each fault to understand its implications and causes. You canalso automate error handling by developing rules that trigger specific actions inresponse to alert conditions.

Faults in the SFHA environment are hierarchical in nature. For example, a faulton the disk causes a fault on the related volume, which in turn, causes a fault inthe VCS resource managing it. Hence, it is very easy to identify the source of thefault using Veritas Operations Manager.

Faults are displayed in the following Veritas Operations Manager views:

■ Faults view: Lists all the faulted entities in the managed environment alongwith fault source, time and cause.

■ Individual object detail view:Indicates the possible cause, source, and timeof the fault. It also indicates the objects's association with the business entitythat is also impacted.

■ Businessentitiesview: Indicates all the faults for the business entity, possiblecauses, source, and time of the fault.

Veritas Operations Manager fault and risk monitoring answers the following typesof questions:

■ What are the conditions of the managed entities (applications, storageenclosures, hosts, clusters and so on) in the environment?

■ What are some of the possible causes of the fault?

Managing alertsAbout faults and risks

40

■ What is the source of the fault?

■ What was the time when the fault occurred?

■ Are there any critical connections that are disabled?

■ How much space remains on critical storage?

See “About analyzing faults” on page 41.

Viewing faults and risksOn Faults and Risks page, you can view the system identified fault conditionsalong with their corresponding faulty entities and the fault sources. If required,you can suppress one or more faults for a specific period using the SuppressFaults option. You can also create rules for a selected fault. The rule determinesthe action that Veritas Operations Manager performs when it receives the alertthat is related to a faulty entity. Click the Analyze icon to view the Faultdependencyview panel that displays the hierarchy of a particular fault. You musthave administrative privileges to create rules and suppress faults.

Using the provided search filter, you can search existing faults based on variouscriteria. For example, suppress status of the fault, type of the fault, type of thefaulty entity and the storage type. Since it is dynamic search, the displayed faultlist changes automatically as you type the term in the Search text box or whenyou select the check box for faulty entities. For instance, when you select Exchangecheck box in Faulted Entity Type, the application displays a list of only thosefaulty entities where Microsoft Exchange Server is installed. Similarly, when youselect Showonlybasefaults check box in Faulttype, Veritas Operations Managerdisplays a list of only the base faults.

To view faults and risks

1 In Veritas Operations Manager console, select Monitor > Faults.

2 On the left panel, in Search text box, type the name of the fault that you wantto search.

Click Show all Faults and Risks to view the list of all faults.


See “Analyzing faults” on page 42.

About analyzing faultsFollowing data is displayed about the faults and risks in the managed objects bythe Veritas Operations Manager console:

41Managing alertsViewing faults and risks

■ Fault hierarchy: A graphical view shows the hierarchy of faults with severitiesassociated with each fault. You can click on each fault to change the displayon the right pane and provide more information on the selected fault.

■ Fault details: A detailed message about the fault, the time of the fault, the logsrelated to each object (if available), the associated alert, and the suppressedinformation on each fault.

■ Possible causes and related faults: A list of possible causes that created thefault. You can also add more causes that are specific to your environment foreach fault ID.

■ Possible troubleshooting recommendations: A list of actions defined for eachfault ID. These actions link to live pages to perform the remedial action. Youcan add remedial actions specific to your environment to each fault ID.

■ Links to UMI/SORT

■ Root cause analysis tool

Analyzing faultsVeritas Operations Manager lets you analyze faults that are reported on storageobjects.

After you analyze a fault, you can view the following details in the Faultdependency view panel:

■ Name of the entity where the fault occurred.

■ Type of the faulted entity.

■ Possible cause of the fault.

■ Source of the fault.

■ Date and time at which the fault occurred.

Also, the Fault dependency view panel gives you a graphical representation ofthe dependencies of the faulted entity.

In Veritas Operations Manager, you can analyze faults from the FaultsandRisksview.

Also, you can analyze faults from the Overview view of the following storageobjects:

■ Business entities

■ Hosts

■ Disks

Managing alertsAnalyzing faults

42

■ Disk groups

■ Volumes

■ File systems

■ Clusters

■ Service groups

■ Replications

To analyze faults from the Faults and Risks view

1 In the Veritas Operations Manager console, select Monitor > Faults.

2 In the Faults and Risks view, in the Faulted Conditions table, select thecorresponding check box of the fault that you want to analyze.

3 In the FaultedConditions table, click the Analyze icon to display the detailsin the Fault dependency view panel.

To analyze faults from the details view of the Storage object

1 In the Veritas Operations Manager console, select Manage > Storage object.

For example, to analyze faults from the BusinessEntities view, select Manage> Business Entities.

2 Click the name of the storage object to display the details view.

For example, in the BusinessEntities view, click the name of a business entityto display the details view.

3 In the Overview view of the storage object, in the Faulted Conditions table,select the fault that you want to analyze.

For example, in the Overview view of the business entity, in the FaultedConditions table, select the fault that you want to analyze.

4 Do one of the following to display the details in the Fault dependency viewwindow:

■ At the top of the Faulted Conditions table, click Analyze all faults.

■ In the Faulted Conditions table, right-click to select the fault that youwant to analyze. From the shortcut menu, select Analyze all faults.

See “Viewing faults and risks” on page 41.

43Managing alertsAnalyzing faults

Suppressing faultsYou can suppress one or more faults and fault definitions in Veritas OperationsManager. The following features are provided for the fault suppressionmanagement:

■ Ability to temporarily hide one or more faults.

■ Ability to disable the selected faults for the affected fault sources.

■ Ability to disable all the faults for the affected fault sources.

■ Ability to disable the fault definition itself.

For all the options, you can either specify the date and time to keep the faults inthe suppressed state, or you can suppress the faults forever.

When you disable a fault definition, Veritas Operations Manager does not detectits corresponding faults. However, after you activate the fault definition, VeritasOperations Manager again uses that fault definition for subsequent fault detection.

You must have administrator rights to suppress the faults.

To suppress a fault


2 In the FaultsandRisks view, under FaultedConditions table, select the faultthat you want to suppress, and then do one of the following:

■ Click Actions > Suppress Faults.

■ Right-click the fault and from the submenu, select Suppress Faults.

3 On the Suppress Faults wizard panel, enter the required information andclick OK.

See “Suppress Faults options” on page 44.

See “Analyzing faults” on page 42.

See “Activating suppressed faults” on page 48.

Suppress Faults optionsUse this panel to suppress the faults in Veritas Operations Manager. You can hideor disable the faults either temporarily or permanently. You can disable a faultfor a specific object; however, the fault definition is still considered as active forother objects.

For all these options, you can either specify the date and time to keep the faultsin the suppressed state, or suppress the faults forever.

Managing alertsSuppressing faults

44

Table 3-1 Suppress Faults

DescriptionField

Select this option to temporarily hide theselected fault. It is essentially hiding thecurrent instance of the fault. The fault isdisplayed again when it is detected.

Hide the selected fault(s). Show again if theproblem reoccurs.

Select this option to disable the fault for theaffected fault source.

Disable the selected fault(s) for the affectedfault sources

Select this option to disable all faults for theaffected fault source.

Disable all fault(s) for the affected faultsources

Select this option to hide the fault withoutspecifying any time interval.

Hide or disable forever

You can specify the date until which the faultremains suppressed. After this date, the faultis again considered as active in VeritasOperations Manager.

Hide or disable until

Provide the reason why the fault wassuppressed. You can enter up to 254characters for the description.

Reason

See “Suppressing faults” on page 44.

Viewing the faults definitionsYou can view a comprehensive list of all the fault definitions that VeritasOperations Manager uses to generate all faults. You can use this list to view thedefinitions of the faults that are already generated and yet to generate. If you donot want to view a particular fault at all, you can disable its fault definition itselfusing the Suppress Faults option. After the fault definition is disabled, allassociated faults are automatically suppressed. You can suppress the faultdefinition until a specific date, or disable it forever.

Note: Though the option to forever disable a fault definition is provided, you canagain activate the fault definition using the Unsuppress Faults option.

Review the following information on this page:

■ Type: Displays the type of the fault. For example, fault or risk.

45Managing alertsViewing the faults definitions

■ Message: Displays the information about the fault.

■ Entity type: Displays the source object on which the fault has occurred.

■ Affected Types: Displays all the object types that are affected by the fault onthe source object. For example, if a service group (source object) is faulted, itis listed under the Entity Type column. Since a service group is associatedwith managed hosts, clusters, and other objects, Veritas Operations Managergenerates derived faults for these objects. All such associated objects are listedin this column.

To view the faults definitions

◆ In Veritas Operations Manager console, select Monitor > Fault Definitions.

See “About faults and risks” on page 40.


Suppressing the fault definitionsYou can suppress the fault definitions for the faults that you want to disablepermanently. After the definition itself is suppressed, Veritas Operations Managertreats the corresponding faults as non-existing. You can specify a period to keepthe selected fault definition in the suppressed state.

Note: Though the option to forever disable a fault definition is provided, you canagain activate the fault definition using the Unsuppress Faults option.

To suppress a fault definition

1 In the Veritas Operations Manager console, select Monitor > FaultDefinitions.

2 In the Fault Definitions view, select the fault definition that you want tosuppress, and do one of the following:

■ Click Actions > Suppress Faults.

■ Right-click the fault definition and from the submenu, select SuppressFaults.

3 On the Suppress Faults wizard panel, enter the required information andclick OK.

See “Suppress the fault definition panel options” on page 47.

Managing alertsSuppressing the fault definitions

46

Suppress the fault definition panel optionsUse this panel to suppress the selected fault definition. After the fault definitionis suppressed, it is no longer displayed on Veritas Operations Manager userinterface. You can suppress one or more fault definitions simultaneously.

Table 3-2 Suppress Faults

DescriptionField

Select this option to disable the faultdefinition without specifying any timeperiod.

Note: Though the fault definition issuppressed forever, you can still activate it.This option provides additional flexibility tothe users who want to be able to suppressthe definition without specifying date alongwith the ability to re-activate the definition.

Hide or disable forever

You can specify the date until which the faultdefinition remains suppressed. After thisdate, the fault definition is again consideredas active in Veritas Operations Manager.

Hide or disable until

Provide the reason to suppress this faultdefinition. You can enter up to 254characters for the description.

Reason for hiding or disabling

See “Suppressing the fault definitions” on page 46.

Activating suppressed fault definitionsYou can activate a suppressed fault definition using Veritas Operations Managerconsole. After re-activation, Veritas Operations Manager starts using the faultdefinition for subsequent fault detections.

To activate a suppressed fault definition

1 In the Veritas Operations Manager console, select Monitor > FaultDefinitions.

2 In the FaultDefinitions view, select the suppressed fault definition that youwant to activate, and do one of the following:

■ Click Actions > Unsuppress Faults.

47Managing alertsActivating suppressed fault definitions

■ Right-click the suppressed fault definition and from the submenu, selectUnsuppress Faults.

3 On the Unsuppress Faults wizard panel click OK.

See “Activate the suppressed fault definition panel options” on page 48.

Activate the suppressed fault definition panel optionsUse this panel to activate a suppressed fault definition. After the fault definitionis activated, Veritas Operations Manager starts generating faults for this faultdefinition. You can activate more than one fault definitions simultaneously.

See “Activating suppressed fault definitions” on page 47.

Activating suppressed faultsYou can activate the fault that is suppressed in Veritas Operations Manager.

When you suppress a fault, you set a date until which the fault is suppressed.After the specified date, the fault is again considered as active in the system.However, Veritas Operations Manager also provides you with the option to activatethe fault before that set date.

To activate a suppressed fault


2 In the Faults and Risks view, select the suppressed fault that you want toactivate, and do one of the following:

■ Click Actions > Unsuppress Faults.

■ Right-click the suppressed fault and from the submenu, select UnsuppressFaults.

3 In the Unsuppress Faults panel, click OK.

See “Suppressing faults” on page 44.

About alertsYou can monitor the faulty status and performance information of your datacenterenvironment by reviewing alert notices on the Veritas Operations Manager console.You can also automate error handling by developing rules that trigger specificactions in response to alert conditions.

You can set alert notices to show warnings about events and conditions, such asstopped replication or storage capacity, enabled or disabled I/O paths, faulted

Managing alertsActivating suppressed faults

48

clusters and so on. These enable the administrator to make decisions about hisenvironment and the resources managed by Veritas Operations Manager.

You can create rules which trigger actions in response to specific alerts or classesof alerts. You can also create rules which are based on alert severity level, topicor just the alert names, that can trigger one or more actions in response to specificalerts or classes of alerts.

Alerts can trigger actions such as sending emails to operators, displaying consolealerts, sending an SMTP trap, or executing shell scripts and command files.

Veritas Operations Manager alerts provide answers to the following type ofquestions:

■ What are the conditions of the managed entities (applications, storageenclosures, hosts, clusters and so on) in the environment?



The alert severities that categorize the level of error are:

■ Critical

■ Error

■ Warning

■ Information

See “About alert rules” on page 49.

About alert rulesOperators need to manage the condition of the resources in the environment.Operators typically define the custom rules that specify what conditions generatean alert, what actions should occur if an alert is detected, and which actionsgenerate which type of alert severity. With Veritas Operations Manager, you cancreate and maintain rules pertaining to alerts.

When an alert is raised, theVeritas Operations Manager evaluates alert properties(alert name, severity, and classification). If an alert meets the conditions of a rule,theVeritas Operations Manager invokes one or more user-defined actions thatare associated with the rule.

If an alert condition occurs, you can specify that Veritas Operations Managerinitiate one of the following types of actions:

■ Send an email message. For some alert conditions, operators may want to sendemails notifying key personnel about the condition.

49Managing alertsAbout alert rules

■ Send an SNMP trap notification. Some objects are not polled. When eventstake place, these objects send traps or unsolicited asynchronous SNMPmessages to the Server. Some of the rules that Veritas Operations Manageruses to monitor objects in the environment rely on SNMP trap-based messages.The default port for the trap is 162.

■ Execute a command script. For example, if an operator sees an alert thatindicates that a switch is down or that it carries a high volume of traffic, theoperator might execute a script that changes DMP paths so that keyapplications can bypass the problem switch.

■ Upload a custom script and execute it. This facility provides the administratormore control over Veritas Operations Manager.

Note: You must provide the details for the SMTP settings and save them to thedatabase before you set up the email notification for an alert using that SMTPsettings. You can save the SMTP settings on the Settings > General view.

With Veritas Operations Manager, you can create rules and do the following onrules you or anyone else created:

■ Create rules.

■ Edit rules that include renaming, enabling, and disabling rules.

■ Delete rules.

■ Copy rules.

■ Enable rules.

■ Disable rules.

Note: You must have administrator privileges to create, copy, view, or managealert rules.

See “Creating alert rules” on page 50.

Creating alert rulesIn Veritas Operations Manager, you can create the rules that trigger variousactions based on alert conditions. Aside from creating rules from the rules option,you can also create rules for selected faults and alerts.

Managing alertsCreating alert rules

50

To create a rule from the Rules view

1 In the Veritas Operations Manager console, click Monitor > Rules.

2 In the Rules view, at the top of the Rules table, click Actions > Create Rule.

3 In the Create Rule dialog box, select from the following options to create arule, and click Next :

You can create a rule by selecting the alert condition that triggers an action.

You can create a rule by selecting the alert severity level.

You can also create a rule by selecting from a list of alert topics.

See “Create Rule - Alert Conditions options” on page 52.

4 In the dialog box to select the source of the alert trigger, select if you wantto trigger the rule for alerts originating from any host in the domain or specifichost. Click Next.

See “Create Rule - Trigger Alert Source options” on page 53.

5 In the wizard panel to specify the notification medium, select the requiredoption. Click Next.

See “Create Rule - Setup notifications options” on page 54.

6 In the wizard panel to specify the descriptions for the rule, enter the requiredinformation. Click Finish

7 See “Create Rule - Description” on page 57.

8 In the Result panel, verify that the rule has been successfully created.

To create a rule from the Faults and Risks view

1 In the Veritas Operations Manager console, click Monitor > Faults.

2 From the Faulted Conditions table, select the fault for which you want tocreate the rule.

3 Click Actions > Create Rule.

4 In the CreateRule panel, enter the alert that triggers actions for the rule thatyou create. Click Next.


5 In the wizard panel to specify the alert source, select the required option.Click Next.


51Managing alertsCreating alert rules




See “Create Rule - Description” on page 57.


To create a rule from the Alerts view

1 In the Veritas Operations Manager console, click Monitor > Alerts.

2 From the Alerts table, select the alert for which you want to create a rule.

3 Click Actions > Create Rule.

4 In the CreateRule panel, enter the alert that triggers actions for the rule thatyou create. Click Next.


5 In the wizard panel to specify the alert source, select the required option.Click Next.





See “Create Rule - Description” on page 57.


See “About alert rules” on page 49.

See “Modifying alert rules” on page 59.

Create Rule - Alert Conditions optionsUse this panel to define the context and conditions of an alert that triggers anautomatic action.

Table 3-3 refers to possible alert condition options that you can select to createa rule.


52

Table 3-3 Create Rule - Alert Conditions

DescriptionField

Select this option to trigger this rule for anyalerts with the selected severity. Each alertis assigned a severity level upon creation.You can set the rule to trigger the automaticaction for all alerts with a specific severitylevel.

You can select the following severity levelsfor the alert:

■ Critical

■ Error

■ Warning

■ Information

The default severity is Critical.

This rule will be triggered for all alerts witha severity of

Select this option to trigger the rule whenthe specifically entered alert ID(s) occur.Each alert is assigned an alert ID uponcreation. You can set the rule to trigger theautomatic action for all alerts with a specificalert ID.

Use semicolon (;) to separate multipleentries.

Enter the alert(s) that will trigger theaction(s) for this rule

Select this option to trigger this rule whenspecific alerts occur. Click Next > to displaya list of all alert topics and classificationsthat are available.

Choose from a list of alerts


Create Rule - Select Alerts optionsUse this panel to select the specific alerts that will trigger this rule. Select thealerts from the table. The table contents reflect the filtering selections made inthe Create Rule - Alert Conditions panel.


Create Rule - Trigger Alert Source optionsUse this dialog box to select the specific alert sources that triggers this rule.


Table 3-4 refers to possible Trigger Alert Source options that you can select tocreate a rule.

Table 3-4 Create Rule - Trigger Alert Source options

DescriptionField

Select this option to activate the rule whenthe designated alert occurs on any monitoredhost in the domain. This is the defaultselection.

Trigger Rule for alerts originating from anyhost in the domain

Select this option to activate the rule whenthe designated alert occurs on specific hostsin the domain.

To specify the host, check the name of thehost. You can also filter the list of the hosts.

Trigger rule for alerts originating fromspecific hosts


Create Rule - Setup notifications optionsUse this wizard panel to set up notifications for the rule. You can select any or allof the following check boxes to set up the notification:

Note: You can choose multiple notification options. For all the notificationsmethods that you have selected, fill in the required information.

Table 3-5

DescriptionField

Select to set up an email notification whenthe alert conditions that are specified by therule occur.

Email

Select to send an SNMP Trap when the alertconditions that are specified by the ruleoccur.

SNMP Trap

Select to run a command script when thealert conditions that are specified by the ruleoccur.

Command script


54

Table 3-5 (continued)

DescriptionField

Select to run a custom script when the alertconditions that are specified by the ruleoccur.

Custom script

You must set up at least one type of notification for the rule that you create.

Table 3-6

DescriptionField

Enter the email address of one or more usersor groups that you want Management Serverto notify. Separate the multiple entries witha comma (,). Visible only when email isselected.

Example: [email protected],[email protected]

Email: To



DescriptionField

Displays the email body format. Not Editable.Variables, indicated by the words in brackets,are replaced by the specific alert informationindicated.

[Rule Name] = The name of the rule that isspecified in the first dialog box.

[Alert Message] = The message in the alert.Set by the alert.

[Severity Level] = The severity of the alert.For example, Critical.

[Description] = The detail description for thealert. Set by the alert.

[Action] = The recommended action thatshould be done for the alert.

[Source Host] = The host where the alertoriginated.

[Alert Classification] = The classification ofthe alert. Set by the alert.

[Alert Name] = The name of the alert. Set bythe alert.

[Alert Date And Time] = The timestampwhen the alert was first created on thesource host.

Email: Email Format

Select to send the email notification as dailydigest.

If you select this check box, VeritasOperations Manager combines all your emailalert notifications into one summary emailand sends to you everyday.

Email: Send email as daily digest

Enter the IP Address or name of the hostwhere the SNMP trap console is located.Visible only when SNMP Trap is selected.

Example: Host123.example.com

SNMP Trap: Host

Displays the port number 162, the defaultport number for SNMP traps. You can editthe port number, if required.

SNMP Trap: Port


56


DescriptionField

Enter the name of the host where thecommand script file is located. Maximumlength is 255 characters. The source hostname cannot contain spaces.


Command Script: Source Host

Enter the path and name of the commandscript file. Maximum length is 255characters. Valid entries should contain thefull path and a valid file name. Visible onlywhen Command script is selected.

Example: /opt/scripts/script1.exe

Command Script: Source File

Enter the name of the host where thecommand script file is to be executed.Maximum length is 255 characters. Thedestination host name cannot containspaces. Accepts multiple entries that areseparated by comma(,).


Command Script: Destination host

Browse the custom script file and upload it.

You can only upload the following types ofscripts:

■ perl (.pl)

■ shell (.sh)

■ batch (.bat)

Custom script: Custom script


Create Rule - DescriptionUse this panel to assign a name and description to a new rule. Rules define theautomatic actions taken when specific alerts are generated, and they are listedon the Rule Manager tab.

For example, a rule can automatically run a script to restart an application whenit receives an alert saying that the application has stopped. This allows networkadministrators to automate routine tasks and focus their energies on more criticalissues.


Table 3-7 Create Rule - Description

DescriptionField

Enter the name of the rule. Maximum fieldlength is 255 characters.

Example: Restart stopped ABC program.

Rule Name

Enter a description for this rule. Thedescription should include the purpose ofthe rule. Maximum field length is 255characters. Example: When the ABC programgenerates a service stopped alert, run therestart program script and send an alert tothe SNMP trap console.

Description

Clear to disable the rule. The default isenabled. An enabled rule monitors alerts forthe defined conditions.

Enable Rule


Viewing the overview of a ruleThe Rule page displays the properties of the selected rule. The information onthis page includes:

■ Overview: It includes name of the rule, its description, its current state, nameof the owner, and the date when the rule was last modified.

■ Alert Conditions: It includes the alert conditions that are configured for thisrule.

■ Actions: It displays the actions the system performs when a rule is executed.The information includes E-mail notification details, SNMP configuration,command file details, and the information about custom script.

You can create rules for faults as well as alerts from their respective user interfacepanels. All such rules are also displayed on this page.

To view the overview for a rule

1 In the Veritas Operations Manager console, select Monitor > Rules.

2 Click the rule.



Managing alertsViewing the overview of a rule

58

See “Disabling alert rules” on page 67.

Modifying alert rulesIn Veritas Operations Manager, you can modify an alert rule that you have created.You can modify the following elements of an alert rule:

■ Alert condition

■ Alert source

■ Notification method

■ Name and description

You can modify the alert rule from the following views:

■ Rule Manager view

■ Details view of the individual alert

You must have administrator privilege to modify an alert rule.

To modify a rule

1 In the Veritas Operations Manager console, click Monitor > Rule.

2 In the Rules table, click the name of the rule that you want to modify and doone of the following:

■ Click Actions > Edit Rule.

■ In the Overview view of the rule, click Edit Rule.

3 In the Edit Rule - Alert Conditions panel, modify the alert condition thattriggers an action, and click Next to continue.

See “Edit Rule - Alert Conditions options” on page 60.

4 If you chose the multiple alerts condition in step 4, in the Edit Rule - SelectAlerts panel, check one or more alerts in the table, and click Next to continue.

See “Edit Rule - Select Alerts options” on page 61.

5 In the Edit Rule - Trigger Alert Source panel, modify the selection of therequired alert source, and click Next to continue.

See “Edit Rule - Trigger Alert Source options” on page 61.

6 In the Edit Rule - Setup notifications panel, modify the notifications thatyou have specified for the rule, and click Next to continue.

See “Edit Rule - Setup notifications options” on page 62.

59Managing alertsModifying alert rules

7 In the Edit Rule - Name panel, modify the details of the rule, and click Nextto continue.

See “Edit Rule - Name options” on page 64.

8 In the Result panel, verify that the rule has been successfully modified. ClickOK.

You can view the modified rule listed in the Rules table. If you elected toenable the rule immediately, the rule is followed as soon as its conditions aremet.


See “Copying alert rules” on page 65.

See “Deleting alert rules” on page 67.


See “Enabling alert rules” on page 66.

Edit Rule - Alert Conditions optionsUse this panel to define the context and conditions of an alert that triggers anautomatic action.

Table 3-8 Edit Rule - Alert Conditions

DescriptionField

Select this option to trigger this rule for any alerts with the selectedseverity. Each alert is assigned a severity level upon creation. You canset the rule to trigger the automatic action for all alerts with a specificseverity level.

You can modify the severity level for the alert by selecting any of thefollowing:

■ Critical

■ Error

■ Warning

■ Information

The default severity is Critical.

This rule will betriggered for allalerts with aseverity of

Managing alertsModifying alert rules

60

Table 3-8 Edit Rule - Alert Conditions (continued)

DescriptionField

Enter the alert topics that trigger the actions for this rule. If you entermultiple topics, you must separate each topic with a semi-colon

Enter the alerttopic(s) that willtrigger theaction(s) for thisrule(separated by';')

Select this option to trigger the rule when specific alerts occur. ClickNext to display a list of all alert topics and classifications that areavailable, optionally filtered according to these criteria:

■ Severity: Select to filter the alerts based on severity level. Selectthe filter’s severity level from the drop-down list.

■ Topic: Select to filter the alerts based on the entered topic. Enterthe text for the filter to sort the topics. You can enter partial textto view all alert conditions with the partial text in the topic field.Wildcard characters, such as an asterisk (*), or multiple wordentries are not valid.

Choose from a listof alerts


Edit Rule - Select Alerts optionsUse this panel to select the specific alerts that will trigger this rule. Select thealerts from the table. The table contents reflect the filtering selections made inthe Edit Rule - Alert Conditions panel.

Select the Include VEA alert topics check box to include the alerts specific toVeritas Enterprise Administrator.


Edit Rule - Trigger Alert Source optionsUse this panel to select the specific alert sources that triggers the rule.

Table 3-9 Edit Rule - Trigger Alert Source

DescriptionField

Select this option to activate the rule when the designated alert occurson any monitored host in the domain. This is the default selection.

Trigger Rule foralerts originatingfrom any host inthe domain


Table 3-9 Edit Rule - Trigger Alert Source (continued)

DescriptionField

Select this option to activate the rule when the designated alert occurson specific hosts in the domain.

To specify the host, check the name of the host. You can also filterthe list of the hosts.

Trigger rule foralerts originatingfrom specific hosts


Edit Rule - Setup notifications optionsUse this wizard panel to modify the notifications that you set up for the selectedrule. You can select any or all of the following check boxes to modify thenotification setup:

Select to modify the email notification.Email

Select to modify the SNMP Trap.SNMP Trap

Select to modify the command action.Command Action

Select to modify the custom script that youhave specified.

Custom script

Table 3-10 Edit Rule - Setup notifications options

DescriptionField

Email

Enter the email address of one or more usersor groups that you want Management Serverto notify. Separate multiple entries withcomma (,). Visible only when email isselected.

Example: [email protected];[email protected]

To


62

Table 3-10 Edit Rule - Setup notifications options (continued)

DescriptionField

Displays the email body format. Not Editable.

The specific alert information replaces thevariables that are indicated in brackets inthe following list:

■ [Rule Name] = The name of the rule thatis specified in the first dialog box.

■ [Alert Message] = The message in thealert. Set by the alert.

■ [SeverityLevel] = The severity of the alert.For example, Critical.

■ [Description] = The detail description forthe alert. Set by the alert.

■ [Action] = The recommended action thatshould be done for the alert.

■ [Source Host] = The host where the alertoriginated.

■ [Alert Classification] = The classificationof the alert. Set by the alert.

■ [AlertName] = The name of the alert. Setby the alert.

■ [Alert Date And Time] = The timestampwhen the alert was first created on thesource host.

Email Format

Select to send the email notification as dailydigest.

If you select this check box, SF Managercombines all your email alert notificationsinto one summary email and sends to youeveryday.

Send email as daily digest

SNMP Trap

Enter the IP Address or the name of the hostwhere the SNMP trap console is located.Visible only when SNMP Trap is selected.


Host

Displays the port number 162, the defaultport number for SNMP traps. You can editthe port number, if required.

Port


Table 3-10 Edit Rule - Setup notifications options (continued)

DescriptionField

Command Action

Enter the name of the host where thecommand script file is located. Maximumlength is 255 characters. The source hostname cannot contain spaces.


Source Host

Enter the path and name of the commandscript file. Maximum length is 255characters. Valid entries should contain thefull path and a valid file name. Visible onlywhen Command script is selected.

Example: /opt/scripts/script1.exe

Source File

Argument List

Enter the name of the host where thecommand script file is to be executed.Maximum length is 255 characters. Thedestination host name cannot containspaces. Use comma (,) to separate themultiple host name entries.


Destination host

Custom script

Browse the custom script file and upload it.

You can only upload the following types ofscripts:

■ perl (.pl)

■ shell (.sh)

■ batch (.bat)

Custom script


Edit Rule - Name optionsUse this panel to edit the name and description for an existing rule. Rules definethe automatic actions that are taken when specific alerts are generated, and theyare listed on the Rules tab.


64

For example, a rule can automatically run a script to restart an application whenit creates an alert that the application has stopped. This allows networkadministrators to automate routine tasks and focus their energies on more criticalissues.

Table 3-11 Edit Rule - Name

DescriptionField

Edit the name of the rule. Maximum field length is 255 characters.

Example: Restart stopped ABC program.

Rule Name

Edit the description for this rule. The description should include thepurpose of the rule. Maximum field length is 255 characters.

Example: When the ABC program generates a service stopped alert,run the restart program script and send an alert to the SNMP trapconsole.

Description

Clear to disable the rule. The default is enabled. An enabled rulemonitors alerts for the defined conditions.

Enable Rule


Copying alert rulesThe administrators can copy rules and specify their properties. This option ismore efficient than creating new rules.

To copy an alert rule

1 Click Monitor > Rules.

2 From the list of existing rules, select the rule that you want to copy, and doone of the following:

■ Click Actions > Copy Rule.

■ Right-click the desired rule and from the submenu, select Copy Rule.

3 In the Copy Rule wizard panel, specify the name of the new rule and clickOK.

See “Copy Rule options” on page 66.

4 In the Results panel, click OK.



65Managing alertsCopying alert rules




Copy Rule optionsUse this panel to create an identical copy of the selected rule with a distinct name.After you create a copy of the original rule, you can edit its properties to make itunique.

Table 3-12 Copy Rule

DescriptionField

Enter a name for the new rule.Name of New Rule


Enabling alert rulesYou can enable the alert rules that are in the disabled state.

You can perform this task from any of the following views:


■ Overview view of an alert rule

Depending on the status of the alert rule that you have selected, the Overviewpage of the alert rule displays the EnableRule option or the DisableRule option.This option is available in the Actions menu of the Overview page.

To enable a rule


2 From the list of existing rules, select the rule that you want to enable and doone of the following:

■ At the top of the Rules table, click Actions > Enable Rule.

■ Right-click the name of the rule, and select Enable Rule.

3 In the Enable Rule panel, click Yes.

4 In the Result panel, verify that the rule has been successfully enabled. ClickOK.


Managing alertsEnabling alert rules

66





Disabling alert rulesYou can disable the alert rules that are in the enabled state.

You can perform this task from any of the following views:


■ Overview view of an alert rule

Depending on the status of the alert rule that you have selected, the Overviewview of the alert rule displays the DisableRule option or the EnableRule option.This option is available in the Actions menu of the Overview page.

To disable a rule


2 From the list of existing rules, select the rule that you want to disable and doone of the following:

■ At the top of the Rules table, click Actions > Disable Rule.

■ Right-click the name of the rule, and select Disable Rule.

3 In the Disable Rule panel, click Yes.

4 In the Result panel, verify that the rule has been disabled successfully. ClickOK.






Deleting alert rulesYou can delete the alert rules that are no longer needed.

67Managing alertsDisabling alert rules

To delete an alert rule

1 Click Monitor > Rules.

2 From the list of existing rules, select the rule that you want to delete and doone of the following:

■ Click Actions > Delete Rule.

■ Right-click the desired rule and from the submenu, select Delete Rule.

3 In the Delete Rule wizard panel, click Yes.

See “Delete an Existing Rule options” on page 68.







Delete an Existing Rule optionsUse this panel to remove an existing rule. Deleted rules are no longer availablefor sending emails, generating SNMP traps, or executing command scripts inresponse to alerts.


Viewing alertsOperators monitor faulty status and performance information of the storagenetwork by reviewing alert notices. Veritas Operations Manager alerts helpoperators answer the following types of questions:

■ What are the conditions of hosts, initiators, disk groups, disks, or applicationsin the environment?



Alerts show warnings about events and conditions, such as VxFS file systemcapacity monitoring, file system status, VxFS file system storage checkpoint alerts,VVR alerts, enabled or disabled paths, alternate paths available or not available,

Managing alertsViewing alerts

68

enabled or disabled disks, system I/O alerts, Action Provider alerts, and VxVMprovider service alerts. These items show as alert classifications.

The following alert severities categorize the level of the error:

■ Critical

■ Error

■ Warning

■ Information

With the Veritas Operations Manager console, operators can quickly ascertainthe condition of all resources in the Veritas Operations Manager environment.The Alert Log displays alerts from all hosts that the central server manages.

Alert conditions can trigger actions such as sending emails to operators thatinform them about alert conditions, sending an SMTP trap, or running a batchfile on specific hosts.

Veritas Operations Manager retains Alert Logs for 30 days.

In the Alerts view, you can view the following information in a table:

■ The message which is a part of the alert. It includes the name of the agent thatidentified the alert condition and the name of the host on which the alertcondition occurred.

■ The classification of the alert, for example, volume alert, subdisk alert, andpath enabled.

■ The host on which the alert condition occurred.

■ The date and time when the alert was generated.

■ The details of the alerts.

You can view the detailed information about an alert by clicking on the icon inthe Details column. The AlertLogDetails panel displays the following informationabout an alert.

Table 3-13 Alert Log Details panel options

DescriptionField

Displays the alert level: Critical, Error,Warning, or Information.

Severity

Displays the alert name.Topic

Displays the date and time on which the alertwas generated.

Date

69Managing alertsViewing alerts

Table 3-13 Alert Log Details panel options (continued)

DescriptionField

Displays the message from the alert, usuallyincluding the name of the agent thatidentified the alert condition and the nameof the host on which the alert conditionoccurred.

Message

Displays the alert classification, for example,Volume alert, Subdisk alert, and pathenabled.

Class

Displays the host on which the alertcondition occurred.

Host

Displays the recommended action to resolvethe issue.

Recommended Action

Displays the details about the cause of thealert.

Details

You can add a note regarding the alert in the Alert Log Details panel by clickingAdd Note.

You can use the options on the left-side panel to do the following:

■ Search for alerts based on message, classification, and source host.

■ Filter the tasks based on their severity.

To view all alerts

◆ In the Veritas Operations Manager console, select Monitor > Alerts.

See “About alerts” on page 48.

About tasksA task represents any operation that can be performed by using Veritas OperationsManager. You can view the list of all tasks and the details about each of them inthe Tasks view. The list of all tasks lets you keep a track of all the operations thatare either in progress or that have completed for the various datacenter objects.

See “Viewing tasks” on page 71.

Managing alertsAbout tasks

70

Viewing tasksIn Veritas Operations Manager, you can view the list of tasks that are either inprogress or that have completed. You can also view the tasks that have failed.

You can view the following information about the tasks in a table:

■ The name of the task.

■ The state of the task: In Progress, Completed, or Failed.

■ The target object on which the task must be executed.

■ The system on which the task must be executed.

■ The user that executes the task.

■ The start time of the task.

■ The end time of the task.

■ The total number of tasks.

You can view the detailed information about a task by clicking on the icon in theDetails column. The Task Details panel displays the detailed information suchas the commands that are executed as part of the task and their results.

You can use the options on the left-side panel to do the following:

■ Search for tasks based on task name, state, target, source, and user.

■ Filter the tasks based on their current state.

To view the list of tasks

◆ In the Veritas Operations Manager console, select Monitor > Tasks.

See “About tasks” on page 70.

About messages posted on Activity BoardYou can post messages in the Activity Board panel on the Veritas OperationsManager Home view. These messages let you inform other users about anyadministrative or other important activities that are scheduled or that may havebeen performed.

See “Viewing the messages posted on the Activity Board” on page 72.

71Managing alertsViewing tasks

Viewing the messages posted on the Activity BoardIn Veritas Operations Manager, you can view all the messages that are posted onthe ActivityBoard panel in the Veritas Operations Manager Home view. You canview only the 10 most recent messages on the Veritas Operations Manager Homeview.

In the Activity Board view, you can view the following information in a table:

■ The date and time at which the message was sent.

■ The sender of the message.

■ The message that was sent.

You can use the Search option on the left-side panel to search for messages basedon the sender and the message.

To view all the messages posted on Activity Board

◆ In the Veritas Operations Manager console, do one of the following:

■ Select Monitor > Activities.

■ In the Activity Board panel on the Home view, click Show all.

See “About messages posted on Activity Board” on page 71.

Deleting a message that is posted on Activity BoardIn the Activity Board view of Veritas Operations Manager, you can remove themessages that are posted on the Activity Board panel.

To remove a message that is posted on Activity Board

1 In the Veritas Operations Manager console, select Monitor > Activities.

2 In the Activity Board view, in the All Activities table , select the checkboxto on the left-side of the message that you want to remove and do one of thefollowing:

■ At the top of the All Activities table, click Actions > Delete Message(s).

■ Right-click the message that you want to remove and from the submenu,select Delete Message(s).

3 In the Delete Message(s) panel, click Yes to remove the message.


See “Viewing the messages posted on the Activity Board” on page 72.

Managing alertsViewing the messages posted on the Activity Board

72

About setting alerts for replicationDuring replication,sometimes the secondary storage site lags behind the primarystorage site. This could be due to time delay, bandwidth issues, or failure at thesecondary storage site.

In Veritas Operations Manager, you can monitor any Replicated Volume Group(RVG) for replications that lag behind in terms of log usage (SRL usage) and interms of data size. You can define high and low threshold levels for raising analert.You can view the alert in the Monitor > Alerts view.

See “Setting the alerts for replication” on page 73.

Setting the alerts for replicationIn Veritas Operations Manager, you can specify low and high threshold valuesfor raising an alert, when a replication lags behind in terms of size or log usage.An alert is displayed if the data size or log usage reaches the specified thresholds.The severity of the alert differs in cases of low and high thresholds.

You can either specify low and high thresholds individually for each selectedreplication, or you can specify common threshold values for all the replications.

Note: To disable the replication alerts, set empty values for both low and highthresholds.

To set a replication alert

1 In the Veritas Operations Manager console, select Manage > Replications.

2 In the list of replications, select the replications for which you want to setlow or high thresholds.

3 Click Actions > Monotor RVG.

4 In the Monitor RVG(s) wizard panel, specify values for low and highthresholds.

See “Monitor RVG(s) panel options” on page 74.

5 Result panel displays a message about updating the threshold valuessuccessfully in the database. The page displays an error message if thethreshold values does not get updated in the database. In the result panel,click OK.

73Managing alertsAbout setting alerts for replication

Monitor RVG(s) panel optionsUse this wizard panel to specify low and high threshold values for raising an alertfor replications that are lagging.

Table 3-14 Monitor RVG(s) panel options

DescriptionField

To specify common threshold values for all theselected replications, select Apply to all. Selectingthis option disables the options to set thresholdvalues for individual replications.

Apply to all

Displays the name of the replicated volume group(RVG).

Name

Displays the name of the secondary storage site.Secondary

Specify the low threshold in terms of data size forraising an alert to indicate that the replication islagging.

Behind By (Size) Low Threshold

Specify the high threshold in terms of data size forraising an alert to indicate that the replication islagging.

Behind By (Size) High Threshold

Specify the low threshold in terms of log usagepercentage for raising an alert to indicate that thereplication is lagging.

Log Usage Low Threshold (%)

Specify the high threshold in terms of log usagepercentage for raising an alert to indicate that thereplication is lagging.

Log Usage High Threshold (%)

See “Setting the alerts for replication” on page 73.

Managing alertsSetting the alerts for replication

74

Deploying VeritasOperations Managersolutions


■ About Veritas Operations Manager solutions

■ About deploying Veritas Operations Manager solutions

■ Viewing solutions in the repository

■ Uploading a solution to repository

■ Uploading packages or add-ons to repository as a zip file

■ Installing a Veritas Operations Manager 5.0 solution

■ Upgrading add-ons

■ Uninstalling a Veritas Operations Manager solution

■ Removing a Veritas Operations Manager solution from repository

■ Viewing the solution deployment summary and the hosts to install solution

■ Installing solutions on specific managed hosts

■ Uninstalling solutions from specific managed hosts

■ Enabling the add-ons on specific managed hosts

■ Disabling the add-ons on specific managed hosts

■ Viewing the deployment requests for a solution

4Chapter

■ Canceling deployment request for a solution

■ Downloading the deployment log for a solution's deployment request

About Veritas Operations Manager solutionsVeritas Operations Manager solutions are independent and optional feature packsthat you can download and use to enhance the functionality of Veritas OperationsManager. These solutions are grouped into the following categories:

■ Add-on

■ Package

■ Patch

■ Hotfix

The solutions can be installed on Veritas Operations Manager Management Serverand the managed hosts. To deploy these solutions you must have domainadministrative privileges. The status information for the solutions is maintainedin the Management Server database.

See “About deploying add-ons” on page 77.

See “Downloading the deployment log for a solution's deployment request”on page 91.

See “About deploying packages or patches” on page 78.

See “Installing a Veritas Operations Manager 5.0 solution” on page 81.


About deploying Veritas Operations Managersolutions

This section provides you with the required information to deploy solutions(add-on, package, patch, and hotfix) for Veritas Operations Manager.

After uploading a solution to the repository, you can install the solution onManagement Server, managed host or on both (whichever is applicable). You caninstall a solution on the selected hosts, or you can select a platform (for exampleAIX), and install the solution on all the managed hosts that use the specificplatform. When you run the installation process, a deployment request is sent.You can view that deployment request in the Deployment Requests page. The

Deploying Veritas Operations Manager solutionsAbout Veritas Operations Manager solutions

76

following list provides an overview of various states of the solution that you seeon the User Interface of Veritas Operations Manager:

■ Upload: You need to upload the solution to the repository before you installit. Note that few solutions (add-ons) are pre-bundled with Veritas OperationsManager. For those add-ons, you can directly proceed with the installation.You can download other add-ons from Symantec support Web site. When asolution is uploaded, it is in the Not Installed state. To use the solution, youneed to install it on managed hosts, Management Server, or on both (whicheveris applicable for the solution).

■ Install: After you upload the solution, you need to install the solution beforeyou can start using it. Once the solution is installed, you can enable or disableit.

■ Enable: The solution must be in the installed state before you can enable it.

■ Disable: The solution must be in the installed state before you can disable it.

■ Uninstall: If the add-on is no longer used, you can uninstall it. After you haveuninstalled it, enable and disable options are not available. However, evenafter uninstalling the add-on, it is still present in the repository. If required,you can again install it. Note that you can uninstall the solution irrespectiveof its state (enabled or disabled).

■ Remove: You need to uninstall the solution (add-on or hotfix) before you canremove it. That is, the add-on must be in Not Installed state before you canremove it. You cannot remove the solutions, which are pre-bundled with VeritasOperations Manager.

See “About deploying add-ons” on page 77.

See “About deploying packages or patches” on page 78.

See “Uploading a solution to repository” on page 80.


About deploying add-onsThe add-ons need to be downloaded and deployed in Veritas Operations Manager.

For example, to administer a UNIX managed hosts from Management Server,download and deploy Storage Foundation Administration for Unix Add-on onManagement Server. To administer a Windows managed hosts from ManagementServer, download and deploy Storage Foundation Administration for WindowsAdd-on on Management Server. To enable template-based storage provisioningfrom Management Server, you must download and deploy Veritas StorageFoundation Add-on for Storage Provisioning on Management Server.

77Deploying Veritas Operations Manager solutionsAbout deploying Veritas Operations Manager solutions

The following Veritas Operations Manager add-on is deployed along with theManagement Server installation:

■ Veritas Operations Manager Add-on for Veritas Cluster Server Administration

■ Veritas Operations Manager Add-on for Storage Foundation Administration

For more information on the Veritas Operations Manager add-ons and theirsupported versions, refer to the Veritas Operations Manager Hardware andSoftware Compatibility List (HSCL).

Note:When you install the add-on in high availability and high availability-disasterrecovery (HA-DR) environment, you need to install the add-ons manually on allthe nodes of high availability and high availability-disaster recovery cluster beforeusing them for the configuration. Avoiding this step might result into configurationloss when the Management Server failovers to other nodes in the high availabilityand high availability-disaster recovery cluster.

See “About deploying Veritas Operations Manager solutions” on page 76.

About deploying packages or patchesYou can download and install packages or patches for Veritas Operations Managerfrom the Symantec Web site. Packages or patches for Veritas Operations Managerare available in tape archive (tar.gz) format, Storage Foundation archive (.sfa)format, or zip (.zip) format. To install the Veritas Operations Manager packagesor patches, you must upload the packages or patches to the repository ofManagement Server.


About deploying hotfixesYou can install hotfixes for Veritas Operations Manager. You can upload one ormore hotfixes to the repository, and then install them to Management Server andthe managed hosts.

Note: First, you need to install the hotfix on Management Server, and then, youcan install that hotfix on the managed hosts.


Deploying Veritas Operations Manager solutionsAbout deploying Veritas Operations Manager solutions

78

Viewing solutions in the repositoryThe Veritas Operations Manager solutions provide extended functionality to theusers. In the Deployment Management view, under the Repository tab, you canview the solutions that are already uploaded to the Veritas Operations Managerrepository. When a solution is uploaded, it is in the Not Installed state. To use thesolution, you need to install it on hosts, server, or both (whichever is applicablefor the solution). Once the solution is installed, you can enable or disable it.

The Repository tab in the DeploymentManagement view displays the followingdetails:

■ Solution: The name of the solution.

■ Type: The type of the solution - add-on, package, patch, or hotfix.

■ Scope: The scope of the solution. It displays whether the solution is installedon a managed host, server, or on both.

■ Version: The version of the installed solution.

■ Status: The status of the solution. For example, installed, not installed, orenabled. You can view the hosts where you have installed the solution. Forexample, enabled (4 of 10) notifies that out of 10 hosts, the particular solutionis installed on four hosts.

■ Platform: The supported platform for the solution. For example, HP-UX, Linux,Windows and so on.

■ Description: Additional information about the solution.

■ UserGenerated: Indicates whether the user has created the add-on. CurrentlyVeritas Operations Manager does not provide any option to the user to createnew add-on. Therefore the value of User Generated field is set to No.

Refine your search based on the following filters:

■ Scope: Select the scope of the solution that you want to search. For example,the solution that can be installed only on Management Server, only on themanaged host (MH), and on both. Select Prebundled check box to search allthe solutions that are pre-bundled with Veritas Operations Manager.

■ Type: Select the solution type that you want to search. For example, add-on,package, patch, or hotfix.

■ Platform: Select the platform. For example, to search the solutions that canbe installed only on AIX, you need to select AIX check box. Veritas OperationsManager displays all the solutions that can be installed on AIX platform(irrespective of their scope and type).

79Deploying Veritas Operations Manager solutionsViewing solutions in the repository

To view solutions in the repository

◆ In the Veritas Operations Manager console, select Settings > Deployment.In the Deployment Management view, under the Repository tab, you canview the available solutions.


See “Uninstalling a Veritas Operations Manager solution” on page 84.

See “Viewing the solution deployment summary and the hosts to install solution”on page 85.


Uploading a solution to repositoryAfter you have downloaded the solution for Veritas Operations Manager fromSymantec Web site, you need to upload it. After you upload the solution, you needto install it, and then you can start using it.

Note: You can upload all the packages or add-ons together as a zip file.

See “Uploading packages or add-ons to repository as a zip file” on page 81.

To upload a solution to repository

1 In the Veritas Operations Manager console, click Settings > Deployment.

2 In the Deployment Management view, under the Repository tab, do one ofthe following:

■ Click Actions > Upload.

■ Right-click in the table, and from the submenu select Upload.

3 In UploadtoRepository panel, click Browse and select the solution that youwant to upload.

4 Click Upload to upload the solution to the repository.

5 Click Close.


See “Removing a Veritas Operations Manager solution from repository” on page 85.

Deploying Veritas Operations Manager solutionsUploading a solution to repository

80

Uploading packages or add-ons to repository as a zipfile

You need to download following zip files for the packages or add-ons for VeritasOperations Manager from Symantec Web site:

■ Veritas_Operations_Manager_Addons_Bundle_5.0.0.zip for the add-ons.

■ Veritas_Operations_Manager_Managed_Host_Bundle_5.0.0.zip for thepackages.

To upload packages or add-ons to repository as a zip file


2 In the Deployment Management view, under the Repository tab, do one ofthe following:

■ Click Actions > Upload.

■ Right-click in the table, and from the submenu select Upload.

3 In Upload to Repository panel, click Browse and select the .zip file that youwant to upload.

4 Click Upload to upload the .zip file to the repository.

5 Click Close.



Installing a Veritas Operations Manager 5.0 solutionUse this page to view the instructions to select solution from the list of all solutionsthat are uploaded to the repository, and then install it on managed hosts orManagement Server. In the DeploymentManagement view, under Scope column,you can view which solution can be installed on managed host (MH Only),Management Server (CS Only), or on both (MH+CS).

Note: If the solution is a hotfix, first you need to install it on the ManagementServer/Central Server, and then on the managed hosts.

81Deploying Veritas Operations Manager solutionsUploading packages or add-ons to repository as a zip file

To install a solution

1 In the Veritas Operations Manager console, select Settings > Deployment.

2 In the Deployment Management view, under the Repository tab, select thesolution that you want to install, and then do one of the following:

■ Click Actions > Install.

■ Right-click the solution and then select Install.

3 You see options in the InstallSolution panel depending on whether you haveselected solution to install only on managed hosts or Management Server.

■ For Management Server: No selection is required from the user. Thesolution is installed directly on the Management Server. If the solution isalready installed on the Management Server, this operation overwritesthe earlier installation. You need to restart the Web server on theManagement Server after the successful installation of solution.

■ For managed hosts: Select the required option (Hosts or Platforms).

See “Install solution options” on page 82.

4 Click Install.

5 In the Result panel, click OK


See “Installing solutions on specific managed hosts” on page 87.

Install solution optionsThe solutions can be installed on:

■ Management Server

■ Managed hosts

■ Both

If you select to install a solution (applicable only for managed hosts), you seeHosts and Platforms options in the wizard panel. If you select to install a solution(applicable only for Management Server), these options are not available. In thatscenario, the application installs the solution on the Management Server, oroverwrites the solution if it is already installed.

Use this panel to install the uploaded solutions on managed hosts or ManagementServer. For managed hosts, you can either select the hosts explicitly, or you canselect the platform. When you select a specific platform, the solution is installedon all the managed hosts using that platform.

Deploying Veritas Operations Manager solutionsInstalling a Veritas Operations Manager 5.0 solution

82

Table 4-1 Install solution options for managed hosts

DescriptionField

Select to view the list all managed hostswhere the solution is not installed.

If you select the Show all applicable hosts(Overwrites existing installation) option,you can see all the managed hosts where youcan install the solution. It includes:

■ Managed hosts on which the solution innot installed currently.

■ Managed hosts where the solution isinstalled currently. In this scenario,Veritas Operations Manager overwritesthe existing solution installation.

Hosts

Select to install the solution on all managedhosts using the specific operating system.For example, if you select Windows in thelist, the application installs the solution onall the hosts that use Windows operatingsystem. This option is also useful to installthe solution whenever a new managed hostusing the specific operating system is addedto the Management Server.

Select Force Install (Overwrites existinginstallation) option to overwrite existingsolution installation on the managed hosts.

Platforms

Start the installation. After the installation,a deployment request is sent. The solutionis installed asynchronously. You can checkits status on the Deployment Summarypage.

Install


Upgrading add-onsYou can upgrade add-ons using the Veritas Operations Manager console. Beforeyou upgrade, you need to download the add-on package from the SORT Web siteor the Fileconnect Web site, and upload it to the repository. This will upload allthe add-ons to the repository. To upgrade selective add-ons, you need to unzip

83Deploying Veritas Operations Manager solutionsUpgrading add-ons

the add-ons bundle before uploading to the repository. You need not remove theexisting version of the add-on before the upgrade.

You need domain administrator privileges to upgrade an add-on.

To upgrade add-ons


2 In the Deployment Management view, on the Repository tab, select theadd-on, and click Actions > Install.

3 In the Install Solution panel, review the information and click Install.

4 In the Result panel, review the information and click Close.

5 Do one of the following:

■ For Storage Insight Add-on and VBS Availability Add-on, you are loggedout of Management Server. Log in to Management Server.

■ If the add-on requires a Web server restart, click WebServer RestartPending in the Status column of the Repository view .

If the Management Server is configured in high availability (HA) environment,the add-ons should be upgraded on both the nodes.

See “Uploading a solution to repository” on page 80.


Uninstalling a Veritas Operations Manager solutionYou can uninstall a solution from the Management Server and managed host. Youcan uninstall only add-on; package or patch cannot be uninstalled. After youuninstall an add-on, you cannot enable or disable it. If the uninstalled add-on isapplicable to the Management Server, you need to restart the Web server on theManagement Server after you uninstall the add-on successfully.

Note: You cannot uninstall pre-bundled add-ons.

To uninstall a solution


2 In the Deployment Management view, under the Repository tab, select theadd-on that you want to uninstall and do one of the following:

■ Click Actions > Uninstall.

Deploying Veritas Operations Manager solutionsUninstalling a Veritas Operations Manager solution

84

■ Right-click the add-on and then select Uninstall.

3 In the Uninstall solution from all hosts panel, click OK.

See “Enabling the add-ons on specific managed hosts” on page 88.

See “Disabling the add-ons on specific managed hosts” on page 88.


RemovingaVeritasOperationsManager solution fromrepository

You can remove Veritas Operations Manager solution from the solution repository.You need to uninstall the solution (add-on, hotfix, or distribution) before youremove it. That is, the solution must be in Not Installed state before you removeit. You cannot remove the solutions, which are pre-bundled with Veritas OperationsManager. You can remove one solution at a time.

Note: If the solution is a hotfix, first you need to remove it from all managed hosts,and then from Management Server.

To remove a solution from the repository


2 In the Deployment Management view, under the Repository tab, select thesolution that you want to remove and do one of the following:

■ Click Action > Remove from the shortcut menu.

■ Right-click on the solution and then select Remove.

3 In the Remove solution from repository panel, click OK.


See “Uninstalling solutions from specific managed hosts” on page 87.

Viewing the solution deployment summary and thehosts to install solution

Use this page to view the deployment summary of the solution and the hostswhere you can install the solution.

In the Deployment Summary view, you can review the following information:

85Deploying Veritas Operations Manager solutionsRemoving a Veritas Operations Manager solution from repository

■ Version: The version of the selected solution.

■ Type: The type of the solution. For example, package and add-on.

■ Description: Additional information about the solution.

The pie chart displays the number of hosts where the solution is in Installed,Enabled, Disabled, or Not Installed state. In the bar chart, you can view the hostdetails and their states along with the information on their operating systems.When you click a specific portion of these charts, the host details in Hosts tablechanges dynamically.

Select the appropriate option under the Hosts table to install, uninstall, enable,and disable solution for the selected host. For packages and patches, only Installoption is available. For hotfix, Install and Uninstall options are available. Foradd-ons, Install, Uninstall, Enable, and Disable options are available to you.

Review the following host properties in the Hosts table:

■ Name: Name of the managed host.

■ State: Current state of the managed host. For example, Faulted, At Risk, Healthyand so on.

■ Status: Solution status on the host. For example, Installed, Not Installed andso on.

■ Architecture: Managed host's architecture. For example, SPARC, x86, x86_64and so on.

■ Platform: Managed host's platform. For example, Windows, HP-UX, Solarisand so on.

■ Family: Managed host's operating system family. For example, Solaris, WindowsServer NT, Red Hat Enterprise Linux and so on.

■ OS Version: Version of the operating system.

■ MH Version: Version of the managed host.

To view the hosts to install solution


2 In the Deployment Management view, click the desired add-on or package.

3 In the Deployment Summary view, under Hosts tab, you can view the hostdetails.




Deploying Veritas Operations Manager solutionsViewing the solution deployment summary and the hosts to install solution

86


Installing solutions on specific managed hostsUse this option to install a solution on the selected managed hosts of VeritasOperations Manager. If the solution is already installed on the selected host, theapplication overwrites the existing installation, and reinstall the solution. It isreferred to as a force installation.

To install a solution on specific managed hosts


2 In the Deployment Management view, under the Repository tab, click thedesired solution that you want to install on the managed hosts.

3 In the Deployment Summary view, under the Hosts table, you can view allthe hosts where you can install the solution.

4 Select one or more hosts and click Actions > Install.

5 In the Install Solution panel click OK.



Uninstalling solutions from specific managed hostsUse this option to uninstall a solution from one or more selected managed hostsof Veritas Operations Manager. This option is available only for add-on and hotfix.You can uninstall the solution irrespective of its state (enabled or disabled).

To uninstall a solution from specific managed hosts


2 In the Deployment Management view, under the Repository tab, click thedesired solution that you want to uninstall from one or more managed hosts.

3 In the Deployment Summary view, under the Hosts table, select the host.

4 Click Actions > Uninstall.

5 In the Uninstall Solution panel click OK.



87Deploying Veritas Operations Manager solutionsInstalling solutions on specific managed hosts

Enabling the add-ons on specific managed hostsYou can use the enable solutions option to enable add-ons on one or more managedhosts. This option is available only for add-ons.

To enable an add-on on specific managed hosts


2 In the Deployment Management view, under the Repository tab, click thedesired add-on that you want to enable on one or more managed hosts.

3 In the Deployment Summary view, under the Hosts table, select the hostswhere you want to enable the selected add-on.

4 Click Actions > Enable.

5 In the Enable Solution wizard panel, click OK.


Disabling the add-ons on specific managed hostsYou can use the disable solutions option to disable add-ons on one or moremanaged hosts. This option is available only for add-ons.

To disable an add-on on specific managed hosts


2 In the Deployment Management view, under the Repository tab, click thedesired add-on that you want to disable on one or more managed hosts.

3 In the Deployment Summary view, under the Hosts table, select the hostson which you want to disable the selected add-on.

4 Click Actions > Disable.

5 In the Disable Solution wizard panel, click OK.


Viewing the deployment requests for a solutionThe Deployment Requests view lets you overview the details of deploymentrequests for a solution. You can view the following details:

■ Request Time: Time and date when the request for the solution deploymentwas raised.

Deploying Veritas Operations Manager solutionsEnabling the add-ons on specific managed hosts

88

■ Operation: The operation that was performed as a result of the request. Forexample, install and uninstall.

■ Type: Deployment Request Type. For example Deploy by host and Deploy byplatform.

■ Status: Status of the deployment operation. For example Active and Canceled.

■ Result: Result of the deployment. For example Finished, In-Progress and soon.

■ Hosts Succeeded: The number of hosts where the solution deployment wassuccessful.

■ Hosts Failed: The number of hosts where the solution deployment failed.

■ Hosts In Progress: The number of hosts where the solution deployment is inprogress.

■ Total Hosts: Total number of hosts.

Refine your search based on the following filters:

■ Status: The present status of solution deployment request. For example,whether the request is still active or it is canceled.

■ Result: The result of the deployment request. For example, whether it is inprogress or finished.

■ Deployment Type: The type of the deployment request. For example, by hostor by platform.

To view the deployment requests for a solution


2 In the Deployment Repository view, click the desired add-on or package.

3 In the Deployment Summary view, click the Requests tab. You can view allthe requests that are related to the selected add-on or package.


Viewing deployment request details for a solutionUse this page to view the details of deployment requests for a specific add-on inVeritas Operations Manager. It displays the hosts where the add-on is installedor scheduled to install. Along with it, you can view the add-on operation status.For example, install success, uninstall success, and install scheduled.

89Deploying Veritas Operations Manager solutionsViewing the deployment requests for a solution

To view the deployment request details


2 In the Deployment Management view, click the desired add-on or package.

3 In the Deployment Summary view, click the Requests tab.

4 In the Deployment Requests view, select the request, and under Resultcolumn, click its status - Finished or In Progress.


Canceling deployment request for a solutionAfter you start a solution deployment, if you want to cancel the request; you cando so using the Cancel Request option. However, you need to cancel thedeployment request when it is in Progress state. Veritas Operations Manager doesnot let you cancel the deployment request if the deployment request is completed.

Note: You cannot cancel a deployment request that is of Deploy By Host type.

To cancel the deployment request for a solution


2 In the Deployment Management view, under the Repository tab, click thedesired solution.


4 In Deployment Requests view, select the check box for the solutiondeployment request you want to cancel, and then do one of the following:

■ Click Actions > Cancel Request.

■ Right-click the desired deployment request and from the submenu selectCancel Request.The CancelDeploymentRequest wizard panel displays the status messageof the deployment operation.

5 In the Cancel Deployment Request wizard panel, click OK.


Deploying Veritas Operations Manager solutionsCanceling deployment request for a solution

90

Downloading the deployment log for a solution'sdeployment request

For a selected solution, you can download the deployment log for its deploymentrequests. The deployment log file is a compressed file (tar.gz). You must haveadministrative privileges to download the deployment log.

To download the deployment log for a solution's deployment request


2 In the Deployment Management view, under the Repository tab, click thedesired add-on or package.


4 In the Deployment Requests view, select the deployment request for whichyou want to download its log, and then do one of the following:

■ Click Actions > Download Deployment Log.

■ Right-click the desired deployment request and from the submenu selectDownload Deployment Log.

5 Save the compressed file.

See “Viewing solutions in the repository” on page 79.

91Deploying Veritas Operations Manager solutionsDownloading the deployment log for a solution's deployment request

Deploying Veritas Operations Manager solutionsDownloading the deployment log for a solution's deployment request

92

Managing databases


■ Performing the database discovery for secure databases

Performing the database discovery for securedatabases

Veritas Operations Manager discovers both the non-secure and the securedatabases. Veritas Operations Manager does not require any configurations todiscover the non-secure databases. For the secure databases, Veritas OperationsManager can discover the basic-level information without any authentication. Todiscover the secure databases using Veritas Operations Manager, you mustauthenticate the databases with the correct credentials. Veritas OperationsManager supports discovering the SQL, DB2, Sybase, and Oracle databases.

When you perform discovery of the Oracle databases, ensure that you have rightpermission to the following system tables:

DBA_TS_QUOTASALL_TAB_COMMENTSALL_ARGUMENTS

DBA_USERSALL_TRIGGERSALL_CATALOG

DBA_VIEWSALL_TRIGGER_COLSALL_COL_COMMENTS

DICTIONARYALL_TYPESALL_CONSTRAINTSALL_CONS_COLUMNS

DICT_COLUMNSALL_UPDATABLE_COLUMNSALL_DB_LINKSALL_ERRORS

GLOBAL_NAMEALL_USERSALL_INDEXES

NLS_DATABASE_PARAMETERSALL_VIEWSALL_IND_COLUMNS

5Chapter

NLS_INSTANCE_PARAMETERSDATABASE_COMPATIBLE_LEVELALL_LOBS

NLS_SESSION_PARAMETERSDBA_DB_LINKSALL_OBJECTS

PRODUCT_COMPONENT_VERSIONDBA_ERRORSALL_OBJECT_TABLES

ROLE_TAB_PRIVSDBA_OBJECTSALL_SEQUENCES

SESSION_PRIVSDBA_ROLESALL_SNAPSHOTS

SESSION_ROLESDBA_ROLE_PRIVSALL_SOURCE

SYSTEM_PRIVILEGE_MAPDBA_SOURCEALL_SYNONYMS

TABLE_PRIVILEGESDBA_TABLESPACESALL_TABLES

TABLE_PRIVILEGE_MAPDBA_TAB_PRIVSALL_TAB_COLUMNS

DBA_TRIGGERSALL_TAB_COL_STATISTICS

To perform database discovery for a secure database

1 Select Manage > Databases.

2 If Veritas Operations Manager discovers any secure database instances, thenyou can view the following text at the top of the database list:

ThereareNumberofsecuredatabasessecuredatabaseinstancesthatrequirecredentials to perform full discovery. Click here to provide credentials.

Click the link.

3 In the Select database instances panel, select the secure database that youwant to authenticate, and click Next.

See “Select database instances options” on page 95.

4 In the Provide Credentials panel, enter the required information, and clickNext.

See “Provide credentials options” on page 95.

5 In the Database Instance Credentials Summary panel, review theauthentication information. Click Next.

See “Database Instance Credentials Summary” on page 95.

6 In the Result panel, verify that the database instances have been authenticatedsuccessfully.

See “Overview of host discovery” on page 104.

Managing databasesPerforming the database discovery for secure databases

94

Select database instances optionsUse this wizard panel to specify the secure databases that you want to authenticate.

Select the check boxes to choose the database instances that you want toauthenticate.

Note:You can choose multiple database instances if the credentials for the databaseinstances are the same.

See “Performing the database discovery for secure databases” on page 93.

Provide credentials optionsUse this wizard panel to specify the credentials to authenticate the database.

Note:These two options are available only for the SQL Server database instances.For discovering the database instances other than the SQL Server, VeritasOperations Manager uses only the domain authentication method, which promptsyou to enter the user name and password for the domain.

Table 5-1 Provide credentials panel options

DescriptionField

Choose this option to authenticate thedatabase using the domain or SQL servercredentials.

Enter the user name and the password forthe SQL server or the domain.

Domain/SQL Authentication

Choose this option to authenticate thedatabase using the administrator credentialsfor the operating system.

Operating System Authentication


Database Instance Credentials SummaryUse this wizard panel to verify the authentication and the credential details.


95Managing databasesPerforming the database discovery for secure databases

Managing databasesPerforming the database discovery for secure databases

96

Managing clusters


■ Viewing the fire drill schedules

■ Modifying a fire drill schedule

Viewing the fire drill schedulesIn Veritas Operations Manager, you can view the schedules that you have createdfor the high availability and the disaster recovery fire drills. This page also containsthe list of fire drill schedules that failed.

Using the fire drill page, you can edit, enable, disable, or delete a fire drill schedule.

This page displays the following information for a fire drill schedule:

The name of the fire drill scheduleName

The description for the fire drill that youentered when you configured it

Description

The schedule of the fire drill runRecurrence

The date when the fire drill was startedStart Date

The current status of the fire drill. Indicateswhether the fire drill is enabled, disabled, orinvalid.

Status

The category of the fire drill. Indicateswhether the schedule is for a highavailability fire drill or a disaster recoveryfire drill.

Category

6Chapter

Click the icon to view further details of thefire drill.

Details

The fire drill schedules page displays the following information for a failed firedrill:

The name of the fire drill scheduleSchedule Name

The category of the fire drill. Indicateswhether the schedule is for a highavailability fire drill or a disaster recoveryfire drill.

Schedule Category

The name of the fire drill schedule alongwith the user name of the user who createdthe schedule.

User

The date and time when the fire drill wasstarted

Start Time

The date and time when the fire drill wasfinished

End Time

Click on the icon to view the details of thefailed fire drill schedule

Details

To view the fire drill schedules and details

1 In the Veritas Operations Manager console, select Policies > Fire Drills.

2 Click Schedules.

See “Modifying a fire drill schedule” on page 98.

Modifying a fire drill scheduleUsing Veritas Operations Manager, you can edit the schedules that you havecreated for running a high availability (HA) or a disaster recovery (DR) fire drill.You can identify the HA and the DR fire drills from the Category column in thispage.

To modify a fire drill schedule

1 In the Veritas Operations Manager console, select Policies > Fire Drills.

2 Click Schedules.

3 In the schedules list, select the required fire drill schedule. Click Actions >Edit.

Managing clustersModifying a fire drill schedule

98

4 In the SelectServiceGroup(s) wizard panel, verify the selection of the servicegroups for which you want to run the fire drill are selected. Click Next.

See “Select Service Group(s) panel options” on page 99.

5 In the Schedule wizard panel, modify the schedule to run the fire drill. ClickNext.

See “Schedule panel options” on page 100.

6 In the Summary panel, verify the selections that you have made. Click Finish.

See “Summary panel options” on page 101.

7 In the Result panel, verify that the fire drill has been modified successfully.

See “Viewing the fire drill schedules” on page 97.

Select Service Group(s) panel optionsUse this wizard panel to select the service groups for which you want to run thehigh availability (HA) fire drill.

The selection of service groups in this page varies according to various types ofselections:

■ If you have selected the service groups from a list of service groups, this pagedisplays only the service groups that you have chosen previously

■ If you have selected a specific cluster to perform HA fire drill, this page displaysall the service groups that are online on the selected cluster

■ If you have selected a specific business entity for performing the HA fire drilloperation, this page displays all the base service groups that are online in thebusiness entity and also the service groups that are online on the base clustersof the business entity

Enter a keyword, such as a few letters of the name of the service group, in theFilter field to filter the selection on the table. You can filter the list by the name,state, type, or the cluster.

This page displays the following information on the service groups:

Table 6-1 Select Service Group(s) panel options

DescriptionField

Displays the name of the service group.Name

Displays the current state of the servicegroup.

State

99Managing clustersModifying a fire drill schedule

Table 6-1 Select Service Group(s) panel options (continued)

DescriptionField

Displays the type of the service group.Type

Displays the cluster to which the servicegroup is associated.

Cluster


Schedule panel optionsUse this wizard panel to specify the schedule for running the fire drill on theselected service groups in the cluster.

Table 6-2 Schedule panel options

DescriptionField

Enter a name for the schedule for runningthe fire drill.

Schedule Name

Enter the schedule description for runningthe fire drill.

Schedule Description

Select a frequency for running the fire drill.The values under the When column changeswith the options that you choose here.

The available options are daily, weekly, andmonthly. Select NoSchedule not to schedulethe fire drill. If you choose this option thefire drill runs immediately after you set itup.

Frequency


100

Table 6-2 Schedule panel options (continued)

DescriptionField

Specify exactly when you want to run thefire drill as follows:

■ For daily schedule: Select the time fromthe Time filed.

■ For weekly schedule: Select the Everyweekday option to run the fire drill everyweek days from Monday to Friday in aweek. If you want to run the fire drill onspecific days of the week, select the dayfrom the Recur every week on field.Select the time from the Time field.

■ For monthly schedule: To run the firedrill on a specific day of the month, enterthe date in the Day field. To run the firedrill on the recurring days of a month,choose the required options from thedrop-down list. Select the time from theTime field.

When


Summary panel optionsUse this wizard panel to verify your selection for running the fire drill on theselected service groups.

If you have scheduled the fire drill, you can select the RunFireDrill immediatelycheck box to run the fire drill immediately after setting it up. If you have notscheduled the fire drill, this check box is not displayed on the console, and thefire drill is run immediately.


101Managing clustersModifying a fire drill schedule


102

Managing hosts


■ Overview of host discovery

■ Overview of agentless discovery

■ About managing the hosts from Management Server

■ Viewing the details of the managed hosts associated with Management Server

■ Adding the managed hosts to Management Server using the Web console

■ Adding managed hosts to Management Server using the Auto Configure(gendeploy.pl) script

■ Refreshing the details of the managed host

■ Editing the details of an agentless host

■ Removing the managed hosts from the Management Server domain

■ About monitoring usage and configuring the automatic growth for file systems

■ Setting the threshold for monitoring file system usage

■ Configuring the automatic growth of the file systems

■ Reclaiming thin storage for file systems

■ Reclaiming thin storage for disks

■ Compressing files in Veritas Operations Manager

■ About using Veritas Operations Manager to manage the hosts with SymantecApplicationHA

■ Enabling application heartbeat for a service group

7Chapter

■ Disabling application heartbeat for a service group

Overview of host discoveryFor an overview of host discovery, refer to the following topics:

■ See “How Veritas Operations Manager discovers hosts” on page 104.

■ See “Supported features for host discovery options” on page 106.

How Veritas Operations Manager discovers hostsVeritas Operations Manager provides several ways to discover the hosts and theirassociations to storage resources and network devices. To discover the hosts andtheir connections to storage resources, you can either install an agent or useagentless capabilities.

Agent and agentless capabilities include the following:

An agent is a software package that runs on ahost. It discovers the storage resources thatare associated with a host and relays theinformation to Management Server.

Discovery of the hosts using an agent, forthe hosts that have Veritas OperationsManager and Storage Foundation installedon them

Agent-based discovery is also used for thenon-Storage Foundation hosts that haveVeritas Operations Manager installed on them.

Discovery of the non-Storage Foundationhosts using an agent, for the hosts thathave Veritas Operations Manager installedon them

Veritas Operations Manager can discover ahost by remotely accessing the host and thenrunning the scripts that collect data.

The agentless discovery scripts access the hostusing SSH (for UNIX hosts) or WMI (forWindows hosts).

Veritas Operations Manager identifies thistype of the host as an agentless host.

Discovery of the non-Storage Foundationhosts using agentless discovery scripts, forthe hosts that do not have VeritasOperations Manager installed on them

Note:Agentless discovery is not supported on the hosts that have Veritas StorageFoundation or Veritas Operations Manager installed.

The following categories of host discovery are Veritas Operations ManagerAdvanced features:

■ Agentless host discovery

Managing hostsOverview of host discovery

104

■ Agent-based host discovery for the non-Storage Foundation hosts that haveVeritas Operations Manager installed on them

You can temporarily use Veritas Operations Manager Advanced features undera demo license of Veritas Operations Manager Advanced. To obtain a permanentlicense, you need to accept the End User's License Agreement (EULA) for VeritasOperations Manager Advanced.

Through each of these host discovery options, Management Server is the centralpoint to which all of the discovered data flows. The following figure depicts theflow of data with each of the host discovery options.

Figure 7-1 How Veritas Operations Manager components work together todiscover hosts

Agentlesshosts

Agentlesshosts

Agentlesshosts

Agenthosts

ControlHost

ControlHost

Storagearrays

ManagementServer

See “Supported features for host discovery options” on page 106.


105Managing hostsOverview of host discovery

Supported features for host discovery optionsVeritas Operations Manager provides several ways to discover hosts and theirassociations to storage resources and network devices.

See “How Veritas Operations Manager discovers hosts” on page 104.

Table 7-1 identifies the use cases that each host discovery option provides.

Table 7-1 Use cases for discovery options at the host level

Agent HostAgentless hostUse caseCategory

XX*

* Does not includeVeritas StorageFoundation diskgroups, volumes,file systems,clusters, anddatabases.Includes onlyVMware serversand virtualmachines

Inventory report for variousresources at License and productusage reporting

host, enclosure, and cluster level

Inventoryandenvironmentreporting

X

XStorage allocation at host levelStorageutilization

XX*

*Does not includeVeritas StorageFoundation FileSystems

File system usage

XXResource mapping from disks onhosts to LUNs in an enclosure

XXThin pool usage

XXEnclosure storage allocation tohosts

XCluster activity and trendsClusteranalysis

Managing hostsOverview of host discovery

106

Table 7-1 Use cases for discovery options at the host level (continued)

Agent HostAgentless hostUse caseCategory

XX*

*Does not includeVeritas StorageFoundation FileSystems

Reporting underutilized filesystems

Storagereclamation

XXLUNs connected to multiple hosts

XUnderutilized LUNs under VeritasStorage Foundation

XLUNs that are not part of a diskgroup

Veritas Operations Manager includes the ability to discover virtualization servers(VMware ESX servers). You can choose from different discovery options to discovervirtualization servers. For VMware ESX servers, Management Server and ControlHost can perform remote discovery by using VMware Infrastructure (VI SDK). Todiscover ESX servers, the Control Host Add-on must be installed.

Note: Agentless discovery of non-global zones, LDOMs, and VMWare ESX serversis not supported. Agentless discovery of any virtual machines other than VMWareguests is not supported. Agentless discovery of a non-globlal zone or LDOM virtualmachine will result in the discovery of a physical host without any storagecorrelation. Agentless discovery of global zones is supported, however resourcesallocated from global to non-global zones on the hosts will not be discovered.

Veritas Operations Manager has the ability to discover VMware guest operatingsystems. The information that Veritas Operations Manager discovers depends onthe discovery option that you choose. To discover information from VMwareenvironments, you must configure the ESX server or VirtualCenter discovery, andalso configure the guests using agent or agentless discovery.

If you discover the VMware guests using agentless discovery, any RDM disksvisible on the guest will not be correlated to array LUNs. Similar to non-RDMdisks visible to the guest, the RDM disks will be correlated to the storage exportedby the corresponding ESX server. You can view this correlation in the StorageMapping tab when you go to Manage > Hosts view. If you configure VMwareguests using an agent then you can see the correlation of RDM disks visible to theguest with corresponding array LUNs.

107Managing hostsOverview of host discovery

Note:For configuring Linux VMware guests using agentless discovery, the versionof the /usr/sbin/dmidecode utility must be 2.7 or higher.

The following tables identify the objects that Veritas Operations Manager candiscover and report on with each host discovery option.

Table 7-2 compares the storage resources that Veritas Operations Manager candiscover with each host discovery option.

Table 7-2 Discovery of storage resources by host discovery option

Agent HostAgentless hostDiscovery area

XXHost

XX*

* Does not supportiSCSCI initiatorsdiscovery

HBA

XXStorage allocation and connectivity

XX*

* Does not supportVeritas DMP. Doesnot support iSCSILUN correlation toenclosures

LUNs and multipathing

XX*

* Does not supportVeritas StorageFoundationVolume Managerand File Systems

Volume managers and file systems

XDatabases

XClusters

Overview of agentless discoveryFor an overview of agentless discovery, refer to the following topics:

■ See “About agentless discovery using the Control Host” on page 109.

Managing hostsOverview of agentless discovery

108

■ See “About agentless discovery of remote hosts” on page 109.

■ See “How agentless discovery of a UNIX host works” on page 110.

■ See “How agentless discovery of a Windows host works” on page 111.

■ See “Prerequisites for agentless configuration” on page 110.

■ See “Requirements for agentless discovery of UNIX hosts” on page 112.

■ See “Requirements for agentless discovery of Windows hosts” on page 114.

■ See “Requirements for deep array discovery for agentless hosts” on page 115.

■ See “Commands that require root access for agentless discovery of UNIX hosts”on page 116.

■ See “Using the privilege control software with agentless discovery of UNIXhosts” on page 118.

■ See “SSH configuration requirements for agentless discovery” on page 119.

■ See “About installing OpenSSH on a UNIX host” on page 121.

About agentless discovery using the Control HostVeritas Operations Manager uses Control Hosts as a discovery mechanism. AControl Host can be used to perform agentless discovery of a remote host. Toperform agentless discovery, you must install the Control Host Add-on on one ofthe managed hosts. You can install the Control Host Add-on on ManagementServer, however it is not recommended as it puts extra load on ManagementServer.

Platform support for a host that can act as a Control Host is the same as that ofManagement Server.

Note: A UNIX Control Host can only discover UNIX agentless hosts using SSH. AWindows Control Host can discover Windows agentless hosts using WMI or UNIXagentless hosts using SSH. Ensure that you install one or more Control Hosts onthe appropriate platform depending on the operating system of the remote hostsyou want to discover agentlessly.

See “About Control Hosts in Veritas Operations Manager” on page 157.

About agentless discovery of remote hostsAgentless discovery lets you discover hosts without installing an agent on thehost. The discovery provides end-to-end visibility from the file system to the

109Managing hostsOverview of agentless discovery

spindle. Because an agent is not required, agentless discovery eliminates agentdeployment and maintenance and minimizes CPU and memory consumption.

To perform agentless discovery, Veritas Operations Manager remotely accessesthe host and runs discovery scripts that collect data from a host.

See “How agentless discovery of a UNIX host works” on page 110.

See “How agentless discovery of a Windows host works” on page 111.

Prerequisites for agentless configurationThe following list provides prerequisites required for agentless configuration:

■ You must install the Control Host Add-on on one or more managed hosts and/orManagement Server.Veritas Operations Manager lets you discover a host through the Control Host.The Control Host helps you manage discovery data from agentless hosts andcan discover HBAs, andles on the host, multipathing, Linux LVM, and filesystems (including ZFS). Agentless discovery does not support the discoveryof databases and applications.

■ A UNIX Control Host cannot be used to agentlessly discover Windows hosts.If you plan to agentlessly discover Windows hosts, you will need to plan yourControl Host deployment accordingly.

■ You must install Veritas Operations Manager Storage Insight Add-on for DeepArray Discovery and Mapping and configure arrays for deep discovery.Veritas Operations Manager Storage Insight Add-on for Deep Array Discoveryand Mapping must be deployed to enable correlation of OSHandles on theagentless hosts to array LUNs.If you make any configuration changes, for example creating new LUNs andmaking them visible to the host, on storage arrays, then the agentless discoverythat occurs after a subsequent SI deep array discovery will reflect the changeson the agentless hosts. After making changes to the array, one SI deep discoveryneeds to occur and only then a subsequent agentless discovery will pick upthe changes on the host.

See “About agentless discovery using the Control Host” on page 109.

How agentless discovery of a UNIX host worksTo perform agentless discovery of a remote UNIX host, Veritas Operations Managerdoes the following:

■ Uses Secure Shell (SSH) to send the discovery script to the remote host.

■ Runs the discovery script on the remote host.


110

■ Saves the output of the script to a data file on the remote host in the /var/tmpdirectory.

■ Uses SSH to get the oputput on to the Control Host.

■ Deletes the files from the remote host that it used for discovery.

To perform this discovery process, Veritas Operations Manager requires a non-rootuser account for the remote host. Privileged access is required to discover someinformation.

See “Requirements for agentless discovery of UNIX hosts” on page 112.

Figure 7-2 depicts how Veritas Operations Manager performs agentless discoveryof UNIX hosts.

Figure 7-2 Agentless discovery of UNIX hosts

UNIX hosts

ControlHost

(Optional)

UNIX hosts

SSH SSH

ManagementServer

How agentless discovery of a Windows host worksTo perform agentless discovery of a remote Windows host, Veritas OperationsManager runs a script that executes data-gathering commands. The script usesWindows Management Instrumentation (WMI), a Windows managementtechnology that is used to work with remote hosts. The WMI calls use Microsoft’sDistributed Component Object Model (DCOM) to obtain the data from the host.Veritas Operations Manager creates a private local user account (vomuser) onManagement Server or a Control Host to facilitate its use of DCOM. To


communicate between Veritas Operations Manager Control Host and the remotehost, WMI uses port 135.

Veritas Operations Manager uses WMI in two ways:

■ First, WMI contacts a service that runs on the remote host and invokes theservice to perform the actions that collect data about the host. As it collectsdata, WMI sends the data back to the Control Host.

■ Second, WMI invokes command line tools such as nslookup and fcinfo. Theoutput from the command line tools saves to a data file on the remote host inthe %systemroot%\temp directory. Veritas Operations Manager copies the filefrom the host’s mapped admin$ filestore, sends it to Veritas OperationsManager Control Host, and deletes the file from the remote host.

To perform this discovery process, Veritas Operations Manager requires a localadministrator account for the remote host.

Veritas Operations Manager cannot perform agentless discovery of a Windowshost from a Solaris Control Host.

Figure 7-3 depicts how Veritas Operations Manager performs agentless discoveryof Windows hosts.

Figure 7-3 Agentless discovery of Windows hosts

WindowsControlHost

Windows hosts

WMI

Windows orSolaris

ManagementServer

Requirements for agentless discovery of UNIX hostsTable 7-3 lists the requirements for agentless discovery of UNIX hosts.


112

Table 7-3 Requirements for agentless discovery of UNIX hosts

DescriptionRequirement

■ The minimum requirement is a non-root user account.

■ Symantec requires privileged access to discover someinformation. You can use privilege control software todesignate privileged access to a specific user for specificcommands.

See “Commands that require root access for agentlessdiscovery of UNIX hosts” on page 116.

See “Using the privilege control software with agentlessdiscovery of UNIX hosts” on page 118.

A user account

Ensure there is network access between the host that youwant to discover and Veritas Operations Manager ControlHost that performs discovery.

UNIX agentless discovery requires contacting SSH runningon TCP port 22 on the remote host. TCP port 22 should beopen in both directions between the Control Host and theremote host.

Network access betweenhosts

Enable persistent binding if you want Veritas OperationsManager to discover the storage that is allocated to a Solaris9 host.

Persistent binding for Solaris9 hosts

Veritas Operations Manager requires a shell on the remotehost (sh, ksh, or bash) that accepts sh file redirection.

A shell on the remote host


Table 7-3 Requirements for agentless discovery of UNIX hosts (continued)


To communicate between the Veritas Operations Managerhost and remote UNIX hosts, Veritas Operations Manageruses the non-keyboard interactive, password-basedauthentication of SSH.

Ensure that:

■ SSH is isntalled.

The SSH package is typically installed by default;however, it may not be present if a minimal operatingsystem installation was performed. If the SSH packageis not present, use the operating system installer toinstall SSH, or download and install OpenSSH.

See “About installing OpenSSH on a UNIX host”on page 121.

■ SSH is set up properly.

See “SSH configuration requirements for agentlessdiscovery” on page 119.

■ SunSSH is version 1.1 (Sun_SSH_1.1) or higher on Solaris9 hosts. If a Solaris 9 host runs version 1.0(Sun_SSH_1_0), network communication between VeritasOperations Manager and the Solaris 9 host mayterminate during agentless configuration and discovery.

■ OpenSSH is not version 0.9.8e or 0.9.7e on AIX, Linux,and Solaris hosts. These versions have known AESencryption issues, which can cause a warning.

Secure Shell (SSH) on theremote host


Requirements for agentless discovery of Windows hostsTable 7-4 lists the requirements for agentless discovery of Windows hosts

Table 7-4 Requirements for agentless discovery of Windows hosts


Veritas Operations Manager requires a local administratoraccount for the remote host.

A user account

Ensure there is network access between the host that youwant to discover and Veritas Operations Manager ControlHost that performs discovery.

Network access betweenhosts


114

Table 7-4 Requirements for agentless discovery of Windows hosts (continued)


WMI is installed as part of the Windows operating system.Ensure that the WMI service is enabled on the VeritasOperations Manager host that performs discovery and onthe remote host that you want to discover.

Windows ManagementInstrumentation (WMI)

Open TCP port 135 on the remote host that you want todiscover and the host that performs discovery (ControlHost). WMI uses port 135 to communicate between the hosts.

Port 135 opened

Veritas Operations Manager cannot perform agentlessdiscovery of a Windows host from a Solaris ManagementServer or Control Host. Initiate discovery from a WindowsControl Host if you want to discover a Windows host anddo not have a Windows Management Server.

A Windows ManagementServer or Control Host

Disable User Account Control on Veritas OperationsManager Control Host that initiates agentless discovery, ifthe host runs Windows 2008.

For information about how to turn off UAC, see the sectiontitled "Turning off UAC" at the following URL:

http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx

User Account Control (UAC)turned off on a Windows2008 host

Install Microsoft’s Fibre Channel Information Tool (fcinfo)on Windows 2003 hosts that you want to discover. This toolis required only if you want Veritas Operations Manager todiscover information about the host’s Fibre Channel (FC)hardware (HBAs and Fibre Channel LUNs). For example, thetool is not necessary if you want to discover a VMwareWindows guest operating system. FC discovery is notpossible for VMware guest operating systems.

You can download the tool from the following location:

www.microsoft.com/downloads/details.aspx?FamilyID=73d7b879-55b2-4629-8734-b0698096d3b1&displaylang=en

Microsoft’s Fibre ChannelInformation Tool installedon Windows 2003 hosts

See “How agentless discovery of a Windows host works” on page 111.

Requirements for deep array discovery for agentless hostsThe following list provides requirements for deep array discovery for agentlesshosts:


http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx

www.microsoft.com/downloads/details.aspx?FamilyID=�73d7b879-55b2-4629-8734-b0698096d3b1&displaylang=en

www.microsoft.com/downloads/details.aspx?FamilyID=�73d7b879-55b2-4629-8734-b0698096d3b1&displaylang=en

■ You must have the Veritas Operations Manager Storage Insight Add-on forDeep Array Discovery and Mapping deployed to correlate OSHandles on theagentless host with array LUNs.

■ After making masking changes to make new LUNs visible to a host, you mustwait for the next scheduled Storage Insight deep array discovery and theneither perform a manual refresh or wait for the next scheduled discovery ofthe agentless host.For VMWare environments, when you make new LUNs visible to the ESXserver, you must wait for the next scheduled Storage Insight deep arraydiscovery, either perform a manual refresh or wait for the next scheduleddiscovery of the agentless host, and then either perform a manual refresh orwait for the next scheduled discovery of VCenter.

These requirements apply to both UNIX and Windows agentless hosts.

Commands that require root access for agentless discovery of UNIXhosts

Veritas Operations Manager requires a user account to perform agentless discoveryof a remote UNIX host. The minimum requirement is a non-root user account.However, there are a few cases where Veritas Operations Manager requires a rootuser account.

Table 7-5 identifies the commands that require root access.

Table 7-5 Commands that require root access for agentless discovery

Requirement¹PurposeCommandOperatingsystem

Resource

Mandatory(for VMwareguests only)

Provides VMWare BIOS UUID for the virtualmachine.

/usr/sbin/dmidecodeLinux(VMWareGuest OS)

VMWareBIOS UUID

MandatoryProvides device handles for disks./usr/sbin/diskinfoHP-UXDisks


116

Table 7-5 Commands that require root access for agentless discovery(continued)

Requirement¹PurposeCommandOperatingsystem

Resource

MandatoryProvides license-related information.AIX:/usr/sbin/powermtcheck_registration

HP-UX:/sbin/powermtcheck_registration

Linux:/sbin/powermtcheck_registration

Solaris:/etc/powermtcheck_registration

AIX, HP-UX,Linux andSolaris

EMCPowerPath

MandatoryProvides the paths and their status details.Linux:/usr/sbin/powermtdisplay dev=all

HP-UX:/sbin/powermtdisplay dev=all

Linux:/sbin/powermtdisplay dev=all

Linux: /etc/powermtdisplay dev=all

OptionalProvides the Fibre Channel-related detailsregarding HBA, HBA port WWNs, etc.

fcinfoSolarisHBAs ortarget ports

Mandatory/opt/fcms/bin/fcmsutil

HP-UX

MandatoryProvides volume-related details for all volumes.vgdisplay -v --unitsb

LinuxLinux LVM

MandatoryProvides volume-related details for all volumes.lvdisplay -m --unitsb

¹ Mandatory indicates that the specified part of feature discovery fails if you donot provide root access for the command. Optional indicates that most of thefeature discovery works even if you do not provide root access for the command.


The mandatory commands for a given OS platform need to be enabled in theprivilege control software that you are using, even if the host does not have theutilities installed. For example, you must put powermt in the sudoers file whenusing sudo even if EMC PowerPath is not installed on the host.


Using the privilege control software with agentless discovery of UNIXhosts

Veritas Operations Manager requires a user account to perform agentless discoveryof a remote UNIX host. The minimum requirement is a non-root user account.However, there are a few instances where Veritas Operations Manager requiresa root user account.

See “Commands that require root access for agentless discovery of UNIX hosts”on page 116.

To discover that information, you can configure Veritas Operations Manager touse one of the following:

■ A root user account.

■ A non-root user account and use privilege control software to grant that userthe ability to run specific commands.

Veritas Operations Manager supports the following privilege control softwarewith agentless discovery:

■ PowerBroker

■ Privilege Manager for UNIX

■ Sudo

Table 7-6 identifies how you can use privilege control software with agentlessdiscovery.

Table 7-6 Using privilege control software with agentless discovery of UNIXhosts

ActionStep

Install the privilege control software on the remote hostthat you want to discover.

1


118

Table 7-6 Using privilege control software with agentless discovery of UNIXhosts (continued)

ActionStep

Modify the configuration file for the privilege controlsoftware as follows:

■ Add the user name that you want to use for agentlessdiscovery.

■ Add the commands that you want to allow the user torun.

See “Commands that require root access for agentlessdiscovery of UNIX hosts” on page 116.

■ Ensure that the software does not require a TTYsession for commands to succeed.

■ Ensure that the software does not require a passwordwhen running a command.

■ Ensure that the user has the privilege to kill thecommands that are initiated with the privilege controlsoftware. Symantec recommends this privilege becauseit gives the non-root user the ability to kill anycommands that hang when run through the privilegecontrol software.

2

Configure agentless discovery of hosts.

See “Adding the managed hosts to Management Serverusing the Web console” on page 127.

3

See “Requirements for agentless discovery of UNIX hosts” on page 112.


SSH configuration requirements for agentless discoveryVeritas Operations Manager uses SSH to perform agentless discovery of UNIXhosts. The configuration file sshd_config defines SSH configuration. The file islocated in /etc/ssh or in /opt/etc/ssh.

Table 7-7 lists the requirements for SSH and the associated parameters that aredefined in sshd_config.


Table 7-7 Requirements for SSH

CommentsParameter(s)Requirement

The port must be set to 22.Agentless configuration does notsupport the specification of theSSH port.

PortThe SSH port isopen for the useraccount that youuse for discovery

To allow password-basedauthentication, set the parameterto yes.

PasswordAuthenticationSSH allowspassword-basedauthentication

Root user logon is required only ifyou use a root account fordiscovery. To allow logons by theroot user, set thePermitRootLogin parameter toyes.

PermitRootLoginSSH allows accessfor the root user

By default, SSH does not restrictuser logons. However, you mayhave setup SSH to restrict access.If you use parameters to restrictaccess, ensure that they do notblock access by the user accountthat you use for discovery.

■ AllowUsers

If you use this parameter,ensure that it allows the useraccount that you use foragentless discovery.

■ DenyUsers

If you use this parameter,ensure that it does not denythe user account that you usefor agentless discovery.

■ AllowGroups

If you use this parameter,ensure that it allows the groupto which the user accountbelongs.

■ DenyGroups

If you use this parameter,ensure that it does not denythe group to which the useraccount belongs.

SSH allows accessfor the useraccount that youuse for discovery

For more information about sshd_config, refer to your system documentation.


See “About agentless discovery of remote hosts” on page 109.


120

About installing OpenSSH on a UNIX hostThe SSH package may not be present on a UNIX host. If SSH is not present, youcan either use the operating system installer to install SSH, or you can downloadand install OpenSSH. OpenSSH is a free, open-source version of SSH.

See “Installing OpenSSH on AIX” on page 121.

See “Installing OpenSSH on Linux” on page 121.

See “Installing OpenSSH on Solaris” on page 122.

Installing OpenSSH on AIXAIX includes OpenSSH. You may also download OpenSSH.

To install OpenSSH on AIX

1 For AIX 5.2 or earlier, download OpenSSL from the AIX Toolbox page on theIBM Web site:

https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx&S_PKG=dlaixww&S_TACT=&S_CMP=

For AIX 5.3 or later, download the OpenSSL install package from the AIX WebDownload Pack Programs page on the IBM Web site:

https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=aixbp

2 Install OpenSSL.

3 Download OpenSSH from the following location:

http://sourceforge.net/projects/openssh-aix/files

4 Install OpenSSH.

See “About installing OpenSSH on a UNIX host” on page 121.

Installing OpenSSH on LinuxMost Linux distributions include OpenSSH. You may also download OpenSSH. OnLinux, the following OpenSSH packages are required:

■ openssl-0.9.8b-8.3.e15.i386.rpm

■ openssh-4.3p2-16.e15.i386.rpm

■ openssh-server-4.3p2-16.e15.i386.rpm




https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=aixbp

http://sourceforge.net/projects/openssh-aix/files

To install OpenSSH on Linux

1 For Red Hat, download the OpenSSH packages from the following location:

http://www.redhat.com

For other Linux distributions, download the OpenSSH packages from thefollowing location:

http://rpm.pbone.net

2 Run the following command to install the OpenSSH packages:

# rpm -ivh openssh-4.3p2-16.e15.i386.rpm

openssh-server-4.3p2-16.e15.i386.rpm


Installing OpenSSH on SolarisOn Solaris 10, SSH is installed by default. There is no need to install SSH manually.

On Solaris 9, the easiest way to install OpenSSH is to download and install theprecompiled packages from Sunfreeware.com. The following OpenSSH packagesare required:

■ GNU Compiler

■ Zlib

■ OpenSSL

■ OpenSSH

To install OpenSSH on Solaris 9

1 Download the OpenSSH packages from the following locations.

■ GNU Compilerftp://ftp.sunfreeware.com/pub/freeware/sparc/9/libgcc-3.4.6-sol9-sparc-local.gz

■ Zlibftp://ftp.sunfreeware.com/pub/freeware/sparc/9/zlib-1.2.3-sol9-sparc-local.gz

■ OpenSSLftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssl-0.9.8l-sol9-sparc-local.gz

■ OpenSSH


122

http://www.redhat.com

http://rpm.pbone.net

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/libgcc-3.4.6-sol9-sparc-local.gz

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/zlib-1.2.3-sol9-sparc-local.gz

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssl-0.9.8l-sol9-sparc-local.gz

ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssh-5.3p1-sol9-sparc-local.gz

2 Unzip the packages and install the files using the following commands:

For the GNU Compiler:

# gunzip libgcc-3.4.6-sol9-sparc-local.gz

# pkgadd -d libgcc-3.4.6-sol9-sparc-local

For Zlib:

# gunzip zlib-1.2.3-sol9-sparc-local.gz

# pkgadd -d zlib-1.2.3-sol9-sparc-local

For OpenSSL:

# gunzip openssl-0.9.81-sol9-sparc-local.gz

# pkgadd -d openssl-0.9.81-sol9-sparc-local

For OpenSSH:

# gunzip openssh-5.3p1-sol9-sparc-local.gz

# pkgadd -d openssh-5.3p1-sol9-sparc-local

3 Set up the /var/empty directory by running the following commands:

# mkdir /var/empty

# chown root:sys /var/empty

# chmod 775 /var/empty

4 Add the user sshd by running the following command:

# useradd -g sshd -c 'sshd Privsep' -d /var/empty -s /bin/false

sshd

5 Edit the default /user/local/sshd_config file.

Replace these lines:

Subsystem sftp /user/libexec/sftp-server

PermitRootLogin no

with:

Subsytem sftp /user/local/libexec/sftp-server

PermitRootLogin yes


ftp://ftp.sunfreeware.com/pub/freeware/sparc/9/openssh-5.3p1-sol9-sparc-local.gz

6 Generate keys for the server by running the following commands:

# ssh-keygen -t rsa1 -f /usr/local/etc/ssh_host_key -N ""

# ssh-keygen -t dsa -f /usr/local/etc/ssh_host_dsa_key -N ""

# ssh-keygen -t rsa -f /usr/local/etc/ssh_host_rsa_key -N ""

7 Start SSHD by running the following command:

# nohup /usr/local/sbin/sshd &


About managing the hosts fromManagement ServerThe current version of Veritas Operations Manager lets you manage hosts fromManagement Server. To perform the management tasks on the hosts, you musthave the Admin role.

The following table lists the differences between the current and the previousversions of Veritas Operations Manager:

Table 7-8 Managing hosts—Differences between the current and the previousversions of Veritas Operations Manager

Previous Veritas Operations Managerversions

Current Veritas Operations Managerversion

The DNS server must be able to resolve thehost names of both Management Server andthe managed host.

The DNS server must be able to resolve thehost name of Management Server, but notthe managed host.

You must log in to each managed host toperform the management tasks.

You must log in to Management Server toperform the management tasks on the hosts.Make sure that you can ping the managedhost from Management Server.

You can use the current release of Veritas Operations Manager to perform thefollowing host management tasks:

■ List the details of all managed hosts, including their statuses.

■ Add a new managed host to Management Server.

■ Refresh the information about managed hosts.

■ Edit agentless host information.

■ Remove managed hosts from Management Server.

Managing hostsAbout managing the hosts from Management Server

124

See “Refreshing the details of the managed host” on page 132.

See “Removing the managed hosts from the Management Server domain”on page 135.

Viewing the details of the managed hosts associatedwith Management Server

In the Settings>Host view, under HostManagement, you can view the managedhosts that Management Server currently manages. A table displays the followinginformation for each managed host:

Name or IP address of the managed host.Host Name

The state of the managed host. Host Statecan be one of the following:

■ Healthy – Management Server candiscover the managed host and theinformation that the host contains.

■ At Risk – The managed host containsfaulted objects or it uses the demo licenseof Storage Foundation products.

A host can also be in the At Risk statebecause of any of the following reasons:

■ External faults

■ VCS conditions

■ VVR conditions

■ Degraded DMP state

■ Faulted – The managed host does notreport to Management Server. Either themanaged host is no longer associatedwith Management Server or ManagementServer cannot reach the host.

Host State

The latest date and time when managed hostpinged Management Server

This value is not displayed for agentlesshosts.

Last Ping Time

The platform of the managed host.Platform

The version of the operating system of themanaged host.

OS Version

125Managing hostsViewing the details of the managed hosts associated with Management Server

The Veritas Operations Manager version onthe managed host.

This value is set as N/A for agentless hosts.

MH Version

The name of the Control Host discoveringthe agentless host.

Control Host

The configuration type of the of the managedhost.

Configuration Type

State of hosts being configured or the lasttime the discovery data was reported forconfigured hosts. The discovery state can beone of the following:

■ Probing

■ Discovering

■ Discovery Failed

Discovery State/Time

Using this page, you can perform the following tasks on the hosts:

■ Add the hosts

■ Refresh the hosts

■ Remove the hosts

■ Edit the agentless hosts

■ Set the auto configuration for the hosts

To filter the managed hosts based on their names, you can use the free text filterat the top of the table.

To filter the list of managed hosts

1 In the Veritas Operations Manager console, select Settings > Host.

2 Under Host Management, in the filter field, do one of the following:

■ Enter text to filter the list of managed hosts. You can filter the list basedon any column in the table except the Last Ping Time. As you type in thefilter box, the list of managed host is filtered to only show the hosts thatmatch your text.

■ Paste text you want to use to filter the list of managed hosts and clickFilter host. This filters the list of managed hosts to only show the hoststhat match your text.

Managing hostsViewing the details of the managed hosts associated with Management Server

126

To view the details of managed hosts


2 Under Host Management, view the table that lists managed hosts and theirdetails.

To view the details of a managed host, click on its name in the table.

See “Adding the managed hosts to Management Server using the Web console”on page 127.

See “Adding managed hosts to Management Server using the Auto Configure(gendeploy.pl) script” on page 130.

Adding the managed hosts to Management Serverusing the Web console

You can add a new managed host to Management Server using agent or agentlessdiscovery.

To add a new managed host to Management Server, you can use the Add Host(s)option under Settings > Host of Veritas Operations Manager console.

Note:Veritas Operations Manager does not support adding a managed agent hostto Management Server if the version of the managed agent host is later than theversion of Management Server. However, Veritas Operations Manager does notdisplay any error messages when you perform this task.

You can add multiple hosts to Management Server. After you click Submit, youcan view the operations that are finished, and the operations that are in progresson the subsequent page of the Add Host(s) wizard.

You can view the details of the new-added host in the Managed Hosts table.

Before you add a managed agent host to the Management Server, make sure thatthe managed agent host can communicate with the Management Server.

To add a managed host to the Management Server using an agent


2 In the host view, click Actions > Add Host(s).

3 In the Add Host(s) wizard panel, select the Agent option to add the host(s)to the Management Server.

127Managing hostsAdding the managed hosts to Management Server using the Web console

4 Enter the host details and click Next >.

See “Add host options” on page 128.

5 In the Results panel, verify that the host has been added successfully. ClickOK.

To add an agentless managed host to the Management Server


2 In the host view, click Actions > Add Host(s).

3 In the AddHost(s) wizard panel, select the Agentless option to add the host(s)to the Management Server.

4 Select the Discovery Mode to display available UNIX or Windows ControlHosts. Select the Control Host through which you will discover the agentlesshost(s).

The discovery mode should be SSH for adding UNIX agentless hosts and WMIfor adding Windows agentless hosts. You cannot add both UNIX and Windowshosts at the same time. If you want to add multiple hosts, you must add theUNIX hosts and the Windows hosts separately.

5 Enter the host details and click Next >.

See “Add host options” on page 128.

6 In the Results panel, verify that the host has been added successfully. ClickOK.

You can convert an agentless host to an agent host using the AddHost(s) wizard.To convert the agentless host, you must install theVeritas Operations Manageragent on the host and add the host using the Agent option in the Add Host(s)wizard. You do not need to remove the host.

The Advanced option lets you use privilege control software with the agentlessdiscovery of a host. You must specify the type and location of the software on theremote host. The Advanced option is optional and is required when addingagentless host discovery for non-root users.

Add host optionsUse this wizard panel to specify options to add a managed host to ManagementServer.

Selecting the agent or agentless configuration option will display different optionsfor adding the managed host.

You can also use this wizard panel to add multiple hosts at once by importing theinformation from a comma-separated (.csv) file from a specified location. The

Managing hostsAdding the managed hosts to Management Server using the Web console

128

CSV file must include the “.csv” extension. You can use the manual hostspecification and the CSV file simultaneously to add hosts.

The following is an example of a CSV file that includes user names and passwordsfor each host:

Host,User,Password

host1,user1,password1


The first line in the CSV file must appear as above. You can replace the subsequentlines with your hosts, user names, and passwords.

For agentless configuration, the CSV file cannot contain both UNIX and Windowshosts.

Note: The discovery mode (SSH or WMI) must be consistent with the types ofhosts you specify in the CSV file. You must specify SSH for UNIX hosts and WMIfor Windows hosts.

Table 7-9 Add host wizard panel options for agent configuration

OptionsField

Lets you manually specify more than onehost to add.

Add entries

Displays all discovered virtual machinesfound using VCenter configuration. If agentsare present on the virtual machines , you canselect and populate the entries.

Add VMs

Enter host name or IP address that you canuse to reach the managed host fromManagement Server.

Host

Enter user name with administrator rights.User name

Enter password to log on to the managedhost.

Password

129Managing hostsAdding the managed hosts to Management Server using the Web console

Table 7-10 Add host wizard panel options for agentless configuration

OptionsField

Lets you filter the Control Host field bydiscovery mode.

SSH should be used for adding UNIX host(s)and WMI should be used for adding Windowshost(s).

Discovery Mode

Control Host through which the agentlesshost(s) is being discovered.

Windows agentless hosts can only bediscovered by Windows Control Hosts.

Control Host

Lets you manually specify more than onehost to add.

Add entries

Enter host name or IP address that you canuse to reach the managed host fromManagement Server.

Host

Enter user name with administrator rights.User name

Enter password to log on to the managedhost.

Password

Lets you specify type and location ofprivilege control software to use on theagentless host(s).

Advanced


Adding managed hosts to Management Server usingthe Auto Configure (gendeploy.pl) script

You can add an agent host to the Management Server domain with minimal userinteraction. The Auto Configure ( gendeploy.pl) script available on ManagementServer can be used to create a script that is run on the host to add the host to thedomain. You can create the script either at the command prompt, or in the VeritasOperations Manager Management Server console.

Managing hostsAdding managed hosts to Management Server using the Auto Configure (gendeploy.pl) script

130

Note: You can only add an agent host using the Auto Configure (gendeploy.pl)script. This feature is not applicable for adding agentless hosts.

You need to copy the script that is created using gendeploy.pl to all the hoststhat you want to add to the domain. After you copy the script, you have to run iton each host. A host on which you run the script must have the VRTSsfmh packageinstalled on it.

Note: Adding many hosts to Management Server at the same time using the AutoConfigure (gendeploy.pl) script can affect the performance of ManagementServer. It is recommended that you add no more than 50 agent hosts at a time.

For information on installing Veritas Operations Manager host management, seethe Veritas Operations Manager Management Server Installation Guide.

To add an agent host toManagement Server using theAutoConfigure (gendeploy.pl)script

1 Create the script to add an agent host using either the command prompt, orthe console. Do one of the following:

■ Log on to the Veritas Operations Manager console as an Admin user. SelectSettings > Host. In the Host Management view, click Auto Configurebutton. In the Auto Configure dialog, click Download. In the FileDownload dialog, click Save to save the script to the required location.

■ Create the script using command prompt.

■ On UNIX Management Server, log on as root.Run the following command:/opt/VRTSsfmh/bin/gendeploy.pl --out filename [--domain

sfm:domainname:port]

where, filename is the name of the script that you specify. Thedomainname is the Management Server host name.

For example,/opt/VRTSsfmh/bin/gendeploy.pl --out test.pl --domain

sfm://Managementserver.domain.com:5634

In this example, the domain name is the Management Server name,or the domain hosted by Management Server.

■ On Windows Management Server, log on as a user with theadministrator privileges.To change the directory, run the following command at the commandprompt:

131Managing hostsAdding managed hosts to Management Server using the Auto Configure (gendeploy.pl) script

cd "C:\Program Files\Veritas\VRTSsfmh\bin"

To create the script to add an agent host, run the following command:perl.exe gendeploy.pl --out <filename> [--domain

<sfm:domainname:port>]

where, filename is the name of the script that you specify. The domainname is the Management Server host name.

For example,perl.exe gendeploy.pl --out test.pl[--domain

sfm://Managementserver.domain.com:5634]

In this example, the domain name is the Management Server name,or the domain hosted by the Management Server.

2 Copy the script to the agent host.

3 On the agent host, change the directory to the location where you copied thescript.


■ On UNIX-based hosts, run the following command to make the scriptexecutable:chmod +x filename

where, filename is the name of the script.

Run the script:./filename

■ On Windows-based hosts, run the following command:"C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe" filename

where, filename is the name of the script.

For the above script, the optional hostname parameter is the host as seenby the Management Server. The host is discovered by this name or IPaddress in Veritas Operations Manager.

5 In the console, verify that the agent host has been added to the ManagementServer domain.


Refreshing the details of the managed hostTo refresh the discovery of the agent families on both managed agent and agentlesshosts, you can use the Refresh Host(s) option.

You can also perform this task in the Hosts view in Manage > Hosts view.

Managing hostsRefreshing the details of the managed host

132

Note: You can perform the Refresh Hosts task on one or more managed hosts ata time.

To refresh the details of a managed host

1 In the Veritas Operations Manager console, do one of the following:

■ Select Settings > Host.

■ Select Manage > Hosts.

2 In the Host Management view, do one of the following:

■ Select the check box for the managed host, and click Actions > RefreshHost(s).

■ Right-click on the managed host to display the shortcut menu, and clickRefresh Host(s).

3 In the wizard panel to confirm the refresh operation, click OK.

The refresh operation for agentless hosts is asynchronous. The wizard displaysthat the operation has triggered the refresh, but the discovery operation for theagentless host is actually in progress in the background. You must wait for theactual discovery to complete. When it is complete, you can view the status reflectedin the Host State or Discovery State/Time columns in the Host Managementtable. You can also view the status in the State column in the Hosts table.

See “About managing the hosts from Management Server” on page 124.

Editing the details of an agentless hostTo edit the details of an agentless host, you can use the Edit Agentless Host(s)option.

To edit the details of an agentless host

1 In the Veritas Operations Manager console, click Settings > Host.


■ Select the check box for an agentless host and on top of the HostManagement table, click Actions > Edit Agentless Host(s).

■ Right-click on the agentless host to display the shortcut menu, and clickEdit Agentless Host(s).

133Managing hostsEditing the details of an agentless host

3 In the Edit Agentless Host(s) wizard panel, edit the host details and clickNext >.

See “Edit agentless host options” on page 134.

4 In the Results panel, verify that the host has been modified successfully.Click OK.

The Advanced option lets you use privilege control software with the agentlessdiscovery of a host. You must specify the type and location of the software. TheAdvanced option is optional and is required when configuring agentless hostdiscovery for non-root users.

The edit operation for agentless hosts is asynchronous. The wizard displays thatthe operation has triggered the edit, but the discovery operation for the agentlesshost is actually in progress in the background. You must wait for the actualdiscovery to complete. When it is complete, you can view the status reflected inthe HostState or DiscoveryState/Time columns in the HostManagement table.

See “Using the privilege control software with agentless discovery of UNIX hosts”on page 118.


Edit agentless host optionsUse this wizard panel to edit options for configured agentless hosts.

You can also use this wizard panel to edit options for multiple agentless hosts atonce by importing the information from a comma-separated (.csv) file from aspecified location. The CSV file must include the “.csv” extension.

The following is an example of a CSV file that includes user names and passwordsfor each host:

Host,User,Password



The first line in the CSV file must appear as above. You can replace the subsequentlines with your hosts, user names, and passwords.

For agentless configuration, the CSV file cannot contain both UNIX and Windowshosts.

Managing hostsEditing the details of an agentless host

134

Table 7-11 Edit agentless host wizard panel options for agentless configuration

OptionsField

Host name or IP address that you can use toreach the managed host from ManagementServer.

Host

User name with administrator rights.User name

Password to log on to the managed host.Password

Lets you specify type and location ofprivilege control software to use on theagentless host(s).

Advanced

See “Editing the details of an agentless host” on page 133.


Removing the managed hosts from the ManagementServer domain

If you want to dissociate the managed hosts from Management Server and removethe managed hosts from the database, you can use the Remove Host(s) option.

To remove the managed hosts from the Management Server domain

1 In the Veritas Operations Manager console, click Settings > Host.


■ Select the check box for the managed host and click Actions > RemoveHost(s).

■ Right-click on the managed host to display the shortcut menu, and clickRemove Hosts(s).

3 In the wizard panel to confirm the remove operation, click OK.


135Managing hostsRemoving the managed hosts from the Management Server domain

About monitoring usage and configuring theautomatic growth for file systems

In Veritas Operations Manager, the capacity and the usage of file systems are veryimportant because it directly affects the performance of the applications that usethese file systems. Therefore, the administrators need to constantly monitor theusage of the file systems in their environment and prevent any faults that mayhappen to it.

Note:Monitoring the usage and configuring the automatic growth for file systemsis not applicable for file systems on agentless hosts.

Veritas Operations Manager provides you options to set thresholds for monitoringthe file system usage and plan preventive measures to avoid file system failures.The system notifies you with adequate alerts if the current usage exceeds thresholdlevels. This feature also provides the capability to increase the size of the filesystem at a predefined stage. These options include the following:

■ Setting up threshold values for triggering alerts when the file system usagecrosses a specific limit

■ Specifying the amount of space that you want to increase on the file systemswhen the file system usage crosses a specified limit.

In Veritas, you can configure two types of thresholds to trigger alerts based onthe file system usage. The High Usage Warning, which is the low threshold, triggersrisk alert when the file system usage crosses the limit that you have specified. Itlets you identify and address the space issues early. The High Usage Risk threshold,which is highest threshold, triggers the fault alert that needs the urgent attentionfrom administrators.

The optimal performance of the file systems in your environment is directlyrelated to the amount of free space in them. You can configure the file system togrow automatically by a specified value when the usage of the file system crosseshigh threshold, that is the High Usage Risk. When you choose this option, VeritasOperations Manager increases the size of the file system if enough space isavailable on the volume. If the volume does not have enough space for increasingthe size of the file system, Veritas Operations Manager increases the size of thevolume, which automatically increases the size of the file system in an equivalentproportion. Veritas Operations Manager uses a system rule which executes thecanned script for increasing the size of the file system. This rule is executed whenManagement Server receives the fault alert that is triggered when the file systemcrosses the High Usage Risk threshold. You cannot edit or delete this system rule.

Managing hostsAbout monitoring usage and configuring the automatic growth for file systems

136

In a clustered file system environment where the file system has been mountedon multiple servers, the master node triggers the fault alert and resizes the filesystem when the file system crosses the High Usage Risk threshold.

Before doing this operation, you must ensure that you have enough space on thedisk or the disk group to increase the size of the volume. If the disk or the diskgroup does not have enough space to increase the size of the volume, the systemrule which executes the canned script for increasing the file system size fails andraises an alert.

The automatic growth operation is supported only for the VxFS File Systems,which are mounted on the VxVM volumes that are not configured under VeritasVolume Replicator. Also, the automatic growth operation is not supported for theVxFS File Systems that are mounted on the VxVM volume sets.

Note: For a fault, Veritas Operations Manager triggers the alert only once. If thefile system usage is greater than the High Usage Risk threshold value after asuccessful automatic growth operation, you must reset the High Usage Riskthreshold value to let Veritas Operations Manager trigger fault alerts when thefile system crosses the High Usage Risk threshold at a later time. VeritasOperations Manager does not trigger further fault alerts until a fault is addressedby resetting the High Usage Risk threshold value.

See “Setting the threshold for monitoring file system usage” on page 137.

See “Configuring the automatic growth of the file systems” on page 140.

Setting the threshold formonitoring file systemusageIn Veritas Operations Manager, you can monitor the usage of the file systems inyour environment. To monitor the file system usage, you can set the High UsageWarning and the High Usage Risk thresholds. The High Usage Warning thresholdtriggers risk alert when the file system usage crosses the limit that you havespecified. The High Usage Risk triggers the fault alert that needs your urgentattention. You can view these alerts in the Alerts page of Veritas OperationsManager.

To perform this operation, you must have the administrator or the operatorprivilege on the parent host of the file system.

In Veritas Operations Manager, you can do this operation from any locationswhere you can find a file system.

137Managing hostsSetting the threshold for monitoring file system usage

To set the threshold for monitoring file system usage

1 In the Veritas Operations Manager console, click Manage > Hosts.

2 In the page that lists the hosts, click on the required host.

3 In the Host details page, click File Systems.

4 Select the required file systems, and select Actions > Monitor Capacity.■

■ Right-click on the required file system and select Monitor Capacity.

5 In the Monitor Capacity wizard panel, enter the information in the HighUsage Warn (%) and in the High Usage Risk (%) fields. Click Next.

See “Monitor Capacity panel options” on page 138.

6 In the MonitorCapacitySummary wizard panel, review the information thatyou have entered. Click Finish.

See “Monitor Capacity Summary panel options” on page 139.

7 In the Result page, verify that you have successfully configured the thresholdvalues for monitoring the file system usage.

See “About monitoring usage and configuring the automatic growth for filesystems” on page 136.

Monitor Capacity panel optionsUsing this wizard panel, you can do the following operations:

■ Setting the threshold values for monitoring the file system usage

■ Specifying the amount of space that you want to increase on the file system

Table 7-12 Monitor Capacity panel options

DescriptionField

Select this check box to apply the thresholdand autogrow values to all the file systemsin the list. If you select this option, the fieldsthreshold and autogrow fields under thischeck box are activated.

Apply to all systems

The location where the file system ismounted

Mount Point

The host where the file system residesHost

The type of the file systemType

Managing hostsSetting the threshold for monitoring file system usage

138

Table 7-12 Monitor Capacity panel options (continued)

DescriptionField

The total size of the file systemSize

The amount of the used space on the filesystem in percentage

% Used

Specify the size of the file system to triggera risk alert on Management Server

High Usage Warn (%)

Specify the size of the file system to triggera fault alert on Management Server

High Usage Risk (%)

Specify the amount of space that you wantto increase on the file system when the filesystem crosses the high usage risk threshold

Autogrow (%)



Monitor Capacity Summary panel optionsUse this wizard panel to verify the information that you have entered for settingthe threshold for monitoring your file systems, and for increasing the file systemsize.

Table 7-13 Monitor Capacity Summary panel options

DescriptionField

The location where the file system ismounted

Mount Point

The host where the file system residesHost

The total size of the file systemSize

The size of the file system at which you wantVeritas Operations Manager to trigger a riskalert

High Usage Warn (%)

The size of the file system at which you wantVeritas Operations Manager to trigger a faultalert

High Usage Risk (%)

139Managing hostsSetting the threshold for monitoring file system usage

Table 7-13 Monitor Capacity Summary panel options (continued)

DescriptionField

The amount of space that you want toincrease on the file system when the filesystem usage crosses the high usage riskthreshold

Autogrow (%)

The estimated size of the file system afterthe automatic growth is completed

Estimated approximate autogrow size



Configuring the automatic growth of the file systemsYou can use the file system usage monitoring functionality in Veritas OperationsManager to increase the size of the file systems when they cross the High UsageRisk threshold. When you choose this option, Veritas Operations Managerincreases the size of the file system if enough space is available on the volume. Ifthe volume does not have enough space for increasing the size of the file system,Veritas Operations Manager increases the size of the volume, which automaticallyincreases the size of the file system in an equivalent proportion.

To perform this operation, you must have the administrator privilege on theparent host of the file system.

In Veritas Operations Manager, you can do this operation from any locationswhere you can find a file system.

To configure the automatic growth of the file systems


2 In the page that lists the hosts, click on the required host.

3 In the Host details page, click File Systems.

4 Select the required file systems and select Actions > Monitor Capacity.■

■ Right-click on the required file system and select Monitor Capacity.

5 In the Monitor Capacity wizard panel, enter the information in the HighUsage Risk (%) and the Auto Grow (%) fields. Click Next.

See “Monitor Capacity panel options” on page 138.

Managing hostsConfiguring the automatic growth of the file systems

140

6 In the MonitorCapacitySummary wizard panel, review the information thatyou have entered. Click Finish.

See “Monitor Capacity Summary panel options” on page 139.

7 In the Result page, verify that you have successfully configured the thresholdand the automatic growth for monitoring the file system.

See “About monitoring usage and configuring the automatic growth for filesystems” on page 136.

Reclaiming thin storage for file systemsYou can use Veritas Operations Manager to reclaim storage on thin LUNs. Youcan reclaim the difference between the allocated size of the thin LUN and theactual file system size on that LUN.

Thin reclamation is CPU and I/O intensive and can affect performance. You canuse the Top hosts for thin reclamation report to identify file systems and hoststhat would most benefit.

Thin reclamation is available for file systems and hosts that meet the followingrequirements:

■ VxFS file system

■ SF version 6.0 or later

■ Layout version 9 or later

■ Managed host version 5.0 or later

To reclaim thin storage


2 Click on the required host.

3 In the Host details page, click the File Systems tab.

4 In the table do one of the following:

■ Select the required mount points and select Actions > Reclaim ThinStorage.

■ Right-click the required mount point and select Reclaim Thin Storage.

5 Confirm proceeding with the operation.

See “Reclaiming thin storage for disks” on page 142.

141Managing hostsReclaiming thin storage for file systems

Reclaiming thin storage for disksYou can use Veritas Operations Manager to reclaim storage on thin disks. Youcan reclaim the difference between the allocated size of the thin LUN thatrepresents the disk and the actual file system size on the disk. The ThinReclaimable Size column on the Disks view table shows the maximum spaceavailable for thin reclamation.

Thin reclamation is CPU and I/O intensive and can affect performance.

Thin reclamation is available for disks and hosts that meet the followingrequirements:

■ SF version 6.0 or later

■ Managed host version 5.0 or later

To reclaim thin storage


2 Click on the required host.

3 In the Host details page, click the Disks tab.

4 In the table do one of the following:

■ Select the required disks and select Actions > Reclaim Thin Storage.

■ Right-click the required disk and select Reclaim Thin Storage.

5 Confirm proceeding with the operation.

You can check the results on the Thin Reclaimable Size column.

See “Reclaiming thin storage for file systems” on page 141.

Compressing files in Veritas Operations ManagerVeritas Operations Manager lets you compress files by directory on a managedhost 5.0 or later.

See the following topics:

See “About file compression in Veritas Operations Manager” on page 143.

See “Setting up compression schedules” on page 144.

See “Adding compression directories” on page 146.

See “Removing compression directories” on page 147.

See “Starting or stopping compression on demand” on page 148.

Managing hostsReclaiming thin storage for disks

142

See “Uncompressing directories on demand” on page 149.

About file compression in Veritas Operations ManagerIn Veritas Operations Manager, you set up file compression on a host at the filesystem (mount point) level by selecting directories for compression. You cancompress directories on demand, and you can set up a schedule for running thecompression process on the host. You can view a report of space saved by filecompression.

To compress files requires Veritas File System (VxFS) file systems with StorageFoundation 6.0 or later and disk layout version 9 or later. The managed host mustbe 5.0 or later. Veritas Operations Manager does not support file compression onWindows file systems.

Following are details on how file compression works:

■ Only user data is compressible, not VxFS metadata.

■ Compression is a property of a file, not a directory. If you compress all files ina directory, for example, any files that you later copy into that directory donot automatically get compressed as a result of being copied into the directory.

■ A compressed file is a file with compressed extents. Writes to the compressedfile cause the affected extents to get uncompressed; the result can be files withboth compressed and uncompressed extents.

■ After a file is compressed, the inode number does not change, and filedescriptors that are opened before the compression are still valid after thecompression.

File compression can have the following interactions with applications:

■ In general, applications notice no difference between compressed anduncompressed files, although reads and writes to compressed extents areslower than reads and writes to uncompressed extents. When an applicationreads a compressed file, the file system does not perform its usual readaheadto avoid the CPU load that this can require. However, when reading from theprimary fileset, the file system uncompresses an entire compression block(default 1 MB) and leaves these pages in the page cache. Thus, sequential readsof the file usually only incur an extra cost when crossing a compression blockboundary. The situation is different when reading from a file in a StorageCheckpoint; in this case, nothing goes into the page cache beyond the dataactually requested. For optimal read performance of a compressed file accessedthrough a Storage Checkpoint, the application should use a read size thatmatches the compression block size.

143Managing hostsCompressing files in Veritas Operations Manager

■ When writing to compressed extents, ensure that you have sufficient diskspace and disk quota limits for the new uncompressed extents since the writeuncompresses the extents. If you do not have sufficient disk space, the writecan fail with the ENOSPC error. If you do not have enough disk quota, the writecan fail with the EDQUOT error.

■ An application that reads data from a compressed file and then copies the fileelsewhere, such as tar, cpio, cp, or vi, does not preserve compression in thenew data. The same is true of some backup programs.

■ Backup programs that read file data through the name space do not noticethat the file is compressed. The backup program receives uncompressed data,and the compression is lost.

Setting up compression schedulesVeritas Operations Manager lets you set up a compression schedule for the selectedhost. You can add, update, and delete a schedule.

The schedule applies to the directories that are selected for compression oruncompression for each file system on the host.

See “Adding compression directories” on page 146.

To add a compression schedule

1 Select the file system for compression:

■ In the Veritas Operations Manager console, click Manage > Hosts.

■ In the Hosts view, click the name of the host. The managed host must be5.0 or later.

■ On the File Systems tab, click the file system mount point.To compress files requires Veritas File System (VxFS) file systems withStorage Foundation 6.0 or later and disk layout version 9 or later. VeritasOperations Manager does not support file compression on Windows filesystems.

2 Click the Compression tab.

3 In the Compression Schedule section, click Add Schedule.

4 In the CompressionSchedule window, specify the compression options andclick Save.

See “Compression Schedule options” on page 145.

Managing hostsCompressing files in Veritas Operations Manager

144

To update a compression schedule

1 On the Compression tab, in the CompressionSchedule section, click UpdateSchedule.

If the compression process is running, Update Schedule is not available.Optionally, click Stop to stop the compression process.

2 In the CompressionSchedule window, update the compression options andclick Save.

See “Compression Schedule options” on page 145.

To delete a compression schedule

◆ On the Compression tab, in the CompressionSchedule section, click DeleteSchedule.

Compression Schedule optionsUse the Compression Schedule window to specify the settings to use for ascheduled run of Veritas Operations Manager file compression.

Select Daily, Weekly, or Monthly.Frequency

The options in the When area change depending on theFrequency selection. For Weekly, you can select weekdayto schedule Monday through Friday or select specific daysof the week. For Monthly, you can schedule the compressionto re-occur on a specific day of every month.

When

Specify how long the compression process runs. If alldirectories are not compressed during the specified duration,at the next scheduled compression run, the processcontinues with the remaining directories.

For example, say that a duration of one hour is set and 10directories are enabled for compression. After one hour,nine directories are compressed. The compression processstops. At the next scheduled run, the compression processcontinues with the tenth directory. The process then startsover with the first directory and compresses any new filesthat were added since the last run.

Default: four hours

Compression Duration

Specify how many CPUs to use for the scheduledcompression run.

Default: 50 percent of the CPUs available for the host, upto 4 CPUs.

Number of CPUs to use forcompression


Adding compression directoriesVeritas Operations Manager lets you select which directories to compress for theselected file system. You can add or remove directories from the list of directoriesthat are enabled for compression. Directories that are enabled for compressionare compressed during scheduled runs of the compression process or can becompressed on demand.

See “Setting up compression schedules” on page 144.


To add directories for compression



■ In the Hosts view, click the name of the host. The managed host must be5.0 or later.

■ On the File Systems tab, click the file system mount point.To compress files requires Veritas File System (VxFS) file systems withStorage Foundation 6.0 or later and disk layout version 9 or later. VeritasOperations Manager does not support file compression on Windows filesystems.


3 In the Directories Enabled for Compression/Uncompression section, clickActions > Add Directory.

Alternatively, click the Add Directory button in the Compression Statussection.

4 In the Selectdirectorytoaddforcompression window, select the directories.The window lists only the directories that have not yet been added forcompression.

See “Select directory to add for compression options” on page 146.

5 Click Save. The directories are added to the table of directories that areenabled for compression/uncompression and shown as enabled forcompression.

Select directory to add for compression optionsUse the Selectdirectory toadd for compression window to select the directoriesto add for Veritas Operations Manager file compression. Only directories that arenot yet selected for compression are listed.


146

When the window opens, first-level directory names in the file system are listed.You can filter which directories are listed using regular expressions.

To drill down to view subdirectories, click the directory name. To return to theparent directory, click its name in the Current Directory Path field.

To add a directory, select the check box next to it. Adding a parent directory addsany subdirectories as well.

When you click Save, the window closes and the selected directories are listedunder Directories Enabled for Compression/Uncompression.

If you want to add some subdirectories and leave other subdirectories unselected,drill down to the list of subdirectories, make the selection, and click Save. Theselected directories are added to the list of directories enabled for compression.If you return to the parent directory without saving, the selections at the lowerlevel are lost.

Removing compression directoriesIf you no longer want directories to be compressed, remove them from the list ofdirectories that are enabled for compression. After you remove a directory, nofurther compression occurs for that directory. During removal, you can alsospecify that the directory be uncompressed. You can also uncompress directorieson demand.

See “Uncompressing directories on demand” on page 149.

To remove directories from compression

1 On the Compression tab, in the Directories Enabled forCompression/Uncompression section, select the check boxes next to thedirectories that you want to remove from compression.

2 Click Actions > Remove Directory.

3 In the confirmation window, choose whether to uncompress the directoriesthat are removed. If you select the check box for uncompression, an additionaloption is displayed that lets you select the number of CPUs for theuncompression.

If you choose to uncompress, the selected directories are uncompressedimmediately if the compression process is not running. Otherwise, they areuncompressed at the next scheduled run of the compression process.


Starting or stopping compression on demandVeritas Operations Manager lets you start the compression or uncompressionprocess immediately if there are no compression-related activities occurring onthe host. You can stop an ongoing compression run at any time.

Note: The compression applies to all that are directories listed for compressionin the Directories Enabled for Compression/Uncompression area. You cannotlimit the compression to an individual directory on the list.

To start compression on demand



■ In the Hosts view, click the name of the host.

■ On the File Systems tab, click the file system mount point.


3 In the Compression Status section, click the Compress Now button.

The button is not available if a compression activity is occurring.

4 On the CompressNow panel, specify the options for compression and confirmstarting compression.

See “Compress Now options” on page 148.

To stop a compression or uncompression activity

◆ On the Compression tab, in the Compression Schedule section, click Stop.

Compress Now optionsAfter selecting the Compress Now button, optionally change the compressiondefaults.


148

Specify how long the compression process runs. Alldirectories may not be processed during the specifiedduration. For example, a duration of one hour is set and 10directories are enabled for compression. After one hour,nine directories are compressed. The compression processstops. At the next scheduled run, the compression processcontinues with the tenth directory, and then starts overwith the first directory and compresses any new files addedsince the last run.

Default: four hours

Compression Duration

Specify how many CPUs to use for compression.

Default: 50 percent of the CPUs available for the host, upto 4 CPUs.

Number of CPUs to use forcompression


Uncompressing directories on demandIf you compress directories using Veritas Operations Manager, you can lateruncompress directories on demand.

To uncompress directories on demand

1 On the Compression tab, in the Directories Enabled forCompression/Uncompression section, click Actions > Uncompress Now.

2 In the Uncompression confirmation window, optionally select the check boxto remove the selected directories from compression. Optionally, change thenumber of CPUs to use for uncompression.

If the compression process is not running, the selected directories areuncompressed immediately. Otherwise, they are uncompressed at the nextscheduled run of the compression process.

See “About file compression in Veritas Operations Manager” on page 143.

About using Veritas Operations Manager to managethe hosts with Symantec ApplicationHA

Symantec ApplicationHA provides enhanced monitoring capabilities for theapplications that run on the virtual machines that are hosted on VMware ESXServers. ApplicationHA uses the high availability concepts of agents, resources,and service groups. However, it does not include the high availability cluster

149Managing hostsAbout using Veritas Operations Manager to manage the hosts with Symantec ApplicationHA

components such as the Global Atomic Broadcast (GAB) and Low Latency Transport(LLT). You can install ApplicationHA on the Linux and the Windows platforms.

ApplicationHA can communicate directly with VMware HA with a mechanismcalled "heartbeat". If an application fails and the agents cannot start theapplication, ApplicationHA invokes a trigger that requests VMware HA to restartthe virtual machine

Veritas Operations Manager provides enhanced monitoring and reportingcapabilities for the virtual machines that have ApplicationHA configured. Thecapabilities of Veritas Operations Manager to manage and monitor the applicationsand generate various types of reports help you manage the applications insideyour virtual machines in a deeper level. To use Veritas Operations Manager tomanage the applications on the virtual machines where ApplicationHA is installed,you must add all these virtual machines as hosts to Veritas Operations Managerusing the Veritas Operations Manager console. If ApplicationHA is installed onthese virtual machines, Veritas Operations Manager identifies the virtual machinesas hosts, and the applications inside them as service groups. This lets you performvarious high availability operations on the applications inside the virtual machinesusing the Veritas Operations Manager console. However, the high availability andthe disaster recovery features such as readiness, fire drills, and globalconfiguration of clusters are not supported in Veritas Operations Manager forthe applications that are managed by ApplicationHA.

Veritas Operations Manager uses a service group that is created by ApplicationHAas the heartbeat agent for each virtual machine. You can identify this servicegroup by the name "VCSAppMonHBSG". You must not perform any operationson this service group.

After you add the virtual machines as hosts to Veritas Operations Manager, VeritasOperations Manager uses a consistent monitoring mechanism to monitor theapplications that run on these virtual servers. This mechanism lets theadministrators of the VMware vCenter Servers identify the problems with theconfigured applications, and take necessary steps to rectify it. In some cases, youmay not want the VMware vCenter Servers to act upon the faults on certainsystems or service groups. In such cases, Veritas Operations Manager gives youoptions to disable the fault reporting function. You can enable the fault reportinganytime after you disable it.

Veritas Operations Manager console displays the hosts and the service groupsindividually when it displays the information pertaining to the objects ofApplicationHA.

Managing hostsAbout using Veritas Operations Manager to manage the hosts with Symantec ApplicationHA

150

Note:ApplicationHA includes the VRTSsfmhpackage version 3.0.358 that has beenshipped with Veritas Operations Manager version 3.0 RU1. You must upgradetheVRTSsfmh package to version 3.1 or later to use Veritas Operations Managerto manage the virtual machines that have ApplicationHA installed.

For more information on how to upgrade the VRTSsfmh package, refer theVeritasOperations Manager Management Server Installation Guide.

Enabling application heartbeat for a service groupSymantec ApplicationHA sends consistent messages to the VMware vCenterServer. These messages, normally called as "heartbeats" lets the VMware vCenterServer know about the health of a service group. In certain situations, you maynot want to propagate the faults on a service group to the VMware vCenter Serverbecause the actions that the server performs to resolve the fault (mostly startingor stopping of the virtual machine) can result in the downtime of the entire virtualmachine. In such situations, you can disable the heartbeats and then enable itusing the Veritas Operations Manager console.

When you enable the heartbeat on a service group, the heartbeat is enabled forall other service groups in the same host.

To perform this operation, you must have the administrator privileges on theservice groups where you are enabling the application heartbeat.

To enable the application heartbeat service groups

1 In the Veritas Operations Manager console, do one of the following to locatethe service groups:

■ To locate the service groups in the list of all service groups, select Manage> Service Groups.

■ To locate the service groups in a host, select Manage > Hosts and clickService Groups.


■ Select the check boxes to select the service groups to enable the applicationheartbeat. Click Actions above the service groups list and selectApplicationHA > Enable Application Heartbeat.

■ To enable the application heartbeat for a single service group, right-clickon the row of the service group to display the shortcut menu. In case ofmultiple service groups, first select the check box for each service group,and then, right-click on any of the rows to display the shortcut menu.From the shortcut menu, select Enable Application Heartbeat.

151Managing hostsEnabling application heartbeat for a service group

3 In the Enable Application Heartbeat page, click OK.

4 In the Result page, verify that the operation was successful. Click OK.

See “About using Veritas Operations Manager to manage the hosts with SymantecApplicationHA” on page 149.

Disabling application heartbeat for a service groupSymantec ApplicationHA sends consistent messages to the VMware vCenterServer. These messages, normally called as "heartbeats", let the VMware vCenterServer know about the health of a service group. In certain situations, you maynot want to propagate the faults on a service group to the VMware vCenter Serverbecause the actions that the server performs to resolve the fault (mostly startingor stopping of the virtual machine) can result in the downtime of the entire virtualmachine. In such situations, you can disable the heartbeats using the VeritasOperations Manager console.

When you disable the heartbeat on a service group, the heartbeat is disabled forall other service groups on the same host.

To perform this operation, you must have the administrator privileges on theservice groups where you need to disable the application heartbeat.

To disable the application heartbeat service groups

1 In the Veritas Operations Manager console, do one of the following to locatethe service groups:

■ To locate the service groups in a host, select Manage > Hosts and clickService Groups.

■ To locate the service groups in the list of all service groups, select Manage> Service Groups.


■ Select the check boxes to select the service groups to disable theapplication heartbeat. Click Actions above the service groups list andselect ApplicationHA > Disable Application Heartbeat.

■ To disable the application heartbeat for a single service group, right-clickon the row of the service group to display the shortcut menu. In case ofmultiple service groups, first select the check box for each service group,and then, right-click on any of the rows to display the shortcut menu.From the shortcut menu, select Disable Application Heartbeat.

3 In the Disable Application Heartbeat page, click OK.

4 In the Result page, verify that the operation was successful. Click OK.

Managing hostsDisabling application heartbeat for a service group

152

See “About using Veritas Operations Manager to manage the hosts with SymantecApplicationHA” on page 149.

153Managing hostsDisabling application heartbeat for a service group

Managing hostsDisabling application heartbeat for a service group

154

Discovering the server andstorage virtualizationenvironment


■ About the virtualization technologies supported

■ About Control Hosts in Veritas Operations Manager

■ About discovering the VMware Infrastructure using Veritas OperationsManager

■ Viewing the Virtualization Management view

■ Configuring the virtualization discovery

■ Editing a virtualization discovery configuration in Veritas Operations Manager

■ Refreshing a virtualization discovery configuration

■ Removing a virtualization discovery configuration

■ About discovering Solaris zones

■ About discovering Logical domains in Veritas Operations Manager

■ About discovering LPAR and VIO in Veritas Operations Manager

■ About LPAR storage correlation supported in Veritas Operations Manager

■ About Microsoft Hyper-V virtualization discovery

■ About Kernel-based Virtual Machine (KVM) virtualization discovery in VeritasOperations Manager

8Chapter

■ About the reports related to virtualization in Veritas Operations Manager

■ Viewing the virtual environment summary

■ Viewing virtualization servers

■ Viewing the virtual machines

About the virtualization technologies supportedDatacenters adopt virtualization technology to effectively use the IT-infrastructureand substantially reduce the capital and operational expenditures. If you haveadopted virtualization technology in your datacenter, Veritas Operations Managerprovides you an efficient way of discovering and managing your virtual storageand infrastructure assets.

In your datacenter, Veritas Operations Manager helps you view the followingrelationships:

■ Applications in your datacenter that Veritas Operations Manager managesand the virtual hosts on which they are running.

■ Physical storage in your datacenter that is exported to the virtual machines.

Veritas Operations Manager supports the following virtualization technologies:

■ VMware

■ Solaris Zones

■ Oracle VM Server for SPARC (previously called Sun Logical Domains - LDoms)

■ Logical partition (LPAR)

■ Microsoft Hyper-V

■ Kernel-based Virtual Machine (KVM)

In the VMware virtualization technology, a designated Control Host discovers theVMware vCenter Server in the datacenter. This discovery displays those ESXservers that VMware vCenter Server manages, and the virtual machines that areconfigured on the ESX servers.

In the Solaris Zones virtualization technology, the zone agentlet that is presentin the VRTSsfmh package, which is installed on a Solaris managed host discoversthe Global zones that are configured on the host. This discovery displays thenon-Global zones that are configured on the Global Zone.

In the Sun LDoms virtualization technology, the LDom agentlet that is presentin the VRTSsfmh package, which is installed on a Solaris managed host discovers

Discovering the server and storage virtualization environmentAbout the virtualization technologies supported

156

the LDom Server that is configured on the host. This discovery displays the LDomsthat are configured on the LDom Server.

For logical partition (LPAR) discovery, Veritas Operations Manager can useHardware Management Console (HMC), VRTSsfmh package that is installed on theLPAR client, or VRTSsfmh package installed as a part of DMP on the VIO server.

For Microsoft Hyper-V, Veritas Operations Manager discovers Hyper-V virtualmachines and their correlation with the Hyper-V server. It also discovers thestorage that is provisioned to the guests, and its correlation with the virtualmachine and Hyper-V server. The Hyper-V guest (with or without VRTSsfmhpackage), when added to Veritas Operations Manager Management Server domain,provides storage mapping discovery.

For Kernel-based Virtual Machine (KVM), Veritas Operations Manager discoversKVM virtual machines on the Linux host if the KVM modules are installed, andconfigured. Veritas Operations Manager discovers basic information about onlyrunning virtual machines. For example, virtual machine name, CPU, and so on.

See “About discovering the VMware Infrastructure using Veritas OperationsManager” on page 159.

See “About discovering Solaris zones” on page 173.

See “About discovering Logical domains in Veritas Operations Manager”on page 178.

See “About discovering LPAR and VIO in Veritas Operations Manager” on page 182.

See “About Microsoft Hyper-V virtualization discovery” on page 185.

About Control Hosts in Veritas Operations ManagerVeritas Operations Manager uses Control Hosts as a discovery mechanism. InVeritas Operations Manager, the Control Hosts discovers the following:

■ Information on VMware Virtualization Infrastructure. To configure this ControlHost on a managed host, you need to install the Control Host Add-on on themanaged host.

■ Agentless discovery of a host. The Control Host Add-on enables a managedhost to perform agentless discovery of remote hosts. Platform support for ahost that can act as a Control Host is the same as that of Management Server.

Note: The following sections provide detailed information about theabove-mentioned features.

157Discovering the server and storage virtualization environmentAbout Control Hosts in Veritas Operations Manager

Information on VMware Virtualization Infrastructure

In Veritas Operations Manager, you can configure Veritas Operations ManagerManagement Server or a managed host that reports to Management Server asControl Host for discovering the information on the VMware virtualizationinfrastructure. For this configuration, you must install the Control Host Add-onon the traditional hosts that you want to designate as Control Host. In VeritasOperations Manager, you must download the Control Host Add-on from theSymantec Web site, upload to the Deployment Management Repository, andinstall it on the relevant traditional hosts.

In your datacenter, Control Hosts help Management Server in discovering thefollowing information on VMware virtualization infrastructure:

■ VMware VirtualCenter servers that are configured in your datacenter.

■ VMware ESX servers that Virtual Centers manage.

■ VMware Virtual machines that are configured on the VMware ESX servers.

■ VMware HA Clusters

In Veritas Operations Manager, you can install the Control Host Add-on on themanaged hosts with the following platforms:

■ Solaris 10 (SPARC)

■ Linux (64-bit)

■ Solaris x86 (64-bit)

■ Windows Server 2003/2008 (64-bit)

Note: To administer a Control Host on the Windows platform, VeritasOperations Manager creates a user named 'vomuser' with the administrativeprivileges.

Ensure that the Control Hosts can ping the VirtualCenter servers from which theycan discover the information on VMware Infrastructure.

The Control Host discovers the VMware Infrastructure from the traditional hostsother than Management Server. After the discovery of VMware Infrastructure,the Control Host reports the discovered data to Management Server. ManagementServer coalesces the data that it receives from the Control Host and populates therelevant views.

You can designate a managed host that reports to Management Server as ControlHost to address the following situations:

Discovering the server and storage virtualization environmentAbout Control Hosts in Veritas Operations Manager

158

■ To discover the VirtualCenter server that is behind a firewall and you do notwant to install Management Server inside the firewall.

■ To except Management Server from the discovery of VMware infrastructureto reduce the load on Management Server.

Agentless discovery of a remote host

To perform agentless discovery of hosts, you must install the Control Host Add-onon one of the managed hosts. You can install the Control Host Add-on onManagement Server, however it is not recommended as it puts extra load onManagement Server.

A UNIX Control Host can only discover UNIX agentless hosts using SSH. AWindows Control Host can discover Windows agentless hosts using WMI or UNIXagentless hosts using SSH. Ensure that you install one or more Control Hosts onthe appropriate platform depending on the operating system of the remote hostsyou want to discover agentlessly.

See “How Veritas Operations Manager discovers VirtualCenter and ESX servers”on page 161.

See “Information that Veritas Operations Manager discovers on the VMwareInfrastructure components” on page 162.


About discovering the VMware Infrastructure usingVeritas Operations Manager

In Veritas Operations Manager, a managed host that is designated as a ControlHost can discover the VMware Infrastructure.

The managed host on which you have installed the Control Host Add-on discoversthe information on the following VMware infrastructure components in yourdatacenter:

■ VirtualCenter servers, which manage one or more ESX servers.

■ ESX servers on which the individual virtual machines are configured.

A VirtualCenter or an ESX server does not need to be a managed host to let theControl Host to discover them.

Ensure that the Control Hosts can ping the VirtualCenter servers or the ESXservers from which they can discover the information on VMware Infrastructure.Ideally, a Control Host and a VirtualCenter server or an ESX server from whichthe Control Host wants to discover the information on VMware Infrastructuremust be on the same subnet.

159Discovering the server and storage virtualization environmentAbout discovering the VMware Infrastructure using Veritas Operations Manager

The Control Host Add-on that you install on the designated Control Hosts containsthe VMware Infrastructure SDK (VI SDK), which provides a standard interfacefor the VMware servers and the Control Hosts to access the VMware Infrastructure.A Control Host reports the information on the VMware Infrastructure that itdiscovers to Management Server. Management Server coalesces the data that itreceives from the Control Host and populates the relevant views.

Note: If you have installed Storage Insight Add-on 4.0, Veritas Operations Managercan correlate the storage that is visible to the ESX servers with the storageenclosures that Storage Insight Add-on supports.

In Veritas Operations Manager, you must configure the storage enclosure discoveryusing Storage Insight Add-on before you configure the discovery of theVirtualCenter and the ESX servers.

If you configure the storage enclosure discovery after you configure the discoveryof the VirtualCenter and the ESX servers, then the storage enclosure details becomevisible to the ESX servers from the next discovery cycle.

For more information on the supported versions of VirtualCenter servers and ESXservers, refer to the Veritas Operations Manager Hardware and SoftwareCompatibility List (HSCL).

See “About the virtualization technologies supported” on page 156.


See “Requirements for discovering VirtualCenter and ESX servers using VeritasOperations Manager” on page 161.



See “About the datastores in Veritas Operations Manager” on page 163.

See “Configuring the virtualization discovery” on page 166.

See “Refreshing a virtualization discovery configuration” on page 172.

See “Viewing virtualization servers” on page 188.

See “Viewing the virtual machines” on page 190.


Discovering the server and storage virtualization environmentAbout discovering the VMware Infrastructure using Veritas Operations Manager

160

Requirements for discovering VirtualCenter and ESX servers usingVeritas Operations Manager

The following are the requirements for discovering VMware Infrastructure usingVeritas Operations Manager:

■ Install the VRTSsfmh package on the traditional hosts on which you want toinstall the Control Host Add-on.

■ Ensure that the Control Hosts can ping the VirtualCenter servers or the ESXservers from which they can discover the information on VMwareInfrastructure.

■ Ensure that you have appropriate privileges to log on to the VirtualCenterserver or the ESX server.

■ Ensure that you have the Browse Datastore privileges on the VirtualCenter orthe ESX server that you want Veritas Operations Manager to discover.




How Veritas Operations Manager discovers VirtualCenter and ESXservers

Veritas Operations Manager uses designated Control Hosts to discover theinformation on the virtual machines. You must install the Control Host Add-onon the managed hosts that you want to designate as Control Hosts. Control Hostuses the VMware Infrastructure SDK (VI SDK) to access the VirtualCenter andthe ESX servers.

Ensure that the Control Hosts can ping the VirtualCenter servers or the ESXservers from which they can discover the information on VMware Infrastructure.Ideally, a Control Host and a VirtualCenter server or an ESX server from whichthe Control Host wants to discover the information on VMware Infrastructuremust be on the same subnet.

When you configure the virtualization discovery in Veritas Operations Manager,you must ensure that you have appropriate privileges to access the VirtualCenteror the ESX servers. Also, you must ensure that you have Browse Datastoreprivileges on the VirtualCenter or the ESX servers from which you want to discoverthe VMware Infrastructure information. There are two methods to enable the


virtualization discovery of the servers. The AutoDiscover option, when enabled,allows you to discover all the ESX servers that are currently existing as well asany new servers that are added under the VirtualCenter automatically. The SelectESX Servers option allows you to select some or all of the ESX servers. If theservers are selectively enabled, the new servers configured under VirtualCenterare discovered only after they are manually enabled using the Edit VirtualizationConfiguration wizard panel.

The VirtualCenter or the ESX servers contains a Web server, which is an ApacheTomcat server. The web services that are hosted on the Web server communicatewith the VMware Infrastructure. After you configure a virtualization discovery,the Control Host uses VI SDK to communicate with the web services that arehosted on the Web server. For this communication, the Control Host uses theHTTPS protocol.

The URL for the VMware SDK web services is as follows:

https://traditional host name of the VirtualCenter or the ESX servers/sdk

After the discovery of VMware Infrastructure, the Control Host reports thediscovered data to Management Server. Management Server coalesces the datathat it receives from the Control Host and populates the relevant views.







Information that Veritas Operations Manager discovers on the VMwareInfrastructure components

Discovery of the VMware Infrastructure components provides the followinginformation:

■ Host name and IP address of the VMware Infrastructure components thatVeritas Operations Manager discovers.

■ Operating system handles of the VMware Infrastructure components thatVeritas Operations Manager discovers.


162

■ Correlation of operating system handles to the virtual disks that are associatedwith the virtual machines configured on the ESX servers.





See “Viewing the virtual environment summary” on page 188.



About the datastores in Veritas Operations ManagerA datastore is a collection of physical storage that is created based on the disksand LUNs that are attached to an ESX server. The storage is assigned to VMwarevirtual machines from the datastore. Veritas Operations Manager lets you viewthe storage mapping between the datastore and the virtual machines.

A datastore is a storage location for virtual machine files.This storage locationcan be a VMFS volume, a directory on Network Attached Storage, or a local filesystem path.

Also, VMware can assign storage to the virtual machines directly from the physicaldisks that are available with the ESX servers. This storage assignment is knownas Raw Disk Assignment.


About the multi-pathing discovery in the VMware environmentThe support for multi-pathing discovery in the VMware environment lets youdiscover information that is related to the disk multipathing for the ESX serversin your datacenter. It lets you manage disk paths under VxDMP on the ESX servers.It is enabled using Control Host Add-on. For each disk, you can discover thefollowing information:

■ Total number of paths, and number of active paths.

■ The details about the path.


■ The information about the multipathing applications. The multipathingapplications can be VMware native multipathing (NMP), EMCPowerPath/Virtual Edition, or Symantec VxDMP.

You can enable or disable the disk paths using the DMP maintenance wizard usingthe Veritas Operations Manager console.

Note: You can also generate the report containing the details about the DMPlicenses that are installed on the VMware ESX servers. The license discovery isalso enabled using Control Host Add-on.

See “About the user privileges for multi-pathing discovery in the VMwareenvironment” on page 164.

About the user privileges for multi-pathing discovery in theVMware environmentThe following table lists the privileges that are required for the multi-pathingdiscovery on the ESX server:

Table 8-1

What if the privilege is notgiven

Is it optionalPrivilege

VMware discovery does nothappen.

NoDatastore\Browse Datastore

■ VxDMP tunablesdiscovery does nothappen.

■ The discovery of VxDMPlicenses does not happen.

■ DMP path maintenanceoperations in VeritasOperations Manager willnot be able to operate onthe disk paths in the ESXservers that are managedby VxDMP.

No.

However, it is required onlyfor the ESX servers that runVxDMP. It is not required ifyou don’t have any ESXrunning VxDMP.

Host\CIM\CIM Interaction


164


What if the privilege is notgiven

Is it optionalPrivilege

Veritas Operations Managercannot discover the versionof VxDMP running inside theVMware ESX server. There isno effect on the ESX serversthat are not running VxDMP.

YesHost\Configuration\ChangeSettings

See “About the multi-pathing discovery in the VMware environment” on page 163.

Viewing the Virtualization Management viewIn Veritas Operations Manager, the Virtualization Management view displaysthe information on the virtualization environment that Veritas OperationsManager discovers. In this view, a tree-table structure displays the informationon the virtual servers that Veritas Operations Manager discovers.

In the Virtualization Management view, you can perform the following tasks:

■ Configure the virtualization discovery.

■ Edit the virtualization discovery that you have already configured.

■ Refresh a virtual server to view the periodic discovery of virtual servers thatit manages.

■ Remove a virtual server that Veritas Operations Manager discovers.

In the Virtualization Management view, you can view the following details of avirtual server:

■ Servername: Host name of the virtual server that Veritas Operations Managerdiscovers. You can click the + sign on the left side of the VirtualCenter servername to view the list of ESX servers that the VirtualCenter server manages.Click the + sign on the left side of the HMC server name to view the list of LPARservers that the HMC server manages.

■ Type: Type of the host that Veritas Operations Manager discovers. This fieldspecifies whether the host is a VirtualCenter server, ESX server, LPAR server,or HMC server.

■ Control Host: Host name of the Control Host, which is used to discover thevirtual server.

165Discovering the server and storage virtualization environmentViewing the Virtualization Management view

■ Configuration Name: Name that you have specified for the virtualizationdiscovery configuration.

■ Auto Discovery: Displays the status of auto discovery configuration on theserver.

■ DiscoveryState/Time: Discovery state and time. If the virtualization discoveryis successful, this field displays the discovery state as Successful. For an ESXserver or LPAR server, this field displays the date and time at which thediscovery occurred. Also, this field displays the status of the latest discoverycycle for an ESX server.

To view the Virtualization Management view

◆ In the Veritas Operations Manager console, select Settings>Virtualization.


See “Editing a virtualization discovery configuration in Veritas OperationsManager” on page 169.


See “Removing a virtualization discovery configuration” on page 173.

Configuring the virtualization discoveryIn Veritas Operations Manager, you must configure the virtualization discoveryto let a Control Host discover the virtual servers. You can configure thevirtualization discovery for VMware discovery, or HMC discovery.

The VMware discovery provides the following information:

■ Information on VirtualCenter servers

■ Information on the ESX servers that the VirtualCenter server manages

■ Information on the virtual machines that are configured on the ESX servers

The HMC discovery provides the following information:

■ Information on HMC servers

■ Information on the LPAR servers that the HMC server manages

■ Information on the virtual machines that are configured on the LPAR servers

In Veritas Operations Manager, you can use the Virtualization Configurationwizard to configure the virtualization discovery.

After you configure virtualization discovery, you can view the VirtualCenter orHMC servers, which Veritas Operations Manager discovers, in the VirtualizationManagement view. All ESX servers that each VirtualCenter server manages are

Discovering the server and storage virtualization environmentConfiguring the virtualization discovery

166

displayed as children under the VirtualCenter server. All LPAR servers that eachHMC server manages are displayed as children under the HMC server.

To configure virtualization discovery in Veritas Operations Manager

1 In the Veritas Operations Manager console, select Settings > Virtualization.

2 In the VirtualizationManagement view, click Actions > AddConfiguration.

3 In the VirtualizationConfiguration wizard panel, enter the details and clickNext.

See “Virtualization Configuration panel options” on page 167.

4 In the Select option wizard panel, select the method for virtualizationdiscovery of the servers, and click Finish.

See “Select option panel” on page 169.

5 In the result panel, view the progress of the configuration . After theconfiguration is complete, click OK.

See “Virtualization Configuration progress details panel” on page 169.




See “Viewing the Virtualization Management view” on page 165.

Virtualization Configuration panel optionsUse this wizard panel to configure virtualization server discovery in VeritasOperations Manager.

Table 8-2 Virtualization Configuration panel options

DescriptionField

Select the configuration type from the drop-down list.Configuration Type

Enter a name for the virtualization server discoveryconfiguration. You can reference the new virtualizationserver discovery configuration with the name that youspecify in this field.

Configuration Name

167Discovering the server and storage virtualization environmentConfiguring the virtualization discovery

Table 8-2 Virtualization Configuration panel options (continued)

DescriptionField

Select the name of the control host from the drop-down list:

■ In case of VMware configuration, Veritas OperationsManager uses the control host that you specify in thisfield to discover the VMware environment thatVirtualCenter and ESX servers manage. The control hostand the VirtualCenter or the ESX servers should belongto the same subnet.

■ In case of HMC configuration, Veritas OperationsManager uses the control host that you specify in thisfield to discover the HMC environment that HMC serversmanage. The control host and the HMC servers shouldbelong to the same subnet.

Control Host

This field is displayed only when you are configuring aVMware configuration. Specify the fully-qualified name ofthe VirtualCenter or ESX server that you want the controlhost to discover along with its port number, separated by acolon. If the VirtualCenter web service is running on adefault port, you do not need to specify the port number.

VMware vCenter server

This field is displayed only when you are configuring a HMCconfiguration. Specify the fully-qualified name of the HMCserver that you want the control host to discover.Alternatively, you can also specify the IP address of theserver.

HMC Server

Enter the user name that you can use to log on to the virtualservers that you want the control host to discover.

You can use a read-only user account if it has the BrowseDatastore permissions on the virtual servers.

Note: Ensure that you have appropriate privileges to log onto the virtual servers.

User Name

Enter the password that you can use with the user name tolog on to the virtual servers that you want the control hostto discover.

Password


Discovering the server and storage virtualization environmentConfiguring the virtualization discovery

168

Select option panelUse this wizard panel to choose a method to enable the virtualization discoveryconfiguration of servers.

Table 8-3 Select option panel

DescriptionField

Select this method to discover the ESXServers or LPAR Servers automatically.

When Auto Discover option is enabled, thelist of configured servers is not displayed.

Auto Discover ESX Servers

Auto Discover LPAR servers

Select this method to selectively discoverthe ESX Servers or LPAR Servers .

Select ESX Servers

Select LPAR servers

The name of the server.Name

Select the check box to enable discovery ofthe server.

Discovery Enabled

The configuration name of the server.Configuration Name


Virtualization Configuration progress details panelUse this wizard panel to view the progress of the virtualization discoveryconfiguration. This panel displays the start and the successful completion of thevirtualization discovery.


Editing a virtualization discovery configuration inVeritas Operations Manager

In Veritas Operations Manager, you can edit the virtualization discovery that youhave already configured.

You can edit a virtualization discovery configuration to modify the followinginformation:

■ Name of the configuration.

■ Name of the VirtualCenter or HMC server that you have specified when youconfigured the virtualization discovery.

169Discovering the server and storage virtualization environmentEditing a virtualization discovery configuration in Veritas Operations Manager

■ Credentials to log on to the VirtualCenter or HMC server.

To edit a virtualization discovery configuration in Veritas Operations Manager


2 In the VirtualizationManagement view, in the table that displays the detailsof the virtualization discovery configurations, select the configuration thatyou want to edit.

3 At the top of the table, which displays the virtualization discoveryconfigurations, click Actions > Edit Configuration.

4 In the Virtualization Configuration wizard panel, modify the requiredinformation, click Next.

See “Virtualization Configuration panel options (Edit)” on page 170.

5 In the Selectoption wizard panel, edit the method for virtualization discoveryof the servers, click Finish.

See “Select option panel (Edit)” on page 171.

6 In the result panel, view the progress of the configuration, click OK.

See “Virtualization Configuration progress details panel (Edit)” on page 172.





Virtualization Configuration panel options (Edit)Use this wizard panel to edit the virtualization server discovery that you haveconfigured in Veritas Operations Manager.

Table 8-4 Virtualization Configuration panel options for editing configurations

DescriptionField

Displays the configuration type.Configuration Type

Displays the name that is provided to the virtualizationdiscovery configuration. You can modify the name of theconfiguration in this field.

Configuration Name

Displays the name of the Control Host that is specified fordiscovering the virtual servers that Veritas OperationsManager manages.

Control Host

Discovering the server and storage virtualization environmentEditing a virtualization discovery configuration in Veritas Operations Manager

170

Table 8-4 Virtualization Configuration panel options for editing configurations(continued)

DescriptionField

This field is displayed only when you edit a VMwareconfiguration. The field displays the name of theVirtualCenter server that you have specified when youconfigured the VMware discovery. You can modify the nameof the server in this field.

VMware VCenter Server

This field is displayed only when you edit a HMCconfiguration. The field displays the name of the HMC serverthat you have specified when you configured the HMCdiscovery. You can modify the name of the server in thisfield.

HMC Server

Displays the user name that you can use to log on to thevirtual servers that you have specified. You can modify theuser name in this field.

Note: Ensure that you have appropriate privileges to log into the virtual servers.

User Name

Displays the password that you can use with the user nameto log on to the virtual servers that you have specified. Youcan modify the password in this field.

Password


Select option panel (Edit)Use this wizard panel to choose a method to edit the virtualization discoveryconfiguration of servers.

Table 8-5 Select option panel

DescriptionField

Select this method to discover the ESXservers or LPAR servers automatically.

When Auto Discover option is enabled, thelist of configured servers is not displayed.

Auto Discover ESX Servers

Auto Discover LPAR servers

Select this method to selectively edit thediscovery of ESX servers or LPAR servers.

Select ESX Servers

Select LPAR servers

171Discovering the server and storage virtualization environmentEditing a virtualization discovery configuration in Veritas Operations Manager

Table 8-5 Select option panel (continued)

DescriptionField

The name of the server.Name

Select the check box to enable discovery ofthe server.

Discovery Enabled

The configuration name of the server.Configuration Name


Virtualization Configuration progress details panel (Edit)Use this wizard panel to view the progress of the virtualization discoveryconfiguration update. This panel displays the start and the successful update ofthe virtualization discovery configuration.


Refreshing a virtualization discovery configurationIn Veritas Operations Manager, you can refresh the virtual server that VeritasOperations Manager has already been discovered.

To refresh a virtualization discovery configuration in Veritas Operations Manager


2 In the VirtualizationManagement view, in the table that displays the detailsof the virtualization discovery configurations, select the configuration thatyou want to refresh.

3 At the top of the table, which displays the virtualization discoveryconfigurations, click Actions > Refresh Configuration.

4 In the RefreshVirtualizationConfiguration wizard panel, view the progressof the refresh task. After the refresh of the selected virtualization discoveryconfiguration is completed, the RefreshVirtualizationConfiguration paneldisplays the message that the refresh is successfully completed.

5 Click OK.


Discovering the server and storage virtualization environmentRefreshing a virtualization discovery configuration

172




Removing a virtualization discovery configurationIn Veritas Operations Manager, you can remove a virtualization discoveryconfiguration.

To remove a virtualization discovery configuration in Veritas Operations Manager


2 In the VirtualizationManagement view, in the table that displays the detailsof the virtualization discovery configurations, select the configuration thatyou want to remove.

3 At the top of the table, which displays the virtualization discoveryconfigurations, click Actions > Remove Configuration.

4 In the Remove Virtualization Configuration wizard panel, click Remove.

5 In the panel that confirms the confirmation, click OK.





About discovering Solaris zonesSolaris zones and Solaris Resource Manager are the components of SolarisContainer environment. A Solaris zone is a virtualized operating systemenvironment that is created within a Solaris 10 operating system instance. Youcan run your applications on the virtualized operating system services that youhave created using Solaris zones.

Two types of Solaris zones are Global Zones and non-Global Zones. In a singleinstance of Solaris operating system, a Global Zone administers multiplenon-Global Zones. Each non-Global Zone is isolated from other non-Global Zones.The IP address, traditional host name, security context, applications, and the

173Discovering the server and storage virtualization environmentRemoving a virtualization discovery configuration

processes that run on each non-Global Zone are completely isolated from theother non-Global Zones.

Veritas Operations Manager discovers the zones that are created on a Solaris 10host that it manages. The Zone Agentlet that is installed along with the VRTSsfmhpackage on a Solaris 10 host lets Veritas Operations Manager Management Serverdiscover the Global Zones and the non-Global Zones on the host.

Through the discovery of Solaris zones, Veritas Operations Manager discoversthe following information:

■ The non-Global Zones that are associated with a Global Zone.

■ The storage that is exported from the Global Zone to non-Global Zones.

■ databases that run in non-Global Zones.

Note:Veritas Operations Manager discovers the Oracle databases on a non-GlobalZone only if the non-Global Zone is in the Running state.

Note: Veritas Operations Manager does not support the discovery of theapplications other than the Oracle databases on non-Global Zones.

See “Requirements for discovering Solaris zones” on page 174.

See “How Veritas Operations Manager discovers Solaris zones” on page 176.

See “Information that Veritas Operations Manager discovers on Solaris zones”on page 177.

See “Limitations of the discovery of Solaris zones in Veritas Operations Manager”on page 178.

Requirements for discovering Solaris zonesThe following are the requirements for discovering Solaris zones in VeritasOperations Manager:

■ Install the VRTSsfmh package on one or more traditional hosts that containsGlobal Zones. This helps Veritas Operations Manager discover non-global-zonesthat are configured on the Global Zones.

■ Ensure that the managed hosts with the Solaris 10 operating system containnon-Global Zones.

■ Ensure that the managed hosts with the Solaris 10 operating system do notcontain any LDoms.

Discovering the server and storage virtualization environmentAbout discovering Solaris zones

174

■ Enable the zlogin utility if you have already disabled it on the non-GlobalZones.See “Requirements for the zlogin utility on non-Global Zones” on page 175.

■ Ensure that the non-Global Zones can access the devices that are exportedfrom the Global Zone.See “Requirements for devices exported to non-Global Zones” on page 175.

■ Ensure that the file systems that are exported from the Global Zone to thenon-Global Zones are mounted in the non-Global Zones.See “Requirements for file systems exported to non-Global Zones” on page 176.





Requirements for the zlogin utility on non-Global ZonesVeritas Operations Manager uses the zloginutility to discover non-Global Zones.By default, the zlogin utility is enabled on non-Global Zones. If you have disabledthe zlogin utility on non-Global Zones, you need to enable it.

For example, you might have disabled the zlogin utility by adding the followingline to the /etc/pam.conf configuration file on a non-Global Zone:

zlogin auth required pam_deny.so.1


Requirements for devices exported to non-Global ZonesVeritas Operations Manager can discover the devices that are exported from theGlobal Zone to non-Global Zones. However, if the storage is not accessible to thenon-Global Zone, Veritas Operations Manager cannot discover that storage asexported from the Global Zone. For example, the storage may not be accessibleto the non-Global Zone because the non-Global Zone was not yet restarted. Ensurethat the non-Global Zones can access the devices that are exported from the GlobalZone.


175Discovering the server and storage virtualization environmentAbout discovering Solaris zones

Requirements for file systems exported to non-Global ZonesVeritas Operations Manager can discover the file systems that are exported fromthe Global Zone to non-Global Zones. However, if a file system is not mounted ina non-Global Zone, Veritas Operations Manager does not discover that file systemas exported from the Global Zone. Ensure that the file systems that are exportedfrom the Global Zone to the non-Global Zones are mounted in the non-GlobalZones.


How Veritas Operations Manager discovers Solaris zonesIn Veritas Operations Manager, the zone agentlet that is part of the VRTSsfmh

package facilitates the discovery of Solaris zones on a Solaris 10 managed host.Through the zone agentlet, Veritas Operations Manager discovers the Global Zoneand the associated non-Global Zones.

Note: Discovery of zones is performed only in the Global Zones.

Veritas Operations Manager uses the following Solaris utilities to discover globaland non-Global Zones:

Table 8-6 Solaris utilities to discover global and non-Global Zones

PurposeUtility

Lists the non-Global Zones that areconfigured on the Global Zone on the Solaris10 managed host

zoneadm

Displays the details of each non-globalconfigurations

zonecfg

Logs on to a non-Global Zone from a GlobalZone.

zlogin





Discovering the server and storage virtualization environmentAbout discovering Solaris zones

176

Information that Veritas Operations Manager discovers on Solariszones

Discovery of Solaris zones provides the following information:

Table 8-7 Solaris zones information that Veritas Operations Manager discovers

ComponentsType of information

Veritas Operations Manager discovers thefollowing:

■ The devices that are exported from theGlobal Zone to the non-Global Zones.

■ The file systems that are mounted in thenon-Global Zones.

Non-Global Zones , which are configured onGlobal Zones


■ Full operating system handles (not slices)

■ Veritas Volume Manager volumes

■ ZFS volumes

Storage that is exported from the GlobalZone to the non-Global Zones


■ Oracle databases

■ Oracle RAC databases.

■ Oracle database on solaris9 brandedzone.

■ Oracle database on Solaris nativebranded zone.

Note: Veritas Operations Manager does notsupport the discovery of secure Oracledatabases on the non-Global Zones. A secureOracle database has a password-set on'sysdba' account to secure them.

Oracle databases inside non-Global Zones





177Discovering the server and storage virtualization environmentAbout discovering Solaris zones

Limitations of the discovery of Solaris zones in Veritas OperationsManager

The following limitations apply to the discovery of Solaris zones in VeritasOperations Manager:

■ Veritas Operations Manager does not support the discovery of Solaris zoneson Solaris managed hosts where both the zones and the LDoms are configured.

■ Veritas Operations Manager does not recommend the installation of theVRTSsfmh package in non-Global Zones.

Note: Conversely, you can install Veritas Operations Manager ManagementServer in a non-Global Zone and add the corresponding Global Zone as amanaged host to Management Server.

■ Veritas Operations Manager does not discover the devices that are exportedto non-Global Zones if the zlogin utility is not allowed on them.

■ Veritas Operations Manager discovers only the native and the Solaris-brandedzones.





About discovering Logical domains in VeritasOperations Manager

Logical Domains (LDoms) is the paravirtualization technology from Oracle Sun.An LDom provides a separate virtualized operating system environment and avirtualized CPU that are created within a Solaris operating system instance. EachLDom uses an independent kernel. Each LDom contains a dedicated, virtualizedoperating system, and a virtualized CPU. You can start, stop, and restart theoperating system that run inside an LDom. Each LDom functions as a full virtualmachine with a subset of hardware resources that you can configure as required.You can run your applications on the LDoms.

The physical server in your datacenter on which the LDoms are created is knownas LDom Server. Individual Guest LDoms that are created on an LDom Server can

Discovering the server and storage virtualization environmentAbout discovering Logical domains in Veritas Operations Manager

178

have several different roles, which are based on the context and usage of theLDoms.

The following are the four major types of roles of the LDoms:

Table 8-8 LDom roles

DescriptionLDom role

Creates and manages other LDoms andservices by communicating with thehypervisor that is present in the LDomServer.

Control domain

Provides the services to other LDoms thatare created on the LDom Server. Forexample, the Service domain provides avirtual network switch or a virtual diskservice.

Service domain

Accesses the inputor output devices directly.For example, the I/O domain can access anetwork device.

I/O domain

Uses the services from the Service and theI/O domains. The Control domain managesthe Guest domains.

Guest domain

The LDom Agentlet that is installed along with the VRTSsfmh package on a Solaristraditional host lets Veritas Operations Manager Management Server discoverthe LDom Server and Guest LDoms that are configured on the LDom server.


See “Requirements for discovering Solaris Logical domains using VeritasOperations Manager” on page 180.

See “How Veritas Operations Manager discovers Solaris Logical domains”on page 180.

See “Information on Logical domains that Veritas Operations Manager discovers”on page 181.

See “Limitations of the discovery of Logical domains in Veritas OperationsManager” on page 182.

179Discovering the server and storage virtualization environmentAbout discovering Logical domains in Veritas Operations Manager

Requirements for discovering Solaris Logical domains using VeritasOperations Manager

The following are the requirements for discovering Solaris LDoms using VeritasOperations Manager:

■ Install the VRTSsfmh package on one or more traditional hosts with the Solarisoperating system on which you want Veritas Operations Manager to discoverSolaris LDoms.

■ Ensure that the managed hosts with the Solaris operating system containLDoms.





How Veritas Operations Manager discovers Solaris Logical domainsIn Veritas Operations Manager, the LDom agentlet that is part of the VRTSsfmh

package facilitates the discovery of LDoms on a Solaris managed host. Throughthe LDom agentlet, Veritas Operations Manager discovers the LDom Server andthe associated Guest LDoms.

Veritas Operations Manager uses the ldm command to discover the details ofSolaris Logical domains.

The following are the major options that Veritas Operations Manager uses withthe ldm command to discover the details of Solaris Logical domains:

Table 8-9 Options that Veritas Operations Manager uses with the ldmcommand

Purposeldm command and option

Lists all the LDoms that are configured onthe LDom Server and their details.

ldm list

Discovers the information on the CPU andmemory of the LDoms that VeritasOperations Manager discovers.

ldm devices

Discovering the server and storage virtualization environmentAbout discovering Logical domains in Veritas Operations Manager

180





Information on Logical domains that Veritas Operations Managerdiscovers

Discovery of Solaris LDoms provides the following information:

Table 8-10 LDom information that Veritas Operations Manager discovers

ComponentsType of Information


■ Total number of Virtual CPUs.

■ Number of Virtual CPUs by core.

■ Number of Virtual CPUs that are assignedto each LDom.

■ Total system memory.

■ Available system memory.

■ Memory, which is assigned to each LDom.

Guest LDoms that are configured on LDomServers





181Discovering the server and storage virtualization environmentAbout discovering Logical domains in Veritas Operations Manager

Limitations of the discovery of Logical domains in Veritas OperationsManager

The following limitations apply to the discovery of Solaris LDoms in VeritasOperations Manager:

■ Veritas Operations Manager does not discover the Solaris LDoms that are inthe inactive state.

■ Veritas Operations Manager does not perform the discovery of Solaris LDomsalong with the discovery of Solaris zones





About discovering LPARandVIO inVeritasOperationsManager

You can use Veritas Operations Manager to configure LPAR server, and discoverthe information that is related to LPARs, VIO clients, and VIO servers in yourdatacenter. There are two methods to enable the virtualization discovery of theservers. The Auto Discover option, when enabled, allows you to discover all theLPAR servers that are currently existing as well as any new servers that are addedunder the HMC server automatically. The SelectLPARServers option allows youto select some or all of the LPAR servers. If the servers are selectively enabled,the new servers configured under the HMC server are discovered only after theyare manually enabled using the Edit Virtualization Configuration wizard panel.

Note: Agentless discovery of client LPARs and VIO servers is not supported.

LPAR discovery mechanisms can be grouped into the following categories:

■ Discovery using Hardware Management Console (HMC): HMC server managesLPAR servers, and lets you discover information related to VIO servers, andVIO clients. You can use virtualization management option on Veritas

Discovering the server and storage virtualization environmentAbout discovering LPAR and VIO in Veritas Operations Manager

182

Operations Manager console to add HMC server to Veritas Operations ManagerManagement Server.To add HMC server to Veritas Operations Manager, you need to install theControl Host add-on on the host where HMC server should be added. VirtualSCSI disks on LPAR client are supported. However, NPIV, or virtual FibreChannel disks are not supported. Currently, only Virtual SCSI disks backed bynative or DMP devices are supported.With Veritas Operations Manager 5.0, HMC server itself provides additionalstorage information about VIO server. The information is grouped under Disk,LUN, Adapter, Virtual machines, and Storage Mapping tabs on VeritasOperations Manager console. By configuring HMC server only (withoutVRTSsfmh package), you can discover information about the exported storagefrom VIO server to VIO clients, and the devices that are given to VIO serverfrom storage area network (SAN).

■ Discovery using VRTSsfmh package that is installed on LPAR client: Presenceof VRTSsfmh package on LPAR client provides additional information aboutthem. This information is correlated with the information that is discoveredusing HMC server.With Veritas Operations Manager 5.0, Virtual SCSI device discovery, andVirtual SCSI device correlation with the source device in VIO server is alsosupported.

Note: Veritas Operations Manager supports only native disks as the back-enddevices for VIO server. These disks can be controlled by Microsoft MultipathI/O (MPIO) and Symantec Dynamic Multipathing (DMP). Disks that arecontrolled by any third-party multipathing software (or the logical volumes),when used as the backing devices, do not have end-to-end correlation available.

■ Discovery using VRTSsfmh package that is installed as a part of DMP on VIOserver: When a VIO server having DMP 6.0 is added, it provides the discoveryof DMP backed exported storage along with the normal managed host discovery.For end-to-end correlation, DMP 6.0 on VIO server is required. Storage mappingfor DMP backed devices is available only if VIO server (with DMP installed) isadded to Veritas Operations Manager Management Server.

■ Storage Insight Add-on lets you discover complete information about arraysand LUNs from SAN, which are allocated to VIO server.

183Discovering the server and storage virtualization environmentAbout discovering LPAR and VIO in Veritas Operations Manager

Note: When an array (consumed by VIO server) is configured, or a VIO server(with DMP) is added to Veritas Operations Manager Management Server,refreshing the corresponding HMC discovery is recommended to view theend-to-end correlation immediately in Veritas Operations Manager console.

See “Prerequisites for LPAR storage correlation support in Veritas OperationsManager” on page 185.


About LPAR storage correlation supported in VeritasOperations Manager

Veritas Operations Manager provides support for storage correlation of VIOservers and clients. The storage correlation support for VIO servers and clientsprovides the information that is related to VIO servers and clients storageconsumption at each layer. The following VIO server and clients-relatedinformation is provided:

■ Information about assigned storage to VIO client; whether the storage in VIOclient is directly assigned from storage area network (SAN), or through a VIOserver.

■ Discovery of VIO servers, and correlation of VIO server storage with SAN.

■ Details of storage that is exported from VIO server to VIO client, and themapping between VIO server source device and VIO client target device.

■ Information about which VIO server participates in storage allocation to VIOclients, and how much storage is allocated.

■ Information about how much storage is allocated to the VIO server, and howmuch storage is allocated to the VIO clients from that VIO server.

■ Information about how much of the allocated storage is consumed by VIOclient for various applications, and file systems.

Note: In Veritas Operations Manager 4.1, virtual machine to virtualization servercorrelation was available, and discovery was done using Hardware ManagementConsole (HMC). However, no storage correlation was available.



Discovering the server and storage virtualization environmentAbout LPAR storage correlation supported in Veritas Operations Manager

184

Prerequisites for LPAR storage correlation support in VeritasOperations Manager

Ensure that the following prerequisites are met before you begin the discoveryof LPAR storage correlation:

■ You have added Hardware Management Console (HMC) to Veritas OperationsManager Management Server. You can navigate to Settings > Virtualization,and add HMC server. The HMC server is used to manage LPAR servers andLPARs.

■ For end-to-end correlation, you must add the LPAR client (with VRTSsfmh

package installed) to Veritas Operations Manager Management Server.

■ You must have the required administrative privileges (hmcoperator role inHMC) to perform these tasks.

■ For end-to-end correlation and discovery of exported storage backed bydynamic-multi-pathing (DMP) on VIO server, the VIO server managed hostmust be added to Veritas Operations Manager Management Server.


About Microsoft Hyper-V virtualization discoveryHyper-V is a hypervisor-based virtualization technology from Microsoft for x86-64systems. You can use Veritas Operations Manager to discover Hyper-V host andvirtual machine-related information if the Hyper-V role is enabled on the managedhost. Veritas Operations Manager uses Hyper-V WMI API for the discovery.

Hyper-V discovery can be grouped into the following categories:

■ Virtual machine discovery: Hyper-V virtual machine discovery by VeritasOperations Manager, and its correlation with the Hyper-V server.

■ Exported storage discovery: Discovery of storage that is provisioned to theguests, and its correlation with the virtual machine and Hyper-V server.

See “Virtual machine discovery in Microsoft Hyper-V ” on page 185.

See “Storage mapping discovery in Microsoft Hyper-V” on page 186.

Virtual machine discovery in Microsoft Hyper-VVeritas Operations Manager lets you discover information about Hyper-V virtualmachines. For example, name of the virtual machine, allocated memory, CPU,state, and the storage exported (virtual hard disks and pass through disks) fromHyper-V server to Hyper-V guest. Veritas Operations Manager discovers all virtual

185Discovering the server and storage virtualization environmentAbout Microsoft Hyper-V virtualization discovery

machines including the virtual machines without the guest operating systeminstalled.

Agent and agentless discoveries of Hyper-V virtual machines are supported.However, for the agentless method, the discovered information is limited. Todiscover more information about the configured virtual machines, agent discoverymethod should be used. It provides detailed information about the virtualmachines.

Virtual machine discovery prerequisites are listed below:

■ VRTSsfmhpackage should be installed on the Hyper-V server (parent partition).

■ Hyper-V role should be enabled.

■ Windows Management Instrumentation (WMI) service should be running.

Limitation of virtual machine discovery is listed below:

■ Hyper-V discovery is not supported on agentless Hyper-V Server (parentpartition) to which the Hyper-V virtual machines are associated.


Storage mapping discovery in Microsoft Hyper-VVeritas Operations Manager discovers the storage provisioned to the guests fromthe host's local storage, or storage area network (SAN). The Hyper-V guest (withor without VRTSsfmh package), when added to Veritas Operations ManagerManagement Server domain, provides storage mapping discovery. These detailsare displayed on the StorageMapping tab on Veritas Operations Manager console.

Additional storage attributes are also displayed on the page. For example, size,type of the storage (VHD or passthrough disk), and the storage container (volumeon the host where virtual storage is provisioned). The storage device handles onthe guest will be mapped to the corresponding VHD or passthrough diskprovisioned from host. Veritas Operations Manager also discovers the snapshotdisks provisioned to the VMS.

Storage mapping discovery prerequisites are listed below:

■ The Hyper-V server must be running Microsoft Windows 2008 R2, or lateroperating system.

■ Windows Management Instrumentation (WMI) should be running on the guest.

Storage mapping discovery limitation is listed below:

■ Storage correlation is not supported for Linux guests.


Discovering the server and storage virtualization environmentAbout Microsoft Hyper-V virtualization discovery

186

About Kernel-based Virtual Machine (KVM)virtualizationdiscovery inVeritasOperationsManager

Kernel-based Virtual Machine (KVM) is a full virtualization solution for Linux onx86 hardware containing virtualization extensions (Intel VT or AMD-V). VeritasOperations Manager discovers KVM virtual machines on the Linux host if theKVM modules are installed, and configured. Veritas Operations Manager discoversbasic information about only running virtual machines. For example, virtualmachine name, CPU, and so on. Veritas Operations Manager usesvirsh commandsto discover KVM-related information.

Kernel-based Virtual Machine (KVM) discovery pre-requisites are as follows:

■ VRTSsfmh package must be present on the Linux host.

■ KVM modules must be installed and configured.

Kernel-based Virtual Machine (KVM) discovery limitations are as follows:

■ Veritas Operations Manager discovers only running virtual machines.

■ Exported storage discovery, and storage correlation is not supported.

See “About the Symantec Performance Value Unit for kernel-based virtualmachines” on page 322.

About the reports related to virtualization in VeritasOperations Manager

In Veritas Operations Manager, you can generate the following reports that displaythe details of the virtualization environment that Veritas Operations Managerdiscovers:

Displays the details of all virtual machinesin the datacenter that Veritas OperationsManager discovers.

All Virtual Machines report

Displays the details of all virtualizationservers in the datacenter that VeritasOperations Manager discovers.

All Virtualization Servers report

Displays the details of the storage pools inthe datacenter that Veritas OperationsManager discovers.

All Storage Pools report


187Discovering the server and storage virtualization environmentAbout Kernel-based Virtual Machine (KVM) virtualization discovery in Veritas Operations Manager


Viewing the virtual environment summaryThe Virtualization view displays the information on the virtual environment thatVeritas Operations Manager discovers in its datacenter. The Virtualization viewdisplays a bar chart that displays the number of virtual machines and virtualizationservers. Distinct colors represent the virtual machines and the virtualizationservers of different virtualization technologies that Veritas Operations Managersupports. You can click the bar chart to view the details of virtual machines orvirtualization servers.

At the bottom of the Virtualization view, you can view the Virtualization tablethat lists the details of the virtualization servers and virtual machines.

The Virtualization table lists the following details of the virtualization serversand the virtual machines of different virtualization technologies that VeritasOperations Manager supports:

■ Total number of the virtualization servers and the virtual machines.

■ Total number of the virtualization servers and the virtual machines that arefaulted.

■ Total number of the virtualization servers and the virtual machines that areat risk.

■ Total number of the virtualization servers and the virtual machines that arehealthy.

You can click the type of the virtualiztion servers or the virtual machines viewtheir details.

To view the virtual environment summary

◆ In the Veritas Operations Manager console, select Manage>Virtualization.



Viewing virtualization serversIn the VirtualizationServers view, you can view the list of virtualization serversthat Veritas Operations Manager manages. Virtualization servers hosts the virtualmachines.

Discovering the server and storage virtualization environmentViewing the virtual environment summary

188

The Virtualization Servers view lists the following information on thevirtualization servers that Veritas Operations Manager discovers:

■ Name of the virtualization server.

■ State of the virtualization server.

■ Version of the virtualization server's operating system.

■ Version of Storage Foundation or Dynamic Multipathing (DMP) that is installedon the virtualization server.

■ Total memory of the virtualization server.

■ Number of CPUs of the virtualization server.

■ Name of the cluster this virtualization server is a part of.

■ Configuration type for the virtualization server.

■ Type of virtualization server. For example, LDOM Server, Hyper-V Server,VMware ESX Server, KVM Server, and Global Zone.

■ Name of the virtualization manager for the virtualization server.

■ Version of the cluster that is associated with the virtualization server.

■ Name of the clustering technology.

■ Indicates if Veritas Volume Replicator is enabled.

■ Version of theVRTSsfmhpackage, which is installed on the virtualization server.

■ Family of the operating system of the virtualization server. For example, AIX,Solaris, VMware, and Red Hat Enterprise Linux.

■ Architecture of the operating system of the virtualization server. For example,x64, x86_64, and SPARC.

■ Total unallocated memory of the host.

■ The time zone to which the host belongs. For example, IST, and UTC.

■ The GMT offset for the time zone to which the host belongs.

■ The locale of the host. For example, EN_US.

■ The name of the business entity this host belongs to.

You can filter the Virtualization Servers view based on the following:

■ State

■ Platform

■ Virtualization Type

189Discovering the server and storage virtualization environmentViewing virtualization servers

■ Configuration Type

To view the virtualization servers in Veritas Operations Manager

◆ In the Veritas Operations Manager console, select Manage > VirtualizationServers.


Viewing the virtual machinesIn the Virtual Machines view, you can view the list of virtual machines that areconfigured on virtualization servers in Veritas Operations Manager.

The Virtual Machines view displays the following information on the virtualmachines:

■ Host name of the virtual machine.

■ Name of the virtual machine.

■ State of the virtual machine.

■ Platform of the virtual machine.

■ Version of the virtual machine's operating system.

■ Version of Storage Foundation or Dynamic Multipathing (DMP) that is installedin the virtual machine.

■ Memory that the virtual machine uses.

■ Number of CPUs that are associated with the virtual machine.

■ Name of the cluster that is associated with the virtual machine.

■ Name of the virtualization server on which the virtual machine is configured.

■ Configuration type of the virtual machine.

■ Server type of the virtual machine. For example, VMware Virtual Machine.

■ Version of the cluster that is associated with the virtual machine.

■ Cluster technology of the cluster that is associated with the virtual machine.

■ Version of the VRTSsfmh package, which is installed on the virtual machine.

■ Family of the operating system of the virtual machine.

■ Architecture of the operating system of the virtual machine.

■ Current state of the virtual machine.

■ Type of the virtual machine.

Discovering the server and storage virtualization environmentViewing the virtual machines

190

■ The name of the business entity this virtual machine belongs to.

■ The time zone to which the host belongs. For example, IST, and UTC.

■ The locale of the host. For example, EN_US.

Also, you can search for the virtual machines based on the following the VirtualMachines view:

■ Name

■ State

■ Architecture

■ Platform

■ OS Version

■ SF Version

■ Cluster version

■ Family

To view the virtual machines in Veritas Operations Manager

◆ In the Veritas Operations Manager console, select Manage>VirtualMachines.


See “Viewing the virtual environment summary” on page 188.

191Discovering the server and storage virtualization environmentViewing the virtual machines

Discovering the server and storage virtualization environmentViewing the virtual machines

192

Downloading StorageFoundation and StorageFoundation and HighAvailability patches usingSymantec OperationsReadiness Tools


■ About updating the patch information on Management Server

■ Viewing the patches that are available on SORT for a host

■ Viewing the details of a patch on the SORT Web site

■ Updating the patch information automatically using Management Server

■ Updating the patch information automatically using a proxy server

■ Updating the patch information manually on Management Server

9Chapter

Aboutupdating thepatch informationonManagementServer

To generate the correct patch report for the Storage Foundation and HighAvailability products that are installed on the managed hosts, Veritas OperationsManager requires the latest information on the patches for these products.Symantec updates the latest information on the patches on the SymantecOperations Readiness Tools (SORT) Web site as a script file. Management Serverrequires HTTPS connectivity with the SORT server for downloading thisinformation.

The Veritas Operations Manager console provides you with various methods toupdate the patch information script files from the SORT Web site. You can useany one of the following methods to update the patch information on ManagementServer:

■ Configure Management Server to update the patch information automaticallywhen Management Server is continuously connected to the Internet

■ Set up a proxy server to update the patch information automatically whenManagement Server is not connected to the Internet

■ Download a script file manually from Management Server when ManagementServer is not continuously connected to the Internet, or you cannot set up aproxy server. You must run the file on a Windows system that is connected tothe Internet to extract a text file that contains the latest information on thepatches, and upload the extracted text file to Management Server.

The automatic update of the patch information on Management Server occurs asper a schedule that you set. By default, the patch information is updated onManagement Server every Sunday.

See “About updating the price tier information on Management Server” on page 325.

See “Updating the patch information manually on Management Server” on page 197.

Viewing the patches that are available on SORT for ahost

Veritas Operations Manager Management Server connects to Symantec OperationsReadiness Tools (SORT) to retrieve and display the information on the patchesthat Symantec has released.You can download these patches and deploy them inthe datacenter.

In the Veritas Operations Manager console, you can view the patches that areavailable for a host in the Available Patches tab.

Downloading Storage Foundation and Storage Foundation and High Availability patches using Symantec OperationsReadiness ToolsAbout updating the patch information on Management Server

194

In the Available Patches tab, you can view the following details:

■ Release Name: Name of the release.

■ Product: Name of the product for which the patch is available.

■ ReleaseType: Type of the patch release.It can be Patch, Servicepack, Platformrelease, Maintenance pack, Rolling patch, cumulative patch, Point patch,or hot Fix.

■ Size: Size of the patch.

■ Products Applicable: Products for which you can apply the patch.

■ Release Date: The date and time at which the patch is released.

■ Criticality: Whether the patch is critical, recommended, or optional.

■ Requires Application Downtime: Whether the patch requires applicationdowntime or application restart. Applications may include VOM, SF, VCS orUser Applications

■ Has Kernel Component: Whether the patch has a kernel component.

■ May require system reboot : Whether you need to restart the host afterinstalling the patch.

■ # of Customer Downloads: Total Number of downloads by customers.

■ Obsolete: Whether the patch is obsolete.

In the Product column, you can click Details to view the details of the patch onthe SORT Website. In the Release name column, you can download a patch.

To view the patches available for a host

1 In the Veritas Operations Manager console, select Manage > Hosts.

2 In the table that lists the hosts, click the name of the host to view its details.

3 In the details view of the host, click the Available Patches tab to view thepatches that are available for the host.

See “Viewing the details of a patch on the SORT Web site” on page 196.

See “Updating the patch information automatically using Management Server”on page 196.

See “Updating the patch information automatically using a proxy server”on page 197.


195Downloading Storage Foundation and Storage Foundation and High Availability patches using Symantec OperationsReadiness Tools

Viewing the patches that are available on SORT for a host

Viewing the details of a patch on the SORT Web siteIn the Veritas Operations Manager console, you can click the Details icon to viewthe details of a patch on the Symantec Operations Readiness Tools (SORT) Website.

To view the details of a patch on the SORT Web site

1 In the details view of a host, click the Available Patches tab to view thepatches that are available for the host in the Patches table.

2 In the Products column of the table, click the Details icon next to the nameof a product.

3 On the SORT Web site that is opened in a separate Web browser window,review the details of the patch.

See “Viewing the patches that are available on SORT for a host” on page 194.




Updating the patch information automatically usingManagement Server

You can configure Management Server to connect to the SORT Web site to updatethe patch information automatically when Management Server is continuouslyconnected to the Internet. Also, you can set a schedule for the automatic updateof the patch information on Management Server. By default, the automatic updateof the patch information occurs every Sunday at 00.00 hours.

To update the patch information automatically using Management Server

1 In Veritas Operations Manager console, select Settings > Download.

2 In Download Schedule, select the Patch Information check box and specifythe day and the time when you want to update the patch information.

3 Click Save Settings.


See “About updating the patch information on Management Server” on page 194.

Downloading Storage Foundation and Storage Foundation and High Availability patches using Symantec OperationsReadiness ToolsViewing the details of a patch on the SORT Web site

196

Updating the patch information automatically usinga proxy server

You can configure Management Server to update the patch informationautomatically when Management Server is continuously connected to the Internet.When Management is not connected to the Internet, you can use a proxy serverto connect to the SORT Web site and update the patch information automatically.Also, you can set a schedule for the automatic update of patch information onManagement Server. By default, the automatic update of the patch informationoccurs every Sunday at 00.00 hours.

To update the patch information automatically using a proxy server

1 In Veritas Operations Manager, select Settings > Download.

2 Enter the information in the fields as follows:

■ In the ProxyServer field, enter the name or IP address of the proxy server.

■ In the ProxyServerPort field, enter the port number of the proxy server.

■ In the Proxy User field, enter the user name that you use to access theproxy sever.

■ In the Proxy Password field, enter the password that you use to accessthe proxy sever.

3 In Download Schedule, select the Patch Information check box and specifythe day and the time when you want to update the patch information.




Updating the patch information manually onManagement Server

You can update the patch information manually when Management Server is notconnected to the Internet, or you cannot set up a proxy server to access the SORTWeb site. To do this, you must download thevos.vbs script file from ManagementServer and run it on a Windows system that has Internet connectivity to extractthe text file that contains the latest information on the patches. You must copythis text file to the system where Management Server is running and manuallyupload the text file.

197Downloading Storage Foundation and Storage Foundation and High Availability patches using Symantec OperationsReadiness Tools

Updating the patch information automatically using a proxy server

You can navigate to the Monitor > Tasks to view the status of the patch uploadtask.

Note: You must use a Windows system to perform this operation.

To update the patch information manually on Management Server

1 In the Veritas Operations Manager console, select Settings > Download.

2 In the ManualDownloadSettings section, click PatchInformationDownload.

3 Click Download to download the vos.vbs script.

4 Copy the vos.vbs file to a Windows system that has Internet connectivity.

5 Run the following command to extract the text file that contains theinformation on the patches:

cscript /NoLogo vos.vbs

Alternatively, you can double-click the script file to extract the text file. Thevos.txt file is generated in the folder where you have kept the vos.vbs scriptfile.

6 Copy the text file to the system where Management Server is running.

7 In the console, under Patch Information Download, click Browse to selectthe vos.txt file.

8 Click Upload.


See “Viewing the details of a patch on the SORT Web site” on page 196.

Downloading Storage Foundation and Storage Foundation and High Availability patches using Symantec OperationsReadiness ToolsUpdating the patch information manually on Management Server

198

Monitoring performance


■ About performance metering statistics

■ About metered resources

■ About space estimation for data logs

■ Enable performance metering for a VMware vCenter server

■ Disable performance metering for a VMware vCenter server

■ Enable performance metering for a VMware ESX server

■ Disable performance metering for a VMware ESX server

■ Enable performance metering for a host

■ Disable performance metering for a host

■ About Veritas Operations Manager performance graphs

■ Viewing the performance graphs for a volume

■ Viewing the performance graphs for a host

■ Viewing the performance graphs for a disk

■ Viewing the performance graphs for an initiator

■ Viewing the performance graph for a file system

■ Viewing the performance graphs for a multipathing path

■ Viewing the performance graphs for an enclosure

10Chapter

About performance metering statisticsHistorical performance data of various resources is collected in a fixed-size binaryfile. The older data is overwritten as new data arrives in a circular round robinarray. The number of metrics, frequency of data insertion, number of objects, andthe roll-up databases affect the size of binary file. The higher resolution data iscompressed to a lower resolution data. For example, data is collected every5-minutes for the last 24 hours for daily performance analysis. For monthlyperformance analysis, average of the 5-minutes data for every two hours is used.For the yearly performance log, average of the 5-minutes data for every 24 hoursis used.

See “About metered resources” on page 200.

See “About space estimation for data logs” on page 203.

About metered resourcesTable 10-1 lists the resources that are metered and the difference in the logconfigurations of prior versions of Veritas Operations Manager and VeritasOperations Manager 5.0 and onwards. For example, to understand the percentageof CPU utilization of a system, the metering is done every 5 minutes for 24 hoursin Veritas Operations Manager 5.0. Whereas the metering in the prior versionsof Veritas Operations Manager was 5 minutes for one week.

The data that is collected during metering is used to generate the performancecharts of the resource.

Table 10-1 Log configurations

Log configurationin version 5.0 andonwards

Log configurationin the priorversions

Chart nameResource

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

5 minutes / 1 weekAvailable Memory (inKB)

Average CPU Load

Host

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Not availableCPU Utilization (inpercentage)

Swap in Rate (inKB/sec)

Used Swap (in KB)

Host

Monitoring performanceAbout performance metering statistics

200

Table 10-1 Log configurations (continued)



Chart nameResource

6 hours / 1 month

1 day / 1 year

6 hours / 1 month

1 day / 1 year

Size/Used (in KB)File system

1 minute / 6 hours

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

1 minute / 6 hours

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Average Read/WriteLatency

Bytes Read/Written(in bytes)

VxVM Volume

1 minutes / 6 hours

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

1 minutes / 6 hours

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year



VxVM Disk

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

1 minute / 6 hours

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year



Read/Write Errors

Read/Write QueueLengths

Host Initiator

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Not availableAverage Read/WriteLatency for Host

Average BytesRead/Written forHost (in bytes)

Host Enclosure

5 minutes / 1 day

2 hours / 1 month

Not availableAverage Read/WriteLatency


Host Path

201Monitoring performanceAbout metered resources




Chart nameResource

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Not availableAvailable Memory (in KB)

CPU Utilization (inpercentage)

Swap in Rate (inKB/sec)

Used Swap (in KB)

VMware ESX serverand Virtual Machine

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year



VMware ESX serverInitiator

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year



VMware ESX serverEnclosure

5 minutes / 1 day

2 hours / 1 month

1 day / 1 year



VMware ESX serverPath

30 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Not availableIO Operations persecond

IO Throughput persecond

Storage array - Port

30 minutes / 1 day

2 hours / 1 month

1 day / 1 year

Not availableIO Operations persecond

IO Throughput persecond

Storage array -Controller

Monitoring performanceAbout metered resources

202




Chart nameResource

30 minutes / 1 day

2 hours / 1 month

1 day / 1 year


Average BytesRead/Written forHost (in bytes)

IO Operations persecond

Storage array -Enclosure

Note: Veritas Operations Manager Control Host Add-on 5.0 is required to enableperformance metering for the VMware ESX server and Virtual Machine. StorageInsight Add-on 5.0 is required to enable performance metering for storage arrayport, controller and enclosure.

See “About performance metering statistics” on page 200.

About space estimation for data logsTable 10-2 describes the space estimation for data logs for the various resources.For estimation purposes, the data in the Number of resources column is accordingto the standard environment. The metrics collected column represents the numberof metrics collected for each resource. For example, in case of DMP paths, thetotal number of metrics collected is four: bytes read, bytes written, read average,and write average.

Data logs for host, DMP (path, controller, enclosure), volume, disk and file systemare stored on the managed host. The data logs for VMware host, VxDMP (path,controller, enclosure) are stored on the Control Host. For storage array (port,controller, enclosure), data log for 1 day is stored on the discovery host, where asall the other logs are stored on Management Server.

203Monitoring performanceAbout space estimation for data logs

Table 10-2 Space estimation for data logs

Size in KBfor asingleobject

Size in KBDurationofcollection

Interval ofcollection

Metricscollected

Numberofresources

Name ofresource

24241 day5 minutes51Host,VMwareESX server,and VirtualMachine

29291 month2 hours51

30301 year1 day51

19189671 day5 minutes41000Multipathingpaths

24234771 month2 hours41000

431711 day5 minutes94Initiator


1074281 year1 day184

19761 day5 minutes44Enclosure

281 month2 hours84

461901 year1 day84

1414231 day5 minutes3100File system

1817841 year1 day3100

2323486 hours1 minute4100VxVMVolume

1918981 day5 minutes4100


2423791 year1 day4100

2323486 hours1 minute4100VxVM Disk

1918981 day5 minutes4100


2323791 year1 day4100

Monitoring performanceAbout space estimation for data logs

204

Table 10-2 Space estimation for data logs (continued)

Size in KBfor asingleobject

Size in KBDurationofcollection

Interval ofcollection

Metricscollected

Numberofresources

Name ofresource

93041 day30 minutes232Storagearray -Array port 237511 month2 hours432

247611 year1 day432

9761 day30 minutes28Storagearray -Adapter 231881 month2 hours48

241901 year1 day48

551 day30 minutes11Storagearray-Enclosure 12121 month2 hours21

12121 year1 day21

Note: If Veritas Operations Manager is configured in high availability environment,storage array port, controller, and enclosure logs are saved on a shared disk. IfControl Host Add-on 5.0 is installed on Management Server, then, VMware ESXserver and virtual machines logs are saved on a shared disk.


Enable performance metering for a VMware vCenterserver

Use this option to enable performance metering for a VMware vCenter server.

Note: To perform this operation you must have Control Host Add-on 5.0.

To enable performance metering for a VMware vCenter server

1 In the Veritas Operations Manager console, click Settings > Virtualization.

2 In the Virtualization Management view, do one of the following:

205Monitoring performanceEnable performance metering for a VMware vCenter server

■ Click a VMware vCenter server and on the top of the VirtualizationManagement table, click Actions > Configure performance metering.

■ Right-click the VMware vCenter server to display the shortcut menu,select Configure performance metering.

3 In the Configure performance metering wizard panel, specify the requiredinformation, and click Finish.

See “Configure performance metering panel options” on page 206.

See “Disable performance metering for a VMware vCenter server” on page 207.


Configure performance metering panel optionsUse this wizard panel to specify the details when you configure performancemetering for a resource.

Table 10-3 Configure performance metering panel options

DescriptionField

Select this check box to enable performancemetering for a resource.

Clear the check box to disable performancemetering for a resource.

Enable Performance metering

Enter an interval period for which you wantthe performance data to be collected.

Interval period should be between 5 minutesand 1440 minutes. The interval periodshould be in the multiples of five.

Note: Selection of the interval period is notapplicable for hosts and VMware ESXservers.

Interval

See “Enable performance metering for a VMware vCenter server” on page 205.

See “Disable performance metering for a VMware vCenter server” on page 207.

See “Enable performance metering for a VMware ESX server” on page 207.

See “Disable performance metering for a VMware ESX server” on page 208.

See “Enable performance metering for a host” on page 208.

See “Disable performance metering for a host” on page 209.

Monitoring performanceEnable performance metering for a VMware vCenter server

206

Disable performancemetering for a VMware vCenterserver

Use this option to disable performance metering for a VMware vCenter server.

To disable performance metering for a VMware vCenter server

1 In the Veritas Operations Manager console, click Settings > Virtualization.

2 In the Virtualization Management view, do one of the following:

■ Click a VMware vCenter server and on the top of the VirtualizationManagement table, click Actions > Configure performance metering.

■ Right-click the VMware vCenter server to display the shortcut menu,select Configure performance metering.



See “Enable performance metering for a VMware vCenter server” on page 205.


Enable performance metering for a VMware ESXserver

Use this option to enable performance metering for a VMware ESX server.

Note: To perform this operation you must have Control Host Add-on 5.0.

To enable performance metering for a VMware ESX server

1 In the Veritas Operations Manager console, click Manage > VirtualizationServers.

2 In the Virtualization Servers view, do one of the following:

■ Select the check box for a VMware ESX server and on the top of theVirtualization Servers table, click Actions > Configure performancemetering.

207Monitoring performanceDisable performance metering for a VMware vCenter server

■ Right-click a VMware ESX server to display the shortcut menu, selectConfigure performance metering.



See “Disable performance metering for a VMware ESX server” on page 208.


Disable performance metering for a VMware ESXserver

Use this option to disable performance metering for a VMware ESX server.

To disable performance metering for a VMware ESX server

1 In the Veritas Operations Manager console, click Manage > VirtualizationServers.

2 In the Virtualization Servers view, do one of the following:

■ Click a VMwareESX server and on the top of the Virtualization Serverstable, click Actions > Configure performance metering.

■ Right-click the VMware ESX server to display the shortcut menu, selectConfigure performance metering.



See “Enable performance metering for a VMware ESX server” on page 207.


Enable performance metering for a hostUse this option to enable performance metering for a host.

Note: You cannot enable performance metering if the host is on the Windowsplatform and if the configuration type of the host is agentless or no-configuration.Control Host Add-on 5.0 is required to enable performance metering for a host.

Monitoring performanceDisable performance metering for a VMware ESX server

208

To enable performance metering for a host


2 In the Hosts view, do one of the following:

■ Select the check box for a host and on the top of the Hosts table, clickActions > Configure performance metering.

■ Right-click a host to display the shortcut menu, select Configureperformance metering.



See “Disable performance metering for a host” on page 209.


Disable performance metering for a hostUse this option to disable performance metering for a host.

To disable performance metering for a host


2 In the Hosts view, do one of the following:

■ Select the check box for a host and on the top of the Hosts table, clickActions > Configure performance metering.

■ Right-click a host to display the shortcut menu, select Configureperformance metering.



See “Enable performance metering for a host” on page 208.


About Veritas Operations Manager performancegraphs

Install Control Host Add-on 5.0 on a managed host to view the performance ofthe following objects by using interactive graphs:

209Monitoring performanceDisable performance metering for a host

■ Host

■ Volume

■ File system

■ Disk

■ Multipathing path

■ Initiators

■ Enclosure

■ Array port

■ Adapter

You can select an object and view graphs for multiple performance parameters.These graphs are line charts. The lines that represent the performance parametersare rendered in different colors. The X-axis represents the time duration and theY-axis represents the performance parameter. Linear trend line is displayed forevery performance parameter. The linear trend line is plotted by fitting a line onthe historical data. Linear trend is not available for live charts.

Performance charts for volume and disk are available if they are managed byVxVM. Performance charts for multipathing path, initiator, and enclosure areavailable only if they are managed by physical hosts running DMP or VMwareESX servers running VxDMP.

On the performance graph, you can perform the following actions:

■ Specify the duration for which you want to view the performance of the objectthat you have selected.

■ Move the mouse pointer over the line chart to view the performance data. Atool tip is displayed corresponding to the positon of the mouse pointer on thegraph.

■ Click the desired legend to temporarily hide or display the line graph.

See “Pre-requisite commands to view performance graphs for a resource”on page 211.

See “Viewing the performance graphs for a host” on page 213.

See “Viewing the performance graphs for a volume” on page 211.

See “Viewing the performance graph for a file system” on page 216.

See “Viewing the performance graphs for a disk” on page 214.

See “Viewing the performance graphs for a multipathing path” on page 217.

See “Viewing the performance graphs for an initiator” on page 215.

Monitoring performanceAbout Veritas Operations Manager performance graphs

210

See “Viewing the performance graphs for an enclosure” on page 219.

Pre-requisite commands to view performance graphs for a resourceTable 10-4 lists the pre-requisite commands that are required to view performancegraphs for a host.

Table 10-4 Pre-requisite commands for a host

Pre-requisite commandsChart name

Solaris/Linux: vmstat

AIX: svmon

HP-UX: swapinfo

Available Memory

VMware Guest/ESX: SWPR/S

Solaris: sar

AIX: vmstat

HPUX: vmstat

Linux: sar

Swap in Rate

Solaris/AIX: swap

Linux: cat /proc/swaps

HP-UX: swapinfo

VMware: vSphere APIs

Used Swap

vxlistSize/Used

Users having Host\CIM\CIM Interactionprivileges on a VMware vCenter servercan view the performance graphs for enclosure, multipathing path, and initiatorfor an ESX server running VxDMP.

Users having Host\Configuration\Change Settings privileges on a vCenterserver can view the Available Memory, CPU Utilization, Swap in Rate, and theUsed Swap performance graphs for VMware ESX servers and virtual machines.

See “About Veritas Operations Manager performance graphs” on page 209.

Viewing the performance graphs for a volumeIn Veritas Operations Manager, you can view the performance of a volume in aninteractive graph.

211Monitoring performanceViewing the performance graphs for a volume

Note: You can view the performance graphs only for a volume of type VxVM andif the volume belongs to a disk group.

You can specify one of the following durations for which the performance graphscan be rendered:

■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

You can view the following performance graphs for a volume:

■ The Average Read/Write Latency graph that displays the average read andwrite latency for the volume and the trend for the specified duration.

■ The Bytes Read/Written graph that displays the number of bytes read andwritten on the volume and the trend for the specified duration.

To view the performance graphs for a volume


2 In the Hosts view, click the host.

3 Click the Volumes tab.

4 In the Volumes view, do one of the following:

■ Click the name of the volume. Click the Performance tab.

■ Select the check box for the volume and on the top of the Volumes table,click Actions > Performance.

■ Right-click the volume to display the shortcut menu, select Performance.

5 On the performance graph, in the Duration drop-down list, click the desiredtime duration to change the view of the performance graph.

6 Click the desired legend to temporarily hide (or display) the line graph.


Monitoring performanceViewing the performance graphs for a volume

212

Viewing the performance graphs for a hostIn Veritas Operations Manager, you can view the performance of a host in aninteractive graph.

Note:You cannot view the performance graphs for a host on the Windows platform.


■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

You can view the following performance graphs for a host:

■ The Available Memory graph displays the free memory in the selected hostand the trend for the specified duration.

■ The Average CPU Load graph displays the CPU queue length on the selectedhost and the trend for the specified duration.

Note: The Average CPU Load graph graph is not displayed for virtualizationserver and the virtual machine.

■ The CPU Utilization graph displays the CPU utilization (in percentage) on theselected host and the trend for the specified duration.

■ The Swap in Rate graph displays the swap in rate (in KB/second) for the selectedhost and the trend for the specified duration

■ The Used Swap graph displays the swap that is used by the selected host andthe trend for the specified duration.

To view the performance graphs for a host


■ For Hosts: Select Manage > Hosts.

■ For Virtualization Servers: Select Manage > Virtualization Servers.

213Monitoring performanceViewing the performance graphs for a host

■ For Virtual Machines: Select Manage > Virtual Machines.

2 In the Hosts, VirtualizationServer or VirtualMachines view, do one of thefollowing:

■ Click the name of the host. Click the Performance tab.

■ Select the check box for the host and on the top of the Hosts table, clickActions > Performance.

■ Right-click the host to display the shortcut menu, select Performance.

3 On the performance graphs, in the Duration drop-down list, click the desiredtime duration to change the view of the performance graphs.



Viewing the performance graphs for a diskIn Veritas Operations Manager, you can view the performance of a disk in aninteractive graph.

Note: You can view the performance graphs only for a disk that VxVM managesand if the disk belongs to a disk group.


■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

You can view the following performance graphs for a disk:

■ The Average Read/Write Latency graph displays the average read and writelatency for the disk and the trend for the specified duration.

■ The Bytes Read/Written graph displays the number of bytes read and written(in bytes) on the disk and the trend for the specified duration.

Monitoring performanceViewing the performance graphs for a disk

214

To view the performance graphs for a disk



3 Click the Disks tab.

4 In the Disks view, do one of the following:

■ Click the name of the disk. Click the Performance tab.

■ Select the check box for the disk and on the top of the Disks table, clickActions > Performance.

■ Right-click the disk to display the shortcut menu, select Performance.

5 On the performance graph, in the Duration drop-down list, click the desiredtime duration to change the view of the performance graph.


7 Click the ellipses to select another disk.

Note: The ellipses are displayed only if the disk is a shared disk.


Viewing the performance graphs for an initiatorIn Veritas Operations Manager, you can view the performance of an initiator inan interactive graph.

Note: You can view the performance graphs for an initiator only if the initiatoris managed by DMP or VxDMP.


■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

215Monitoring performanceViewing the performance graphs for an initiator

You can view the following performance graphs for an initiator:

■ The Average Read/Write Latency graph displays the average read and writelatency for the initiator and the trend for the specified duration.

■ The Bytes Read/Written graph displays the number of bytes read and written(in bytes) on the initiator and the trend for the specified duration.

■ The Read/Write Errors graph displays the number of read and write errors onthe initiator and the trend for the specified duration.

■ The Read/Write Queue Lengths graph displays the length of read and writequeue on the initiator and the trend for the specified duration.

Note: Read/Write Errors and Read/Write Queue Lengths graphs for an initiatorare displayed only for Storage Foundation version 5.1 and above. These chartsare available only for non-virtualized hosts.

To view the performance graphs for an initiator


■ For Hosts: Select Manage > Hosts.

■ For Virtualization Server: Select Manage > Virtualization Servers.

2 In the Hosts or Virtualizations Servers view, click the host.

3 Click the Adapters tab.

4 In the Adapters view, in the Initiators table, do one of the following:

■ Click the name of the initiator. Click the Performance tab.

■ Select the check box for the initiator and on the top of the Initiators table,click Actions > Performance.

■ Right-click the initiator to display the shortcut menu, select Performance.

5 On the performance graphs, in the Duration drop-down list, click the desiredtime duration to change the view of the performance graph.



Viewing the performance graph for a file systemIn Veritas Operations Manager, you can view the performance of a file system inan interactive graph.

Monitoring performanceViewing the performance graph for a file system

216

You can specify one of the following durations for which the performance graphcan be rendered:

■ One month

■ One year

You can view the following performance graph for a file system:

■ The Size/Used graph displays the size and the used space of the file systemand the trend for the specified duration.

To view the performance graph for a file system



3 Click the File Systems tab.

4 In the File Systems view, do one of the following:

■ Click the Mount Point. Click the Performance tab.

■ Select the check box for the Mount Point and on the top of the FileSystemstable, click Actions > Performance.

■ Right-click the Mount Point to display the shortcut menu, selectPerformance.



7 Click the ellipses to select another file system.

Note:The ellipses are displayed only if the file system is a shared file system.


Viewing the performance graphs for a multipathingpath

In Veritas Operations Manager, you can view the performance of a multipathingpath in an interactive graph.

Note: You can view the performance graphs for a multipathing path only if thepath is managed by DMP or VxDMP.

217Monitoring performanceViewing the performance graphs for a multipathing path

You can specify one of the following durations for which the performance graphcan be rendered:

■ Six hours

■ 24 hours

■ One week

■ One month

■ Live

You can view the following performance graphs for a multipathing path:

■ The Average Read/Write Latency graph displays the average read and writelatency of the selected multipathing path and the trend for the specifiedduration.

■ The Bytes Read/Written graph displays the number of bytes read and written(in bytes) in the selected multipathing path and the trend for the specifiedduration.

To view the performance graph for a multipathing path


■ For Host: Select Manage > Hosts.

■ For Virtualization Server: Select Manage > Virtualization Servers.

2 In the Hosts or Virtualization Servers view, click the host.

3 Click the Disks tab.

4 In the Disks view, click the disk.

5 Click the Paths tab.

6 In the Paths view, click the desired path.

7 On top of the Paths table, do one of the following:

■ Click Actions > Performance.

■ Right click the path to display the shortcut menu, click Performance.




Monitoring performanceViewing the performance graphs for a multipathing path

218

Viewing the performance graphs for an enclosureIn Veritas Operations Manager, you can view the performance of an enclosure inan interactive graph.


■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

You can view the following performance graphs for an enclosure:

■ The Average Read/Write Latency for Host graph displays the average readand write latency and the trend for the selected host for the specified duration.

■ The Average Bytes Read/ Written for Host graph displays the bytes read andwritten (in KB) and the trend for the selected host for the specified duration.

Note:You can view the performance graphs for an enclosure only if the enclosureis managed by DMP or VxDMP.

If Veritas Operations Manager Storage Insight Add-on for Deep Array Discoveryand Mapping version 5.0 is installed, you can view the following performancegraph for an enclosure:

■ The IO Operations per second graph displays the number of IO operations persecond and the linear trend for the selected host for the specified duration.

Note: This graph is displayed only for EMC Symmetrix, EMC Clariion, NetAppand IBM XIV arrays.

IO Operations per second performance graph cannot be rendered for Live data.

To view the performance graphs for an enclosure

1 In the Veritas Operations Manager console, Select Manage > Enclosures.

2 In the Enclosures view, do one of the following:

■ Click the name of the enclosure. Click the Performance tab.

219Monitoring performanceViewing the performance graphs for an enclosure

■ Select the check box for the enclosure and on the top of the Enclosurestable, click Actions > Performance.

■ Right-click the enclosure to display the shortcut menu, selectPerformance.

3 On the performance graphs, in the Duration drop-down list, click the desiredtime duration to change the view of the performance graphs.


5 Click the ellipses to select a host.


Monitoring performanceViewing the performance graphs for an enclosure

220

Managing security groups


■ About the security model for Veritas Operations Manager

■ About predefined roles in Veritas Operations Manager

■ Viewing security group details

■ Adding security groups to the Veritas Operations Manager domain

■ Modifying security groups in the Veritas Operations Manager domain

■ Removing security groups from Veritas Operations Manager

About the security model for Veritas OperationsManager

The security model specifies and enforces security policies. In Veritas OperationsManager, the security model is based on the mapping between security groupsand roles.

The security model uses the following entities:

■ Security group

■ Role

■ Authentication domain

Veritas Operations Manager lets you combine a role and a scope to specify apredefined role. The following table explains the combination of roles and scopesand the resultant predefined roles:

11Chapter

Predefined roleRole and scope

Domain AdminAdmin and Domain (All Business Entities)

AdminAdmin and Selected Business Entities

Domain OperatorOperator and Domain (All BusinessEntities)

OperatorOperator and Selected Business Entities

GuestNone

When a user logs in, Veritas Operations Manager uses an authentication brokerto authenticate the user across an authentication domain. If the user isauthenticated, Veritas Operations Manager uses the authentication domain nameand domain type to determine the security group that can be associated with theuser. The security group is mapped to a predefined role.

See “About predefined roles in Veritas Operations Manager” on page 222.

See “Viewing security group details” on page 228.

Aboutpredefined roles inVeritasOperationsManagerVeritas Operations Manager lets you combine a role and a scope to specify apredefined role. The following table explains the combination of roles and scopesand the resultant predefined roles:

Table 11-1 Summary of predefined roles in Veritas Operations Manager


Domain AdminAdmin and Domain (Entire Domain)


Domain OperatorOperator and Domain (Entire Domain)


GuestGuest

In the New Security Group panel, you must specify a role and a scope to assigna predefined role to the security group.

Veritas Operations Manager lets you provide the role that you create with theprivilege to access the views and reports and perform the operations that arerelated to out-of-band storage management. To provide the storage administration

Managing security groupsAbout predefined roles in Veritas Operations Manager

222

privileges, you can use the Allow access to storage views and operations checkbox on the New Security Group wizard panel.

If you do not select the Allow access to storage views and operations check box,the administrators or the operators with the role that you create can onlyadminister the servers. They cannot access the views and reports and performthe operations that are related to out-of-band storage management from theservers that they administer.

Table 11-2 table explains the role and the scope that you must select to assign apredefined role to security groups.

Note: You cannot provide any scope to the Guest role. When you select the Guestrole, the panel does not display the Scope options.

223Managing security groupsAbout predefined roles in Veritas Operations Manager

Table 11-2 Veritas Operations Manager predefined roles

DescriptionPredefined roleRole and scope

A user with the Domain Admin rolehas complete access to the systemand can do the following:

■ Access all managed hosts thatare added to ManagementServer.

■ Access the views and reportsand perform the operations thatare related to out-of-bandstorage management.

■ Manage the business entities.

■ Manage the authenticationbrokers .

■ Manage the security groups.

■ Create the users with the Adminrole.

■ Access all Veritas OperationsManager Add-ons.

■ Deploy the packages andpatches.

■ Manage all the hosts.

■ Perform all the configurationsand the operations on all theVCS cluster.

Note: Only the users with theDomain Admin role can createbusiness entities, create securitygroups, and add hosts to thedomain.

Domain AdminAdmin and Domain (EntireDomain)


224

Table 11-2 Veritas Operations Manager predefined roles (continued)


A user with the Admin role hasrestricted access to the managedhosts that are added toManagement server. The Adminrole is mapped to a security groupwith one or more business entities.

An Admin can do the following:

■ Access all objects in a businessentity that is associated with thesecurity group to which theAdmin role is mapped.

■ Perform all operations on theobjects in a business entity thatis associated with the securitygroup to which the Admin roleis mapped.

■ Perform the configurations andthe operations on the VCScluster if the cluster is added tothe business entity as a baseobject.

■ Perform the configurations andthe operations on the servicegroups and the associatedstorage objects if the servicegroup is added to the businessentity as a base object.

An Admin with the privileges toaccess the storage views andoperations can access the views andreports and perform the operationsthat are related to out-of-bandstorage management from theobjects in the application group towhich the Admin role is mapped.

AdminAdmin and SelectedBusiness Entities




A user with the Domain Operatorrole can perform all operations onall the VCS clusters. But, this useris not allowed to make anyconfiguration changes to the VCSclusters.

A Domain Operator with theprivileges to access the storageviews and operations can access theviews and reports and perform theoperations that are related toout-of-band storage managementfrom the VCS clusters in VeritasOperations Manager.

A Domain Operator is provided withthe Guest role on the StorageFoundation objects.

Domain OperatorOperator and Domain(Entire Domain)


226



A user with the Operator role cando the following:

■ Clear the service groups.

■ Make service groups and storageresources online or offline.

■ Temporarily freeze or unfreezeservice groups.

■ Switch the service groups.

■ Autoenable the service groups.

■ Display information onapplication heartbeat for aservice group.

■ Bring the resources online ortake them offline.

■ Run an action on the resources.

■ Refresh the information on theresources.

■ Flush the service groups.

■ Flush the resources.

The operator can perform thesetasks based on the clusters orservice groups that are added to thebusiness entities as base objects.

An Operator with the privileges toaccess the storage views andoperations can access the views andreports and perform the operationsthat are related to out-of-bandstorage management from the VCSclusters in the application group towhich the Operator role is mapped.

An Operator is provided with theGuest role on the StorageFoundation objects.

OperatorOperator and SelectedBusiness Entities

The users with the Guest role haveread-only access. They cannotperform any tasks in VeritasOperations Manager.

GuestGuest


See “About the security model for Veritas Operations Manager” on page 221.

Viewing security group detailsThe Security Settings view displays the details of the security groups in VeritasOperations Manager. By default, the root security group is mapped to the rootauthentication group in the primary authentication broker. The root securitygroup is associated with the Domain Admin role.

The following table describes the information that you can view for each securitygroup:

Name of the security group.Name

Name of the authentication domain that youhave associated with the security group.

Domain Name

The domain type in the authenticationdomain of the security group.

Domain Type

The predefined role that is associated withthe security group.

This column displays the followingpredefined roles based on the Role and theScope that you have specified in the NewSecurity Group wizard panel:

■ Domain Admin

■ Admin

■ Domain Operator

■ Operator

■ Guest

Note: You cannot provide any scope to theGuest role.

Role

Managing security groupsViewing security group details

228

The scope that is provided to the role, whichis part of the security group.

For the Domain Admin and the DomainOperator roles, this field displays the scopeas Entire Domain. For the Operator and theAdmin roles, this field displays the name ofone or more business entities that are usedto limit the scope of the roles.

For the Guest role, this field displays thescope as Entire Domain (Read-only).

Note: Business entities are associated withthe security group only if that security groupis mapped to the Admin or the Operatorroles.

Scope

Displays whether the role that is associatedwith the security group has privileges toaccess the views and reports and performthe operations that are related toout-of-band storage management.

Storage Access

In the Security Groups view, you can do the following:

■ Create new security groups.

■ Modify the existing security groups.

■ Remove the security groups.

To view the details of security groups

1 Select Settings > Security Groups.

2 In the Security Groups view, the details of the security groups in a table.


See “Adding security groups to the Veritas Operations Manager domain”on page 230.

See “Modifying security groups in the Veritas Operations Manager domain”on page 234.

See “Removing security groups from Veritas Operations Manager” on page 236.

229Managing security groupsViewing security group details

Adding security groups to the Veritas OperationsManager domain

The New Security Group wizard panel lets you add a new security group to theVeritas Operations Manager domain.

Veritas Operations Manager lets you combine a role and a scope to specify apredefined role. The following table explains the combination of roles and scopesand the resultant predefined roles:


Domain AdminAdmin and Domain (Entire Domain)


Domain OperatorOperator and Domain (Entire Domain)


GuestGuest

To create a new security group, you must associate an authentication group andan authentication domain with one of the predefined roles in Veritas OperationsManager.

Note: You cannot provide any scope to the Guest role. When you select the Guestrole, the panel does not display the Scope options.

To the Admin and the Operator roles, you can provide the rights to administereither all the business entities or a specific set of business entities present inVeritas Operations Manager.

If you want to use an LDAP domain for users belonging to a specific role, you mustcreate a security group that associates the authentication domain and the role.

Veritas Operations Manager lets you provide the role that you create with theprivilege to access the views and reports and perform the operations that arerelated to out-of-band storage management. To provide the storage administrationprivileges, you can use the Allow access to storage views and operations checkbox on the New Security Group wizard panel.

If you do not select the Allow access to storage views and operations check box,the administrators or the operators with the role that you create can onlyadminister the servers. They cannot access the views and reports and perform

Managing security groupsAdding security groups to the Veritas Operations Manager domain

230

the operations that are related to out-of-band storage management from theservers that they administer.

The privilege to access the storage views and operations is global in nature. Youcannot provide any scope to this privilege. However, you can provide the scopeto the role that has the privilege to access the storage views and operations. Forexample, if you have provided the privilege to access the storage views andoperations to the Admin role with the right to administer the business entityBEhosts_example that is based on hosts, the administrators with this role candelve in to the storage views from the hosts that are part of BEhosts_example.

In Veritas Operations Manager, the Dynamic Multipathing (DMP) maintenanceoperations and the discovery of information on the arrays are directly dependenton the privilege to access the storage views and operations that you have providedto a predefined role.

For more information, refer to theVeritasOperationsManagerManagementServerAdd-ons User's Guide.

The name of the security group that you create must match the name of theauthentication group present in the authentication domain that you use to createit.

Note: Users with the Domain Admin role can access all the business entities inVeritas Operations Manager.

To add security groups to the domain

1 In the Veritas Operations Manager console, select Settings>SecurityGroups.

2 Click Actions >New Security Group.

3 In the New Security Group wizard panel, enter the details and click OK.

See “New Security Group options” on page 231.

4 In the Results panel that confirms the action, click OK.




New Security Group optionsUse this wizard panel to define the attributes for a new security group.

231Managing security groupsAdding security groups to the Veritas Operations Manager domain

Table 11-3 New Security Group panel options

DescriptionField

Name of the security group that you want tocreate.

After you enter the name of the securitygroup, click Check to verify that the nameof the authentication group and the namethat you have specified for the securitygroup are the same. Authentication groupcan be an OS group or aLDAP/Authentication Domain group.

Veritas Operations Manager displays an iconthat indicates that the verification of thename of the security group is in progress. Ifthe authentication group name and thesecurity group name are the same, VeritasOperations Manager displays a green icon.If the authentication group name and thesecurity group name are different, you canview a red icon.

Note: You must ensure that the name of theauthentication group and the security groupare the same.

Name of the security group for NT domainmust include the domain name on which thegroup is configured, and the group name.The security group name must be entered inthe domain name\groupname format.

Example: Machinename\Administrator

Name

Name of the authentication domain that youwant to associate with the security group.

You can choose the domain names from thedrop-down list. The drop-down list containsall the authentication domains that are inthe enabled state.

Domain

Choose any of the following roles that youwant to associate with the security group:

■ Admin■ Operator■ Guest

Role

Managing security groupsAdding security groups to the Veritas Operations Manager domain

232

Table 11-3 New Security Group panel options (continued)

DescriptionField

Select this check box if you want to providethe role that you create with the privilegesto access the views and reports and performthe operations that are related toout-of-band storage management.

If you have not selected this check box, theadministrators or operators with the rolethat you create can only administer theservers. They cannot access the views andreports and perform the operations that arerelated to out-of-band storage managementfrom the servers that they administer.

Allow access to storage views andoperations

Choose any of the following options toprovide scope to the roles that you havespecified:

■ Entire Domain■ Selected Business Entities

If you choose the scope as SelectedBusinessEntities, the panel displays all the businessentities present in Veritas OperationsManager. To limit the scope of the role toone or more specific business entities, youmust associate them with the security group.Select the check box on the left side of eachof the business entities to associate themwith the security group that you create.

Note: You cannot provide any scope to theGuest role. When you select the Guest role,the panel does not display the Scope options.

Scope


233Managing security groupsAdding security groups to the Veritas Operations Manager domain

Modifying security groups in the Veritas OperationsManager domain

The Edit Access Control wizard panel lets you modify the security groups in theVeritas Operations Manager domain. You can modify the role and the scope thatare associated with a security group.

You cannot modify the security group name or the authentication domain that isassociated with the security group.

To modify the security groups in a domain

1 In the Veritas Operations Manager console, select Settings>SecurityGroups.

2 Select the check box for the security group that you want to modify and clickActions > Edit Access Control.

3 In the Edit Access Control wizard panel, modify the role and the scope asrequired and click OK.

See “Edit Access Control options” on page 234.

4 In the Results panel that confirms the action, click OK.




Edit Access Control optionsUse this wizard panel to modify the role and the scope that are associated withthe security group.

Note: You cannot modify the name of the security group and the authenticationdomain that is associated with the security group.

Managing security groupsModifying security groups in the Veritas Operations Manager domain

234

Table 11-4 Edit Access Control panel options

DescriptionField

Displays the name of the security group.

You cannot edit this field.

You can click Check to verify that thesecurity group that you have created stillexists in the authentication domain.

Veritas Operations Manager displays an iconthat indicates that the verification of thesecurity group is in progress. If the securitygroup exists in the authentication domain,Veritas Operations Manager displays a greenicon. If the security group no longer existsin the authentication domain, you can viewa red icon.

Name

Displays the authentication domain that isassociated with the security group.


Domain

Choose the new role that you want toassociate with the security group.

Role

Select or clear this check box to modify theprivileges that you have provided to the roleto access the views and reports and performthe operations that are related toout-of-band storage management.

Allow access to storage views andoperations

Choose any of the following options toprovide new scope to the roles that you havespecified:

■ Entire Domain■ Selected Business Entities

If you choose the scope as SelectedBusinessEntities, select the check box on the left sideof the business entities that you want toassociate with the security group.

Note: You cannot provide any scope to theGuest role. When you select the Guest role,the panel does not display the Scope options.

Scope

235Managing security groupsModifying security groups in the Veritas Operations Manager domain


Removing security groups from Veritas OperationsManager

The Remove Security Group wizard panel lets you remove one or more securitygroups from Veritas Operations Manager. When you remove a security group, theassociation of the authentication group and authentication domain with the roleand application groups is also removed.

Note: You cannot remove the root security group that is mapped to the rootauthentication group of the primary Authentication Broker.

To remove security groups from Veritas Operations Manager

1 Select Settings > Security Groups.

2 Select one or more security groups that you want to remove and click Actions> Remove Security Group.

3 In the Remove Security Group wizard panel to confirm whether you needto remove the security groups that you have selected, click Yes.

4 In the Results panel that confirms that you removed the selected securitygroups, click OK.




Managing security groupsRemoving security groups from Veritas Operations Manager

236

Managing business entities


■ About managing business entities in Veritas Operations Manager

■ About composite business entities

■ About security privileges required to manage business entities

■ About Virtual Business Services

■ Creating Virtual Business Services

■ Creating Organization Entities

■ Editing Virtual Business Services

■ Editing Organization Entities

■ Deleting Virtual Business Services

■ Deleting Organization Entities

■ Creating composite Virtual Business Services

■ Creating composite Organization Entities

■ Adding storage or high availability objects to existing business entities

■ Making business entities available to security groups in Veritas OperationsManager

■ Setting extended attributes for business entities

■ Viewing Virtual Business Services

■ Viewing Organization Entities

■ About the makeBE script

12Chapter

■ Creating business entities using the makeBE script

■ Importing business entities using the makeBE script

■ Exporting business entities using the makeBE script

■ Updating business entities using the makeBE script

■ Deleting business entities using the makeBE script

About managing business entities in VeritasOperations Manager

In Veritas Operations Manager, you can create business entities to group baseobjects for the purpose of reporting and alerting. Based on the type of includedobjects, Veritas Operations Manager version provides two types of businessentities: Virtual Business Services and organization business entities.

A Virtual Business Service (VBS) is a collection of assets such as arrays, hosts,files systems, and clusters that you can manage as a single consolidated entity.A Virtual Business Services can be used to group one or more of the followingbase object types:

■ Databases

■ Hosts

■ Service Groups

■ File systems

■ Disk groups

■ Enclosures

■ Clusters

■ Exchange ServersSee “About Virtual Business Services” on page 240.

Organization business entities can be used to group only managed hosts.

You can perform the following operations related to business entities:

■ Create new business entities.

■ Modify business entities.

■ Change the security priorities of business entities.

■ Delete business entities.

Managing business entitiesAbout managing business entities in Veritas Operations Manager

238

See “Editing Virtual Business Services” on page 254.

About composite business entitiesDepending on your business requirements, you may want to group existingbusiness entities. This is achieved using composite business entities. Withcomposite business entities, you can group one or more business entities of similartype, and treat them as a single object. This mechanism lets you perform varioustasks collectively on the added business entities.

You can create two types of composite business entities:

■ Virtual Business Service: This type of composite business entity contains onlyVirtual Business Services.

■ Organization: This type of composite business entity contains only organizationbusiness entities.

See “About managing business entities in Veritas Operations Manager” on page 238.

See “Creating composite Virtual Business Services” on page 272.

See “Creating composite Organization Entities” on page 276.

See “Adding storage or high availability objects to existing business entities”on page 279.

See “Setting extended attributes for business entities” on page 281.

About security privileges required tomanagebusinessentities

In Veritas Operations Manager, business entities are associated with the securitygroups to provide access rights to the users with the Domain Admin role so thatthey can access specific hosts and storage devices. Domain administrators canperform all operations on business entities.

Restricted administrators can also perform some operations on business entitieswithin the following rules:

■ They can remove base hosts from a Virtual business Service if they haveadministrator privileges for the Virtual business Service.

■ They can add any host that they have administrator privileges on, as a basehost to a Virtual business Service. This includes the hosts that are added toother Virtual business Service or organization business entities that therestricted administrator has administrator privileges on.

239Managing business entitiesAbout composite business entities

■ They cannot add hosts to organization business entities, or remove hosts fromthem.

■ They cannot edit Virtual business Service.

■ They cannot delete Virtual business Services even if they have administratorprivileges for them.



About Virtual Business ServicesVirtual Business Services provide continuous high availability and reducefrequency and duration of service disruptions for multi-tier business applicationsrunning on heterogeneous operating systems and virtualization technologies. AVirtual Business Service represents the multi-tier application as a singleconsolidated entity and builds on the high availability and disaster recoveryprovided for the individual tiers by Symantec products such as Veritas ClusterServer and Symantec ApplicationHA. Additionally, a Virtual Business Service canalso represent all the assets used by the service such as arrays, hosts, and filesystems, though they are not migrated between server tiers. A Virtual BusinessService provides a single consolidated entity that represents a multi-tier businessservice in its entirety. Application components that are managed by Veritas ClusterServer or Symantec ApplicationHA can be actively managed through a VirtualBusiness Service.

You can configure and manage Virtual Business Services created in VeritasOperations Manager by using Veritas Operations Manager Virtual BusinessServices Availability Add-on. Besides providing all the functionality that wasearlier available through Business Entity Operations Add-on, VBS AvailabilityAdd-on provides the additional ability to configure fault dependencies betweenthe components of the multi-tier application.

Note: All the Application Entities that were created using Veritas OperationsManager Business Entity Operations Add-on versions 3.1 and 4.0 are available asVirtual Business Services after you deploy the VBS Availability Add-on in VeritasOperations Manager 5.0. Veritas Operations Manager 5.0 is a prerequisite forrunning Virtual Business Services.

Managing business entitiesAbout Virtual Business Services

240

Creating Virtual Business ServicesWith Virtual Business Services, the administrators can treat a collection of objectsas a single entity.

When generating Veritas Operations Manager reports, you can specify a VirtualBusiness Service to run the report on. The users with domain administrator rolecan manage the Virtual Business Service in Veritas Operations Manager.

You can create a Virtual Business Service in one of the following ways:

■ From the Virtual Business Services view

■ From the Business Entities view

To create a Virtual Business Service from the Virtual Business Services view

1 In the Veritas Operations Manager console, select Manage > VirtualBusinessServices.

2 In the Virtual Business Services view, at the top of the table that lists theVirtual Business Service, click Actions > Create Virtual Business Service.

3 In the Virtual Business Service Attributes, enter its name and description,and click Next.

See “Virtual Business Service Attributes options for creating a Virtual BusinessService” on page 244.

4 In the SelectBaseObjectTypes panel, select one or more available items andclick Next.

Each of the base object types that you select displays an associated SelectBase item panel from which you can select items of that type.

See “Select Base Object Types options for creating a Virtual Business Service”on page 244.

5 In the Select Base item panels, do the following:

■ If the SelectBaseDatabases panel appears, select one or more databasesand click Next.See “Select Base Databases options for creating a Virtual Business Service”on page 245.

■ If the Select Base Exchange Servers panel appears, select one or moreenclosures and click Next.See “Select Base Exchange Servers options for creating a Virtual BusinessService” on page 247.

■ If the SelectBaseClusters panel appears, select one or more clusters andclick Next.

241Managing business entitiesCreating Virtual Business Services

See “Select Base Clusters options for creating a Virtual Business Service”on page 247.

■ If the SelectBaseServiceGroups panel appears, select one or more servicegroups and click Next.See “Select Base Service Groups options for creating a Virtual BusinessService” on page 246.

■ If the SelectBaseHosts panel appears, select one or more hosts and clickNextSee “Select Base Hosts options for creating a Virtual Business Service”on page 245.

■ If the Select Base File Systems panel appears, select one or more filesystems and click NextSee “Select Base File Systems options for creating a Virtual BusinessService” on page 246.

■ If the Select Base Disk Groups panel appears, select one or more diskgroups and click NextSee “Select Base Disk Groups options for creating a Virtual BusinessService” on page 247.

■ If the SelectBaseEnclosures panel appears, select one or more enclosuresand click Next.See “Select Base Disk Groups options for creating a Virtual BusinessService” on page 247.

6 In the Business Entity Summary panel, review your selections and clickFinish.

See “Virtual Business Service summary for creating a Virtual Business Service”on page 248.

7 In the Results panel that confirms the creation of the Virtual Business Service,click OK.

To create a Virtual Business Service from the business entities view

1 In the Veritas Operations Manager console, select Manage > BusinessEntities.

2 In the Business Entities view, at the top of the table that lists the VirtualBusiness Service, click Actions > Create Business Entities (VBS/OE).

3 In the BusinessEntityAttributes, select the type of business entity as Virtualbusiness Service. Enter its name and description, and click Next.

See “Business Entity Attributes options for creating a business entity”on page 248.

Managing business entitiesCreating Virtual Business Services

242

4 In the SelectBaseObjectTypes panel, select one or more available items andclick Next.

Each of the base object types that you select displays an associated SelectBase item panel from which you can select items of that type.

See “Select Base Object Types options for creating a business entity”on page 249.


■ If the SelectBaseDatabases panel appears, select one or more databasesand click Next.See “Select Base Databases options for creating a business entity”on page 249.

■ If the Select Base Exchange Servers panel appears, select one or moreenclosures and click Next.See “Select Base Exchange Servers options for creating a business entity”on page 251.

■ If the SelectBaseClusters panel appears, select one or more clusters andclick Next.See “Select Base Clusters options for creating a business entity” on page 250.

■ If the SelectBaseServiceGroups panel appears, select one or more servicegroups and click Next.See “Select Base Service Groups options for creating a business entity”on page 251.

■ If the SelectBaseHosts panel appears, select one or more hosts and clickNextSee “Select Base Hosts options for creating a business entity” on page 250.

■ If the Select Base File Systems panel appears, select one or more filesystems and click NextSee “Select Base File Systems options for creating a business entity”on page 251.

■ If the Select Base Disk Groups panel appears, select one or more diskgroups and click NextSee “Select Base Disk Groups options for creating a business entity”on page 250.

■ If the SelectBaseEnclosures panel appears, select one or more enclosuresand click Next.See “Select Base Enclosures options for creating a business entity”on page 251.



See “Business Entity Summary options for creating a business entity”on page 252.



See “Deleting Virtual Business Services” on page 269.

Virtual Business Service Attributes options for creating a VirtualBusiness Service

Use this panel to create a Virtual Business Service. Veritas Operations Managerautomatically determines the resources that can belong to a Virtual BusinessService.

Table 12-1 Virtual Business Service Attributes options

DescriptionField

Enter the name of the Virtual Business Service. In this field, you canenter up to 255 characters.

Example: Accounts Receivable

Name

Enter a description for this Virtual Business Service. In this field, youcan enter up to 255 characters.

Example: All servers and storage that are associated with the AccountsReceivable billing system.

Description

See “Creating Virtual Business Services” on page 241.

Select Base Object Types options for creating a Virtual Business ServiceUse this wizard panel to specify the type of base objects on which the new VirtualBusiness Service is to be predicated on. Base objects determine the other objectsin the Virtual Business Service. All other objects that are associated with the baseobject are included automatically to the Virtual Business Service.

For example, you might choose a host to be the base object. Then, all the objectsthat are associated with the hosts are added to the Virtual Business Service.


244

Table 12-2 Select Base Object Types panel options

DescriptionField

You can select the check box for one or more of the followingapplication types to add them as base objects.

■ Databases■ Exchange Servers

Applications

You can select the check box for one or more of the following HA-DRobjects to add them as base objects.

■ Clusters■ Service Groups

HA-DR

You can select the check box for one or more of the following servertypes to add them as base objects.

■ Hosts■ File Systems■ Disk Groups

Servers

You can select the check box for Enclosures to add it as the base object.Storage


Select Base Databases options for creating a Virtual Business ServiceUse this wizard panel to select one or more databases as base objects for theVirtual Business Service.

Table 12-3 Select Base Databases

DescriptionField

Select one or more databases to include as base objects for the VirtualBusiness Service.

Database Table


Select Base Hosts options for creating a Virtual Business ServiceUse this wizard panel to select the base hosts for the Virtual Business Service.


Table 12-4 Select Base Hosts

DescriptionField

Select one or more hosts to include as base objects for the VirtualBusiness Service.

Host Table


Select Base File Systems options for creating a Virtual Business ServiceUse this wizard panel to select the file systems for the Virtual Business Service.

Table 12-5 Select Base File Systems

DescriptionField

Select one or more file systems to include as base objects for the VirtualBusiness Service.

File System Table


Select Base Service Groups options for creating a Virtual BusinessService

Use this wizard panel to select the base service groups for the Virtual BusinessService.

Table 12-6 Select Base Service Groups panel options

DescriptionField

Select one or more service groups to include as base objectsfor the Virtual Business Service.

Service Group Table


Select Base Enclosures options for creating a Virtual Business ServiceUse this wizard panel to select the base enclosures for the Virtual Business Service.


246

Table 12-7 Select Base Enclosures panel options

DescriptionField

Select one or more enclosures to include asbase objects for the Virtual Business Service.

Enclosures Table


Select Base Exchange Servers options for creating a Virtual BusinessService

Use this wizard panel to select the base Exchange Servers for the Virtual BusinessService.

Table 12-8 Select Base Exchange Servers panel options

DescriptionField

Select one or more Exchange Servers toinclude as base objects for the VirtualBusiness Service.

Exchange Servers Table


Select Base Clusters options for creating a Virtual Business ServiceUse this wizard panel to select the base clusters for the Virtual Business Service.

Table 12-9 Select Base Clusters options

DescriptionField

Select one or more clusters to include as baseobjects for the Virtual Business Service.

Clusters Table


Select Base Disk Groups options for creating a Virtual Business ServiceUse this wizard panel to select the base disk groups for the Virtual BusinessService.


Table 12-10 Select Base Disk Groups

DescriptionField

Select one or more disk groups to include as base objects for the VirtualBusiness Service.

Disk Group Table


Virtual Business Service summary for creating a Virtual BusinessService

Use this wizard panel to review the contents and attributes of the business entitybefore creating it.


Business Entity Attributes options for creating a business entityUse this panel to create a business entity. Veritas Operations Managerautomatically determines the resources that can belong to a business entity.

Table 12-11 Business Entity Attributes options

DescriptionField

Enter the name of the business entity. In this field, you can enter upto 255 characters.


Name

Enter a description for this business entity. In this field, you can enterup to 255 characters.


Description

Select one of the following types of business entity to create:

■ Virtual Business Service: A Virtual Business Service (VBS) is acollection of assets such as arrays, hosts, files systems, and clustersthat you can manage as a single consolidated entity. It is moreresource intensive, so should be limited to specifying less than 100base objects.

■ Organization: A group of logically associated hosts. For example,by Admin, by Team, by Datacenter. It is less resource intensive,and can include potentially thousands of base hosts.

Type


248

See “Creating Organization Entities” on page 252.


Select Base Object Types options for creating a business entityUse this wizard panel to specify the type of base objects on which the new businessentity is to be predicated on. Base objects determine the other objects in thebusiness entity. All other objects that are associated with the base object areincluded automatically to the business entity.

For example, you might choose a host to be the base object. Then, all the objectsthat are associated with the hosts are added to the business entity.

Table 12-12 Select Base Object Types panel options

DescriptionField

You can select the check box for one or more of the followingapplication types to add them as base objects.


Applications

You can select the check box for one or more of the following HA-DRobjects to add them as base objects.


HA-DR

You can select the check box for one or more of the following servertypes to add them as base objects.


Servers

You can select the check box for Enclosures to add it as the base object.Storage


Select Base Databases options for creating a business entityUse this wizard panel to select one or more databases as base objects for thebusiness entity.


Table 12-13 Select Base Databases

DescriptionField

Select one or more databases to include as base objects for the businessentity.

Database Table


Select Base Hosts options for creating a business entityUse this wizard panel to select the base hosts for the business entity.


DescriptionField

Select one or more hosts to include as base objects for the businessentity.

Host Table



Select Base Clusters options for creating a business entityUse this wizard panel to select the base clusters for the business entity.


DescriptionField

Select one or more clusters to include as baseobjects for the business entity.

Clusters Table


Select Base Disk Groups options for creating a business entityUse this wizard panel to select the base disk groups for the business entity.

Table 12-16 Select Base Disk Groups

DescriptionField

Select one or more disk groups to include as base objects for thebusiness entity.

Disk Group Table


250


Select Base File Systems options for creating a business entityUse this wizard panel to select the file systems for the business entity.

Table 12-17 Select Base File Systems

DescriptionField

Select one or more file systems to include as base objects for thebusiness entity.

File System Table


Select Base Service Groups options for creating a business entityUse this wizard panel to select the base service groups for the business entity.

Table 12-18 Select Base Service Groups panel options

DescriptionField

Select one or more service groups to include as base objectsfor the business entity.

Service Group Table


Select Base Enclosures options for creating a business entityUse this wizard panel to select the base enclosures for the business entity.


DescriptionField

Select one or more enclosures to include asbase objects for the business entity.

Enclosures Table


Select Base Exchange Servers options for creating a business entityUse this wizard panel to select the base Exchange Servers for the business entity.


Table 12-20 Select Base Exchange Servers options

DescriptionField

Select one or more Exchange Servers toinclude as base objects for the businessentity.



Business Entity Summary options for creating a business entityUse this wizard panel to review the contents and attributes of the business entitybefore creating it.



Creating Organization EntitiesWith Organization Entities, the administrators can treat a collection of objectsas a single entity.

When generating Veritas Operations Manager reports, you can specify anOrganization Entity to run the report on. The users with domain administratorrole can manage the Organization Entity in Veritas Operations Manager.

You can create an Organization Entity in one of the following ways:

■ From the Organization Entities view


To create an Organization Entity from the Organization Entities view

1 Select Manage > Organization Entities.

2 In the Organization Entities view, at the top of the table that lists theOrganization Entities, click Actions > Create Organization Entity.

3 In the OrganizationEntityAttributes panel, enter its name and description,and click Next.

See “Organization Entity Attributes options for creating an OrganizationEntity” on page 253.

4 In the Select Base Hosts panel, select one or more hosts and click Next.

See “Select Base Hosts options for creating an Organization Entity”on page 254.

Managing business entitiesCreating Organization Entities

252

5 In the OrganizationEntitySummary panel, review your selections and clickFinish.

See “Organization Entity Summary options for creating an OrganizationEntity” on page 254.

6 In the Results panel that confirms the creation of the Organization Entity,click OK.

To create an Organization Entity from the Business Entities view

1 In the Veritas Operations Manager console, select Manage > BusinessEntities.

2 In the Business Entities view, at the top of the table that lists the VirtualBusiness Service, click Actions > Create Business Entities (VBS/OE).

3 In the Business Entity Attributes, select the type of business entity asOrganization Entity. Enter its name and description, and click Next.

See “Business Entity Attributes options for creating a business entity”on page 248.

4 In the Select Base Hosts panel, select one or more hosts and click Next

See “Select Base Hosts options for creating a business entity” on page 250.


See “Business Entity Summary options for creating a business entity”on page 252.


See “Editing Organization Entities” on page 267.


Organization Entity Attributes options for creating an OrganizationEntity

Use this panel to create an Organization Entity. Veritas Operations Managerautomatically determines the resources that can belong to an Organization Entity.

253Managing business entitiesCreating Organization Entities

Table 12-21 Organization Entity Attributes options

DescriptionField

Enter the name of the Organization Entity. In this field, you can enterup to 255 characters.


Name

Enter a description for this Organization Entity. In this field, you canenter up to 255 characters.


Description


Organization Entity Summary options for creating an OrganizationEntity

Use this wizard panel to review the contents and attributes of the OrganizationEntity before creating it.


Select Base Hosts options for creating an Organization EntityUse this wizard panel to select the base hosts for the Organization Entity.


DescriptionField

Select one or more hosts to include as base objects for the OrganizationEntity.

Host Table


Editing Virtual Business ServicesThe administrators can edit the content of a Virtual Business Services by modifyingthe selection of the base objects, and their dependencies on the Virtual BusinessServices.

You can edit a Virtual Business Service in one of the following ways:


Managing business entitiesEditing Virtual Business Services

254


To edit a Virtual Business Services

1 In the Veritas Operations Manager console, select Manage> VirtualBusinessServices.

2 In the Virtual Business Services view, do one of the following:

■ Select the Virtual Business Service that you want to edit and click Actions> Edit Virtual Business Services.

■ Right-click the Virtual Business Service and from the submenu, selectEdit Virtual Business Services.

3 In the Virtual Business Service Attributes panel, modify the details andclick Next.

See “Virtual Business Service Attributes options for editing a Virtual BusinessService” on page 258.

4 In the Select Base Object Types panel, select one or more of the availableitems to modify the selection and click Next.

Each of the base object types you select displays an associated Select Baseitem panel. You can select the desired items from the list. For instance, underApplications base object type, you can select Database and ExchangeServers.

See “Select Base Object Types options for editing a business entity” on page 263.


■ If the SelectBaseDatabases panel appears, select one or more databasesto modify the selection and click Next.See “Select Base Databases options for editing a Virtual Business Service”on page 259.

■ If the Select Base Exchange Servers panel appears, select one or moredisk groups to modify the selection and click Next.See “Select Base Exchange Servers options for editing a Virtual BusinessService” on page 262.

■ If the Select Base Clusters panel appears, select one or more clusters tomodify the selection and click Next.See “Select Base Clusters options for editing a Virtual Business Service”on page 261.

■ If the SelectBaseServiceGroups panel appears, select one or more servicegroups to modify the selection and click Next.See “Select Base Service Groups options for editing a Virtual BusinessService” on page 260.

255Managing business entitiesEditing Virtual Business Services

■ If the SelectBaseHosts panel appears, select one or more hosts to modifythe selection and click Next.See “Select Base Hosts options for editing a Virtual Business Service”on page 259.

■ If the Select Base File Systems panel appears, select one or more filesystems to modify the selection and click Next.See “Select Base File Systems options for editing a Virtual BusinessService” on page 260.

■ If the Select Base Disk Groups panel appears, select one or more diskgroups to modify the selection and click Next.See “Select Base Disk Groups options for editing a Virtual Business Service”on page 261.

■ If the SelectBaseEnclosures panel appears, select one or more disk groupsto modify the selection and click Next.See “Select Base Enclosures options for editing a Virtual Business Service”on page 261.

6 In the Business Entiy Summary panel, review your modified selections andclick Finish.

See “Virtual Business Service Summary for editing a Virtual Business Service”on page 262.




To edit a Virtual Business Service from the Business Entities view

1 In the Veritas Operations Manager console, select Manage> BusinessEntities.

2 In the Business Entities view, do one of the following:

■ Select the Virtual Business Service that you want to edit and click Actions> Edit Business Entities (VBS/OE).

■ Right-click the Virtual Business Service and from the submenu, selectEdit Business Entities (VBS/OE).

3 In the Business Entity Attributes panel, modify the details and click Next.

See “Business entity Attributes options for editing a business entity”on page 262.


256

4 In the Select Base Object Types panel, select one or more of the availableitems to modify the selection and click Next.

Each of the base object types you select displays an associated Select Baseitem panel. You can select the desired items from the list. For instance, underApplications base object type, you can select Database and ExchangeServers.

See “Select Base Object Types options for editing a Virtual Business Service”on page 258.


■ If the SelectBaseDatabases panel appears, select one or more databasesto modify the selection and click Next.See “Select Base Databases options for editing a business entity”on page 264.

■ If the Select Base Exchange Servers panel appears, select one or moredisk groups to modify the selection and click Next.See “Select Base Exchange Servers options for editing a business entity”on page 266.

■ If the Select Base Clusters panel appears, select one or more clusters tomodify the selection and click Next.See “Select Base Clusters options for editing a business entity” on page 266.

■ If the SelectBaseServiceGroups panel appears, select one or more servicegroups to modify the selection and click Next.See “Select Base Service Groups options for editing a business entity”on page 264.

■ If the SelectBaseHosts panel appears, select one or more hosts to modifythe selection and click Next.See “Select Base Hosts options for editing a business entity” on page 264.

■ If the Select Base File Systems panel appears, select one or more filesystems to modify the selection and click Next.See “Select Base File Systems options for editing a business entity”on page 265.

■ If the Select Base Disk Groups panel appears, select one or more diskgroups to modify the selection and click Next.See “Select Base Disk Groups options for editing a business entity”on page 265.

■ If the SelectBaseEnclosures panel appears, select one or more disk groupsto modify the selection and click Next.See “Select Base Enclosures options for editing a business entity”on page 266.


6 In the BusinessEntitySummary panel, review your modified selections andclick Finish.

See “Business Entity Summary for editing a business entity” on page 267.



Virtual Business Service Attributes options for editing a VirtualBusiness Service

Use this wizard panel to modify the name and the description of a Virtual BusinessService.

Table 12-23 Virtual Business Service Attributes options

DescriptionField

Modify the name of the Virtual BusinessService. You can enter up to 255 charactersin this field.

Name

Modify the description for the VirtualBusiness Service. You can enter up to 255characters in this field.

Description


Select Base Object Types options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of the type of objects on which theVirtual Business Service is based.

Table 12-24 Select Base Object Types options

DescriptionField

Modify the selection of one or more of thefollowing application types to include orexclude them as base objects.


Applications


258

Table 12-24 Select Base Object Types options (continued)

DescriptionField

Modify the selection of one or more of thefollowing HA-DR objects to include orexclude them as base objects.


HA-DR

Modify the selection of one or more of thefollowing server types to include or excludethem as base objects.


Servers

Modify the selection to include or excludeEnclosures as the base object.

Storage


Select Base Databases options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of base database(s) for the VirtualBusiness Service.

Table 12-25 Select Base Databases options

DescriptionField

Select one or more databases to include asbase objects for the Virtual Business Service.

Database Table

Use the dynamic search to filter the list of base databases. Use the Only showcurrent bases option to see only those base databases, which are currently partof the Virtual Business Service.


Select Base Hosts options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of the base hosts for the VirtualBusiness Service.


Table 12-26 Select Base Hosts panel options

DescriptionField

Select one or more hosts to include as baseobjects for the Virtual Business Service.

Host Table

Use the dynamic search to filter the list of base hosts. Use the Onlyshowcurrentbases option to see only those base hosts, which are currently part of the VirtualBusiness Service.


Select Base Service Groups options for editing a Virtual BusinessService

Use this wizard panel to modify the selection of the base service groups for theVirtual Business Service.

Table 12-27 Select Base Service Groups options

DescriptionField

Select one or more service groups to includeas base objects for the Virtual BusinessService.

Service Group Table

Use the dynamic search to filter the list of base service groups. Use the Onlyshowcurrent bases option to see only those base service groups, which are currentlypart of the Virtual Business Service.


Select Base File Systems options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of the file systems for the VirtualBusiness Service.

Table 12-28 Select Base File Systems options

DescriptionField

Select one or more file systems to include asbase objects for the Virtual Business Service.

File System Table


260

Use the dynamic search to filter the list of base file systems. Use the Only showcurrentbases option to see only those base file systems, which are currently partof the Virtual Business Service.


Select Base Disk Groups options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of the base disk groups for the VirtualBusiness Service.

Table 12-29 Select Base Disk Groups panel options

DescriptionField

Select one or more disk groups to include asbase objects for the Virtual Business Service.

Disk group Table

Use the dynamic search to filter the list of base disk groups. Use the Only showcurrentbases option to see only those base disk groups, which are currently partof the Virtual Business Service.


Select Base Enclosures options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of the base enclosures for the VirtualBusiness Service.


DescriptionField

Select one or more enclosures to include asbase objects for the Virtual Business Service.

Enclosures Table

Use the dynamic search to filter the list of base enclosures. Use the Only showcurrent bases option to see only those base enclosures, which are currently partof the Virtual Business Service.


Select Base Clusters options for editing a Virtual Business ServiceUse this wizard panel to modify the selection of clusters for the Virtual BusinessService.



DescriptionField

Select one or more clusters to include as baseobjects for the Virtual Business Service.

Base Clusters Table

Use the dynamic search to filter the list of base clusters. Use the Onlyshowcurrentbases option to see only those base clusters, which are currently part of the VirtualBusiness Service.


Select Base Exchange Servers options for editing a Virtual BusinessService

Use this wizard panel to modify the selection of the base Exchange Servers forthe Virtual Business Service.


DescriptionField

Select one or more Exchange Servers toinclude as base objects for the VirtualBusiness Service.



Virtual Business Service Summary for editing a Virtual Business ServiceUse this wizard panel to review the modified contents and attributes of the virtualbusiness service.


Business entity Attributes options for editing a business entityUse this wizard panel to modify the name and the description of a business entity.

Table 12-33 Business Entity Attributes options

DescriptionField

Modify the name of the business entity. Youcan enter up to 255 characters in this field.

Name


262

Table 12-33 Business Entity Attributes options (continued)

DescriptionField

Modify the description for the businessentity. You can enter up to 255 charactersin this field.

Description



Select Base Object Types options for editing a business entityUse this wizard panel to modify the selection of the type of objects on which thebusiness entity is based.

Table 12-34 Select Base Object Types options

DescriptionField

Modify the selection of one or more of thefollowing application types to include orexclude them as base objects.


Applications

Modify the selection of one or more of thefollowing HA-DR objects to include orexclude them as base objects..


HA-DR

Modify the selection of one or more of thefollowing server types to include or excludethem as base objects.


Servers

Modify the selection to include or excludeEnclosures as the base object.

Storage



Select Base Databases options for editing a business entityUse this wizard panel to modify the selection of base database(s) for the businessentity.

Table 12-35 Select Base Databases options

DescriptionField

Select one or more databases to include asbase objects for the business entity.

Database Table

Use the dynamic search to filter the list of base databases. Use the Only showcurrent bases option to see only those base databases, which are currently partof the business entity.


Select Base Hosts options for editing a business entityUse this wizard panel to modify the selection of the base hosts for the businessentity.


DescriptionField

Select one or more hosts to include as baseobjects for the business entity.

Host Table

Use the dynamic search to filter the list of base hosts. Use the Onlyshowcurrentbases option to see only those base hosts, which are currently part of the businessentity.



Select Base Service Groups options for editing a business entityUse this wizard panel to modify the selection of the base service groups for thebusiness entity.


264

Table 12-37 Select Base Service Groups options

DescriptionField

Select one or more service groups to includeas base objects for the business entity.

Service Group Table

Use the dynamic search to filter the list of base service groups. Use the Onlyshowcurrent bases option to see only those base service groups, which are currentlypart of the business entity.


Select Base File Systems options for editing a business entityUse this wizard panel to modify the selection of the file systems for the businessentity.

Table 12-38 Select Base File Systems options

DescriptionField

Select one or more file systems to include asbase objects for the business entity.

File System Table

Use the dynamic search to filter the list of base file systems. Use the Only showcurrentbases option to see only those base file systems, which are currently partof the business entity.


Select Base Disk Groups options for editing a business entityUse this wizard panel to modify the selection of the base disk groups for thebusiness entity.

Table 12-39 Select Base Disk Groups panel options

DescriptionField

Select one or more disk groups to include asbase objects for the business entity.

Disk group Table

Use the dynamic search to filter the list of base disk groups. Use the Only showcurrentbases option to see only those base disk groups, which are currently partof the business entity.



Select Base Enclosures options for editing a business entityUse this wizard panel to modify the selection of the base enclosures for thebusiness entity.


DescriptionField

Select one or more enclosures to include asbase objects for the business entity.

Enclosures Table

Use the dynamic search to filter the list of base enclosures. Use the Only showcurrent bases option to see only those base enclosures, which are currently partof the business entity.


Select Base Clusters options for editing a business entityUse this wizard panel to modify the selection of clusters for the business entity.


DescriptionField

Select one or more clusters to include as baseobjects for the business entity.

Base Clusters Table

Use the dynamic search to filter the list of base clusters. Use the Onlyshowcurrentbases option to see only those base clusters, which are currently part of thebusiness entity.


Select Base Exchange Servers options for editing a business entityUse this wizard panel to modify the selection of the base Exchange Servers forthe business entity.


266


DescriptionField

Select one or more Exchange Servers toinclude as base objects for the businessentity.



Business Entity Summary for editing a business entityUse this wizard panel to review the modified contents and attributes of thebusiness entity.



Editing Organization EntitiesThe administrators can edit the content of an Organization Entity by modifyingthe selection of the associated hosts.

You can edit an Organization Entity in one of the following ways:



To edit an Organization Entity from the Organization Entities view

1 Select Manage > Organization Entities.

2 In the Organization Entities view, do one of the following:

■ Select the Organization Entity that you want to edit and click Actions >Edit Organization Entity.

■ Right-click the Organization Entity and from the submenu, select EditOrganization Entity.

3 In the Organization Entity Attributes panel, modify the details and clickNext.

See “Organization Entity Attributes options for editing an OrganizationEntity” on page 269.

267Managing business entitiesEditing Organization Entities

4 In the SelectBaseHosts panel, select one or more hosts to modify the selectionand click Next.

See “Select Base Hosts options for editing an Organization Entity” on page 269.

5 In the OrganizationEntitySummary panel, review your modified selectionsand click Finish.

See “Organization Entity Summary for editing an Organization Entity”on page 268.


To edit an Organization Entity from the Business Entities view

1 In the Veritas Operations Manager console, select Manage> BusinessEntities.

2 In the Business Entities view, do one of the following:

■ Select the Organization Entity that you want to edit and click Actions >Edit Business Entities (VBS/OE).

■ Right-click the Organization Entity and from the submenu, select EditBusiness Entities (VBS/OE).

3 In the Business Entity Attributes panel, modify the details and click Next.

See “Business entity Attributes options for editing a business entity”on page 262.

4 In the SelectBaseHosts panel, select one or more hosts to modify the selectionand click Next.

See “Select Base Hosts options for editing a business entity” on page 264.

5 In the BusinessEntitySummary panel, review your modified selections andclick Finish.

See “Business Entity Summary for editing a business entity” on page 267.



See “Deleting Organization Entities” on page 271.

Organization Entity Summary for editing an Organization EntityUse this wizard panel to review the modified contents and attributes of theOrganization Entity.


Managing business entitiesEditing Organization Entities

268

Select Base Hosts options for editing an Organization EntityUse this wizard panel to modify the selection of the base hosts for the OrganizationEntity.


DescriptionField

Select one or more hosts to include as baseobjects for the Organization Entity.

Host Table

Use the dynamic search to filter the list of base hosts. Use the Onlyshowcurrentbases option to see only those base hosts, which are currently part of theOrganization Entity.


Organization Entity Attributes options for editing an OrganizationEntity

Use this wizard panel to modify the name and the description of an OrganizationEntity.

Table 12-44 Organization Entity Attributes options

DescriptionField

Modify the name of the Organization Entity.You can enter up to 255 characters in thisfield.

Name

Modify the description for the OrganizationEntity. You can enter up to 255 charactersin this field.

Description


Deleting Virtual Business ServicesYou can use the Delete Virtual Business Service option to delete an existingVirtual Business Service in the Veritas Operations Manager console.

You can delete a Virtual Business Service in one of the following ways:

■ From the Virtual Business Service view

269Managing business entitiesDeleting Virtual Business Services


To delete a Virtual Business Service from the Virtual Business Services view

1 In the Veritas Operations Manager console, select Manage > VirtualBusinessService.

2 In the VirtualBusinessService view, select the Virtual Business Service thatyou want to delete and do one of the following:

■ Click Actions > Delete Virtual Business Service.

■ Right-click the Virtual Business Service from the submenu, select DeleteVirtual Business Service.

3 In the Delete Virtual Business Service wizard, click Yes.

See “Delete Virtual Business Service options for deleting a Virtual BusinessService” on page 270.


To delete a Virtual Business Service from the Business Entities view

1 In the Veritas Operations Manager console, select Manage>BusinessEntities.

2 In the Business Entities view, select the business entity that you want todelete and do one of the following:

■ Click Actions > Delete Business Entity.

■ Right-click the business entity and from the submenu, select DeleteBusiness Entity.

3 In the Delete Business Entity wizard, click Yes.




Delete Virtual Business Service options for deleting a Virtual BusinessService

Use this wizard panel to delete an exisiting Virtual Business Service.


Managing business entitiesDeleting Virtual Business Services

270

Deleting Organization EntitiesYou can use the Delete Organization Entity option to delete an existingOrganization Entity using Veritas Operations Manager console.

You can delete an Organization Entity in one of the following ways:



To delete an Organization Entity from the Organization Entities view

1 In the Veritas Operations Manager console, select Manage > OrganizationEntities.

2 In the Organization Entities view, at the top of the table that lists theOrganization Entities, click Actions > Delete Organization Entity.

3 In the Delete Organization Entity wizard, click Yes.

See “Delete Organization Entity options to delete an Organization Entity”on page 271.


To delete an Organization Entity from the Business Entities view


2 In the Business Entities view, select the business entity that you want todelete and do one of the following:

■ Click Actions > Delete Business Entity.

■ Right-click the business entity and from the submenu, select DeleteBusiness Entity.

3 In the Delete Business Entity wizard, click Yes.




Delete Organization Entity options to delete an Organization EntityUse this wizard panel to delete an exisiting Organization Entity.

See “Deleting Organization Entities” on page 271.

271Managing business entitiesDeleting Organization Entities

Creating composite Virtual Business ServicesWith composite Virtual Business Service, the administrator can group one ormore Virtual Business Services of similar type, and treat them as a single object.This mechanism lets you perform various tasks collectively on the added VirtualBusiness Service.

You can create a composite Virtual Business Service in one of the following ways:



To create a composite Virtual Business Service from the Virtual Business Servicesview

1 In the Veritas Operations Manager console, select Manage > VirtualBusinessServices.

2 In the Virtual Business Services view, click Actions > Create CompositeVirtual Business Service.

3 In the CompositeVirtualBusinessServiceAttributes panel, enter the nameand description of the Virtual Business Service, and click Next.

See “Composite Virtual Business Service Attributes options for creating acomposite Virtual Business Service” on page 273.

4 In the Select Virtual Business Service panel, select one or more VirtualBusiness Service that you want to add to the composite business entity, andclick Next.

See “Select Virtual Business Service panel options for creating a compositeVirtual Business Service” on page 274.

5 In the Composite Virtual Business Service Summary panel, review yourselections and click Finish.

See “Composite Virtual Business Service Summary panel options for creatinga composite Virtual Business Service” on page 274.

6 In the Results panel that confirms the creation of the composite VirtualBusiness Service, click OK.

To create a composite Virtual Business Service from the Business Entities view


2 In the Business Entities view, at the top of the table that lists the businessentities, click Actions > Create Composite Business Entity.

Managing business entitiesCreating composite Virtual Business Services

272

3 In the Composite Business Entity Attributes panel, select the type ofcomposite business entity that you want to create. Enter its name anddescription, and click Next.

See “Business Entity Attributes options for creating a composite businessentity” on page 274.

4 In the SelectBusinessEntity panel, select one or more business entities thatyou want to add to the composite business entity, and click Next.

See “Select Business Entity panel options for creating a composite businessentity” on page 275.


See “Composite Business Entity Summary panel options for creating acomposite business entity” on page 276.

6 In the Results panel that confirms the creation of the composite businessentity, click OK.



Composite Virtual Business Service Attributes options for creating acomposite Virtual Business Service

Use this panel to create a new composite Virtual Business Service.

Table 12-45 Composite Virtual Business Service Attributes options

DescriptionField

Enter the name of the composite Virtual Business Service. In this field,you can enter up to 255 characters.

Example: Production Virtual Business Service

Name

Enter a description for this composite Virtual Business Service. In thisfield, you can enter up to 255 characters.

Example: All servers and storage that are associated with theProduction Virtual Business Service.

Description


273Managing business entitiesCreating composite Virtual Business Services

Select Virtual Business Service panel options for creating a compositeVirtual Business Service

Use this panel to add one or more Virtual Business Service to the new compositeVirtual Business Service.

Table 12-46 Select Virtual Business Service options

DescriptionField

Displays the name of the Virtual Business Service. Select the desiredVirtual Business Service that you want to add to the composite VirtualBusiness Service.

Name

Displays the description for the Virtual Business Service.Description


Composite Virtual Business Service Summary panel options for creatinga composite Virtual Business Service

Use this panel to review the contents, and the attributes of the composite VirtualBusiness Service before creating it.


Business Entity Attributes options for creating a composite businessentity

Use this panel to create a new composite business entity. A composite businessentity lets you group business entities of same type. For example, you can createa composite business entity of Virtual Business Service type, and add multipleVirtual Business Services to it.

Table 12-47 Composite Business Entity Attributes options

DescriptionField

Enter the name of the composite business entity. In this field, you canenter up to 255 characters.

Example: Production Business Entity

Name

Managing business entitiesCreating composite Virtual Business Services

274

Table 12-47 Composite Business Entity Attributes options (continued)

DescriptionField

Enter a description for this composite business entity. In this field,you can enter up to 255 characters.

Example: All servers and storage that are associated with theProduction Business Entity.

Description

Select the type of the composite business entity.

■ Virtual Business Service: The Virtual Business Service type ofcomposite business entity can contain one or more Virtual BusinessServices.

■ Organization: The organization type of composite business entitycan contain one or more organization business entities.

Type



Select Business Entity panel options for creating a composite businessentity

Use this panel to add one or more business entities to the new composite businessentity. If you create a composite business entity of Virtual Business Service type,only Virtual Business Services are available for the selection. Similarly, if youcreate a composite business entity of organization type, only organization businessentities are available for the selection.

Table 12-48 Select Business Entity options

DescriptionField

Displays the name of the business entity. Select the desired businessentity that you want to add to the composite business entity.

Name

Displays the description for the business entity.Description

Displays the present state of the business entity.Type



275Managing business entitiesCreating composite Virtual Business Services

Composite Business Entity Summary panel options for creating acomposite business entity

Use this panel to review the contents, and the attributes of the composite businessentity before creating it.



Creating composite Organization EntitiesWith composite Organization Entity, the administrator can group one or moreOrganization Entities of similar type, and treat them as a single object. Thismechanism lets you perform various tasks collectively on the added organizationentities.

You can create a composite Organization Entity in one of the following ways:



To create a composite Organization Entity from the Organization Entities view

1 In the Veritas Operations Manager console, select Manage > OrganizationEntities.

2 In the Organization Entities view, click Actions > Create CompositeOrganization Entity.

3 In the CompositeOrganizationEntityAttributes panel, enter the name anddescription of the organization entity, and click Next.

See “Composite Organization Entity Attributes options for creating acomposite Organization Entity” on page 277.

4 In the Select Organization Entity panel, select one or more organizationentities that you want to add to the composite organization entity, and clickNext.

See “Select Organization Entity panel options for creating a compositeOrganization Entity” on page 278.

Managing business entitiesCreating composite Organization Entities

276

5 In the OrganizationEntitySummary panel, review your selections and clickFinish.

See “Composite Organization Entity Summary panel options for creating acomposite Organization Entity” on page 278.

6 In the Results panel that confirms the creation of the composite OrganizationEntity, click OK.

To create a composite Organization Entity from the Business Entities view


2 In the Business Entities view, at the top of the table that lists the businessentities, click Actions > Create Composite Business Entity.

3 In the Composite Business Entity Attributes panel, select the type ofcomposite Organization Entity that you want to create. Enter its name anddescription, and click Next.

See “Business Entity Attributes options for creating a composite businessentity” on page 274.

4 In the SelectBusinessEntity panel, select one or more business entities thatyou want to add to the composite business entity, and click Next.

See “Select Business Entity panel options for creating a composite businessentity” on page 275.


See “Composite Business Entity Summary panel options for creating acomposite business entity” on page 276.

6 In the Results panel that confirms the creation of the composite businessentity, click OK.



Composite Organization Entity Attributes options for creating acomposite Organization Entity

Use this panel to create a new composite Organization Entity.

277Managing business entitiesCreating composite Organization Entities

Table 12-49 Composite Organization Entity Attributes options

DescriptionField

Enter the name of the composite Organization Entity. In this field,you can enter up to 255 characters.

Example: Production Organization Entity

Name

Enter a description for this composite Organization Entity. In thisfield, you can enter up to 255 characters.

Example: All servers and storage that are associated with theProduction Organization Entity.

Description


Select Organization Entity panel options for creating a compositeOrganization Entity

Use this panel to add one or more organization entities to the new compositeOrganization Entity.

Table 12-50 Select Organization Entity options

DescriptionField

Displays the name of the Organization Entity. Select the desiredOrganization Entity that you want to add to the compositeOrganization Entity.

Name

Displays the description for the Organization Entity.Description

Displays the present state of the Organization Entity.Type


Composite Organization Entity Summary panel options for creating acomposite Organization Entity

Use this panel to review the contents, and the attributes of the compositeOrganization Entity before creating it.


Managing business entitiesCreating composite Organization Entities

278

Adding storage or high availability objects to existingbusiness entities

You can add storage and high availability objects to the business entity that ispresent in Veritas Operations Manager.

To add storage and high availability objects to an existing business entity

1 To add one or more storage or high availability objects to an existing businessentity, navigate to view where you can view object. For example, to add hoststo the business entity, select Manage > Hosts.

2 Select the check box for the object.

3 At the top of the table that displays objects, click Actions > Add to BusinessEntity.

4 In the Add to Business Entity panel, enter the details and click OK.

See “Add to Business Entity options” on page 279.


Add to Business Entity optionsUse this panel to add the selected object to an existing business entity.

Table 12-51 Add to Business Entity options

DescriptionField

Select the business entity to which the selected object is to be added.Add to BusinessEntity


Making business entities available to security groupsin Veritas Operations Manager

You can use the ChangePermissions wizard panel to provide permissions to oneor more security groups to access a business entity.

You can use the security groups to provide access to specific hosts in a businessentity to the users with the Domain Admin role.

279Managing business entitiesAdding storage or high availability objects to existing business entities

To make a business entity available to the security groups

1 Select Manage > Business Entities.

2 In the Business Entities view, you can do one of the following:

■ Select the business entity that you want to access using the security groupsand click Actions > Change Permissions.Alternatively, you can right-click the business entity and from thesubmenu, select Change Permissions.

■ Click the name of the business entity to view its details. In the details viewof the business entity, click the tab Permissions. Under the Permissionstab, click Change Permissions.

3 In the Change Permissions for business entity name panel, do one of thefollowing and click OK.

■ To provide access permissions, select the check box corresponding thesecurity group.

■ To remove access permissions, clear the check box corresponding toselected security group.

See “Change Permissions options” on page 280.


See “Business Entity Attributes options for creating a business entity” on page 248.


Change Permissions optionsUse this panel to select the security groups to provide permissions to access thebusiness entities. Under SelectSecurityGroups, you can view the table that listsall the security groups that are available in Veritas Operations Manager.

In the table, you can view the following details of the security groups:

■ Name of the security group.

■ Name of the authentication domain that is associated with the security group.

■ Type of the authentication domain that is associated with the security group.

■ Role that is associated with the security group.

See “Making business entities available to security groups in Veritas OperationsManager” on page 279.

Managing business entitiesMaking business entities available to security groups in Veritas Operations Manager

280

Setting extended attributes for business entitiesVeritas Operations Manager lets you apply the value of an extended attribute ona business entity. You can select the base object type of the business entity toapply the extended attribute value. Setting the extended attribute on the basebusiness entity applies the extended attributes value to all the objects that areassociated with the base object type. Also, you can select an object type that isrelated to the base object type of the business entity to define the attributes onall the objects that are associated with the object type.

Note: You must define the extended attribute for the base object type of thebusiness entity before you set the extended attributes for the business entity.

To set the extended attributes on a business entity

1 In Veritas Operations Manager console, select Manage > Business Entities.

2 In the BusinessEntities view, select the check box on the left side of the rowthat represents the business entity for which you want to set the extendedattributes.

3 At the top of the business entity table, select Actions > Set ExtendedAttribute.

4 In the Selectbaseobjecttype panel, enter the required details and click Next.

5 In the Select relatedobject types panel, select the object types on which youwant to define the extended attribute, which is set for the base object type,and click Finish.

See “Select related object types options” on page 282.

6 In the Result panel that confirms the extended attribute is successfully seton the business entity, click OK.

See “Setting values to the extended attributes on one or more objects” on page 441.

See “Modifying the extended attributes value on an object” on page 442.

Select base object type optionsUse this panel to select the base object type of the business entity, which lets youapply the extended attribute value to all the objects that are associated with thebase business entity.

281Managing business entitiesSetting extended attributes for business entities

Note: On the Select base object type panel, you can select only one object type ata time.

Table 12-52 Select base object type panel options

DescriptionField

Select the base object type of the businessgroup for which you want to set the extendedattribute value.

Object Type

Select the extended attribute that you wantto set for the business entity.

Attribute

Enter the value for the extended attributethat you want to apply to all the objects thatare associated with the base business entity.

Value


Select related object types optionsUse this panel to specify the object types on which you want to define the extendedattribute that you have set on the business entity.

Table 12-53 Select related object types panel options

DescriptionField

Select the object type on which you want todefine the extended attribute.

Object Type


Viewing Virtual Business ServicesIn Veritas Operations Manager, you can view all the Virtual Business Servicescurrently present in the datacenter.

You can view the following details of the Virtual Business Services in the table:

■ Name: Name of the Virtual Business Service.

■ Description: Information that you had entered when you created the VirtualBusiness Service.

Managing business entitiesViewing Virtual Business Services

282

■ Availability status: Displays the availability of the Virtual Business Servicebased upon the state of service groups in a Virtual Business Service.

Service Group StateVBSAvailabilityStatus

All service groups are in Offline state.Offline

All service groups are in Online state.Online

At least one of the service groups is in Offline or Partial state andother service groups are in Online or Partial state.

Partial

All service groups are in Offline state and at least one of the servicegroups is in Faulted state on some system(s).

Offline(Attention)

All service groups are in Online state and at least one of the servicegroups is in Faulted state on some system(s).

Online(Attention)

At least one of the service groups is Faulted on some system(s) andall the service groups form a Partial state(see Partial).

Partial(Attention)

■ State:

■ For Virtual Business Service, the state of the base objects and theirdependencies is displayed. The state is based on the faults and the risks onthe base objects and their associated objects. If these objects have faults,the state of the Virtual Business Service is displayed asFaulted. If the baseobjects and their associated objects are at risks, the state of the VirtualBusiness Service is displayed as At Risk.

■ AdminAccess: Indicates whether the logged on user has administrator accessto the hosts that are associated with the business entity.

■ LastUpdated: Date when the owner of the business entity made a configurationchange to the group.

■ Fault Management: Indicates whether fault management is configured forthe Virtual Business Service.

Use the dynamic search filter to search existing business entities in the datacenter.You can filter the Virtual Business Services list based on the health of the businessentities - Faulted, At Risk, or Healthy. You can filter the list based on the typeof the business entities - Virtual Business Service or Organization Entities.

In this view, you can perform the following operations on a business entity:

■ Create a Virtual Business Service.

283Managing business entitiesViewing Virtual Business Services

■ Create a composite Virtual Business Service.

■ Edit a Virtual Business Service.

■ Delete a Virtual Business Service.

■ Set the extended attributes for a Virtual Business Service.

■ Run the high availability fire drill for a Virtual Business Service.

■ Run the disaster recovery fire drill for a Virtual Business Service.

■ Change the security permissions of a Virtual Business Service.

To view the Virtual Business Service in Veritas Operations Manager

◆ In the Veritas Operations Manager console, click Manage>VirtualBusinessService.



Viewing Organization EntitiesIn Veritas Operations Manager, you can view all the Organization Entities currentlypresent in the datacenter.

You can view the following details of the Organization Entities in the table:

■ Name: Name of the Organization Entity.

■ Description: Information that you had entered when you created theOrganization Entity.

■ Availabilitystatus: Displays the availability of the Organization Entity basedupon the state of service groups in an Organization Entity.

Service Group StateOrganizationEntity

AvailabilityStatus

All service groups are in Offline state.Offline

All service groups are in Online state.Online

At least one of the service groups is in Offline or Partial state andother service groups are in Online or Partial state.

Partial

All service groups are in Offline state and at least one of the servicegroups is in Faulted state on some system(s).

Offline(Attention)

Managing business entitiesViewing Organization Entities

284

Service Group StateOrganizationEntity

AvailabilityStatus

All service groups are in Online state and at least one of the servicegroups is in Faulted state on some system(s).

Online(Attention)

At least one of the service groups is Faulted on some system(s) andall the service groups form a Partial state(see Partial).

Partial(Attention)

■ State:

■ For Organization Entities, the state is displayed as Healthy, At Risk, orFaulted. Healthy indicates that none of the base hosts are faulted, or atrisk. At Risk indicates that some, but not all, hosts are faulted, or at leastone base host is at risk. Faulted indicates that all the base hosts are faulted.

■ AdminAccess: Indicates whether the logged on user has administrator accessto the hosts that are associated with the business entity.

■ Last Updated: Date when the owner of the Organization Entity made aconfiguration change to the group.

Use the dynamic search filter to search existing business entities in the datacenter.You can filter the business entities list based on the health of the business entities- Faulted, At Risk, or Healthy. You can filter the list based on the type of thebusiness entities - Virtual Business Service or Organization Entities.

In this view, you can perform the following operations on an organization entity:

■ Create an organization entity.

■ Create a composite organization entity.

■ Edit an organization entity.

■ Delete an organization entity.

■ Set the extended attributes for an organization entity.

■ Change the security permissions of an organization entity.

To view the Organization Entities in Veritas Operations Manager

◆ In the Veritas Operations Manager console, click Manage > OrganizationEntities.


285Managing business entitiesViewing Organization Entities

About the makeBE scriptWith the introduction of makeBE command-line script, now Veritas OperationsManager users can perform various business entity-related operations using thecommand line. The makeBE script is packaged with the VRTSsfmh package, andyou need to use the vomadm utility to run makeBE script. The vomadm utility letsyou run various commands on Veritas Operations Manager Management Server.The makeBE script is one such command. You can run these commands in contextwith both types of business entities - Organization Entities and Virtual BusinessServices. The makeBE script is supported on Veritas Operations Manager version4.1or later.

The makeBE script lets you perform the following operations that are related tobusiness entities:

■ Create a business entity.

■ Update a business entity.

■ Delete a business entity.

■ Import business entities from a comma separated value (CSV) file. You needto ensure that the CSV file already contains the information about the objectsthat you want to add to the business entity.

■ Export the objects of a business entity to a comma separated value (CSV) file.

Note: In the high availability (HA) environment, the makeBE commands are notsupported on non-active cluster nodes (slave). In non-high availabilityenvironment, makeBE commands are not supported on the managed host.

See “Objects used in the makeBE script” on page 286.

See “makeBE script CSV file details” on page 287.

See “Creating business entities using the makeBE script” on page 290.

Objects used in the makeBE scriptThe makeBE script uses the following objects for its business entity-relatedoperations:

■ Baseobjects: These objects are typically all the objects that you use when youcreate a business entity using the Veritas Operations Manager console. Theobjects are host, database, disk group, File System, service group, enclosure,cluster, and Exchange server.

Managing business entitiesAbout the makeBE script

286

Along with the above-mentioned objects, you also need to define two moredescription parameters for the Organization Entity and the Virtual BusinessServices. They are listed below:

■ For Organization Entity: OE_description

■ For Virtual Business Service: VBS_description and AE_description

Note: The term Virtual Business Service was earlier referred to asApplication Entity in Veritas Operations Manager version 4.0 and earlier.Though Application Entity is re-packaged as Virtual Business Service, ifyou have used AE_description parameter in your existing CSV file, youcan still continue to use AE_description parameter while running themakeBE commands.

■ Security Group: You can assign a security_group to a business entity usingthe makeBE script. However, ensure that the security group is already created.

■ makeBE CSV file: The makeBE CSV file contains one or many occurrences ofthe following pattern in each line:<BE_name>,<obj_type>,<obj_id>,<oper_type>,<optional information

column>

Each line instructs themakeBE command how to manipulate the business entity.Each makeBE CSV file may contain multiple lines to create the business entity.You can use a makeBE CSV file to manipulate multiple business entities.

See “About the makeBE script ” on page 286.

makeBE script CSV file detailsThe makeBE script CSV file contains one or many occurrences of the followingpattern in each line:

<BE_name>,<obj_type>,<obj_id>,<oper_type>,<optional information

column>

The detailed information about the makeBE CSV file parameters is provided in thefollowing table:

287Managing business entitiesAbout the makeBE script

Table 12-54 makeBE script CSV file details

You can useBE_name to refer to any existing business entity or a newbusiness entity.

This parameter is common to import, export, and user-defined importoperations.

<BE_name>

Indicates the type of operation performed on the business entity.

■ I: This option is used to add an object to the business entity, orupdate if the object already exists.

■ D: This option is used to remove an object from the business entity.

These parameters are common to import, export, and user-definedimport operations.

<oper_type>

Provides the description for the business entity object.

■ <obj_type>=‘AE_description’, <obj_id>=detail description of theApplication Entity

■ <obj_type>=‘VBS_description’, <obj_id>=detail description of theVirtual Business Service

■ <obj_type>=‘OE_description’, <obj_id>=detail description of theOrganization Entity

■ <obj_type>=’security_group’,<obj_id>=Security group name

The above-mentioned parameters are common to import, export, anduser-defined import operations.

However, the following parameters are specific to import and exportoperations:

■ <obj_type>=’host’,<obj_id>=host_id in the host table

■ <obj_type>=’database’,<obj_id>=db_id in the db table

■ <obj_type>=’diskgroup’,<obj_id>=dg_id in the diskgroup table

■ <obj_type>=’filesystem’,<obj_id>=fs_id in the filesystem table

■ <obj_type>=’servicegroup’,<obj_id>=sg_id in the servicegrouptable

■ <obj_type>=’enclosure’,<obj_id>=enc_id in the array_subsystemtable

■ <obj_type>=’cluster’,<obj_id>=hc_id in the host_container table

■ <obj_type>=’exchange_server’,<obj_id>=exch_id in theexchange_server table

The following parameter is specific to the user-defined importoperation:

■ <obj_type>=’host_name_pattern’,<obj_id>=regular expressionpattern

<obj_type> and<obj_id>

Managing business entitiesAbout the makeBE script

288

Table 12-54 makeBE script CSV file details (continued)

This column is populated with the object name when the export optionis given. For the other operations, this column is ignored.

This option is common to import, export, and user-defined importoperations.

<optional

information

column>


See “Importing business entities using the makeBE script” on page 291.

See “Exporting business entities using the makeBE script” on page 292.

makeBE script parameters detailsYou can view the makeBE script-related parameters by typing the followingcommand on the Veritas Operations Manager Management Server:

vomadm makeBE --help

The command output displays three operations that you can perform to manipulatethe business entities. The supported operations are import, export, anduser_defined_import. With these commands, you also need to specify the infile(a CSV file) that contains the information about the business entity, its objects,and the type of operation you want to perform on the business entity.

vomadm makeBE [--import <infile> | --export <outfile> |

--user_defined_import <infile>]

infile: full path to the input file

outfile: full path to the output file

■ import: Use import option to create a business entity, add objects to a businessentity, and remove the objects from the selected business entity. Import optionalso lets you update and delete an existing business entity. The operation typeparameter (<oper_type>) mentioned in the CSV file determines the type ofbusiness entity operation. To add an object to the business entity, the valueof <oper_type> is set to I, and for the delete operation, it is set to D.

■ export: Use export option to export a business entity's content to a CSV file.The file can be used for the import, or verification purpose.

■ user_defined_import: Like the import option, you can use this option to addor remove business entity objects. However, this option also provides additionalflexibility for the business entity operations. For instance, you can specify<obj_type> as 'host_name_pattern' and <obj_id> as the 'regular expressionpattern'. For example, the following expression adds all the hosts starting with

289Managing business entitiesAbout the makeBE script

'vcs' to the TestBE business entity: In this example, the value of 'regularexpression pattern' is vcs.*.

'TestBE','host_name_pattern',vcs.*,'I',


Limitations of makeBE scriptThis section lists the limitations of makeBE script:

■ You cannot export a single business entity object using the makeBE script fromManagement Server.

■ If you want to associate a security group with a business entity using the makeBEscript, make sure that the security group is already existing.

■ The makeBE commands are not supported for composite business entities.


makeBE script log filesThe generated log files of the makeBE operations are listed below:

■ UNIX

■ /var/opt/VRTSsfmh/logs/vomadm.log

■ /var/VRTSsfmcs/SFMdb3.dblog

■ Windows

■ <appdirmh>/logs/vomadm.log

■ <appdircs>/logs/SFMdb3.dblog


Creating business entities using the makeBE scriptYou can create a business entity using the makeBE script. This operation issupported for both types of business entities - Organization Entity and VirtualBusiness Service. Note that the makeBE script does not provide any separatecommand to create business entity. To create a business entity, you need to usethe import option of the makeBE script. The import option uses an existing CSVfile to create a business entity. The content of the CSV file determines the businessentity's objects. For example, name of the service groups and managed hosts, theirdescriptions, and other properties.

Managing business entitiesCreating business entities using the makeBE script

290

You can create a new CSV file and import it to create a new business entity. Youcan also import an existing CSV file to update your Organization Entity or VirtualBusiness Service. In this operation, the existing business entity is overwritten bythe new CSV file content.

To create a business entity using the makeBE script

1 Log on to the Management Server as the administrator or the root user.

2 Run the following commands on Management Server:

■ For UNIX Management Server: /opt/VRTSsfmh/bin/vomadm makeBE

--import /tmp/Samplefile.csv

■ For Windows Management Server: C:\ProgramFiles\VERITAS\VRTSsfmh\bin>perl.exe vomadm makeBE --import

"C\tmp\Samplefile.csv

3 After the successful import, the business entity is displayed in the Manage> Business Entities view.

A sample CSV file used for the business entity create operation is listed below.The business entity is TestBE that contains a host, enclosure, database, disk group,and file system.

'TestBE','host','{422e85ef-33e8-9257-2be9-704ff07a9d38}','I',

'TestBE','enclosure','EMC_CLARiiON_CK200082401064','I',

'EMC_CLARiiON_CK200082401064'

'TestBE','database','MSSQL@win2k3-6\\SQL32BIT@

{0012001a-a03b-5952-0000-000038caa494}@-1107251074','I','TestDB'

'TestBE','diskgroup','{b932c8c8-b9d0-11e0-a90c-001aa03b5950}','I',

'win2k3-6-Dg0'

'TestBE','filesystem','\\?\\Volume{58ca12bd-11a6-11e0-9946-001aa03b5950}

\\','I','\\?\\Volume{58ca12bd-11a6-11e0-9946-001aa03b5950}\\'


Importing business entities using the makeBE scriptYou can import the content of an existing CSV file using the makeBE script. Thecontent of the imported CSV file determines the business entity's objects Thisoperation is supported for both types of business entities - Organization Entityand Virtual Business Service.

291Managing business entitiesImporting business entities using the makeBE script

To import a business entity using the makeBE script

1 Log on to the Management Server as the administrator.






A sample CSV file used for the business entity import operation is listed below.The business entity is TestBE that contains a database, host, service group, filesystem, and a storage enclosure. The last line of the CSV file includes businessentity description. Each object entry in the CSV file also includes its object ID.

'TestBE','database','Sybase@nbk1@sybaseha@

{00020003-bae2-42d7-0000-000083e242d7}','I','nbk1'

'TestBE','host','{564dd88a-0ae2-a9bb-7854-b50e3e0376ee}','I',

'TestBE','servicegroup','VCSAppMonHBSG@ApplicationHA_pl8dom5-',

'I','VCSAppMonHBSG'

'TestBE','filesystem','{00120015-c5f4-2b83-0000-00004a2cf9a3}

\\Device\\Harddisk0\\Partition2','I',

'{00120015-c5f4-2b83-0000-00004a2cf9a3}\\Device\\Harddisk0\\Partition2'

'TestBE','enclosure','EMC_CLARiiON_CK200082401064',

'I','EMC_CLARiiON_CK200082401064'

'TestBE','VBS_description','Full description of the Business

Entity','I',


Exporting business entities using the makeBE scriptIf you have created a business entity using the Veritas Operations Manager console,you can export the business entity-related information to a CSV file using theexport option of makeBE script.

Managing business entitiesExporting business entities using the makeBE script

292

To export a business entity using the makeBE script




--export /tmp/Samplefile.out

■ For Windows Management Server: C:\ProgramFiles\VERITAS\VRTSsfmh\bin>perl.exe vomadm makeBE --export

C\tmp\Samplefile.out

A sample CSV file generated after the business entity export operation is listedbelow. The business entity is TestBE that contains three hosts and two storageenclosures. The last line of the CSV file includes business entity description. Eachobject entry also includes its object ID. For example, each host entry includes itshost_id. For the first host entry, the object ID is422e85ef-33e8-9257-2be9-704ff07a9d38.


'TestBE','host','{4207f2c1-8538-115f-d3b0-80638d0b0f2d}','I',

'TestBE','host','{42070e20-1106-3042-99ea-428e38dea523}','I',

'TestBE','enclosure','EMC000287971357','I','EMC000287971357'

'TestBE','enclosure','EMC_CLARiiON_CK200082401064','I','EMC_CLARiiON_CK200082401064'

'TestBE','VBS_description','This is the BE description.','I',


Updating business entities using the makeBE scriptSince a business entity provides an easier method to group multiple objects, avariety of storage objects can exist in a typical business entity. Therefore, whileupdating a business entity using the makeBE script, you can perform a wide varietyof operations depending on what objects you want to add to the business entity,or remove from the business entity. For example, adding a host to the businessentity, removing the association of a business entity with a security group, adding,or removing the service groups, databases, clusters and so on. The--user_defined_import option of makeBE script lets you specify the CSV file thatcontains the necessary information to update the business entity. This operationis supported for both types of business entities - Organization Entity and VirtualBusiness Service.

293Managing business entitiesUpdating business entities using the makeBE script

To update a business entity using the makeBE script




--user_defined_import /tmp/Samplefile

■ For Windows Management Server: C:\ProgramFiles\VERITAS\VRTSsfmh\bin>perl.exe vomadm makeBE

--user_defined_import "C\tmp\Samplefile.csv

A sample CSV file used for the user_defined_import operation is listed below:


'TestBE','host','{4207f2c1-8538-115f-d3b0-80638d0b0f2d}','D',

'TestBE','host','{42070e20-1106-3042-99ea-428e38dea523}','I',

'TestBE','enclosure','EMC000287971357','D','EMC000287971357'

'TestBE','enclosure','EMC_CLARiiON_CK200082401064',

'I','EMC_CLARiiON_CK200082401064'

'TestBE','VBS_description','This is the BE description.','I',


Deleting business entities using the makeBE scriptYou can delete an existing business entity using the makeBE script. This operationis supported for both types of business entities - Organization Entity and VirtualBusiness Service. To delete a business entity, you need to use the import optionof the makeBE script. The import option uses an existing CSV file to delete abusiness entity. The <oper_type> parameter (set to D) in the CSV file indicatesthe type of operation that is performed on the business entity.

To delete a business entity using the makeBE script







Managing business entitiesDeleting business entities using the makeBE script

294

A sample CSV file used for the business entity delete operation is listed below.Note that the value of <oper_type> defined in CSV file is D. It indicates that deleteoperation is performed on the business entity upon successful import of the CSVfile.

'TestBE','VBS_description','Virtual Business Service full

description','D',



295Managing business entitiesDeleting business entities using the makeBE script

Managing business entitiesDeleting business entities using the makeBE script

296

Managing AuthenticationBrokers


■ About managing Authentication Brokers in the Veritas Operations Managerdomain

■ About managing domains associated with an Authentication Broker in VeritasOperations Manager

■ Viewing the details of the Authentication Brokers and the domains associatedwith them

■ Adding secondary Authentication Brokers to the Management Server domain

■ Refreshing the information associated with the Authentication Brokers

■ Removing the Authentication Brokers from the Veritas Operations Managerdomain

■ Configuring Lightweight Directory Access Protocol-based authentication onManagement Server

■ Removing Lightweight Directory Access Protocol or Active Directoryconfiguration from the primary Authentication Broker

■ Enabling the authentication domains associated with an Authentication Broker

■ Disabling the authentication domains associated with an Authentication Broker

13Chapter

AboutmanagingAuthenticationBrokers in theVeritasOperations Manager domain

An Authentication Broker is an intermediate registration and certificationauthority that can authenticate clients including users or services.

In Veritas Operations Manager, an Authentication Broker has one or moreauthentication domains that authenticate users.

Veritas Operations Manager contains the following types of AuthenticationBrokers:

■ Primary Authentication Broker

■ Secondary Authentication Brokers

Primary Authentication Broker is installed on Management Server. You configureit when you configure Management Server.

Note: VRTSatServer 6.0 is the primary Authentication Broker on ManagementServer. VRTSat Client 6.0 enables communication between managed hosts.

The Authentication Broker that you add to Veritas Operations Manager is knownas secondary Authentication Broker. You can add one or more SecondaryAuthentication Brokers to the Veritas Operations Manager domain.

Note: Only the users with the Domain Admin role can manage AuthenticationBrokers in Veritas Operations Manager.

Veritas Operations Manager lets you do the following:

■ Add one or more secondary Authentication Brokers to the Veritas OperationsManager domain.

■ Refresh Authentication Brokers.

■ Remove secondary Authentication Brokers from the Veritas OperationsManager domain.

You can also manage the domains that are associated with Authentication Brokersin Veritas Operations Manager.

See “About managing domains associated with an Authentication Broker in VeritasOperations Manager” on page 299.

See “Refreshing the information associated with the Authentication Brokers”on page 304.

Managing Authentication BrokersAbout managing Authentication Brokers in the Veritas Operations Manager domain

298

See “Removing the Authentication Brokers from the Veritas Operations Managerdomain” on page 305.

About managing domains associated with anAuthenticationBroker in VeritasOperationsManager

The Authentication Brokers view lets you select an Authentication Broker toview the authentication domains that are associated with it. By default, the primaryAuthentication Broker is selected. Under Domains, Veritas Operations Managerlists the authentication domains that are associated with the selectedAuthentication Broker.

Veritas Operations Manager lets you manage the authentication domains thatare associated with the Authentication Brokers. Only the users with the DomainAdmin role can manage Authentication Brokers in Veritas Operations Manager.

Veritas Operations Manager supports the authentication mechanism that isconfigured in the operating system, including Pluggable Authentication Modules(PAM), Network Information Service (NIS), or NIS+, with the exception ofmulti-factor authentication mechanisms. In addition to the native operatingsystem authentication, Veritas Operations Manager supports Lightweight DirectoryAccess Protocol (LDAP) and Active Directory (AD).

In the Veritas Operations Manager log in page, you can view the following domaintypes:

■ unixpwd

■ Network (NT) Domain

■ LDAP

See “About managing Authentication Brokers in the Veritas Operations Managerdomain” on page 298.

See “Viewing the details of the Authentication Brokers and the domains associatedwith them” on page 300.

See “Configuring Lightweight Directory Access Protocol-based authentication onManagement Server” on page 306.

See “Removing Lightweight Directory Access Protocol or Active Directoryconfiguration from the primary Authentication Broker” on page 311.

See “Enabling the authentication domains associated with an AuthenticationBroker” on page 312.

See “Disabling the authentication domains associated with an AuthenticationBroker” on page 313.

299Managing Authentication BrokersAbout managing domains associated with an Authentication Broker in Veritas Operations Manager

Viewing the details of the Authentication Brokers andthe domains associated with them

The Security Settings view lets you view the Authentication Brokers and theauthentication domains that are associated with them.

Under Authentication Brokers, you can view the list of primary and secondaryAuthentication Brokers in the Veritas Operations Manager domain. You can viewthe following details for each Authentication Broker:

Name of the Authentication BrokerBroker Name

Port number on which the AuthenticationBroker is configured to run

Port No

If you select an Authentication Broker, you can view the authentication domainsthat are associated with it under Domains. By default, the primary AuthenticationBroker is selected in the list of Authentication Brokers.

Under Authentication Brokers, you can also do the following:

■ Add a new secondary Authentication Broker to the Veritas Operations Managerdomain.

■ Remove the secondary Authentication Broker from the Veritas OperationsManager domain.

■ Refresh an Authentication Broker.

Under AuthenticationBrokers, you must select an Authentication Broker to viewthe domains that are associated with it. Under Domains, you can view the list ofthe authentication domains. You can view the following details for eachauthentication domain:

Name of the authentication domainDomain Name

Type of the authentication domainDomain Type

Displays whether the authentication domainis enabled or disabled

Status

Under Domains , you can do the following:

■ Configure LDAP on an Authentication Broker.

■ Remove the LDAP configuration from an Authentication Broker.

■ Enable the authentication domain.

Managing Authentication BrokersViewing the details of the Authentication Brokers and the domains associated with them

300

■ Disable the authentication domain.

To view the details of the Authentication Brokers and the domains associated withthem

1 Select Settings > Security.

2 Click Authentication Brokers.






Adding secondary Authentication Brokers to theManagement Server domain

The AddNewBroker wizard panel lets you add secondary Authentication Brokersto the Management Server domain. This task does not install AuthenticationBroker. By default, in the Security Settings view, Veritas Operations Managerdisplays the primary Authentication Broker.

You can use the Veritas Operations Manager console to add Authentication Brokersto the Veritas Operations Manager domain, only if you use Symantec ProductAuthentication Service version 4.3.46.0, or later versions. If you use the SymantecProduct Authentication Service version lower than 4.3.46.0, you must use thecommand-line interface to add the secondary Authentication Brokers.

Note: Only the users with the Domain Admin role can manage AuthenticationBrokers .

To add secondary Authentication Brokers

1 In the Veritas Operations Manager console, select Settings>AuthenticationBrokers.

2 In the Authentication Brokers view, click Actions > Add Broker.

301Managing Authentication BrokersAdding secondary Authentication Brokers to the Management Server domain

3 In the Add New Broker wizard panel, enter the details and click OK.

See “Add New Broker options” on page 304.

4 In the Results panel that confirms that you added a secondary AuthenticationBroker to the Management Server domain, click OK.

To add the secondary Authentication Brokers using the command-line interface onWindows

1 Run setuptrust on Management Server:

C:\Program Files\Veritas\VRTSvomer\sec\bin>vssat.bat setuptrust

-b BROKER_HOST_NAME :14545 -s low

2 Create a SQL file broker.sql in a temporary directory that contains thefollowing query:

INSERT P_BROKER_INFO

(DOMAIN_NAME,DOMAIN_TYPE,BROKER_NAME,BROKER_TYPE,BROKER_PORT,STATUS)

ON EXISTING UPDATE

VALUES('BROKER_HOST_NAME','DOMAIN_TYPE','BROKER_HOST_NAME',0,2821,0);

where, DOMAIN_TYPE is nt and BROKER_HOST_NAME is the name of thebroker host.

3 Run the following command to retrieve the Veritas Operations Managerdatabase password:

C:\Program Files\Veritas\VRTSsfmh\bin>xdbadm.exe -g -u HABDBSYNC

- c "C:\ProgramData\Symantec\VRTSvomer\db\conf"

The command displays the database password.

4 Run the following command to set the password in the ENV variable for theconsole:

set SFMDBPASSWD=DB_PASSWORD

5 Run the following command to execute the SQL query:

C:\Program Files\VERITAS\VRTSsfmcs\config\adm\db_isql.bat

HABDBSYNC C:\temp\broker.sql

6 Restart the Veritas Operations Manager console. Under Service ControlManager (services.msc), restart the Storage Manager Service.

7 Log on to the Veritas Operations Manager console and select Settings >AuthenticationBrokers to view the secondary Authentication Broker. Clickon the secondary Authentication Broker to enable the domains and createsecurity groups for users to log on from that domain.

Managing Authentication BrokersAdding secondary Authentication Brokers to the Management Server domain

302

To add the secondary Authentication Brokers using the command-line interface onUNIX

1 Run setuptrust on the Management Server:

export EAT_HOME_DIR=/opt/VRTSsfmcs/sec

export EAT_DATA_DIR=/var/opt/VRTSsfmcs/sec

/opt/VRTSsfmcs/sec/bin/vssat setuptrust -b BROKER_HOST_NAME :14545

-s low

2 Create a SQL file broker.sql in a temporary directory that contains thefollowing query:

INSERT P_BROKER_INFO

(DOMAIN_NAME,DOMAIN_TYPE,BROKER_NAME,BROKER_TYPE,BROKER_PORT,STATUS)

ON EXISTING UPDATE VALUES ('BROKER_HOST_NAME ','DOMAIN_TYPE

','BROKER_HOST_NAME ',0,2821,0);

where, DOMAIN_TYPE is unixpwd and BROKER_HOST_NAME is the nameof the broker host.

3 Run the following command to retrieve the Veritas Operations Managerdatabase password:

/opt/VRTSsfmh/bin/xdbadm -g -u HABDBSYNC -c

/var/opt/VRTSsfmcs/conf

The command displays the database password.

4 Run the following command to set the password in the ENV variable for theconsole:

export SFMDBPASSWD=DB_PASSWORD

5 Run the following command to execute the SQL query:

/opt/VRTSsfmcs/config/adm/db_isql.sh HABDBSYNC /tmp/broker.sql

6 Run the following command to restart the Veritas Operations Managerconsole:

/opt/VRTSsfmcs/bin/vomsc restart sfmcswd

7 Log on to the Veritas Operations Manager console and select Settings >AuthenticationBrokers to view the secondary Authentication Broker. Clickon the secondary Authentication Broker to enable the domains and createsecurity groups for users to log on from that domain.


303Managing Authentication BrokersAdding secondary Authentication Brokers to the Management Server domain





Add New Broker optionsUse this panel to enter the details of the secondary Authentication Broker thatyou want to add to the Management Server domain.

Table 13-1 Add New Broker panel options

DescriptionField

Fully-qualified host name or IP Address ofthe Authentication Broker host that youwant to add to Management Server domain.

Broker Hostname

Port number on which the AuthenticationBroker is configured to run.

Port No

See “Adding secondary Authentication Brokers to the Management Server domain”on page 301.

Refreshing the information associated with theAuthentication Brokers

The RefreshBroker wizard panel lets you refresh an Veritas Operations Managerauthentication broker so you can see the authentication domains that you haveadded to it.

After you refresh the authentication broker , you can go under Domains, and viewthe added authentication domains.

Managing Authentication BrokersRefreshing the information associated with the Authentication Brokers

304

To refresh the information associated with an authentication broker


2 In the Authentication Brokers view, select the authentication broker thatyou want to refresh.

3 Click Actions > Refresh Broker.

4 In the Refresh Broker wizard panel, click Yes.

5 In the Results panel that confirms the refresh, click OK.



See “Adding secondary Authentication Brokers to the Management Server domain”on page 301.

Removing theAuthenticationBrokers fromtheVeritasOperations Manager domain

The Remove Broker wizard lets you remove secondary authentication brokersfrom the Veritas Operations Manager domain. When you remove an authenticationbroker , the operation does not uninstall the authentication broker. It only removesthe authentication broker from the Veritas Operations Manager domain.

Note: You cannot remove the primary authentication broker from the VeritasOperations Manager domain.

To remove the secondary authentication brokers from the domain


2 In the Authentication Brokers view, select the authentication broker thatyou want to remove.

3 Under Authentication Brokers click Actions > Remove Broker.

4 In the RemoveBroker wizard panel to confirm whether you want to removethe authentication broker , click Yes.

5 In the Results panel that confirms that you removed the selectedauthentication brokers , click OK.

305Managing Authentication BrokersRemoving the Authentication Brokers from the Veritas Operations Manager domain



Configuring Lightweight Directory AccessProtocol-basedauthenticationonManagementServer

You can configure Lightweight Directory Access Protocol (LDAP)-basedauthentication on the primary authentication broker.

Note: By default, the LDAP-based authentication domain that you configure is inthe enabled state.

To configure LDAP-based authentication

1 Select Settings > Authentication Brokers.

2 In the Authentication Brokers view, under Domains, click Actions >Configure LDAP/AD.

3 In the LDAP/ADSettings-discoverattributesandconfigurationinformationwizard panel, enter the details and click Next.

See “LDAP/AD Settings - discover attributes and configuration informationpanel options” on page 307.

4 In the LDAP/AD Settings - configure LDAP/AD wizard panel, specify thesearch base and click Finish.

See “LDAP/AD Settings - configure LDAP based authentication options”on page 309.

5 In the Results panel that confirms that you have configured LDAP basedauthentication, click OK.



See “Removing Lightweight Directory Access Protocol or Active Directoryconfiguration from the primary Authentication Broker” on page 311.


Managing Authentication BrokersConfiguring Lightweight Directory Access Protocol-based authentication on Management Server

306



LDAP/AD Settings - discover attributes and configuration informationpanel options

Use this wizard panel to start configuring Lightweight Directory Access Protocol(LDAP)based authentication on the primary authentication broker.

Table 13-2 LDAP/AD Settings - discover attributes and configurationinformation panel options

DescriptionField

Server Information

Fully-qualified host name or IP address ofthe LDAP server.

If a secure session is configured with theLDAP server using SSL certificates, you mustenter the fully-qualified hostname thatmatches with the fully-qualified hostnamein the LDAP server certificate.

Server Name (Mandatory)

Number of the port on which the LDAPserver is configured to run.

By default, this field displays the portnumber as 389. You can edit this portnumber, if required.

Port (Mandatory)

Select this check box if the anonymousoperations are disabled on the LDAP serverand a bind user ID is required to proceedwith configuring the LDAP-basedauthentication.

Thisserverrequiresmetologon (Optional)

307Managing Authentication BrokersConfiguring Lightweight Directory Access Protocol-based authentication on Management Server

Table 13-2 LDAP/AD Settings - discover attributes and configurationinformation panel options (continued)

DescriptionField

The complete Distinguished Name (DN) ofthe user that is used to bind to the LDAPserver.

If the LDAP server being used is ActiveDirectory (AD), you can provide the DN inany of the following formats:

■ [email protected]

■ domainname\username

For example, You can provide the DN [email protected]\Administrator

For RFC 2307 compliant LDAP servers,specify complete bind DN.

For example,cn=Manager,dc=vss,dc=symantec,dc=com

The LDAP or the AD administrator canprovide you the bind user name that you canuse.

Bind User Name/DN

Password that is assigned to the bind username that you use.

Password

Select this check box to use the SecureSockets Layer (SSL) certificates to establisha secure channel between the authenticationbroker and the LDAP server.

Use Secure Sockets Layer

Location of the trusted root CA certificate ofthe vendor that issued the LDAP servercertificate.

Certificate location

Query Information


308

Table 13-2 LDAP/AD Settings - discover attributes and configurationinformation panel options (continued)

DescriptionField

User name that the system use to detect theLDAP server-related settings.

Note: You must ensure that the user namethat you enter does not contain any specialcharacters. For example, you must not enterthe special character '(' in this field.

The system determines the search basebased on the user name that you specify inthis field.

User Name (Mandatory)

Name of the user group that the system useto detect the LDAP server-related settings.

Veritas Operations Manager displays thisfield if the user does not belong to any usergroups.

Note: Make sure that the group name thatyou enter does not contain any specialcharacters. For example, you must not enterthe special character '(' in this field.

The system determines the search basebased on the group name along with the username that you have specified.

Group Name


LDAP/AD Settings - configure LDAP based authentication optionsUse this wizard panel to specify the Domain Name and the Search Base to configureLightweight Directory Access Protocol (LDAP) based authentication on the primaryauthentication broker.

309Managing Authentication BrokersConfiguring Lightweight Directory Access Protocol-based authentication on Management Server

Table 13-3 LDAP/AD Settings - configure LDAP based authentication options

DescriptionField

Displays the fully-qualified host name or IPAddress of the LDAP server that you havespecified in the LDAP/AD Settings -discover attributes and configurationinformation wizard panel.


Server Name

Unique name to identify the LDAP basedauthentication that you configure on theprimary authetication broker.

Note: In the Domain Name field, you canenter up to 32 characters.

Domain Name

Search Base

Select this option if you want to use thedefault search base that the sytem hasdetected using the information that you havespecified on the LDAP/AD Settings -discover attributes and configurationinformation wizard panel.

Use Default


310

Table 13-3 LDAP/AD Settings - configure LDAP based authentication options(continued)

DescriptionField

Select this option to specify the search baseother than the default search base.

For example, you can customize the searchbase as follows to authenticate the user(sampleuser) who belongs to theorganization (ou=HR), which is anorganization unit under ou=user:

The organization structure is given below:

ou=HR,ou=People,dc=veritas,dc=com

|-sampleuser

ou=Engg,ou=People,dc=veritas,dc=com

|-Eng1

The default search base isou=HR,ou=People,dc=veritas,dc=com

To authenticate users under ou=HR andou=Engg, set custom search base to a levelup:

ou=People,dc=symantec,dc=com

Custom


Removing Lightweight Directory Access Protocol orActive Directory configuration from the primaryAuthentication Broker

The Unconfigure LDAP wizard lets you remove Lightweight Directory AccessProtocol (LDAP) or Active Directory (AD) configuration from the primaryAuthentication Broker.

311Managing Authentication BrokersRemoving Lightweight Directory Access Protocol or Active Directory configuration from the primary Authentication

Broker

To remove LDAP or AD configuration from the primary Authentication Broker

1 In the Veritas Operations Manager console, select Settings>AuthenticationBroker.

2 In the AuthenticationBroker view, under Domains, select the authenticationdomain that you have configured as LDAP or AD.

3 Under Domains, click Actions > Unconfigure LDAP.

4 In the Results panel that confirms that you removed the authenticationdomain that is configured as LDAP or AD, click OK.




Enabling the authentication domains associatedwithan Authentication Broker

The EnableDomain wizard lets you enable one or more authentication domains.

You must enable an authentication domain to do the following:

■ Display the authentication domain on the Veritas Operations Manager loginpage.

■ Add the authentication domain to a security group.

To enable the authentication domains associated with an Authentication Broker

1 In the Veritas Operations Manager console, select Settings>AuthenticationBroker.

2 In the Authentication Broker view, under Domains, select one or moreauthentication domains that you want to enable.

3 Under Domains, click Actions > Enable Domains.

4 In the Enable Domain wizard panel, enter the details and click OK.

See “Enable Domains options” on page 313.

5 In the Results panel that confirms that you enabled the selectedauthentication domains, click OK .

Managing Authentication BrokersEnabling the authentication domains associated with an Authentication Broker

312





Enable Domains optionsUse this panel to enable the Authentication Broker that you have selected.

Table 13-4 Enable Domains panel options

DescriptionField

Name of the Authentication Domain thatyou have selected to enable.

Domain Name

Type of the Authentication Domain that youhave selected to enable.

Domain Type


Disabling the authenticationdomains associatedwithan Authentication Broker

The DisableDomain wizard lets you disable one or more authentication domains.

To disable the authentication domains associated with an Authentication Broker


2 In the Authentication Brokers view, under Domains, select one or moreauthentication domains that you want to disable.

3 Under Domains, click Actions > Disable Domains.

313Managing Authentication BrokersDisabling the authentication domains associated with an Authentication Broker

4 In the Disable Domains wizard panel, review the details and click OK.

See “Disable Domains options” on page 314.

5 In the Results panel that confirms that you disabled the selectedauthentication domains, click OK.





Disable Domains optionsUse this panel to disable the Authentication Domain that you have selected.

Table 13-5 Disable Domains panel options

DescriptionField

Name of the Authentication Domain thatyou have selected to disable.

Domain Name

Type of the Authentication Domain that youhave selected to disable.

Domain Type


Managing Authentication BrokersDisabling the authentication domains associated with an Authentication Broker

314

Managing licenses


■ About licenses

■ About Symantec licensing and pricing

■ About assigning price tiers to hosts

■ About updating the price tier information on Management Server

■ Assigning a price tier to a host manually

■ Assigning a price tier to a host automatically

■ Updating the price tier information automatically using Management Server

■ Updating the price tier information automatically using a proxy server

■ Updating the price tier information manually on Management Server

■ About license deployment policies

■ Viewing platform specific licensing and pricing information

■ Viewing the details of license deployment policies

■ Creating a license deployment policy

■ Modifying a license deployment policy

■ Updating the default virtual machine count factor

■ Removing a license deployment policy

14Chapter

About licensesTypically, if you want to check the status of your Storage Foundation licenses,you must examine each server individually. A datacenter may have many typesof hosts running a variety of software which can be a time-consuming process.In Veritas Operations Manager, you can view the real time status of the StorageFoundation product licenses deployed on the managed host .You can view hostswhich have demo, evaluation, expired licenses, or the license keys that needattention.

You can also view the following information about deployed licenses:

■ License deployment summary, summary by product, platform, edition, release,and the host deployment summary.

■ Product inventory, that is, number licenses deployed, keyless deployments,accountable deployments, the number of expired licenses, and so on.

■ Tiering information, that is, SPVU, Server, Processor, Nprocessor, and OSprice tiers.

■ Exceptions, that is the list of hosts on which licenses were not found or thelicense discovery failed.

The Product-Tier Mapping summary lets you view the products that are classifiedaccording to a specific Symantec price tier. This summary provides details of theaccountable licenses for the products that are deployed in your datacenter. Youcan view the list of licenses due for renewal and hence reduce the time that isrequired for renewals.

Licenses deployed on a managed host are discovered at an interval of 24 hours.

See “About Symantec licensing and pricing” on page 317.

See “About assigning price tiers to hosts” on page 324.


See “Viewing platform specific licensing and pricing information” on page 332.

See “Viewing the summary of product inventory” on page 350.

See “Viewing the Product-Tier Mapping summary” on page 352.

See “Viewing the summary of host-level license deployment exceptions”on page 368.

See “Viewing product details by license key” on page 362.

See “Viewing license key details” on page 364.

Managing licensesAbout licenses

316

About Symantec licensing and pricingThe storage and server management high availability products which operate onUNIX (Solaris, HP-UX, AIX), Linux and Windows must be certified to work onservers. The product certification differs from platform to platform. Certificationis how storage and server management high availability products are licensed byplatform. The price tier information is available on the Symantec OperationsReadiness Tools (SORT) Web site. You can configure Management Server to updatethe price tier information automatically according to a schedule, whenManagement Server is connected to the Internet. When Management Server isnot connected to the Internet, you can set up a proxy server to update the pricetier information automatically. You can download a script file from ManagementServer and run it on a Windows system that is connected to the Internet to extractthe text file that contains the price tier information. You can upload the text fileto Management Server to update the price tier information.

The following table describes the various types of Symantec price tiers:

Table 14-1 Types of Symantec price tiers

DescriptionPlatformssupported

Tier Type

The Veritas storage and servermanagement, high availability products onUNIX are generally licensed and priced perserver. The pricing depends on the serverprice tier to which a server is assigned. Aserver can be assigned to 14 differentserver tiers from Tier A through Tier N.Customers must pay the per-server pricefor each server that runs storage and servermanagement, high availability products.This pricing meter applies to all versionsof Veritas storage and server management,high availability products on UNIX (Solaris,HP-UX, AIX).

The available price tiers for the server tierare A, B, C, D, E, F, G, H, I, J, K, L, M, N

UNIX: Solaris,HP-UX, and IBMAIX

Server Tier

317Managing licensesAbout Symantec licensing and pricing

Table 14-1 Types of Symantec price tiers (continued)


Tier Type

The Veritas storage and servermanagement, high availability products onUNIX can be licensed and priced per tieredprocessor. The price depends on the tier towhich a processor is assigned. A processorcan be assigned to three different processortiers from Processor Tier 1 throughProcessor Tier 3. Customers must pay theper-tiered-processor price for everyprocessor that runs storage and servermanagement, high availability products.

The available price tiers for the processortier are Tier 1, Tier 2, and Tier 3.

All platformsProcessor Tier

Storage Foundation and high availability5.0 for Linux is licensed on a per-processorbasis regardless of the number of cores onthe processor. A multi-core chip with “n”cores counts as one processor. For example,each dual-core AMD Opteron processor thatruns Storage Foundation for Linux requiresone processor license.

The available price tiers for the NProcessortier are 1, 2, 3, 4, 5, 6, 7, 8 Processors.

Linux: Red Hat andNovell SUSE

NProcessor Tier

The Veritas storage and server automation,high availability products which operateon the Microsoft Windows operatingsystem are priced per server. The price alsodepends on the edition of Windows that isinstalled; for example, NT or 2000. TheStorage Foundation and high availabilityproducts on Windows do not follow aper-processor pricing meter.

The available price tiers for the operatingsystem tier are Level 1, Level 2, and Level3.

Microsoft WindowsOperation System Tier

Managing licensesAbout Symantec licensing and pricing

318

Table 14-1 Types of Symantec price tiers (continued)


Tier Type

The following are considered forcalculating SPVU for the Veritas storageand server management, high availabilityproducts on a host:

■ The operating system on the host

■ The make and the model of theprocessor

■ Number of cores per processor

All platformsSymantec PerformanceValue Unit (SPVU)

See “About the Symantec Performance Value Unit” on page 319.


See “Viewing platform specific licensing and pricing information” on page 332.

About the Symantec Performance Value UnitFrom the Storage Foundation and high availability 6.0 release, Symantec uses theSymantec Performance Value Unit (SPVU) pricing method for Storage Foundationand high availability products. The total number of SPVUs required for a specificproduct is calculated by multiplying the number of cores used by the product withthe SPVU value per core.

The SPVU per core is calculated based on the following:

■ The operating system on the host

■ The make and the model of the processor

■ The number of cores per processor

Note: Version 4.1 is the minimum version of the Veritas Operations Managermanaged host to be installed on the host to calculate the SPVU.

To calculate the SPVU for the products that run on IBM LPAR and kernel-basedvirtual machines, you need to install Veritas Operations Manager managed hostversion 5.0.

Based on these criteria, a host is assigned a specific SPVU value per core. Thenumber of cores used by the physical and the virtual hosts is different. On theproducts that are deployed on a physical host, the SPVU is calculated for the actualcores used by the products. The number of cores used by all the products are the


same on a physical host. For example, you have a physical host that has eightused cores, and you have installed Storage Foundation and Veritas Cluster Serveron this host. To calculate the SPVU for this host, all the eight used cores areconsidered for both the products. Essentially, on a physical host, the number ofused cores are the same for all the products that run on the same operating system.

For the virtualization servers, the SPVUs for the products are calculated differentlyfor various types of virtualization servers. Veritas Operations Manager cancalculate the SPVUs required for the products that are installed on the VMware,Solaris LDOM, the Solaris Zones virtualization servers, kernel-based virtualmachines, and IBM LPAR.

The SPVU for Application HA is calculated only when it is deployed on Linux andWindows virtualization platform.


See “About the Symantec Performance Value Unit for VMware virtual machines”on page 320.

See “About the Symantec Performance Value Unit for Solaris LDOM virtualizationserver” on page 321.


See “About the Symantec Performance Value Unit for IBM LPAR” on page 323.

About the Symantec Performance Value Unit for VMware virtualmachines

Veritas Operations Manager cannot calculate the Symantec Performance ValueUnits (SPVU) for the products installed on the VMware virtual machines if itcannot recognize the mapping between the VMware ESX virtualization serverand the virtual machines. To enable Veritas Operations Manager to recognize themapping between the VMware ESX virtualization server and the virtual machines,you must perform the following tasks:

■ Add the virtualization server to Veritas Operations Manager using VMwarevCenter by navigating to Settings > Virtualization.

■ Add the virtual machines separately to Veritas Operations Manager as managedhosts.


320

Note: If you add the virtual machines to Veritas Operations Manager as managedhosts before you add the VMware ESX virtualization server, it takes a maximumof 24 hours for Veritas Operations Manager to calculate the SPVUs. Similarly, ifyou add only the virtual machines to Veritas Operations Manager, and do not addthe virtualization server, Veritas Operations Manager cannot calculate the SPVUsfor the products that are installed on the virtualization server. However, VeritasOperations Manager discovers all the licenses for the products in this scenario.

When the SPVU is calculated for the products that run on the virtual machine ofa VMware ESX server, the total number of cores on the server is compared withthe total number of Virtual CPUs (vCPUs) that are allocated to the virtual machinesthat have same guest operating system and the same product. The smaller numberamong these two is the total number of the cores that need to be licensed(core-to-license) for the server. The SPVU is calculated by multiplying this numberwith the SPVU value per core.

For example, consider a VMware ESX Server that has three virtual machines, anda total number of eight cores. Two of the virtual machines use six vCPUs each andrun Storage Foundation for Windows. The total number of the vCPUs on thevirtual machine is calculated by adding 6 to 6, which is 12. To calculate thecore-to-license for the server, 12 is compared with 8 (the number of cores on thephysical VMware ESX Server). Because 8 is the smaller number, the core to licensefor the products on this VMware ESX server is 8. To find the required SPVU forthe products on this virtual machine, 8 is multiplied with the actual SPVU valueper core.





About the Symantec Performance Value Unit for Solaris LDOMvirtualization server

To enable Veritas Operations Manager to calculate the Symantec PerformanceValue Units (SPVU) for the products that are installed on an LDOM virtualizationserver, you must perform the following tasks:

■ Add the virtualization server to Veritas Operations Manager as a managedhost.


■ Add the guest domains to Veritas Operations Manager as managed hosts.

Note: If you add only the domains to Veritas Operations Manager, and do not addthe LDOM virtualization server, Veritas Operations Manager cannot calculate theSPVUs for the products that are installed on the virtualization server. However,Veritas Operations Manager discovers all the licenses on the products in thisscenario.

To calculate the SPVU for the products on a Solaris LDOM virtualization server,Veritas Operations Manager considers the total number of threads that areallocated to the logical domains (the control and the guest domains), where thesame product is installed. For example, consider a Solaris LDOM server with fourcores, with eight threads in each of the core. This server has a control domainwith 10 threads and two guest domains with 6 and 4 threads each. On all the threedomains, Storage Foundation is installed. The total number of threads are 20. Thetotal number of core-to-license is calculated by dividing 20 (total threads) by 8(thread per core), which is rounded to 3. The SPVU is calculated by multiplying 3with the SPVU value per core.

The SPVUs for the products on Solaris Zones are calculated based on the coreson the global zones. The cores on the local zones are not considered for calculatingSPVUs for the products on Solaris Zones.





About the Symantec Performance Value Unit for kernel-based virtualmachines

To calculate the Symantec Performance Value Unit (SPVU) for the products thatrun on kernel-based virtual machines (KVM), you need to install Veritas OperationsManager managed host version 5.0.

When the SPVU is calculated for the products that run on the virtual machine,the total number of cores on the server is compared with the total number ofVirtual CPUs (vCPUs) that are allocated to the virtual machines that have sameguest operating system and the same product. The smaller number among thesetwo is the total number of the cores that need to be licensed (core-to-license) for


322

the server. The SPVU is calculated by multiplying this number with the SPVUvalue per core.

For example, consider a virtual server that has three virtual machines, and a totalnumber of eight cores. Two of the virtual machines use six vCPUs each and runStorage Foundation for Windows. The total number of the vCPUs on the virtualmachine is calculated by adding 6 to 6, which is 12. To calculate the core-to-licensefor the virtual server, 12 is compared with 8 (the number of physical cores on theserver). Because 8 is the smaller number, the core to license for the products onthis server is 8. To find the required SPVU for the products on this virtual machine,8 is multiplied with the actual SPVU value per core.

When the SPVU is calculated for the products that run in the KVM clusterenvironment, the total number of vCPUs of all the virtual machines in the clusteris compared with the total number of cores on the server. The smaller numberamong these two is the total number of the cores that need to be licensed(core-to-license) for the server. The SPVU is calculated by multiplying this numberwith the SPVU value per core.

For example in a KVM cluster environment, the total number of vCPUs on all thevirtual machines in the cluster is 24 and the total number of cores is 35. Tocalculate the core-to-license, 24 is compared with 35. Because 24 is the smallernumber, the core-to-license for the products on this server is 24. To find therequired SPVU for the products in this cluster environment, 24 is multiplied withthe actual SPVU value per core.

For the products that run on KVM, and are deployed on the server as well as thevirtual machines, the total number of cores on the server are used to calculatethe SPVU.





About the Symantec Performance Value Unit for IBM LPARTo calculate the Symantec Performance Value Unit (SPVU) for the products thatrun on IBM LPAR, you need to install Veritas Operations Manager managed hostversion 5.0.

When SPVU is calculated for the products that run on IBM LPAR, the sum ofVirtual CPUs (vCPUs) is compared with the number of cores on the physical LPAR


server. The smaller number among these two is the total number of cores thatneed to licensed (core-to-license) for the server. The SPVU is calculated bymultiplying this number with the SPVU value per core

Note: The vCPUs are allocated cores in case of dedicated LPAR. They are entitledcapacity in case of capped LPAR and reserved capacity in case of uncapped LPAR.

When SPVU is calculated for the products that run on IBM LPAR in a clusterenvironment, the sum of all vCPUs of all the virtual machines in the cluster iscompared with the sum of physical cores on the LPAR server in the cluster. Thesmaller number among these two is used to calculate the license.





About assigning price tiers to hostsYou can use operating system-specific commands to find host characteristics.This includes the make and the model of the host and the processor, processortype, and the processor count. However, although you can discover hardwareinformation for most hosts, you may not have all the characteristics of a host. Inthat case, it is called an "unknown tier."

The assign price tier feature lets you assign price tiers to an unknown host. Iteliminates the need to find host characteristics manually.

You can assign a price tier to a host by selecting the server price tier, processortype price tier, processors price tier, or the Symantec Price Value Unit (SPVU)price tier. It also depends on the characteristics of the host, such as the make andthe model of the host and the processor, number of processors, and the operatingsystem.

See “Assigning a price tier to a host manually” on page 326.

Managing licensesAbout assigning price tiers to hosts

324

About updating the price tier information onManagement Server

To find the appropriate price tier or the Symantec Performance Value Unit (SPVU)for the licenses of the Storage Foundation and High Availability products that areinstalled on the managed hosts, Veritas Operations Manager requires the latestinformation on the price tiers for these products. Symantec updates the latestinformation of the price tiers on the Symantec Operations Readiness Tools (SORT)Web site. Management Server requires HTTPS connectivity with the SORT serverfor downloading this information.

The Veritas Operations Manager console provides you with various methods toupdate the price tier information on Management Server. You can use any one ofthe following methods to update the price tier information on Management Server:

■ Configure Management Server to update the latest price tier informationautomatically when Management Server is continuously connected to theInternet

■ Set up a proxy server to update the latest price tier information automaticallywhen Management Server is not connected to the Internet

■ Download a script file manually from Management Server when ManagementServer is not continuously connected to the Internet, or you cannot set up aproxy server. You must run the file on a Windows system that is connected tothe Internet to extract a text file that contains the latest information on theprice tiers, and upload the extracted text file to Management Server

The price tiers assigned to the managed hosts do not change automatically whenyou upload a new price tier file to Management Server. Manually assign the pricetier to the host using the Veritas Operations Manager console to assign a pricetier to a host or modify an existing price tier, you must

The automatic update of the price tier information on a Management Server occursaccording to the schedule set by you. By default, the price tier information isupdated on Management Server on the first day of every month.

Note:Veritas Operations Manager downloads the price tier information from theSORT Web site only if a newer version is available on the Web site.


See “Updating the price tier information manually on Management Server”on page 331.

325Managing licensesAbout updating the price tier information on Management Server

Assigning a price tier to a host manuallyYou can manually assign a price tier to a host by selecting the server price tier,processor type price tier, Nprocessors price tier, operating system price tier, orthe Symantec Price Value Unit (SPVU) price tier. Only users with domainadministrator privileges can perform this task.

To assign a price tier to a host manually

1 In the Veritas Operations Manager console, select Licenses > DeploymentSummary.

2 In the Host deployment summary table, click the number that correspondsto the Total hosts.

3 In the Hosts with licenses deployed table, select the host to assign the pricetier and do one of the following:

■ Click Actions > Assign Price Tier Manually.

■ Right-click on the selected row to display the shortcut menu, and selectAssign Price Tier Manually.

4 In the Select Price Tier panel, specify the required information, and clickNext.

See “Select Price Tier options” on page 326.

5 If you want to assign the price tier to other hosts with similar configuration,select the Assign the same tier to the other hosts that have the sameconfiguration check box.

6 In the Select hosts to set chosen tier panel, select the hosts, and click Next.

See “Select hosts to set chosen tier options” on page 328.

7 In the Assign price tier summary panel, view the summary of the price tierand the hosts that you have selected, and click Finish.

See “Assign price tier summary manually” on page 328.




Select Price Tier optionsUse this wizard panel to manually assign the latest price tier to the host on whichthe licenses are deployed.

Managing licensesAssigning a price tier to a host manually

326

Note: All the information may not apply to a host that you have selected. You canspecify the values from the drop-down boxes for the information that are applicablefor the host.

Table 14-2 Select Price Tier panel options

DescriptionField

Select the appropriate server price tier. Theserver price tiers are represented usingalphabets A through N.

The server price tier applies to the Solaris,the HP-UX, and the AIX platforms.

Server Price Tier

Select the appropriate processor type pricetier. The processor price tiers arerepresented as Tier 1, Tier 2, Tier 3, and Tier4.

The processor price tier applies to all thesupported platforms.

Processor Price Tier

Select the appropriate NProcessors pricetier. The NProcessor price tiers arerepresented using integers 1 through 8.

The NProcessor price tier applies to theLinux platform.

NProcessors Price Tier

Select the appropriate operating systemprice tier. The operating system price tiersare represented as Level 1, Level 2, and Level3.

The operating system price tier applies tothe Windows, and the virtual Windowsplatforms.

OS Price Tier

Enter the value for the SymantecPerformance Value Unit (SPVU) perprocessor core of the host.

SPVU/Core

327Managing licensesAssigning a price tier to a host manually

Table 14-2 Select Price Tier panel options (continued)

DescriptionField

Select this check box if you want to assignthe price tier to other hosts with a similarconfiguration. This check box is enabled onlyif you have hosts that have a similarconfiguration.

Note: If you select this check box, the Selecthosts to set chosen tier panel is displayed.You can select the hosts to assign the pricetier.

See “Select hosts to set chosen tier options”on page 328.

Assign thesametier to theotherhosts thathave the same configuration


Select hosts to set chosen tier optionsUse this panel to select one or more hosts with similar configuration to whichyou want to assign the price tier.

This panel is displayed only if you selected the Assign the same tier to the otherhosts thathave the sameconfiguration check box in the SelectPriceTier panel.


Assign price tier summary manuallyUse this panel to review your selections.


Assigning a price tier to a host automaticallyYou can assign price tiers to a single host or multiple hosts automatically in VeritasOperations Manager using the uploaded price tier information. Only users withdomain administrator privileges can perform this task.

Managing licensesAssigning a price tier to a host automatically

328

To assign a price tier to a host automatically


2 In the Host deployment summary table, click the number that correspondsto the Total hosts.

3 In the Hostswith licensesdeployed table, select the hosts to assign the pricetier and do one of the following:

■ Click Actions > Assign Price Tier Automatically.

■ Right-click on any selected row to display the shortcut menu, and selectAssign Price Tier Automatically.

4 In the Automatically calculate tier information panel, view the list of hoststhat you have selected. Click OK.




Assign the price tier summary automaticallyUse this panel to review your selections.

See “Assigning a price tier to a host automatically” on page 328.

Updating the price tier information automaticallyusing Management Server

You can configure Management Server to update the price tier informationautomatically when Management Server is continuously connected to the Internet.Also, you can set a schedule for the automatic update of price tier information onManagement Server. By default, the automatic update of the price tier informationoccurs on the first day of every month at 00.00 hours.

To update the price tier information automatically using Management Server


2 In Download Schedule, select the Price Tier Information check box andspecify the day of the month and the time when you want to update the pricetier information.


329Managing licensesUpdating the price tier information automatically using Management Server

See “Updating the price tier information automatically using a proxy server”on page 330.


Updating the price tier information automaticallyusing a proxy server

You can configure Management Server to connect to the SORT Web site and updatethe price tier information automatically when Management Server is continuouslyconnected to the Internet. When Management Server is not connected to Internet,you can use a proxy server to update the price tier information automatically.Also, you can set a schedule for the automatic update of price tier information onManagement Server. By default, the automatic update of the price tier informationoccurs on the first day of every month at 00.00 hours.

To update the price tier information automatically using a proxy server


2 Enter the information in the fields as follows:

■ In the ProxyServer field, enter the name or IP address of the proxy server.

■ In the ProxyServerPort field, enter the port number of the proxy server.

■ In the Proxy User field, enter the user name that you use to access theproxy sever.

■ In the Proxy Password field, enter the password that you use to accessthe proxy sever.

3 In Download Schedule, select the Price Tier Information check box andspecify the day of the month and the time when you want to update the pricetier information.


See “Updating the price tier information automatically using Management Server”on page 329.


Managing licensesUpdating the price tier information automatically using a proxy server

330

Updating the price tier information manually onManagement Server

You can update the price tier information manually when Management Server isnot connected to the Internet, or you cannot set up a proxy server to access theSORT Web site. To do this, you must download the pricetier.vbs script file fromManagement Server and run it on a Windows system that has Internet connectivityto extract the text file that contains the latest information on the price tiers. Youmust copy this text file to the system where Management Server is running andmanually upload this text file.

You can navigate to the Monitor>Tasks to view the status of the price tier uploadtask.

Note: You must use a Windows system to perform this operation.

To update the price tier information manually on Management Server


2 In the Manual Download Settings section, click Price Tier InformationDownload.

3 Click Download to download the pricetier.vbs script.

4 Copy the pricetier.vbs file to a Windows system that has Internetconnectivity.

5 Run the following command to extract the text file that contains theinformation on the price tiers:

cscript /NoLogo pricetier.vbs

Alternatively, you can double-click the script file to extract the text file. Thepricetier.txt file is generated in the folder where you have downloadedthe pricetier.vbs script file.

6 Copy the text file to the system where Management Server is running.

7 In the console, under Price Tier Information Download, click Browse toselect the pricetier.txt file.

8 Click Upload.



331Managing licensesUpdating the price tier information manually on Management Server

About license deployment policiesVeritas Operations Manager lets you create license deployment policies to managethe license deployment in the datacenter.

You can define a risk threshold value and a fault threshold value for a specificlicense. If the number of licenses that you have deployed in the datacenter exceedthe risk threshold value, Veritas Operations Manager generates a warning. Thealert is also generated if the number of licenses that are deployed exceed the faultthreshold value. You can view alerts in the Veritas Operations Manager console.

See “Viewing the details of license deployment policies” on page 333.

See “Creating a license deployment policy” on page 335.

Viewing platform specific licensing and pricinginformation

Veritas Storage and Server Management High Availability products on UNIX(Solaris, HP-UX, and AIX) are typically licensed and priced on a per-tiered-servermeter, regardless of the number of domains on the server. Starting with UxRT5.0, UxRT products are sold on a per-tiered-server pricing meter or aper-tiered-processor pricing meter.

Licenses for UNIX products are priced in the following ways:

■ Per tiered server meter/pricingVeritas Storage and Server Management, High Availability products on UNIXare generally licensed and priced per server. The per-server price depends onthe server price tier that a server is assigned to. A server can be assigned toone of 13 server tiers (Tier 1A through Tier 4D). You must pay the per-serverprice for each server running Storage and Server Management, HighAvailability products. This pricing meter applies to all versions of VeritasStorage and Server Management, High Availability products on UNIX (Solaris,HP-UX, and AIX).

■ Per tiered processor meter/pricing (UxRT 5.x only)Starting with UxRT 5.0, Veritas Storage, and Server Management, HighAvailability products on UNIX can be licensed and priced per tiered processor.The per-tiered-processor price depends on the processor price tier that aprocessor is assigned to. A processor can be assigned to one of three processortiers (Processor Tier 1, 2, or 3). You must pay the per-tiered-processor pricefor every active processor running Storage and Server Management, HighAvailability products.

Managing licensesAbout license deployment policies

332

Note: Storage and Server Automation, High Availability for Linux is licensed ona per-processor basis, regardless of the number of cores on the processor. Amulticore chip is considered one processor. For example, each dual-core AMDOpteron processor running Storage Foundation for Linux requires one processorlicense.

Note: Storage and Server Automation High Availability products running on theMicrosoft Windows operating system are priced per server, according to theinstalled Windows edition, for example, Windows NT or Windows 2000. Thepricing is not based on the server's processor capacity.

To view platform specific licensing and pricing information

1 In the Veritas Operations Manager console, select Licenses>TierInformation.

2 To view licensing and pricing information specific to a platform, click one ofthe following tabs:

■ Solaris

■ HP-UX

■ AIX

■ Linux

■ Windows


Viewing the details of license deployment policiesIn the License deployment policies view, you can view the following details ofthe license deployment policies that you have created in Veritas OperationsManager:

■ Name: Name of the license deployment policy.

■ Business Entity: The name of the applied business entity to the deploymentpolicy. It is displayed only when you have applied a business entity to thedeployment policy when you created the deployment policy.

■ Platform: The platform based on which the licenses are deployed while creatingthe deployment policy.

■ Virtual Machine: Indicates whether the deployment policy is applied to avirtual machine.

333Managing licensesViewing the details of license deployment policies

■ Product: The Storage Foundation product for which you have created thedeployment policy.

■ ProductEdition: The edition of the Storage Foundation product for which youhave created the deployment policy.

■ Version: The version of the Storage Foundation product for which you havecreated the deployment policy.

■ Tier Type: The tier type for the deployment policy. For example, total SPVU,processor, server, NProcessors, and the operating system.

■ Tier: The tier value for the deployment policy.

■ Risk Threshold: The lower threshold value for the deployment policy.

■ Fault Threshold: The higher threshold value for the deployment policy.

■ #Deployments SPVU: The policy deployment count.

In the License deployment policies table, the license deployment policy for whichthe licenses have exceeded the Fault Threshold value is highlighted in red. Therow highlighted in yellow, represents the license deployment policy for which thelicenses have exceeded the Risk Threshold value.

In this view, you can perform the following operations:

■ Create the license deployment policy.

■ Change thresholds for license deployment policy.

■ Remove the license deployment policy.

You can enter one of the following in the Search text box at the top of the leftpanel to filter the table:

■ Policy name

■ Product name

You can filter the License deployment policies table based on the following:

■ Platform on which the license is deployed

■ Policies that are deployed on the virtual machine

■ Violation type of the policy

■ Edition of the Storage Foundation product

■ Version of the Storage Foundation product

Managing licensesViewing the details of license deployment policies

334

To view the details of license deployment policies

1 In the Veritas Operations Manager console, select Licenses > DeploymentPolicy.

2 In the License deployment policies table, review the details of the licensedeployment policies.


See “Removing a license deployment policy” on page 342.

See “Modifying a license deployment policy” on page 338.

Creating a license deployment policyUsing the Veritas Operations Manager console, you can create a license deploymentpolicy that lets you receive various types of alerts on the deployment of licensesin the datacenter.

To create a license deployment policy


2 In the License deployment policies view, click Actions > Create Policy.

3 In the Create license deployment policy wizard panel, enter the details andclick Next.

See “Create license deployment policy options” on page 335.

4 In the DeploymentPolicy Summary wizard panel, view the summary of thedetails that you have entered and click Finish.

See “Deployment Policy Summary panel” on page 338.

5 In the Results panel that confirms the creation of the deployment policy,click OK.



Create license deployment policy optionsUse this wizard panel to create a license deployment policy.

335Managing licensesCreating a license deployment policy

Table 14-3 Create license deployment policy panel options

DescriptionField

Specify the name of the deployment policy.You can use the name to identify thedeployment policy later. For example, thename of the policy helps you identify thepolicy in an alert message.

Note: In Veritas Operations Manager 3.1 orlater, you can identify the policies using thepolicy names. The policies that were createdusing the earlier versions of VeritasOperations Manager does not contain policyname. However, you can add names to suchpolicies when you modify them using theChange Threshold wizard panel. You canonly change the lower and the higherthreshold values for a policy that has a policyname.

Name

Choose the platform based on which thelicenses are deployed.

Platform

Choose one of the following price tier typesbased on the platform on which the licensesare deployed:

■ Server

■ Processor

■ NProcessors

■ OS

■ Total SPVUs

Here is the list of platforms and their tiertypes:

■ Linux - Processor and NProcessor pricetiers

■ Solaris, HP-UX, and AIX - Server andProcessor price tiers

■ Virtual Linux, Solaris, HP-UX, and AIX -Processor price tier

■ Windows and virtual Windows -Processor and OS price tiers

Tier Type

Managing licensesCreating a license deployment policy

336

Table 14-3 Create license deployment policy panel options (continued)

DescriptionField

Choose the price tier based on the platformthat you choose.

The following list explains the tier types andthe price tiers for them:

■ Processor tier - Tier 1, Tier 2, Tier 3, andTier 4.

■ NProcessor tier - Integers 1-8.

■ Server tier - Alphabets A-N.

■ OS tier - Level 1, Level 2, and Level 3.

Note: This field does not apply to the SPVUtier type.

Price Tier

The Storage Foundation product for whichyou want to create a deployment policy.

If you choose the Windows platform, youcan choose any of the following products:

■ Storage Foundation for Windows

■ Storage Foundation HA for Windows

■ Storage Foundation HA/DR for Windows

Product

Choose the edition of the product for whichyou want to create the deployment policy.

Product Edition

Choose the version of the product for whichyou want to create the deployment policy.

Version

Enter the number of license deployments forwhich Veritas Operations Manager mustgenerate a warning.

If you have selected SPVU as the tier type,you must specify the number of SPVUs inthis field. Veritas Operations Manager raisesa warning alert when the total number ofSPVUs for the product crosses this thresholdlevel.

Risk threshold

337Managing licensesCreating a license deployment policy

Table 14-3 Create license deployment policy panel options (continued)

DescriptionField

Enter the number of license deployments forwhich Veritas Operations Manager mustgenerate an alert. You must verify the licensedeployments in your datacenter .

If you have selected SPVU as the tier type,you must specify the number of SPVUs inthis field. Veritas Operations Manager raisesa fault alert when the total number of SPVUsfor the product crosses this threshold level.

Fault threshold

Select this check box if you want to associateone or more business entities with the policy.

Do you wish you apply Business Entity tothe policy?


Deployment Policy Summary panelUse this panel to view the details of the information that you have provided inthe Create license deployment policy options panel.


Modifying a license deployment policyYou can modify the low watermark and high watermark values for a licensedeployment policy that you have created.

Note: In Veritas Operations Manager 3.1, or later, you can identify the policiesusing the policy names. The policies that were created using the earlier versionsof Veritas Operations Manager does not contain policy name. However, you canadd names to such policies when you modify them using the Change Thresholdwizard panel. You can only change the lower and the higher threshold values fora policy that has a policy name.

To modify a license deployment policy


2 In the License deployment policies view, select the check box for thedeployment policy that you want to modify and click Change Threshold.

Managing licensesModifying a license deployment policy

338

3 In the Change thresholdof licensedeploymentpolicy wizard panel, modifythe values in the Lowthreshold and Higher threshold fields as required andclick Next.

See “Change thresholds of license deployment policy options” on page 339.

4 In the DeploymentPolicy Summary wizard panel, view the summary of thedetails that you have entered and click Finish.

See “Deployment Policy Summary (modify) options” on page 341.

5 In the Results panel that confirms the creation of the deployment policy,click OK.



Change thresholds of license deployment policy optionsUse this wizard panel to modify the Lower threshold and the Higher thresholdvalues that you have defined for a license deployment policy.

If the policy that you want to edit has no name, you can provide a name to thepolicy in this panel.

Table 14-4 Change thresholds of license deployment policy panel options

DescriptionField

Displays the name of the policy that youhave provided.

If the policy that you want to edit has noname, you can provide a name to the policyin this field.

Note: In Veritas Operations Manager 3.1 orlater, you can identify the policies using thepolicy names. The policies that were createdusing the earlier versions of VeritasOperations Manager does not contain policyname. However, you can add names to suchpolicies when you modify them using theChange Threshold wizard panel. You canonly change the lower and the higherthreshold values for a policy that has a policyname.

Name

339Managing licensesModifying a license deployment policy

Table 14-4 Change thresholds of license deployment policy panel options(continued)

DescriptionField

Displays the platform that you chose whenyou create the license deployment policy.You cannot edit this field.

Platform

Displays the selection that you have madewhen you create the license deploymentpolicy. You cannot edit this field.

Virtual machine

Displays the tier type that you chose whenyou create the license deployment policy.You cannot edit this field.

Tier Type

Displays the Price Tier that you chose whenyou create the license deployment policy.You cannot edit this field.

Price Tier

Displays the Storage Foundation productthat you chose when you create the licensedeployment policy. You cannot edit this field.

Product

Displays the edition of the StorageFoundation product that you chose whenyou create the license deployment policy.You cannot edit this field.

Product Edition

Displays the version of the StorageFoundation product that you chose whenyou create the license deployment policy.You cannot edit this field.

Version

Modify the number of license deploymentsfor which Veritas Operations Manager mustgenerate a warning.

Lower threshold

Modify the number of license deploymentsfor which Veritas Operations Manager mustgenerate an alert. You must verify the licensedeployments in your datacenter .

Higher threshold

Displays the business entities that areassociated with the policy.

Business Entity


Managing licensesModifying a license deployment policy

340

Deployment Policy Summary (modify) optionsUse this panel to view the details of the information that you have provided inthe Changethresholdsof licensedeploymentpolicyoptions panel. You can viewthe Low watermark and the High watermark values that you have modified.


Updating the default virtual machine count factorTo update the default factor for counting the licenses that are deployed on oneor more virtual systems, you can use the Update counting factor for virtualenvironment wizard panel.

Currently, the default factor for the Windows virtual host is four. Symantec countthe licenses that are deployed on four virtual machines as one license. The licensesthat are deployed on two UNIX virtual machines are counted as one license. ForUNIX, the default factor is two.

To update the default virtual machine count factor

1 Select Licenses > Deployment Summary.

2 In the License Deployment Summary view, click Product-Tier Mapping.

3 In the left-side panel, under All Tasks, click Update counting factor forvirtual environment.

4 In the Updatecountingfactorforvirtualenvironment wizard panel, updatethe default count for UNIX or the Windows system , and click OK.

See “Update counting factor for virtual environment options” on page 341.

5 In the Result panel that confirms the action, click OK.

Update counting factor for virtual environment optionsUse this panel to update the default factor that Symantec uses for counting thelicenses that are deployed on one or more virtual machines.

Table 14-5 Update count factor for virtual environment options

DescriptionField

Choose the appropriate number from thedrop-down list.

By default, the current factor for the UNIXvirtual machine is selected.

Factor for UNIX virtual machine

341Managing licensesUpdating the default virtual machine count factor

Table 14-5 Update count factor for virtual environment options (continued)

DescriptionField

Choose the appropriate number from thedrop-down list.

By default, the current factor for theWindows virtual machine is selected.

Factor for Windows virtual machine

See “Updating the default virtual machine count factor” on page 341.

Removing a license deployment policyYou can remove a license deployment policy that you no longer require.

To remove a license deployment policy


2 In the License deployment policies view, select the check box for thedeployment policy that you want to remove and click Actions > RemovePolicy.

3 In the VeritasOperationsManager-Removedeploymentpolicy panel, clickYes.




Managing licensesRemoving a license deployment policy

342

Viewing deploymentinformation


■ About License Deployment detailed view

■ Viewing the License Deployment Summary view

■ Viewing the summary of product inventory

■ Viewing the Product-Tier Mapping summary

■ Viewing a product overview

■ Viewing hosts with product license deployed

■ Viewing the evidence details of a feature

■ Viewing the overview of a host

■ Viewing the overview of the licenses information for a host

■ Viewing product details by license key

■ Viewing license key details

■ Viewing the details of the mapping between the licenses and hosts

■ Viewing License-Host Mapping details

■ Viewing the summary of host-level license deployment exceptions

■ Viewing the VOM Entitlement Report

■ Scoping a license deployment view using business entities

15Chapter

About License Deployment detailed viewYou can view license deployment detailed reports for platform, release, edition,hosts, and licenses. In addition, you can view the following license deploymentreports:

Use the Exceptions tab to review host-level deployment issues. The Exceptionstab helps you to determine if any hosts have an invalid license. You can viewhost-level exceptions that are not shown on the Product Inventory tab, such asmultiple or higher version licenses.

In the Overview view, you can view a product’s name, edition (for example,Enterprise, Standard), platform (for example, SunOS, Linux, AIX), and version(for example, 4.1, 5.0). You can also view the price tier, the number of hosts, thenumber of licenses, the invalid licenses, the expired licenses, and licenses whichneed verification.

You can also view product details by host name and license key.

■ Product details by host nameView details including the platform, operating system type, model, processortype, number of processors, match type, number of licenses, number of invalidlicenses, and product evidence. The details also provide tier information suchas the server tier, the processor tier, the number of processor tier, and theoperating system tier.

■ Product details by license keyView details including the product name, platform name, license key serialnumber, edition, version, type, number of hosts, and the features that areenabled in the license key.

Under Product Evidence, you can click the icon to view details of the featuresthat are enabled in the license key. ProductEvidence details also provide evidenceof the features on the host. You can view the product name and product versionnumber of the products that are installed on the host. You can also view name ofthe enabled features, the status of enabled features, the product name to whichthe feature belongs, the package, the product marker file, and the number ofobjects.

Note: The version of the product that you have installed may be different fromthe version of the product for which you have the license.

See “Viewing the License Deployment Summary view” on page 345.

Viewing deployment informationAbout License Deployment detailed view

344

Viewing the License Deployment Summary viewThe License Deployment Summary view displays the following:

■ License deployment summary table

■ Summary by product chart

■ Summary by Platform chart

■ Summary by Edition chart

■ Summary by Release chart

■ Host deployment summary table

Note: From the License Deployment Summary view, you can scope the licensedeployment views for the business entities using Change scope available on thetop-left corner of the page.

The License deployment summary table displays the following information:

Total number of license deployed in thedatacenter. Click the number to view thedetails of the mapping between the deployedlicenses and the hosts.

Total deployments

The total number of accountable deployedlicenses.

Click the number to view the details of themapping between the deployed licenses andthe hosts.

See “About accountable deployed licenses”on page 349.

Accountable deployments

The number of keyless licenses that aredeployed in the datacenter. Click the numberto view the details of the keylessdeployments.

Keyless deployments

The number of licenses that are deployed onthe VMware virtual machines in thedatacenter. Click the number to view thedetails of the licenses deployed on the virtualmachines.

Deployments on Virtual Machines

345Viewing deployment informationViewing the License Deployment Summary view

The number of unique licenses that aredeployed in the datacenter. Click the numberto view the details of the unique licenses.

Unique licenses

The number of expired licenses in thedatacenter. Click the number to view thedetails of the expired licenses.

Expired licenses

Deployment policies that are violated. Clickthe number to view the details of the violateddeployment policies.

Violated deployment policies

The License Deployment Summary view displays the following bar charts:

This bar chart displays the number oflicenses that are deployed in the datacenterfor each Storage Foundation and highavailability product. Click the bar chart toview the details under the Product Inventorytab. Also, this bar chart displays the totallicense deployment and the expired licensedeployments.

The Others category in this bar chartrepresents the number of licenses forCoreTech and CC Stor.

Note: In the bar charts, the green colorrepresents valid licenses and the red colorrepresents expired licenses. The number oflicenses that are displayed on the chart isequal to the total number of licenses that aredeployed in the datacenter.

Summary by product

Viewing deployment informationViewing the License Deployment Summary view

346

This bar chart displays the number ofproduct licenses that are deployed in thedatacenter for the following platforms:

■ Linux

■ Sun OS

■ AIX

■ HP-UX

■ Windows.

Click the bar chart to view the details underthe Product Inventory tab.

Note: The number of licenses that aredisplayed on the chart is equal to the totalnumber of licenses that are deployed in thedatacenter.

Summary by platform

This bar chart displays the number ofproduct licenses that are deployed in thedatacenter for the following editions:

■ Basic

■ Standard

■ Enterprise

■ Others.


The Others category in this bar chartrepresents the number of licenses that donot belong to the Basic edition, Standardedition, or the Enterprise edition categories.


Summary by edition


This bar chart displays the number ofproduct licenses that are deployed in thedatacenter for the following releases ofStorage Foundation:

■ 4.0

■ 4.1

■ 4.2

■ 4.3

■ 5.0

■ 5.1

■ 6.0

■ Others.


The Others category in this bar chartrepresents the number of licenses that donot belong to the releases 4.0, 4.1, 4.2, 4.3,5.0, 5.1, and 6.0.


Summary by release

The Host deployment summary table displays the following information:

The number of hosts in the datacenter onwhich the product licenses are deployed.Click the number in this column to view thedetails of the hosts.

Total hosts

The number of virtual hosts in thedatacenter on which the product licenses aredeployed. Click the number in this columnto view the details of the virtual hosts.

Virtual hosts

The number of hosts on which the keylesslicenses are deployed. Click the number inthis column to view the details of the hoststhat contain keyless licenses.

Hosts with keyless licenses

The number of hosts that contain expiredDemo licenses. Click the number in thiscolumn to view the details of the hosts thatcontain the invalid licenses.

Hosts with expired licenses

Viewing deployment informationViewing the License Deployment Summary view

348

Hosts having deployed licenses which haveoverlapping features. These licenses can beconsolidated.

For example, if Storage Foundation forVeritas Volume Replicator Standard editionand Storage Foundation High AvailabilityEnterprise edition is installed on a host.

The license for Storage Foundation VeritasVolume Replicator can be consolidated withStorage Foundation High Availability withVeritas Volume Replicator license.

Needs Attention

The exception counts represent the numberof hosts that belong to the exceptioncategory. The licenses for a StorageFoundation and Storage Foundation-HA canmove to this state if:

■ The licenses are not found on the hosts

■ The license deployment discovery failsto run on the hosts

■ The license deployment discovery on thehosts is still in progress

Click the number to go to the exceptionsdetails page.

Exceptions

To view the License Deployment Summary

◆ In the Veritas Operations Manager console, select Licenses > DeploymentSummary.


About accountable deployed licensesA deployed license is accountable based on factors such as, the type of the license,the edition, the version, and the feature set of the license.

When a single license is deployed on a host, that license is always marked asaccountable.

Consider the following situations in which a host has multiple redundant licensesfor the same product, but either the version or the edition is different:

■ If a host has multiple licenses for the same product with different editions,but same versions, the license with highest edition is marked as accountable.For example, if Storage Foundation version 5.0 Standard edition and Storage


Foundation version 5.0 Enterprise edition are deployed on the host, then SorageFoundation Enterprise edition is marked as accountable.

■ If a host has multiple licenses for the same product with different versions,but same editions, the version of the corresponding package is considered tomark the license as accountable. For example, if you have deployed StorageFoundation 5.0 Standard and Storage Foundation 5.1 Standard on one of yourhosts, Storage Foundation 5.0 Standard license is marked as accountable ifVRTSvxvm 5.0 is installed on the host.

■ If a host has multiple license for the same product with different versions anddifferent editions, then the license with highest edition is marked asaccountable. For example, if Storage Foundation version 4.1 Enterprise andStorage Foundation version 5.0 Standard are deployed then, Storage Foundation4.1 Enterprise is accountable.

When a host has multiple products deployed, with different versions, differenteditions, then the license for which product evidence is found is marked asaccountable. Else the product with highest license is marked as accountable.

The overlapping of feature set of the licenses also determines licenseaccountability. For example if Storage Foundation for Veritas Volume ReplicatorStandard edition and Storage Foundation High Availability Enterprise edition isinstalled on a host, then both the licenses are marked as accountable, and the hostis marked as "Needs Attention".

All point product licenses, for example ApplicationHA licenses or Database licensesare always marked as accountable.


Viewing the summary of product inventoryThe Product Inventory view lets you view various details of a product, such as thetotal license deployments, the keyless deployments, the number of expired licenses,the version, the edition and so on.

Under the Product Inventory tab, you can view the following information:

Table 15-1 Product Inventory view

DescriptionField

Name of the product, for example, StorageFoundation or Veritas Cluster Server.

Product

Platform on which the product is installed,for example, Linux or AIX.

Platform

Viewing deployment informationViewing the summary of product inventory

350

Table 15-1 Product Inventory view (continued)

DescriptionField

Edition of the product, for example,Enterprise or Standard.

Product Edition

Type of the license, for example, Permanentor Demo.

Type

Version of the product.Release

Number of hosts on which the product hasbeen installed. You can click the number inthis column to view the details in the Hostshaving license deployed table.

Number of hosts

Number of licenses deployed for the product.You can click the number in this column toview the details in the Licenses-HostMapping table.

License deployments

The total number of accountable deployedlicenses.

Accountable deployments

Number of keyless licenses for the product.You can click the number in this column toview the details in the Licenses-HostMapping table.

Keyless deployments

Number of licenses that are deployed onmultiple hosts. You can click the number inthis column to view the details in the LicenseDeployed table.

Number of licenses

Number of expired licenses. You can clickthe number in this column to view the detailsin the License Deployed table.

Expired Licenses

You can enter the product name in the Search text box at the top of the left-sidepanel to filter the Inventory table

Also, the left-side panel displays the following categories that lets you filter theInventory table:

■ Platform

■ Edition

■ Release

351Viewing deployment informationViewing the summary of product inventory

Under each category, you can use the options to filter the table.

To view the Product Inventory summary


2 In the Deployment Summary view, click the Product Inventory tab.


See “About accountable deployed licenses” on page 349.

Viewing the Product-Tier Mapping summaryThe Product-Tier Mapping summary lets you view the products that are classifiedaccording to a specific Symantec price tier. This view displays only the accountablelicenses for the products that are deployed in your datacenter.

Symantec uses the following price tiers:

■ SPVU price tierThe price is based on the number of cores on the host.See “About the Symantec Performance Value Unit” on page 319.

■ Server price tierThe price is based on the make and model of the server. For example, theper-tiered-server meter is used to price and license the Veritas Storage andServer Management, High Availability products on UNIX (Solaris, HP-UX, andAIX). The price is independent of the number of domains available on theserver. You can sell UxRT products with the per-tiered-server-pricing meteror with the per-tiered-processor-pricing meter.

■ Processor price tierThe price is based on the processor type. For example, Veritas Storage andServer Management, High Availability products on UNIX can be licensed andpriced per tiered processor. The per-tiered-processor price depends on theprocessor price tier to which a processor.

■ NProcessor price tierThe price is based on the number of processors. For example, Storage andServer Automation, High Availability products on Linux are licensed on aper-processor basis. This price does not depend on the number of coresavailable on the processor. A multicore chip with “n” number of cores countsas one processor. For example, a dual-core AMD Opteron processor that runsStorage Foundation for Linux requires one processor license.

■ Operating system (OS) price tier

Viewing deployment informationViewing the Product-Tier Mapping summary

352

The price is based on the installed operating system. For example, Storage andServer Automation, High Availability products on Microsoft Windows arepriced per server. The price depends on the edition of Windows that is installed;for example, NT or 2000. The price does not depend on the processor capacityof the server.

Also, Veritas Operations Manager displays the products that are not based onSymantec price tiers in the Unknown column.

The following table explains the Symantec price tiers that apply to the hosts usingvarious operating systems:

Table 15-2 Price tier - Operating system mapping

NProcessortier

OS tierProcessor tierServer tierOperatingsystem

Yes-Yes-Linux

--YesYesSolaris, AIX, andHP-UX

--Yes-Virtual Linux

Virtual Solaris

Virtual AIX

Virtual HP-UX

-YesYes-Windows

-YesYes-Virtual Windows

In the Deployments by SPVU Price Tier table, you can view the following:

■ Product name

■ Platform

■ Product edition

■ Product version

■ License type

■ Total number of the Symantec Performance Value Unit (SPVU) required forthe product

In the Deployments by Server Price Tier table, you can view the following:

■ Product name

■ Platform

353Viewing deployment informationViewing the Product-Tier Mapping summary

■ Product edition

■ Version

■ License type

■ Server price tier details

In the Deployments by Processor Type Price Tier table, you can view thefollowing:

■ Product name

■ Platform

■ Product edition

■ Product release

■ Processor type price tier details.

In the DeploymentsbyNProcessorsPriceTier table, you can view the following:

■ Product name

■ Platform

■ Product edition

■ Version

■ Type

■ NProcessors price tier details.

In the Deploymentsby InstalledOSPriceTier table, you can view the following:

■ Product name

■ Platform

■ Product edition

■ Version

■ Operating system price tier details.

In the Application HA Pricing table, you can view the following:

■ Product name

■ Platform

■ Product edition

■ Release

■ Product type

Viewing deployment informationViewing the Product-Tier Mapping summary

354

■ Number of deployments

To view the Product-Tier Mapping summary


2 In the LicenseDeploymentSummary view, click the Product-TierMappingtab.


Viewing a product overviewThe Product Overview view displays the following information:

■ Product name

■ Edition (for example, Enterprise or Standard)

■ Platform (for example, SunOS, Linux, or AIX)

■ Version (for example, 4.1, or 5.0)

■ Price tier

■ Number of hosts

■ Number of licenses

■ Expired licenses

■ Licenses that need verification

You can also review the following tabs:

■ Hosts

■ Licenses

■ Licenses-Hosts Mapping

To view a product overview


2 In the License Deployment Summary view, click Product Inventory.

3 In the Inventory view, under Product, click the product name.

See “About License Deployment detailed view” on page 344.


355Viewing deployment informationViewing a product overview

Viewing hosts with product license deployedIn the Hosts with licenses deployed table, you can view the following details ofthe hosts in the datacenter on which the licenses are deployed:

■ Host Name: The name of the host.

■ Platform: The platform of the host.

■ OS: The version of the operating system.

■ Virtual Machine: Indicates whether the host is a virtual machine.

■ Server Tier: The server price tier that is assigned to the host. This column isapplicable only to the hosts that run on Solaris, AIX, or HP-UX.

■ SPVU/Core: Symantec Performance Value Unit per processor core.

■ Processor Tier: The processor price tier that is assigned to the host.

■ NProcessor Tier: The NProcessor price tier that is assigned to the host. Thiscolumn is applicable only to the Linux hosts.

■ OS Tier: Operating system tier.

■ Match Type: Indicates the way the tier was assigned to the host.

■ Number of Licenses: The total number of licenses.

■ Number of Expired Licenses: The total number of expired licenses.

■ Number of Keyless Licenses: The total number of keyless licenses.

■ Product Evidence: Click the icon to view the details of the features that thelicense key enables. You can view the name of the products that are installedon the host. You can view the name of the enabled features and the usage ofthe feature. You can also view the number of storage objects that are associatedwith the feature, the package, and the product marker file details.

In this view, you can assign price tiers to hosts, either manually or automatically.

You can enter one of the following in the Search text box at the top of the leftpanel to filter the table:

■ Host name

■ Processor tier

■ OS tier

The left panel provides you the options to filter the list of hosts that are displayedin the Hosts having license deployed table. You can filter the hosts based on thefollowing:

■ Platform

Viewing deployment informationViewing hosts with product license deployed

356

■ Hosts that are virtual machines

■ Tier definition

■ Type of licenses

■ Hosts that need attention

To view hosts with product license deployed


2 In the Deployment Summary view, click the Product Inventory tab.


4 Click the Hosts tab to view the Hosts with licenses deployed table.

See “Viewing the evidence details of a feature” on page 357.


See “Viewing the overview of a host” on page 358.


See “Assigning a price tier to a host automatically” on page 328.

Viewing the evidence details of a featureIn the EvidenceDetails view, you can view the details of the features that a licensekey enables. Also, the EvidenceDetails view displays the evidence of the featuresthat are present on a host.

The Evidence Details view displays the details in a table.

At the top of the table, you can view the following information:

■ Name of the host on which the licenses are deployed.

■ Product that is installed on the host.

■ Version of the product that is installed on the host.

The table that lists the evidence details displays the following information:

■ Name of the product for which the evidence details are listed.

■ Features of the product that the license key enables.

■ Feature tracking information on the usage of the feature.

■ Number of the storage objects that are associated with the feature.

■ Package to which the feature belongs.

357Viewing deployment informationViewing the evidence details of a feature

In the Feature trackingcolumn of the Evidence Details view, you can view thefollowing information for each feature:

■ Number of times the feature was used in the previous day.

■ Number of times the feature was used in the previous month.

■ Date and time when the feature was used last.

To view the evidence details of a feature in Veritas Operations Manager


2 In the LicenseDeploymentSummary view, click the ProductInventory tab.

3 In the Product Inventory view, in the Inventory table, click the name of theproduct.

4 In the details view of the product, click the Hosts tab to view the list of hostson which the licenses are deployed.

5 Select the option on the left-hand side to select a specific host for which youwant to view the feature evidence details.

6 Under ProductEvidence column, click the icon to view the feature evidencedetails.

7 In the EvidenceDetails panel, view the details of the feature that the licensekey enables.

See “Viewing hosts with product license deployed” on page 356.

Viewing the overview of a hostA host contains the central processing unit on which applications run and databasetransactions occur. In a typical storage network, hosts provide access to storagein one of the following ways:

■ Physical storage devices, which are attached directly to the host.

■ Logical storage structures, which are mapped to physical storage resourceson the network.

To view the overview of a host


2 In the Host view, select the check box for the host, which you want tooverview.

3 In the Host Details view, review the following information related to theselected host.

Viewing deployment informationViewing the overview of a host

358

■ Overview: You can select a single host and view detailed information aboutit. SF Manager displays the host’s name, management state, IP address, andgroup membership, if any. It also displays whether it is managed in VeritasVolume Manager, replicated by Veritas Volume Replicator, or part of a VeritasCluster Server.See “Viewing the overview of a host” on page 358.

■ Disks: View information about the disk on the selected host. View the diskgroup to which the disk belongs along with the disk’s type, status, sharingcapabilities, vendor, and volume information.

■ Disk Groups: View information about any disk groups on the selected host.View the disk group’s status, type, size, free space, version, number of disks,and number of volumes.

■ Volumes: View information about volumes on the selected host. View thevolume layout, Mount Point location of the file system, file system type, freespace, usage, and the name of the volume for which a snapshot contains apoint-in-time copy of its data.

■ File Systems: View information about file systems on the selected host. Viewthe Mount Point or location of the file system along with file system type,capacity, available storage, and usage.

■ ServiceGroups: Administrators can view information about the service group,such as its state, type, family, hosts, version, cluster name, failover order, andauto start status.

■ Initiators: View the initiators associated with the host.

■ LUNs: View information about the logical unit numbers (LUNs) on the selectedhost. LUNs represent a unique and discrete addressable unit or logical volumethat may reside inside one or more simple or array storage devices.

■ VCS attributes: View all the VCS attributes that are associated with the host.

■ Host attributes:View the host attributes. For instance, enclosure attributes,DMP attributes, and VxVM attributes.

■ Licenses/Packages: View information about software licenses on the selectedhost. View the product’s name, the type of license (for example, demo orpermanent), the license key information, serial number, and any licensedproduct features. View information about packages that are installed on theselected host. Packages can include applications, utilities, system options, ormanual pages for applications. View the type of package (for example,application, option, utility or feature), and version number.

■ Available patches: View information about the available patches on theselected host. View the product’s name, the patch type (for example, rolling

359Viewing deployment informationViewing the overview of a host

patch or patch), the size of the patch file, the products on which the patch isapplicable, the release date of the patch, the release name of the patch, andthe status of the patch (i.e. active or obsolete).

■ Performance: View the performance of the host using interactive graph.See “Viewing the performance graphs for a host” on page 213.




Viewing the overview of the licenses information fora host

This view provides you an overview of the licenses that are installed on a host inyour datacenter.

This view displays the following information:

Overview

Name of the host that you have selectedHost Name

Platform on which the host runsPlatform

Model of the platformModel

Number of processors for the hostNProcessor

Tier that is identified based on the processortype information.

Processor Tier

The Symantec Performance Value Unit perthe processor core

SPVU/Core

Tier that is identified for the installedoperating system. This field is applicableonly for the Windows hosts.

OS Tier

Actual product installed on the host.Actual Installed Product

Version of the product that is installed onthe host

Installed Product Version

Operating system on which the host runsOS

Viewing deployment informationViewing the overview of the licenses information for a host

360

Specifies whether the host is a virtualmachine

Virtual Machine

Type of the processor for the hostProcessor Type

Tier that is identified based on the serverinformation. This field is applicable only forthe hosts that run on Solaris, AIX, andHP-UX.

Server Tier

Tier that is identified based on the numberof processors of the host. This field isapplicable only for the Linux hosts.

NProcessor Tier

Indicates the way the tier was identified forthe host. The available types are Exactmatch, Best match, and No match.

Match Type

Highest license that is installed on the hostHighest License

Evidence of featured on the host. Click onthe corresponding icon to view the detailsof the product evidence.

Product Evidence

Licenses Deployed

License key for the productLicense Key

Name of the productProduct

Specifies whether the license is keylessKeyless

Serial number of the licenseSerial No.

Specifies whether the license is accountableAccountable

Platform for the productPlatform

Edition of the productProduct Edition

Version of the licenseVersion

Type of the licenseType

Specifies whether the license is a site license.Site licenses can be installed on multiplehosts.

Site License

Specifies whether Veritas Volume Manageroption is enabled

VVR Option

361Viewing deployment informationViewing the overview of the licenses information for a host

Identification number of the OriginalEquipment Manufacturer

OEM ID

Date on which the license expiresExpiration Date

Number of days within which the license isexpired

Days Remaining

Child licenses for the product license. ChildLicenses are the licenses that are installedthrough Edition products.

Click on the corresponding icon to view thedetails.

Child Licenses

Features that are enabled by this license.Click on the icon to view the details of thefeatures enabled by this license.

Click on the corresponding icon to view thedetails.

Feature Enabled

To view the overview of the licenses information for a host

1 In the Veritas Operations Manager console, click Licenses > DeploymentSummary.

2 In the Hostdeploymentsummary table, click the number in the TotalHostscolumn.

3 In the Hosts tab, click on a host to view its overview.


Viewing product details by license keyThe Product Inventory tab lets you view product details by license key.

The details include the following:

■ License key

■ Product

■ Keyless

■ Serial No.

■ Platform

■ Edition

■ Version

Viewing deployment informationViewing product details by license key

362

■ Type

■ Site Licenses

■ VVR Option

■ OEM ID

■ Number of hosts

■ Expired licenses on hosts

■ Child Licenses

■ Features enabled

You can click the icon under Features Enabled to view the name of each feature,the status of the enabled feature, and the product to which the enabled featuresbelong.

Note: Windows managed hosts do not contain any child licenses.

The left-side panel provides you the options to filter the Licensesdeployed table.You can enter the product name or the license key in the Search text box at thetop of the left-side panel to filter the Licenses deployed table.

Also, the left-side panel displays the following categories that lets you filter theLicenses deployed table:

■ Platform

■ Edition

■ Release

■ License attributes

■ Licenses that need verification


To view product details by license key



3 In the Inventory table, under Product, click the product name.

4 Click the Licenses tab and view the details that are displayed on the Licensesdeployed table.


363Viewing deployment informationViewing product details by license key

See “Viewing license key details” on page 364.

Viewing license key detailsYou can view license key details including the license key number; the productname, edition, version and type; the license and product expiration dates; thenumber of days before the product license expires; the status of license expiration;the status of deployment; the number of hosts; and the features enabled.

To view license key details




4 Click the Licenses tab.

Viewing deployment informationViewing license key details

364

5 Under License Key, click the license key number link.

6 View detailed host information:

Click the icon to display enabled features,their status, and the product to which theybelong.

Features Enabled

Click the links to sort hosts by platform,license matches, or types of license. Youcan use the Assign Price Tier button toassign a new price tier to hosts.

Hosts having license deployed

Displays license key details including thehost name, platform, server tier, processortier, number of processors tier, operatingsystem tier, operating system, model,processor type, number of processors,match type, number of licenses, numberof invalid licenses, whether the productcorresponding to license key is installed,comments, and product evidence.

License detail table

Displays the features that are enabled inthe license key and evidence of featureson the host. You can view the names andversion numbers of the products installedon the host. You can also view the nameand status of enabled features, the productto which the feature belongs, the package,marker file, and the number of objects.

Product Evidence



Viewing the details of the mapping between thelicenses and hosts

The Licenses-Hosts Mapping view displays detailed product information includingthe following:

■ License key

■ Product name

■ Version (for example, 4.1, 5.0)

365Viewing deployment informationViewing the details of the mapping between the licenses and hosts

■ Edition (for example, Enterprise, Standard)

■ License expiration date (for example, 2008-08-05)

■ Days until the license expires

To view product details by license-host mapping




4 Click the Licenses-Hosts Mapping tab.


See “Viewing a product overview” on page 355.

Viewing License-Host Mapping detailsThe Licenses-Hosts Mapping view displays detailed product information includingthe following:

■ License key

■ Product name

■ Keyless license details

■ Serial number

■ Accountable licenses

■ Version (for example, 4.1, 5.0)

■ Edition (for example, Enterprise, Standard)

■ License type

■ License expiration date (for example, 2008-08-05)

■ Days until the license expires

■ Host on which the license is deployed

■ Operating system of the host

■ Whether the host is a virtual machine

■ Server tier details

■ Total number of the required Symantec Performance Value Unit (SPVU). Clickon this number to view the details of the method to calculate the SPVUs.

Viewing deployment informationViewing License-Host Mapping details

366

■ Processor tier details

■ NProcessor tier details

■ OS tier details

■ Match type

■ Child licenses

■ Features that the license key enables .

The left-side panel provides you the options to filter the Licenses-HostsMappingtable.

You can enter one of the following in the Search text box at the top of the left-sidepanel to filter the Licenses-Hosts Mapping table:

■ Host name

■ Product name

■ Processor tier

■ OS tier

Also, the left-side panel displays the following categories that lets you filter theLicenses-Hosts Mapping table:

■ Platform

■ Virtual Machine

■ Edition

■ Release

■ Expired licenses

■ Keyless licenses

■ Accountable licenses


To view product details by license-host mapping




4 Click the Licenses-HostsMapping tab and view the details that are displayedon the Deployed License-Host Mapping table.


367Viewing deployment informationViewing License-Host Mapping details

See “Viewing a product overview” on page 355.

Viewing the summary of host-level licensedeployment exceptions

The Exceptions tab lets you review the host-level license deployment issues thatcannot be reviewed through the Product Inventory view. You can view the listof hosts on which licenses were not found or the license discovery was failed.

To view the Exceptions summary


2 In the License Deployment Summary view, click the Exceptions tab.


Viewing the VOM Entitlement ReportThis view provides you detailed information on the VOM advanced licenses thatyour hosts require. The number of hosts requiring license changes if VeritasOperations Manager Management Server reports to Veritas Operations ManagerEnterprise Server. At the top of VOM Entitlement Report view, you can view theinformation whether or not Management Server reports to a Veritas OperationsManager Enterprise Server.

The Overview section in this view displays the following information:

■ The total number of hosts that report to Veritas Operations ManagerManagement Server.

■ The number of hosts that run Storage Foundation, Veritas Cluster Server,Application HA, or Dynamic Multipathing out of the total number of hosts.

■ The number of hosts that run Storage Foundation Enterprise out of the numberof hosts that run Storage Foundation.

■ The number of NAS capable enclosures that are configured on ManagementServer.

■ The number of hosts that require the Veritas Operations Manager Advancedlicense out of the total number of hosts. The number of hosts that require theVeritas Operations Manager Advanced license, is calculated based on followingset of rules:

■ VIOS and Virtualization Servers are not charged.

Viewing deployment informationViewing the summary of host-level license deployment exceptions

368

Note: A server is a Virtualization Server only if there are guest, domains,or virtual machines created, this applies to LDOM, KVM and ZONE. LPARVIO servers and ESX servers are by default Virtualization Servers.

■ Storage Foundation, Storage Foundation Enterprise, or DynamicMultipathing entitlement is propagated from Virtualization servers toVirtual Machines.

■ Hosts that are not entitled to Storage Foundation , Storage FoundationEnterprise, or Dynamic Multipathing (for example -Agentless,No-configuration, or Non-Storage Foundation hosts) are charged.

■ VOM–Advanced is free for the hosts that are entitled to Storage FoundationEnterprise(directly or propagated).

■ In case of rollup, physical hosts that are having Storage Foundation withNon-Enterprise edition, or Dynamic Multipathing with Non-Enterpriseedition are charged.

■ The number of hosts that do not run Storage Foundation, Veritas ClusterServer, AppHA or Dynamic Multipathing out of the total number of hosts.

■ The number of hosts that have a valid license for Storage Foundation Standardor Storage Foundation Basic out of the number of hosts that runs StorageFoundation.

Using the Search field on the left side, you can search for a host using its nameor the platform on which it runs. To search for a host, enter a part of the name orthe platform in the Search field.

Using the filter option on the left side, you can filter the selection of hosts in theVOM Entitlement Report table based on the following criteria:

■ Host - Non SF/VCS/DMP/AppHA Host, and SF/VCS/DMP/AppHA Hosts.

■ Edition -Enterprise, Basic, Standard, and Not Available.

■ Configuration Type -Agentless Host, Agent Host, and No Configuration.

■ Chargeable -Yes, No, and Propagated

The VOM Entitlement Report table in this view displays the following details:

Name of the host.Host Name

Operating system on which the host runs.Platform

Type of the host.Host Type

369Viewing deployment informationViewing the VOM Entitlement Report

Indicates whether the host is an Agentlesshost, Agent host, or host with noconfiguration.

Configuration Type

Indicates whether Storage Foundation,Veritas Cluster Server, DynamicMultipathing , or Application HA is installedon the host.

SF/VCS/DMP/AppHA

The edition of the Storage Foundation,Veritas Cluster Server, DynamicMultipathing , or Application HA installedon the host. The value can be Enterprise,Standard, or Basic.

Edition

Indicates whether the host is chargeable,propagated , or not chargeable.

Is Chargeable

To view the VOM Entitlement Report

◆ In the Veritas Operations Manager console, select Licenses > VOMEntitlement Report.

See “Viewing the overview of the licenses information for a host” on page 360.


Scoping a license deployment view using businessentities

In Veritas Operations Manager, you can scope a license deployment view byspecifying business entities. You can do this task from any views that are relatedto license deployment.

Scoping the license deployment views based on a specific business entity helpsyou focus on the deployment details of licenses that are part of that businessentity.

Note: By default, Veritas Operations Manager displays the deployment details ofall the licenses in the domain.

Viewing deployment informationScoping a license deployment view using business entities

370

To scope a license deployment view using business entities


2 At the top of any license deployment view, near to the Current scope field,click Change scope.

For example, at the top of the License Deployment Summary view, near tothe Current scope field, click Change scope.

3 In the Scoping License Views wizard panel, select the business entity basedon which you want to scope the license deployment view and click Finish.

See “Scoping License Views options” on page 371.


Scoping License Views optionsUse this wizard panel to scope a license deployment view using a business entity.

Note: In Veritas Operations Manager, business entities comprise application andorganization entities.

Table 15-3 Scoping License Views panel options

DescriptionField

Choose this option to scope the licensedeployment view using all the businessentities.

Entire Domain

Choose this option to scope the licensedeployment view using selected businessentities. In the table that lists all the businessentities in Veritas Operations Manager, youcan specify the business entities that youwant to include.

Select business entity

See “Scoping a license deployment view using business entities” on page 370.

371Viewing deployment informationScoping a license deployment view using business entities

Viewing deployment informationScoping a license deployment view using business entities

372

Using policy checks


■ About policy checks

■ About policy templates

■ About creating policy templates

■ Creating policy templates

■ Modifying policy templates

■ Running a manual policy template scan

■ Deleting a policy template

■ About policy violations

■ Marking policy violations to exclude from the subsequent scans

■ About Installed Signatures

■ About the customized signature in Veritas Operations Manager for identifyingrisks

■ Adding signatures to a policy template

■ Setting signature tunables

■ Removing a signature from a policy template

■ Deleting a policy template scan

■ Viewing scan tunables associated with a policy scan

■ Removing ignored violations from the ignore list

16Chapter

About policy checksThe Veritas Operations Manager policy check uses individual rules to validatewhether the datacenter configuration conforms to a pre-defined standard. Theseindividual rules are named as signatures. You can run the signatures across theVeritas Operations Manager environment. The policy check feature in VeritasOperations Manager lets you manage the signatures. Veritas Operations Managercontains 50 pre-defined signatures. In addition to the pre-defined signatures,Veritas Operations Manager lets you create the customized signatures.

The Veritas Operations Manager policy check enables the administrator to identifythe resources which do not meet that specified standard, and track these violationsover time. These standards can be configured to scan multiple signatures, atspecific scheduled intervals, with different options, against any number of hostsin your datacenter. The policy check allows you to better identify and addressrisks in your environment by providing notification of error and risk conditionson a proactive basis, before they evolve into something more severe.

The time that is required for collecting data to generate a Policy Check reportdepends on the number of hosts against which the policy checks must run on, thesize of the configuration, and the number of signatures run.

See “About policy templates” on page 374.

See “About Installed Signatures” on page 383.

See “About the customized signature in Veritas Operations Manager for identifyingrisks” on page 384.

About policy templatesVeritas Operations Manager lets you configure a policy template by specifyingthe signatures that must be included in the scan. You can also specify the hostsor business entities against which the scan must be run. You can also specify howfrequently to run the scan i.e. daily, weekly, and so on. In short, the policytemplates enable you to customize the checks on the managed objects and set theoptions for the checks in that template.

You cannot run the policy checks on ESX servers and non-global zones becausethe VRTSsfmh package is not installed on them.

Note: Users other than the Domain Administrators are only allowed to create,edit, or delete policy templates on Business Entities on which they haveadministrative privileges.

Using policy checksAbout policy checks

374

See “About creating policy templates” on page 375.

Table 16-1 provides details on the available policy templates .

Table 16-1 Information on policy templates

DescriptionPolicy template Attributes

Specifies the name of the policy template. This is anoptional value.

Name

Specifies the policy template and what it does. This is anoptional value.

Description

Specifies what hosts or business entities the template isrun against.

Scope

Specifies the date and time and the link to the last scanthat was run using this policy template.

Last Scan

Specifies the number of policy violations in the last scan.Violations in last scan

The Policy Templates view also provides a filter to view the specified policytemplates as per the specified criteria. This filter searches on the Name,Description, and Scope fields

In the search box on the Filter Policy Templates panel, you can type in a searchkeyword.

You can click on the name of the policy template to get more information aboutit. This provides details about the time when the policy template was scanned,the signatures which were violated, the hosts on which the violation occurred,and the total number of violations.

For more detailed information of the policy violations resulting from a scan thatis conducted on a specific date, click on the date of the scan.

For more information on policy violations:

See “About policy violations” on page 382.

About creating policy templatesYou can create a policy template in the following ways:

■ Creating a policy template using wizards.See “Creating policy templates” on page 376.

■ Adding signatures to policy templates.See “Adding signatures to a policy template” on page 392.

375Using policy checksAbout creating policy templates

Creating policy templatesVeritas Operations Manager lets you create policy templates to check theperformance, availability, utilization of the storage objects in your datacenter.The policy templates also generates information based on the conformance of thestorage objects with the best practices. Using the policy templates, you can scanthe storage objects for 42 types of checks.

You can create policy templates only for the domains where you have administratorprivileges.

To create a policy template

1 Select Policies > Policy Templates.

2 Click Actions > Create Policy Template.

3 In the Policy Template Details panel, enter the required information. ClickNext.

See “Policy Template Details options” on page 377.

4 In the Select Signatures panel, select the check boxes next to the signaturesthat you want to include in the policy template. Click Next

See “Select Signatures options” on page 377.

5 If you chose to run the policy template scan on specific hosts, select the hostsin the Select Scope panel. This panel is not displayed if you chose to run thescan on all the hosts. Click Next.

See “Select Scope options” on page 378.

6 In the SpecifySchedule panel, choose when to run all the signatures that areassociated with the policy template. Click Next.

See “Specify Schedule options” on page 378.

7 In the PolicyTemplateSummary panel, confirm the selections that you madeto create the policy template.

See “Policy Template Summary options” on page 379.

8 Click Finish to create the policy template.

9 In the Result panel, verify that the policy template was successfully created.Click OK.


See “Deleting a policy template” on page 381.

Using policy checksCreating policy templates

376

Policy Template Details optionsUse this wizard panel to specify the details of the policy template.

Table 16-2 Policy Template Details panel options

DescriptionField

Specify the policy template name.Name

Add a brief description of the policytemplate.

Description

Select one of the following to define the scanscope:

■ Scan specific hosts to choose the hoststo be scanned

■ Scan hosts associated with a BusinessEntity to scan the hosts that areassociated with a business entity

■ Scan all hosts to scan all the hosts

Scan Scope

Specify the email address to whichnotifications must be sent in case of policyviolations. This field is optional.

Email

See “Creating policy templates” on page 376.

See “Modifying policy templates” on page 380.

Select Signatures optionsSome signatures are packaged with a standard Veritas Operations Managerinstallation.

Use this wizard panel to select the signatures for the policy template.

Table 16-3 Select Signatures panel options

DescriptionField

Specify keywords to filter the list of availablesignatures.

Filter

Lists all the signatures that you haveselected.

Selected

377Using policy checksCreating policy templates

Table 16-3 Select Signatures panel options (continued)

DescriptionField

Removes a selected signature from theselected signatures list.

Remove Selected

Removes all the signatures from the selectedsignatures list.

Remove All



Select Scope optionsUse this wizard panel to select the hosts on which to run the policy template scan.Select the check boxes to select the hosts.

Table 16-4 Select Scope panel options

DescriptionField

Specify keywords to filter the list of availablehosts.

Filter



Specify Schedule optionsUse this wizard panel to specify when the policy template scan is to be run.

Using policy checksCreating policy templates

378

Table 16-5 Specify Schedule panel options

DescriptionField

No Schedule - Select this option to indicatethat you will manually run the scan as andwhen required.

Daily - Select this option to run the scanonce every day. You have to specify the timewhen the scan should be run.

Weekly - Select this option to run the scanonce every week. You can choose to run iton every weekday, or on specific weekdays.Also, you have to specify the time when thescan should be run.

Monthly - Select this option to run the scanonce every month. You can choose to run iton a particular day of the month, or on aspecific weekday. Also, you have to specifythe time when the scan should be run.

Frequency

Specify the schedule for the policy templatescan.

When



Policy Template Summary optionsUse this wizard panel to confirm the selections that you made to create the policytemplate.

Table 16-6 Policy Template Summary panel options

DescriptionField

Select this option to run the scanimmediately after the policy template iscreated.

Run Policy Template Scan immediately



379Using policy checksCreating policy templates

Modifying policy templatesIn Veritas Operations Manager, the Edit Policy Template option lets you makefurther changes to the existing policy templates.

To modify an existing policy template

1 In the Veritas Operations Manager console, select Policies > PolicyTemplates.

2 To modify the policy template, do one of the following:

■ Select the policy template and click Actions > Edit Policy Template.

■ Right-click the policy template and select Edit Policy Template.

3 In the PolicyTemplateDetails wizard panel, modify the required informationand click Next.

See “Policy Template Details options” on page 377.

4 In SelectSignatures panel, modify the selection of the signatures if requiredand click Next.

See “Select Signatures options” on page 377.

5 In Select Scope panel, modify the scope for the scan and click Next.


6 In the Specify Schedule panel, modify the frequency at which you want torun the scan and click Next.

See “Specify Schedule options” on page 378.

7 In the PolicyTemplateSummary panel, review the configuration details thatyou entered while modifying the policy template.

Select the Run Policy Template Scan immediately check box if you want torun the policy scan immediately after you modify the policy template.

See “Policy Template Summary options” on page 379.

8 Click Finish.

9 In the Result panel, click OK to confirm the changes that you have made tothe policy template.


See “Deleting a policy template” on page 381.

See “Adding signatures to a policy template” on page 392.

See “Removing a signature from a policy template” on page 393.

Using policy checksModifying policy templates

380

Running a manual policy template scanIn Veritas Operations Manager, you can run a policy template scan manually.

To run a manual policy template scan

1 Select Policies > Policy Templates.

2 Select the check box corresponding to the policy template that you want torun manually.

3 Click Actions > Scan Now.

4 In the Run Policy Template Scan Now page, click Yes to run the scan.

5 In the Results page, verify that the policy template scan has started. ClickOK.

See “About policy checks” on page 374.


See “Deleting a policy template scan” on page 394.

Deleting a policy templateYou can delete one or more existing policy templates if they are no more requiredin Veritas Operations Manager. If you delete a policy template, its associated scansand the identified policy violations are also removed permanently from the system.

Only the root user or the domain administrator can delete the policy templates.

To delete a policy template

1 In the Veritas Operations Manager console, select Policies>PolicyTemplates.

2 Select the policy template that you want to delete and do one of the following:

■ Click Actions > Delete Policy Template.

■ Right-click the policy template and from the submenu, select DeletePolicyTemplate.

3 Click Yes to confirm.



See “Deleting a policy template scan” on page 394.

381Using policy checksRunning a manual policy template scan

About policy violationsA policy violation occurs when a configuration option on a manged host does notmeet the condition that a signature for the corresponding policy template setsfor it.

You can scan for policy violations using the ScanNow tab on the PolicyTemplatesview instead of waiting for the scheduled scan time (if specified). This opens adialog box asking for confirmation to run the policy scan.

Table 16-7 displays the manner in which the results of the completed scan areclassified.

Table 16-7 Scan operations

DescriptionScan operations

Indicates new policy violations in this scan that were not partof a previously run scan.

Show New Violations

Indicates the policy violations that were found in previousscans that are no longer occuring.

Show Resolved Violations

Indicates the violations that occured in previous scans andare continuing to happen in the selected scan.

Show Persisting Violations

Deletes the selected scans.Delete Scan

Indicates the tunables or configurable variables associatedwith included signatures.

Show Scan Tunables Used

Indicates the policy violations that the administrator haschosen to ignore.

Ignored violations

See “Running a manual policy template scan” on page 381.

See “Marking policy violations to exclude from the subsequent scans” on page 382.

See “Removing ignored violations from the ignore list” on page 395.

Marking policy violations to exclude from thesubsequent scans

After the policy template scan, you can view the list of all policy violations. Youcan mark one or more policy violations if you want to exclude them from thesubsequent scans. It is referred to as ignoring the violation. Once you have markedthese policy violations, they are not included in next scan cycles.

Using policy checksAbout policy violations

382

To mark a policy violation to exclude from the subsequent scans

1 In the Veritas Operations Manager console, select Policies >PolicyTemplates.

2 Click the policy template for which you want to exclude its associated policyviolations in the subsequent scans.

3 Under Scans, you can view all the scan reports associated with the policytemplate that you have selected. Click the desired scan report.

4 In Violations table, select the violation that you want to exclude from thesubsequent scans.

5 At the top of the Violations table, click Ignore Violation.

6 In the Ignore Violations panel, click OK.

7 In the Results panel, click OK to confirm.


See “Removing ignored violations from the ignore list” on page 395.

About Installed SignaturesThe Policy Check signatures are installed and managed centrally. Currently, thereis a default set of signatures that is shipped with a basic Veritas OperationsManager installation. The Installed Signature view provides a global overviewof the the signatures or policies that are already installed and available to you.

The InstalledSignatures view also provides a filter to selectively view the specifiedsignatures.

Table 16-8 displays information about the available signatures.

Table 16-8 Installed Signatures

Functional descriptionInstalledSignatureInformation

Name of the installed signatureName

Brief description about the installed signature and what it does.Description

Keyword or search categories that can be used in the filter to identifyrequired signatures as per a specified criteria.

Keywords

Default configurable options or variables that can be set or adjusted forsome signatures.

Tunable settings

383Using policy checksAbout Installed Signatures

The Set Tunables tab displays the tunables that are associated with a signature.

See “Setting signature tunables” on page 392.

The Show Additional information tab provides some additional informationdetailing what violations the signature will discover. It also suggests some possibleways to remediate that condition.

The RemoveSignature tab allows you to remove the specified signature from thepolicy template.

For more information on removing signatures:


Note: Additional signatures are distributed via a signature pack.




About the customized signature in VeritasOperationsManager for identifying risks

Veritas Operations Manager lets you create customized signatures, which youcan schedule to run at specified time with specified options on specified sets ofhosts. As administrators, you can use the information that these customizedsignatures gather to address the risks in the Veritas Operations Managerenvironment proactively. Also, you can define notifications based on thesesignatures on any error conditions that may occur in your Veritas OperationsManager environment.

After you create the customized signature script, you must register the script onManagement Server. Then, you must copy the customized signature script to themanaged hosts where you want to run it. Also, you can use the DistributionManager Add-on to create a customized signature script, register it on ManagementServer, and copy it to the managed hosts.

Apart from the 50 predefined signatures available with Veritas OperationsManager, you can plug-in the customized signatures to the policy check feature.



Using policy checksAbout the customized signature in Veritas Operations Manager for identifying risks

384

See “About creating a customized signature script” on page 385.

See “About registering the customized signature” on page 388.

See “About copying the customized signature script” on page 388.

See “About using the Distribution Manager Add-on to bundle a customizedsignature in Veritas Operations Manager” on page 389.

See “About removing a customized signature from Veritas Operations Manager”on page 392.

About creating a customized signature scriptYou can create the customized signature script using any programming language.Also, the customized signature script can have any type of code.

You must ensure the following when you create the customized signature script:

■ Script must return 0 for success.

■ Script must return a value other than 0 for errors.

In case of error, the script must print as follows:

Table 16-9 Script output when an error occurs

ValueItem

Any of the following exit codes:

■ 0 - Check passed.

■ 1 - Check fails with warning.

■ 2 - Check fails with error.

■ 100 - Not supported or cannot run check.

RESULT_RC

Displays the failure messageRESULT_TXT

Displays the message that helps resolve theproblem.

RESULT_REMEDY

The customized signature script must support the --what command line argument,which ensures the following output when you use the customized signature

script.pl --what command:

385Using policy checksAbout the customized signature in Veritas Operations Manager for identifying risks

Table 16-10 Output of the command: customized signature script.pl

--what

ValueItem

Displays a unique value. This value can be anumber or a string.

The CHECK_ID and the name of the scriptfile need to be the same for the customsignature to work properly.

Example: PC_VXVM_UNUSED_VOLUMES

CHECK_ID

Displays the name of the customizedsignature.

CHECK_NAME

Displays the description for signature.CHECK_DESCRIPTION

Displays the category to which thecustomized signature belongs.

Example:UTILIZATION/VXVM/PERFORMANCE/VCS

CHECK_KEYWORDS

Note:The customized signature must return the code 0 on successful registrationon Management Server. It must not give any other output.

See “Sample customized signature script” on page 386.






Sample customized signature script

Note: The following sample script is created using PERL.


386

#!/opt/VRTSsfmh/bin/perl

BEGIN { @INC = ("/opt/VRTSsfmh/lib/modules"); }

use strict;

if ($ARGV[0] eq "--what")

{

print "CHECK_ID: PC_VXVM_UNUSED_VOLUMES\n";

print "CHECK_NAME: VxVM Unused Volumes\n";

print "CHECK_DESCRIPTION: Check to see if any VxVM volumes are unused.\n";

print "CHECK_KEYWORDS: UTILIZATION UNIX VXVM\n";

exit (0);

}

if($^O =~ /Win32/i)

{

print "RESULT_RC=100\n";

print "RESULT_TXT=Windows host detected\n";

print "RESULT_REMEDY=This check is intended only for unix hosts\n";\

exit(100);

}

my $exitcode = 0;

my @items = `/opt/VRTSsfmh/bin/vxlist -t stats vol`;

my $iocount = {};

foreach (@items) {

if(/^vol\s+(\S+)\s+(\S+)\s+(read|write)\s+(\S+)\s+/) {

my $name = $2."/".$1;

$iocount->{$name} += $4;

}

}

foreach (keys %$iocount) {

if($iocount->{$_} == 0) {

/(\S+)\/(\S+)/;

print "RESULT_RC=2\n";

print "RESULT_TXT=VxVM volume $2 in disk group $1 may be unused. It has performed no I/O since last reboot.\n";

print "RESULT_REMEDY=There may be data on the volume, such as an unmounted file system. If not, space can be reclaimed by deleting the volume,\n";

$exitcode = 2;

}

}

exit($exitcode);



About registering the customized signatureAfter you create the customized signature, you must register it on VeritasOperations Manager Management Server. Before you register the signature, youmust ensure that the signature is in the executable format.

To register a customized signature, you can use the pcregutility, which is availablein the following locations:

■ On UNIX Management Server - /opt/VRTSsfmh/bin

■ On Windows Management Server - C:\Program Files\VERITAS\VRTSsfmh\bin

The following is the syntax that you can use for registering the customizedsignatures:

■ pcreg --script policy check script

Note: In this syntax, you must provide the full path to the customized signaturescript.

After you register the customized signature, you can view the signature in theInstalled Signatures view. You can add this signature to an existing or a newpolicy template. Also, you must copy the customized signature on the managedhosts where you want to run it.

To view the customized signature that you have registered, navigate to Policies> Signatures in the Veritas Operations Manager console.






About copying the customized signature scriptYou must ensure that the customized signature exists on the managed host whereyou want it to run it.


388

You must copy the customized script to the following locations:

■ On UNIX managed hosts - /opt/VRTSsfmh/lib/signatures

■ On Windows managed host - C:\ProgramFiles\VERITAS\VRTSsfmh\lib\signatures

You can copy the customized signature to the managed hosts manually. Also, youcan use the Distribution Manager Add-on to push the customized signatures tothe required managed hosts.






About using the Distribution Manager Add-on to bundle a customizedsignature in Veritas Operations Manager

Using the Distribution Manager Add-on, you can bundle the signature, set up,and the unsetup scripts to a .sfa archive. The setup script can register thecustomized signature at a specific location on Management Server and copy thecustomized signature at a specific location on the managed host. Once the add-onis created for the customized signature, you can deploy it using the DeploymentManagement feature. The unsetup script of the add-on can unregister thecustomized signature on Management Server and remove the customized signaturefrom managed hosts.

For information on using the Distribution Manager Add-on, seeVeritasOperationsManager Management Server Add-ons User's Guide.

See “Sample setup.pl script for the customized signature” on page 390.

See “Sample unsetup.pl script for a customized signature” on page 391.







Sample setup.pl script for the customized signatureThe following is the sample setup.pl script for the customized signature:



use VRTS::AddOnInfo;

use File::Copy;

require File::Spec;

my $store_dir = $ENV{'Store'};

my $install_dir = VRTS::Paths::get_path("InstallDir");

my $pcregutil = File::Spec->catfile($install_dir,"bin","pcreg");

my $sigdir = File::Spec->catfile($install_dir,"lib","signatures");

# Creating array of signature files name

@signature_files = ("UnUsedVolumes.pl");

# Copy file under signatures directory

foreach $sigfile (@signature_files)

{

print "Coping script $sigfile to $sigdir\n";

copy($sigfile,$sigdir);

print "Making script executable\n";

my $pc = File::Spec->catfile($sigdir,$sigfile);

system("chmod +x $pc");

# Register signature only on CS

if ( VRTS::AddOnInfo::is_CS() )

{

print "Registering scipt\n";

my $cmd1 = VRTS::Util::make_command($pcregutil,"--script",$pc);

system($cmd1);

}

}

exit(0);


390


Sample unsetup.pl script for a customized signatureThe following is the sample unsetup.pl script for a customized signature:



use VRTS::AddOnInfo;

use File::Copy;

require File::Spec;

my $install_dir = VRTS::Paths::get_path("InstallDir");

my $sigdir = File::Spec->catfile($install_dir,"lib","signatures");

my $pcregutil = File::Spec->catfile($install_dir,"bin","pcreg");

# Creating array of signature files name and signature name

@signature_files = ("UnUsedVolumes.pl");

@signature_names = ("PC_VXVM_UNUSED_VOLUMES");

# Unregister script on CS

if ( VRTS::AddOnInfo::is_CS() )

{

foreach $signame (@signature_names)

{

print "Unregister signature $signame\n";

system("$pcregutil --id $signame");

}

}

# Remove signature from signature directory

foreach $sigfilename (@signature_files)

{

print "Remove script $sigfilename\n";

my $sigfile = File::Spec->catfile($sigdir,$sigfilename);

File::Path::rmtree("$sigfile");

}

exit(0);



About removing a customized signature from Veritas OperationsManager

To remove a customized signature from Veritas Operations Manager, you can runthe following utility:

pcreg --id policy check id




Adding signatures to a policy templateIn Veritas Operations Manager, you can add signatures to a policy template inthe Installed Signatures view.

To add signatures to policy templates

1 In the Veritas Operations Manager console, select Policies > InstalledSignatures.

2 In the Installed Signatures view, select the check boxes for the signaturesthat you want to add to a policy template and do one of the following:

■ Click Actions > Add to Policy Template.

■ Right-click one of the selected signatures, and then click Add to PolicyTemplate.

3 In the AddSignature toPolicyTemplate panel, in the PolicyTemplates list,select the policy template to which you want to add the signatures and clickOK.

4 In the Result panel, verify that the operation was successful and click OK.




Setting signature tunablesIn Veritas Operations Manager, you can set the tunables for a signature that youselected while creating a policy check template under the Signatures tab in the

Using policy checksAdding signatures to a policy template

392

policy template details. However, some of the signatures may not have anyassociated tunables. You can refer to the Tunable Settings column of theSignatures table to determine whether a signature has any associated tunables.

To set signature tunables


2 Click on the desired policy template to view the policy template details.

3 On the Signatures tab, do one of the following:

■ Select the check box for the signature for which you want to set thetunables and click Set Tunables.

■ Right-click the signature for which you want to set the tunables, and thenclick Actions > Set Tunables.

See “Set Signature Tunables options” on page 393.

4 In the Set Signature Tunables panel, enter the new tunable values and clickOK.


See “Viewing scan tunables associated with a policy scan” on page 394.

Set Signature Tunables optionsUse this wizard panel to enter the new tunable values for the signature youselected. The tunable options that are displayed on this panel vary depending onthe signature you have selected.


Removing a signature from a policy templateIn Veritas Operations Manager, you can remove a signature from a policy templateunder the Signatures tab in the policy template details. After you remove asignature from a policy template, it is not included in the future policy scans basedon that policy template.

To remove a signature from a policy template



3 On the Signatures tab, do one of the following:

■ Select the check box for the signature that you want to remove from thepolicy template and click Actions > Remove Signature.

393Using policy checksRemoving a signature from a policy template

■ Right-click the signature that you want to remove from the policy template,and then click Remove Signature.

4 In the RemoveSignaturefromPolicyTemplate panel, confirm that you wantto remove the selected signature and click Yes.





Deleting a policy template scanYou can delete a policy check scan if you no longer require it.

To delete a policy template scan

1 In the console, select Policies > Policy Templates.

2 Click on the policy template to view the scan details.


■ Select the check box for the scan. Click Actions > Delete Scan.

■ Right-click on the row for the scan to display the shortcut menu, and selectDelete Scan.

4 In the DeletePolicyTemplateScan panel, confirm whether you want to deletethe policy template scan.

5 In the Result panel, verify that the operation was successful and click OK..



See “Running a manual policy template scan” on page 381.

Viewing scan tunables associated with a policy scanIn Veritas Operations Manager, you can view the scan tunables that are associatedwith a policy scan under the Scans tab in the policy template details.

Using policy checksDeleting a policy template scan

394

To view the scan tunables



3 On the Scans tab, do one of the following:

■ Select the check box for the policy scan for which you want to view theassociated tunables and then click Actions > Show Scan Tunables Used.

■ Right-click the policy scan for which you want to view the associatedtunables, and then click Show Scan Tunables Used.


Removing ignored violations from the ignore listIn Veritas Operations Manager, you can remove the ignored violations from theignore list. After you remove the violations from the ignore list, they are listed inthe scan details again.

To remove the ignored violations from the ignore list



3 On the Ignored Violations tab, select the check boxes for the violations thatyou want to remove from the ignore list and do one of the following:

■ Click Remove from Ignore List.

■ Right-click one of the selected violations, and then click Actions>Removefrom Ignore List.

4 In the Remove fromIgnoreList panel, confirm whether you want to removethe selected violations and click OK.



See “Marking policy violations to exclude from the subsequent scans” on page 382.

395Using policy checksRemoving ignored violations from the ignore list

Using policy checksRemoving ignored violations from the ignore list

396

Managing reports


■ About reports

■ About managing reports

■ Running a report

■ Creating a report schedule

■ Editing a report schedule

■ Enabling a report schedule

■ Disabling a report schedule

■ Removing a report schedule

■ Archiving reports

■ Sending a report through email

■ Deleting an archived report

■ Exporting report data to a file

About reportsIn Veritas Operations Manager, you can generate a variety of reports for variouspurposes. The following are the broad categories under which the reports aregrouped:

■ Storage UtilizationThe Storage Utilization category reports provide information on the utilizationof the various resources such as file systems, thin pools, enclosures, array

17Chapter

volumes, and so on. For example the Array Volume Usage report shows arrayvolume usage across all enclosures.

■ Trend/ActivityThe Trend or Activity category reports provide information on the activity ofa resource during a specified time duration. For example, the Uptime Analysisreport displays the total time for which the selected service groups were online.Also, the report summarizes the events that affect the online availability ofthe service groups.

■ Storage ReclamationThe Storage Reclamation category reports provide analysis of the storage thatcan be reclaimed from thin pools, or the storage that can be reclaimed fromfile systems under Veritas File System (VxFS). For example, the UnderutilizedLUNs managed by Storage Foundation report lists all LUNs for which availablecapacity is not fully utilized by Storage Foundation, whereas the UnderutilizedFile Systems report lists the file systems for which the available capacity isnot fully utilized.

■ EnvironmentThe Environment category reports provide information about the StorageFoundation product versions, product usage, underutilized license details, andso on. For example, the Patch report provides consolidated information aboutpatches applicable to each host in the datacenter.

■ InventoryThe Inventory category reports provide various details about the resources inyour datacenter, such as the mount point of a file system, or type and currentstate of a cluster, and so on. For example, the All Cluster report lists all theclusters in the datacenter, whereas the All Enclosures Report lists all theenclosures discovered in your datacenter.

See “Running a report” on page 399.

See “Creating a report schedule” on page 401.

About managing reportsIn Veritas Operations Manager, you can perform the following tasks from theReports view:

■ Run a report.

■ Schedule a report.

Managing reportsAbout managing reports

398

You must specify the business entities on which you want to run the report. Ifyou want to run the report on all the business entities in the datacenter , you canselect the Entire Domain option.

To schedule a report in Veritas Operations Manager, you must specify the followingdetails:

■ Scope of the report.

■ Time and frequency at which you want to generate the report.

■ Output types for the report that you schedule to generate.

In the report details view, you can perform the following tasks on the reportschedules that you have created:

■ Edit the report schedule.

■ Enable the report schedule.

■ Disable the report schedule.

■ Delete the report schedule.

In any of the reports views in Veritas Operations Manager, you can do thefollowing:

■ Send the report details through email.

■ Archive the report.

In the report details view, you can view the details of the reports that you havearchived.

Also, you can perform the following tasks on the reports that you have archived:

■ Delete an archived report.

■ Send an archived report through email.



See “Archiving reports” on page 407.

See “Sending a report through email” on page 408.

See “Exporting report data to a file” on page 411.

Running a reportYou can run a report either from the Reports view or from the details view of areport.

399Managing reportsRunning a report

To run a report

1 In the Veritas Operations Manager console, click Reports.

2 In the Reports view, do one of the following:

■ Identify the report that you want to generate and click Run.

■ Click the report that you want to generate. In the details view of the report,click Run.

3 In the Select Scope wizard panel, enter the details and click Finish to viewthe selected report.


Select Scope optionsUse this wizard panel to select the scope for running or scheduling a report. Youcan select the business entities that you need to include when you run or schedulea report.

Table 17-1 Select Scope options

DescriptionField

Select the file system type for which youwant to run or schedule the report.

Note: This option appears only for the FileSystem Usage report.

Select File System Type

You can enter the following data to specifythe date range for which you want to run thereport.

■ In the Start Date field, enter the date onwhich the date range for the reportstarts.

■ In the EndDate field, enter the date untilwhich date range for the report lasts.

Note: The DateRange field appears only forthe reports that belong to theTrend/Activity category and the Licenselifecycle report.

Date Range

Managing reportsRunning a report

400

Table 17-1 Select Scope options (continued)

DescriptionField

Specify the number of days for which youwant to run the report.

Note: The Duration field appears only forthe reports that belong to theTrend/Activity category.

Duration

Choose this option to include all the businessentities when you run or schedule a report.

Entire Domain

Choose this option to include selectedbusiness entities when you run or schedulea report. In the table that lists all thebusiness entities in Veritas OperationsManager, you can specify the businessentities that you want to include.

Select Business Entity


Creating a report scheduleYou can create a report schedule so that the report is generated at the time andfrequency that you specify.

You can schedule the report to run with the following frequency:

■ Daily

■ Weekly

■ Monthly

■ Once

In Veritas Operations Manager, business entities comprise Virtual BusinessServices and organization entities.

To create a report schedule


2 In the Reports view, do one of the following:

■ Identify the report that you want to schedule and click Schedule.

■ Click the report that you want to schedule. In the details view of the report,click Schedule.

401Managing reportsCreating a report schedule

3 In the Select Scope wizard panel, enter the details and click Next.


4 In the Schedule wizard panel, enter the details and click Next.

See “Schedule options” on page 402.

5 In the SpecifyScheduleDetails wizard panel, enter the details and click Next.

See “Specify Schedule Details options” on page 403.

6 In the Summary wizard panel, review the information and click Finish.

7 In the Result panel, click OK.

See “Editing a report schedule” on page 404.

See “Enabling a report schedule” on page 405.

See “Disabling a report schedule” on page 405.

See “Removing a report schedule” on page 406.

Schedule optionsUse this wizard panel to specify the recurrence of a report schedule.

Table 17-2 Schedule options

DescriptionField

Enter the name of the schedule.Schedule Name

You can enter the following data to specifythe date range for which you want toschedule the report.

■ In the Start Date field, enter the date onwhich you want to commence the reportgeneration.

■ In the EndDate field, enter the date untilwhich you want to generate the report.This field is not displayed if you selectthe report generation frequency as Once.

Date Range

Managing reportsCreating a report schedule

402

Table 17-2 Schedule options (continued)

DescriptionField

Enter the frequency at which the reports areto be generated with in the specified daterange.

You can specify any of the followingfrequencies for a report:

■ Daily

■ Weekly

■ Monthly

■ Once

Frequency

Specify the time at which the report is to begenerated within the date range andfrequency.

When



Specify Schedule Details optionsUse this wizard panel to choose the output type for the report that you schedule.

This panel lets you choose one of the following output types:

■ Email

■ Archive

Table 17-3 Specify Schedule Details options

DescriptionField

Choose this option if you want to send thereport through email after it is generatedbased on the schedule that you create.

Email

Subject line of the report email.

By default, the subject line is 'Emailing:Name of the report'.

You can edit the subject line, if required.

Subject

403Managing reportsCreating a report schedule

Table 17-3 Specify Schedule Details options (continued)

DescriptionField

Enter one or more email addresses to whichyou want to send the report. Use ';' toseparate the email addresses.

To email address(s)

Choose this option if you want to archive thereport after it is generated based on theschedule that you create.

Archive

Enter the file name in which the report is tobe archived.

Archive File Name



Editing a report scheduleYou can edit the details of a report schedule that you have created.

Note: In Veritas Operations Manager, business entities comprise Virtual BusinessServices and organization entities.

To edit a report schedule


2 In the Reports view, click the report for which you want to edit the reportschedule.

3 In the details view of the report, in the Schedules table, do one of thefollowing:

■ Select the check box for the schedule that you want to modify and on thetop of the Schedules table, click Actions > Edit.

■ Right-click on the row of the schedule to display the shortcut menu, selectEdit.

4 In the Select Scope wizard panel, modify the details, if required, and clickNext.


Managing reportsEditing a report schedule

404

5 In the Schedule wizard panel, modify the details, if required, and click Next.

See “Schedule options” on page 402.

6 In the SpecifyScheduleDetails wizard panel, modify the details, if required,and click Next.

See “Specify Schedule Details options” on page 403.

7 In the Summary wizard panel, review the information that you have modifiedand click Finish.




See “Removing a report schedule” on page 406.

Enabling a report scheduleYou can enable a report schedule that you have created.

To enable a report schedule


2 In the Reports view, click the report for which you want to enable theschedule.


■ Select the check box for the schedule that you want to enable and on topof the Schedules table, click Actions > Enable.

■ Right-click on the row of the schedule to display the shortcut menu, selectEnable.

4 In the Enable Schedule panel, click Yes.


See “Disabling a report schedule” on page 405.

Disabling a report scheduleYou can disable a report schedule that you have created.

405Managing reportsEnabling a report schedule

To disable a report schedule


2 In the Reports view, click the report for which you want to disable theschedule.


■ Select the check box for the schedule that you want to disable and on topof the Schedules table, click Actions > Disable.

■ Right-click on the row of the schedule to display the shortcut menu, selectDisable.

4 In the Disable Schedule panel, click Yes.



Removing a report scheduleYou can remove a report schedule that you have created.

To remove a report schedule


2 In the Reports view, select the report for which you want to remove theschedule.

3 In the details page of the report, in the Schedules table, do one of thefollowing:

■ Select the check box for the report schedule that you want to remove andon top of the Schedules table, click Actions > Delete.

■ Right-click on the row of the schedule to display the shortcut menu, selectDelete.

4 In the Delete Schedule panel, click Yes.




Managing reportsRemoving a report schedule

406

Archiving reportsYou can archive the contents of a report to view later or to email to other users.The data that is displayed in the archived report represents the state of themanaged objects in the network when the report was created. For example, anoperator can archive a report that shows the performance data at midnight anda system administrator can review the next morning.

Archived reports are stored on Management Server so that you and other userscan display them in the console.

When you no longer need archived reports, you can delete them.

To archive a report

1 In the Veritas Operations Manager console, display the report.

2 On the top-right of the window that displays the report, click Archive.

3 In the Archive wizard panel, enter the details and click OK.

See “Archive options” on page 407.


To view an archived report


2 In the Reports view, click the report for which you want to view the versionof the report that you have archived earlier.

3 In the details view, in the ArchivedReports table, click the name of the reportthat you want to view.

The time and date at the top of the report identify when the archived reportwas created.



Archive optionsUse this wizard panel to create an archive of the report that is currently displayed.You can view the archived instances of a report in the Report details view.

407Managing reportsArchiving reports

Table 17-4 Archive options

DescriptionField

Enter the name of the file for the archived report data.Veritas Operations Manager saves the archived reports inthe HTML format.

The file name should not contain any of the followingcharacters:

\ / : * ? " < > | )

Archive File Name


Sending a report through emailYou can send a newly generated report through email. Also, you can send anarchived report through email from the details view of the report.

Note: Before you send the report through email, you must define SMTP server ,SMTP Port, and Sender Account in the SMTP Setting view. To specify the SMTPsettings in the console, select Settings > General.

To send a new generated report through email

1 In the Veritas Operations Manager console, display a report.

2 On the top-left of the window that displays the report, click Email.

3 In the Email Report Data wizard panel, enter the details and click Yes.

See “Email options” on page 409.


To send an archived report through email


2 In the Reports view, click the report for which you want to send an archievedreport through email.

3 In the details view of the report, in the ArchivedReports table, do one of thefollowing:

■ Select the check box for the report that you want to send through emailand on top of the Archived Reports table, click Actions > Email.

Managing reportsSending a report through email

408

■ Right-click on the row of the archived report to display the shortcut menu,select Email.

4 In the Email Archived Report panel, enter the details and click OK.

See “Email Archived Report options” on page 409.





Email Archived Report optionsUse this wizard panel to forward the selected archived report to an email recipient.

Table 17-5 Email Archived Report

DescriptionField

Enter the name of your network’s SMTP server.

Example: SMTPServer1.example.com

SMTP ServerName

Enter the sender’s email address.


From emailaddress

Enter the subject of the email.

Example: Archived Report from Friday

Subject

Enter the email address of one or more recipients. Separate emailaddresses with a semicolon (;).

Example: [email protected]; [email protected]

To emailaddress(s)


Email optionsUse this wizard panel to send an HTML copy of the report data to one or moreemail recipients.

409Managing reportsSending a report through email

Table 17-6 Email Report Data

DescriptionField

Enter the name of your network’s SMTP server.Maximum field length is 255 characters.

Example: SMTPServer1.example.com

SMTP Server Name

Enter the sender’s email address.


From email address

Enter the subject of the email. Maximum field lengthis 255 characters.

Example: Storage Allocation Summary Report

Subject

Enter the email address of one or more recipients.Separate email addresses with a semicolon (;).

Example: [email protected]; [email protected]

To email address(s)


Deleting an archived reportIn the details view of a report, you can delete an archived report.

To delete an archived report

1 In the Veritas Operations Manager console, display the Report.

2 In the details view of the report, in the ArchivedReports table, do one of thefollowing:.

■ Select the check box for the archived report that you want to remove andon top of the Archived Reports table, click Actions >Delete.

■ Right-click on the row of the archived report to display the shortcut menu,select Delete.

3 In the Delete Archived Reports panel, click Yes.

4 In the Results panel to confirm the action, click OK.


Managing reportsDeleting an archived report

410

Exporting report data to a fileWhen you export a report, the report data is captured on your computer in acomma-separated (.csv) file format. You can then open the file using either aspreadsheet program or a text editor.



To preserve report data in a comma-separated file

1 In Veritas Operations Manager console, click Reports.

2 In the Reports view, run the report.

3 In the window that displays the report, do one of the following:

■ To export the summary part of a report to a .csv file, select the Summarytab. Click Export at the top-right of the report window.

■ To export the data in the tables in a report to a .csv file, select the Detailstab. Click the Table Tasks icon at the top-right of a table, and click Save.

4 In the dialog box, select Save File, and click OK.

5 In the dialog box that displays, specify a name for the file and select a path.Click OK.

The data in the table is saved in the location you specify.


411Managing reportsExporting report data to a file

Managing reportsExporting report data to a file

412

Managing schedules


■ About managing schedules in Veritas Operations Manager

■ Enabling schedules

■ Disabling schedules

■ Deleting schedules

About managing schedules in Veritas OperationsManager

In Veritas Operations Manager, you can view the various schedules that run inthe system. The following are the two types of schedules that Veritas OperationsManager contains:

■ Schedules, which you can create using the Veritas Operations Manager console.

■ Preconfigured schedules, which are running on the managed hosts. Theseschedules are created when you added managed host to Veritas OperationsManager Management Server.

Note: You can create the schedules from the respective categories in VeritasOperations Manager.

You can view all the global schedules that are created on various events in VeritasOperations Manager in the Schedules view. Veritas Operations Manager lets youmanage the schedules that you have created.

18Chapter

The security group and the associated business entity to which you belong decidesthe ownership of the schedule that you have created. Only the users who belongto the same security group can enable, disable, or remove the schedules.

In Veritas Operations Manager, the schedules belong to the following categories:

■ Policy Check

■ Licenses

■ DR Fire Drill

■ Report

■ System

■ Refresh Snapshot

■ HA Fire Drill

In the Schedules view, you can perform the following tasks:

■ Enable the schedules.

■ Disable the schedules.

■ Remove the schedules.

See “Enabling schedules” on page 414.

See “Disabling schedules” on page 415.

See “Deleting schedules” on page 415.

Enabling schedulesIn Veritas Operations Manager, you can enable one or more schedules in theSchedules view.

To enable schedules

1 In the Veritas Operations Manager console, click Settings > Schedules.

2 In the Schedules view, select the check boxes for the schedules that you wantto enable and click Actions > Enable.

3 In the Enable Schedule(s) panel, review the name and the recurrenceinformation of the selected schedules and click OK.




Managing schedulesEnabling schedules

414

Disabling schedulesIn Veritas Operations Manager, you can disable one or more schedules in theSchedules view.

To disable schedules


2 In the Schedules view, select the check boxes for the schedules that you wantto disable and click Actions > Disable.

3 In the Disable Schedule(s) panel, review the name and the recurrenceinformation of the selected schedules and click OK.




Deleting schedulesIn Veritas Operations Manager, you can delete one or more schedules in theSchedules view.

To delete schedules


2 In the Schedules view, select the check boxes for the schedules that you wantto delete and click Actions > Delete.

3 In the Delete Schedule(s) panel, review the name and the recurrenceinformation of the selected schedules and click OK.




415Managing schedulesDisabling schedules

Managing schedulesDeleting schedules

416

Managing Veritas DynamicMultipathing paths


■ About using the Veritas DMP Maintenance functionality in Veritas OperationsManager

■ Disabling the DMP paths on an array

■ Disabling the DMP paths on an initiator

■ Re-enabling the DMP paths on an array or initiator

■ Resuming an incomplete DMP maintenance case

■ Reviewing the output and results of a completed DMP maintenance case

■ Removing a completed DMP maintenance case record

About using the Veritas DMP Maintenancefunctionality in Veritas Operations Manager

Dynamic Multipathing (DMP) lets you direct the communication to the storagethrough different sets of nodes to achieve failover and load balancing. When aconnection fails, DMP spreads the communication to alternate paths automatically.Veritas Operations Manager provides you the options of disabling the DMP pathsby choosing the arrays or the specific initiators in your datacenter. DMP operationscan done both on physical hosts running DMP as well as VMware ESX serversrunning VxDMP.

In certain circumstances, you may want to perform maintenance operations onthe array ports or on the initiators in your datacenter. For example, you may want

19Chapter

to upgrade the firmware that has been installed on one or more initiators. In suchsituations, you may want to temporarily disable the DMP paths that connect thesearray ports and the initiators to the storage, and re-enable these paths after themaintenance operations are completed. When you temporarily disable the DMPpaths that are connected to an array port or on an initiator, the communicationto the storage is maintained through an alternate path.

Before you disable the DMP paths, you must ensure that the connected resourceshave alternate paths to the underlying physical storage. Veritas OperationsManager provides you options to verify the associated volumes, disk groups, hosts,and applications that currently use the storage that is connected through theselected initiators or array ports.

The following table lists the user privileges that are required for performing theDMP maintenance operation.:

Actions allowedUser role

Can manage all resources in the domain. Thedomain admin user can complete themaintenance cases that were started by anadmin, domain operator, or an operator.

Domain Admin

Allowed to perform DMP maintenance onthe arrays and the initiators that areconnected to hosts on which they haveadmin access.

Admin with storage access

Allowed to perform DMP maintenance onlyon the initiators that are connected to hostson which they have admin access.

Admin without storage access

Note: You cannot use Veritas Operations Manager to manage the DMP paths forWindows managed hosts.

See “Veritas DMP Maintenance Result Summary panel” on page 430.

See “Veritas DMP Maintenance Associations Report” on page 423.

Disabling the DMP paths on an arrayIn certain circumstances, you may want to perform maintenance operations onthe array ports or array adapters in your datacenter. For example, you may wantto upgrade the firmware that has been installed on the array adapter. In such asituation, you may want to temporarily disable the DMP paths that connect this

Managing Veritas Dynamic Multipathing pathsDisabling the DMP paths on an array

418

array adapter to the storage, and re-enable these paths after the maintenanceoperations are completed. When you temporarily disable the DMP paths on anarray port or an array adapter, the communication to the storage is maintainedthrough an alternative path.

Veritas Operations Manager lets you disable the DMP paths by choosing specificarrays in your datacenter.

To disable the DMP paths on an array


■ Select Solutions to go the Solutions page. Under Veritas DMPMaintenance, click Start new Veritas DMP Maintenance case.

■ Select Manage > Enclosures. In the Enclosures list page, select anenclosure and click Actions > Veritas DMP Maintenance.

2 In the Start panel, ensure that Array is selected, and enter the requiredinformation. Click Next.

See “Start panel options” on page 420.

3 In the SelectEnclosure wizard panel, choose the enclosure that contains thearray port or the array adapter on which you want to perform maintenance.Click Next.

See “Select Enclosure panel options” on page 421.

4 In the SpecifyArrayPort(s) wizard panel, choose the array port or the arrayadapter that contains the ports on which you want to perform maintenance.You can choose from array adapters only if the Veritas Operations ManagerStorage Insight Add-on is configured for the selected array.

See “Specify Array Port(s) panel options” on page 422.

5 In the PathDisableConfirmation panel, review the details of the DMP paths.To view the information on the relationship of the DMP paths with otherresources in your datacenter, click View Associations Report.

See “Path Disable Confirmation panel options” on page 422.


6 In the PathDisableConfirmation panel, click Disable to disable all the listedDMP paths.


7 In the PathsDisabled panel, review the details of the disabled paths and thecommands that were run to complete the operation. Do one of the following:

419Managing Veritas Dynamic Multipathing pathsDisabling the DMP paths on an array

■ To save and close the configuration and re-enable the DMP paths later,click Save&Close. If you choose this option, you can re-enable the DMPpaths later using the options available on the Solutions page, or using theUnfinished Cases drop-down in the Start wizard panel.

■ To re-enable the DMP paths after the array port or the array adaptermaintenance operations are completed, click Next.

See “Paths Disabled panel options” on page 424.

See “Re-enabling the DMP paths on an array or initiator” on page 427.

Start panel optionsUse this wizard panel to start a new Dynamic Multipathing (DMP) maintenancecase or resume a partially completed DMP maintenance case.

This panel lets you specify a name for a new DMP maintenance case that you wantto start. You can use this name to refer to the DMP maintenance case with thisname later on.

You can resume an incomplete DMP maintenance case by selecting the case namein this panel.

Table 19-1 Start panel options

DescriptionField

Start New Veritas DMP Maintenance Case

Lets you select the storage object to performthe DMP maintenance operation. Choose:

■ Array to disable the DMP paths toperform maintenance on an array port,or an array adapter (if Veritas OperationsManager Storage Insight Add-on isconfigured for the array) .

■ Initiator to disable the DMP paths toperform maintenance on an initiator.

Maintenance Type

Name of the new DMP maintenance case thatyou want to start. You can use this name torefer to the case later on.

Case Name

The additional information that you want toinclude for the new DMP maintenance case.

This field is optional.

Description


420

Table 19-1 Start panel options (continued)

DescriptionField

Resume Existing Veritas DMP Maintenance Case

From the drop-down list, select theincomplete DMP maintenance case that youwant to complete.

Unfinished Cases

See “Disabling the DMP paths on an array” on page 418.

See “Disabling the DMP paths on an initiator” on page 424.

Select Enclosure panel optionsUse this wizard panel to select the enclosure that contains the array ports onwhich you want to perform maintenance operations.

This panel lists the enclosures available in Veritas Operations Manager that haveVeritas DMP configured on exported LUNs. It does not list the enclosures that donot use DMP. To filter the list, enter the keywords, such as the first few letters ofthe enclosure name, in the Filter field.

Select the enclosure that contains the array ports on which you want to performmaintenance operations. When you select the option, the row that represents theenclosure is highlighted.

Table 19-2 Select Enclosure panel options

DescriptionsField

Name of the disk enclosureName

Serial number of the disk enclosureSerial

Name of the manufacturer of the diskenclosure

Vendor

Name of the array modelProduct

Type of arrayType

Total number of the disk enclosures that arelisted on the panel

Total Objects



Specify Array Port(s) panel optionsUse this wizard panel to select the array ports on which you want to disable theassociated DMP paths. You can also use this wizard to clear the paths that you donot want to disable.

This panel displays the names of the array ports and their Array Port WWN. Selectone or more array ports on which you want to disable the associated DMP paths.To filter the list, enter the keywords (preferably, the first few letters of theenclosure) in the Filter field.

By default, when you select an array port, all the paths that are associated withthat array port are also selected.

You cannot select any non-redundant paths that are associated with an arrayport. Single paths are highlighted in red.



Path Disable Confirmation panel optionsUse this wizard panel to view the details of the DMP paths that you have selectedfor disabling.

You can click the View Association Report link to view the information on therelationship of the DMP paths that you want to disable with other storageresources.

Table 19-3 Path Disable Confirmation panel options

DescriptionField

Names of the DMP paths that you haveselected for disabling

Name

Current status of the DMP Paths that youhave selected for disabling

Status

Name of the disk where the path is locatedDevices

The number of the active DMP pathsActive Paths

Host to which the DMP Paths that you haveselected for disabling is connected

Host

Initiator to which the DMP path is associatedInitiator


422

Table 19-3 Path Disable Confirmation panel options (continued)

DescriptionField

Array port to which the DMP Paths that youhave selected for disabling is associated

Array Port

Total number of DMP Paths that you haveselected for disabling

Total Objects


Veritas DMP Maintenance Associations ReportUse this wizard panel to understand the relationship between the DynamicMultipathing (DMP) paths that you want to disable and other resources in yourdatacenter. With DMP, you can avoid the disruptions that can occur in the accessto your storage resources when you need to perform upgrades and maintenance.This report helps you identify the related applications so that you can inform theappropriate persons about the upcoming maintenance action.

Table 19-4 Veritas DMP Maintenance Associations Report fields

DescriptionField

Name of the enclosure that contains thearray ports to which the DMP paths that youwant to disable are associated. If you areperforming the DMP maintenance on aninitiator, the selected enclosure is notdisplayed in this report.

Selected Enclosure

Name of the DMP maintenance case that youentered.

Case Name

Selected array port on which you want todisable the DMP paths.

Associations for Array Port

The details of the business entities that areassociated with the selection

Business Entities

The details of the virtual machines that areassociated with the selection.

Virtual Machines

The details of the hosts that are associatedwith the selection.

Hosts


Table 19-4 Veritas DMP Maintenance Associations Report fields (continued)

DescriptionField

The details of the volumes that areassociated with the selection.

Volumes

The details of the disks that are associatedwith the selection.

Disks


Paths Disabled panel optionsUse this wizard panel to view the output summary of the DMP path disablingoperation. This wizard panel displays the following information:

Table 19-5 Path Disabled panel options

DescriptionField

■ Total number of successful commands.

■ Total number of failed DMP commands.

Path Disable Operation Output Summary

■ Hosts on which the successful DMPcommands were run

■ Details of the DMP paths that aredisabled

■ Details of the failed DMP commands andthe reason for the failure.

Command Details



Disabling the DMP paths on an initiatorIn certain circumstances, you may want to perform maintenance operations onthe initiators in your datacenter. For example, you may want to upgrade thefirmware that has been installed on one or more initiators. In such situations, youmay want to temporarily disable the Dynamic Multipathing (DMP) paths thatconnect these initiators to the storage, and re-enable these paths after themaintenance operations are completed. When you temporarily disable the DMPpaths on an initiator, the communication to the storage is maintained throughan alternative path.

Managing Veritas Dynamic Multipathing pathsDisabling the DMP paths on an initiator

424

Veritas Operations Manager lets you disable the DMP paths by choosing specificinitiators.

To disable the DMP paths on an initiator


■ Select Solutions to go the Solutions page. Under Veritas DMPMaintenance, click Start new Veritas DMP Maintenance case.

■ Select Manage > Hosts. In the Hosts list page, click on a host, and clickAdapter tab. Select the required initiator from the Initiator table, andclick Actions > Veritas DMP Maintenance.

2 In the Start panel, and enter the required information. Click Next.


3 In the SelectHost(s) panel, select one or more hosts that contain the initiator.Click Next.

See “Select Host(s) panel options” on page 426.

4 In the Select Initiators panel, select one or more initiators that contain theDMP paths that you want to disable.

See “Select Initiators panel options” on page 426.

5 In the PathDisableConfirmation panel, review the details of the DMP paths.To view the information on the relationship of the DMP paths with otherstorage resources in your datacenter, click View Associations Report.



6 In the PathDisableConfirmation panel, click Disable to disable all the listedDMP paths.


7 In the PathsDisabled panel, review the details of the disabled paths and thecommands that were run to complete the operation. Do one of the following:

■ To save and close the configuration and re-enable the DMP paths later,click Save&Close. If you choose this option, you can re-enable the DMPpaths later using the options available on the Solutions page, or using theUnfinished Cases drop-down in the Start wizard panel.

■ To re-enable the DMP paths after the array or the array adaptermaintenance operations are completed, click Next.



425Managing Veritas Dynamic Multipathing pathsDisabling the DMP paths on an initiator

Select Host(s) panel optionsUse this wizard panel to select the hosts that contain the initiators on which youwant to perform maintenance.

You can enter the keywords, such as the first few letters of the host name, in theFilter field to filter the list. You can filter this list by the name of the host, the IPaddress, the architecture of the host, or by the platform the host runs.

Note: You cannot use Veritas Operations Manager to manage the DMP paths forWindows managed hosts.

Table 19-6 Select Host(s) panel options

DescriptionField

Name of the hostName

The IP address of the hostIP Address

The architecture of the host, such asPowerPC and SPARC

Architecture

The operating system that the host usesPlatform


Select Initiators panel optionsUse this wizard panel to select the initiators to perform maintenance by disablingthe Dynamic Multipathing (DMP) paths. You can select multiple initiators fromthis list at a time.

You can enter the keywords, such as the first few letters of the initiator name, inthe Filter fields to filter the list. You can filter this list by the name of the initiator,the version of the driver, version of the firmware, or by the name of the vendor.

Table 19-7 Select Initiators panel options

DescriptionField

The name of the initiatorName

The host to which the initiator is associatedHost

The version of the driver for the initiatorDriver Version

Managing Veritas Dynamic Multipathing pathsDisabling the DMP paths on an initiator

426

Table 19-7 Select Initiators panel options (continued)

DescriptionField

The version of the firmware that is used onthe initiator

Firmware Version

The manufacturer of the initiatorVendor


Re-enabling the DMP paths on an array or initiatorIn Veritas Operations Manager, you can re-enable the DMP paths that you havedisabled as part of the maintenance operation. You can re-enable the DMP pathsin the following ways:

■ Immediately after disabling the DMP paths for an array port, array adapter,or an initiator

■ Using the [Totalnumberofwaitingcases] case(s)waiting foruseraction linkon the Solutions page

■ Using the wizard panel to start a new DMP maintenance case

To re-enable the DMP paths immediately after disabling them

1 After you disable the DMP paths on an array or an initiator, click Next.


2 In the Paths Re-Enable Confirmation panel, click Re-Enable.

See “Paths Re-Enable Confirmation panel options” on page 429.

3 In the Paths Enabled panel, review the details of the re-enabled paths. ClickNext.

See “Paths Enabled panel options” on page 429.

4 In the VeritasDMPMaintenanceResult Summary page, view the details ofthe current paths and the commands run to complete the operation. ClickClose.


427Managing Veritas Dynamic Multipathing pathsRe-enabling the DMP paths on an array or initiator

To re-enable the DMP paths using the Solutions home page option

1 In the Veritas Operations Manager console, select Solutions to go theSolutions page.

2 Under Veritas DMP Maintenance, click the link for the cases pending forthe user action.

3 In the Veritas DMP Maintenance Waiting Cases page, select the pendingcase and click Actions > Resume Case and Re-Enable Paths







To re-enable the DMP paths using the Start wizard panel


2 Under VeritasDMPMaintenance, click StartnewVeritasDMPMaintenancecase.

3 In the Start panel, click Resume Existing Veritas DMP Maintenance Caseand choose a case name from the Unfinished Cases drop-down list. ClickNext.








Managing Veritas Dynamic Multipathing pathsRe-enabling the DMP paths on an array or initiator

428


Paths Re-Enable Confirmation panel optionsUse this wizard panel to view the details of the DMP paths that you want tore-enable after performing maintenance on the associated storage resource. TheseDMP paths were disabled before you performed maintenance.

Table 19-8 Paths Re-enable Confirmation panel options

DescriptionField

Name of the DMP paths that you want tore-enable

Name

Disk device to which the DMP path isassociated

Device

Host to which the DMP path is associatedHost

Initiator to which the DMP path is associatedInitiator

Array port to which the DMP Paths that youwant to re-enable is associated

Array Port


Paths Enabled panel optionsUse this wizard panel to view the output summary of the path re-enable operation.

On this panel, you can view the following:

■ Details of the path re-enable commands that successfully executed

■ DMP paths that are re-enabled

■ Hosts on which the commands that successfully disabled the DMP paths areexecuted

■ Commands that failed to re-enable the DMP paths, if any

This panel displays the name of the DMP maintenance case that you are currentlyprocessing. It also displays the name of the enclosure that contains the arrayports with which the DMP paths that you are re-enabling are associated.

Under Path Enable Operation Output Summary, you can view the path enablecommands that are successfully executed. You can also view the path enablecommands that are failed along with the output details.

429Managing Veritas Dynamic Multipathing pathsRe-enabling the DMP paths on an array or initiator

Under Command Details, you can view the details of the path enable commandsthat successfully executed and the path enable commands that failed. For thesuccessful path enable commands, this panel displays the DMP paths that areenabled and the host with which these paths are associated. You can also viewthe details of the path enable commands that failed, if any.


Veritas DMP Maintenance Result Summary panelUse this wizard panel to view the overall summary of the Dynamic Multipathing(DMP) maintenance case that you have completed.

This panel lists the following details:

■ DMP paths that were managed and their current statuses

■ All commands that are executed during the DMP maintenance operation andtheir results

Table 19-9 Veritas DMP Maintenance Result Summary panel options

DescriptionField

Current Path Status

Name of the DMP path on which you havecompleted the state management

Name

The current status of the DMP pathStatus

The disk device to which the DMP path isassociated

Device

Host to which the DMP path is associatedHost

The initiator to which the DMP path isassociated

Initiator

Array port to which the DMP path isassociated

Array Port

All Commands Executed and Results

Displays the names of the commands thatare run for disabling the DMP paths with thename of the host on which they were run

Disable Path Commands Executed

Managing Veritas Dynamic Multipathing pathsRe-enabling the DMP paths on an array or initiator

430

Table 19-9 Veritas DMP Maintenance Result Summary panel options (continued)

DescriptionField

Displays the name of the commands that arerun for enabling the DMP paths with thename of the host on which they were run

Enable Path Commands Executed




See “Reviewing the output and results of a completed DMP maintenance case”on page 432.

Resuming an incomplete DMP maintenance caseUsing Veritas Operations Manager, you can disable the Dynamic Multipathing(DMP) paths in your datacenter before you perform the maintenance of the arrayports or the initiators. After the maintenance operations are completed, you canre-enable the DMP paths that are connected to the arrays and initiators. VeritasOperations Manager provides you options for re-enabling the DMP paths usingthe same wizard panel that you used for disabling the DMP paths. However, if youwant to save and close the configuration after the disabling operation is complete,you can re-enable the DMP paths from the [Totalnumberofwaitingcases]case(s)waiting for user action link on the Solutions home page.

To resume an incomplete DMP maintenance case


2 In the Solutions page, under Veritas DMP Maintenance, click the [Totalnumber of waiting cases] case(s) waiting for user action link.

3 In the DMP Maintenance Waiting Cases page, under Waiting Cases, selectthe incomplete DMP maintenance case that you want to resume. Click Actions> Resume Case and Re-enable Paths.



431Managing Veritas Dynamic Multipathing pathsResuming an incomplete DMP maintenance case





See “Removing a completed DMP maintenance case record” on page 433.

Reviewing the output and results of a completedDMPmaintenance case

Using the Veritas Operations Manager console, you can view the status of theDMP path and the list of commands that were run as part of the DMP maintenanceprocess.

You can view these details in the following two ways:

■ Immediately after the process of re-enabling the DMP paths after themaintenance operations are completed on the array ports or the host busadapters

■ Using the Veritas DMP Maintenance Completed Cases page

This topic describes how you can view the output and the results of a completedDMP maintenance case using the Veritas DMP Maintenance Completed Casespage.

To review the output and the results of a completed DMP maintenance case


2 In the Solutions page, under Veritas DMP Maintenance, click the [Totalnumber of] case(s) completed link.

3 In the Veritas DMP Maintenance Completed Cases page, under CompletedCases, select the completed DMP maintenance cases that you want to remove.Click Actions > Show Case Output and Results.

4 In the Veritas DMP maintenance Result Summary page, review theinformation.



Managing Veritas Dynamic Multipathing pathsReviewing the output and results of a completed DMP maintenance case

432


Removing a completedDMPmaintenance case recordThe Veritas Operations Manager database keeps the records of each of thecompleted DMP maintenance cases. If you do not want to keep this record for alonger period of time, you can remove them from the database using the VeritasOperations Manager console.

To remove a completed DMP maintenance case record


2 In the Solutions page, under Veritas DMP Maintenance, click the [Totalnumber of] case(s) completed link.

3 In the Veritas DMP Maintenance Completed Cases page, under CompletedCases, select the completed DMP maintenance cases that you want to remove.Click Actions > Delete Cases.

4 In the Delete Completed Case confirmation panel, click Yes.

433Managing Veritas Dynamic Multipathing pathsRemoving a completed DMP maintenance case record

Managing Veritas Dynamic Multipathing pathsRemoving a completed DMP maintenance case record

434

Managing extendedattributes on storageobjects


■ About using extended attributes on the objects

■ Viewing the list of extended attributes

■ Creating an extended attribute on one or more storage objects

■ Modifying an extended attribute

■ Removing an extended attribute

■ Setting values to the extended attributes on one or more objects

■ Modifying the extended attributes value on an object

About using extended attributes on the objectsAn extended attribute is an additional user-defined attribute that providesadditional details about an object in Veritas Operations Manager. This informationabout an object is in addition to the details that Veritas Operations Managerdiscovers for that object. You can define multiple extended attributes on VeritasOperations Manager objects. You can use the extended attributes to search, filter,and sort the objects in Veritas Operations Manager.

You can define an extended attribute in Veritas Operations Manager and associateit with the relevant objects. You need to set the value for the extended attributewhen you associate it with the object. Also, you can associate an extended attribute

20Chapter

with the base object type of a business entity. When you associate the extendedattributes with a business entity, it applies the values for the extended attributesto all the objects that are part of the base object type of the business entity.

In Veritas Operations Manager, you can define the extended attributes only forthe following object types:

■ Host

■ File System

■ Disk group

■ Enclosure

■ Databases

■ Exchange Server

■ Cluster

■ Service Group

■ LUN

See “Creating an extended attribute on one or more storage objects” on page 437.

See “Viewing the list of extended attributes” on page 436.

Viewing the list of extended attributesIn Veritas Operations Manager, the ExtendedAttributes view lists all the extendedattributes that you have defined, in a table.

In the table that list the extended attributes, you can view the following details:

■ Unique name of the extended attribute that you have defined.

■ Object type that is associated with the extended attribute.

■ Whether you want to display the extended attribute as a column in the objectviews.

You can sort the table based on the Attributes Name column.

You can use the free text search box on the left side panel to filter the table thatlists the extended attributes. Also, you can use the options under the ObjectTypeheading to filter the Extended Attributes table.

In the Extended Attributes view, you can perform the following tasks:

■ Defining an extended attribute.

■ Modifying an existing extended attribute.

Managing extended attributes on storage objectsViewing the list of extended attributes

436

■ Removing an extended attribute.

To view the list of extended attributes in Veritas Operations Manager

◆ In the Veritas Operations Manager console, select Settings > ExtendedAttributes.


See “Modifying an extended attribute” on page 439.

See “Removing an extended attribute” on page 440.

See “About using extended attributes on the objects” on page 435.

Creating an extended attribute on one or morestorage objects

In the ExtendedAttributes view, Veritas Operations Manager lets you Create oneor more extended attributes for multiple object types. You can specify the namefor the extended attribute. Also, you can specify whether the extended attributethat you have created should appear as a column in the relevant object view.Otherwise, the extended attribute that you have created appears in the detailsview of the object. It also appears as a hidden column in the TableSettings dialogbox of the table in which the object is listed in Veritas Operations Manager. Youcan use the value that you have created for the extended attribute to search, filter,or sort the objects in the view.

Note:Only the users with the Domain Admin role can create an extended attributefor an object type.

The extended attributes that you create for an object type apply to all the objectsthat are part of the object type. After you create an extended attribute for an objecttype, other users with Administrator, Domain Operator, or Operator roles can setthe values for the extended attribute in the relevant views.

For example, you can create the extended attribute named Location on the Hostsobject type. All the hosts in the domain display this extended attribute. TheAdministrator who knows that a specific host that is located in New York can setthe value for the location attribute for that host as New York. In the host view,the Location column for that host displays the value as New York.

437Managing extended attributes on storage objectsCreating an extended attribute on one or more storage objects

To create an extended attribute on one or more storage objects

1 In the Veritas Operations Manager console, select Settings > ExtendedAttributes.

2 In the Extended Attributes view, click Actions > Create.

3 In the Create Extended Attribute wizard panel, enter the required data andclick OK.

See “Create Extended Attribute options” on page 438.

4 In the Results panel that confirms that the extended attribute is successfullycreated, click OK.


See “Removing an extended attribute” on page 440.


Create Extended Attribute optionsUse this wizard panel to create the extended attribute for one or more object types.

Table 20-1 Create Extended Attribute panel options

DescriptionField

Enter the name of the extended attribute.Veritas Operations Manager uses the namethat you enter in this field to identify theextended attribute that you create.

Note: Ensure that the name that you provideto the extended attribute is not used for anyof the existing attributes of the object types.

Name

Select one of the following object types forwhich you can create the extended attribute:

■ Host

■ File System

■ Disk group

■ Enclosure

■ Databases

■ Exchange Server

■ Cluster

■ Service Group

■ LUN

Object Type

Managing extended attributes on storage objectsCreating an extended attribute on one or more storage objects

438

Table 20-1 Create Extended Attribute panel options (continued)

DescriptionField

Select this check box against each object typeto display the extended attribute as a columnin the relevant object views or as an optionalcolumn in the Table Settings of table inwhich the object type is listed in VeritasOperations Manager. If you have not selectedthis check box, you can view the extendedattribute in the details view of the object.

Show as Column


Modifying an extended attributeIn the Extended Attributes view, Veritas Operations Manager lets you modifythe name of the extended attributes that you have defined.

Note:Only the users with the Domain Admin role can modify an extended attribute.

When you modify the name of the extended attribute, Veritas Operations Managerensures that the updated name is unique in the domain. Then, Veritas OperationsManager updates the objects to display the new name for the extended attribute.Also, you can set a different value for the modified external attribute in the objectviews. In this way, modifying an extended attribute is equivalent to defining anew extended attribute.

To modify an extended attribute in Veritas Operations Manager


2 In the ExtendedAttributes view, select the extended attribute that you wantto modify and click Actions > Modify.

3 In the EditExtendedAttribute wizard panel, modify the name of the extendedattribute and click OK.

See “Edit Extended Attribute options” on page 440.

4 In the Results panel that confirms that the extended attribute is successfullymodified, click OK.



439Managing extended attributes on storage objectsModifying an extended attribute

Edit Extended Attribute optionsUse this panel to modify the name of an extended attribute that you have defined.

Table 20-2 Edit Extended Attribute panel options

DescriptionField

Displays the name of the object type that youhave specified for the extended attribute.You cannot modify this field.

Object Type

Enter the new name of the extendedattribute.

Name


Removing an extended attributeIn the Extended Attributes view, Veritas Operations Manager lets you removean extended attribute that you have defined. When you remove an extendedattribute, it’s association with the objects are also removed. Therefore, theseextended attributes are not visible in the relevant object’s views.

Note:Only the users with the Domain Admin role can modify an extended attribute.

To remove an extended attribute in Veritas Operations Manager


2 In the ExtendedAttributes view, select the extended attribute that you wantto remove and click Actions > Delete.

3 In the Delete Extended Attribute wizard panel, click Yes.

4 In the Result panel that confirms that the extended attribute is successfullyremoved, click OK.



Managing extended attributes on storage objectsRemoving an extended attribute

440

Setting values to the extended attributes on one ormore objects

Veritas Operations Manager lets you set the values for the extended attributesthat are defined for a specific object. You can set the values for the extendedattributes from the relevant object views.

Note:Users with the Domain Admin, Admin, Domain Operator, and Operator rolescan set the values for an extended attribute.

If you want to set the values for the extended attributes of multiple objects, youmust select the objects in the relevant object views before you perform this task.For example, if you want to set the value for the extended attribute named Locationon multiple hosts, you must select those hosts in the Hosts view before you performthis task.

To set values to the extended attributes on one or more objects

1 In the Veritas Operations Manager console, navigate to the relevant objectview.

2 In the object view, in the table that lists the objects, select the check box onthe left side of one or more objects on which you want to set the value for theextended attributes.


■ At the top of the objects view table, click Environment > Set ExtendedAttributes.

■ Right-click the highlighted rows in the table that represent the object thatyou have selected. From the submenu, select Set Extended Attributes.

4 In the SetExtendedAttributes panel, select the check box on the left side ofthe name of the attribute.

See “Set Extended Attributes option” on page 442.

5 In the Value field, enter the value for the attribute and click OK.




441Managing extended attributes on storage objectsSetting values to the extended attributes on one or more objects

Set Extended Attributes optionUse this panel to specify the values for the extended attributes on the objects thatyou have selected in the objects table.

Table 20-3 Set Extended Attributes panel options

DescriptionField

Displays the name of the extended attributethat you have defined for the object.

Name

Enter the value that you want to specify forthe extended attribute.

Value


Modifying the extended attributes value on an objectVeritas Operations Manager lets you modify the values that you have set for theextended attributes defined for a specific object. You can modify the values forthe extended attributes from the details view of the relevant object.

To modify the values that are set for the extended attributes on an object

1 In the Veritas Operations Manager console, navigate to the relevant objectview.

2 In the object view, in the table that lists the objects, click the name of theobject to navigate to its details view.

3 In the details view of the object, on the task toolbar, select Environment >Edit Extended Attributes.

4 In the EditExtendedAttributes wizard panel, modify the extended attributevalue and click OK.

See “Edit Extended Attributes option (object)” on page 442.



Edit Extended Attributes option (object)Use this panel to modify the values that you have set for the extended attributeson a relevant object.

Managing extended attributes on storage objectsModifying the extended attributes value on an object

442

Table 20-4 Edit Extended Attributes panel options (object)

DescriptionField

Displays the name of the extended attributethat you have defined for the object.

Name

Displays the existing value for the extendedattribute. You can modify the value that isalready specfied in this field.

Value


443Managing extended attributes on storage objectsModifying the extended attributes value on an object

Managing extended attributes on storage objectsModifying the extended attributes value on an object

444

Veritas Operations Managercommand line interface


■ About the vomadm utility

■ Listing all configured enclosures using the vomadm utility

■ Host management using the vomadm utility

■ Deployment management using the vomadm utility

■ Business entity management using the vomadm utility

■ Service management using the vomadm utility

About the vomadm utilityThe vomadm utility lets you perform several operations falling into followingcategories:

OperationCategoryOption

Listing all enclosures configured throughStorage Insight Add-on

config-listarrayinfo

Host management in Veritas OperationsManager

HostManagementhost-mgmt

Deployment of hotfix in Veritas OperationsManager

deploymenthotfix

21Chapter

OperationCategoryOption

Business entities management in VeritasOperations Manager

BEManagementmakeBE

Service management in Veritas OperationsManager

Service-Managementservice

Note: You need to have administrative privileges to run these commands.

The host-mgmt and makeBE options can be used only on the Veritas OperationsManager Management Server. These commands are supported on UNIX andWindows operating system.

The vomadm command syntax is described below:

■ For Windows Management Server: c:\ProgramFiles\Veritas\VRTSsfmh\bin>perl.exe vomadm < command>

■ For UNIX Management Server: /opt/VRTSsfmh/bin/vomadm <command>

Listing all configured enclosures using the vomadmutility

Use the following command to list all the enclosures configured through StorageInsight Add-on:

vomadm arrayinfo --config-list <type> [--output-format <json>]

Where

config-list: Method used to configure the enclosure under Storage InsightAdd-on , default value is 'all'.

output-format: Type of output that the user wants, default is tabular format.

See “About the vomadm utility” on page 445.

Host management using the vomadm utilityUse the following commands to manage the configured hosts in Veritas OperationsManager.

vomadm host-mgmt [--remove --host <hostname> | --remove --hostfile

<file> | --list ]

Veritas Operations Manager command line interfaceListing all configured enclosures using the vomadm utility

446

Where

list: It lists all hosts configured as agents to Veritas Operations ManagerManagement Server.

remove: It removes specified host(s) from Veritas Operations Manager. To removesingle host, use the --host option. To remove multiple hosts use the --hostfileoption.

host: The name for the managed host as known by Veritas Operations ManagerManagement Server as listed in the --list option.

hostfile: The path to a file containing list of host names. Hosts should be listedin the file with each host on a new line.


Deployment management using the vomadm utilityUse the following commands to deploy hotfix using the vomadm utility:

vomadm hotfix [--install <hf> | --uninstall <hf-id> | --list ]

Where

hf: full path to the HotFix file

hf-id: ID of the HotFix


Businessentitymanagementusing thevomadmutilityThe makeBE command option in vomadm utility lets you perform various businessentity-related operations using the command line. For example, create a businessentity, import a business entity, export the content of a business entity and so on.

You can run these commands in context with both types of business entities -Organization Entities and Virtual Business Services. Three options are providedto manipulate the business entities. They are import, export, anduser_defined_import. With these commands, you also need to specify the infile(a CSV file) that contains the information about the business entity, its objects,and the type of operation you want to perform on the business entity.

The makeBE command syntax is as follows:

vomadm makeBE [--import <infile> | --export <outfile> |

--user_defined_import <infile>]

447Veritas Operations Manager command line interfaceDeployment management using the vomadm utility

infile: full path to the input file

outfile full path to the output file


Service management using the vomadm utilityUse the following command to manage the various services in Veritas OperationsManager:

vomadm service { --start | --stop | --restart | --status | --version

| --help } [process]

Where

start: Starts the specified service, or all the services that the script manages.

stop: Stops the specified service, or all the services that the script manages.

restart: Restarts the specified service, or all the services that the script manages.

status: Displays the status of the specified service, or all the services that thescript manages.

version: Displays the version of the VRTSsfmcs package or RTSsfmh package thatis installed on the Management Server host.

help: Displays help to use the service command and various options availablewith the command.

process: Name of any of the following process:

■ xprtld - Veritas Operations Manager Messaging Service

■ sd - Veritas Operations Manager watchdog

■ dcli - Veritas Operations Manager Distributed Command Line Daemon

■ db - Veritas Operations Manager Database Service

■ at - Veritas Operations Manager Authentication Service

■ web - Veritas Operations Manager Web Server

■ ALL - All the processes that the script manages


Veritas Operations Manager command line interfaceService management using the vomadm utility

448

Command file reference

This appendix includes the following topics:

■ sfmw

■ vomsc

■ vxlist

■ vomadm

■ xdistc

AAppendix

sfmwsfmw – startup and shutdown script for the Veritas Operations Manager Webapplication, Storage Management (SM) Web application, and Tomcat Web server.

SYNOPSISsfmw start | stop | restart | status | listports

DESCRIPTIONsfmw starts and stops the Tomcat Web server, the Veritas Operations ManagerWeb application, and the Storage Management (SM) Web application

KEYWORDSstart

Starts the Tomcat Web server, the Veritas Operations Manager Webapplication, and the Storage Management (SM) Web application, if not alreadyrunning.

stop

Terminates the Veritas Operations Manager Web application, StorageManagement (SM) Web application (if already running), and the Tomcat Webserver.

restart

Stops the Veritas Operations Manager Web application, the StorageManagement (SM) Web Application (if already running), and the Tomcat Webserver, then starts them.

status

Indicates whether the Veritas Operations Manager Web application is running.

listports

Displays the HTTPS port that the Tomcat Web server listens to forconnections.

NOTESOn UNIX, the default installation path is: /opt/VRTSsfmcs/cweb

The log for Veritas Operations Manager and the SM Web application resides bydefault in: /var/opt/VRTSsfmcs/esmweb/log

Command file referencesfmw

450

vomscvomsc – enables you to manage Veritas Operations Manager services on aUNIX-based Management Server.

SYNOPSISvomsc {start | stop | restart | status | version} {service | ALL}

DESCRIPTIONThe vomsc script lets you start, stop, or restart one or more Veritas OperationsManager services on a UNIX-based Management Server. You can also use thescript to check the status of one or more services. The change in the state of theservices is temporary. When the host is restarted, all the services are startedagain.

You can use the vomsc script to view the version of the VRTSsfmcs package andthe VRTSsfmh package that is installed on the Management Server host.

KEYWORDSstart

Starts the specified service, or all the services that the script manages.

stop

Stops the specified service, or all the services that the script manages.

restart

Restarts the specified service, or all the services that the script manages.

status

Displays the status of the specified service, or all the services that the scriptmanages.

version

Displays the version of the VRTSsfmcs package and the VRTSsfmh packagethat is installed on the Management Server host.

service

The services managed by the vomsc script that you can specify are:

■ xprtld - Veritas Operations Manager Messaging Service

■ sfmh-discovery - Veritas Operations Manager watchdog

451Command file referencevomsc

■ vxdcli - Foundation Distributed Command Line Daemon

■ vxsfmcsdb - Veritas Operations Manager Database Service

■ sfmsecd - Veritas Operations Manager Security Service

■ sfmcswd - Veritas Operations Manager Web console

ALL

Performs the operation on all the services that the script manages.

EXAMPLESThis section provides usage examples for vomsc.

EXAMPLE 1:

To start the xprtld service.

vomsc start xprtld

EXAMPLE 2:

To stop all the Veritas Operations Manager services that the vomsc script manages.

vomsc stop ALL

EXAMPLE 3:

To stop all the Veritas Operations Manager services that the vomsc script manages,and then start the services again.

vomsc restart ALL

EXAMPLE 4:

To display the status of the database service.

vomsc status vxsfmcsdb

NOTESThe default location of vomsc on UNIX is /opt/VRTSsfmcs/bin/.

On Windows, you can use the C:\Program

Files\Veritas\VRTSsfmcs\bin\vomsc.bat file.

Command file referencevomsc

452

vxlistvxlist – displays records of the Storage Foundation configuration.

SYNOPSISvxlist [-option] [keyword] [arguments] [storage_object_names ...]

DESCRIPTIONvxlist lists Storage Foundation objects.

To display the vxlist command output, the vxdclid daemon must be running.If vxdclid is not running, run /opt/VRTSsfmh/adm/dclisetup.sh as a root user.

KEYWORDSalert

Lists the Veritas Volume Manager alerts.

cache

Lists the Volume Manager cache objects.

disk

Lists the disks.

diskgroup|dg

Lists the Volume Manager disk groups.

dmp

Lists the supported Array Support Libraries (ASL).

enclosure|enclr|array

Lists the enclosures.

filesystem|fs

Lists the mounted file systems.

getfield

Lists the specified fields from Veritas Volume Manager (VxVM) records. Usedwith the -F option.

hba|hostport|controller|ctrl

Lists the controllers.

453Command file referencevxlist

lun

Lists the Storage Insight Add-on information of LUNs. The information isonly available if the host has been added to a Management Server domain,and the associated array has been enabled for Storage Insight.

The first use of the lun keyword fetches the array information fromManagement Server. Any vxlist lun command that is run within the nextone hour uses the vxdclid cache. The vxdclid cache may be stale if arrayparameters have been modified. The vxlist lun command that is run afterone hour of the lastvxlist lun command fetches the latest array informationfrom Management Server again.

To force the vxlist lun command to fetch the updated array information,use the rescan keyword.

nodeinfo

Lists the Cluster Volume Manager node information.

path

Lists the paths.

plex|pl

Lists the plexes.

rescan

Fetches updated Storage Foundation information.

See the lun keyword.

snapshot|snap

Lists the Volume Manager snapshots.

subdisk|sd

Lists the subdisks.

tag|tags

Lists the volume tags.

targetport|tca

Lists the target ports.

task

Lists the Volume Manager tasks that are running.

umfilesystem|umfs

Lists the unmounted file systems that are referenced in the file system tablefile.

Command file referencevxlist

454

volume|vol

Lists the Volume Manager volumes.

vset

Lists the Volume Manager volume sets.

OPTIONS-a|--all

Displays all fields or sections including those that have no data.

-d|--deliminator string

Uses the specified string instead of spaces to delimit fields in tabular display.

-e|--exact

Displays all size-related numbers in sectors.

See the -u option.

-F|--format "objtype:field1[,field2...] [objtype:field1[,field2...]]"

Displays the fields specified for one or more object types. For each objecttype, specify the object type, a colon, and a comma-separated list of fieldnames. A field name can be any field listed in the output of 'vxprint -m' forthat object type. The following object types are supported:

■ disk

■ diskgroup|dg

■ enclosure|enclr|array

■ filesystem|fs

■ hba|hostport|controller|ctrl

■ path

■ targetport|tca

■ volume|vol

■ vset

-k|--kilobyte

Displays all size-related numbers in kilobytes.

-g|--diskgroup dg

Lists storage objects in the specified disk group.

-H|--help [objtype]

Displays usage information.


-l|--long

Displays in long format.

-B|--bare field1[,field2...] objtype

Displays bare format. Displays only the specified long format fields

-O|--output [csv|long|table]

Displays information in the selected format. The default is the 'table' format.

-p|--property object_name1 object_name2...

Displays the property pages of the specified LUNs. The sections without dataare not displayed unless the --all option is used.

-q|--suppress

Suppresses headers in tabular output format.

-s|--sections sectionname,... object_name

Displays only the specified sections in the property page. Sections with nodata are not displayed unless the --all option is used.

-t|--table [default|lun|stats]

Displays LUN information in the specified table format. The default formatis 'default'.

-u|--unit [p|t|g|m|k|blocks|bytes|scaled]

Displays all size-related numbers in the specified unit. The default is 'scaled'.

EXAMPLESThis section provides usage examples for vxlist.

EXAMPLE 1:

To display vxlist usage for viewing information on disks.

vxlist -H disk

EXAMPLE 2:

To display the fields Device, Status, Log Info, and VDID for disks, in bare format,delimited by the '++' string.

vxlist -B "Device,Status,Log Info,VDID" -d ++ disk

EXAMPLE 3:

To display only the disks section in the property page for the volume named vol_1.

vxlist -s disks vol vol_1

EXAMPLE 4:

Command file referencevxlist

456

To display the property pages with the disks section for the volumes named vol_1

and vol_2.

vxlist -p -s disks vol vol_1 vol_2

EXAMPLE 5:

To display the fields device_tag, guid, and mediatype for the disk disk_1.

vxlist -g dg_1 -F disk:device_tag,guid,mediatype getfield disk_1

EXAMPLE 6

To display the specified disk and volume fields for the dg_1 disk group:

vxlist -g dg_1 -F "disk:device_tag,guid,mediatype volume:state"

getfield

FILES/etc/vx/dcli/sfm/conf/dcli_conf.ini

The vxlist and vxdclid configuration file

/etc/vx/dcli/log/server_A

The vxdclid log file

NOTESThe default location of vxlist is /opt/VRTSsfmh/bin/vxlist. There is also avxlist link named /etc/vx/bin/vxlist.

Windows-based Management Server does not support the vxlist command.


vomadmvomadm – enables you to perform Veritas Operations Manager related operationsusing the command line. The available options are listing configured enclosures,service management, host management, hotfix deployment management, andbusiness entity management.

SYNOPSISvomadm arrayinfo

vomadm host-mgmt

vomadm hotfix

vomadm makeBE

vomadm service

DESCRIPTIONUse arrayinfo option for listing configured enclosures, host-mgmt option forhost management,hotfixoption for hotfix deployment,makeBEoption for businessentities operations, and service option for service management.

KEYWORDSarrayinfo

Used to list all the enclosures configured through Storage Insight Add-on.

host-mgmt

Used to manage the configured hosts in Veritas Operations Manager.

hotfix

Used to install and uninstall hotfix.

makeBE

Used to perform various business entity-related operations. For example,create a business entity, import a business entity, export the content of abusiness entity.

service

Used to start, stop, or restart one or more Veritas Operations Manager serviceson a Management Server or to get help, version of VRTSsfmcs package andthe VRTSsfmh package, or status of one or more Veritas Operations Managerservices.

Command file referencevomadm

458

OPTIONSFor arrayinfo

[--config-list <type> [--output-format<json>] ]

For host-mgmt

[--remove --host <hostname> | --remove --hostfile <file> | --list

]

For hotfix

[--install <hf> | --uninstall <hf-id> | --list ]

For makeBE

[--import <infile> | --export <outfile> | --user_defined_import

<infile>]

For service

[{ --start | --stop | --restart | --status | --version | --help

} <process> ]

FILESLog files

/var/opt/VRTSsfmh/logs/vomadm.log

EXAMPLESThis section provides the usage example for vomadm.

EXAMPLE 1:

To list all the enclosures configured through Storage Insight Add-on in json format.

/opt/VRTSsfmh/bin/vomadm arrayinfo --config-list all --output-format

json

EXAMPLE 2:

To list all the hosts configured as agents toVeritas Operations ManagerManagement Server.

/opt/VRTSsfmh/bin/vomadm host-mgmt --list

EXAMPLE 3:

To uninstall a hotfix.

/opt/VRTSsfmh/bin/vomadm hotfix --unistall VRTSsfmch-4.1.142.0.sfa

EXAMPLE 4:

459Command file referencevomadm

To create a business entity using the makeBE command.

/opt/VRTSsfmh/bin/vomadm makeBE --import /tmp/Samplefile

EXAMPLE 5:

To display the status of all the services.

/opt/VRTSsfmh/bin/vomadm service --status All

EXAMPLE 6:

To start all the services.

/opt/VRTSsfmh/bin/vomadm service --start All

EXAMPLE 7:

To stop all the services.

/opt/VRTSsfmh/bin/vomadm service --stop All

NOTESThe default location of vomadm command is /opt/VRTSsfmh/bin/vomadm

Command file referencevomadm

460

xdistcxdistc – command-line interface to VRTSsfmh distributor

SYNOPSISxdistc [OPTIONS] --push localfile remotefile

xdistc [OPTIONS] --run --command arg1 arg2..

xdistc [OPTIONS] --push localfile remotefile --run --command arg1

arg2..

xdistc --results --id requestid [--wait duration]

DESCRIPTIONxdistc is the command-line interface to the VRTSsfmh distributor. You can usexdistc to copy files or run commands across all managed hosts in a centrallymanaged domain. You can perform these tasks on the available hosts that arecurrently running, and on the unavailable hosts when they are started. When yourun xdistc, the task that is specified with it continues to run in the backgroundeven when xdistc has stopped running.

You can run xdistc only from a Management Server host that has the xprtld

daemon running. You must be logged on as root to run xdistc.

OPTIONS--push localfile remotefile

Copies a file to multiple managed hosts. The symbolic names $TMPDIR,$VARDIR, and $TMPFILE can be used as destination file paths. $TMPDIR typicallypoints to the /tmp directory, but it may vary on Windows managed hosts.$VARDIR points to the /VRTSsfmh/var directory. To use, append the file nameafter the symbolic name. For example, $TMPDIR/myfile.txt, or$VARDIR/myfile2.txt. $TMPFILE creates a temporary file name ensuring nocollision with other files in /tmp. This is useful with the --run option.

You can specify only a few designated directories as the destination.

To overwrite existing files while copying, use the --force option.

--run --command arg1 arg2..

Runs a command on multiple managed hosts. In this form, a command isused from commands previously whitelisted on each destination host. Thearguments after the double dash are passed directly to the command. You

461Command file referencexdistc

can specify a request ID with the --id option. If the request ID is not specified,a random ID is internally created.

--push localfile remotefile --run --command arg1 arg2..

Used to copy files and run a command on multiple hosts simultaneously. Thisoption is useful when you want to copy an executable file to multiple managedhosts, and run it.

--results

Retrieves the stdout and stderr results from a run request. You can specifythis option with the --run option to view the results of the command that isexecuted. You must specify the request ID if you use the --results optionwithout the --run option. You can use the --wait option to specify the timethe xdistc script should wait to obtain the results.

--os osname

Specifies the operating system. The task that is specified with xdistc is runon the managed hosts that have the specified operating system running. Theosname must be specified as one of the following: SunOS, Linux, HP-UX,AIX, Windows. You can also specify multiple operating systems. For example,to specify AIX and Linux, use '/AIX|Linux/', including the single quotes.

--cpu cputype

Specifies the processor. The task that is specified with xdistc is run on themanaged hosts that have the specified processor. The cputype must bespecified as one of the following: sparc, x86_64, powerpc, x86, x64, i386,i686.

--host hostname

Specifies the host. The task that is specified with xdistc is run on the specifiedmanaged host. You can specify the option multiple times to specify multiplehosts.

--hostfile filename

Specifies a file that contains the names of managed hosts. The file must bewhitespace delimited. The task that is specified with xdistc is run on themanaged hosts that are specified in the file.

--when spec

Specifies the state of the managed hosts. The possible values for spec are'now', 'up', or 'now,up', without the single quotes. If you specify 'now', thetask that you specify with xdistc is run on the managed hosts that are alreadystarted. If you specify 'up', the task that you specify with xdistc is run onthe managed hosts that are being started or restarted, or the managed hosts

Command file referencexdistc

462

that are being added to the centrally managed domain. The default value ofspec is 'now,up'.

--id requestid

Specifies the request ID. You can use the --id option with the --push or --runoptions to assign a request ID. It also collects the output when it is used withthe --results option. If not specified, an ID is generated internally.

--ttl timespec

Specifies the time that xdistc should remember the request and the outputresults of the request. You can specify the time for which xdistc shouldattempt to send the request to the managed hosts. The value of timespec canbe in days, hours, or minutes. For example, you can use any one of thefollowing values to specify that xdistc should remember the request and theoutput results for a day: 1d, 24h, or 1440m, where d stands for days, h standsfor hours, and m stands for minutes. You can also specify one of the followingvalues for timespec: 'complete', or 'forever', without the single quotes. If youspecify timespec as 'complete', xdistc deletes the request after it has run thetask on the specified hosts. If you specify 'forever', the request is not deletedautomatically.

--wait seconds

Used with the --results option to specify the time the xdistc script shouldwait to obtain the results. You must specify the time in seconds. The defaultvalue is 0 seconds, which causes the xdistc script to wait indefinitely for theresults.

--force

Specifies that existing files should be overwritten when files are copied tothe managed host.

--delete

Specifies that the copied file should be deleted from the managed host afterthe command that is specified with the --run option has completed. The--delete option is used only when the --push option and the --run optionare used together.

--permission p

Specifies the access permissions for the file that is copied to the managedhost. You can specify the access permission as an octal number. For example,500, or 444.

--whitename name

Specifies that after a file is copied, it should be included in the whitelist to berun later.


--user username

Specifies the user name to be used when the task is run from xdistc on eachmanaged host. The default is user name is vxss:///sfm_admin//.

--uri uri

Specifies a raw URI to call. This is a lower-level interface above the --push

and the --run options that is used to invoke arbitrary URLs.

--d option=value

Specifies the additional values that xdistc passes as form data to remoteURLs.

NOTESThe default location of xdistc is /opt/VRTSsfmh/bin/xdistc.

The default log file for xdistc is /var/opt/VRTSsfmh/logs/xdist.log.

Windows-based Management Server does not support the xdistc command.

EXAMPLESThis section provides usage examples for xdistc.

EXAMPLE 1:

To copy the script.sh file to all Linux managed hosts, run it, and display theresults. The file will be deleted from the managed host after it is run. The requestwill remain active on Management Server for a day. The command will be sent toany new hosts joining the domain during this time, and results can be collecteduntil the request is automatically cleaned up on Management Server.

xdistc --ttl 1d --os Linux --push script.sh /tmp/remote.sh --run

--delete --results

EXAMPLE 2:

To copy the /root/script.sh file to all managed hosts, set its access permissions,and whitelist it. The request will remain active on Management Server for a day.The command will be sent to any new hosts joining the domain during this time,and results can be collected until the request is automatically cleaned up onManagement Server.

xdistc --ttl 1d --push /root/script.sh /var/opt/VRTSsfmh/script99.sh

--permission 755 --whitename script99

EXAMPLE 3:


464

To run the whitelisted script99 command with arguments. The request willremain active on Management Server for a day. The command will be sent to anynew hosts joining the domain during this time, and results can be collected untilthe request is automatically cleaned up on Management Server.

xdistc --ttl 1d --run -- script99 arg1 arg2

EXAMPLE 4:

To run script99using the whitelist and the lower-level URI interface. The requestwill remain active on Management Server for a day. The command will be sent toany new hosts joining the domain during this time, and results can be collecteduntil the request is automatically cleaned up on Management Server.

xdistc --ttl 1d --uri admin/whitelist.pl/run --d

argv=["script99","arg1","arg2"]



466

Managing VeritasOperations Managerlogging


■ About log files

■ About log file locations

About log filesThe Storage Foundation products maintain several log files that operators canuse for troubleshooting. You can also configure logging levels that determinewhat kinds of events are logged.

See “About log file locations” on page 467.

About log file locationsThe following table lists the Veritas Operations Manager log files and their defaultlocations:

Note: For Veritas Operations Manager on Windows platform, all web applicationand Web server log files are at %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\logs\

For Veritas Operations Manager on UNIX platform, all web application and Webserver log files are at /var/opt/VRTSsfmcs/logs/

BAppendix

Table B-1 Default Veritas Operations Manager log locations

Default locationComponent

Solaris and Red Hat Linux:

■ /var/opt/VRTSsfmh/logs/error.log

■ /var/opt/VRTSsfmh/logs/access.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\error.log

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\access.log

Veritas OperationsManager service(xprtld) log


■ /var/opt/VRTSsfmcs/logs/WebDebugLog.txt.0

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\logs\WebDebugLog.txt.0

Web applications

(Veritas OperationsManager and the otherStorage FoundationWeb plug-ins)


■ /var/opt/VRTSsfmcs/logs/webserver.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\logs\webserver.log

Web Server


■ /var/opt/VRTSsfmh/logs/cs_config.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\cs_config.log

Management Server log


■ /var/opt/VRTSsfmh/logs/vxdeploy.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\vxdeploy.log

Deployment log

Managing Veritas Operations Manager loggingAbout log file locations

468

Table B-1 Default Veritas Operations Manager log locations (continued)

Default locationComponent


■ /var/opt/VRTSsfmh/logs/add_host.log

■ /var/opt/VRTSsfmh/logs/mhrun.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\add_host.log

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\logs\mhrun.log

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\logs

Add hosts log


■ /var/opt/VRTSsfmcs/logs

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\logs

Management Server log


■ /var/opt/VRTSsfmh/family/log/mh.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmh\family\log\mh.log

Agentlet driver (byfamily)


■ /var/VRTSsfmcs/SFMdb3.log

Windows:

■ %ALLUSERSPROFILE%\ApplicationData\Symantec\VRTSsfmcs\db\SFMdb3.log

Database log

See “About log files” on page 467.

469Managing Veritas Operations Manager loggingAbout log file locations

Managing Veritas Operations Manager loggingAbout log file locations

470

VOM pricing model


■ Veritas Operations Manager Advanced License Requirements

Veritas Operations Manager Advanced LicenseRequirements

This topic provides you detailed information on the Veritas Operations Manageradvanced licenses that your hosts require. The number of hosts requiring licensechanges if Veritas Operations Manager Management Server reports to VeritasOperations Manager Enterprise Server. Enterprise product license on VirtualizationServer is propagated to Virtual Machines, making the Virtual Machines free.

The number of hosts that require the Veritas Operations Manager Advancedlicense, is calculated based on following criteria:

Table C-1

Roll UpNo Roll UpHosts

Physical Hosts

$FreeStorage Foundation Basic/Standard

FreeFreeStorage FoundationEnterprise

$$Agentless

$$Only managed hosts

$$Hosts having other productslike CommandCentral

CAppendix

Table C-1 (continued)


Virtual servers

FreeFreeVMWARE ESX Server

FreeFreeHMC Server / LPAR

FreeFreeVIOS

KVM

FreeFreeHas Virtual Machines

Has no Virtual Machines buthas

$Free– Storage Foundation Basic/Standard

FreeFree– Storage FoundationEnterprise

$$– No Storage Foundation

LDOM


Zones


Virtual Machines

FreeFreeStorage FoundationEnterprise Virtual Machinewith Non Storage FoundationVserver

$FreeStorage Foundation Virtualmachine with Non StorageFoundation Vserver

VOM pricing modelVeritas Operations Manager Advanced License Requirements

472

Table C-1 (continued)


$$Non Storage FoundationVirtual machine with NonStorage Foundation Vserver

FreeFreeStorage FoundationEnterprise Virtual Machinewith Storage FoundationVserver

$FreeStorage Foundation Virtualmachine with StorageFoundation Vserver

$FreeNon Storage FoundationVirtual machine with StorageFoundation Vserver

FreeFr

Freeee

Storage FoundationEnterprise Virtual Machinewith Storage FoundationEnterprise Vserver

Free( Not Propagated)Free( Not Propagated)Storage Foundation Virtualmachine with StorageFoundation EnterpriseVserver

$FreeNon Storage FoundationVirtual machine with StorageFoundation EnterpriseVserver

Virtual Machine directlyadded as managed host

$FreeStorage Foundation Basic /Standard

FreeFreeStorage FoundationEnterprise

$$Agentless

$$Only managed host

473VOM pricing modelVeritas Operations Manager Advanced License Requirements

VOM pricing modelVeritas Operations Manager Advanced License Requirements

474

Aabout

communication between managed host andManagement Server 23

Active Directoryremoving 311

activity boardmessages 72

activity board messagedeleting 72

add-onsdisabling 88enabling 88upgrading 83

adding managed hostsgendeploy.pl 130

adding secondary Authentication Brokers 301using CLI 301

agentless discoveryabout 104hosts 115prerequisites 110supported features 106

agentless discovery of hostsabout 109overview 109–111requirements for UNIX hosts 112requirements for Windows hosts 114

alert rulesabout 49copying 65creating 50deleting 67disabling 67editing 59enabling 66modifying 59removing 67

alertsabout 48adding notes 68

alerts (continued)filtering 68monitoring 68viewing 68

analytics gathering on Management Server 32disable 33enable 33

analyzing faults 42Faults and Risks 42

archiving reports 407array management capabilities 109arrays

disabling DMP paths 418assigning price tier

automatically 328manually 326processor price tier 324server price tier 324

Authentication Brokersauthentication domains 299refreshing 304removing 305viewing 300

authentication domainsdisabling 313enabling 312viewing 300

Bbundling a customized signature

Distribution Manager Add-on 389business entity

changing permissions 279managing 238managing security privileges 239setting additional attributes 281setting extended attributes 281

Cchange permissions 279Composite business entity 274

Index

composite organization entitycreating 276

composite Virtual Business Servicecreating 272

compression 143adding directories 146removing directories 147scheduling 144starting or stopping on demand 148uncompressing on demand 149

configuringControl Host 157Control Host Add-on 157File system automatic growth 140Firefox 26Internet Explorer 26SMTP settings 33Web browsers 26Web server settings 37

configuring virtualization discovery 166Control Host 157

about 109discover VMware Virtualization

Infrastructure 157copying

alert rules 65creating

alert rules 50composite organization entity 276composite Virtual Business Service 272extended attributes 437organization entity 252policy templates 376Virtual Business Service 241

creating organization entity 252customized signature

copying to the managed hosts 388creating script 385registering on Management Server 388using Distribution Manager Add-on 389

Ddatabase

log file 467datastore 163deep array

discovery 115deep array discovery

ESX servers 159

default count factorUNIX virtual systems 341virtual machines 341Windows virtual systems 341

deletingalert rules 67policy template scan 394policy templates 381virtual business service 269

deleting activity board message 72deleting archived reports 410deleting Organization Entities 271deleting report schedule 406deleting schedules 415deleting virual busniess service 269deploying add-ons 77deploying hotfixes 78deployment requests

viewing 88disable performance metering

host 209VMware ESX server 208VMware vCenter server 207

disablingalert rules 67

disabling add-ons 88disabling authentication domains 313disabling report schedule 405disabling schedules 415discovering VMware Infrastructure 161disk performance graphs 214DMP maintenance case

Removing a record 433Resuming 431View results and output 432

DMP pathsdisabling on an array 418re-enabling 424, 427

Dynamic Multipathing 417

Eediting

alert rules 59organization entities 267Virtual Business Service 254

editing configurationvirtualization discovery 169

editing organization entities 267editing report schedule 404

Index476

editing Virtual Business Service 254emailing reports 408enable performance metering

host 208VMware ESX server 207

enablingalert rules 66

enabling add-ons 88enabling authentication domains 312enabling report schedule 405enabling schedules 414enclosure performance graphs 219ESX servers

datastore 163deep array discovery 159

evidence detailsfeature 357

exporting reports 411extended attributes

about using 435creating 437modifying 439modifying value 442removing 440setting values 441viewing 436

Ffaults

about 40fault and dependency view 41suppressing 44un-suppress 48viewing 41

featureevidence details 357

feature tracking 357fibre channel switch capabilities 109file compression 143

adding directories 146removing directories 147scheduling 144starting or stopping on demand 148uncompressing on demand 149

File system automatic growthconfiguring 140

file system performance graphs 216file systems

automatic growth 136

file systems (continued)monitoring threshold 137monitoring usage 136

fire drillmodifying schedule 98viewing schedules 97

GGuest LDoms 178

HHardware Management Console 182high availability objects

adding to business entity 279host discovery 104

See also agentless discovery of hostsabout 104supported features 106

host managementcurrent and previous versions 124

host performance graphs 213hosts

available patches 194view patches 194

Hyper-V virtualization discovery 185

Iinitiator performance graphs 215installation

log files 467installing

solution 81

LLDAP

configuring authentication 306removing 311

LDom discovery 178information 181limitations 182method 180prerequisites 180requirements 180

LDom Server 178LDoms

roles 178license deployment detailed reports

exceptions 344

477Index

license deployment detailed reports (continued)product details by host name 344product details by license key 344product evidence 344product overview 344

license deployment policycreating 335modifying 338removing 342

License Deployment SummaryHost deployment summary table 345License deployment summary table 345Summary by edition 345Summary by platform 345Summary by product 345Summary by release 345

license deployment viewsscoping 370

License-Host Mapping detailsdays remaining until expiration 366edition 366expiration date 366version 366

licensesabout 316accountable deployed license 349deployed licenses 316discovery interval 316

Licensing and PricingNProcessor tier 317OS tier 317processor tier 317server tier 317UNIX

Solaris, HP-UX, AIX 317log files

about 467database 467installation 467Veritas Operations Manager 467Veritas Operations Manager Web

Application 450Web application plug-ins 467Web Server 467

Logical Domains discovery 178LPAR

about discovering 182storage correlation prerequisites 185

MmakeBE script 286managed hosts

adding using gendeploy.pl 130deleting 135refresh agent families details 132refresh information 132removing 135verifying version using the console 28

Management Serveractive users 38alert log retention period 36configure SMTP settings 33delete managed hosts 135dissociate managed hosts 135download patch 194editing agentless hosts 133enable analytic gathering 34enable VOM Advanced features 35LDAP based authentication 306list of active users 32managing hosts 124remove managed hosts 135SMTP details 32task log retention period 36user session time-out 37web server log levels 37web server session time-out 37

managingDMP paths 417

managing business entities 238managing reports 398metered resources 200modifying

alert rules 59extended attributes 439extended attributes value 442fire drill schedule 98policy templates 380

modifying report schedule 404monitor

file system usage 136multi-pathing discovery

user privileges 164VMware environment 163

multipathing path performance graphs 217

Index478

OOpenSSH

installing on AIX 121installing on Linux 121installing on Solaris 122

Organization Entitiesdeleting 271viewing 284

Ppatch details

viewing 196patch information

update manually 197performance graphs

about 209disk 214enclosure 219file system 216host 213initiator 215multipathing path 217volume 211

performance meteringabout 200disable for host 209disable for VMware ESX server 208disable for VMware vCenter server 207enable for host 208enable for VMware ESX server 207

policyabout 374about creating templates 375about templates 374about violations 382adding signatures 392creating templates 376deleting template scan 394deleting templates 381exclude violations 382manual template scans 381modifying templates 380removing ignored violations 395removing template signatures 393running template scans 381scan tunables 394violation scans 382

predefined roles 222

prerequisitesagentless discovery 110

price tierupdating 331

price tier informationmanagement server

automatically 329proxy server

automatically 330primary Authentication Brokers 298product details by license key

edition 362number of hosts 362platform name 362product name 362serial number 362version 362

product evidence 357product inventory

expired licenses 350invalid licenses 350valid licenses 350

product license deployedhost 356

Product-Tier Mapping summaryverification needed 352

RRe-enabling

DMP paths 424, 427reclamation of thin storage 141–142refreshing Authentication Brokers 304refreshing configuration

virtualization discovery 172removing

Active Directory 311alert rules 67DMP maintenance record 433extended attributes 440ignored violations 395LDAP 311policy template signatures 393solution 85

removing Authentication Brokers 305removing configuration

virtualization discovery 173removing report schedule 406replication

alert 73

479Index

Replication alertabout 73

reportsabout 397archiving 407csv files 411deleting archived report 410disabling schedule 405editing schedule 404email 408enabling schedule 405exporting 411managing 398removing schedule 406running 399saving 407saving to file 411scheduling 401virtualization 187

ResumingDMP maintenance case 431

risksabout 40

roles 222rule

overview 58running reports 399

Ssaving reports 407schedules 413

deleting 415disabling 415enabling 414

scheduling file compression 144scheduling reports 401scope

license deployment views 370scripts

sfmw 450vomsc 451vxlist 453xdistc 461

secondary Authentication Brokers 298adding 301

security groupsaccessing business entities 279adding 230modifying 234

security groups (continued)removing 236

setting additional attributesbusiness entity 281

setting extended attributesbusiness entity 281

setting valuesextended attributes 441

sfmw 450signatures

about 383adding to policy template 392customizing 384setting tunables 392

SMWeblog file 450startup script 450

solaris zones 173Global Zones 173non-Global Zones 173

solaris zones discovery 173information 177limitations 178method 176prerequisites 174requirements 174utilities 176

solutionsabout 76deployment 76disable 88enable 88install 81remove 85uninstall 84upload 80view solution deployment summary 85

space estimationdata logs 203

SPVU 319IBM LPAR 323kernel-based virtual machines 322Solaris LDOM virtualization server 321VMware virtual machine 320

storage objectsadding to business entity 279

Symantec Performance Value Unit 319IBM LPAR 323kernel-based virtual machines 322

Index480

Symantec Performance Value Unit (continued)Solaris LDOM virtualization server 321VMware virtual machine 320

Ttasks

viewing 71thin storage reclamation 141–142

Uuninstall

solution 84UNIX

agentless discovery of hosts 110upgrading

add-ons 83upload

packages as a zip file 81solution 80

Vverifying

managed host version using the console 28Veritas Operations Manager

log files 467viewing

activities 72extended attributes 436fire drill schedules 97messages 72patch details in SORT Web site 196scan tunables 394solution deployment summary 85solutions in repository 79

viewing Authentication Brokers 300viewing authentication domains 300viewing Organization Entities 284viewing Virtual Business Services 282viewing virtual machines 190viewing virtualization servers 188Virtual Business Service

creating 241overview 240viewing 282

virtual machinesdefault count factor 341

virtualization discoveryconfiguring 166

virtualization discovery (continued)editing configuration 169refreshing configuration 172removing configuration 173

virtualization management view 165virtualization reports 187virtualization summary 188virtualization technology

kernel-based virtual machine 156LPAR 156Microsoft Hyper-V 156Solaris LDom 156Solaris zones 156VMware 156

VMware discovery 159datastore 163ESX servers 159information 162prerequisites 161requirements 161VirtualCenter servers 159

VMware Infrastructurediscovery 161VMware SDK 161

volume performance graphs 211vomadm

about 445Business entities management 445deployment 445host management 445service management 445

vomsc 451vxlist 453

WWeb application plug-ins

log files 467Web browsers

configuring 26Web Server

log file 467Web UI framework

starting and stopping 30Windows

agentless discovery of hosts 111

Xxdistc 461

481Index

ZZone Agentlet 173

Index482

Veritas™ Operations Manager Management Server 5.0 ... · Connecting to Veritas Operations Manager Management Server ..... 27 Verifying the version of a managed host in the console

Documents