Veritas™ Cluster Server Management Console Implementation...
511
Veritas™ Cluster Server Management Console Implementation Guide AIX, ESX, HP-UX, Linux, Solaris, Windows 5.5
Transcript of Veritas™ Cluster Server Management Console Implementation...
Veritas™ Cluster ServerManagement ConsoleImplementation Guide
AIX, ESX, HP-UX, Linux, Solaris,Windows
5.5
Veritas™ Cluster Server Management ConsoleImplementation 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.5
Documentation version 5.5.0
Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and Veritas are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks 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 Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014
http://www.symantec.com
Printed in the United States of America.
10 9 8 7 6 5 4 3 2 1
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 maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the rightamount of service for any size organization
■ Telephone and Web-based support that provides rapid response andup-to-the-minute information
■ Upgrade assurance that delivers automatic software upgrade protection
■ Global support that is available 24 hours a day, 7 days a week
■ Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Website at the following URL:
www.symantec.com/techsupp/
Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:
www.symantec.com/techsupp/
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:
www.symantec.com/techsupp/
Customer serviceCustomer service information is available at the following URL:
www.symantec.com/techsupp/
Customer Service is available to assist with the following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and maintenance contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs or manuals
Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:
[email protected] and Japan
[email protected], Middle-East, and Africa
[email protected] America and Latin America
Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.
Symantec Early Warning Solutions
These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.
Managed Security Services
Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.
Consulting Services
Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.
Educational Services
To access more information about Enterprise services, please visit our Web siteat the following URL:
www.symantec.com
Select your country or language from the site index.
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 1 Introducing the VCS Management Console . . . . . . . . . . . . . . . . . . . 19
About VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Components of the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About the management server database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About Symantec Product Authentication Service ... . . . . . . . . . . . . . . . . . . . . . . 20
About objects in the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About object states and consolidated states ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About sites and the enterprise ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22About sites and cluster types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23How the VCS Management Console connects to VCS clusters ... . . . . . . . . . . . . 24How the VCS Management Console works ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24What you can do with the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . 25Where to get more information about VCS Management
Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26What's new and changed in this version .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2 About users and user privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29About user privileges ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Privilege persistence .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Privilege precedence .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Privilege-restricted navigation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
About user privileges on the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32About user privileges on clusters and service groups .... . . . . . . . . . . . . . . . . . . . . . . 32About user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Supported user domain types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Internal user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
User account representations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34How the management server authenticates user accounts ... . . . . . . . . . . . . . . . . 34
Contents
Chapter 3 Preparing to install the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Typical setup diagrams .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installation workflow .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Supported software for the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . 40
Supported operating systems for the management server ... . . . . . . . . . . . 41Supported VCS versions for clustering the management
server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Supported VCS versions for managed clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . 41Supported browsers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Required plugins ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Recommended management server hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . 42
About the security infrastructure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Installing the root broker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Installing and configuring the root broker on Solaris ... . . . . . . . . . . . . . . . . . 44Installing and configuring the root broker on Windows .... . . . . . . . . . . . . . 45Installing and configuring the root broker on Linux .... . . . . . . . . . . . . . . . . . . 46
Installing the authentication broker on the management server ... . . . . . . . . 48Provisioning the authentication broker account on Solaris ... . . . . . . . . . 49Installing and configuring the authentication broker on
Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Provisioning the authentication broker account on
Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Installing and configuring the authentication broker on
Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Provisioning the authentication broker account on Linux .... . . . . . . . . . . 55Installing and configuring the authentication broker on
Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 4 Installing, upgrading, and uninstalling themanagement server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Before you install the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59About installing the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing the management server on Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Installing a standalone management server on Solaris ... . . . . . . . . . . . . . . . 61Installing a highly-available management server on Solaris ... . . . . . . . . 63
Installing the management server on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Installing a standalone management server on Windows .... . . . . . . . . . . . 65Installing a highly-available management server on
Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Installing the management server on Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Installing a standalone management server on Linux .... . . . . . . . . . . . . . . . . 69Installing a highly-available management server on Linux .... . . . . . . . . . 71
Contents8
Upgrading to VCS Management Console 5.5 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Upgrading a standalone management server on Solaris ... . . . . . . . . . . . . . 73Upgrading a highly-available management server on
Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Upgrading a standalone management server on Windows .... . . . . . . . . . 79Upgrading a highly-available management server on
Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Post-upgrade procedure for peer management servers ... . . . . . . . . . . . . . . . 82
Installing the Japanese language pack for the console ... . . . . . . . . . . . . . . . . . . . . . . 82Installing the Japanese language pack for the console on Windows
systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Installing the Japanese language pack for the console on Solaris
systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Configuring the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Configuring a newly-installed standalone management serveron Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring a newly-installed highly-available managementserver on Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configuring an upgraded standalone management server onSolaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Configuring an upgraded highly-available management serveron Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuring a newly-installed standalone management serveron Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configuring a newly-installed highly-available managementserver on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Configuring an upgraded standalone management server onWindows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring an upgraded highly-available management serveron Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring a newly-installed standalone management serveron Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configuring a newly-installed highly-available managementserver on Linux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configuring a peer management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Uninstalling the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Uninstalling a standalone management server on Solaris ... . . . . . . . . . 107Uninstalling a highly-available management server on
Solaris ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Uninstalling a standalone management server on Windows .... . . . . . 111Uninstalling a highly-available management server on
Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Uninstalling a standalone management server on Linux .... . . . . . . . . . . 113
9Contents
Uninstalling a highly-available management server onLinux .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Uninstalling the authentication broker ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Uninstalling the authentication broker from a Solaris
system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Uninstalling the authentication broker from a Windows
system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Uninstalling the authentication broker from a Linux
system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 5 Configuring sites and clusters for centralizedmanagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
About the initial user's role in centralized management configuration.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configuring sites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Discovering and configuring one or more clusters for
management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Reconfiguring clusters that use the cluster connector ... . . . . . . . . . . . . . . . . . . . . 128Enabling and disabling cluster monitoring .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Removing a cluster from console management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Chapter 6 Getting started with the VCS ManagementConsole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
DNS prerequisite for using the console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Connecting to the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Logging on to the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Logging out of the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138About task availability in the VCS Management Console ... . . . . . . . . . . . . . . . . . 138About the startup page .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138About site summary pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140About the main tab bar ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142About the left pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143About the Manage tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143About the Reports tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147About the Event Filter panel ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148About the details pane .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149About the details tab bar and detail links ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150About quick navigation links ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151About the navigation bar on the Manage tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151About the navigation bar on tabs other than Manage .... . . . . . . . . . . . . . . . . . . . . 152About the menu bar ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Setting data filters on detail pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Contents10
Sorting detail page tables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Viewing multiple pages of a table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156About icon conventions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Controlling page updates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Determining the currently-connected management server ... . . . . . . . . . . . . . . 158Setting the time zone .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Setting user preferences ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158About the title bar links ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Chapter 7 Administering users and user privileges . . . . . . . . . . . . . . . . . . . . . . 161
Viewing user status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161About user listing tables ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Administering users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Adding users to the management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Modifying management server privileges for selected users ... . . . . . . 165Granting and revoking reporting privileges ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Deleting selected users from the management server ... . . . . . . . . . . . . . . . 167Adding selected users to selected clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Adding selected OS users to one cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Adding selected users to groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Chapter 8 Administering basic high availability clusterconfigurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Administering tags ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Editing the Regions tag for clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Editing the sites tag for clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Editing the Departments tag for service groups .... . . . . . . . . . . . . . . . . . . . . . . 175Editing the Line of Business tag for service groups .... . . . . . . . . . . . . . . . . . 175
Administering sites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Creating sites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Changing sites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Deleting sites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Administering clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Administering multiple clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Administering an individual cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Administering service groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Administering multiple service groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Administering an individual service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Administering systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Administering multiple systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Administering an individual system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Administering resources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
11Contents
Administering multiple resources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Administering an individual resource ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Administering resource types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271About the Resource Types Listing table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271About the Resource Type Details table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Editing attributes of a resource type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Viewing resource type status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Viewing logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274About the logging mechanism .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Viewing logs for cluster objects ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Searching .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Chapter 9 Administering VCS global clusterconfigurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
About VCS global clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279VCS global cluster task terminology .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280About creating global service groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281About the Status tab for global clusters and service groups .... . . . . . . . . . . . . 281Administering global clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Adding a remote cluster to a local cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Administering global service groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Converting local service groups to global service groups .... . . . . . . . . . . 286Bringing a remote service group online .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Taking a remote service group offline ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Switching a remote service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Converting global service groups to local service groups .... . . . . . . . . . . 292
Deleting a remote cluster from a local cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Taking the wac resource offline ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Removing the cluster from group and heartbeat cluster
lists ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Removing the remote cluster from the local cluster ... . . . . . . . . . . . . . . . . . 295
Administering global heartbeats ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Adding a global heartbeat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Deleting a global heartbeat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Migrating a site (local site disaster recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299When to use site migration for DR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Migrating the site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Recovering a failed site (remote site disaster recovery) ... . . . . . . . . . . . . . . . . . . . 301When to use failed site recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Recovering the site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Contents12
Chapter 10 Administering stretch cluster configurations . . . . . . . . . . . . . . 305
About stretch cluster administration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Configuring a stretch cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Unconfiguring a stretch cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Configuring a stretch service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Chapter 11 Monitoring readiness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
About HA and DR readiness ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309About fire drills ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
About HA fire drills ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Configuring an HA fire drill .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315About DR fire drills ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Configuring a DR fire drill .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Viewing readiness ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318About viewing HA readiness ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318About viewing HA and DR readiness ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Updating readiness ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339About running HA fire drills ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Running an HA fire drill on selected service groups in the
enterprise ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Scheduling an HA fire drill .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Disabling automatic HA fire drill checks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Enabling automatic HA fire drill checks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342About running DR fire drills ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Running a DR fire drill .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344Halting a DR fire drill .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Clearing the fault on a DR fire drill group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Chapter 12 Administering reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
About reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Administering report jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Viewing a list of report jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Specifying new report job options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350Creating the job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Viewing a report job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Modifying a report job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Deleting report jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Running a report job to generate a report output ... . . . . . . . . . . . . . . . . . . . . 357Enabling and disabling report jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Cloning report jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Filtering the report jobs table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
13Contents
Granting and revoking reporting privileges ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Administering report outputs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Viewing outputs of a report job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Exporting a report output ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Emailing exported report outputs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364Viewing exported outputs for a report job run .... . . . . . . . . . . . . . . . . . . . . . . . . 364Filtering the Report Runs table ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Deleting selected report outputs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
About report types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366About tracking VCS agents across the enterprise with reports
... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367About managing cluster configurations with reports ... . . . . . . . . . . . . . . . . 367About analyzing failures for patterns, problems, and trends with
reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370About managing uptime of service groups with reports ... . . . . . . . . . . . . 371About tracking cluster activity with reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 373About tracking HA and DR performance and DR heartbeats ... . . . . . . 373
Chapter 13 Administering notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
About events, policies, and notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375About configuring SNMP consoles to receive traps ... . . . . . . . . . . . . . . . . . . . . . . . . 379Configuring notification settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Configuring SMTP notification .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Testing the SMTP settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380Configuring SNMP notification .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Viewing a list of policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Viewing policy details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Creating a policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Editing a policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Deleting a policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Disabling a policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Enabling a policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386Exporting policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386Importing policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Viewing alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387About the alert popup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Chapter 14 Searching the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
About the search feature ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Conducting a search .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Contents14
Chapter 15 Administering the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Viewing information about the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Pruning the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Backing up the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396Restoring the database from a backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Prerequisite tasks for using the gadbrestore command .... . . . . . . . . . . . . 397Arguments for the gadbrestore command .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399Restoring the database using the gadbrestore command .... . . . . . . . . . . 400
Modifying guest access to the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Chapter 16 Administering maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Creating and deleting maintenance windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403Assigning and unassigning maintenance windows .... . . . . . . . . . . . . . . . . . . . . . . . 406
Appendix A Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Navigating the VCS Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409Accessibility features in GUI controls ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Appendix B Object states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
About object states ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Appendix C Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Introduction to the command-line interface (CLI) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 415CLI usage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Notations for object names in the CLI ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417Use of qualified and unqualified names .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Output options summary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Version output option .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
CLI commands .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Appendix D Creating custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Accessing the database information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457Registering the ODBC driver ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457Creating the ODBC data source ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
About database schema object descriptions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459About published database schema objects ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
K2VW_ENTERPRISE .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460K2VW_MServers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461K2VW_Clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
15Contents
K2VW_Groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465K2VW_Nodes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467K2VW_ResourceTypes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469K2VW_Resources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470K2VW_Schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472K2VW_Logs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Example statements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475Example 1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475Example 2 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475Example 3 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Appendix E Symantec Product Authentication Service rootbroker tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
About the Symantec Product Authentication Service ... . . . . . . . . . . . . . . . . . . . . . 477Authentication service overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477Root and Authentication brokers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Setting up an authentication broker on the management server ... . . . . . . . 478Setting up trust between two authentication brokers ... . . . . . . . . . . . . . . . . . . . . . 479
Appendix F CMCServerConfig agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
About the CMCServerConfig agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Sample configuration for the CMCServerConfig agent ... . . . . . . . . . . . . . . . . . . . . 482Resource dependency diagram .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Appendix G Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Installation issues and recommendations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Avoid concurrent installations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485VCS 4.3 upgrade .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Installation user account privileges issue for Windows .... . . . . . . . . . . . . 486Exception message during management server upgrade .... . . . . . . . . . . 486Specifying host names with installcmc causes failure ... . . . . . . . . . . . . . . . 486Symantec Product Authentication Service post-upgrade
versions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486Configuration issues and recommendations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Cluster configuration state after cluster user addition .... . . . . . . . . . . . . . 487DNS configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487Configuring a clustered management server on Firefox 2.0 ... . . . . . . . 487
Operational issues and recommendations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488VCS Management Console controls not immediately active ... . . . . . . . 488Cluster status is offline during snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488Very large clusters may not load into the console ... . . . . . . . . . . . . . . . . . . . . 488
Contents16
Reports stop running on very large configurations .... . . . . . . . . . . . . . . . . . 489Discovering clusters allows one authentication domain .... . . . . . . . . . . . 490
User issues and recommendations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490NIS user group authentication issue .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490OS user password requirement ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491OS group reporting privileges issue .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491VCSMC administrator user limitation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Console display issues and recommendations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Navigation tree context menu issue .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Attributes added in VCS CLI may not display as expected .... . . . . . . . . . 491Table blank but filter panels report service groups .... . . . . . . . . . . . . . . . . . 492Random characters displayed on https login .... . . . . . . . . . . . . . . . . . . . . . . . . . . 492VCS version numbers indicate engine version .... . . . . . . . . . . . . . . . . . . . . . . . . 492Very large dependency trees may not display quickly ... . . . . . . . . . . . . . . . 492
Resolving localization issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492Viewing VCS 5.0 logs in Japanese .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Installing the Japanese language pack on Windows has no
effect ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Maintaining reliable access to the database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Localizing the web server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Log file locations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Appendix H Administering Symantec Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
About Symantec Web Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495Configuring ports for VRTSweb .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
About VRTSweb ports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496Retrieving the list of VRTSweb ports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496Adding ports for VRTSweb .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496Deleting ports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497Changing the administrative port ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Managing VRTSweb SSL certificates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498Viewing SSL certificate information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498Creating a self-signed SSL certificate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498Exporting the SSL certificate to a file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Configuring a CA-signed SSL certificate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Cloning the VRTSweb SSL certificate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Configuring SMTP notification for VRTSweb .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502Retrieving the name of the configured SMTP server ... . . . . . . . . . . . . . . . . 502Setting the SMTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503Retrieving SMTP settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503Adding an SMTP recipient ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504Deleting an SMTP recipient ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
17Contents
Modifying the maximum heap size for VRTSweb .... . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Contents18
Introducing the VCSManagement Console
This chapter includes the following topics:
■ About VCS Management Console
■ Components of the VCS Management Console
■ About objects in the VCS Management Console
■ About object states and consolidated states
■ About sites and the enterprise
■ About sites and cluster types
■ How the VCS Management Console connects to VCS clusters
■ How the VCS Management Console works
■ What you can do with the VCS Management Console
■ Where to get more information about VCS Management Console
■ What's new and changed in this version
About VCS Management ConsoleVeritas Cluster Server Management Console is a centralized management solutionfor high availability application clusters based on VCS. The VCS ManagementConsole enables centralized administration, management, and analysis of allclusters in the enterprise from a single console. The console interface is aweb-served application and is available through the corporate intranet. Anynetworked system that runs a supported Web browser can run the console.
1Chapter
Components of the VCS Management ConsoleThe VCS Management Console consists of several software components. Theconsole also depends on the external software components that enable it tofunction in a cluster environment.
About the management serverThe management server is the software engine that performs centralizedmulti-cluster management and monitoring tasks. It communicates with the HighAvailability Daemon (HAD) or the VCS engine. The management server functionsas the main server process. It also serves as a web server to serve web pages forthe VCS Management Console graphical user interface. You can cluster themanagement server or install it on a standalone system.
The management server also supports a command-line interface or CLI. The CLIis a textual interface that you can use to issue the commands that perform clustermanagement tasks.
One management server is capable of administering many clusters. Managementservers can also function as peers. A management server at one location cancommunicate with a peer management server at another location. Thiscommunication enables you to view and manage all clusters at both locations.Currently, you can configure two management servers as peers. However, eachmanagement server can manage clusters across multiple geographic sites.
About the management server databaseThe management server stores configurational and historical cluster data in anembedded Sybase ASA database. Every management server requires one database.The database stores all information that the console displays in its web pages andin its reports.
The database includes maintenance features such as backup, restore, and prune.Read-only access is available to external clients through ODBC and JDBC.
About Symantec Product Authentication ServiceSymantec Product Authentication Service securely authenticates user accountsand secures communication between cluster nodes and client software, includingthe VCS Management Console. The Symantec Product Authentication Serviceuses digital certificates for user account authentication and SSL to encryptcommunication over the public network.
Introducing the VCS Management ConsoleComponents of the VCS Management Console
20
The user accounts are local operating system and domain user accounts. The VCSManagement Console does not require native or proprietary user accounts.
The following are the main components of the Symantec Product AuthenticationService:
A root broker serves as the main user account registrationand certification authority. The root broker maintains a uniqueidentification data sequence that is called a root hash. Whenyou create an authentication broker, the root broker uses theroot hash to create an authenticated (signed) certificate forthat authentication broker. The root broker performs onlythis function in the authentication process.
The authentication broker subsequently propagates thecertificate to its registered users. If you create twoauthentication brokers under the same root, a user that isregistered in one can still log on through the other. The otherauthentication broker recognizes the certificate from thecommon root broker and permits the logon.
Root broker
Authentication brokers serve as intermediate user accountregistration and certification authorities. An authenticationbroker is installed on every management server and everycluster node in a secure-mode cluster. Every logon to amanagement server or to a secure-mode cluster verifies theuser account against an authentication broker.
Authentication brokers
Note: Symantec recommends that you configure only one root broker in theenterprise. You can configure multiple authentication brokers to use one rootbroker. Each operating system in the enterprise requires at least one authenticationbroker. Configuring all authentication brokers to use one root enablesauthentication across all operating systems. If you have no root broker, you canconfigure the console management server as a root broker and an authenticationbroker.
About objects in the VCS Management ConsoleObjects represent the various hardware, software, and human elements that makeup and interact with your managed enterprise. The VCS ManagementConsolegroups the objects that you administer into two types: management serverobjects and cluster objects.
Management server objects are not directly part of a cluster but they supportcluster operation and administration. Management server objects include users,
21Introducing the VCS Management ConsoleAbout objects in the VCS Management Console
management servers, notification policies, reports, report jobs, and tags. Aparticularly important tag is the site tag, which is used to assign clusters togeographical sites.
Cluster objects are part of a cluster and participate directly in making yourapplications highly available. Cluster objects include clusters, service groups,resources, resource types, and systems.
About object states and consolidated statesObjects such as service groups and resources can be in more than one state at atime (one for each system on which they are configured). Other objects, such asclusters, systems, and management servers, can be in only one state at a time.Still other objects, such as resource types, schedules, and users, are stateless.
The VCS Management Console maps the many possible object states onto a groupof cumulative, effective states called consolidated states.
See “About object states” on page 411.
About sites and the enterpriseThe VCS Management Console employs the following concepts to make organizingcluster objects and navigating among them easier.
The enterprise represents all clusters in your entire company ororganization that are configured for centralized management
The enterprise
Sites represent logical groupings of clusters in the enterprise. Sitestypically represent geographical sites.
Sites
The console displays sites and the enterprise as an expandable, navigable tree ofbranch lines and icons. The enterprise is the root of the tree, which can branchinto many sites. Each site branch contains more branches that represent hardwareand software objects such as clusters, service groups, and systems.
Note: Sites are abstract, logical groupings of clusters. An attribute called the sitetag determines these groupings. You can define and apply the Site tag at yourdiscretion.
Introducing the VCS Management ConsoleAbout object states and consolidated states
22
About sites and cluster typesThe many cluster configurations that you can create using VCS usually correspondto one of the following types:
The application nodes in a single cluster at a single siteshare access to a storage device, typically over a SAN.If a node or application fails, the shared storage providesall data that is required to start the application onanother node.
High availability (HA) cluster
A single cluster spans two sites. Instead of a singlestorage array, data is mirrored between arrays at eachsite. Replication technologies such as Veritas VolumeManageer (VVM) or EMC SRDF are used to mirror thedata.
This configuration provides synchronized copies of dataat both sites. If a node or application fails, the sharedstorage provides all data that is required to start onanother node at the other site.
A type of stretch cluster that is called a replicated datacluster (RDC) uses separate storage at both sites withdata replication configured between them.
Stretch cluster (campus cluster,metropolitan cluster, metrocluster)
A global cluster links two clusters at two sites. Thisconfiguration enables wide-area failover and disasterrecovery. Local clustering still provides local failoverfor each site. If failover within the local cluster is notpossible, the global service group or groups start up atthe distant remote site. As usual, the cluster nodes ateach site share storage. Data replication is usuallyconfigured between the sites.
VCS global cluster
The following are the site-based differences between a stretch cluster and a VCSglobal cluster:
■ A stretch cluster is a single cluster. Its private network connections forheartbeat and cluster communications physically span the distance betweensites. The sites in a stretch cluster usually share storage.
■ A VCS global cluster is one-half of a global cluster relationship. A global clusterrelationship consists of two identically configured clusters at two separatesites. The two sites are connected only by the corporate network. The two sitesare far enough apart so that a local disaster at one site is unlikely to affect thecorresponding remote site. The sites in a global cluster relationship maintainseparate local storage. Data replication is usually configured between the sites.
23Introducing the VCS Management ConsoleAbout sites and cluster types
A stretch cluster is unique in that it is a single cluster that is associated with twosites. The VCS Management Console enables you to specify which systems are atwhich sites during cluster identification, verification, and configuration. Afterconfiguration, the console creates a hybrid site and places it in the navigationtree. Hybrid sites are of the following form:
Site1:Site2
See “About sites and the enterprise” on page 22.
The navigation tree displays the stretch cluster within the hybrid site branch.
Note: The console also supports three-sided, or STAR, hybrid sites.
How the VCS Management Console connects to VCSclusters
In this release of the VCS Management Console, the management server connectsdirectly to VCS clusters. The connection is made directly through the VCS socketinterface. The management server initiates a connection to the High AvailabilityDaemon (HAD) on any one node of a cluster at port 14141. This cluster port mustbe visible to the management server across firewalls. Direct connection requiresno additional software to be installed on the cluster nodes
Earlier versions of the console optionally allowed clusters to initiate connectionsto the management server using the cluster connector agent. If you have usedprevious versions of the console, you may have clusters in your managed enterprisethat use the cluster connector. If so, you must remove the cluster connector andreconfigure each cluster to use a direct connection.
See “Upgrading to VCS Management Console 5.5” on page 73.
See “Reconfiguring clusters that use the cluster connector” on page 128.
How the VCS Management Console worksThe VCS Management Console works by using management servers, clusterconnections, authentication brokers, and VCS clusters to implement centralizedcluster management technology. Centralized cluster management is theadministration of large, distributed, heterogeneous clustered platforms from asingle console.
Figure 1-1 shows a large VCS Management Console deployment in which two peermanagement servers manage clusters on different continents.
Introducing the VCS Management ConsoleHow the VCS Management Console connects to VCS clusters
24
Figure 1-1 Centralized cluster management
The notebook computer represents a web connection to the VCS ManagementConsole through a supported web browser.
What you can do with the VCS Management ConsoleThe VCS Management Console provides many features for managing multipleclusters.
The VCS Management Console provides certain features that enable you to managethe following:
■ High application availability
■ Business continuity
■ Cluster configuration
■ User configuration
■ Maintenance downtime
■ Event logging
■ Event notification
■ Robust reporting
25Introducing the VCS Management ConsoleWhat you can do with the VCS Management Console
Where to get more information about VCSManagement Console
If you are new to high availability cluster management, Symantec recommendsthat you read and learn the concepts and terminology in your existing VeritasCluster Server documentation. Refer to your VCS User's Guide for this information.
The VCS Management Console context-sensitive help system is also available onthe Help menu . The Help menu always displays at the top of the console screen.Use this system while you use the console to quickly orient yourself in the interfaceand to learn about available tasks.
What's new and changed in this versionThe following are new features in this version of the Veritas Cluster ServerManagement Console:
■ A streamlined installation and configuration.
■ An enhanced usability throughout the interface.
■ Support for new releases of VCS since 5.0MP1 (UNIX) and 5.1 (Windows).
■ Enhanced support for stretch (campus or metropolitan) clusters.
■ Floating menus—the console menus now scroll with your view on long pages.
■ Connected management server information is part of console window.
■ Peer management servers information is available on the Administration tab.
■ The References page—a page with links to a variety of service and supportresources.
■ Monitoring and proactive management of high availability (HA) and disasterrecovery (DR) readiness.
■ Enhanced visualization for HA and DR configurations, objects, and datareplication.
■ Link to the VIAS website for new functionality that customers can downloadand use.
■ Management server availability for Linux.
■ Enhanced and scalable reporting offers improved clarity and formatting; PDF,Excel, PPT, DOC, and HTML export formats are now available.
■ Email enablement for report outputs.
■ Enhanced, visually integrated search functionality in the navigation tree.
Introducing the VCS Management ConsoleWhere to get more information about VCS Management Console
26
■ Service group and resource dependency diagrams can be opened in separatewindows for reference.
■ Mouse over (roll over) support is available for status icons in tables, whichenables you to view status details about objects or fire drills.
■ Full operating system group support—privileges can now be given to operatingsystem (OS) groups. VCS OS groups are also completely honored.
■ The Convert CC to DC wizard is also available to reconfigure VCS clusters touse a direct connection.
■ The Feedback link on the title bar, which enables you to submit feedbackdirectly to the VCS Management Console product team.
27Introducing the VCS Management ConsoleWhat's new and changed in this version
Introducing the VCS Management ConsoleWhat's new and changed in this version
28
About users and userprivileges
This chapter includes the following topics:
■ About users
■ About user privileges
■ About user privileges on the management server
■ About user privileges on clusters and service groups
■ About user accounts
■ User account representations
■ How the management server authenticates user accounts
About usersThe VCS Management Console enables its users to perform comprehensive clusteradministration and management tasks throughout the entire enterprise. All usersin the VCS Management Console are operating system users; you do not need toset up separate, proprietary user accounts for the console. You do, however, needto add existing operating system users to the management server database. TheSymantec Product Authentication Service authenticates the users that you addwhen they log in. You can add or delete users at any time.
About user privilegesIt may be desirable or necessary to maintain a division of capability andresponsibility among many users. You can maintain such divisions by assigning
2Chapter
different types of privileges to each user. In the VCS Management Console, aprivilege is the authorization or permission to perform an administrative or amanagement task. For example, permission to modify the value of a clusterattribute is a privilege.
A user’s privileges determine the tasks and data that are available to that user.Therefore, you assign privileges to users based upon the tasks that you want theuser to perform.
The VCS Management Console enables you to specify user privileges for the tasksthat pertain to the following:
■ users
■ the management server
■ the management server database
■ the notifier
■ sites
■ clusters
■ service groups
■ resources
■ resource types
■ reports
The console enables you to assign privileges in sets. Otherwise, it would beuntenable to add permissions for each available task to each user. The privilegeset names indicate a user's level of authority. The following table shows theavailable privilege sets.
Administrator privileges allow a user to perform the maximum numberof tasks on a managed object. Administrator privileges allow users tochange object configurations.
A user can have administrator privileges on the management server,on clusters, and on service groups.
Administratorprivileges
Operator privileges allow a user to perform a limited number of taskson a managed object. It includes some tasks that come underadministrator privileges. However, operator privileges do not allowusers to change object configurations.
A user can have operator privileges on clusters and service groups.
Operatorprivileges
About users and user privilegesAbout user privileges
30
Guest privileges allow a user only to view object data. Guest privilegesdo not allow the user to perform tasks or to change objectconfigurations.
A user can have guest privileges on the management server.
Guest privileges
Reporting privileges allow a user to manage reports. A user withreporting privileges can create, run, enable, disable, clone, delete, andschedule report jobs and export report outputs to various formats.
A user can have reporting privileges on the management server.
Reportingprivileges
Users can have combinational privileges. For example, a user can haveadministrator privileges on the management server but only operator privilegeson a particular cluster.
Privilege persistenceUser privileges are persistent; a privilege remains assigned to a user even if thatuser operates in other capacities using different privileges. For example, if acluster administrator is also assigned administrator privileges on a managementserver, that user retains administrator privileges on the cluster.
Privilege precedenceWhen a user is assigned more than one privilege on the same object, the privilegewith the higher authority takes precedence. For example, suppose that a userbegins using the console as a service group operator. If that user is later made anadministrator of the service group's parent cluster, that user also gainsadministrator privilege on the service group. However, both explicit privilegeassignments still appear in the Users table on the Administration tab.
Privilege-restricted navigationUser privileges determine the objects and tasks available to a user. Some usersmay not be able to access certain information because of their privileges. If auser’s privileges do not apply to certain objects and tasks, that user cannot viewthose objects nor perform those tasks. Based on privileges, the VCS ManagementConsole restricts some users by not displaying various information or by disablingvarious task and navigation links. For example, a user with only guest privilegeson the management server cannot view the Administration tab.
31About users and user privilegesAbout user privileges
Note: Some tasks may also be unavailable due to system state. For example, thefreeze operation for an offline system is unavailable to all users regardless oftheir privileges.
About user privileges on the management serverSome privileges allow users to perform general administration of the managementserver and its users. These privileges do not affect a user's ability to manageclusters or related cluster objects such as service groups and resources. Users canhave either the administrator or the guest privileges on the management server.A management server administrator is also called a VCSMC administrator.Information about users' privileges on the management server is maintained inthe management server database.
The VCS Management Console reserves the following privileges for a managementserver administrator:
■ Configure the local management server
■ Add clusters to, and remove clusters from, the managed enterprise
■ Create and delete other users
■ Assign and modify users' privileges (including the administrator's own)
■ Manage tags (sites, regions, departments, lines of business)
■ Schedule and run reports
■ Configure the notifier
■ Administer the management server database
■ Manage maintenance windows (scheduled downtime)
About user privileges on clusters and service groupsSome privileges allow users to perform management tasks on clusters, servicegroups, resources, and resource types. These privileges do not affect a user'sability to perform general administration of the management server or its users.Users can have either administrator, operator, or guest privileges on clusters orservice groups.
When a mangement server creates a user, it receives guest privileges (read-onlyprivileges) on all clusters, service groups, resources, and resource types.
About users and user privilegesAbout user privileges on the management server
32
Note: Clusters, service groups, resources, resource types, and their associatedattributes and other properties are referred to collectively as cluster objects.
Information about user privileges on cluster objects is not maintained in themanagement server database. This information is kept on the cluster, whetherthe cluster user was created in the VCS Management Console or in VCS.
The following are true for users with privileges on the VCS clusters that areconfigured in secure mode. This refers to clusters that are configured to useSymantec Product Authentication Service:
■ These users must be explicitly added as users in the VCS Management Consoleso that they can log on to the console.
■ On the console, these users retain their original privileges on their originalclusters.
■ The management server authenticates these users against a Symantec ProductAuthentication Service authentication broker.
You cannot log on to the console management server with VCS user names fromany VCS clusters that are not configured in secure mode.
About user accountsUsers log on to the VCS Management Console and the CLI using existing operatingsystem user accounts. The operating system user accounts must be valid on thesystem where the management server is installed.
If you install the management server on a system that is a member of an NT,Active Directory, NIS, or NIS+ domain, you can also use domain accounts. Themanagement server can validate the domain user accounts that are configuredfor any domain that the authentication broker recognizes.
Supported user domain typesThe VCS Management Console uses the Symantec Product Authentication Servicefor user authentication.
The authentication service supports the following user domain types:
■ Windows
■ UNIX NIS
■ UNIX NIS+
■ UNIX Password (the UNIX system password)
33About users and user privilegesAbout user accounts
■ Lightweight Directory Access Protocol (LDAP)
Note: In some circumstances, the authentication service may not authenticateNIS OS groups as expected.
Internal user accountsThe management server maintains internal user accounts for infrastructurecommunications.
The following are the internal user accounts:
■ CMC@CMC_SERVICES: The management server uses this account to connectand authenticate with the local network upon startup.
■ CMC_CLI@CMC_SERVICES: The CLI uses this account to connect andauthenticate with the management server.
User account representationsThe following table contains the internal representation for each type of useraccount.
user_name@domainSecure mode cluster users
user_name@domain@domain_typeOperating system users
If the management server user name [email protected], the username that is added to the non-secure mode cluster isa_AT_b_DOT_com
Operating system user - A userwho is added to cluster that isnot configured in secure mode
user_name@domain@domain_typeOperating system user groups
user_name@cluster@vcsClassic VCS
How the management server authenticates useraccounts
The management server uses a Symantec Product Authentication Serviceauthentication broker to authenticate users. The authentication broker must beinstalled on the same system as the management server.
The authentication broker requires a root broker. You must install and configurea root broker somewhere in the enterprise and then configure the authentication
About users and user privilegesUser account representations
34
broker. If you do not currently have a root broker, you may install and configureone on the management server host system.
See “About Symantec Product Authentication Service” on page 20.
35About users and user privilegesHow the management server authenticates user accounts
About users and user privilegesHow the management server authenticates user accounts
36
Preparing to install theconsole
This chapter includes the following topics:
■ Typical setup diagrams
■ Installation workflow
■ Supported software for the VCS Management Console
■ About the security infrastructure
■ Installing the root broker
■ Installing the authentication broker on the management server
Typical setup diagramsYou can install the VCS Management Console on a standalone or a clusteredmanagement server.
In a standalone configuration, the management server resides on one system. Astandalone configuration is a simpler installation, but the management server isnot highly available.
Figure 3-1 displays a typical setup with a standalone management server.
3Chapter
Figure 3-1 Typical setup with standalone management server
Symantec ProductAuthentication ServiceRoot Broker
Veritas Cluster ServerManagement Consolemanagement server
Managed Cluster Managed Cluster
Authentication broker
In a clustered configuration, the management server resides on each node of acluster and is configured for failover. The clustered configuration is a morecomplex installation, but the management server is highly available.
Figure 3-2 displays a typical setup with a clustered management server.
Preparing to install the consoleTypical setup diagrams
38
Figure 3-2 Typical setup using a clustered management server
Symantec ProductAuthentication ServiceRoot Broker
Managed Cluster Managed Cluster
Management server cluster
management server(failover target)
management server(running)
Installation workflowInstalling VCS Management Console involves several decisions and tasks.
Figure 3-3 displays the installation workflow for the VCS Management Console.
39Preparing to install the consoleInstallation workflow
Figure 3-3 VCS Management Console installation flowchart
Set up a highly availablemanagement server
Set up a VCS cluster in securemode
Import shared storage on one node
Start the management server for the first time
Install Symantec productAuthentication Service. Set up aroot broker in your enterprise.
Install and configure an authenticationbroker on the system designatedto be the management server
Install the management serverpackages
Do you havea Symantec product
Authentication Serviceroot broker
in yourenterprise?
Log in as a local administrator
Configure VCS Management Console (as either standalone orclustered). The installer will then restart the management server.
Log in again with the initial administrator user chosenduring configuration
Set up a standalonemanagement server
Decide uponthe configuration
layout
Install the management serverin the cluster
No
Yes
Supported software for theVCSManagementConsoleThe VCS Management Console supports several operating systems and VCSversions for both the management server and for the managed clusters.
Preparing to install the consoleSupported software for the VCS Management Console
40
Supported operating systems for the management serverTable 3-1 displays the supported operating systems for the management server.
Table 3-1 Supported operating systems for the management server
Supported operating systemsVCSManagementConsolemanagementserver configuration
■ Solaris 9 and 10 (SPARC), 64-bit, withpatches indicated by Sun
■ Windows Server 2003 Standard Edition,Datacenter Edition, Enterprise Edition,and Web Edition, 32- and 64-bit(x86,x86-64), with patches as indicated byMicrosoft.
■ Red Hat Linux 5 Update 2, 64-bit
Standalone or highly available (clustered)
Supported VCS versions for clustering the management serverTable 3-2 displays the supported VCS versions for management server clustering.
Note: Refer to the VCS documentation for the specific platform and versioninformation on VCS requirements. You must configure the VCS cluster in securemode.
Table 3-2 VCS versions that support management server clustering
Supported VCS versionsManagement Server cluster
VCS versions supported for managementserver clustering:
■ For Solaris, 9, 10, SPARC:
VCS for Solaris (SPARC) 5.0 MP1 and 5.0MP3
■ For Windows 2003, latest service pack,x86, x86-64:
VCS for Windows 5.0, 5.0 RP1a and 5.1
■ For Linux, RH 5 U2, x86-64:
VCS for Linux 5.0 MP3
Cluster that hosts a highly availablemanagement server
Supported VCS versions for managed clustersTable 3-3 displays the supported VCS versions for the managed clusters.
41Preparing to install the consoleSupported software for the VCS Management Console
Note: If you have supported VCS clusters that also run the cluster connecter,reconfigure the clusters to use a direct connection. The version 5.5 managementserver does not support the cluster connector.
Table 3-3 VCS versions that are supported on managed clusters
Supported VCS versions by operatingsystem
Managed clusters
VCS 4.0 with latest MP, 5.0, 5.0 MP1, 5.0 MP3AIX managed clusters
VCS 4.1 with latest MP, 5.0, 5.0 MP1, 5.0 MP3HP-UX managed clusters
VCS 4.1 with latest MP, 5.0, 5.0 MP1, 5.0MP2, 5.0 MP3
Linux managed clusters
VCS 4.1 with latest MP, 5.0, 5.0 MP1, 5.0 MP3Solaris SPARC managed clusters
VCS 4.1 with latest MP, 5.0, 5.0 MP3Solaris Opteron managed clusters
VCS 5.0, 5.1, 5.1 MP1, 5.1 MP2VMware ESX managed clusters
VCS 4.1, 4.2, and 4.3 with latest MP, 5.0RP1a, VCS 5.1
Windows managed clusters
Supported browsersYou must view the VCS Management Console using a Web browser.
The VCS Management Console supports the following browsers:
■ Microsoft Internet Explorer 6.0 and 7.0
■ Firefox 2.0 and 3.0.x
Note:VCS Management Console 5.5 does not support Firefox on Linux platforms.
Required pluginsThe console also requires the Macromedia Flash plug-in 9.0 or 10.0 for the browser.
Recommended management server hardwareSymantec recommends the following minimum configuration for the managementserver hardware:
■ Two CPUs
Preparing to install the consoleSupported software for the VCS Management Console
42
■ Two GB of RAM
■ Approximately 30 GB of storage per 100 clusters.
Note: For enterprises with large cluster configurations, additional hardwareresources (CPUs and memory) are recommended for optimal performance. Contactsupport for more information.
About the security infrastructureThe VCS Management Console requires that you set up a properly configuredsecurity infrastructure to ensure proper user authentication among the VCSManagement Console and clusters in the managed enterprise.
Perform the following tasks to set up the security infrastructure:
■ Root broker:Verify that you have a root broker in your enterprise. Install the root broker,if needed. Symantec recommends installing one root broker in the enterprise.You may choose to configure the management server system as a root broker.See “Installing the root broker” on page 43.
■ Authentication broker:Set up the system that you plan to use as the management server to be theauthentication broker. This task involves installing the authentication brokeron the management server system.See “Installing the authentication broker on the management server”on page 48.
Installing the root brokerSymantec recommends that you have one root broker for your whole enterprise.However, you can optionally install the root broker and the management serveron the same system for testing purposes. The option is calledroot-plus-authentication-broker mode, or R+AB. This option appears in theinstaller menu of the Symantec Product Authentication Service.
Follow the appropriate procedure for installing and configuring the root brokerfor your system:
■ Installing and configuring the root broker on Solaris
■ Installing and configuring the root broker on Windows
■ Installing and configuring the root broker on Linux
43Preparing to install the consoleAbout the security infrastructure
Installing and configuring the root broker on SolarisThis task enables you to install and configure the root broker on a Solaris system.A Solaris root broker can be set up for use with a Windows management server.
To install and configure the root broker on Solaris
1 Insert the distribution media into the disc drive on the local system. At thecommand prompt, enter the following command to move to the authenticationservice directory:
cd solaris/sparc/authentication_service
2 Execute the installat script using the following command:
./installat -rsh
This presents copyright information and the location of log files for theinstallat script.
You can install the Symantec Product Authentication Service in three modes:root broker mode; authentication broker mode; or a combination of both.
3 Enter 2 to select the root broker option.
Enter the mode which you would like VxSS installed? [1-3,q] 2
Note: If you want to make the management server the authentication brokeras well for the R+AB mode, then select option 1. This procedure and thefollowing steps only describe the root broker option.
4 Enter the system name on which you want to install the root broker.
Enter the system name on which to install VxSS: <system RB>
This performs an initial system check on the system where you want to installthe root broker. If these checks are satisfactory, setup lists the authenticationservice packages to be installed.
5 Press Enter. The installation completes on all systems.
You may install authentication service packages without configuration.Choose to configure the authentication service later using the installat
-configure command.
6 Enter y to configure the authentication service.
Are you ready to configure VxSS? [y,n,q] (y) y
Preparing to install the consoleInstalling the root broker
44
7 Enter the password for the root broker.
Enter password for Root Broker administrator for the Root Broker
on host <system RB>
You must retain the password that you entered at this prompt. You need thispassword later to configure the authentication brokers.
8 Enter y to start the Symantec Product Authentication Service processes.
Do you want to start Symantec Product Authentication Service
processes now?[y,n,q] (y)
9 Enter five or more characters to create an encryption key.
Enter five or more characters to be used an encryption key:
This key must be retained in a secure file and referenced using
the -enckeyfile option if the generated response file is to be
used again.
Press [Return] to continue
10 Press Enter. Verify that the root broker is running by using the followingcommand to look for the vxatd process:
ps -ef|grep vxatd
11 Verify that the process is running as a root broker, RB and not asauthentication broker, AB or in the combination mode, R + AB. Use thefollowing command:
/opt/VRTSat/bin/vssat showbrokermode
The broker mode should be 2.
Installing and configuring the root broker on WindowsThis task enables you to install and configure the root broker on a Windowssystem.
45Preparing to install the consoleInstalling the root broker
To install a root broker on Windows
1 Find the installer at the following location:
windows/Symantec_Product_Authentication_Service/VxSSVRTSatSetup.exe
on the install DVD.
2 Launch the wizard to install the Symantec Product Authentication Service.Click Next.
3 Select the setup type Complete to install the authentication service. ClickNext.
4 On the Authentication Broker Service dialog box, do the following:
■ Select the Root Broker Only mode to install the authentication service.
■ Select the Automatic option.
■ Select the Start Service After Installation option.
■ Click Next.
Note: If you want to make the management server the authentication brokeras well for the R+AB mode, then the Windows option isRoot+AuthenticationBroker. This procedure and the following steps only describe the root brokeroption.
5 The setup screen displays a summary of the settings that are specified forthe authentication service installation. Click Next.
6 Provide the root broker password. Click Next.
7 The wizard successfully completes the authentication service installation.Click Finish.
Installing and configuring the root broker on LinuxThis task enables you to install and configure the root broker on a Linux system.
Preparing to install the consoleInstalling the root broker
46
To install and configure the root broker on Linux
1 Insert the distribution media into the disc drive on the local system. At thecommand prompt, enter the following command to move to the authenticationservice directory:
cd linux/rhel5_x86_64/authentication_service
2 Execute the installat script using the following command:
./installat -rsh
This presents copyright information and the location of log files fortheinstallat script. You can install the Symantec Product AuthenticationService in three modes: root broker mode; authentication broker mode; or acombination of both.
3 Enter 2 to select the root broker option.
Enter the mode which you would like VxSS installed? [1-3,q] 2
Note: If you want to make the management server the authentication brokeras well for the R+AB mode, then select option 1. This procedure and thefollowing steps only describe the root broker option.
4 Enter the system name on which you want to install the root broker.
Enter the system name on which to install VxSS: <system RB>
This performs an initial system check on the system where you want to installthe root broker. If these checks are satisfactory, setup lists the authenticationservice packages to be installed.
5 Press Enter. The installation completes on all systems.
You may install authentication service packages without configuration.Choose to configure the authentication service later using the installat
-configure command.
6 Enter y to configure the authentication service.
Are you ready to configure VxSS? [y,n,q] (y) y
47Preparing to install the consoleInstalling the root broker
7 Enter the password for the root broker.
Enter password for Root Broker administrator for the Root Broker
on host <system RB>
You must retain the password that you entered at this prompt. You need thispassword later to configure the authentication brokers.
8 Enter y to start the Symantec Product Authentication Service processes.
Do you want to start Symantec Product Authentication Service
processes now?[y,n,q] (y)
9 Enter five or more characters to create an encryption key.
Enter five or more characters to be used an encryption key:
This key must be retained in a secure file and referenced using
the -enckeyfile option if the generated response file is to be
used again.
Press [Return] to continue
10 Press Enter.
Verify that the root broker is running by using the following command tolook for the vxatd process:
ps -ef|grep vxatd
11 Verify that the process is running as a root broker, RB and not asauthentication broker, AB or in the combination mode, R+AB.
Use the following command:
/opt/VRTSat/bin/vssat showbrokermode
The broker mode should be 2.
Installing the authentication broker on themanagement server
Before you can use the VCS Management Console, you must install anauthentication broker on the machine that hosts the management server. Theauthentication broker on the management server handles user authenticationfor console logons.
Preparing to install the consoleInstalling the authentication broker on the management server
48
The authentication broker must also connect to a root broker. The root brokerwill exist in your enterprise due to one of the following reasons:
■ The root broker may already exist in the enterprise (it was previously installedand configured).
■ You may have installed or will install a new root broker on a different machinefrom the one that hosts the management server. This process is described inthe previous section:See “Installing the root broker” on page 43.
■ The authentication broker that you install on the management server systemmay be installed in the root-plus-authentication-broker mode or R+AB mode,which means that it is both an authentication broker and a root broker.
If the root broker already exists in the enterprise (it was previously installed andconfigured) or if you have installed a new root broker on a different machine fromthe one that hosts the management server, then you need to provision anauthentication broker account on the root broker. Refer to the following proceduresfor provisioning an authentication broker account on the root broker:
■ See “Provisioning the authentication broker account on Solaris” on page 49.
■ See “Provisioning the authentication broker account on Windows” on page 53.
■ See “Provisioning the authentication broker account on Linux” on page 55.
If you installed or will install the management server system in theroot-plus-authentication-broker mode or R+AB mode, then you do not need toprovision an authentication broker account on the root broker. For the R+ABmode, this procedure is unnecessary.
Provisioning the authentication broker account on SolarisProvisionment involves the following tasks:
■ Creating a principal i.e. authentication broker account on the intendedmanagement server.
■ Copying the root broker credential (root hash) to the intended managementserver for use by the new authentication broker account.
You must run the commands in this procedure on the dedicated root broker system.
Note: This procedure requires the path to the vssat command (/opt/VRTSat/bin)to be specified in the default path.
49Preparing to install the consoleInstalling the authentication broker on the management server
To provision the authentication broker account on Solaris
1 Check for any existing principal on the target standalone Solaris managementserver. In the following command, the dedicated root broker system (i.e. thelocal system) is [email protected]. The target standalone Solarismanagement server is system2.
vssat showprpl --pdrtype root --domain [email protected]
--prplname system2
2 If found, delete the existing principal.
vssat deleteprpl --pdrtype root --domain [email protected]
--prplname system2
3 Create and add a new principal.
vssat addprpl --pdrtype root --domain [email protected]
--prplname system2 --password veritas --prpltype service
4 Retrieve the root hash from the root broker.
cd /opt/VRTSat/bin/
ls -l root_hash
5 Copy the root hash to the target management server.
rcp ./root_hash system2:/tmp/
6 Log in to the target management server and run the installat program toinstall and configure the authentication broker.
Installing and configuring the authentication broker on SolarisIf you have a Solaris management server, you must also have a Solarisauthentication broker.
Note:Before installing and configuring the authentication broker, you must installand configure a dedicated root broker system. If you chose theroot-plus-authentication-broker mode or R+AB mode earlier, then skip thefollowing authentication broker installation procedures.
Preparing to install the consoleInstalling the authentication broker on the management server
50
To install and configure the authentication broker on Solaris
1 Insert the distribution media into the disc drive on the local system. At thecommand prompt, enter the following command to move to the authenticationservice directory:
cd solaris/sparc/authentication_service
2 Run the installat script using the following command:
./installat -rsh
This command presents copyright information and the location of log filesfor the installat script.
3 Enter 3 to select the authentication broker only option.
Enter the mode which you would like VxSS installed? [1-3,q] 3
4 Enter the system name on which you want to install the authentication broker.
In this command, "system_AB" is the name of the intended standalonemanagement server.
Enter the system name on which to install VxSS: <system_AB>
The installat script performs an initial check of the management serversystem and them prompts you to press [Return].
Press [Return] to continue: [Return]
The installat script displays status information about the install.
5 Type y or press Enter to configure the authentication broker.
Are you ready to configure VxSS? [y,n,q] (y)
To configure the authentication broker, enter the root broker host, port, andthe path to the root hash.
In the following example, system1.veritas.com is the host, 2821 is the port,and /tmp/root_hash is the path:
Please enter the root broker host system1.veritas.com
Enter the broker port (1556) 2821
Please enter complete path to the file which contains the
Root Broker's hash /tmp/root_hash
51Preparing to install the consoleInstalling the authentication broker on the management server
6 Enter y or press Enter to verify that the information up to this point is correct.
Are the above information correct? [y,n,q] (y)
7 Enter the system name, the password, and the domain name for theauthentication broker.
In the following example: the system name is system_AB, the password is notshown, and the domain is [email protected]
Enter Authentication Broker's identity system_AB
Enter password for system_AB
Enter the domain name for the Authentication Broker's identity
8 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
9 Enter the password for the authentication broker administrator.
Enter password for Authentication Broker administrator for the
Authentication Broker on host system_AB
10 Enter y or press Enter to start the Symantec Product Authentication Serviceprocesses.
Do you want to start Symantec Product Authentication Service
processes now?[y,n,q] (y)
11 Enter five or more characters to create an encryption key.
In the following example, the encryption key is veritas.
Enter five or more characters to be used an encryption key:
This key must be retained in a secure file and referenced using
the -enckeyfile option if the generated response file is to be
used again.
Press [Return] to continue
Preparing to install the consoleInstalling the authentication broker on the management server
52
12 Press Enter. Verify that the authentication broker is running by using thefollowing command to look for the vxatd process:
ps -ef|grep vxatd
13 Verify that the process is running as an authentication broker, AB and notas a root broker, RB or in the combination mode, R + AB using the followingcommand: /opt/VRTSat/bin/vssat showbrokermode
The broker mode should be 1.
Provisioning the authentication broker account on WindowsProvisionment involves the following tasks:
■ Creating a principal (authentication broker account) on the root broker system.
■ Copying the root broker credential (root hash) to the intended managementserver for use by the new authentication broker account.
You must perform the following steps on the dedicated root broker system.
The commands in this procedure assume that the directory to the vssat command(i.e., C:\Program Files\VERITAS\Security\authentication\bin) has been added tothe default path. In the following example, the root broker is the local system,system1.veritas.com. The target system that is provisioned as an authenticationbroker is system2.veritas.com.
To provision authentication broker account in the root broker on Windows
1 Check for any existing principal (i.e. authentication broker) on the root brokersystem.
vssat showprpl --pdrtype root --domain [email protected]
--prplname system2
2 Create and add the principal if you cannot find it.
vssat addprpl --pdrtype root --domain [email protected]
--prplname system2 --password veritas --prpltype service
3 Retrieve the root hash.
53Preparing to install the consoleInstalling the authentication broker on the management server
4 Copy the root hash to the intended authentication broker system.
rcp ./root_hash system2:/tmp/
5 Log in to the target authentication broker system and run the installat
program.
Installing and configuring the authentication broker on WindowsIf you have a Windows management server, you must also have a Windowsauthentication broker.
Note:Before installing and configuring the authentication broker, you must installand configure a dedicated root broker system. If you chose theroot-plus-authentication-broker mode or R+AB mode earlier, then skip thefollowing authentication broker installation procedures.
To install and configure the authentication broker on Windows
1 Insert the distribution media into the disc drive. Click the icon for the wizardto install the Symantec Product Authentication Service. Click Next.
2 Select the setup type Complete to install the authentication service. ClickNext.
3 On the Authentication Broker Service dialog box, do the following:
■ Select the AuthenticationBrokerOnly mode to install the authenticationservice.
■ Select the Automatic option.
■ Select the option Start Service After Installation.
■ Click Next.
4 The setup screen displays a summary of the settings that are specified forthe authentication service installation. Click Next to display the progress ofthe authentication service installation.
5 Select Yes to enable authentication service to look for the root broker. Also,indicate the IP range and the timeout to scan.
6 From the list of discovered root broker, select the root broker. Click Next.
7 On the Authentication Broker Identity dialog box, do the following:
■ Provide the domain name and authentication broker name to identify theauthentication broker’s identity at the root broker.
Preparing to install the consoleInstalling the authentication broker on the management server
54
■ Click Next to display the progress of the authentication service installation.
8 Provide the authentication broker passwords. Click Next.
The wizard completes the authentication service installation.
9 Click Finish.
Provisioning the authentication broker account on LinuxProvisionment involves the following tasks:
■ Creating a principal i.e. authentication broker account on the intendedmanagement server.
■ Copying the root broker credential (root hash) to the intended managementserver for use by the new authentication broker account.
You must run the commands in this procedure on the dedicated root broker system.
Note: This procedure requires the path to the vssat command (/opt/VRTSat/bin)to be specified in the default path.
To provision the authentication broker account on Linux
1 Check for any existing principal on the target standalone Linux managementserver. In the following command, the dedicated root broker system (i.e. thelocal system) is [email protected]. The target standalone Linuxmanagement server is system2.
vssat showprpl --pdrtype root --domain [email protected]
--prplname system2
2 If found, delete the existing principal.
vssat deleteprpl --pdrtype root --domain [email protected]
--prplname system2
3 Create and add a new principal.
vssat addprpl --pdrtype root --domain [email protected]
--prplname system2 --password veritas --prpltype service
4 Retrieve the root hash from the root broker.
cd /opt/VRTSat/bin/
ls -l root_hash
55Preparing to install the consoleInstalling the authentication broker on the management server
5 Copy the root hash to the target management server.
rcp ./root_hash system2:/tmp/
6 Log in to the target management server and run the installat program toinstall and configure the authentication broker.
Installing and configuring the authentication broker on LinuxIf you have a Linux management server, you must also have a Linux authenticationbroker.
Note:Before installing and configuring the authentication broker, you must installand configure a dedicated root broker system. If you chose theroot-plus-authentication-broker mode or R+AB mode earlier, then skip thefollowing authentication broker installation procedures.
To install and configure the authentication broker on Linux
1 Insert the distribution media into the disc drive on the local system. At thecommand prompt, enter the following command to move to the authenticationservice directory:
cd linux/rhel5_x86_64/authentication_service
2 Run the installat script using the following command:
./installat -rsh
This command presents copyright information and the location of log filesfor the installat script.
3 Enter 3 to select the authentication broker only option.
Enter the mode which you would like VxSS installed? [1-3,q] 3
Preparing to install the consoleInstalling the authentication broker on the management server
56
4 Enter the system name on which you want to install the authentication broker.
In this command, "system_AB" is the name of the intended standalonemanagement server.
Enter the system name on which to install VxSS: system_AB
The installat script performs an initial check of the management serversystem and them prompts you to press Enter.
Press [Enter] to continue: [Enter]
The installat script displays status information about the install.
5 Type y or press Enter to configure the authentication broker.
Are you ready to configure VxSS? [y,n,q] (y) y
To configure the authentication broker, enter the root broker host, port, andthe path to the root hash.
In the following example, system1.veritas.com is the host, 2821 is the port,and /tmp/root_hash is the path:
Please enter the root broker host system1.veritas.com
Enter the broker port (1556) 2821
Please enter complete path to the file which contains the
Root Broker's hash /tmp/root_hash
6 Enter y to verify that the information up to this point is correct.
Are the above information correct? [y,n,q] (y)
Press Enter to continue.
7 Enter the system name, the password, and the domain name for theauthentication broker.
In the following example: the system name is system_AB, the password is notshown, and the domain is [email protected].
Enter Authentication Broker's identity system_AB
Enter password for system_AB
Enter the domain name for the Authentication Broker's identity
8 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
57Preparing to install the consoleInstalling the authentication broker on the management server
9 Enter the password for the authentication broker administrator.
Enter password for Authentication Broker administrator for the
Authentication Broker on host system_AB
A string of five or more characters is required to encrypt passwords in theresponsefile.
Enter five or more characters to be used as an encryption key.
This key must be retained in a secure file and referenced using the -enckeyfileoption if the generated responsefile is to be used again.
10 Press Enter to continue.
11 Verify that the authentication broker is running by using the followingcommand to look for the vxatd process:
ps -ef|grep vxatd
12 Verify that the process is running as an authentication broker, AB and notas a root broker, RB or in the combination mode, R + AB using the followingcommand:
/opt/VRTSat/bin/vssat showbrokermode
The broker mode should be 1.
Preparing to install the consoleInstalling the authentication broker on the management server
58
Installing, upgrading, anduninstalling themanagement server
This chapter includes the following topics:
■ Before you install the management server
■ About installing the management server
■ Installing the management server on Solaris
■ Installing the management server on Windows
■ Installing the management server on Linux
■ Upgrading to VCS Management Console 5.5
■ Installing the Japanese language pack for the console
■ Configuring the management server
■ Configuring a peer management server
■ Uninstalling the management server
■ Uninstalling the authentication broker
Before you install the management serverBefore you install the management server, perform the following steps:
■ Review the system requirements and the supported software.
4Chapter
■ Ensure that you have set up the required security infrastructure.Symantec recommends that you have a Symantec Product AuthenticationService root broker already installed in your enterprise. If you do not, youmust install a root broker before installing the management server. You mustalso install an authentication broker on the management server system.
See “Recommended management server hardware” on page 42.
See “Supported operating systems for the management server” on page 41.
See “Supported VCS versions for clustering the management server” on page 41.
See “Installing the root broker” on page 43.
See “Installing the authentication broker on the management server” on page 48.
About installing the management serverInstall the management server to centrally manage multiple clusters.
The VCS Management Console installation program offers two types of installation:standalone or clustered. You can install the management server on a standalonesystem. You can also configure high-availability for your management server byinstalling it in a VCS cluster.
Note: If you install the management servers in a VCS cluster for high-availability,the VCS cluster must be configured in secure mode.
For typical setup diagrams:
See “Typical setup diagrams” on page 37.
For information about VCS requirements:
See “Supported software for the VCS Management Console” on page 40.
If the enterprise has more than one management server, you can mix standaloneand clustered installations.
In a clustered installation, you install the management server on all nodes in thecluster. VCS can be either online or offline during either type of installation.
Note: For a Windows installation, if you copy the disc image of the Windowsinstaller to another location, ensure that the path to run the installer is no longerthan 255 characters. Otherwise, the installation tasks fail.
Installing, upgrading, and uninstalling the management serverAbout installing the management server
60
Table 4-1 lists the available management server installation options. Choose theappropriate installation option for your configuration.
Table 4-1 Management server installation options
Installation optionOperating system
Standalone management server installation
See “Installing a standalone management server on Solaris”on page 61.
Solaris
Highly-available management server installation
See “Installing a highly-available management server onSolaris” on page 63.
Solaris
Standalone management server installation
See “Installing a standalone management server onWindows” on page 65.
Windows
Highly-available management server installation
See “Installing a highly-available management server onWindows” on page 67.
Windows
Standalone management server installation
See “Installing a standalone management server on Linux”on page 69.
Linux
Highly-available management server installation
See “Installing a highly-available management server onLinux” on page 71.
Linux
Installing the management server on SolarisYou must install and configure the Symantec Product Authentication Servicebefore installing the management server.
See “About the security infrastructure” on page 43.
Installing a standalone management server on SolarisYou can install the management server on any standalone system that meets thehardware and the software requirements.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to have
61Installing, upgrading, and uninstalling the management serverInstalling the management server on Solaris
problems, type q to quit the installation and then verify the installationprerequisites.
To install the management server on a standalone Solaris system
1 Insert the disc into the drive on the local system and navigate to thesubdirectory: solaris/sparc/cluster_management_console
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents the following message:
Set up will install the veritas cluster server management console.
4 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed packages. If these checks are satisfactory, the programlists the packages to be installed and presents the following prompt:
Press [Return] to continue:
Installing, upgrading, and uninstalling the management serverInstalling the management server on Solaris
62
5 Press Enter to complete the installation process.
The installcmc script eventually responds with the following messages:
Veritas Cluster Server Management Console 5.5 Installation Program
Installing VCSMC: 0% _______________________________________
Installing VCSMC: 50% _______________________
Installing VCSMC: 100%
Installation completed successfully on all systems
Installation log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installcmc-kO4Sv4
To configure VCS Management Console:
1. Start the console with: /opt/VRTScmcm/bin/vxcmcweb start
2. In a browser, navigate to: https://[hostname]:14443
Note: it may take a few moments for VCS Management Console
to become accessible.
6 Start the Web console and proceed to configure the management server.
See “Configuring a newly-installed standalone management server on Solaris” on page 86.
Installing a highly-available management server on SolarisInstalling the management server in a VCS cluster makes it highly available. Runthe installcmc script on every node in a VCS cluster that is configured in securemode.
Note: You will need to install the management server on each node in the VCScluster.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
Ensure that the following prerequisites are met before you install the managementserver:
63Installing, upgrading, and uninstalling the management serverInstalling the management server on Solaris
■ Set up a VCS clusterOn UNIX platforms, see the Veritas Cluster Server Installation Guide forinformation about setting up a VCS cluster.
■ Ensure that the cluster is configured to run in secure mode
■ Ensure that shared storage is available, either as shared disks or nfs mounts
See “Supported software for the VCS Management Console” on page 40.
To install a highly-available management server on Solaris
1 Insert the disc into the drive on the local system and navigate to thesubdirectory: solaris/sparc/cluster_management_console
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents the following message:
Set up will install the veritas cluster server management console.
4 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed packages. If these checks are satisfactory, the scriptlists the packages to be installed or upgraded and presents the followingprompt:
Press [Return] to continue:
Installing, upgrading, and uninstalling the management serverInstalling the management server on Solaris
64
5 Press Enter to complete the installation process.
The installcmc script eventually responds with the following messages:
Veritas Cluster Server Management Console 5.5 Installation Program
Installing VCSMC: 0% _________________________________________
Installing VCSMC: 50% _______________________
Installing VCSMC: 100%
Installation completed successfully on all systems
Installation log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installcmc-kO4Sv4
To configure VCS Management Console:
1. Start the console with: /opt/VRTScmcm/bin/vxcmcweb start
2. In a browser, navigate to: https://[hostname]:14443
Note: it may take a few moments for VCS Management Console
to become accessible.
6 Start the Web console and configure the management server.
See “Configuring a newly-installed highly-available management server onSolaris” on page 87.
Installing the management server on WindowsYou must install and configure the Symantec Product Authentication Servicebefore installing the management server.
See “About the security infrastructure” on page 43.
Installing a standalone management server on WindowsYou can install the management server on any standalone system that meets thehardware and the software requirements.
If at any step you experience a result other than the expected result that isdocumented here, you can click Back to re-enter information. If you continue tohave problems, click Cancel to quit the installation and then verify the installationprerequisites.
65Installing, upgrading, and uninstalling the management serverInstalling the management server on Windows
To install a standalone management server on Windows
1 Insert the disc into the drive on the local system. Using Windows Explorer,navigate from the top directory to the windows/cluster_management_console/directory.
2 Double-click setup.exe.
3 In the dialog box, select a language and then click OK.
4 In the SymantecProductInstaller window, select VCSManagementConsole5.5 for Windows.
5 In the Welcome panel, ensure that the listed prerequisites for the installationare satisfied.
The left pane of the Welcome panel contains a list of main installation steps.A white arrow indicates your progress through the list. Check marks indicatecompleted steps.
Click Next.
6 In the Computer Selection panel, wait while setup populates the controlswith default information and then do the following:
■ Specify the computer on which to install the management server.The local system displays in the Computer box. Click Browse to searchfor and specify a computer other than the default. You can also type acomputer name directly into the Computer text box.
■ Click Add to select the specified computer.Setup analyzes the selected system to verify platform prerequisites anddisplays the results in the Description field.
■ If you want to change the computer selection, click Remove and beginthis step again.
■ If you want to change the install path, click Change. Click Default tochange a changed path back to the original path.
■ Click Next.
7 In the Validation panel, setup validates the computer that is listed in thetable. The status column of the table must eventually show Accepted for theinstallation to proceed. If you encounter a problem, you can attempt to correctthe error on the candidate computer and then click Validate Again.
When the Status column shows Accepted, click Next.
8 The Summary panel displays a summary of installation options before theactual installation. Click Install.
Installing, upgrading, and uninstalling the management serverInstalling the management server on Windows
66
9 In the Install/Uninstall panel, the table shows the selected computer and aprogress bar that indicates installation status. When installation is complete,click Next.
10 In the Finish panel, use the list box to scroll through the installation reportand verify that no errors occurred. Click Next.
11 Read the instructions on how to start the console for management serverconfiguration and then click Finish.
See “Configuring a newly-installed standalone management server onWindows” on page 92.
Installing a highly-available management server on WindowsInstalling the management server in a VCS cluster makes it highly available. Runthe install program on every node of a VCS cluster that is configured in securemode.
Note: You will need to install the management server on each node in the VCScluster.
Ensure that the following prerequisites are met before you install the managementserver:
■ Set up a VCS clusterOn Windows, see theVeritas Cluster Server Installation andUpgrade Guide ortheStorageFoundationandHighAvailabilitySolutions InstallationandUpgradeGuide for information about setting up a VCS cluster.
■ Ensure that the cluster is configured to run in secure mode
■ Ensure that shared storage is available, either as shared disks or NFS mounts
See “Supported software for the VCS Management Console” on page 40.
If at any step you experience a result other than the expected result that isdocumented here, you can click Back to re-enter information. If you continue tohave problems, click Cancel to quit the installation and then verify the installationprerequisites.
To install a highly-available management server on Windows
1 Insert the disc into the drive on the local system. Using Windows explorer,navigate from the top directory to the windows/cluster_management_console/directory.
2 Double-click setup.exe.
67Installing, upgrading, and uninstalling the management serverInstalling the management server on Windows
3 In the dialog box, select a language and then click OK.
4 In the SymantecProductInstaller window, select VCSManagementConsole5.5 for Windows.
5 In the Welcome panel, ensure that the listed prerequisites for the installationare satisfied.
The left pane of the Welcome panel contains a list of main installation steps.A white arrow indicates your progress through the list. Check marks indicatecompleted steps.
Click Next.
6 In the Computer Selection panel, wait while setup populates the controls withdefault information and then do the following:
■ Specify the cluster systems on which to install the management server.The local system displays in the Computer text box. Click Add to selectthe specified computer. Click Browse to search for the remaining clustersystems. Click Add to add each one to the table. You can also type acomputer name directly into the Computer text box.Setup analyzes the selected systems to verify platform prerequisites anddisplays the results in the Description field.
■ If you want to change the computer selection, click a computer in thetable, click Remove, and browse for another system.
■ If you want to change the install path, click Change. Click Default tochange a changed path back to the original path.
■ Click Next.
7 In the Validation panel, when the Status column shows Accepted for eachsystem, click Next.
Setup validates the computers that are listed in the table. The Status columnof the table must eventually show Accepted for each system for the installationto proceed. If you encounter a problem, you can attempt to correct the erroron the candidate computer and then click Validate Again.
8 The Summary panel displays a summary of installation options before theactual installation. Click Install.
9 In the Install/Uninstall panel, the table shows the selected computer and aprogress bar that indicates installation status. When installation is complete,click Next.
Installing, upgrading, and uninstalling the management serverInstalling the management server on Windows
68
10 In the Finish panel, use the list box to scroll through the installation reportand verify that no errors occurred. Click Next.
11 In the final panel, read the instructions on how to start the console formanagement server configuration and then click Finish.
See “Configuring a newly-installed highly-available management server onWindows” on page 94.
Installing the management server on LinuxYou must install and configure the Symantec Product Authentication Servicebefore installing the management server.
See “About the security infrastructure” on page 43.
Installing a standalone management server on LinuxYou can install the management server on any standalone system that meets thehardware and the software requirements.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To install the management server on a standalone Linux system
1 Insert the disc into the drive on the local system and navigate to thesubdirectory: /linux/rhel5_x86_64/cluster_management_console
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents the following message:
Set up will install the veritas cluster server management console.
69Installing, upgrading, and uninstalling the management serverInstalling the management server on Linux
4 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed rpms. If these checks are satisfactory, the programlists the rpms to be installed and presents the following prompt:
Press [Enter] to continue:
5 Press Enter to complete the installation process.
The installcmc script eventually responds with the following messages:
Veritas Cluster Server Management Console 5.5 Installation Program
Installing VCSMC: 0% _________________________________________
Installing VCSMC: 33% __________________________
Installing VCSMC: 66% ___________
Installing VCSMC: 100%
Installation completed successfully on all systems
Installation log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installcmc-pBdEoh
To configure VCS Management Console:
1. Start the console with: /opt/VRTScmcm/bin/vxcmcweb start
2. In a browser, navigate to: https://[hostname]:14443
Note: it may take a few moments for VCS Management Console
to become accessible.
6 Start the Web console and configure the management server:
See “Configuring a newly-installed standalone management server on Linux”on page 100.
Installing, upgrading, and uninstalling the management serverInstalling the management server on Linux
70
Installing a highly-available management server on LinuxInstalling the management server in a VCS cluster makes it highly available. Runthe installcmc script on every node in a VCS cluster that is configured in securemode.
Note: You will need to install the management server on each node in the VCScluster.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q quit the installation and then verify the installation prerequisites.
Ensure that the following prerequisites are met before you install the managementserver:
■ Set up a VCS clusterOn Linux platforms, see the Veritas Cluster Server Installation Guide forinformation about setting up a VCS cluster.
■ Ensure that the cluster is configured to run in secure mode
■ Ensure that shared storage is available, either as shared disks or nfs mounts
To install a highly-available management server on Linux
1 Insert the disc into the drive on the local system and navigate to the/linux/rhel5_x86_64/cluster_management_console subdirectory.
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents the following message:
Set up will install the veritas cluster server management console.
71Installing, upgrading, and uninstalling the management serverInstalling the management server on Linux
4 Enter y or press Enter to verify that the information up to this point iscorrect.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed rpms. If these checks are satisfactory, the script liststhe rpms to be installed or upgraded and presents the following prompt:
Press [Enter] to continue:
5 Press Enter to complete the installation process.
The installcmc script eventually responds with the following messages:
Veritas Cluster Server Management Console 5.5 Installation Program
Installing VCSMC: 0% _________________________________________
Installing VCSMC: 33% __________________________
Installing VCSMC: 66% ___________
Installing VCSMC: 100%
Installation completed successfully on all systems
Installation log files, summary file, and response file are saved at:
/opt/VRTS/install/logs/installcmc-pBdEoh
To configure VCS Management Console:
1. Start the console with: /opt/VRTScmcm/bin/vxcmcweb start
2. In a browser, navigate to: https://[hostname]:14443
Note: it may take a few moments for VCS Management Console
to become accessible.
6 Start the Web console and configure the management server:
See “Configuring a newly-installed highly-available management server onLinux” on page 101.
Installing, upgrading, and uninstalling the management serverInstalling the management server on Linux
72
Upgrading to VCS Management Console 5.5The following procedures enable you to upgrade standalone and clusteredmanagement servers to VCS Management Console 5.5.
Table 4-2 lists the available management server upgrade options. Choose theappropriate upgrade option for your system or systems.
Table 4-2 VCS Management Console 5.5 upgrade options
Upgrade to VCS Management Console 5.5 optionOperating system
Standalone management server upgrade
See “Upgrading a standalone management server on Solaris” on page 73.
Solaris
Highly-available management server upgrade
See “Upgrading a highly-available management server onSolaris” on page 77.
Solaris
Post-upgrade procedure for peer management servers (ifapplicable)
See “Post-upgrade procedure for peer management servers”on page 82.
Solaris
Standalone management server upgrade
See “Upgrading a standalone management server onWindows” on page 79.
Windows
Highly-available management server upgrade
See “Upgrading a highly-available management server onWindows” on page 80.
Windows
Post-upgrade procedure for peer management servers (ifapplicable)
See “Post-upgrade procedure for peer management servers”on page 82.
Windows
Upgrading a standalone management server on SolarisPerform this upgrade on a standalone system that is outside all clusters andavailable on the local network.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to have
73Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
problems, type q to quit the installation and then verify the installationprerequisites.
To upgrade the management server on Solaris
1 Insert the disc into the drive on the local system and navigate to thesolaris/sparc/cluster_management_console subdirectory.
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents a message stating that it installs themanagement server.
4 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed packages. If these checks are satisfactory, the programlists the packages to be installed or upgraded and presents the followingprompt:
Press [Return] to continue:
5 Some packages used by the management server in previous versions may bedeprecated in version 5.5. If the installer detects other software packages onthe system that require these deprecated packages, you will be prompted forconfirmation to remove both the deprecated package and the dependentpackage. For example:
Checking installed packages on system1
Do you want to uninstall package VRTScmccc from system1
which is dependent on package VRTSjre15? [y,n,q,?] (n)
Answer y and the installer will remove both the deprecated package and thedependent package (in this example, VRTSjre15 and VRTScmccc, respectively).
Answer n and neither the deprecated package, nor the dependent packagewill be removed by the upgrade.
Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
74
6 Press Enter. The installcmc program displays the following message:
installcmc is now ready to upgrade VCSMC.
All VCSMC processes that are currently running must be stopped.
75Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
7 Enter y or press Enter to confirm that you want to upgrade the VCSManagement Console.
Are you sure you want to upgrade VCSMC? [y,n,q] (y)
The installcmc script eventually responds with the following messages, whichconclude with instruction for how to complete the upgrade.
Veritas Cluster Server Management Console 5.5 Installation Program
Stopping VCSMC: 0% _________________________________________
Stopping VCSMC: 100%
Shutdown completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Installation Program
Running pre-upgrade tasks for Veritas Cluster Server
Management Console
Stopping Embedded Cluster Management Console ......... Done
Veritas Cluster Server Management Console 5.5 Installation Program
Uninstalling VCSMC: 0% __________________________
Uninstalling VCSMC: 50% ______________________
Uninstalling VCSMC: 100%
Uninstall completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Installation Program
Installing VCSMC: 0% __________________________
Installing VCSMC: 50% _______________________
Installing VCSMC: 100%
Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
76
Installation completed successfully on all systems
Upgrade log files and summary file are saved at:
/opt/VRTS/install/logs/installcmc-r9X1BW
To complete upgrade of VCS Management Console:
1. Start the console with: /opt/VRTScmcm/bin/vxcmcweb start
2. In a browser, navigate to: https://[hostname]:14443
Note: it may take a few moments for VCS Management Console
to become accessible.
8 Proceed to configure standalone management server on Solaris.
See “Configuring a newly-installed standalone management server on Solaris” on page 86.
Upgrading a highly-available management server on SolarisPerform this upgrade on each node of the cluster that hosts the highly-availablemanagement server.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To upgrade a highly-available management server on Solaris
1 Insert the disc into the drive on the local system and navigate to thesolaris/sparc/cluster_management_console subdirectory.
2 At the command prompt, enter the following command to run the installcmcscript:
./installcmc
3 Enter 3 or press Enter to select management server installation.
Select the option you would like to perform: [1-3,q] (3)
The installcmc script presents a message stating that it installs themanagement server.
77Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
4 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The installcmc script performs an initial system check of the local systemand checks for installed packages. If these checks are satisfactory, the scriptlists the packages to be installed or upgraded and presents the followingprompt:
Press [Return] to continue:
5 Some packages used by the management server in previous versions may bedeprecated in version 5.5. If the installer detects other software packages onthe system that require these deprecated packages, you will be prompted forconfirmation to remove both the deprecated package and the dependentpackage. For example:
Checking installed packages on system1
Do you want to uninstall package VRTScmccc from system1
which is dependent on package VRTSjre15? [y,n,q,?] (n)
Answer y and the installer will remove both the deprecated package and thedependent package (in this example, VRTSjre15 and VRTScmccc, respectively).
Answer n and neither the deprecated package, nor the dependent packagewill be removed by the upgrade.
6 Press Enter. The installcmc script displays the following message:
installcmc is now ready to upgrade VCSMC.
All VCSMC processes that are currently running must be stopped.
7 Enter y or press Enter to confirm that you want to upgrade the VCSManagement Console.
Are you sure you want to upgrade VCSMC? [y,n,q] (y)
When the installation finishes, the script presents the following:
■ The path to the installation log files, summary file, and response file.
■ Instructions for how to complete the upgrade.
8 Proceed to configure highly-available management server on Solaris.
See “Configuring an upgraded highly-available management server on Solaris”on page 90.
Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
78
Upgrading a standalone management server on WindowsYou must perform this upgrade on a standalone system that is outside all clustersand available on the local network.
If at any step you experience a result other than the expected result that isdocumented here, you can click Back to re-enter information. If you continue tohave problems, click Cancel to quit the installation and then verify the installationprerequisites.
To upgrade a standalone management server on Windows
1 Insert the disc into the drive on the local system. Using Windows Explorer,navigate from the top directory to the windows/cluster_management_console/directory.
2 Double-click setup.exe.
3 In the Open File - Security Warning dialog box, click Run.
4 In the dialog box, select a language and then click OK.
5 In the Symantec Product Installer window, select VCSManagementConsole5.5 for Windows.
6 In the Open File - Security Warning dialog box, click Run.
Setup presents a progress bar as it copies files to your computer.
7 In the Welcome panel, ensure that the listed prerequisites for the upgradeare satisfied.
The left pane of the Welcome panel contains a list of main installation steps.A white arrow indicates your progress through the list. Check marks indicatecompleted steps.
Click Next.
8 In the Computer Selection panel, wait while setup populates the controls withdefault information and then do the following:
■ Specify the computer on which to upgrade the management server.The local system displays in the Computer text box. Click Browse to searchfor and specify a computer other than the default. You can also type acomputer name directly into the Computer text box.
■ Click Add to select the specified computer.Setup analyzes the selected system to verify platform prerequisites anddisplays the results in the Description field.
■ If you want to change the computer selection, click Remove and beginthis step again.
79Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
■ If you want to change the install path, click Change. Click Default to reverta changed path back to the original path.
■ Click Next.
9 In the Validation panel, setup validates the computer that is listed in thetable. The status column of the table must eventually show Accepted for theinstallation to proceed. If you encounter an error, attempt to correct the erroron the candidate computer and then click Validate Again.
When the Status column shows Accepted, click Next.
10 The Summary panel displays a summary of installation options before theactual installation. Click Install.
11 In the Install/Uninstall panel, a table shows the selected computer and aprogress bar that indicates installation status. When installation is complete,click Next.
12 In the Finish panel, use the list box to scroll through the installation reportand verify that no errors occurred. Click Next.
13 Read the instructions on how to start the console for management serverconfiguration and then click Finish.
See “Configuring a newly-installed standalone management server onWindows” on page 92.
Upgrading a highly-available management server on WindowsThis task enables you to upgrade a highly-available management server onWindows clusters.
Perform this upgrade on each node of the cluster that hosts the highly-availablemanagement server.
If at any step you experience a result other than the expected result that isdocumented here, you can click Back to re-enter information. If you continue tohave problems, click Cancel to quit the installation and then verify the installationprerequisites.
To upgrade a highly-available management server on Windows
1 Insert the disc into the drive on the local system. Using Windows explorer,navigate from the top directory to the windows/cluster_management_console/directory.
2 Double-click setup.exe.
3 In the dialog box, select a language and then click OK.
Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
80
4 In the Symantec Product Installer window, select VCSManagementConsole5.5 for Windows.
5 In the Open File-Security Warning dialog box, click Run.
Setup presents a progress bar as it copies files to your computer.
6 In the Welcome panel, ensure that the listed prerequisites for the upgradeare satisfied.
The left pane of the Welcome panel contains a list of main installation steps.A white arrow indicates your progress through the list. Check marks indicatecompleted steps.
Click Next.
7 In the Computer Selection panel, wait while setup populates the controls withdefault information and then do the following:
■ Specify the computer on which to upgrade the management server.The local system displays in the Computer box. Click Browse to searchfor and specify a computer other than the default. You can also type acomputer name directly into the Computer text box.
■ Click Add to select the specified computer.Setup analyzes the selected system to verify platform prerequisites anddisplays the results in the Description field.
■ If you want to change the computer selection, click Remove and beginthis step again.
■ If you want to change the install path, click Change. Click Default tochange a changed path back to the original path.
■ Click Next.
8 In the Validation panel, the Install Type column shows Install; when theStatus column shows Accepted, click Next.
Setup validates the computer that is listed in the table. The status column ofthe table must eventually show Accepted for the installation to proceed. Ifyou encounter a problem, you can attempt to correct the error on the candidatecomputer and then click Validate Again.
9 The Summary panel displays a summary of installation options before theactual installation. Click Install.
10 In the Install/Uninstall panel, the table shows the selected computer and aprogress bar that indicates installation status. When installation is complete,click Next.
81Installing, upgrading, and uninstalling the management serverUpgrading to VCS Management Console 5.5
11 In the Finish panel, use the list box to scroll through the installation reportand verify that no errors occurred. Click Next.
12 Read the instructions on how to start the console for management serverconfiguration and then click Finish.
See “Configuring a newly-installed highly-available management server onWindows” on page 94.
Post-upgrade procedure for peer management serversWhen upgrading peer management servers from a pre-5.1 software version releaseto 5.5, you must transfer the certificate from the peer management server to thelocal management server. You must also import the certificate using the-importcert command option.
Note:The following procedure only applies for a pre-5.1 software version (5.0, 5.0MP1) to 5.5 version upgrade. The 5.1 software version to 5.5 version upgrade doesnot require this procedure.
Upgrading peer management servers from a pre-5.1 release to 5.5 release
1 First, upgrade both management servers peers to software version 5.5 asdescribed in the earlier sections.
2 Next, copy the file cmc_ms.cer from each peer to a temporary area on theother peer.
3 Execute the command gaserver -importcert <certificate file> <peer
site name> on each management server.
Installing the Japanese language pack for the consoleThe Japanese language pack enables the logon screens and text on the VCSManagement Console pages to display in Japanese.
This task includes installing the language pack for both the Symantec ProductAuthentication Service and for the management server.
Installing the Japanese language pack for the console on Windowssystems
The Japanese language pack enables you to choose Japanese as a language at thelogin screen, which starts the localized Japanese version of the console.
Installing, upgrading, and uninstalling the management serverInstalling the Japanese language pack for the console
82
Ensure that the following prerequisite is met before you install the language pack:
■ You must install the management server—standalone or clustered.See “Installing a standalone management server on Windows” on page 65.See “Installing a highly-available management server on Windows” on page 67.
If at any step you experience a result other than the expected result that isdocumented here, you can click Back to re-enter information. If you continue tohave problems, click Cancel to quit the installation and then verify the installationprerequisites.
To install the Japanese language pack for Symantec Product Authentication Service
1 Locate disc 1 of the Japanese language pack disc set and insert it into the discdrive on the management server host system.
2 Start the installation program for Symantec Product Authentication ServiceJapanese 32.msi located on the disc.
ja\windows\Symantec_Product_Authentication_Service
3 Click Next.
4 In the Welcome panel, specify the user name and organization.
5 In the Set up Type dialog box, select Complete.
6 Click Install.
To install the Japanese language pack for the VCS management server
1 Start the installation program that is located on the disc:
ja\windows\cluster_management_console
2 In the Select Language dialog box, click OK.
3 Select VCSMC Server Japanese Language Pack for Windows. Click Next .
4 In the Welcome panel, specify the target system, domain, and installationpath. Click Next.
5 After the environment check, click Next.
6 Click Install.
Installing the Japanese language pack for the console on Solarissystems
The Japanese language pack enables you to choose Japanese as a language at thelogin screen, which starts the Japanese version of the console.
Ensure that the following prerequisite is met before you install the language pack:
83Installing, upgrading, and uninstalling the management serverInstalling the Japanese language pack for the console
■ You must install the management server—standalone or clustered.See “Installing a standalone management server on Solaris” on page 61.See “Installing a highly-available management server on Solaris” on page 63.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To install the Japanese language pack for Symantec Product Authentication Service
1 Locate disc 1 of the Japanese language pack disc set and insert it into the discdrive on the management server host system.
2 Obtain a command prompt and change to the following directory on the disc.
cd ja/sol_sparc
3 At the command prompt, enter the following command to run the installscript:
./install_lp
To install the Japanese language pack for the management server:
1 Obtain a command prompt and change to the following directory on the disc.
cd ja/sol_sparc
2 Standalone: At the command prompt, enter the following command to runthe install script:
./install_lp
3 Clustered: At the command prompt, enter the following command to run theinstall script:
./install_lp -rsh
For clustered management server, also enter the system name on which youwant to install the language pack.
Configuring the management serverAfter installation, you must name the management server and configure it tofunction in the established Web and security infrastructure.You can configurethe management server on both standalone and clustered systems.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
84
Table 4-3 lists the available management server configuration options. Choosethe appropriate configuration option for your system or systems.
Table 4-3 Management server configuration options
Configuration optionOperating system
Newly-installed standalone management serverconfiguration
See “Configuring a newly-installed standalone managementserver on Solaris ” on page 86.
Solaris
Newly-installed highly-available management serverconfiguration
See “Configuring a newly-installed highly-availablemanagement server on Solaris” on page 87.
Solaris
Upgraded standalone management server configuration
See “Configuring an upgraded standalone managementserver on Solaris” on page 89.
Solaris
Upgraded highly-available management serverconfiguration
See “Configuring an upgraded highly-available managementserver on Solaris” on page 90.
Solaris
Newly-installed standalone management serverconfiguration
See “Configuring a newly-installed standalone managementserver on Windows” on page 92.
Windows
Newly-installed highly-available management serverconfiguration
See “Configuring a newly-installed highly-availablemanagement server on Windows” on page 94.
Windows
Upgraded standalone management server configuration
See “Configuring an upgraded standalone managementserver on Windows” on page 97.
Windows
Upgraded highly-available management serverconfiguration
See “Configuring an upgraded highly-available managementserver on Windows” on page 98.
Windows
85Installing, upgrading, and uninstalling the management serverConfiguring the management server
Table 4-3 Management server configuration options (continued)
Configuration optionOperating system
Newly-installed standalone management serverconfiguration
See “Configuring a newly-installed standalone managementserver on Linux” on page 100.
Linux
Newly-installed highly-available management serverconfiguration
See “Configuring a newly-installed highly-availablemanagement server on Linux” on page 101.
Linux
Configuring a newly-installed standalone management server on SolarisThis task enables you to configure the management server to function in themanaged enterprise.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure a newly-installed standalone management server on Solaris
1 Start the console with the following command:
■ /opt/VRTScmcm/bin/vxcmcweb start
■ Open a browser window to the indicated URL:
https://[hostname]:14443
2 Log in to the console as a user with administrator privileges on themanagement server.
You will need to enter a username, password, and domain.
You will also need to select an appropriate language.
3 After login, the Configuration for Management Server screen appears.
Read the requirements for your configuration, ensure that they have beenmet before proceeding, and then click Next.
4 In the following Configuration for Management Server screen, provide thefollowing required information:
Installing, upgrading, and uninstalling the management serverConfiguring the management server
86
■ Management Server name, IP address, and Site name
■ Management Server Data directory and database port
■ Administrator user name, domain, domain type
After entering this information, click Finish
5 Read the subsequent text boxes that appear and display the followingmessages:
■ Applying configuration. This may take some time.
■ Stopping server...
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
■ VCS Management console is up.
6 Click Click here to log in to log on to the upgraded console.
7 After logon, check the Help>About box to verify that the version number is5.5.
Configuring a newly-installed highly-available management server onSolaris
This task enables you to configure the management server to function in themanaged enterprise.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure a newly-installed highly-available management server on Solaris
1 Start the console with the following command:
■ /opt/VRTScmcm/bin/vxcmcweb start
■ Open a browser window to the indicated URL:
https://[hostname]:14443
2 Log in to the console as a user with administrator privileges on themanagement server.
You will need to enter a username, password, and domain.
You will also need to select an appropriate language.
87Installing, upgrading, and uninstalling the management serverConfiguring the management server
3 After login, the Configuration for Management Server screen appears.
Read the requirements for your configuration, ensure that they have beenmet before proceeding, and then click Next.
4 In the following Configuration for Management Server screen, provide thefollowing required information:
■ Name of the VCSMC Management Server
■ Site Name
■ Webserver Port
■ Database Port
After providing the information, click Next.
5 Select the systems to host the Management Server service group and clickNext.
6 Configure networking for Management Server by selecting the Scope of theNIC (Global or Per System), assigning the NIC, entering the virtual IP address,and entering the Netmask values.
For these values, note the following:
■ For the Scope of the NIC option, select either Global or Per System. TheGlobal option indicates that the cluster uses one network interface card(NIC) to communicate with the network and therefore the managementserver. The Per System option indicates that each system uses its ownNIC.
■ When assigning the NIC, enter the media access control (MAC) addressof the specified NIC. Only one NIC text box is available if you selected theGlobal option.
■ Enter the virtual IP address and netmask of the management server's NICin the corresponding text boxes.
After providing the information, click Next.
7 Configure the storage for the VCS Management Console data.
Select the Storage type (Local or Shared), enter the disk group, the volume,the Scope of the MountPoint (Global or Per System), and the Mount point.
For these values, note the following:
■ For the Storage type option, select either Local Storage or Shared Storage.The Local Storage option indicates that the management server uses localunshared storage for the management server database. The Shared Storage
Installing, upgrading, and uninstalling the management serverConfiguring the management server
88
option indicates that the database resides in shared storage, and thatVeritas Storage Foundation manages that storage.
■ Enter the name of the disk group and volume in the corresponding textboxes.
■ For the Scope of MountPoint options, select either Global or Per System.The Global option indicates that all systems in the cluster use the samemount point. The Shared Storage option indicates that each system usesa different mount point.
After providing the information, click Next.
8 Configure admin user login for Management Server by entering the username, domain, and domain type.
After entering the above information click Finish.
9 Read the subsequent text boxes that appear and display the followingmessages:
■ Configuration of management server will take some time, please wait ...
■ Stopping server...
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
■ VCS Management console is up.
10 Click Click here to log in to log on to the upgraded console.
11 After logon, check the Help>About box to verify that the version number is5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
12 Proceed to view Management Server, Database, and Users subtabs of theAdministration tab to review the Management Server details.
Configuring an upgraded standalone management server on SolarisThis task enables you to configure the management server to function in themanaged enterprise.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure an upgraded standalone management server on Solaris
1 Start the console with the following command:
89Installing, upgrading, and uninstalling the management serverConfiguring the management server
■ /opt/VRTScmcm/bin/vxcmcweb start
■ Open a browser window to the indicated URL:
https://[hostname]:14443
2 Log in to the console as a user with administrator privileges on themanagement server.
In the remaining screens in this procedure, options may be grayed out andunavailable for editing. This preserves the important configurationalparameters of the previous version of the management server.
Note: If your upgrade is from software version 5.1 to 5.5 (standalone orclustered), all options are grayed out and unavailable for editing. If yourupgrade is from a pre-5.1 software release (and only the standalone softwareversion existed at that time), the fields for Database directory and DatabasePort permit editing.
3 In the Upgrade for Management Server screen, click Finish.
4 Read the subsequent text boxes that appear and display the followingmessages:
■ Applying configuration. This may take some time.
■ Stopping server...
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
■ VCS Management console is up.
5 Click Click here to log in to log on to the upgraded console.
6 After logon, check the Help>About box to verify that the version number is5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
Configuring an upgraded highly-available management server onSolaris
This task enables you to configure the management server to function in themanaged enterprise.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
90
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure an upgraded highly-available management server on Solaris
1 Start the console on the cluster node with the following command:
hagrp -online CMC_MS -any
2 Open a browser window to the indicated URL:
https://CMC_IP_address:14443
In this example, CMC_IP_address is the virtual IP address that is configuredin the CMC_MS service group. You can obtain this IP address using thefollowing command:
hares -value CMC_IP_address Address
3 Log in to the console as a user with administrator privileges on themanagement server.
In the remaining screens in this procedure, options may be grayed out andunavailable for editing. This preserves the important configurationalparameters of the previous version of the management server.
Note: If your upgrade is from software version 5.1 to 5.5 (standalone orclustered), all options are grayed out and unavailable for editing. If yourupgrade is from a pre-5.1 software release (and only the standalone softwareversion existed at that time), the fields for Database directory and DatabasePort permit editing.
4 In the Upgrade Management Server panel, provide a site name for the clusterand then click Finish.
The default site name is Untagged Clusters.
Subsequent text boxes display the following messages:
■ Applying configuration. This may take some time.
■ Stopping server.
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
91Installing, upgrading, and uninstalling the management serverConfiguring the management server
■ VCS Management console is up.
5 Click Click here to log in to log on to the upgraded console.
After logon, check the Help>About box to verify that the version number is5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
Configuring a newly-installed standalone management server onWindows
This task enables you to configure the management server to function in themanaged enterprise.
The following services must be running to configure the management server onWindows:
■ The Symantec Product Authentication Service
■ The VCS Management Console web server
Use the Windows Services Manager to ensure that these services are present andrunning.
If at any step you experience a result other than the expected result that isdocumented here, click Back to re-enter information. If you continue to haveproblems, click Cancel to quit the installation and then verify the installationprerequisites.
To configure a newly-installed standalone management server on Windows
1 Click on the shortcut icon of Veritas Cluster Management Console 5.5 onthe desktop to launch the Cluster Management Console web services. Thisstarts the VCS Management Console web server and indicates the IP addresson the browser window.
You can also enter the following address into your browser to launch themanagement server logon page:
https://webserver IP:14443
2 In the Security Alert dialog box, click Yes to accept the security certificate.
3 Log in to the management server with the system administrator’s account.
4 Ensure that all the browser prerequisites that are listed to the right of thelogon information area have green checks by them.
A red x indicates a problem. If you have a problem with a prerequisite, correctthe issue and then log on again.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
92
5 In the Configuration for Management Server panel, click Standalone andthen click Next.
6 In the next Configuration for Management Server panel, do the following:
■ In the Management Server area, verify the name of the management serverhost computer and its IP address.
■ In the Management Server Data area, specify DataDirectory and DatabasePort, or leave the default values.Data directory specifies where the database resides and Port indicates theport that the database uses.
■ In the Administrator area, specify UserName, Domain, and DomainType,or leave the default values.The default values represent the user account that you used to log on forthis configuration session. The management server uses these values tocreate the initial user in the database.Record the domain, domain type, and password for this user account. Theinitial user is the only user that can log on again to configure clusters andother users.See “About the initial user's role in centralized management configuration” on page 121.
7 Click Finish to begin configuration.
The configuration wizard presents the following progress messages duringconfiguration:
■ Applying configuration. Please wait...
■ Restarting server. This may take some time...
■ A security certificate message, which you should accept.
■ The VCS Management Console is up. Click here to log in.
If the management server does not restart, proceed to step 8.
Otherwise, proceed to step 10.
8 Click Close.
93Installing, upgrading, and uninstalling the management serverConfiguring the management server
9 Manually restart the management server.
Obtain a command prompt and enter the following commands:
net stop cmcweb
net start cmcweb
10 Click the link in the message dialog to log on to the console.
Configuring a newly-installed highly-available management server onWindows
This task enables you to configure the management server to function in themanaged enterprise.
The following services must be running to configure the management server onWindows:
■ The Symantec Product Authentication Service
■ The VCS Management Console web server
Use the Windows Services Manager to ensure that these services are present andrunning.
If at any step you experience a result other than the expected result that isdocumented here, click Back to re-enter information. If you continue to haveproblems, click Cancel to quit the installation and then verify the installationprerequisites.
To configure a newly-installed highly-available management server on Windows
1 Click the shortcut icon of Veritas Cluster Management Console 5.5 on thedesktop. This action starts the VCS Management Console web server andindicates the IP address on the browser window.
You can also enter the following address into your browser to launch themanagement server logon page:
https://webserver_IP_address:14443
2 In the Security Alert dialog box, click Yes to accept the security certificate.
3 Log in to the management server with the system administrator’s account.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
94
4 Ensure that all the browser prerequisites that are listed to the right of thelogon information area have green checks by them..
A red x indicates a problem. If you have a problem with a prerequisite, correctthe issue and then log on again.
5 In the Configuration for Management Server panel, click ClusteredManagement Server and then click Next.
6 In the Management Server panel, do the following:
■ In the Name box, enter a name for the management server.
■ In the SiteName box, enter a default site name for the management serveror leave the default name of Untagged Clusters.The management server sets a cluster's site tag to the default site nameif no other site is specified.
■ In the Database Port box, enter a new database port or leave the defaultport of 14995.
■ Click Next.
7 In the SystemList Configuration panel, do the following:
■ Select the cluster nodes (systems) that can host the management server.To select a system, click a system name in the AvailableSystems list boxand then click the single right-arrow.To select all systems, click the double-right arrows.To reject selected systems in the Selected Systems list box, do the sameusing the left- and double-left-arrows.
■ Click Next.
8 In the VCSMC Server IP Configuration panel, do the following to configurethe virtual IP address for the management server:
■ In the Scope of the NIC options, select either Global or Per System.The Global option indicates that the cluster uses one network interfacecard (NIC) to communicate with the network and therefore themanagement server. The Per System option indicates that each systemuses its own NIC.
■ In each NIC text box, enter the media access control (MAC) address of thespecified NIC.Only one NIC text box is available if you selected the Global option.
■ Enter the virtual IP address and netmask of the management server's NICin the corresponding text boxes.
■ Click Next.
95Installing, upgrading, and uninstalling the management serverConfiguring the management server
9 In the Storage Configuration panel, do the following:
■ In the StorageType options, select eitherLocalStorage or SharedStorage.The LocalStorage option indicates that the management server uses localunshared storage for the management server database. The SharedStorage option indicates that the database resides in shared storage, andthat Veritas Storage Foundation manages that storage.
■ Enter the name of the disk group and volume in the corresponding textboxes.
■ In the Scope of MountPoint options, select either Global or Per System.The Global option indicates that all systems in the cluster use the samemount point. The SharedStorage option indicates that each system usesa different mount point.
■ In each Mount Point text box, enter the required mount point.
■ Click Next.
10 In the Administrator Configuration panel, specify User Name, Domain andDomain Type, or leave the default values.
The default values represent the user account that you used to log on for thisconfiguration session. The management server uses these values to createthe initial user in the database.
Record the domain, domain type, and password for this user account. Theinitial user is the only user that can log on again to configure clusters andother users.
See “About the initial user's role in centralized management configuration” on page 121.
11 Click Finish.
The management server restarts automatically after the configuration issuccessfully completed.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
96
12 If the management server fails to restart, click Close. Bring the managementserver online or offline manually using the following commands:
To stop the management server:
net stop cmcweb
To start the management server:
net start cmcweb
13 After your restart the management server, log on using the virtual IP addressand the initial user account that you specified.
Configuring an upgraded standalone management server on WindowsThis task enables you to configure the management server to function in themanaged enterprise.
The following services must be running to configure the management server onWindows:
■ The Symantec Product Authentication Service
■ The VCS Management Console web server
Use the Windows Services Manager to ensure that these services are present andrunning.
If at any step you experience a result other than the expected result that isdocumented here, click Back to re-enter information. If you continue to haveproblems, click Cancel to quit the installation and then verify the installationprerequisites.
To configure an upgraded standalone management server on Windows
1 Click the shortcut icon of Veritas Cluster Management Console 5.5 on thedesktop. This action starts the VCS Management Console web server andindicates the IP address on the browser window.
You can also enter the following address into your browser to launch themanagement server logon page:
https://webserver_IP_address:14443
2 In the Configure the Management Server panel, log on to the managementserver with the system administrator’s account.
97Installing, upgrading, and uninstalling the management serverConfiguring the management server
3 Ensure that all the browser prerequisites that are listed to the right of thelogon information area have green checks by them..
A red x indicates a problem. If you have a problem with a prerequisite, correctthe issue and then log on again.
4 In the Upgrade for Management Server panel, do one of the following
■ If the upgrade is from a version 5.0 management server, specify DataDirectory and Database Port, or leave the default values.The Data Directory option specifies where the database resides and theDatabase Port option indicates the port that the database uses. Recordthe information in all fields.
■ If the upgrade is from a version 5.1 management server, record theinformation in all fields.You cannot change any configuration values on this page during anupgrade from a version 5.1 to a version 5.5 management server.
5 Click Finish to begin configuration.
The configuration wizard presents the following progress messages duringconfiguration:
■ Applying configuration. Please wait...
■ Stopping server...
■ A Security Alert dialog box, in which you should click Yes.
■ The VCS Management Console is up. Click here to log in.
6 In the message box, click Click here to log in to log on to the console.
7 After you log on to the console, on the Help menu, click About.
In the information panel that appears, verify that the version number is 5.5.The format of the version number is 5.5 (5.5.NNNN.N).
Configuring an upgraded highly-available management server onWindows
This task enables you to configure the management server to function in themanaged enterprise.
The following services must be running to configure the management server onWindows:
■ The Symantec Product Authentication Service
■ The VCS Management Console web server
Installing, upgrading, and uninstalling the management serverConfiguring the management server
98
Use the Windows Services Manager to ensure that these services are present andrunning.
If at any step you experience a result other than the expected result that isdocumented here, click Back to re-enter information. If you continue to haveproblems, click Cancel to quit the installation and then verify the installationprerequisites.
To configure an upgraded highly-available management server on Windows
1 Click the shortcut icon of Veritas Cluster Management Console 5.5 on thedesktop. This action starts the VCS Management Console web server andindicates the IP address on the browser window.
You can also enter the following address into your browser to launch themanagement server logon page:
https://webserver_IP_address:14443
2 In the Configure the Management Server panel, log on to the managementserver with the system administrator’s account.
3 Ensure that all the browser prerequisites that are listed to the right of thelogon information area have green checks by them.. A red x indicates aproblem.
If you have a problem with a prerequisite, correct the issue and then log onagain.
4 In the Upgrade for Management Server panel, do one of the following
■ If the upgrade is from a version 5.0 management server, specify DataDirectory and Database Port, or leave the default values. The DataDirectory option specifies where the database resides and the DatabasePort option indicates the port that the database uses.Record the information in all fields
■ If the upgrade is from a version 5.1 management server, record theinformation in all fields. You cannot change any configuration values onthis page during an upgrade from a version 5.1 to a version 5.5management server.
5 Click Finish to begin configuration.
The configuration wizard presents the following progress messages duringconfiguration:
■ Applying configuration. Please wait...
■ Stopping server...
99Installing, upgrading, and uninstalling the management serverConfiguring the management server
■ A Security Alert dialog box, in which you should click Yes.
■ The VCS Management Console is up. Click here to log in.
6 In the message box, click Click here to log in to log on to the console.
7 After you log on to the console, on the Help menu, click About. In theinformation panel that appears, verify that the version number is 5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
Configuring a newly-installed standalone management server on LinuxThis task enables you to configure the management server to function in themanaged enterprise.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure a newly-installed standalone management server on Linux
1 Start the console with the following command:
■ /opt/VRTScmcm/bin/vxcmcweb start
■ Open a browser window to the indicated URL:
https://[hostname]:14443
2 Log in to the console as a user with administrator privileges on themanagement server.
You will need to enter a username, password, and domain.
You will also need to select an appropriate language.
3 After login, the Configuration for Management Server panel appears.
Read the requirements for your configuration, ensure that they have beenmet before proceeding, and then click Next.
4 In the following Configuration for Management Server screen, provide thefollowing required information:
■ Management Server name, IP address, and Site name
■ Management Server Data directory and database port
■ Administrator user name, domain, domain type
After entering this information, click Finish.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
100
5 Subsequent text boxes display the following messages:
■ Applying configuration. This may take some time.
■ Stopping server...
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
■ VCS Management console is up.
6 Click Click here to log in to log on to the upgraded console.
7 After logon, check the Help>About box to verify that the version number is5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
Configuring a newly-installed highly-available management server onLinux
This task enables you to configure the management server to function in themanaged enterprise.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To configure a newly-installed highly-available management server on Linux
1 Start the console with the following command:
■ /opt/VRTScmcm/bin/vxcmcweb start
■ Open a browser window to the indicated URL:
https://[hostname]:14443
2 Log in to the console as a user with administrator privileges on themanagement server.
You will need to enter a username, password, and domain.
You will also need to select an appropriate language.
3 After login, the Configuration for Management Server panel appears.
Read the requirements for your configuration, ensure that they have beenmet before proceeding, and then click Next.
101Installing, upgrading, and uninstalling the management serverConfiguring the management server
4 In the following Configuration for Management Server screen, provide thefollowing required information:
■ Name of the VCSMC Management Server
■ Site Name
■ Webserver Port
■ Database Port
After providing the information, click Next.
5 Select the systems to host the Management Server service group and clickNext.
6 Configure networking for Management Server by selecting the scope of theNIC (Global or Per System), assigning the NIC, entering the virtual IP address,and entering the Netmask values.
For these values, note the following:
■ For the Scope of the NIC option, select either Global or Per System. TheGlobal option indicates that the cluster uses one network interface card(NIC) to communicate with the network and therefore the managementserver. The Per System option indicates that each system uses its ownNIC.
■ When assigning the NIC, enter the media access control (MAC) addressof the specified NIC. Only one NIC text box is available if you selected theGlobal option.
■ Enter the virtual IP address and netmask of the management server's NICin the corresponding text boxes.
After providing the information, click Next.
7 Configure the storage for the VCS Management Console data.
Select the Storage type (Local or Shared), enter the disk group, the volume,the scope of the MountPoint (Global or Per System), and the Mount point.
For these values, note the following:
■ For the Storage type option, select either Local Storage or Shared Storage.The Local Storage option indicates that the management server uses localunshared storage for the management server database. The Shared Storageoption indicates that the database resides in shared storage, and thatVeritas Storage Foundation manages that storage.
■ Enter the name of the disk group and volume in the corresponding textboxes.
Installing, upgrading, and uninstalling the management serverConfiguring the management server
102
■ For the Scope of MountPoint options, select either Global or Per System.The Global option indicates that all systems in the cluster use the samemount point. The Shared Storage option indicates that each system usesa different mount point.
After providing the information, click Next.
8 Configure admin user login for Management Server by entering the username, domain, and domain type.
After entering the above information click Finish.
9 Read the subsequent text boxes that appear and display the followingmessages:
■ Configuration of management server will take some time, please wait ..
■ Stopping server...
■ Restarting server. Please wait... (NOTE: You are prompted to acceptmanagement server's new SSL certificate when it restarts.)
■ VCS Management console is up.
10 Click Click here to log in to log on to the upgraded console.
11 After logon, check the Help>About box to verify that the version number is5.5.
The format of the version number is 5.5 (5.5.NNNN.N).
12 Proceed to view Management Server, Database, and Users subtabs of theAdministration tab to review the Management Server details.
Configuring a peer management serverConfiguring a peer management server enables you to expand the scope of theVCS Management Console to include remote physical locations. Remote locationsusually have a management server that is local to them. The management serverat the remote location is the one that you configure as a peer to your localmanagement server.
After configuration, both management servers are considered to be peers. Usersthat log on to either management server can administer objects at both sites froma single console using a single logon. User privileges determine the views andtasks available at the peer location, just as they are on the local managementserver.
103Installing, upgrading, and uninstalling the management serverConfiguring a peer management server
Note: Symantec recommends that you configure only one management serverper physical location.
The following procedure enables you to create peer management servers on twostandalone Solaris systems. Perform the following procedure on both the localand the remote management server host.
Note: The following procedure can be used on either Windows, Solaris, or Linuxsystems. Although the procedure can be used on either Windows, Solaris or Linuxsystems, the examples in the procedure are for two standalone Solaris systems.
Creating peer management servers on Solaris systems
1 Log in to the local management server host.
Assume that the host name is local_host.
local_host#galogin root local_host.symantec.com unixpwd
Local_host responds with the following:
Enter password:XXXXX
Connecting to Management Server...
Login successful.
2 Run the gaserver -list command.
The values shown for the management server name, IP address, port (ifnon-standard port is used for the management server), and ID are requiredas input for the command to configure the peer.
gaserver -list
Example output; assume that the management server name is solpeer1.
#Name Address Port ID
solpeer1 NNN.NNN.NNN.NNN 14145 288a052d-81c1-4ce6-a6d1-1ee9f47beff1
Installing, upgrading, and uninstalling the management serverConfiguring a peer management server
104
3 Log on to the remote management server host.
Assume that the host name is remote_host:
remote_host#galogin root remote_host.symantec.com unixpwd
Connecting to Management Server...
Login successful.
4 On the local_host system, copy the cmc_ms.cer file from the remote_hostsystem to a local temporary directory:
local_host# rcp remote_host:/opt/VRTScmcm/data/keys/cmc_ms.cer\
/tmp/cmc_ms.cer
Note: For a clustered management server, this file is found in the /keys
subdirectory of the customer-defined database directory, and not in the/opt/VRTScmcm/data/keys subdirectory.
5 On the remote_host system, copy the cmc_ms.cer file from the local_hostsystem to a temporary directory:
remote_host# rcp local_host:/opt/VRTScmcm/data/keys/cmc_ms.cer\
/tmp/cmc_ms.cer
Note: If you specified a preferred database directory during the managementserver configuration, this file is found in the /keys subdirectory of theuser-defined directory. Use this directory in place of the/opt/VRTScmcm/data/keys subdirectory in this command.
6 On the remote host, run the following command to add the managementserver on the local host as a peer.
Assume that the management server on the local host is named solpeer1.Replace solpeer1_ID and IP_Address with the values that you obtained forsolpeer1 using the gaserver -list command.
remote_host# gaserver -add solpeer1_ID solpeer1 IP_address\
-import /tmp/cmc_ms.cer
The peer Management Server has been added successfully.
105Installing, upgrading, and uninstalling the management serverConfiguring a peer management server
7 On the local host, run the following command to add the management serveron the remote host as a peer.
Assume that the management server on the local host is named solpeer2.Replace solpeer2_ID and IP_Address with the values that you obtained forsolpeer2 using the gaserver -list command.
local_host# gaserver -add solpeer2_ID solpeer2 IP_address\
-import /tmp/cmc_ms.cer
The peer Management Server has been added successfully.
8 On either host, run the following command:
gaserver -list
If the output displays both servers, the peers are connected.
remote_host# gaserver -list
#Name Address Port ID
solpeer1 NNN.NNN.NNN.NNN 14145 7f5c62fd-ff91-4dcc-9220-56cdcdf203ca
solpeer2 NNN.NNN.NNN.NNN 14145 c08d7999-fe91-497b-ab0e-47e4dc924dcb
9 On either host, run the following command to ensure that the systems arerunning
gaserver -state
The command output in the Value column should display RUNNING.
remote_host# gaserver -state
#Server Attribute Scope Value
solpeer1 State Global RUNNING
solpeer2 State Global RUNNING
10 On each management server, run the gaclus -state command to verify thatthe peer's cluster information is also available from the peer. It may takesome minutes for the snapshot sent by each management server to the peeris completely processed, and all the peer's information is accessible fromeach management server.
The command output in the Value column should display RUNNING.
remote_host# gaclus -state
#Cluster Server Attribute Value
Primary solpeer2 State RUNNING
Primary solpeer1 State RUNNING
Installing, upgrading, and uninstalling the management serverConfiguring a peer management server
106
Uninstalling the management serverTo uninstall the management server, you must uninstall the management serveron the management server host system.
Table 4-4 lists the options available for uninstalling the management server.Choose the appropriate option for your configuration.
For information about uninstalling the authentication broker:
See “Uninstalling the authentication broker” on page 117.
Table 4-4 Uninstalling the management server
Uninstall optionsOperating system
Standalone management server uninstall
See “Uninstalling a standalone management server onSolaris” on page 107.
Solaris
Highly-available management server uninstall
See “Uninstalling a highly-available management server onSolaris” on page 109.
Solaris
Standalone management server uninstall
See “Uninstalling a standalone management server onWindows” on page 111.
Windows
Highly-available management server uninstall
See “Uninstalling a highly-available management server onWindows” on page 112.
Windows
Standalone management server uninstall
See “Uninstalling a standalone management server onLinux” on page 113.
Linux
Highly-available management server uninstall
See “Uninstalling a highly-available management server onLinux” on page 115.
Linux
Uninstalling a standalone management server on SolarisUse the uninstallcmc script to remove the VCS Management Console managementserver from a standalone management server host system. The default installeroption is -ssh.
107Installing, upgrading, and uninstalling the management serverUninstalling the management server
Note: If you perform a remote uninstallation and ssh is not enabled, run theinstaller program with the -rsh option. Otherwise, the installer generates an errorduring the uninstallation.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To uninstall the management server from a standalone Solaris system
1 Insert the product disc into the drive on the local system and navigate to thesolaris/sparc/cluster_management_console directory. At the commandprompt, type the following command to run the uninstall script:
./uninstallcmc
The uninstall script eventually presents the following message:
Veritas Cluster Server Management Console (VCSMC) uninstallation:
This program will uninstall VCSMC software from the current system.
If you installed VCSMC in clustered mode, run this program on each
node of VCS cluster where VCSMC was configured.
Press [Return] to continue:
2 Press Enter.
The script presents the following message:
Setup will uninstall the veritas cluster server management console.
Installing, upgrading, and uninstalling the management serverUninstalling the management server
108
3 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The script performs an initial system check of the local system and checksfor installed packages.
4 Enter y or press Enter to confirm that you want to uninstall the VCSManagement Console.
Are you sure you want to uninstall VCSMC? [y,n,q] (y)
The uninstallcmc script eventually presents the following messages:
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Stopping VCSMC: 0% _________________________________________
Stopping VCSMC: 100%
Shutdown completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Uninstalling VCSMC: 0% ____________________________________
Uninstalling VCSMC: 100%
Uninstall completed successfully on all systems
Uninstallation log files, summary file, and response file are
saved at:
/opt/VRTS/install/logs/uninstallcmc-rWafQ6
Uninstalling a highly-available management server on SolarisRun the uninstallcmc script on all cluster nodes to uninstall the managementserver from Solaris cluster nodes. You must uninstall the management serverfrom each Solaris cluster node.
Note: Ensure that you take the CMC_MS service group offline before uninstallinga highly-available Solaris management server. If you do not, the uninstallcmcscript cannot remove the CMC_MS service group from the host cluster.
109Installing, upgrading, and uninstalling the management serverUninstalling the management server
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To uninstall a highly-available management server on Solaris
1 Insert the product disc into the drive on a system in the cluster and thennavigate to the solaris/sparc/cluster_management_console directory. At thecommand prompt, type the following command to run the uninstall program:
./uninstallcmc
The uninstall program eventually presents the following message:
Veritas Cluster Server Management Console (VCSMC) uninstallation:
This program will uninstall VCSMC software from the current system.
If you installed VCSMC in clustered mode, run this program on each
node of VCS cluster where VCSMC was configured.
Press [Return] to continue:
2 Press Enter.
The program presents the following message:
Setup will uninstall the veritas cluster server management console.
3 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The script performs an initial system check of the local system and checksfor installed packages.
Installing, upgrading, and uninstalling the management serverUninstalling the management server
110
4 Enter y to verify that you want to uninstall the management server.
Are you sure you want to uninstall VCSMC? [y,n,q] (y)
The uninstaller script presents the following progress messages:
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Stopping VCSMC: 0% ___________________________________________
Stopping VCSMC: 100%
Shutdown completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Uninstalling VCSMC: 0% _______________________________________
Uninstalling VCSMC: 100%
Uninstall completed successfully on all systems
Uninstallation log files, summary file, and response file are
saved at:/opt/VRTS/install/logs/uninstallcmc random numbers
5 If you configured the clustered management server with the shared storageoption, the uninstallcmc script does not remove the VCS Management Consoledata directory.
To remove the data directory, manually bring the shared storage area ONLINEafter the uninstallation. Delete the data subdirectory to ensure completeremoval of VCS Management Console components.
Uninstalling a standalone management server on WindowsUse the Windows Add or Remove Programs control panel to uninstall themanagement server.
111Installing, upgrading, and uninstalling the management serverUninstalling the management server
To uninstall the management server from a standalone Windows system
1 On the Windows taskbar, click Start > Settings > Control Panel > Add orRemove Programs.
2 In the Add or Remove Programs Control panel, in the Currently installedprograms list, click VCS Management Console 5.5 for Windows.
You may have to scroll through the list to find this entry.
3 On the right side of the selected entry, click Change/Remove.
4 This launches the Symantec Product Installer to uninstall the managementserver. Click Next.
5 In the Computer Selection dialog box, do the following:
■ Select the domain name and node on which to uninstall the managementserver. Click Add.
■ If you want to change the path, click Change.
■ Click Next.
6 In the Validation panel, when the Status column shows Accepted, click Next.
The Validation panel appears while setup validates the computer that is listedin the table. The status column of the table must eventually show Acceptedfor the uninstall to proceed. If you encounter a problem, you can attempt tocorrect the error on the candidate computer and then click Validate Again.
7 Review the summary of the uninstallation process. Click Uninstall. The VCSManagement Console is uninstalled from the selected nodes.
8 Check the uninstallation report. Click Next.
9 Click Finish to close this window.
Uninstalling a highly-available management server on WindowsUse the Windows Add or Remove Programs control panel to uninstall themanagement server.
You must uninstall the management server from each Windows cluster node.
Note: Ensure that you take the CMC_MS service group offline before uninstallinga clustered management server.
Installing, upgrading, and uninstalling the management serverUninstalling the management server
112
To uninstall the management server from clustered Windows systems
1 On the Windows task bar, click Start > Settings > Control Panel > Add orRemove Programs.
2 In the Add or Remove Programs control panel, in the Currently installedprograms list, click VCS Management Console 5.5 for Windows.
You may have to scroll through the list to find this entry.
3 On the right side of the selected entry, click Change/Remove.
4 This launches the Symantec Product Installer to uninstall the managementserver. Click Next.
5 In the Computer Selection dialog box, do the following:
■ Select the domain name and nodes on which to uninstall the managementserver. Click Add.
■ If you want to change the path, click Change.
■ Click Next.
6 In the Validation panel, when the Status column shows Accepted, click Next.
The Validation panel appears while setup validates the computer that is listedin the table. The status column of the table must eventually show Acceptedfor the uninstall to proceed. If you encounter a problem, you can attempt tocorrect the error on the candidate computer and then click Validate Again.
7 Review the summary of the uninstallation process. Click Uninstall. The VCSManagement Console is uninstalled from the selected nodes.
8 Check the uninstallation report, and then click Next.
9 Click Finish to close this window.
Uninstalling a standalone management server on LinuxUse the uninstallcmc script to remove the VCS Management Console managementserver from a standalone management server host system. The default installeroption is -ssh.
Note: If you perform a remote uninstallation and ssh is not enabled, run theinstaller program with the -rsh option. Otherwise, the installer generates an errorduring the uninstallation.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to have
113Installing, upgrading, and uninstalling the management serverUninstalling the management server
problems, type q to quit the installation and then verify the installationprerequisites.
To uninstall the management server from a standalone Linux system
1 Insert the product disc into the drive on the local system and navigate to thelinux/rhel5_x86_64/cluster_management_console directory. At the commandprompt, type the following command to run the uninstall script:
./uninstallcmc
The uninstall script eventually presents the following message:
Veritas Cluster Server Management Console (VCSMC) uninstallation:
This program will uninstall VCSMC software from the current system.
If you installed VCSMC in clustered mode, run this program on each
node of VCS cluster where VCSMC was configured.
Press [Enter] to continue:
2 Press Enter
The script presents the following message:
Setup will uninstall the veritas cluster server management console.
3 Enter y or press Enter to verify that the information up to this point iscorrect.
Is this information correct? [y,n,q] (y)
The script performs an initial system check of the local system and checksfor installed rpms.
4 Enter y or press Enter to confirm that you want to uninstall the VCSManagement Console.
you sure you want to uninstall VCSMC? [y,n,q] (y)
Installing, upgrading, and uninstalling the management serverUninstalling the management server
114
5 The uninstallcmc script eventually presents the following messages:
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Stopping VCSMC: 0% _____________________________________
Stopping VCSMC: 100%
Shutdown completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Uninstalling VCSMC: 0% _________________________________
Uninstalling VCSMC: 100%
Uninstall completed successfully on all systems
Uninstallation log files, summary file, and response file
are saved at:
/opt/VRTS/install/logs/uninstallcmc-UyUmNm
Uninstalling a highly-available management server on LinuxRun the uninstallcmc script on all cluster nodes to uninstall the managementserver from Linux cluster nodes. You must uninstall the management server fromeach Linux cluster node.
Note: Ensure that you take the CMC_MS service group offline before uninstallinga highly-available Linux management server. If you do not, the uninstallcmc scriptcannot remove the CMC_MS service group from the host cluster.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
115Installing, upgrading, and uninstalling the management serverUninstalling the management server
To uninstall a highly-available management server on Linux
1 Insert the product disc into the drive on a system in the cluster and thennavigate to the linux/cluster_management_console directory. At the commandprompt, type the following command to run the uninstall program:
./uninstallcmc
The uninstall program eventually presents the following message:
Veritas Cluster Server Management Console (VCSMC) uninstallation:
This program will uninstall VCSMC software from the current system.
If you installed VCSMC in clustered mode, run this program on each
node of VCS cluster where VCSMC was configured.
Press [Return] to continue:
2 Press Enter.
The program presents the following message:
Setup will uninstall the veritas cluster server management console.
3 Enter y or press Enter to verify that the information up to this point is correct.
Is this information correct? [y,n,q] (y)
The script performs an initial system check of the local system and checksfor installed packages.
Installing, upgrading, and uninstalling the management serverUninstalling the management server
116
4 Enter y to verify that you want to uninstall the management server.
Are you sure you want to uninstall VCSMC? [y,n,q] (y)
The uninstaller script presents the following progress messages:
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Stopping VCSMC: 0% ___________________________________________
Stopping VCSMC: 100%
Shutdown completed successfully on all systems
Veritas Cluster Server Management Console 5.5 Uninstallation Program
Uninstalling VCSMC: 0% _______________________________________
Uninstalling VCSMC: 100%
Uninstall completed successfully on all systems
Uninstallation log files, summary file, and response file are
saved at:/opt/VRTS/install/logs/uninstallcmc random numbers
5 If you configured the clustered management server with the shared storageoption, the uninstallcmc script does not remove the VCS Management Consoledata directory.
To remove the data directory, manually bring the shared storage area ONLINEafter the uninstallation. Delete the data subdirectory to ensure completeremoval of VCS Management Console components.
Uninstalling the authentication brokerAfter uninstalling the console, you can remove the authentication broker fromthe former management server and from the cluster nodes.
Table 4-5 lists the options available for uninstalling the authentication broker.Choose the appropriate option or options for your configuration.
117Installing, upgrading, and uninstalling the management serverUninstalling the authentication broker
Table 4-5 Uninstalling the authentication broker
Uninstall optionsOperating system
Authentication broker uninstall
See “Uninstalling the authentication broker from a Solarissystem” on page 118.
Solaris
Authentication broker uninstall
See “Uninstalling the authentication broker from a Windowssystem” on page 119.
Windows
Authentication broker uninstall
See “Uninstalling the authentication broker from a Linuxsystem” on page 120.
Linux
Uninstalling the authentication broker from a Solaris systemThis task enables you to remove the Symantec Product Authentication Serviceauthentication broker and principal.
If at any step you experience a result other than the expected result that isdocumented here, you can type n to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To remove the authentication broker from a Solaris system
1 Navigate to the /opt/VRTS/install directory.
2 At the command prompt, enter the following command to run theuninstallation program:
./uninstallat
Installing, upgrading, and uninstalling the management serverUninstalling the authentication broker
118
3 Enter the system or systems from which you want to uninstall theauthentication broker and principal.
In the following example, system1, system2, and system3 are the systemnames.
Enter the system names separated by spaces on which to uninstall VxSS:
system1 system2 system3
4 Enteryor press Enter to confirm that you want to uninstall the authenticationbroker.
Are you sure you want to uninstall VxSS? [y,n,q] (y)
The uninstall program stops the authentication service on all systems. It thenuninstalls the authentication broker from each system.
When the uninstall process finishes, the uninstall program presents the pathto the installation log files, summary file, and response file.
Uninstalling the authentication broker from a Windows systemThis task enables you to remove the Symantec Product Authentication Serviceauthentication broker and principal. You must perform this procedure on eachsystem from which you want to uninstall the authentication broker.
To remove the authentication broker from a Windows system
1 Right-click My Computer.
2 In the context menu that appears, click Manage.
3 In the right pane of the Computer Management window, double-click Servicesand Applications.
4 Double-click Services.
5 In the Services list, click Symantec Product Authentication Service andthen stop the service.
6 Open the Windows control panel and double-click AddorRemovePrograms.
7 In the Add or Remove Programs window, in the Currently installed programs:list, click Symantec Product Authentication Service.
8 Click Change/Remove.
119Installing, upgrading, and uninstalling the management serverUninstalling the authentication broker
Uninstalling the authentication broker from a Linux systemThis task enables you to remove the Symantec Product Authentication Serviceauthentication broker and principal.
If at any step you experience a result other than the expected result that isdocumented here, you can typen to re-enter information. If you continue to haveproblems, type q to quit the installation and then verify the installationprerequisites.
To remove the authentication broker from a Linux system
1 Navigate to the /opt/VRTS/install directory.
2 At the command prompt, enter the following command to run theuninstallation program:
./uninstallat
3 Enter the system name from which you want to uninstall the authenticationbroker and principal.
In the following example, system100 is the system name.
Enter the system names separated by spaces on which to uninstall VxSS:
system100
An initial system check for a VxSS installation will be done on that system.
4 After the initial system check, you will be prompted to proceed to uninstallVxSS.
Enter y or press Enter to confirm that you want to uninstall theauthentication broker.
The uninstall program stops the authentication service on the system. It thenuninstalls the authentication broker from the system.
When the uninstall process finishes, the uninstall program presents the pathto the installation log files, summary file, and response file.
Installing, upgrading, and uninstalling the management serverUninstalling the authentication broker
120
Configuring sites andclusters for centralizedmanagement
This chapter includes the following topics:
■ About the initial user's role in centralized management configuration
■ Configuring sites
■ Discovering and configuring one or more clusters for management
■ Reconfiguring clusters that use the cluster connector
■ Enabling and disabling cluster monitoring
■ Removing a cluster from console management
About the initial user's role in centralizedmanagement configuration
The following general steps are necessary to deploy the VCS Management Consoleas a centralized management solution:
■ Install the VCS Management Console packages
■ Configure the management server
■ Configure sites
■ Specify which clusters to manage and configure them for management
■ Run the console to manage clusters
5Chapter
The root user (Solaris, Linux) or any local Administrator (Windows) can log on toinstall the packages and configure the management server.
The management server configuration program allows the currently logged-inroot user or Administrator to do one of the following:
■ Accept the current root or Administrator credentials as the initial usercredentials.
■ Specify the credentials of another root user or Administrator as the initialuser credentials.
Only the initial user can log on to and run the console for the first time aftermanagement server configuration. At this time the intial user can configure sites,specify and configure clusters for management, and add other users.
Configuring sitesYou can configure sites for your clusters before you configure the clusters formanagement. Configuring unpopulated sites involves defining the possible valuesfor the site tag. You can then set each cluster's site tag to one of these values.
Note:You can also configure sites during (instead of before) cluster configuration.However, if you configure sites before you configure clusters, you can select thesites from a menu during cluster configuration. Otherwise, you must type the sitenames into a text box each time you configure a cluster.
Configure a number of sites that best suits the distribution of clusters in yourmanaged enterprise. Sites usually, but are not required to, represent geographicallocations.
The VCS Management Console supports the following cluster types:
■ HAAn HA cluster is a single cluster with the member systems that are located atone site.
■ VCS globalA VCS global cluster is one side of a disaster recovery (DR) configuration oftwo clusters at different sites. The systems at each site belong to theirrespective clusters. That is, each cluster and its systems occupy only one site.
■ Stretch or campusA stretch or a campus cluster is a cluster with nodes that span two sites. Thesystems at each site belong to the same cluster. A stretch or a campus clusteris a short-range DR solution compared to a VCS global cluster configuration.
Configuring sites and clusters for centralized managementConfiguring sites
122
See the VCS User's Guide for more information on cluster topologies.
To create an unpopulated site
1 On the main tab bar, click the Administration tab.
2 On the secondary tab bar, click the Tags tab.
3 In the Configuration menu, click Edit Cluster Sites.
4 In the Edit Cluster Sites wizard, in the Value box, enter a new site name andthen click Add.
This action creates a new value for the sites tag and displays it in the selectionarea in the middle of the wizard panel.
5 Repeat the previous step until you have created as many sites as you needand then click OK.
6 In the final panel, read the message about the results of the task and thenclick OK.
The sites that you created appear in the navigation tree as unpopulated sites.To populate the sites, set the site tag value on your clusters to one of thesesite values.
Discovering and configuring one ormore clusters formanagement
Before you can use the console, you must discover VCS clusters and then configurethem for management. These processes bring the clusters into the managedenterprise.
Discovering and configuring clusters for management involves the followingtasks:
■ Connecting to clusters on the network and specifying which ones you want tomanage
■ Organizing clusters into sites
■ Configuring the type of user authentication that is used by each cluster
■ Adding clusters to the VCS Management Console database
The VCS Management Console enables you to perform all of these tasks using asingle wizard. The wizard that discovers and configures clusters for managementis available on the Administration tab.
Upon first logon to a newly installed console, no clusters are discovered orconfigured, and the Administration tab displays the following message:
123Configuring sites and clusters for centralized managementDiscovering and configuring one or more clusters for management
There are no clusters being managed. To manage VCS clusters
please select "Discover/Add Clusters" from the configuration
menu.
Upon subsequent logons after clusters have been configured, the Administrationtab contains the Configured Clusters table.
Upon any logon to an upgraded console, the Configured Clusters table might showsome deprecated clusters. The deprecated clusters are the clusters that used thecluster connector to connect to earlier versions of the console management server.The version 5.5 managment server does not support the cluster connector.
If deprecated clusters exist in the database, you receive a message about the newconnection requirements in version 5.5 of the console. If you want to continue tomanage these clusters, you must reconfigure them to use a direct connection.
See “Reconfiguring clusters that use the cluster connector” on page 128.
The upgraded management server continues to manage the clusters that used adirect connection with the previous version of the management server.
Note: The Configured Clusters table is not available until clusters have beendiscovered and configured.
The following is a list of the columns and data in the Configured Clusters table:
Contains the cluster nameName
Contains the connection status of the cluster
The possible values are CONNECTED, DISCONNECTED, andSYNCHRONIZING
Cluster State
Contains the name of the cluster system to which the managementserver is connected and the port that the connection uses.
The format is cluster_system_name:port_number
Connected to
Contains the type of user authentication that the cluster uses, eitherVCS (Classic VCS) or Symantec Product Authentication Service(VxAT)
Authentication
Contains the VCS version on the clusterCluster Version
Contains the names or addresses of the systems in the cluster towhich the management server tries to connect.
The ... (edit) option enables you to modify the list.
Connection List
Configuring sites and clusters for centralized managementDiscovering and configuring one or more clusters for management
124
Contains the port that management servers use to connect to thecluster
Port
Note: During discovery, you specify at least one system in each cluster to whichyou want to connect. This specification populates each cluster's connection list,which is shown in the Configured Clusters table. You can click ... (edit) to addsystems (cluster nodes) to the connection list.
To discover and configure one or more clusters for management
1 On the main tab bar, click the Administration tab.
If this logon is not the first one to the console, this action selects theConfigured Clusters tab by default and displays a list of previously-configuredclusters in the Configured Clusters table.
2 In the Configuration menu, click Discover/Add Clusters.
3 In the first panel of the Discover and Add Clusters wizard, read the descriptionof the wizard functions and then click Next.
4 In the Specify where to search for clusters panel, specify the followinginformation:
If you use the Node Names/IP Addresses box, specify at leastone node from each cluster. You can specify either node namesor IP addresses separated by spaces, commas, or newlines.
Node names, IPaddresses, or an IPaddress range for thetarget clusters thatyou want to add
You may leave the default value, specify a new single port, orspecify multiple ports separated by spaces, commas or periods.Input spaces after commas or periods.
You may also specify a port range using a hyphen. If you specifya port range, input spaces on each side of the hyphen.
Port
After you finish specifying options in this panel, click Next.
5 In the Specify access credentials panel, specify the following options:
125Configuring sites and clusters for centralized managementDiscovering and configuring one or more clusters for management
Authentication is the type of security access that the clusteruses.
The following are the available types of security access:
■ Classic VCS: This option enables only the VCS users thatare configured locally on this cluster to log on to the cluster
■ VxAT: Otherwise known as Symantec ProductAuthentication Service, VxAT is the Symantec cross-productuser authentication service. If you select VxAT, you mustalso specify the IP address of the Symantec ProductAuthentication Broker that you want to use
Clusters that are configured in secure mode use VxATauthentication. VxAT users have OS or domain accounts.
You must repeat the discovery process for each type ofauthentication. You must also repeat the process for differentuser credentials because you can specify only one set ofcredentials per run. If the management server cannot log onto the cluster using the specified credentials, it does notdiscover the cluster.
For Classic VCS users, the default VCS user name is admin, andthe default password is password.
Authentication
Enter a user name, password, domain, and domain type of auser account that has administrator privileges on each clusterthat you want to discover. You must specify an adminstratoruser account to connect to the clusters.
ClusterAdministratorCredentials
After you finish specifying options in this panel, click Next.
6 In the Discover Clusters panel, review the summary of the discoveryinformation that you have entered and then click Discover.
7 In the Discovery Results panel, read the status messages that the consolegenerates as it attempts to discover each node. A scrollable progress boxshows detailed results for each cluster. Clicking Cancel at this time closes thewizard but does not stop discovery.
8 When the discovery process finishes, review the list of results.
For successfully discovered clusters, the list contains a success status icon(green checked circle) beside the results for the cluster. For unsuccessfullydiscovered clusters, the list contains a failure status icon (red circle withwhite X) beside the results for the cluster.
9 In the Add Clusters panel, check each cluster in the table that you want toconfigure for management.
Configuring sites and clusters for centralized managementDiscovering and configuring one or more clusters for management
126
10 In the table, in the Type and Site(s) column, specify the following options:
On the drop-down menu in each table row,do one of the following:
■ For single-site clusters, clusters that youintend to make global, or clusters whichare global, click HA Only or GCO.
■ For single clusters with systems that areconfigured at two sites, click Stretch(Campus).
Note: HA Only or GCO does not create aglobal cluster. It specifies only that thecluster's systems are contained in a singlesite.
The cluster type
If the management server installation isnew, the default site is Untagged Clusters.If the installation is an upgrade, the defaultsite remains what is was before the upgrade.
In the text box in each table row, leave thedefault site name or click it to select apreconfigured site from a menu. If thecluster type is Stretch (Campus), you mustspecify two sites in two text boxes.
To create a new site, enter a new site nameinto the text box or boxes.
The site that contains the cluster
Note: Sites usually, but are not requiredto, represent geographical location.
Check this option if you want the currentlylogged on user to have administratorprivileges on all the clusters that you haveselected for configuration.
Make current user a ClusterAdministrator on all selected clusters
127Configuring sites and clusters for centralized managementDiscovering and configuring one or more clusters for management
After you finish specifying options in this panel, click Configure.
11 In the Cluster Configuration Results panel, read the status messages that theconsole generates as it attempts to configure each cluster. Click StopConfiguring to discontinue configuration at any time. When available, clickClose.
Discontinuing configuration does not undo, or unconfigure, any cluster.
When the configuration is not in progress, clicking Back returns you to theDiscover Clusters panel where you can modify the search. Clicking Closecloses the wizard but does not stop configuration.
See “About Symantec Product Authentication Service” on page 20.
See “About user privileges” on page 29.
See “About sites and the enterprise” on page 22.
Reconfiguring clusters that use the cluster connectorThis version of the VCS Management Console connects to clusters directly throughan outbound port on the management server. Previous versions of the consoleconnect to clusters directly or through the cluster connector. The cluster connectoris an optional software component that connects a cluster to the managementserver through an outbound port on the cluster.
Newly added clusters use a direct connection by default. To use this version ofthe console to manage clusters that use the cluster connector, reconfigure theclusters to use a direct connection.
You can reconfigure the clusters that use the cluster connector according to oneof the following scenarios:
In this scenario, you uninstall the clusterconnector on each cluster and then add theclusters to the new management server. Thisscenario does not preserve the cluster'shistorical data.
See the implementation guide for theprevious version of the consoleVCSManagement Console for information aboutuninstalling the cluster connector.
Install a new version 5.5 console on a newsystem
Configuring sites and clusters for centralized managementReconfiguring clusters that use the cluster connector
128
In this scenario, you use the Convert CC toDC wizard in version 5.5 to reconfigure theclusters that use the cluster connector. Youcan reconfigure one or more clusters at atime. This scenario preserves the cluster'shistorical data because the original databaseremains intact.
Upgrade the existing console to version 5.5
The procedure in this section describes the second scenario.
The Convert CC to DC wizard must connect to each cluster that uses the clusterconnector. The wizard first checks the cluster's reconnection list and, if populated,attempts to connect to the first system in the list. If it cannot connect, the wizardattempts to connect to each system in the list until a connection is made.
If no reconnection list is specified, the wizard checks the cluster's system list andattempts to connect to the first system in that list.If it cannot connect, the wizardattempts to connect to each system in the list until a connection is made. In theunlikely event that the system list is unpopulated, the Convert CC to DC wizardignores the cluster.
Note: The Convert CC to DC wizard must be able to resolve the system names onthe reconnection list or system list through DNS. Otherwise, the wizard ignoresthe cluster.
The Convert CC to DC wizard always attempts to connect to a deprecated clusteron port 14141 because the cluster connector uses this port. If a cluster'sreconnection list is populated before reconfiguration, the wizard preserves thelist after reconfiguration. Likewise, if a cluster is in a disabled state beforereconfiguration, the wizard places the cluster back in a disabled state afterreconfiguration.
Reconfiguring clusters that use cluster connector
1 On the main tab bar, click the Administration tab.
2 In the Configured Clusters table, do one of the following:
■ To select individual clusters, check the check box beside the name of eachcluster to be reconfigured
■ To select all clusters, check the check box at the top of the table.
Check only those clusters that have the value Deprecated {Cluster Connector}in the Connected To column. If you are selecting multiple deprecated clusters,select clusters that use the same type of user authentication, either ClassicVCS or VxAT. You must run the Convert CC to DC wizard once for each type
129Configuring sites and clusters for centralized managementReconfiguring clusters that use the cluster connector
of deprecated cluster. This wizard ignores any direct connection clusters thatare checked.
3 On the Configuration menu, click Convert CC to DC.
4 In the Cluster Connector to Direct Connect Conversion wizard, read theimportant introductory information and recommendations and then clickNext.
5 In the Access Credentials for Target Clusters panel, specify the followingoptions:
If the deprecated clusters that you selected use VCS forauthentication, click Classic VCS. If the deprecated clustersuse Symantec Product Authentication service for userauthentication, click VxAT.
If you click VxAT, do one of the following:
■ To authenticate your user credentials on the authenticationbroker that is installed on each cluster: Click Useauthentication broker on each cluster.
■ To authenticate your user credentials on a specificauthentication broker: Click SelectAuthenticationBrokerand then, on the drop-down menu, select the IP address ofthe authentication broker that you want to use.
Authentication
Specify the User Name, Password, Domain, and Domain Typefor a user that has administrator privileges on the selecteddeprecated clusters.
ClusterAdministratorCredentials
After you finish specifying these options, click Next.
6 In the Summary of Target Clusters panel, review the options that you specifiedin the previous panel and then click Finish.
Configuring sites and clusters for centralized managementReconfiguring clusters that use the cluster connector
130
7 In the Cluster Connector to Direct Connect conversion results panel, reviewthe results of the reconfiguration.
If the reconfiguration of a cluster is successful, the results panel shows asuccess status icon (green checked circle) for the cluster. If the reconfigurationis not successful, the results panel shows a failure status icon (red circle withwhite X) for the cluster.
Reconfigurations can fail because of incorrect user credentials. Verify thecredentials that are required for any clusters that could not connect.
A message stating that the confguration of clusters is complete appears afterthe list of results.
8 Click Close.
Enabling and disabling cluster monitoringYou can enable or disable monitoring for specific clusters. Enabling or disablingmonitoring does not affect cluster configuration.
If you disable monitoring for a cluster, the management server disconnects fromthe cluster and takes no further snapshots of it. Disable monitoring only whenyou want to temporarily prevent the management server from connecting to thecluster.
If you subsequently enable monitoring for the cluster, the management serverreconnects to it if all other prerequisites are met.
Note: A previously disabled cluster that is subsequently enabled may take a longtime to reconnect.
The Enable and Disable settings persist across management server restarts.
Cluster monitoring must be enabled before you remove a cluster. If you disablecluster monitoring before you remove a cluster, the removal fails because themanagement server cannot connect to the cluster.
To disable monitoring for a cluster
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Configured Clusters tab.
3 In the Configured Clusters table, do one of the following:
■ To select one or more clusters, check the check box next to each requiredcluster.
131Configuring sites and clusters for centralized managementEnabling and disabling cluster monitoring
■ To select all clusters, check the check box at the top of the table.
4 In the Configuration menu, click Disable Connections.
5 In the Disable Conections to Clusters wizard, read the introductoryinformation and then click Next.
6 In the next panel, review the list of clusters to be disconnected and then clickNext.
Cluster names in this panel are represented as hostname_portnumber
7 In the final panel, read the message about the results of the task and thenclick Close.
To enable monitoring for a cluster
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Configured Clusters tab.
3 In the Configured Clusters table, do one of the following:
■ To select one or more clusters, check the check box next to each requiredcluster.
■ To select all clusters, check the check box at the top of the table.
4 In the Configuration menu, click Enable Connections.
5 In the Enable Connections to Clusters wizard, read the introductoryinformation and then click Next.
6 In the next panel, review the list of clusters to be connected and then clickNext.
Cluster names in this panel are represented as hostname_portnumber
7 In the final panel, read the message about the results of the task and thenclick Close.
Removing a cluster from console managementYou can remove any cluster from console management and prevent reconnections.Removing a cluster erases its corresponding configurational and historical datain the management server database.
Removing a cluster does the following:
■ Reenables monitoring for the cluster (removes it from a list of clusters withdisabled monitoring)
■ Connects to the cluster and unconfigures the connection
Configuring sites and clusters for centralized managementRemoving a cluster from console management
132
■ Purges cluster information from the management server database
Remove a cluster only when you want to permanently remove the cluster fromthe database and unconfigure the connection on the cluster.
Note:You can remove only clusters managed by the management server to whichyou are currently logged in. You cannot remove clusters managed by any peermanagement servers. If you select a peer-managed cluster, that cluster is notincluded in the confirmation list in this task and is not removed.
To remove a cluster from console management
1 On the main tab bar, click the Administration tab.
2 In the Configured Clusters table, do one of the following:
■ To select one or more clusters, check the check box next to each requiredcluster.
■ To select all clusters, check the check box at the top of the table.
3 On the Configuration menu, click Remove Clusters.
4 In the Remove Clusters wizard, review the list of the clusters that you havechosen for removal and then click Next.
5 In the final panel, confirm the removal of each cluster that you selected andthen click Close.
133Configuring sites and clusters for centralized managementRemoving a cluster from console management
Configuring sites and clusters for centralized managementRemoving a cluster from console management
134
Getting started with theVCS Management Console
This chapter includes the following topics:
■ DNS prerequisite for using the console
■ Connecting to the VCS Management Console
■ Logging on to the VCS Management Console
■ Logging out of the VCS Management Console
■ About task availability in the VCS Management Console
■ About the startup page
■ About site summary pages
■ About the main tab bar
■ About the left pane
■ About the Manage tab
■ About the Reports tab
■ About the Event Filter panel
■ About the details pane
■ About the details tab bar and detail links
■ About quick navigation links
■ About the navigation bar on the Manage tab
6Chapter
■ About the navigation bar on tabs other than Manage
■ About the menu bar
■ Setting data filters on detail pages
■ Sorting detail page tables
■ Viewing multiple pages of a table
■ About icon conventions
■ Controlling page updates
■ Determining the currently-connected management server
■ Setting the time zone
■ Setting user preferences
■ About the title bar links
DNS prerequisite for using the consoleEnsure that your network and DNS configuration provide proper name resolution.Otherwise, connection attempts between the management server and the clustercan fail.
Connecting to the VCS Management ConsoleTo use the VCS Management Console, you must first connect to the console froma system that runs a supported web browser.
See “Supported browsers” on page 42.
You can connect to the console in the following ways:
To connect to the VCS Management Console by specifying a URL
◆ In the address box of your Internet browser, enter the URL address of themanagement server:
https://hostname:14443/
Replace Hostname with either the system name or the IP address of themanagement server host system.
Getting started with the VCS Management ConsoleDNS prerequisite for using the console
136
To connect to the VCS Management Console using the Windows Start menu
◆ On Windows management servers, click Start > Programs > Symantec >VeritasClusterManagementConsole>VeritasClusterManagementConsole(login).
Logging on to the VCS Management ConsoleLogging on to the VCS Management Console requires that you provide an username and password, a domain, and a domain type. Any user with administratorprivileges on the management server can add other users.
See “About the initial user's role in centralized management configuration ”on page 121.
See “About Symantec Product Authentication Service” on page 20.
To log on to the VCS Management Console
1 Connect to the VCS Management Console.
The URL is:
https://hostname:14443/
2 In the Select Language drop-down menu, select a language.
3 Enter the user name and password for the initial user or for another useraccount that has been added to the VCS Management Console database.
4 Enter the domain name that is associated with the user account into theDomain box.
If the user account is not a domain account, enter the fully-qualified systemname of the management server.
5 On the Domain Typedrop-down menu, click the domain type of the remotebroker host.
Console versions before 5.5 allowed the choice of Automatic for the DomainType. For version 5.5, you must specify a domain type.
6 Specify the authentication broker.
To use the authentication broker on the management server, specify127.0.0.1:2821. To use another authentication broker, specify it in the formatremote_host_name:port_number.
7 Click Login.
137Getting started with the VCS Management ConsoleLogging on to the VCS Management Console
Logging out of the VCS Management ConsoleLog out of the VCS Management Console to change user accounts or to end yourcluster management session.
To log out of the VCS Management Console
◆ On the title bar of the VCS Management Console, click Logout.
About task availability in the VCS ManagementConsole
Certain VCS Management Console tasks on certain pages might not be availableto you. The available tasks depend upon your user type and privileges. The onlyuser that has access to all tasks and pages is a user with administrator privilegeson the console and on all managed clusters.
Tasks may also be unavailable due to the state of a managed object. For example,you cannot bring a service group online if it is already online.
About the startup pageLogging on to the VCS Management Console displays the startup page. The startuppage is the enterprise summary page, which contains summary data about allmanaged sites and clusters in the managed enterprise.
Figure 6-1 shows the startup page
Getting started with the VCS Management ConsoleLogging out of the VCS Management Console
138
Figure 6-1 Enterprise summary page
Note: The enterprise summary page shows data only if clusters are configured inthe management server database. If no clusters are in the database, a differentpage appears that prompts you to configure clusters.
See “Discovering and configuring one or more clusters for management”on page 123.
The enterprise summary page contains the following panels:
Contains the linked name of each configured site. Click a site nameto display information about the clusters that are being synchronizedat that site.
The synchronization information appears at the bottom of the Sitespanel, below the site name and a status icon. The status icon indicatesthe consolidated state of the clusters in the site. The site name nextto the status icon is a link to the site's status page.
Sites
139Getting started with the VCS Management ConsoleAbout the startup page
Contains a bar graph and numeric totals that indicate service groupsin each available state. Beneath the table title is the total number ofservice groups that are configured across all management servers.Click the table title to navigate to a page that lists all service groupsin the enterprise.
Total Groups
Contains a bar graph and numeric totals that indicate systems ineach available state. Beneath the table title is the total number ofservice groups that are configured across all management servers.Click the table title to navigate to a page that lists all systems in theenterprise.
Total Systems
Contains a set of bar graphs that indicate the failover readiness ofglobal service groups across the managed enterprise. Each bar showsthe number of DR fire drills that ran and resulted in the indicatedDR fire drill state.
See “About HA and DR readiness” on page 309.
See “About fire drills” on page 310.
Group DR Readiness
Contains a set of bar graphs that indicate the failover readiness ofservice groups across the managed enterprise. Each bar shows thenumber of HA fire drills that ran and resulted in the indicated HAfire drill state.
See “About HA and DR readiness” on page 309.
See “About fire drills” on page 310.
Group HAReadiness
Contains the total number of clusters in the managed enterprise thatare in each possible cluster state. Click the table title to navigate toa cluster status page.
Total Clusters
About site summary pagesSite summary pages dislay the same type of information as the enterprise summarypage, but the scale is smaller. The reported data is gathered only from managedobjects in the current site instead of from all managed objects in the enterprise.The current site is the site that is currently selected in the navigation tree orwhich appears at the end of the navigation bar.
Figure 6-2 shows a site summary page.
Getting started with the VCS Management ConsoleAbout site summary pages
140
Figure 6-2 Site summary page
The site summary page contains the following panels:
Contains the name of the current site.
Cluster synchronization information appears at the bottom of theSites panel, below the site name and a status icon. The status iconindicates the consolidated state of the clusters in the site. The sitename next to the status icon is a link to the site's status page.
Sites
Contains a bar graph and numeric totals that indicate service groupsin each available state. Beneath the table title is the total number ofservice groups that are configured in the site. Click the table title tonavigate to a page that lists all service groups in the site.
Total Groups
Contains a bar graph and numeric totals that indicate systems ineach available state. Beneath the table title is the total number ofservice groups that are configured across all management servers.Click the table title to navigate to a page that lists all systems in thesite.
Total Systems
141Getting started with the VCS Management ConsoleAbout site summary pages
Contains a set of bar graphs that indicate the failover readiness ofglobal service groups in the site. Each bar shows the number of DRfire drills that ran and resulted in the indicated DR fire drill state.
See “About HA and DR readiness” on page 309.
See “About fire drills” on page 310.
Group DR Readiness
Contains a set of bar graphs that indicate the failover readiness ofservice groups in the site. Each bar shows the number of HA firedrills that ran and resulted in the indicated HA fire drill state.
See “About HA and DR readiness” on page 309.
See “About fire drills” on page 310.
Group HAReadiness
Contains the total number of clusters in the site that are in eachpossible cluster state. Click the table title to navigate to a clusterstatus page.
Total Clusters
About the main tab barThe main tab bar contains a tab for each category of operations available in theVCS Management Console. Each tab contains one or more pages of statusinformation and controls required to administer the corresponding category ofoperations. The following are the tabs on the main tab bar and the operationalcategories that they represent:
For object configuration and manipulationManage(management)
For event monitoring, policies, and filtersNotification
For historical data reportingReports
For user administration, management server administration, tagdefinition, and cluster configuration
Administration
For conducting and saving character-based or tag-based searches onmanagement server and cluster objects
Search
Figure 6-3 shows the tabs on the main tab bar.
Figure 6-3 Main tab bar
Getting started with the VCS Management ConsoleAbout the main tab bar
142
Clicking a tab for the first time after logon takes you to the default page for thattab. Clicking a tab at any other time takes you to the most recently visited pageon that tab. The main tab bar always contains the same tabs.
About the left paneThe left pane of the console is reserved for navigation controls or filtering controls.The left pane is not available on every tab.
On the Manage tab and Reports tab, the left pane contains a navigation tree. Thesenavigation trees enable you to navigate among cluster objects or reports,respectively.
If you select Enterprise or a site in the navigation tree, the left pane can show anEvent Filters panel. This panel enables you to filter event alerts by their severity.
To show the alerts panel
1 On the main tab bar, click Manage.
2 On the Operations menu, click Show/Hide Alerts.
This action displays or hides the alters panel.
About the Manage tabIn the navigation tree on the Manage tab, the root is always labeled Enterprise.The tree contains only one Enterprise root. The Enterprise root represents yourentire company or organization. It contains the child branches that represent allsites, clusters, systems, and service groups that are configured for centralizedmanagement.
The next two branches below Enterprise are labeled with the names of a site anda cluster, respectively, that are configured in the enterprise. These site and clusterbranches may also have sibling branches (branches at the same level) displayedfurther down the tree. Each site branch contains one or more child branches thatrepresent the clusters that are members of that site.
In the navigation tree on the Manage tab, the Enterprise and site branches functiononly to organize objects. They do not represent real physical or software objectsin the enterprise.
See “About sites and the enterprise” on page 22.
The navigation tree on the Manage tab has two subtabs: Service Groups andSystems. If you click the Service Groups tab, expanding a cluster branch showsthe service groups that are members of that cluster. If you click the Systems tab,expanding a cluster branch shows the systems that are members of that cluster.
143Getting started with the VCS Management ConsoleAbout the left pane
Figure 6-4 shows the navigation tree on the Manage tab.
Figure 6-4 The navigation tree expanded with Service Groups tab selected
Getting started with the VCS Management ConsoleAbout the Manage tab
144
Figure 6-5 The navigation tree expanded with Systems tab selected
The details pane is located to the right of the navigation tree. This pane containsdetails about the object that is selected in the navigation tree or one of its relatedobjects. The Service Groups and Systems tabs filter the details pane informationwhen you select a cluster. The following table summarizes navigation tree filteringof details pane information.
145Getting started with the VCS Management ConsoleAbout the Manage tab
To dipsplay this in the details paneDo this in the navigation tree
Details about the selected site or cluster andits member service groups or details aboutthe selected service group
Click the Service Groups tab and then clicka site, cluster, or service group
Details about the selected site or cluster andits member systems or details about theselected system
Click the Systems tab and then click a site,cluster, or system
Figure 6-6 Service group details with cluster selected in navigation tree
Getting started with the VCS Management ConsoleAbout the Manage tab
146
Figure 6-7 System details with site selected in navigation tree
Another feature of the Manage tab navigation tree is the context (right-click)menu. The most commonly-used tasks for cluster object management are availableby right-clicking a branch in the navigation tree.
To search the navigation tree
1 Click the text box that contains the default text --SEARCH--.
2 Enter the character string for which you want to search.
3 Click the magnifying glass (lens) icon.
This action highlights the first occurrence of the string in an object name inthe navigation tree, if the string exists. Click the up or down arrows to navigateto other objects that match the string.
About the Reports tabA navigation tree also appears on the Reports tab, which is on the main tab bar.In the navigation tree on the Reports tab, the root is labeled All Reports. All Reportscontains up to two levels of branches: the first level represents the available report
147Getting started with the VCS Management ConsoleAbout the Reports tab
types, and the second level, if present, represents the jobs that have been createdfor that report type.
Figure 6-8 Navigation tree on the Reports tab showing one report job
In the Reports tab navigation tree, clicking + (plus) expands a report type branch.This enables you to view any report jobs that have been created for it. Clicking -(minus) collapses, or hides, the report jobs. You can view detail pages for a reporttype or a report job by clicking the type or job in the navigation tree.
Another feature of the Reports tab navigation tree is the context (right-click)menu. The most commonly-used tasks for report management are available byright-clicking a branch in the navigation tree.
About the Event Filter panelThe Event Filter panel is available on the Logs details tab on theNotification maintab. It appears in the left pane in place of the navigation tree.
Getting started with the VCS Management ConsoleAbout the Event Filter panel
148
The Event Filter panel enables you to specify filter criteria for the events that youwant to view in the notification log.
Figure 6-9 shows this panel on the Logs details tab.
Figure 6-9 Event Filter panel
You can collapse the Event Filter panel by clicking the up-arrows in the top rightcorner of the panel. Collapsing the panel hides the panel contents, leaving onlythe title visible. The up-arrows change to down-arrows when the panel is collapsed.Click the down-arrows to re-expand the panel.
You can also collapse and expand the entire left pane by clicking the arrow iconon its right border. The arrow points to the left when the panel is expanded andto the right when the panel is collapsed.
About the details paneThe details pane is located beside the left pane in the VCS Management Console,on the right side. The purpose of the details pane is to display detailed informationabout a currently selected management server or cluster object. For example, onthe Manage tab, the details pane contains configurational and status informationabout a selected cluster object or one of its related objects.
In the startup page, the Enterprise root object is the default selection in thenavigation tree. Therefore, the details pane contains detail information about all
149Getting started with the VCS Management ConsoleAbout the details pane
objects in the managed enterprise because they are all related to the Enterpriseroot object.
Figure 6-10 shows the details pane with a cluster selected in the navigation tree.
Figure 6-10 The details pane with cluster selected
About the details tab bar and detail linksThe details tab bar is a row of tabs that displays in the details pane. Differentobjects have different tabbed pages of details.
Clicking tabs in the details tab bar takes you to different categories of details aboutthe currently selected object or its related objects. Clicking these tabs may alsomove you up or down the current branch in the navigation tree. However, thesetabs keep you in the same branch of related objects; they do not switch you toanother branch.
A tab on the details tab bar may or may not contain an additional row of detaillinks at the top of the tab. Like the tabs, these links take you to pages that containsubcategories of detail about the currently selected object or one of its relatedobjects. Clicking detail links may also move you up or down the current branch
Getting started with the VCS Management ConsoleAbout the details tab bar and detail links
150
in the navigation tree. However, these links keep you in the same branch of relatedobjects; they do not switch you to another branch.
The details tab bar and the detail links enable you to quickly adjust the level andtype of object detail that you view. . Each tab and each detail link always takesyou to more detail about the object currently selected in the navigation tree orone of its related objects.
Figure 6-11 Details tab bar for clusters: Status tab and detail links
About quick navigation linksMany pages in the details pane contain linked (underlined and possibly in adifferent color) object names in panels and tables. These links take you directlyto detail pages for the linked object.
Unlike detail links under a tab on the details tab bar, these links often do switchyou to another branch of the navigation tree. That is, you are not always kept inthe same branch of related objects if you click a quick navigation link.
About the navigation bar on the Manage tabThe navigation bar is located along the top of the details pane.
For pages on the Manage tab, it indicates the hierarchical object relationships, orlineage, of one of the following:
■ The object that is currently selected in the navigation tree
■ An object that is related to the object currently selected in the navigation tree,but which is not represented in the tree
Figure 6-12 shows how the navigation bar mirrors the selection in the navigationtree.
151Getting started with the VCS Management ConsoleAbout quick navigation links
Figure 6-12 The navigation bar in page context
Selecting tabs, detail links, or quick navigation links in the details pane can takeyou to detail pages about many different objects. However, attributes, resources,and resource types are not represented in the navigation tree.
To view all the object relationships for a selected object, consult the navigationbar. The navigation bar always contains the complete lineage of the object thatyou view in the details pane. This includes lower-level objects that are not displayedin the navigation tree.
For example, on a resource details page, the navigation bar contains the iconsequence Enterprise >> Site >> Cluster >> Service Group >> Resource and endswith the name of the resource.
In the startup page, the navigation bar displays Enterprise until you select anobject.
The following are a few quick tips about using the navigation bar on the Managetab:
■ Clicking Enterprise on the navigation bar returns you to the startup page.
■ Clicking any other linked object in the navigation tree or in the details paneupdates the navigation bar with the lineage of the newly-selected object.
■ Clicking object links in the navigation bar moves you up the current branchin the navigation tree.
About the navigation bar on tabs other than ManageOn tabs other thanManage and Reports, the navigation bar offers one link,Enterprise, which always takes you back to the startup page. On the reports tab,it contains links to a report type or report job.
Getting started with the VCS Management ConsoleAbout the navigation bar on tabs other than Manage
152
About the menu barThe menu bar in the details pane contains the menus that list specific tasks. Youcan perform these tasks on objects in the VCS Management Console. The menubar is located beneath the details tab bar and beneath any detail links that mightdisplay (not every page has detail links).
Figure 6-13 shows the menu bar as it appears on the manage tab. (In this example,the VCS simulator is also installed on the management server.)
Figure 6-13 The menu bar on the startup page
The name of a menu indicates the function of the tasks that it contains. Selectinga menu item performs an action directly or starts a task wizard. A wizard is asequence of panels on the screen that help you to perform a task. Almost all tasksin the VCS Management Console are perfomed by wizards. Many wizards have asequence of only two panels, one that presents options and one that shows theVCS commands that were submitted to VCS. The final panel of a wizard alwaysdisplays the results of the VCS commands.
For pages that show details for a specific object, some menu items might begrayed-out.
Grayed-out tasks menu items can indicate the following:
■ You do not have a sufficient privileges on the current object or objects toperform the tasks
■ The object is in a state that prevents the console from carrying out the task
For example, you cannot bring a cluster online if it is already in an ONLINE state.
Setting data filters on detail pagesDetail pages that contain tables also contain a filter panel. A filter panel enablesyou to view only those objects that meet the criteria that you specify.
You specify the filter criteria using controls such as check boxes or drop-downmenus. If you want to perform a task on only certain objects, you can first filterthe table for those objects and then select the task. You can apply the filter orreset the filter to its default value at any time.
153Getting started with the VCS Management ConsoleAbout the menu bar
Note: A filter panel contains only those filters and settings that are appropriatefor the objects that are listed in the table that it filters.
The following table lists the available filters.
DescriptionFilter
Shows the objects with the specified value for theConsolidatedState attribute.
State
Shows the systems with the specified value for the Platformattribute.
Platform (systems tablesonly)
Shows the objects with the specified value for the Region tag.This drop-down menu is populated with the currentlyconfigured values for the Region tag and the value All Regions.The default setting for this filter is All Regions.
Region
Shows the objects with the specified value for the Departmenttag. This drop-down menu is populated with the currentlyconfigured values for the Department tag and the value AllDepartments. The default setting for this filter is AllDepartments.
Department
Shows the objects with the specified value for the LOB tag.This drop-down menu is populated with the currentlyconfigured values for the LOB tag and the value All Lines ofBusiness. The default setting for this filter is All Lines ofBusiness.
Line of Business
Shows the objects that returned the specified HA fire drillstatus during their last run HA fire drill. This drop-down menuis populated with the possible HA fire drill states and thevalueAll HA Readiness States. The default setting for thisfilter is All HA Readiness States.
See “Viewing readiness” on page 318.
HA
Shows the objects that returned the specified DR fire drillstatus during their last run DR fire drill. This drop-down menuis populated with the possible DR fire drill states and thevalueAll DR Readiness States. The default setting for thisfilter is All DR Readiness States.
See “Viewing readiness” on page 318.
DR
Getting started with the VCS Management ConsoleSetting data filters on detail pages
154
Users most commonly filter objects by operational state. The following tableshows the possible settings for the State filter, which is listed in the first row ofthe preceding table.
Shows responsive, functioning objectsCONNECTED orONLINE
Shows unresponsive, non-functioning objectsDISCONNECTED orOFFLINE
Shows objects coming onlineSYNCHRONIZING
Shows objects (clusters or service groups) in which some of themember objects have a fault
PARTIAL
Shows objects that have a faultFAULTED
Shows objects in an undetermined, consolidated stateUNKNOWN
See “About object states and consolidated states” on page 22.
Figure 6-14 Service groups filter panel showing criteria selections
To apply a filter to objects on a detail page
1 Select an object using the navigation tree, the tabs or detail links on the detailstab bar, or any quick navigation links in the details pane.
2 In the details pane, in the object filter panel, specify the filter criteria usingthe check boxes and drop-down lists.
3 Click Apply.
To reset a filter to its default criteria settings
1 Select an object using the navigation tree, the tabs or detail links on the detailstab bar, or any quick navigation links in the details pane.
2 In the details pane, in the object filter panel, click Reset.
Sorting detail page tablesMost detail pages contain data tables. An arrow next to a column name denotesthe column by which the table data is currently sorted.
155Getting started with the VCS Management ConsoleSorting detail page tables
To sort rows in a table by data in a column
1 Select an object using the navigation tree, the tabs or detail links on the detailstab bar, or any quick navigation links in the details pane.
2 In the details pane, in the object detail table, locate a sortable column youwant to use to sort the data.
3 Click the column heading.
The order of the list is ascending in order of the values in that column. Anarrow that points up displays in that column heading.
4 If you want, click the column heading a second time.
The order of the list is descending in order of the values in that colum. Anarrow that points down displays in that column heading.
Viewing multiple pages of a tableTables in the details pane may contain multiple pages. You can view subsequentpages of a table using the go-to-page bar.
To access pages in a table
◆ In a table with multiple pages, locate the go-to-page bar underneath the table.
Click arrows or numerals on the go-to-page bar to move forward and backwardthrough the table pages.
About icon conventionsThe VCS Management Console uses icons to represent the managed enterprise,sites, and cluster objects. You can see these icons in the navigation tree and onthe navigation bar.
See “About the Manage tab” on page 143.
See “About the navigation bar on the Manage tab” on page 151.
Status indicators are applied to the basic object icons to create status icons. Statusicons indicate both the type and the state of the object.
The status indicators are the following:
■ Color icons indicate the objects that are in a healthy, running condition.
■ Gray icons indicate the objects that are offline.
■ Icons with orange lines indicate the objects that are partially online with onlysome member (contained) objects online.
Getting started with the VCS Management ConsoleViewing multiple pages of a table
156
■ Icons with red lines indicate faulted objects.
■ Icons with a question mark indicate the objects whose status is unknown.
■ Icons with a red lock indicate objects in a frozen state.
■ Icons with a red circle and white cross bar indicate objects in an autodisabledstate.
Controlling page updatesAs you use the VCS Management Console, the status of clusters, systems, andapplications changes. Devices go online and offline, alerts are generated, and datafluctuates. You can control when and how the information in your console displayupdates (refreshes) to reflect the latest data.
An update icon near the top right-hand corner of the VCS Management Consoleindicates the current update mode and the state of the information displayed inthe console. Clicking the update icon enables you to set the update mode.
The following are the update mode settings:
DescriptionUpdate (refresh) mode
Provides no indication of available updates(disables update notification). Use therefresh function in your web browser toupdate the console information.
Disabled
Indicates that this setting only notifies youwhen data updates are available. The NotifyOnly setting does not perform the update.This is the default setting. When dataupdates are available, this icon changes tothe Page is Stale icon. You must then clickPage is Stale to perform the update.
Notify Only
Indicates that data is no longer current andthat updates are available. This is the defaultsetting. Click this icon to update the consoleinformation.
Page is Stale
Automatically updates the consoleinformation when it is no longer current.
Auto Refresh
157Getting started with the VCS Management ConsoleControlling page updates
To change the refresh mode
◆ Click the update icon to cycle among the refresh modes. You can select anymode except Page is Stale.
Determining the currently-connected managementserver
You can determine the management server to which your console is connectedby viewing the bottom edge of the console window.
Setting the time zoneThis task enables you to set the time zone for the console.
To set the time zone
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click Enterprise.
4 On the Settings menu, click Time Zone.
5 In the dialog box, on the Time Zone menu, select a time zone.
6 Click OK.
Setting user preferencesThis task enables you to set display preferences for the currently logged on user.
To set user preferences
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 On theSettings menu, click User Preferences.
4 In the Table Rows Preference dialog box, on the Table Rows Per Pagedrop-down menu, select a number of rows to display at one time in a table.
5 Click OK.
Getting started with the VCS Management ConsoleDetermining the currently-connected management server
158
About the title bar linksThe yellow title bar at the top of the console contains the several links. Thefollowing table shows each link and describes its function.
FunctionTitle bar link
Opens the VCS Management Console online help.Help
Opens the Veritas Operations Services web page in a newbrowser window.
Veritas Operations Services
Opens a window with various links to Symantecdocumentation, services, and support
References
Opens an e-mail form that is addressed to the VCSManagement Console feedback team.
Feedback
Opens a window that contains copyright, legal, and andversion information.
About
Logs you off of the console.Logout
159Getting started with the VCS Management ConsoleAbout the title bar links
Getting started with the VCS Management ConsoleAbout the title bar links
160
Administering users anduser privileges
This chapter includes the following topics:
■ Viewing user status
■ About user listing tables
■ Administering users
Viewing user statusThe user pages on the Administration tab enable you to manage users and userprivileges. The console displays a table of all registered users, user groups, andtheir privileges.
The initial user is specified during management server configuration and is thefirst user that you can view in a user table. The initial user adds other users tothe management server database.
See “About user privileges” on page 29.
See “About the initial user's role in centralized management configuration ”on page 121.
User status tables are available when you view any of the following:
■ All users in the enterprise
■ All users in a site
■ All users with privileges on a cluster
You can manage users' privileges on service groups through the user managementpages (Users tab) of the parent cluster.
7Chapter
To view all users in the enterprise (Manage tab)
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch.
4 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To view all users in the enterprise (Administration tab)
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To view all users in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the appropriate site.
5 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users at Site table. This table listsall users that are configured in the selected site.
To view all users with privileges on a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the required cluster.
5 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users table. This table lists all usersthat are configured with privileges on the selected cluster.
About user listing tablesThe following is a list of all the columns that you might see in a user status table.Columns vary depending upon whether you select the enterprise, a site, or a
Administering users and user privilegesAbout user listing tables
162
cluster. You can select these objects in either the navigation tree or the navigationbar.
Enables you to select a user as a target for a user managementtask
Check box(This columnhas a check box in theheading that selects allusers)
Graphic that indicates that you are viewing information about auser
User icon (This columnhas no heading)
Indicates the user name string using its full internalrepresentation in the management server database
User or User Name
Indicates the type or method of authentication that is configuredfor this user.
For users with privileges on the management server or clustersconfigured in the secure mode, the Symantec ProductAuthentication Service authenticates the user. The value OS Userindicates this type of authentication.
VCS authenticates users with privileges on a cluster that is notconfigured in a secure mode. The value Classic VCS indicates thistype of authentication.
More than one value is possible.
Type
Indicates the privileges that the user has on the VCS ManagementConsole management server
VCSMC privileges
Indicates the privileges that the user has on the cluster. The valuecan be one of Cluster Administrator, Cluster Operator, or ClusterGuest.
Privileges (Thiscolumn displays intables that show onlyusers with privilegeson clusters)
Administering usersUser administration involves the creation, modification, and deletion of usersand user privileges. A user can have administrator or guest privileges on the VCSManagement Console management server. A management server administratorhas reporting privileges by default, but a guest must be explicitly given reportingprivileges. A user can have administrator, operator, or guest privileges on anycluster.
See “About user privileges” on page 29.
Tasks for managing users are available when you view the following:
163Administering users and user privilegesAdministering users
■ All users in the enterprise
■ All users in a site
■ All users with privileges on a cluster
Adding users to the management serverThe initial user is the first user to have privileges on the management server. Theinitial user is also the first user that can add other users and grant them privilegeson the management server.
Note: The UNIX root user or the Windows Administrator on the managementserver system implicitly have management server administrator privileges in theconsole.
To add a user after management server configuration
1 On the main tab bar, click the Manage tab
2 In the navigation tree, click the Service Groups tab.
3 On the details tab bar, click the Users tab.
4 In the Configuration menu, click Add User.
5 In the Add User wizard, specify the following information:
This is the user's operating system user nameThe user name
This is the name of the user's operating system domainThe domain name
The is the type of operating system domain to which theuser belongs. Possible values are Windows, nis, nisplus,unixpwd, LDAP, and VPAM.
The domain type
The possible values are Administrator (maximumprivileges including reporting), Guest (read-onlyprivileges), and Guest with reporting (read-only privilegesbut includes reporting).
The privileges that theuser is to have on themanagement server.
Check Represents a User Group if the user namedesignates an operating system user group.
Whether or not the user isa group.
Administering users and user privilegesAdministering users
164
6 Click OK.
7 In the final panel, read the message about the results of the task and thenclick Finish.
If successful, the new user appears in the Users in Enterprise table.
Modifying management server privileges for selected usersThis task enables you to change the privileges that one or more users have on amanagement server. These privileges do not affect any privileges that a user mighthave on any clusters.
This task is available when you view all users in the enterprise. The page thatcontains this task is available on the Users details tab on both the Administrationand theManage main tabs. The page is duplicated so that users with guest privileges(who cannot view the Administration tab) can view users.
See “Viewing user status” on page 161.
To view all users in the enterprise (Manage tab)
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 In the navigation tree or on the navigation bar, click Enterprise.
4 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To modify user privileges on the connected management server
1 In the Users in Enterprise table, do one of the following:
■ To select one or more users, check the check box next to each requireduser.
■ To select all users, check the check box at the top of the table.
The privilege modification wizard that is described in subsequent stepsexcludes users of the clusters that use classic VCS authentication, even if youselect them.
2 In the Configuration menu, click Modify VCSMC Privileges.
165Administering users and user privilegesAdministering users
3 In the Mofidy VCSMC User Privileges wizard, specify the following options:
Use the drop-down menu to specify themanagement server on which you wantto modify the selected users’ privileges.The management server must be onlineand communicating for it to be availablein this option.
Select the online management server
Click Administrator or Guest to specifythe privilege for the selected users on thespecified management server.
Select Role to Assign
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Finish.
Granting and revoking reporting privilegesThis task enables you to grant or revoke reporting privileges for one or moreusers. Reporting privileges are exclusive to users with privileges on themanagement server. Reporting privileges include permissions to create, delete,and edit report jobs, run existing report jobs, and view existing report outputs.Users with administrator privileges on the management server have reportingprivileges by default.
This task is available when you view all users in the enterprise.
To view all users in the enterprise (Manage tab)
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click Enterprise.
4 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To grant or revoke reporting privileges
1 In the Users in Enterprise table, do one of the following:
■ To select one or more users, check the check box next to each requireduser.
Administering users and user privilegesAdministering users
166
■ To select all users, check the check box at the top of the table.
2 In the Configuration menu, click Modify Report Privileges.
3 In the Modify Reporting Privileges wizard, in the users table, do the following:
■ Check a check box to grant reporting privileges to the corresponding user.
■ Clear a check box to revoke reporting privileges from the correspondinguserYou cannot revoke reporting privileges from a management serveradministrator to which they have been previously granted. The check boxfor a such a user is checked, grayed-out, and unavailable.
4 After you finish granting and revoking reporting privileges, click OK.
5 In the final panel, read the message about the results of the task and thenclick Finish.
Deleting selected users from the management serverThis task enables you to delete one or more users and their associated privilegesfrom the management server database. You may also optionally delete a user fromany cluster. However, you cannot delete the initial user, which is the first user tohave administrator privileges on the management server.
This task is available when you view all users in the enterprise.
To view all users in the enterprise (Manage tab)
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click Enterprise.
4 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To delete users
1 In the Users in Enterprise table, do one of the following:
■ To select one or more users, check the check box next to each requireduser.
■ To select all users, check the check box at the top of the table.
2 In the Configuration task menu, click Delete Users.
3 If you want to delete any users from any clusters, check Deleteselectedusersfrom clusters also.
167Administering users and user privilegesAdministering users
4 Click OK to confirm that you want to delete the selected users.
5 In the final panel, read the message about the results of the task and thenclick Close.
Adding selected users to selected clustersThis task enables you to do the following:
■ Add one or more users with management server privileges to one or moreclusters.This task enables you to grant cluster privileges to users that already haveprivileges on the management server.
■ Add one or more users with cluster privileges to other clusters.The users must currently have privileges on the clusters that use SymantecProduct Authentication Service (VxAT) for user authentication. The clustersto which you add these users must also use VxAT authentication. You cannotadd users of the clusters that use VCS for authentication (Classic VCS) to otherclusters.
This task is available when you view all users in the enterprise, all users in a site,or all users in a cluster. This procedure describes the task at the enterprise level.
To view all users in the enterprise (Manage tab)
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click Enterprise.
4 On the details tab bar, click the Users tab.
On the Users tab, this action displays the Users in Enterprise table. This tablelists all users that are configured across all management servers.
To add users to selected clusters
1 In the Users in Enterprise table, do one of the following:
■ To select one or more users, check the check box next to each requiredcluster.
■ To select all users, check the check box at the top of the table.
2 In the Configuration task menu, click Modify Cluster Privileges.
3 In the Assign Privileges wizard, verify the list of selected users and then clickNext.
The list excludes users of the clusters that use classic VCS authentication,even if you select them.
Administering users and user privilegesAdministering users
168
4 In the Assign Privileges panel, click Cluster Administrator or ClusterOperator.
5 Click Finish.
6 In the final panel, read the message about the results of the task and thenclick Close.
Adding selected OS users to one clusterThis task enables you to assign privileges on a cluster to one or more OS users.The OS users may already have privileges on other clusters or on the same cluster.
This task is available when you view all users in a cluster.
Note: Users that are added through this task are not removed from the cluster ifthe cluster is removed from the management server.
To view all users in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 In the navigation tree, click Enterprise
4 Expand the appropriate site and click the required cluster.
5 On the details tab bar, click Users.
This action displays a Users table that contains all users that have privilegeson the cluster.
169Administering users and user privilegesAdministering users
To add selected OS users to a cluster
1 On the Configuration menu, click Add User.
2 In the Assign User Privileges wizard, select one of the following options:
This option enables you to add one or more existing OSuser with privileges on the management server to thecluster.
Before you select this option, check the users that youwant to add to the cluster.
Select an existing user
This option enables you to add a user to a cluster that isnot configured in secure mode. VCS clusters that are notconfigured in secure mode use VCS to authenticate users.Once configured, a classic VCS user has privileges only onthe cluster to which they are added.
If you select this option, specify a user name and passwordfor the classic VCS user and confirm the password .
Add a new classic VCSuser
This option enables you to add a new OS user to both themanagement server and to a secure-mode cluster. Clustersthat are configured in secure mode use a VxATauthentication broker to authenticate users.
If you select this option, enter the fully-qualified username in the following format:
user@domain@domain_type
Add a new VCSMC user
3 Click Next.
4 In the Assign User Privileges panel, check the privileges to assign to the newuser.
You can specify administrator or operator privileges on the cluster. You canalso specify administrator or operator privileges on one or more of thecluster's service groups. If you check Administrator in the cluster privileges,you do not need to specify any other privileges.
5 Click Finish.
6 In the Results panel, review the results of the task and then click Close.
Adding selected users to groupsThis task enables you to add one or more users to a service group.
Administering users and user privilegesAdministering users
170
To add users to a service group
1 In the navigation tree, click a service group.
2 In the Configuration menu, click Modify Privileges.
3 On the Select User to modify privileges panel, select a user.
4 On the User panel, assign privileges on the cluster, or select groups.
171Administering users and user privilegesAdministering users
Administering users and user privilegesAdministering users
172
Administering basic highavailability clusterconfigurations
This chapter includes the following topics:
■ Administering tags
■ Administering sites
■ Administering clusters
■ Administering service groups
■ Administering systems
■ Administering resources
■ Administering resource types
■ Viewing logs
■ Searching
Administering tagsTags are special attributes with user-defined values. You apply tags to clustersand service groups so that you can easily identify and organize them for filteredsearches and batch operations. The tag administration tasks in theVCSManagement Console enable you to add, delete, or edit tag values.
Each tag has a list of values that the tag can assume. You can add values to ordelete values from this list..
8Chapter
After you add or delete possible tag values, you can set the value of the tag on aservice group or cluster.You set the value for a tag when you edit the tags forclusters or service groups. (This action is also called applying a tag to a cluster.)You can apply tags to the clusters or the service groups that are configured in thesame management server to which you are currently logged-in.
See “Editing tags on selected clusters” on page 181.
See “Editing the tags on a cluster” on page 198.
See “Editing tags on selected service groups ” on page 203.
See “Editing the tags on a service group” on page 211.
Tag values are user-definable, but the tags are predefined.
The following are the available tags:
■ Cluster Regions
■ Cluster Sites
■ Group Departments
■ Group Lines of Business
In some page, the VCS Management Console might shorten tag names to Region,Site, Department, and LOB.
Note: If you remove a tag from the local management server in a peerconfiguration, the tag is removed only from the local management server. Youmust also remove the tag while logged on to the remote management server.
Editing the Regions tag for clustersThis task enables you to create or delete values for the Regions tag.
To edit the Regions tag
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Tags tab.
3 In the Configuration menu, click Edit Cluster Regions.
4 In the Edit Cluster Regions dialog box, do one or both of the following:
■ If you want to create a tag value, enter the new value into the Values boxand then click Add.
■ If you want to delete a value, check the value name and then click Remove.
5 Click OK.
Administering basic high availability cluster configurationsAdministering tags
174
Editing the sites tag for clustersThis task enables you to create or delete values for the sites tag.
To edit the sites tag
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Tags tab.
3 In the Configuration menu, click Edit Cluster Sites.
4 In the Edit Cluster Sites dialog box, do one or both of the following:
■ If you want to create a tag value, enter the new value into the Values boxand then click Add.
■ If you want to delete a value, check the value name and then click Remove.
5 Click OK.
Editing the Departments tag for service groupsThis task enables you to create or delete values for the Departments tag.
To edit the Departments tag
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Tags tab.
3 In the Configuration menu, click Edit Group Departments.
4 In the Edit Group Departments dialog box, do one or both of the following:
■ If you want to create a tag value, enter the new value into the Values boxand then click Add.
■ If you want to delete a value, check the value name and then click Remove.
5 Click OK.
Editing the Line of Business tag for service groupsThis task enables you to create or delete values for the Lines of Business tag.
To edit the Line of Business tag
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Tags tab.
3 In the Configuration menu, click Edit Group Lines of Business.
4 In the EditGroupLinesofBusiness dialog box, do one or both of the following:
175Administering basic high availability cluster configurationsAdministering tags
■ If you want to create a tag value, enter the new value into the Values boxand then click Add.
■ If you want to delete a value, check the value name and then click Remove.
5 Click OK.
Administering sitesSites are logical groupings of clusters that display as site branches in the navigationtree. All clusters are organized into sites.
Sites are determined wholly through the application of the site tag. The defaultvalue for the site tag is Untagged Clusters. All clusters that have not had theirsite tags set are shown under the Untagged Clusters site branch in the navigationtree.
See “About sites and the enterprise” on page 22.
See “About the Manage tab” on page 143.
After initial management server configuration, to implement a site organizationthat is populated with clusters, you must do the following:
■ Create values for the site tagThis action creates unpopulated sites in the navigation tree.
■ Set a cluster's site tag to a site tag valueThis action places the cluster in the specified site in the navigation tree.
Creating sitesThe first opportunity to create sites is during the first run of the console aftermanagement server configuration. This is the time at which you discover andconfigure the first clusters to be added to the console. After the initial clusterconfiguration, you can discover and configure additional clusters at any time. Tocreate sites during cluster discovery and configuration, you use the Discover/AddClusters wizard on the Administration tab.
You can also create sites without discovering and configuring clusters.
See “Configuring sites” on page 122.
Changing sitesTo move a cluster from one site to another, edit the cluster's site tag.
To perform this task, you must have adminstrator privilege on the managementserver that manages the required clusters.
Administering basic high availability cluster configurationsAdministering sites
176
To change sites by setting the site tag
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 On the main tab bar, click the Clusters tab.
5 In the Clusters Listing table, do one of the following:
■ To select one or more clusters, check the check box next to each requiredcluster.
■ To select all clusters, check the check box at the top of the table.
6 In the Configuration menu, click Edit Tags.
7 In the Edit Tags wizard, in the Tag Name drop-down menu, click Site.
8 In the Values drop-down menu, click a new value for the site tag and thenclick OK.
9 In the final panel, read the message about the results of the command andthen click Close.
The clusters that you selected appear within the specified site. Expand thesite to display the one or more clusters.
If the site tag value that you specified was not previously set on any cluster,a new site appears in the navigation tree.
Deleting sitesTo delete a site, you must first remove all clusters from (depopulate) the site.Depopulating a site requires that you set the site tag values on the member clustersto some other value.
See “Editing tags on selected clusters” on page 181.
See “Editing the tags on a cluster” on page 198.
After you depopulate a site, you can delete the site.
To delete selected sites
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Right-click the Enterprise branch.
4 In the shortcut (context) menu, click Add/Delete Sites.
177Administering basic high availability cluster configurationsAdministering sites
5 In the Edit Cluster Sites wizard, check the check box for each site that youwant to delete and then click Remove.
You receive an error message if you select a populated site.
6 After you finish selecting sites for removal, click OK.
The removed sites no longer appear in the navigation tree.
To delete a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site and then click Delete Site.
If the site is populated or if it is the default site, the Delete Site menu item isunavailable.
5 In the Delete Site wizard, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
The site is no longer shown in the navigation tree.
Administering clustersClusters host your highly available applications as redundant,identically-configured service groups. These service groups are distributed amongthe cluster nodes and can fail over from one node to another.
The cluster administration pages of the VCS Management Console enable you todo the following:
■ Collectively administer multiple clusters: In a multiple cluster administrationpage, one task can affect one or more clusters that you select from a list in thedetails pane.
■ Singly administer individual clusters: In an individual cluster administrationpage, a task can affect only the cluster that is currently described in the detailspane.
The tasks that you can perform differ in each type of cluster administration page.
Administering basic high availability cluster configurationsAdministering clusters
178
Note:You can always perform a task on an individual cluster in a multiple clusteradministration page by selecting only one cluster in a table. However, not allindividual cluster administration tasks are available in a multiple clusteradministration page.
Administering multiple clustersMultiple cluster administration tasks include the following:
■ Editing attributes of selected clusters
■ Editing tags on selected clusters
■ Removing selected clusters (also available on the Administration tab)
■ Marking a default site
The cluster-related task of adding clusters to the managed enterprise is part ofconsole configuration.
See “Discovering and configuring one or more clusters for management”on page 123.
Tasks for collectively administering multiple clusters are available when you viewall clusters in the enterprise or all clusters in a site. The example procedures inthis section conduct the cluster management tasks with the enteprise selected.
About Clusters Listing tablesPages on the Manage tab that list all configured clusters in the enterprise or in asite contain a Clusters Listing table.
You can view the clusters in the enterprise or in a site. If you view the clusters ina site, the Site column is omitted because the site is selected in the navigationtree. The site is also shown on the navigation bar.
The following are the columns and data in a Clusters Listing table:
Contains the name of the cluster. The cluster name is also a link tothe cluster's status.
Name
Contains a status icon that indicates the consolidated state of thecluster
See “About object states and consolidated states” on page 22.
State
Contains an integer that indicates the number of service groups inthe cluster
This number is also a link to the cluster's service groups.
Groups
179Administering basic high availability cluster configurationsAdministering clusters
Contains an integer that indicates the number of systems in the cluster
This number is also a link to the cluster's systems.
Systems
Contains the privileges that you have on the clusterUser Privilege
Contains a numeric designation in N.N.NN.N format that indicatesthe version of the VCS clustering software that is used on the cluster
Cluster Version
Contains the operating system platform of the systems in the clusterPlatform
Contains the region in which the cluster services reside. This columnis populated with the value of the region tag. You can set the value ofthe region tag.
See “Editing tags on selected clusters” on page 181.
Region
Contains the name of the site where cluster resides. This column ispopulated with the value of the site tag. You can set the value of thesite tag.
See “Editing tags on selected clusters” on page 181.
The site is also a link to the site's service groups.
Site
Contains the name of the management server in which the cluster isconfigured—the cluster connects to this management server.
MS (managementserver
Contains various log and other information.Other info
Editing attributes of selected clustersThe Edit Attributes task enables you to edit attributes on selected clusters in aone-to-many fashion (one action modifies many clusters).
To perform this task, you must have administrator privilege on the clusters withattributes to be edited.
Note: Before you begin this task, you must view all clusters in the enterprise orall clusters in a site.
To view all clusters in the enterprise
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 In the details tab bar, click the Clusters tab.
This action displays a Clusters Listing table of all clusters in the enterprise.
Administering basic high availability cluster configurationsAdministering clusters
180
To edit attributes of selected clusters
1 View all clusters in the enterprise.
2 In the Clusters Listing table, do one of the following:
■ To select one or more specific clusters, check the check box next to eachcluster that has attributes that you want to edit.
■ To select all clusters, check the check box at the top of the table.
3 In the Configuration task menu, click Edit Attribute.
4 In the Edit Attribute wizard, specify the following attribute options:
In the Attribute Name drop-down menu, select the attributethat you want to edit.
The attribute name
In the Values box, either click a value to change the it, orclick the + (plus) to add a value. Click a value and then clickthe - (minus) to remove a value. You can enter more thanone value for some attributes. Use the up- and down-arrowsto scroll among multiple values.
The attribute value
Specify a setting for the Apply value to option. Apply to allnodes applies the changes to all systems listed the SystemList, which lists all systems on which the attribute isconfigured. Apply to selected nodes enables you to selectnodes from the System List.
The systems on which tochange the attribute
When you finish specifying attribute options, click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Editing tags on selected clustersThe Edit Tags task enables you to edit tags on selected clusters in a one-to-manyfashion (one action modifies many clusters). You can use this procedure to set thesite tag on a cluster. The site tag determines site membership for a cluster, whichaffects the branch organization of the navigation tree.
See “About sites and the enterprise” on page 22.
See “About the Manage tab” on page 143.
See “Administering tags” on page 173.
To perform this task, you must have administrator privilege on the managementserver that manages the required clusters.
181Administering basic high availability cluster configurationsAdministering clusters
Note: Before you begin this task, you must view all clusters in the enterprise orall clusters in a site.
To view all clusters in the enterprise
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 In the details tab bar, click the Clusters tab.
This action displays a Clusters Listing table of all clusters in the enterprise.
To edit tags of selected clusters
1 View all clusters in the enterprise.
2 In the Clusters Listing table, do one of the following:
■ To select one or more clusters, check the check box next to each requiredcluster.
■ To select all clusters, check the check box at the top of the table.
3 In the Configuration task menu, click Edit Tags.
4 In the Edit Tags wizard, on the Tag Name drop-down menu, click the tag thatyou want to edit.
This action displays the tag's current value in the Values drop-down menu.This drop-down menu is a combination menu and edit box.
5 In the Values drop-down menu, click an existing value or enter new value forthe site tag and then click OK.
6 In the final panel, read the message about the results of the command andthen click Close.
If you entered a new value instead of clicking an existing value, a new sitethat contains the selected clusters appears in the navigation tree.
Removing selected clustersThe Remove Cluster task enables you to delete clusters from the VCS ManagementConsole database in a one-to-many fashion (one action deletes many clusters).You must be a cluster administrator (have administrator privilege) on the selectedclusters to perform this task. You can only delete clusters that are in an unknownstate.
See “About object states and consolidated states” on page 22.
Administering basic high availability cluster configurationsAdministering clusters
182
To perform this task, you must have administrator privileges on the clusters tobe deleted.
Note: Before you begin this task, you must view all clusters in the enterprise orall clusters in a site.
To view all clusters in the enterprise
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 In the details tab bar, click the Clusters tab.
This action displays a Clusters Listing table of all clusters in the enterprise.
To remove selected clusters
1 View all clustes in the enterprise.
2 In the Clusters Listing table, do one of the following:
■ To select one or more clusters, check the check box next to each clusterthat you want to remove.
■ To select all clusters, check the check box at the top of the table.
3 In the Configuration menu, click Remove Clusters.
4 In the Remove Clusters wizard, review the list of the clusters that you haveselected and then click Next.
5 In the Results panel, the Progress box displays status information about theremoval. A successful removal of a single cluster looks similar to the following:
Deleting cluster hp50mp1_51cc_single...
Deleting resource CMC_ClusterConfig
Deleting service group CMC
Deleting resource type CMC
Dumping cluster configuration
Deleting real time dataRemoval of clusters is complete.
6 Click Close.
Marking a default siteThis task enables you to designate a site as the default site. The default site is thefirst site that is listed in the navigation tree. The console automatically designates
183Administering basic high availability cluster configurationsAdministering clusters
Untagged Clusters as the default site. Untagged Clusters remains the default siteuntil you designate a new one.
Note: You cannot delete the default site. If you want to delete the default site, youmust first designate another site as the default.
To perform this task, you must have administrator privilege on the managementserver to which you logged in.
To mark a default site while viewing enterprise status
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch.
On the details tab bar, this action selects the Status tab by default.
4 On the Configuration task menu, click Mark Default Site.
If the current default site is selected in the navigation tree, this menu itemis unavailable.
5 In the Mark Default Site wizard, in the Select a Site drop-down menu, click asite name and then click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
To mark a default site while viewing site status
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the site that contains the required clusters.
On the details tab bar, this action selects the Status tab by default.
5 On the Configuration task menu, click Mark This as Default Site.
If the current default site is selected in the navigation tree, this menu itemis unavailable.
6 In the final panel, read the message about the results of the task and thenclick Close.
Administering an individual clusterIndividual cluster administration tasks include the following:
Administering basic high availability cluster configurationsAdministering clusters
184
■ Opening a cluster configuration
■ Saving a cluster configuration
■ Determining a cluster's connected management server
■ Viewing a cluster's connection list
■ Editing a cluster's connection list
■ Adding a system to a cluster
■ Adding a service group to a cluster
■ Deleting selected service groups from a cluster
■ Linking service groups in a cluster (also available when administering servicegroups)
■ Unlinking service groups in a cluster (also available when administering servicegroups)
■ Editing the attributes on a cluster
■ Editing the tags on a cluster
Tasks for administering an individual cluster are available when you view thedetails of (all service groups or all systems in) one cluster.
Opening a cluster configurationThis task enables you to change a read-only cluster configuration file to aread-write file by opening the configuration. This task is available only when thecluster configuration file is saved in read-only mode.
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
185Administering basic high availability cluster configurationsAdministering clusters
To open a configuration
1 View the service group details of the required cluster.
2 In the navigation tree, right-click the required cluster.
3 In the context menu, click Open Configuration.
4 Click OK.
Saving a cluster configurationThis task enables you to save an updated VCS cluster configuration to disk ineither read-only or read-write mode.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To save the configuration
1 View the service group details of the required cluster.
2 On the Configuration menu, click Save Configuration.
3 In the Save Configuration wizard, check or clear Make configurationread-only.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Determining a cluster's connected management serverYou can determine the management server to which a cluster is connected byviewing the Clusters Listing table. The Clusters Listing table is available whenyou are viewing all clusters in the enterprise or all clusters in a site.
Administering basic high availability cluster configurationsAdministering clusters
186
To view a cluster's connected management server
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 In the details tab bar, click the Clusters tab.
This action displays a Clusters Listing table of all clusters in the enterprise.The MS column shows the management server to which each cluster iscurrently connected.
Viewing a cluster's connection listThe management server maintains a connection list for every cluster. A connectionlist specifies the cluster nodes, in order of preference, to which the managementserver attemtps to connect.
To view a cluster's connection list
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Configured Clusters tab if it is not alreadyselected.
3 In the Configured Clusters table, in the Connection List column, click ... (edit)in the row that corresponds to the required cluster.
Editing a cluster's connection listThis task enables you to edit a cluster's connection list. Every cluster has aconnection list that specifies the cluster nodes, in order of preference, to whichthe management server attempts to connect.
To edit a cluster's connection list
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Configured Clusters tab if it is not alreadyselected.
3 In the Configured Clusters table, in the Connection List column, click ... (edit)in the row that corresponds to the required cluster.
4 In the Edit Connection List dialog box, do one or both of the following:
■ Enter additional cluster node names separated by commas.
187Administering basic high availability cluster configurationsAdministering clusters
■ Delete cluster node names by backspacing over them or by selecting themand pressing the Delete key.
5 Click OK.
Adding a system to a clusterThis task enables you to add a system to a cluster. It adds the system to the consoletables whether or not the system exists or is a member of the cluster. However,if the system is not real or is not a yet a member of the cluster, the cluster doesnot connect to it. Consequently, its status in the console is unknown. If a systemof the same name is later added to the cluster, the system comes online in theconsole.
To perform this task, you must have administrator privilege on the cluster.
Note: Before you begin this task, you must be view all systems in one cluster.
To view all systems in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab by default and displaysa Systems Listing table of all the systems that are configured in the cluster.
To add a system
1 View all systems in the required cluster.
2 In the Configuration menu, click Add System.
3 In the Add System wizard, enter the name of the new system and then clickOK.
4 In the final panel, read the message about the results of the task and thenclick OK.
Removing selected systems from a clusterThis task enables you to remove one or more systems from cluster membership.Ensure that each system that you intend to remove is not running and that noservice groups are configured on it.
Administering basic high availability cluster configurationsAdministering clusters
188
This task describes system removal when you view the details of a cluster (witha cluster selected in the navigation tree). You can also remove a system when youview the details of a single system (with a system selected in the navigation tree).The Delete System task is available on the Operations menu in both cases.
To perform this task, you must have administrator privilege on the cluster.
Note: Before you begin this task, you must be view all systems in one cluster.
To view all systems in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab by default and displaysa Systems Listing table of all the systems in the cluster.
To delete selected systems
1 View all systems in the required cluster.
2 In the Systems Listing table, check one or more systems.
3 On the Configuration menu, click Delete System.
4 In the Delete System wizard, review your system selection and then click OK
5 In the final panel, read the message about the results of the task and thenclick Finish.
Adding a service group to a clusterThis task enables you to add a service group to a cluster.
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
189Administering basic high availability cluster configurationsAdministering clusters
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To add a service group to a cluster
1 View all service groups in the required cluster.
2 On the Configuration menu, click Add Service Group.
3 In the Service Group Configuration wizard, read the introductory informationand then click Next.
4 In the Service Group Configuration panel, specify the following:
■ In the ServiceGroupName box, enter the name of the service group thatyou want to add.
■ For Service Group Type , click Failover or Parallel.See the VCS User's Guide for information on service group types.
After you finish specifying options, click Next.
5 In the System List Configuration panel, specify the following details for thetarget systems (target systems are the systems that can host the servicegroup):
Find the system you want in the list under Select and AddSystems. To quickly find a specific system, click Filter, typea few letters of the system name, and then click Apply.
To select a system, click the system name under Select andAdd Systems and then click the right-arrow button to moveit under Selected Systems. You can select one or more systems.
To reject a system, click the system name under SelectedSystems and then click the left-arrow button to move it backunder Select and Add Systems.
The target systemnames
Under Selected Systems, check Startup next to a system nameif you want the service group to start up automatically on thatsystem.
The startup system
Administering basic high availability cluster configurationsAdministering clusters
190
Use the up- and down-arrow buttons to the right of theSelected Systems table to set the order of systems in the list.To change the position of a system in the list, click the systemname in the Selected Systems table and then click the up- ordown-arrow button to move it up or down in the list.
VCS attempts to bring the service group online on the firstsystem in the system list, unless you have selected a differentsystem as the startup system using the Startup option
If the service group cannot be brought online on the firstsystem or on the designated startup system, VCS does one ofthe following:
■ If the first system is also the startup system, VCS attemptsto bring the service group online on each remaining systemin the order listed.
■ If the first system and the startup system are different,VCS attempts to bring the service group online on the firstsystem in the list. If the first system fails, VCS attemptsto bring the service group online on each remaining systemin the order listed.
The system order ofpreference
After you finish specifying information in this panel, click Next.
6 In the Resource Creation panel, specify the following details about theresources that belong to the service group:
Enter the name of any new resources that you want to add tothe service group into the Resource Name text box.
Resource names must conform to the following guidelines:
■ Consist of only one string
■ Not contain special characters like . (period) or &(ampersand).
■ Begin with an alphabetic character—the remainingcharacters in the name can be letters, digits, hyphens, orunderscores.
The member resourcelist
In the Resource Type drop-down menu, select the resourcetype of the member resource that you are adding.
The resource type
If you want the resource to start in an enabled state after theservice group comes online, check Enable Resource. ClickAdd Resource to add the resource to the Resource List.
The resource startupstate
191Administering basic high availability cluster configurationsAdministering clusters
In the Resource List table, you can edit resource attributes ordelete a resource using the buttons in the Edit and Deletecolumns.
The resourceattribute values orresource removal
7 If you do not want to link resources, click Finish now to exit the wizard.Otherwise, continue with step 7.
8 In the Link/Unlink Resource panel, provide the following relationship details:
In the Parent Resource drop-down menu, click the resourcethat must be brought online after the child resource.
The parent resource
In the Child Resource list box, select which resource shouldbe brought online first, and then click Add Link. You cancreate multiple links.
The child resource
After you finish specifying information in this panel, click Finish.
Deleting selected service groups from a clusterThis task enables you to remove a service group from a cluster.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent clusters of the service groups to bedeleted
■ Administrator privileges on the service groups to be deleted.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
Administering basic high availability cluster configurationsAdministering clusters
192
To remove a service group from a cluster
1 View the service group details of the required cluster.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Configuration menu, click Delete Service Group.
4 In the Delete Service Group panel, click OK to confirm that you want to removethe selected service groups.
5 In the next panel, read the message about the results of the task and thenclick Close.
Linking service groups in a clusterThis task enables you to create links, or dependencies, among service groups ina cluster. Service groups are linked two at a time.
A service group often depends upon the resources and running status of another.Therefore, the service group on which the other depends must come online beforethe dependent service group. When you create a link between two service groups,you indicate which service group must come onilne first.
The service group that must come online first is the child service group. It is calledthe child because, in a dependency diagram, it is beneath the dependent servicegroup..
The service group that must come online after the child is the parent servicegroup. It is called the parent because, in a dependency diagram, it is above thechild.
Links (dependencies) can be recursive: the parent of one dependency can be thechild of another. In a complex service group, several parent-child dependenciesexist to ultimately support a single application service group. In a dependencydiagram, this application service group occupies the apex of the diagram.Dependency diagrams are also called dependency trees.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent clusters of the service groups to belinked
■ Administrator privileges on the service groups to be linked
193Administering basic high availability cluster configurationsAdministering clusters
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
Administering basic high availability cluster configurationsAdministering clusters
194
To link two service groups with a parent-child dependency
1 On the Configuration menu, click Link Service Groups.
2 In the Link Service Groups wizard, specify the following details of thedependencies:
These are the service group that you intend to serve as theparent service group and the child service group. Use thecorresponding drop-down menus to specify these groups.
The service groups
In a local dependency, an instance of the parent servicegroup depends on an instance of the child service groupon the same system. Depending on the category of thedependency, the parent may require that the child be onlineor offline.
In a Global dependency, an instance of the parent servicegroup depends on one or more instances of the child servicegroup. The parent requires that the child or children beonline on any system.
The relationship type
In a soft dependency, VCS imposes minimal constraintswhile it brings the parent service group and child servicegroup online and takes them offline.
In a firm dependency, when the child service group faults,VCS takes the child service group offline before it takesthe parent service group offline .
In a hard dependency, when the child service group faults,VCS takes the parent service group offline before it takesthe child service group offline. Hard dependencies aredesigned for use with Veritas Volume Replicator in disasterrecovery configurations. In these configurations, theapplication is in the parent service group and thereplication resources are in the child service group.
The dependencycategory
After you finish specifying options in the Link Service Groups wizard, clickOK.
3 In the final panel, read the message about the results of the task and thenclick Close.
Unlinking service groups in a clusterThis task enables you to unlink a dependent pair of service groups in a cluster.
See the VCS User's Guide for information on cluster dependencies.
195Administering basic high availability cluster configurationsAdministering clusters
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent clusters of the service groups to beunlinked
■ Administrator privilege on the service groups to be unlinked
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To unlink two service groups
1 In the Configuration menu, click Unlink Service Groups.
2 In the Unlink Service Groups panel, select the parent group and the childgroup from the corresponding drop-down menus and then click OK.
3 In the final panel, read the message about the results of the task and thenclick Close.
Viewing service group dependencies in a clusterThis task enables you to view dependency links, if any, among service groups ina cluster.
See "About service group dependencies" in the VCS User's Guide.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent clusters of the servicegroups to be viewed
■ Administrator or operator privileges on the service groups to be viewed
Note: Before you begin this task, you must view all service groups in one cluster.
Administering basic high availability cluster configurationsAdministering clusters
196
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To view linked service groups and service group information
1 View the service group details of the required cluster.
2 On the details tab bar, on the Status tab, click the Group Dependency detaillink.
In the Service Group dependency view panel, you can inspect the currentcluster's service group dependency tree. If the tree is large, you can use thepanning controls and zoom controls in the lower left of the panel. Thesecontrols enable you to view parts of the tree that might be off the screen.
3 If you want to view the diagram in a separate browser window, click Open innew window.
4 To view service group information, click the service group icons in the treeto go to the status details for that service group.
Editing the attributes on a clusterThis task enables you to edit the attributes on a cluster.
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
197Administering basic high availability cluster configurationsAdministering clusters
To edit the attributes on an individual cluster
1 View the service group details of the required cluster.
2 On the details tab bar, on the Status tab, click the Properties detail link.
3 In the All Attributes table, in the Edit column, click ... (edit) in the row thatcorresponds to the attribute that you want to edit.
4 In the Edit Attribute wizard, specify the following attribute options:
Select the attribute that you want to edit from theAttribute Name drop-down menu.
The attribute name
In the Values box, enter a value or values for theattribute. For multivalute attributes, either click a valueto change it, or click + (plus) to add a value. To removea value, click the value and then click - (minus). Click theup- and down-arrows to scroll among multiple values.
The attribute value
Specify a setting for the Apply value to option. Apply toall nodes applies the changes to all systems listed theSystem List, which lists all systems on which theattribute is configured. Applytoselectednodes enablesyou to select nodes from the System List.
The systems on which tochange the attribute
When you finish specifying attribute options, click OK.
Editing the tags on a clusterThis task enables you to edit the tags that are applied to a cluster. You can usethis procedure to set the site tag on a cluster. The site tag determines sitemembership for a cluster, which affects the branch organization of the navigationtree.
See “About sites and the enterprise” on page 22.
See “About the Manage tab” on page 143.
See “Administering tags” on page 173.
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering clusters
198
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To edit the attributes on an individual cluster
1 On the Configuration menu, click Edit Cluster Tags.
2 In the Edit Tags wizard, specify the following options:
In the Tag Name drop-down menu, clickthe name of a currently-applied tag.
The tag name
In the Values drop-down menu, click avalue for the selected tag.
The tag values
When you finish specifying tag options, click OK.
3 In the final panel, read the message about the results of the task and thenclick Close.
Administering service groupsService groups are associations of hardware and software resources that functiontogether as a running instance of a highly available application in a cluster.Identically-configured service groups are redundantly distributed among thenodes in a cluster to enable failover.
The service group administration pages of the VCS Management Console enableyou to do the following:
■ Collectively administer multiple service groups: In a multiple service groupadministration page, one task can affect one or more service groups that youselect from a list in the details pane.
■ Singly administer individual service groups: In an individual service groupsadministration page, a task can affect only the service group that is currentlydescribed in the details pane.
The tasks that you can perform differ in each type of service group administrationpage.
199Administering basic high availability cluster configurationsAdministering service groups
Note: You can always perform a task on an individual service group in a multipleservice group administration page by selecting only one service group in a table.However, not all individual service group administration tasks are available in amultiple service group administration page.
Administering multiple service groupsMultiple service group administration tasks include the following:
■ Editing attributes of selected service groups
■ Editing tags on selected service groups
■ Clearing faults on selected service groups
■ Online anywhere and offline anywhere for selected groups
■ Freezing selected service groups
■ Unfreezing selected service groups
Tasks for collectively administering multiple service groups are available whenyou are viewing all service groups in the enterprise, all service groups in a site,or all service groups in a cluster.
Sites generally contain a manageable number of service groups. The exampleprocedures in this section conduct the service group management tasks in thecontext of a site (with a site selected). If a service group management task is notavailable on the site menus, the next most convenient context (a cluster, forexample) is used.
About Groups Listing tablesPages on the Manage tab that list all configured service groups in the enterprise,in a site, or in a cluster contain a Groups Listing table.
You can view the service groups in the enterprise, in a site, or in a cluster. If youview the service groups in a site, the Site column is omitted because the site isselected in the navigation tree. The site is also shown on the navigation bar. Ifyou view the service groups in a cluster, the Site and the Cluster Name columnsare omitted for the same reason.
The following are the columns and data in a Groups Listing table:
Contains the name of the service group. The service groupname is a link to the status details page for the service group
Name
Administering basic high availability cluster configurationsAdministering service groups
200
Contains a status icon that indicates the consolidated stateof the service group
See “About object states and consolidated states” on page 22.
State
Contains an HA fire drill status icon that indicates theresults of the last run HA fire drill. HA fire drills are part ofthe readiness management and monitoring system.
See “About HA and DR readiness” on page 309.
HA
Contains a DR fire drill status icon that indicates the resultsof the last run DR fire drill. DR fire drills are part of thereadiness management and monitoring system.
DR
Contains the name of the service group's parent cluster.The cluster name is also a link to the parent cluster's servicegroup details page.
Cluster Name
Contains the VCS version running on the cluster that hoststhe service group.
Cluster Version
Contains a tag value that ndicates the line of business ofthe group. The value of the lines of business (LOB) tag isused to populate this column. You can set the value of theLOB tag.
Line of Business
Contains a tag value that indicates the department of thegroup. The value of the department tag is used to populatethis column.
Department
Contains the name of the service group's parent site. Thesite name is also a link to the parent site's service groupdetails page.
Site
Contains the name of the management server that isconnected to the service group's parent cluster.
MS
Can contain one of many predefined informational messagesabout the service group.
Examples include the following:
■ VCS Internals (the group is used internally by VCS)
■ Fire Drill (the group is a DR fire drill group)
■ Messages about the type of replication that is configured
Note: Replication messages are links to a popup panel withadditional information about the replication.
Other info
Figure 8-1 shows a Groups Listing table:
201Administering basic high availability cluster configurationsAdministering service groups
Figure 8-1 A groups listing table with HA and DR columns populated
Editing attributes of selected service groupsThe Edit attributes task enables you to edit attributes on selected service groupsin a one-to-many fashion (one action modifies many service groups).
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privilege on the parent cluster of the service groupwith attributes to be edited
■ Administrator or operator privilege on the service group with attributes to beedited
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, all service groups in a cluster, or all service groups ina global cluster.
A site generally contains a manageable number of service groups.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To edit attributes of selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more specific service groups, check the check box nextto each service group that has attributes that you want to edit.
Administering basic high availability cluster configurationsAdministering service groups
202
■ To select all service groups, check the check box at the top of the table.
3 In the Configuration menu, click Edit Attribute.
4 In the Edit Attribute wizard, specify the following attribute options:
In the Attribute Name drop-down menu, select the attributethat you want to edit.
The attribute name
In the Values box, either click a value to change it, or click +(plus) to add a value. To remove a value, click a value and thenclick - (minus) .
You can enter more than one value for some attributes. Clickthe up- and down-arrows to scroll among multiple values.
The attribute value
Specify a setting for the Apply value to option. To apply thechanges to all systems in the System List, which lists allsystems on which the attribute is configured, click Apply toall nodes. If you want to select systems (nodes) in the SystemList, click Apply to selected nodes.
The systems onwhich to change theattribute
When you finish specifying attribute options, click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Editing tags on selected service groupsThis task enables you to edit tags on selected service groups in a one-to-manyfashion (one action modifies many service groups).
See “Administering tags” on page 173.
You must have administrator privileges on the connected management server toperform this task.
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, or all service groups in a cluster.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
203Administering basic high availability cluster configurationsAdministering service groups
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To edit tags on selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Configuration menu, click Edit Tags.
4 In the Edit Tags wizard, select the tag you want to modify in the Tag namedrop-down menu.
5 Enter the new value for the tag into the Values box.
6 If you want to enter an optional description, enter it into the Descriptionbox.
7 Click OK.
8 In the final panel, read the message about the results of the task and thenclick Close.
Freezing selected service groupsThe Freeze task enables you to place a service group into a state in which it isactive, but not monitored, not able to change state, and not able to fail over toanother system. Freezing is useful for performing maintenance tasks on a servicegroup.
For example, you may want to freeze a service group if you want to stop VCS(specifically, HAD), but do not want the service group and the correspondingapplications to fail over to another cluster node.
During the time that a service group is frozen, it is running, but not highlyavailable. If you froze the service group because you wanted to stop VCS, do notunfreeze it until you restart VCS.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privilege on the parent cluster of the service groupto be frozen
■ Administrator or operator privilege on the service group to be frozen
Administering basic high availability cluster configurationsAdministering service groups
204
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, all service groups in a cluster.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To freeze selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Operations menu, click Freeze.
4 In the Freeze Service Group(s) wizard, check FreezePersistently if you wantthe service group to remain frozen until explicitly unfrozen. Otherwise, theservice group unfreezes when either the management server or the VCSManagement Console is restarted.
5 Click OK.
When you freeze the selected service groups, the console adds a red padlockto the status icon for each service group.
6 In the final panel, read the message about the results of the task and thenclick Close.
Unfreezing selected service groupsThe Unfreeze task enables you to unfreeze a frozen service group.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privilege on the parent cluster of the service groupto be unfrozen
■ Administrator or operator privilege on the service group to be unfrozen
205Administering basic high availability cluster configurationsAdministering service groups
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, or all service groups in a cluster.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To unfreeze selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table (or Global Groups Status table if you are viewingglobal service groups), do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Operations task menu, click Unfreeze.
4 In the Unfreeze System(s) wizard, click OK.
When you unfreeze the selected service groups, the console removes the redpadlock from the status icon for each service group.
5 In the final panel, read the message about the results of the task and thenclick Close.
Faulting selected service groups (simulated service groupsonly)This task enables you to manually simulate a fault on simulated service groupsto test their failover behavior. This operation is available only when the servicegroups is part of a cluster that is created using the VCS cluster simulator.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the service groups to be faulted
■ Administrator privilege on the service groups to be faulted
Begin here
Administering basic high availability cluster configurationsAdministering service groups
206
Before you begin this task, you must view the details of one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table of all service groups in thecluster.
To fault selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Simulation menu, click Fault Service Groups.
The Simulation menu is available only when the VCS cluster simulator isinstalled.
4 In the Fault Service Group wizard, select the systems on which you want tofault the service group from the drop-down menu.
The console populates this drop-down menu using the service group’s systemlist. The system list contains a list of all systems on which the service groupis configured.
5 Click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Clearing faults on selected service groupsThe Clear Faulted Group task enables you to remove the resource faults withinselected service groups. After you clear resource faults, you can bring the servicegroups online. A resource fault in a service group may occur in several situations,such as a power failure or a faulty configuration.
You must have one of the following privileges on the specified objects to performthis task:
207Administering basic high availability cluster configurationsAdministering service groups
■ Administrator or operator privilege on the parent cluster of the service groupto be cleared of resource faults
■ Administrator or operator privilege on the service group to be cleared ofresource faults
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, or all service groups in a cluster.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To clear faults on selected service groups
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
3 In the Operations menu, click Clear Fault.
In the Clear Service Group(s) Faults wizard, use the appropriate drop-downmenu to select the systems on which you want to clear each service group.Each drop-down menu is populated using the system list of each servicegroup. The system list of a service group contains a list of all systems onwhich the service group is configured.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Online anywhere and offline anywhere for selected groupsThese tasks enable you to manually put a service group into a responsive,functioning state, or into an unresponsive, non-functioning state. You can bringa service group online on a specific system, or you can bring a service group online
Administering basic high availability cluster configurationsAdministering service groups
208
anywhere. If you select anywhere, the console brings the service group online onthe first available system in the first available cluster.
Likewise, you can take a service group offline on a specific system, or you can takethe service group offline anywhere. If you select anywhere, the console takes theservice group offline on the first system in the first cluster on which it finds theservice group to be running.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privilege on the parent cluster of the service groupto be brought online or taken offline anywhere in the cluster
■ Administrator or operator privilege on the service group to be brought onlineor taken offline anywhere in the cluster
Note:Before you begin this task, you must view all service groups in the enterprise,all service groups in a site, or all service groups in a cluster.
To view all service groups in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
5 On the details tab bar, click the Groups tab.
This action displays a Groups Listing table of all service groups in the site.
To bring a service group online or take it offline anywhere
1 View all service groups in the required site.
2 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups anywhere, check the check box at the top ofthe table.
209Administering basic high availability cluster configurationsAdministering service groups
3 In the Operations menu, click Online anywhere or Offline anywhere.
The candidate systems are members of the system list for each service group.The system list of a service group contains a list of all systems on which theservice group is configured. Both of these tasks try each system in a systemlist until the console successfully brings every service group online or takesevery service group offline.
4 Click OK.
Administering an individual service groupIndividual service group administration tasks include the following:
■ Editing the tags on a service group
■ Deleting selected service groups from a cluster
■ Linking service groups in a cluster
■ Unlinking service groups in a cluster
■ Modifying the system list of a service group
■ Faulting a service group
■ Adding a RemoteGroup resource to a service group
■ Clearing a faulted service group
■ Linking resources in a service group
■ Bringing a service group online
■ Taking a service group offline
■ Switching a service group
■ Freezing a service group
■ Unfreezing a service group
■ Flushing a service group
■ Enabling a service group
■ Disabling a service group
■ Enabling a resource
■ Disabling a resource
■ Probing a resource
■ Clearing a faulted service group
Administering basic high availability cluster configurationsAdministering service groups
210
■ Assigning and unassigning maintenance windows
The following service-group-related tasks are part of cluster management:
■ Adding a service group to a cluster
■ Deleting selected service groups from a cluster
■ Linking service groups in a cluster
■ Unlinking service groups in a cluster
See “Administering an individual cluster” on page 184.
Tasks for administering an individual service group are available when you areviewing the details of (all resources or all systems in) one service group.
Editing the tags on a service groupThis task enables you to edit the tags that are applied to a service group.
See “Administering tags” on page 173.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the service group with tagsto be edited
■ Administrator privilege on the service group with tags to be edited
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
211Administering basic high availability cluster configurationsAdministering service groups
To edit the tags on an individual service group
1 On the Configuration menu, click Edit Group Tags.
2 In the Edit Tags wizard, specify the following options:
In the Tag Name drop-down menu, click the name of acurrently-applied tag.
The tag name
In the Values drop-down menu, do the following:
■ To select an existing value, click the down-arrow and thenclick a value.
■ To specify a new value, click the menu box and then enterthe new value
The tag values
When you finish specifying tag options, click OK.
3 In the final panel, read the message about the results of the task and thenclick Close.
Reconfiguring a service groupThis task enables you to edit the configuration of a service group. You cannot editthe service group name or its failover-or-parallel designation using this task.
Note: To change the name or failover-or-parallel designation, remove the servicegroup. You can then then add it back with the new name and designation.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the service group to bereconfigured
■ Administrator privilege on the service group to be reconfigured
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
212
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To reconfigure a service group
1 View all resources in the required service group
2 On the Configuration menu, click Modify Service Group.
3 In the Service Group Configuration wizard, read the introductory text andthen click Next.
4 In the Service Group Configuration panel, click Next.
The service group name and failover-or-parallel designation appear but cannotbe modified in this task.
5 In the System List Configuration panel, specify the following details for thetarget systems (the target systems are the systems that can host the servicegroup):
Find the system you want in the list under Select and AddSystems.
To quickly find a specific system, click Filter, type a few lettersof the system name, and then click Apply.
To select a system, click the system name under Select and AddSystems and then click the right-arrow button to move it underSelected Systems. You can select one or more systems.
To reject a system, click the system name under Selected Systemsand then click the left-arrow button to move it back under Selectand Add Systems.
The target systemnames
Under Selected Systems, check Startup next to a system name ifyou want the service group to startup automatically on thatsystem.
The startupsystem
Use the up- and down-arrow buttons to the right of the SelectedSystems table to set the order of systems in the list. To changethe position of a system in the list, click the system name in theSelected Systems table and then click the up- or down-arrowbutton to move it up or down in the list.
The system orderof preference
213Administering basic high availability cluster configurationsAdministering service groups
VCS uses the modified system list when you bring a service group online. VCSattempts to bring the service group online on the first system in the systemlist. If you select a different system as the startup system using the Startupoption, VCS attempts the online operation on that system.
If the service group cannot be brought online on the first system or on thedesignated startup system, VCS does one of the following:
■ If the first system is also the startup system, VCS attempts to bring theservice group online on each remaining system in the order listed.
■ If the first system and the startup system are different, VCS attempts tobring the service group online on the first system in the list. If the firstsystem fails, VCS attempts to bring the service group online on eachremaining system in the order listed.
After you finish specifying information in this panel, click Next.
6 In the Resource Configuration panel, specify the following details about theresources that belong to the service group:
Enter the name of any new resources that you want to add to theservice group into the Resource Name text box.
Resource names must conform to the following criteria:
■ Consist of only one string
■ Not contain special characters like . (period) or & (ampersand).
■ Begin with an alphabetic character. The remaining charactersin the name can be letters, digits, hyphens, or underscores.
The memberresource list
If you want the resource to start in an enabled state after theservice group comes online, check Enable Resource. Click AddResource to add the resource to the Resource List.
The resourcestartup state
In the Resource List table, you can edit resource attributes ordelete a resource by clicking ... or X icons in the Edit or Deletecolumns.
The resourceattribute values orresource removal
After you finish specifying information in the Resource Configuration panel,click Next.
Administering basic high availability cluster configurationsAdministering service groups
214
7 If you do not want to link one or more resources, click Finish now to exit thewizard. Otherwise, continuse with step 7.
8 If you want to link one or more resources, provide the following relationshipdetails in the Link/Unlink Resource panel:
On the Parent Resource drop-down menu, specify which resourcemust be brought online after the child resource.
The parentresource
In the Child Resource list box, select which resource must bebrought online first and then click Add Link.
The child resource
After you finish specifying relationship information in this panel, click Finish.
Bringing a service group onlineThis task enables you to manually put a service group into a responsive,functioning state. You can bring a service group online on a specific system, oryou can bring the service group online "anywhere." If you select the Anywhereoption, the service group is brought online on the first available system in thecluster.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be brought online
■ Administrator or operator privileges on the service group to be brought online
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
215Administering basic high availability cluster configurationsAdministering service groups
To bring a service group online
1 View all resources in the required service group.
2 In the Operations menu, click Online.
3 This step is necessary only if the service group's system list has more thanone system.
In the Online Service Group wizard, in the drop-down menu, click the systemon which to bring the service group online, or click Anywhere.
The system choices in this step are populated using the service group's systemlist. The Anywhere option causes the management server to try each systemin the list until it successfully brings the service group online.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Taking a service group offlineThis task enables you to manually put a service group into an unresponsive,nonfunctioning state. You can take a service group offline on a specific system,or you can take the service group offline anywhere. If you select the Anywhereoption, the service group is taken offline on the first system in the cluster onwhich it is found.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be taken offline
■ Administrator or operator privileges on the service group to be taken offline
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
216
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To take a service group offline
1 View all resources in the required service group.
2 On the Operations task menu, click Offline.
3 This step is necessary if only if the service group is online on more than onesystem.
In the Offline Service Group wizard, in the drop-down menu, click the systemon which to take the service group offline, or click Anywhere.
The Anywhere option causes the management server to take the service groupoffline on the first system on which it is found.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Switching a service groupThis task enables you to manually switch a service group to another system inthe cluster.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be switched
■ Administrator or operator privileges on the service group to be switched
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
217Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To switch a service group
1 View all resources in the required service group.
2 In the Operations menu, click Switch.
3 In the Switch Service Group wizard, on the drop-down menu, click thedestination system for the service groupt. Click Anywhere to switch theservice group to any other system in the cluster.
The system choices in this step are populated using the service group's systemlist. The Anywhere option causes the management server to try every othersystem in the list until it successfully brings the service group online.
4 If insufficient room exists on the target system, you can check the Evacuatelower-priorityservicegroups option. This option makes room for the servicegroup being switched by taking lower-priority service groups offline.
5 Click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Migrating a service group (VMware ESX only)Migrate a service group from a virtual machine (VM) on an ESX server to anotherVM on another ESX server. This task is similar to switching a service group, exceptthat the migration is live; the service group incurs no downtime.
Note: The Migrate task is available only for service groups that have at least oneresource of type ESXVirtualMachine.
Note: Before you begin this task, you must be viewing the details of one servicegroup.
Administering basic high availability cluster configurationsAdministering service groups
218
To view the details of one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa state table and a Resources Listing table. The state table indicates the stateof the service group on each system that hosts it in the parent cluster. TheResources Listing table lists all the resources in the service group.
To migrate a service group to another ESX server
1 In the Operations task menu, click Migrate.
2 In the Migrate Service Group wizard panel, in the Select drop-down list, clickthe target VM to which you want to migrate the selected service group.
3 Click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Freezing a service groupThis task enables you to prevent a service group from failing over to anothersystem. Freezing a service group stops all online and offline operations on theservice group.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be frozen
■ Administrator or operator privileges on the service group to be frozen
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
219Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To freeze a service group
1 View all resources in the required service group.
2 In the Operations menu, click Freeze.
3 In the Freeze Service Group wizard, check Freeze Persistently if you wantthe service group to remain frozen until explicitly unfrozen. Otherwise, theservice group unfreezes when either the management server or the VCSManagement Console is restarted.
4 Click OK.
When you successfully freeze a service group, the console adds a red padlockto the status icon for the service group.
5 In the final panel, read the message about the results of the task and thenclick Close.
Unfreezing a service groupThis task enables you to return a frozen service group to a state in which it failsover normally. Unfreezing a service group restarts any pending online or offlineoperations on the service group.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be unfrozen
■ Administrator or operator privileges on the service group to be unfrozen
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
220
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To unfreeze a service group
1 View all resources in the required service group.
2 In the Operations menu, click Unfreeze.
3 In the Unfreeze Service Group wizard, click OK.
When you successfully unfreeze a service group, the console removes the redpadlock from the service group's status icon.
4 In the final panel, read the message about the results of the task and thenclick Close.
Disabling a service groupThis task enables you to prevent a service group from being brought online. Usedisablement to temporarily prevent agents from monitoring a service group ona system while it undergoes maintenance operations.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be disabled
■ Administrator or operator privileges on the service group to be disabled
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
221Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To disable a service group
1 View all resources in the required service group.
2 In the Operations menu, click Disable.
3 In the Disable Service Group wizard, on the drop-down menu, click the systemon which to disable the service group. Click AllSystems to disable the servicegroup on all systems in the cluster.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Enabling a service groupThis task allows you to enable a disabled service group so that it can be broughtonline. If you manually disable a service group during a maintenance procedure,you must first enable it before it can be brought online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be enabled
■ Administrator or operator privileges on the service group to be enabled
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
222
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To enable a service group
1 View all resources in the required service group.
2 In the Operations menu, click Enable.
3 In the Enable Service Group wizard, on the drop-down menu, click the systemon which to enable the service group. Click AllSystems to enable the servicegroup on all systems in the cluster.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Adding a resource to a service groupThis task enables you to add and configure a resource as a member of a servicegroup.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group to whichthe resource is to be added
■ Administrator privileges on the service group to which the resource is to beadded
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
223Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To add a resource to a service group
1 View all resources in the required service group.
2 In the Configuration menu, click Add/Modify Resource.
3 In the Resource Configuration wizard, specify the following details about theresource and the service group:
In the Resource Name text box, enter the name of the resourcethat you want to add to the service group.
Names must consist of only one string and must not containspecial characters like . (period) or _ (underscore).
The resourcename
On theResourceType drop-down menu, click the type of the newresource.
The resource type
If you want the resource to start in an enabled state after theservice group comes online, check Enable Resource.
The resourcestartup state
Click Add Resource to add the resource to the member resourcelist for the service group.
The resource list is used to populate the Resource List table. Inthe Resource List table, you can edit resource attributes or deletea resource by clicking ... or X in the Edit or Delete columns.
The resource listfor the servicegroup
After you finish specifying options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Deleting a resource from a service groupThis task enables you to delete a resource from a service group.
You must have one of the following privileges on the specified objects to performthis task:
Administering basic high availability cluster configurationsAdministering service groups
224
■ Administator privileges on the parent cluster of the service group from whichthe resoure is to be removed
■ Administrator privileges on the service group from which the resource is tobe removed
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To delete a resource from a service group
1 View all resources in the required service group.
2 In the Configuration menu, click Add/Modify Resource.
3 In the Resource Configuration wizard, in the Delete column of the ResourceList table, click X.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Linking resources in a service groupThis task enables you to create links (dependencies) among resources in a servicegroup. Resources are linked two at a time.
A resource often depends upon the running status of another resource. Therefore,the resource on which the other depends must come online before the dependentresource. When you create a link between two resources, you indicate whichresource must come onilne first.
The resource that must come online first is the child resource. It is called the childbecause, in a dependency diagram, it is beneath the dependent resource.
225Administering basic high availability cluster configurationsAdministering service groups
The resource that must come online after the child is the parent resource. It iscalled the parent because, in a dependency diagram, it is above the child.
Links can be recursive: the parent of one dependency can be the child of another.In a service group, several parent-child dependencies exist to ultimately supporta single application resource. In a dependency diagram, this application resourceoccupies the apex of the diagram. Dependency diagrams are also called dependencytrees.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withresources to be linked
■ Administrator privileges on the service group with resources to be linked
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To link two resources
1 View all resources in the required service group.
2 In the Configuration menu, click Link/Unlink Resource.
Administering basic high availability cluster configurationsAdministering service groups
226
3 In the Link/Unlink Resource wizard, specify the following details for theresource link:
In the ParentResource drop-down menu, click the parent resource.This resource is the resource that must be brought online after thechild resource. The Parent Resource menu is populated using theservice group's resource list.
The parentresource
In the Child Resource scroll box, click the child resource. This isthe resource that must be brought online first. The Child Resourcescroll box is populated using the service group's resource list. Thelist is filtered depending upon the selection you make in theParentResource menu.
The childresource
After you select a child resource, click AddLinkto add the link to the CurrentlyLinked resources table.
After you finish specifying options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Viewing resource dependencies in a service groupThis task enables you to view a graphical representation of the dependencies thatexist for a resource.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the service group withresources to be viewed
■ Administrator privilege on the service group with resources to be viewed.
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
227Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To view resource dependencies and get resource information
1 View all resources in the required service group.
2 On the details tab bar, click Dependency.
This action displays a diagram of the selected resource and its dependencies.The diagram is a hierarchical tree that shows all currently configuredresources that have a direct dependency relationship or recursive dependencyrelationship with the resource.
3 If you want to view the diagram in a separate browser window, click Open innew window.
4 Click a resource icon to get information about the resource that it represents.
Unlinking resources in a service groupThis task enables you to remove a link dependency between two resources.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withresources to be unlinked
■ Administrator privileges on the service group with resources to be unlinked
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
228
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To unlink two resources
1 View all resources in the required service group.
2 In the Configuration menu, click Link/Unlink Resource.
3 In the Link/Unlink Resource wizard, in the Currently Linked resources table,click X in the row that corresponds to the link that you want to remove.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Modifying the system list of a service groupThis task enables you to add systems to or remove systems from a service group’ssystem list. The VCS Management Console maintains a list of the systems onwhich a service group is configured. This system list includes only those systemsin the service group's parent cluster. If the service group is configured on morethan one cluster, each instance of the service group has its own system list.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group with thesystem list to be modified
■ Administrator privileges on the service group with the system list to bemodified
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
229Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To modify the system list of a service group
1 View all resources in the required service group.
2 On the Configuration menu, click Modify System List.
3 In the System List Configuration wizard, specify the following details for thetarget systems (the target systems are the systems that can host the servicegroup):
If you want to select systems from a filtered list, click Filter, typea few letters into the text box, and then click Apply. The filterenables you to quickly find a specific system or systems.
Filter or NoFilter
Find the system you want in the table on the left side of the panel.Depending upon whether or not you clicked Filter, this table islabeled Filtered Systems or All Systems. To select a system, clickthe system name in the table and then click the right-arrow to moveit under Selected Systems. You can select one or more systems. Toreject a system, click the system name in the Selected Systems tableand then click the left-arrow. The left-arrow moves the system backinto the table on the left.
The targetsystem names
Under Selected Systems, check the Startup option next to a systemname if you want the service group to startup automatically onthat system.
The startupsystem
Administering basic high availability cluster configurationsAdministering service groups
230
Click the up- and down-arrows to the right of the Selected Systemstable to set the order of systems in the list. VCS attempts to bringthe service group online on the first system in the system list, unlessyou have selected a different system as the startup system usingthe Startup option.
To change the position of a system in the list, click the system namein the Selected Systems table and then click the up- or down-arrow.
If the service group cannot be brought online on the first systemor on the designated startup system, VCS does one of the following:
■ If the first system is also the startup system, VCS attempts tobring the service group online on each remaining system in theorder listed.
■ If the first system and the startup system are different, VCSattempts to bring the service group online on the first systemin the list. If the first system fails, VCS attempts to bring theservice group online on each remaining system in the orderlisted.
The systemorder ofpreference
After you finish specifying systems and options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Faulting a service groupThis task enables you to simulate a fault on a service group to test failoverbehavior. This operation is available only when the service group is part of acluster that is created using the VCS cluster simulator.
See the VCS User's Guide for information about the simulator.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group to be faulted
■ Administrator privileges on the service group to be faulted
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
231Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To fault a service group
1 View all resources in the required service group.
2 On the Simulation menu, click Fault Service Group.
3 In the Fault Service Group wizard, on the drop-down menu, click the systemon which you want to fault the service group.
This menu is populated with the service group’s system list. The system listcontains a list of all systems in the parent cluster on which the service groupis configured.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Clearing a faulted service groupThe Clear Faulted Group task enables you to remove the resource faults within aservice group. After a service group faults, you must clear the fault before youcan bring the service group online. A resource fault in a service group may occurin several situations, such as a power failure or a faulty configuration.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the service group with thefault to be cleared
■ Administrator privilege on the service group with the fault to be cleared
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
232
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To clear a faulted service group
1 View all resources in the required service group.
2 On the Operations menu, click Clear Fault.
3 In the Clear Fault for Service Group wizard, on the drop-down menu, clickthe system on which the service group is faulted. To clear the faulted groupon all systems, click All Systems.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Editing the attributes on a service groupThis task enables you to set the attribute values on a service group.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withattributes to be edited
■ Administrator privileges on the service group with attributes to be edited
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
233Administering basic high availability cluster configurationsAdministering service groups
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To edit a service group attribute
1 View all resources in the required service group.
2 On the details tab bar, click the Properties tab.
3 In the All attributes for groupGroup_Name table, locate the line item for theattribute you want to edit.
Group_Name is replaced with the name of the current group.
4 In the Edit column, click ...(edit) .
5 In the Edit Attribute wizard, specify the following attribute details:
In the Values box, either click a value to change it, or click + (plus)to add a value. Click a value and then click - (minus) to remove avalue.
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute value
After you finish specifying attribute options, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Flushing a service groupThis task enables you to address resource-related problems if they occur while aservice group comes online or goes offline. As a service group comes online orgoes offline, the resources in the group also come online or go offline. If the onlineoperation or offline operation hangs on a particular resource, flush the servicegroup to halt the operation on the remaining resources. Flushing a service group
Administering basic high availability cluster configurationsAdministering service groups
234
typically leaves the cluster in a partial state. Resolve the issue with the particularresource (if necessary) and then proceed with bringing the service group onlineor taking it offline.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupto be flushed
■ Aministrator or operator privileges on the service group to be flushed
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To flush a service group
1 View all resources in the required service group.
2 On the Operations menu, click Flush.
3 In the Flush Service Group wizard, in the drop-down menu, select the systemon which you want to flush the service group.
Thies menu is populated with the service group's system list, which containsthe systems in the parent cluster on which the service group is configured.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
235Administering basic high availability cluster configurationsAdministering service groups
Adding a RemoteGroup resource to a service groupThis task enables you to add a special resource to a local service group. This specialresource allows you to manage and monitor remote service groups. The resourcetype is RemoteGroup, and the resource is called a RemoteGroup resource.
For each service group that is configured in a remote cluster, you can create acorresponding RemoteGroup resource in the local service group. When you createa RemoteGroup resource, you also create a dependency between that resourceand a specific service group in the remote cluster.
Symantec recommends that you configure a RemoteGroup resource when a localservice group depends on the state of a remote service group. For example, a webserver application that runs in a local cluster is often dependant upon a databaseapplication that runs in a remote cluster.
A RemoteGroup resource monitors the state of a remote service group. After youadd the RemoteGroup resource to the local service group, you link that resourceto the other resources in the local service group. The result is a dependencybetween the local service group and the remote service group.
The Remote Group Resource Configuration wizard creates the RemoteGroupresource and the dependency on the remote service group. However, you can alsouse the RemoteGroup agent to perform this task.
See theVeritasClusterServerBundledAgentsReferenceGuide for more informationon the RemoteGroup agent.
See "Configuring the RemoteGroup agent" in the VCS User's Guide.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the local service group
■ Administrator privileges on the local service group
Note:Before you begin this task, you must view all resources in one service group.
To view all resources in one service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering basic high availability cluster configurationsAdministering service groups
236
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required service groupand then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysa State information on member Systems table and a Resources Listing table.The state table indicates the state of the service group on each system thathosts it in the parent cluster. The Resources Listing table lists all the resourcesin the service group.
To configure a remote group resource on a local service group
1 View all resources in the required service group.
2 On the Configuration menu, click Add Remote Group Resource.
3 In the Remote Group Resource Configuration wizard, read the introductoryinformation and then click Next.
4 In the RemoteGroup Resource panel, in the RemoteGroup Resource Namebox, enter a name and then click Next.
5 In the Remote Cluster Authentication panel, enter the host IP address andall of the required user authentication information. If the remote cluster isconfigured in secure mode, check Select to enter domain name for SecureCluster and then specify the following:
■ The name of the domain to which the remote cluster belongs
■ The domain type
■ The IP address of the cluster's authentication broker
6 In the Create RemoteGroup Resource panel, specify the following:
In the Remote Service Group drop-down menu, click the remoteservice group. This menu is populated with the service groupsthat are configured in the remote cluster that you specified.
The remote servicegroup
In the Type of Monitoring drop-down menu, click one of thefollowing:
■ OnlineOnly: The RemoteGroup resource only brings theremote service group online. The RemoteGroup resourcecannot take the remote service group offline.
■ MonitorOnly: The RemoteGroup resource only monitors thestate of the remote service group. The RemoteGroup resourcecannot online or offline the remote service group.
■ OnOff: The RemoteGroup resource brings the remote servicegroup online or takes it offline.
The type ofmonitoring youwant to perform
237Administering basic high availability cluster configurationsAdministering service groups
The System Based Monitoring Details setting has two options,Any and One-to-One Mapping. See the Veritas Cluster ServerBundled Agents Reference Guide for information on this setting.
The monitoringdetails
After you configure the RemoteGroup resource, click Finish. You can viewthe service group dependency on the Dependency tab on the details tab bar.
See “Viewing resource dependencies in a service group” on page 227.
7 Create the appropriate dependencies among the resources in the local servicegroup and the new RemoteGroup resource.
Administering systemsSystems are the hardware computer nodes that make up a cluster.
The systems administration pages of the VCS Management Console enable youto do the following:
■ Collectively administer multiple systems: In a multiple system administrationpage, one task can affect one or more systems that you select from a list in thedetails pane.
■ Singly administer individual systems: In an individual system administrationpage, a task can affect only the system that is currently described in the detailspane.
The tasks that you can perform differ in each type of system administration page.
Note:You can always perform a task on an individual system in a multiple systemadministration page by selecting only one system in a table. However, not allindividual system administration tasks are available in a multiple systemadministration page.
Administering multiple systemsMultiple system administration tasks include the following:
■ Editing attributes of selected systems
■ Freezing selected systems
■ Unfreezing selected systemss
The system-related task "Adding a system to a cluster" is part of clustermanagement.
See “Administering an individual cluster” on page 184.
Administering basic high availability cluster configurationsAdministering systems
238
Tasks for collectively administering multiple systems are available when you areviewing all systems in the enterprise, all systems in a site, or all systems in acluster.
Sites generally contain a manageable number of systems. The example proceduresin this section conduct the system management tasks in the context of a site (witha site selected). If a system management task is not available on the site menus,the next most convenient context (a cluster, for example) is used.
About Systems Listing tablesPages on the Manage tab that list all configured systems in the enterprise, in asite, or in a cluster contain a Systems Listing table. The following are the columnsand data in a Systems Listing table:
Contains the name of the system. The system name is also a link tothe details status page for the system
Name
Contains the cumulative, effective state of the service group
See “About object states and consolidated states” on page 22.
State
Contains the operating system that the system runs.Platform
Contains various logged status information.Other info
Editing attributes of selected systemsThis task enables you to edit attributes on selected systems in a one-to-manyfashion (one action modifies many systems).
To perform this task, you must have administrator privileges on the parent clusterof the system with attributes to be edited.
Note:Before you begin this task, you must be viewing all systems in the enterprise,all systems in a site, or all systems in a cluster.
To view all systems in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
On the details tab bar, this action selects the Systems tab by default anddisplays a Systems Listing table of all systems in the site.
239Administering basic high availability cluster configurationsAdministering systems
To edit system attributes
1 View all systems in the required site.
2 In the Systems Listing table, do one of the following:
■ To select one or more systems, check the check box next to each requiredsystem.
■ To select all systems, check the check box at the top of the table.
3 In the Configuration menu, click Edit attributes.
4 In the Edit Attribute wizard, specify the following attribute details:
In the Attribute Name drop-down menu, click the attribute that youwant to edit.
The attributename
In the Values box, either click a value to change it, or click + (plus)to add a value. To remove a value, click a value and then click -(minus) .
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute
After you finish specifying options, click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Freezing selected systemsThis task enables you to temporarily isolate a system from the managed enterprise.
This task enables you to place a system into a state in which it is all of thefollowing:
■ Active
■ Not monitored
■ Not able to change state
■ Not able to fail over any of the service groups it contains to another system
You can perform this task in a one-to-many fashion (one action modifies manysystems). The Freeze task is useful while a system undergoes maintenance. Use
Administering basic high availability cluster configurationsAdministering systems
240
this task whenever you want to stop VCS but do not want the service groups thatit contains to fail over to another system.
During the time that a system is frozen, it is running, but not the applicationsthat is hosts are not highly available. Do not unfreeze a service group until VCShas been restarted.
To perform this task, you must have administrator privilege on the parent clusterof the systems to be frozen.
Note:Before you begin this task, you must be viewing all systems in the enterprise,all systems in a site, or all systems in a cluster.
To view all systems in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
On the details tab bar, this action selects the Systems tab by default anddisplays a Systems Listing table of all systems in the site.
To freeze selected systems
1 In the Systems Listing table, do one of the following:
■ To select one or more systems, check the check box next to each requiredsystem.
■ To select all systems, check the check box at the top of the table.
2 In the Operations menu, click Freeze.
3 In the Freeze System(s) wizard, if you want the service group to remain frozenuntil explicitly unfrozen, check Freeze Persistently.
Otherwise, the service group unfreezes when either the management serveror the VCS Management Console is restarted.
4 Click OK.
When you successfully freeze the selected systems, the console adds a redpadlock to the status icon for each system.
5 In the final panel, read the message about the results of the task and thenclick Close.
241Administering basic high availability cluster configurationsAdministering systems
Unfreezing selected systemsThe Unfreeze task enables you to unfreeze a frozen a system.
To perform this task, you must have administrator privilege on the parent clusterof the systems to be unfrozen.
Note:Before you begin this task, you must be viewing all systems in the enterprise,all systems in a site, or all systems in a cluster.
To view all systems in a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Click the required site.
On the details tab bar, this action selects the Systems tab by default anddisplays a Systems Listing table of all systems in the site.
To unfreeze selected systems
1 In the Systems Listing table, do one of the following:
■ To select one or more systems, check the check box next to each requiredsystem.
■ To select all systems, check the check box at the top of the table.
2 In the Operations menu, click Unfreeze.
3 In the Unfreeze System(s) wizard, click OK.
When you successfully unfreeze the selected systems, the console removesthe red padlock from the status icon for each system.
4 In the final panel, read the message about the results of the task and thenclick Close.
Administering an individual systemIndividual system administration tasks include the following:
■ Freezing a system
■ Unfreezing a system
■ Editing the attributes on a system
Administering basic high availability cluster configurationsAdministering systems
242
Tasks for administering an individual system are available when you are viewingthe details of one system.
Freezing a systemThe Freeze task enables you to prevent the service groups that it hosts from failingover to another system. Use this procedure before performing a system upgrade.
To perform this task, you must have administrator or operator privilege on theparent cluster of the system to be frozen.
Note: Before you begin this task, you must view the details of one system.
To view the details of one system
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required system andthen click the system.
On the details tab bar, this action selects the Status tab by default. The Statustab contains a groups listing table that indicates the state of all service groupsthat are configured on this system."
To freeze a system
1 In the Operations menu, click Freeze.
2 In the Freeze System wizard, check one or both of the following options:
■ Select Evacuateall online servicegroups if you want the system’s activeservice groups to fail over to another system in the cluster before thefreezing operation takes place.
■ Check FreezePersistently if you want the system to retain a frozen statewhen the cluster is rebooted.
After you finish specifying options, click OK.
When you freeze the a system, the console adds a red padlock to the statusicon for the system.
3 In the final panel, read the message about the results of the task and thenclick Close.
243Administering basic high availability cluster configurationsAdministering systems
Unfreezing a systemthe Unfreeze task enables you to unfreeze a frozen system.
To perform this task, you must have administrator or operator privilege on theparent cluster of the system to be unfrozen.
Note: Before you begin this task, you must be viewing the details of one system.
To view the details of one system
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required system andthen click the system.
On the details tab bar, this action selects the Status tab by default. The Statustab contains a groups listing table that indicates the state of all service groupsthat are configured on this system."
To unfreeze a system
1 In the Operations menu, click Unfreeze.
2 In the Unfreeze System wizard, click OK.
When you unfreeze a system, the console removes the red padlock from thestatus icon for the system.
3 In the final panel, read the message about the results of the task and thenclick Close.
Editing the attributes on a systemThis task enables you to edit the attributes of a system.
To perform this task, you must have administrator privilege on the parent clusterof the system with attributes to be edited
Note: Before you begin this task, you must be viewing the details of one system.
To view the details of one system
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Systems tab.
Administering basic high availability cluster configurationsAdministering systems
244
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required system andthen click the system.
On the details tab bar, this action selects the Status tab by default. The Statustab contains a groups listing table that indicates the state of all service groupsthat are configured on this system."
To edit a cluster attribute using the attribute table
1 On the details tab bar, click Properties.
2 In the All attributes for system System_Name table, locate the line item forthe attribute you want to edit. Not all attributes can be edited.
System_Name is replaced with the name of the system that is currentlyselected in the navigation tree.
3 In the Edit column, click ... (edit).
4 In the Edit Attribute wizard, specify the following attribute details:
In the Values box, either click a value to change it, or click + (plus)to add a value. To remove a value, click a value and then click -(minus) .
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute
After you finish specifying attribute options, click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Administering resourcesResources are the most basic elements of a service group.
The resource administration pages of the VCS Management Console enable youto do the following:
■ Collectively administer multiple resources: In a multiple resourceadministration page, one task can affect one or more resources that you selectfrom a list in the details pane.
245Administering basic high availability cluster configurationsAdministering resources
■ Singly administer individual service groups: In an individual service groupsadministration page, a task can affect only the resource that is currentlydescribed in the details pane.
The tasks that you can perform differ in each type of resource administrationpage.
Note: You can always perform a task on an individual resource in a multipleresource administration page by selecting only one resource in a table. However,not all individual service group administration tasks are available in a resourceadministration page.
Administering multiple resourcesMultiple resource administration tasks include the following:
■ Clearing faults on selected resources
■ Enabling resources
■ Disabling resources
■ Marking resources as critical
■ Marking resources as non-critical
Tasks for collectively administering multiple resources are available when youare viewing all resources in a cluster.
About Resources Listing tablesPages on the Manage tab that list all configured resources in a cluster or in aservice group contain a Resources Listing table. The following are the columnsand data in a Resources Listing table:
Contains the name of the resource. The resource name is also a linkto the resource details.
Name
Indicates the resource type. The resource type is also a link to theresource type details.
Type
Contains the cumulative, effective state of the resource.
See “About object states and consolidated states” on page 22.
State
Contains one of the values True or False, which indicate whether ornot the resource is enabled.
Enabled
Administering basic high availability cluster configurationsAdministering resources
246
Contains one of the values True or False, which indicate whether ornot the resource is critical. A critical resource is
Critical
Contains the parent service group of the resource. The parent servicegroup name is also a link to the service group details.
Group
Contains various logged status information.Other info
Clearing faults on selected resourcesThis task enables you to clear a fault on selected resources in a one-to-manyfashion (one action modifies many resources).
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the resources
■ Administrator privilege on the parent service group of the resources
■ Operator privilege on the parent cluster of the resources
■ Operator privilege on the parent service group of the resources
Note: Before you begin this task, you must be viewing all resources in a cluster.
To view all resources in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
5 On the details tab bar, on the Status tab, click the Resources detail link.
This action displays a Resources Listing table of all resources in the cluster.
To clear a fault on one or more resources
1 In the Resources Listing table, do one of the following:
■ To select one or more resources, check the check box next to each requiredresource.
■ To select all resources, check the check box at the top of the table.
2 In the Operations menu, click Clear Fault.
247Administering basic high availability cluster configurationsAdministering resources
3 In the Clear Resource(s) Faults wizard, click OK to confirm that you want toclear the faults on the selected resources.
4 In the final panel, read the message about the results of the task and thenclick Close.
Enabling selected resourcesThis task allows you to enable selected resources in a one-to-many fashion (oneaction modifies many resources). Resources cannot come online until they areenabled.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the resources
■ Administrator privilege on the parent service group of the resources
■ Operator privilege on the parent cluster of the resources
■ Operator privilege on the parent service group of the resources
Note: Before you begin this task, you must be viewing all resources in a cluster.
To view all resources in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
5 On the details tab bar, on the Status tab, click the Resources detail link.
This action displays a Resources Listing table of all resources in the cluster.
To enable one or more resources
1 In the Resources Listing table, check the check box next to each requiredresource.
Check only those resources that have the valueFalse in the Enabled column.
2 In the Operations menu, click Enable Resources.
Administering basic high availability cluster configurationsAdministering resources
248
3 In the Enable Resource(s) wizard, click OK to confirm that you want to enablethe resource.
4 In the final panel, read the message about the results of the task and thenclick Close.
Disabling selected resourcesThis task enables you to disable selected resources in a one-to-many fashion (oneaction modifies many resources). Disabled resources cannot come online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the resources
■ Administrator privilege on the parent service group of the resources
■ Operator privilege on the parent cluster of the resources
■ Operator privilege on the parent service group of the resources
Note: Before you begin this task, you must be viewing all resources in a cluster.
To view all resources in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
5 On the details tab bar, on the Status tab, click the Resources detail link.
This action displays a Resources Listing table of all resources in the cluster.
To disable one or more resources
1 In the Resources Listing table, check the check box next to each requiredresource.
Check only those resources that have the value True in the Enabled column.
2 In the Operations menu, click Disable Resources.
3 In the Disable Resource(s) wizard, click OK to confirm that you want to disablethe enabled resource.
4 In the final panel, read the message about the results of the task and thenclick Close.
249Administering basic high availability cluster configurationsAdministering resources
Making selected resources criticalThis task enables you to make selected resources critical in a one-to-many fashion(one action modifies many resources). A critical resource causes its parent servicegroup to fault whenever the resource, or any resource that it depends upon, faults.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the resources
■ Administrator privilege on the parent service group of the resources
■ Operator privilege on the parent cluster of the resources with faults
■ Operator privilege on the parent service group of the resources with faults
Note: Before you begin this task, you must be viewing all resources in a cluster.
To view all resources in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
5 On the details tab bar, on the Status tab, click the Resources detail link.
This action displays a Resources Listing table of all resources in the cluster.
To make one or more non-critical resources critical
1 In the Resources Listing table, check the check box next to each requiredresource.
Check only those resources that have the value False in the Critical column.
2 In the Operations task menu, click Make Non-Critical.
3 In the Make Resource(s) Critical wizard, click OK to confirm that you wantto make the non-critical resource critical.
4 In the final panel, read the message about the results of the task and thenclick Close.
Marking selected resources as non-criticalThis task enables you to make selected critical resources non-critical in aone-to-many fashion (one action modifies many resources).
Administering basic high availability cluster configurationsAdministering resources
250
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privilege on the parent cluster of the resources
■ Administrator privilege on the parent service group of the resources
■ Operator privilege on the parent cluster of the resources
■ Operator privilege on the parent service group of the resources
Note: Before you begin this task, you must be viewing all resources in a cluster.
To view all resources in a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required cluster and then click thecluster.
5 On the details tab bar, on the Status tab, click the Resources detail link.
This action displays a Resources Listing table of all resources in the cluster.
To make one or more critical resources non-critical
1 In the Resources Listing table, check the check box next to each requiredresource.
Check only those resources that have the value True in the Critical column.
2 In the Operations task menu, click Make Non-Critical.
3 In the Make Resrouce(s) Non-Critical wizard, click OK to confirm that youwant to make the critical resource non-critical.
4 In the final panel, read the message about the results of the task and thenclick Close.
Administering an individual resourceIndividual resource administration tasks include the following:
■ Deleting a resource
■ Overriding resource attributes
■ Removing resource attribute overrides
■ Bringing a resource online
251Administering basic high availability cluster configurationsAdministering resources
■ Taking a resource offline
■ Clearing a fault on a resource
■ Probing a resource
■ Taking a resource offline and propagating the state
■ Enabling a resource
■ Disabling a resource
■ Refreshing the ResourceInfo attribute
■ Faulting a resource
■ Clearing the ResourceInfo attribute
■ Invoking a resource action
The following resource-related tasks are part of service group management:
■ Adding a resource to a service group
■ Linking resources in a service group
■ Unlinking resources in a service group
■ Viewing resource dependencies in a service group
See “Administering an individual service group” on page 210.
Tasks for administering an individual resource are available when you are viewingthe details of one resource.
Deleting a resourceThis task enables you to delete a resource from membership in a service group.
Although this task is offered here as part of managing a single resource, it is alsopart of service group management. The service group administration task describesan alternate procedure.
See “Deleting a resource from a service group” on page 224.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withresources to be deleted
■ Administrator privileges on the service group with resources to be deleted
Note: Before you begin this task, you must view the details of one resource.
Administering basic high availability cluster configurationsAdministering resources
252
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To delete a resource from a service group
1 View the details of the required resource.
2 In the Configuration menu, click Delete Resource.
3 In the Delete Resource wizard, click OK to confirm that you want to deletethe resource.
4 In the final panel, read the message about the results of the task and thenclick Close.
Overriding resource attributesThis task enables you to change the default value of one or more resourceattributes.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withresources that have attributes to be overridden
253Administering basic high availability cluster configurationsAdministering resources
■ Administrator privileges on the service group with resources that haveattributes to be overridden
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To override resource attributes
1 View the details of the required resource.
2 In the Configuration menu, click Override Attributes.
3 In the Override Attributes wizard, in the drop-down menu, click the attributethat you want to override and then click OK.
Administering basic high availability cluster configurationsAdministering resources
254
4 In the Edit Attribute wizard, specify the following attribute details:
In the Values box, either click a value to change it, or click + (plus)to add a value. To remove a value, click a value and then click -(minus) .
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute value
After you finish specifying attribute options, click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Removing resource attribute overridesThis task enables you to remove any override values on a resource’s attributesand set them back to the default values.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group withresources that have attribute overrides to be removed
■ Administrator privileges on the service group with resources that have attributeoverrides to be removed
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
255Administering basic high availability cluster configurationsAdministering resources
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To remove resource overrides
1 View the details of the required resource.
2 In the Configuration menu, click Remove Attribute Overrides.
3 Click OK to confirm that you want to remove previously configured overridevalues.
Enabling a resourceThis task allows you to prepare a resource to be brought online. A resource mustbe enabled before it can be brought online. A disabled resource cannot be broughtonline.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be enabled
■ Administrator or operator privileges on the service group with the resourceto be enabled
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
Administering basic high availability cluster configurationsAdministering resources
256
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To enable a resource
1 View the details of the required resource.
2 In the Operations menu, click Enable.
3 In the Enable Resource wizard, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Disabling a resourceThis task enables you to prevent a resource from being brought online. A resourcemust be enabled before it can come online. A disabled resource cannot come online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be disabled
■ Administrator or operator privileges on the service group with the resourceto be disabled
Note: Before you begin this task, you must view the details of one resource.
257Administering basic high availability cluster configurationsAdministering resources
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To disable a resource
1 View the details of the required resource.
2 In the Operations menu, click Disable.
3 In the Disable Resource wizard, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Bringing a resource onlineThis task enables you to manually bring a resource online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be brought online
■ Administrator or operator privileges on the service group with the resourceto be brought online
Administering basic high availability cluster configurationsAdministering resources
258
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To bring a resource online
1 View the details of the required resource.
2 In the Operations menu, click Online.
3 In the Online Resource wizard, in the drop-down menu, click the system onwhich to bring the resource online.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Taking a resource offlineThis task enables you to manually take a resource offline.
You must have one of the following privileges on the specified objects to performthis task:
259Administering basic high availability cluster configurationsAdministering resources
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be taken offline
■ Administrator or operator privileges on the service group with the resourceto be taken offline
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To take a resource offline
1 View the details of the required resource.
2 In the Operations menu, click Offline.
3 In the Offline Resource wizard, in the drop-down menu, click the system onwhich to take the resource offline.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Administering basic high availability cluster configurationsAdministering resources
260
Taking a resource offline and propagating the stateThis task enables you to take a resource and all of its dependents offline. Whenyou take the parent resource offline, the offline state propagates to the childresources. This task also offers an option that enables you to take only a resource'schild resources offline.
This task is disabled if any of the following conditions exist:
■ The resource does not depend on any other resource
■ An online resource depends on this resource
■ The resource is not online
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be taken offline with state propagation
■ Administrator or operator privileges on the service group with the resourceto be taken offline with state propagation
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
261Administering basic high availability cluster configurationsAdministering resources
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To take a parent resource and all of its child resources offline
1 View the details of the required resource.
2 In the Operations menu, click Offline Propagate.
3 In the Offline Propagate for Resource wizard, in the drop-down menu, clickthe system on which to take the resource offline.
4 If you want to take only the resource's children offline, check Ignoreparent.
5 Click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Faulting a resourceThis task enables you to simulate a fault on a resource to test failover behavior.This task if available only if the simulator is installed.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator priivileges on the parent cluster of the service groupwith the resource to be faulted
■ Administrator or operator privileges on the service group with the resourceto be faulted
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
Administering basic high availability cluster configurationsAdministering resources
262
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To fault a resource
1 View the details of the required resource.
2 In the Simulation menu, click Fault Resource.
3 In the Fault Resource wizard, in the drop-down menu, select the system onwhich you want to fault the resource.
This drop-down menu is populated using the system list of the resource. Thesystem list of a resource contains all systems on which the resource isconfigured.
4 Click OK.
5 In the final panel, read the message about the results of the task and thenclick Close.
Clearing a fault on a resourceThis task enables you to remove a fault and make the resource available to bebrought online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource that has a fault to be cleared
■ Administrator or operator privileges on the service group with the resourcethat has a fault to be cleared
Note: Before you begin this task, you must view the details of one resource.
263Administering basic high availability cluster configurationsAdministering resources
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To clear a fault on a resource
1 View the details of the required resource.
2 In the Operations menu, click Clear Fault.
3 In the Clear Fault wizard, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Probing a resourceThis task enables you to confirm that a resource is properly configured and readyto bring online.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privileges on the parent cluster of the service groupwith the resource to be probed
Administering basic high availability cluster configurationsAdministering resources
264
■ Administrator or operator privileges on the service group with the resourceto be probed
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To probe a resource
1 View the details of the required resource.
2 In the Operations menu, click Probe.
3 In the Probe Resource wizard, in the drop-down menu, click the system onwhich you want to probe the resource and then click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Success indicates that the resource is properly configured and is ready to bebrought online.
265Administering basic high availability cluster configurationsAdministering resources
Editing the attributes on a resourceThis task enables you to edit the attributes of a resource.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group with theresource to be deleted
■ Administrator privileges on the service group with the resource to be deleted
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To edit a resource attribute using the attribute table
1 View the details of the required resource.
2 On the details tab bar, click Properties.
Administering basic high availability cluster configurationsAdministering resources
266
3 In the All attributes for resource Resource_Name table, locate the row thatcontains the required attribute.
Resource_Name is replaced with the name of the resource.
4 In the Edit column, click ... (edit).
5 In the Edit Attribute wizard, specify the following attribute details:
In the Values box, either click a value to change it, or click + (plus)to add a value. To remove a value, click a value and then click -(minus) .
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute value
After you finish specifying attribute options, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Invoking a resource actionThis task enables you to run a predefined script that performs an action on aresource. Examples of predefined resource actions are splitting disk groups andjoining disk groups.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator or operator privielges on the parent cluster of the service groupwith the resource to be acted upon
■ Administrator or operator privileges on the service group with the resourceto be acted upon
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
267Administering basic high availability cluster configurationsAdministering resources
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To invoke a resource action
1 View the details of the required resource.
2 In the Operations menu, click Invoke Action.
3 In the Invoke Action wizard, select the script that you want to run and thesystem on which you want to run it.
4 Specify arguments for the action
To add arguments, click + (plus). To remove arguments, click an argumentname and then click –(minus).
5 Click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Refreshing the ResourceInfo attributeThis task enables you to view the latest parameter values of the ResourceInfoattribute.
You must have one of the following privileges on the specified objects to performthis task:
Administering basic high availability cluster configurationsAdministering resources
268
■ Administrator privileges on the parent cluster of the service group with theresource that has the ResourceInfo attribute
■ Administrator privileges on the service group with the resource that has theResourceInfo attribute
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To refresh the ResourceInfo attribute
1 View the details of the required resource.
2 In the Operations menu, click Refresh Resource Info.
3 In the Refresh Resource Info wizard, in the drop-down menu, click the systemon which you want to refresh the ResourceInfo attribute and then click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
269Administering basic high availability cluster configurationsAdministering resources
Clearing the ResourceInfo attributeThis task enables you to reset all the parameters in the ResourceInfo attribute.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group with theresource that has the ResourceInfo attribute
■ Administrator privileges on the service group with the resource that has theResourceInfo attribute
Note: Before you begin this task, you must view the details of one resource.
To view the details of one resource
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and then click the cluster that contains therequired resource.
5 On the details tab bar, on the Status tab, click the Resources detail link.
6 In the Resources Listing table, click the required resource.
This action displays a resource details page that contains the following fivetables:
■ A table that lists the important attributes for the resources and whichenables attribute editing
■ A table that indicates the state of the resource on the systems on whichit is configured.
■ A table that lists any overridden attributes for the resource
■ A table that lists any parent resources that are linked to (share adependency with) the currently selected resource
■ A table that lists any child resources that are linked to the currentlyselected resource.
To clear and reset the parameters of the ResourceInfo attribute
1 View the details of the required resource.
2 In the Operations menu, click Clear Resource Info.
Administering basic high availability cluster configurationsAdministering resources
270
3 In the Clear Resource Info wizard, select the system on which you want toclear the ResourceInfo attribute and then click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Administering resource typesThe resource type administration pages of the VCS Management Console enableyou to view and edit the attributes of resource types. Resource types are predefined.
About the Resource Types Listing tableThe Resource Types Listing table is available when viewing the details of onecluster and displays all resource types in the cluster. The following are the columnsand data in the Resource Types Listing table:
Indicates the name of the resource type and links to a table of theresource type properties
Resource Type
Links to the Resource Type Details table.Status of resources
Indicates the number of resources of this type that are onlineOnline
Indicates the number of resources of this type that are offlineOffline
Indicates the number of resources of this type that are faultedFaulted
Indicates the total number of resources of this type in the clusterTotal
About the Resource Type Details tableThe Resource Type Details table is available when viewing the details of oneresource type. The following are the columns and data in the Resource Type Detailstable:
Indicates the name of the resources of the type that are present in theparent cluster and links to the Resource Status page.
Resource Name
Indicates the parent service group of the resource in the ResourceName column and links to the Service Group Status page.
Service Group
Indicates the state of the resource and on which system the resourceis configured in the parent cluster.
State
271Administering basic high availability cluster configurationsAdministering resource types
Editing attributes of a resource typeThe only management task available or necessary for a resource type is to editthe resource type attributes.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of service group with resourcesof the type that has attributes to be edited
■ Administrator privileges on the service group with resources of the type thathas attributes to be edited
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To edit resource type attributes
1 View all service groups in the required cluster.
2 On the details tab bar, on the Status tab, click the ResourceTypes detail link.
3 In the Resource Types Listing table, in the Resource Type column, click alinked resource type name.
4 In the All attributes for type Resource_Type_Name table, locate the row thatcontains the required attribute. Not all attributes can be edited.
Resource_Type_Name is replaced with the name of the resource type.
5 In the Edit column, click ... (edit) .
Administering basic high availability cluster configurationsAdministering resource types
272
6 In the Edit Attribute wizard, specify the following attribute details:
In the Values box, either click a value to change it, or click + (plus)to add a value. To remove a value, click a value and then click -(minus) .
You can enter more than one value for some attributes. Click theup- and down-arrows to scroll among multiple values.
The attributevalue
Specify a setting for the Apply value to option. To apply the changesto all systems in the System List, which lists all systems on whichthe attribute is configured, click Apply to all nodes. If you want toselect systems (nodes) in the System List, click Apply to selectednodes.
The systems onwhich tochange theattribute value
After you finish specifying attribute options, click OK.
7 In the final panel, read the message about the results of the task and thenclick Close.
Viewing resource type statusThis task enables you to view the status of a resource in each service group andon each system in which it is configured.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of service group with resourcesof the type that has attributes to be edited
■ Administrator privileges on the service group with resources of the type thathas attributes to be edited
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
273Administering basic high availability cluster configurationsAdministering resource types
To verify the status of a resource type
1 View all service groups in the required cluster.
2 On the Status details tab, click the Resource Types detail link.
3 In the Resource Types Listing table, in the Status of Resources column, clickthe link that corresponds to the required resource type.
This action displays the Resource Type Resource_Type_NameDetails table.
Resource_Type_Name is replaced with the name of the resource type.
See “About the Resource Type Details table” on page 271.
Viewing logsThe VCS Management Console records log entries for all operations andconfigurational changes.
About the logging mechanismThe VCS Management Console management server has a persistent connectionto a managed cluster whether it is connected through a direct connection orthrough the cluster connector.
See “About the management server” on page 20.
The management server listens for updates from the cluster. These updates consistof changes to objects and to logs. As soon as VCS notifies all listeners, it sends logentries to the engine log, engine_A.log, and to the console.
In this logging mechanism, the cluster sends the log message to the consolethrough a direct connection. The console then puts each log message into boththe database and into the search index.
Viewing logs for cluster objectsThe Logs tabs on the management tab enable you to view logs for all managedcluster objects.
The details tab bar contains a Logs tab when you are viewing the details of thefollowing cluster objects:
■ Cluster
■ Service group
■ System
Administering basic high availability cluster configurationsViewing logs
274
■ Resource
The Logs tab takes you to a Logs Listing table that lists log entries about theindividual object.
To view logs for a cluster object
1 In the navigation tree or in a table, click any cluster, service group, system,or resource.
2 On the details tab bar, click the Logs tab.
Each Logs tab contains a Search control group that enables you to quicklyfind log entries.
SearchingThe search feature uses text-based comparison. You can perform a search usingeither the search bar or the Search tab.
The search bar is located immediately below the main tab bar, and contains a textentry box. (On some systems, you may need to scroll the screen to the right to seethese controls.) The search bar is available for all pages except those on the Searchtab.
The Search tab is located on the main tab bar. Pages on the Search tab contain atext entry box and offer some filtering options that the search bar does not.
The search feature displays results in one or more of the search pages. You navigateto the search pages using the details tabs on the Search tab. These tabs are labeledClusters, Groups, Systems, Resources, Resource Types, and Logs. Each tab containsa table that lists the search results, or hits, in the corresponding object category.By default, the console takes you to the search pages after each search. Thedestination page is whichever page was most recently visited.
The console limits searches to text strings. Use a space character to separate twoor more strings.
The search feature does not currently support the following:
■ Direct textual entry of Boolean operators
■ Direct textual entry of wildcards
■ Query expressions
275Administering basic high availability cluster configurationsSearching
To perform a search using the search bar
1 In the text entry box, type one or more text strings that you want to find.
Use a space character to separate text strings.
2 Click Search.
3 Visit each search view to see the hits in each object category.
Your particular destination page depends on which search page was mostrecently visited. Click the other secondary tabs (Clusters, Groups, and so on)to visit the other search pages.
To perform a search using the Search tab
1 On the main tab bar, click Search.
2 On the secondary tab bar, click the object category (Clusters, Groups, and soon) in which you want to begin your search.
3 In the text entry box, type one or more text strings that you want to find.
Use a space character to separate text strings.
4 Check one or more of the following options:
Requires each search result to match at least one whole searchstring. This option excludes occurrences in which a search stringis part of a longer string.
Exact Match
Requires each search result to match all search terms (strings).
Combine Exact Match and Match All Terms to minimize the numberof candidate occurrences.
Match All Terms
Highlights the string occurrences in the search result tables.Highlight
The behavior of the Match All Terms option depends on the setting of theExact Match option according to the following example:
Consider object1 with attribute path = /tmp/f3 and object2 with attributepath = /tmp/f4:
path f3path f3path f3path f3Search strings
clearedclearedcheckedcheckedExact match option settings
clearedcheckedclearedcheckedMatch all terms option settings
object1, object2object1nonenoneSearch results
Administering basic high availability cluster configurationsSearching
276
5 Click Search.
6 Visit each search page to see the hits in each object category.
Your first results are displayed in the same page in which you started thesearch. Click the other details tabs (Clusters, Groups, and so on) to see anyhits the other search pages.
After you perform a search, changing the Exact Match, Match All Terms, andHighlight option settings automatically updates the results.
277Administering basic high availability cluster configurationsSearching
Administering basic high availability cluster configurationsSearching
278
Administering VCS globalcluster configurations
This chapter includes the following topics:
■ About VCS global clusters
■ VCS global cluster task terminology
■ About creating global service groups
■ About the Status tab for global clusters and service groups
■ Administering global clusters
■ Administering global service groups
■ Deleting a remote cluster from a local cluster
■ Administering global heartbeats
■ Migrating a site (local site disaster recovery)
■ Recovering a failed site (remote site disaster recovery)
About VCS global clustersVCS global cluster technology is a central feature of VCS high availability disasterrecovery (HA/DR). Part of VCS HA/DR uses objects called global clusters andglobal service groups to achieve remote, cross-cluster failover. Global clustersand global service groups have corresponding remote clusters and remote servicegroups configured at a distant geographic location.
9Chapter
Table 9-1 VCS global cluster objects
DescriptionVCS global cluster object
A global cluster contains at least one global servicegroup.
Global cluster
A global service group is a service group that has beenreplicated and configured on one or more remoteclusters.
Global service group
A remote cluster is a cluster that is specificallyconfigured as a failover target for a global servicegroup.
Remote cluster
A remote cluster contains a remote service group,which is the replicated global service group.
Remote service group
If failover within the local cluster is not possible, a global service group fails overto its preconfigured remote cluster.
See "Connecting clusters—creating global clusters" in the VCS User's Guide forinformation about creating, configuring, and maintaining global clusters andservice groups using VCS.
Note: Remote clusters are usually configured far away from their correspondingglobal clusters.
VCS global cluster task terminologyIn a VCS global cluster configuration, a global cluster is at the local site and itscorresponding remote cluster is at a remote site. At least one global service groupis configured in the global cluster. At least one remote service group is configuredas the global service group's failover target in the remote cluster.
In the context of the global cluster management task descriptions, global andremote have the following definitions:
Global indicates the following:
■ The cluster or the service group is configured at the local site
■ The cluster or the service group is also configured with a specific failovertarget cluster or failover target group at a distant remote site
Global
Administering VCS global cluster configurationsVCS global cluster task terminology
280
Remote indicates the following:
■ The cluster or the service group is configured at a distant site, far awayfrom the local site
■ The cluster or the serivce group is configured as a failover target for itsglobal counterpart
Remote
The terms are switched if the perspective is from the remote site.
About creating global service groupsYou create global service groups using a combination of manual steps and aconversion wizard.
The process of creating a global cluster involves the following tasks:
■ Creating a common service group on a cluster at the local site and on a clusterat a remote site
■ Converting the service group that is common to both the local and the remoteclusters into a global service group
■ Configuring global cluster heartbeats (intercluster heartbeats) to monitor thehealth of the failover target clusters.
About the Status tab for global clusters and servicegroups
For a global cluster and a global service group, additional information is providedon the Status tab.
For a global cluster, the DR column of the Groups Listing table is populated witha DR fire drill status icon. This icon appears whether or not a DR fire drill groupis configured on the remote cluster. For a single-site HA service group, the DRcolumn contains a dash, indicating that the column does not apply to an HA servicegroup.
Figure 9-1 shows the Groups Listing table for a global cluster.
281Administering VCS global cluster configurationsAbout creating global service groups
Figure 9-1 Status tab for a global cluster
See “About DR fire drills” on page 315.
The columns and data in the Groups Listing table, except for the populated DRcolumn, are the same for a global cluster as they are for a single-site HA cluster.
For a global service group, the Status tab displays an additional table. This tableis shown along with the standard Groups Listing and State information on memberSystems tables that are shown for every service group. The additional table islabeled Group status on remote clusters. This table indicates the state of theservice group at the remote site. It also provides a link to the Status tab for theDR fire drill group if one is configured at the remote site.
Figure 9-2 shows the additional table.
Figure 9-2 Status tab for a global service group
Administering global clustersVCS global cluster technology provides a robust HA/DR solution for the managedenterprise.
A proper global cluster configuration complies with the following conditions:
Administering VCS global cluster configurationsAdministering global clusters
282
■ The ClusterService group for all clusters is properly configured for VCS globalcluster operations. The csgnic resource or gconic resource (NIC resource),gcoip (IP resource), and wac resources can come online.
■ The service group that is intended to serve as the global group has the samename on the global and the remote cluster. This name is not shared with anyother service group.
■ The global cluster and the remote cluster have unique names.
■ The global cluster and the remote cluster use the same version of VCS.
■ The global cluster and the remote cluster use the same operating system.
■ The global cluster and the remote cluster are former standalone clusters thatdo not already belong to a global cluster configuration.
■ The global cluster and the remote cluster are configured to use either SymantecProduct Authentication Service or native VCS (classic VCS) authentication.The VCS Management Console does not support mixed authentication modes.
For remote cluster operations (available on the Remote Operations menu), youmust add a user to the global cluster and to the remote cluster. Give this useridentical privileges on each cluster.
You can administer VCS global clusters when you view the following:
■ All service groups in one non-global cluster (to create a global cluster)
■ All service groups in one global cluster
■ All service groups in one remote cluster
The procedure for viewing global and remote cluster details is the same.
Adding a remote cluster to a local clusterThis task enables you to designate a remote cluster as the failover target for theservice groups that are configured on a local cluster. You must begin with twostandalone clusters. This task can be performed from either cluster.
The next step after you finish this task is to run the Global Group Configurationwizard on one or more service groups on the local cluster.
See “Converting local service groups to global service groups” on page 286.
Before you perform that task, ensure that you configure an identical service groupon the remote cluster for each intended global service group on the local cluster.
The following information is required for this task:
■ The IP address of the cluster, the IP address of a system in the cluster, or thename of a system in the cluster to be added to the configuration
283Administering VCS global cluster configurationsAdministering global clusters
■ The user name and password of the administrator for the cluster to be addedto the configuration
■ The domain and domain type if the cluster to be added is configured in securemode
The console does not support adding a cluster that is already part of a globalcluster configuration.
To perform this task, you must have administrator privileges on the cluster towhich you intend to add a remote cluster.
Note:Before you begin this task, you must view all service groups in one non-globalcluster.
To view all service groups in one non-global cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required cluster and then click thecluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To add a remote cluster to a non-global cluster
1 View all service groups in the required non-global cluster.
2 On the Configuration task menu, click Add/Delete Remote Cluster.
3 In the Remote Cluster Configuration wizard, read the introductory informationand then click Next.
4 In the Configuration Options panel, click Add Cluster and then click Next.
Administering VCS global cluster configurationsAdministering global clusters
284
5 Specify options for the cluster connection.
For clusters configured to use classic VCS authentication: In the ConnectionDetails panel, specify the following options for the connection to the remotecluster.
Enter the IP address of the remote cluster, the IP address of aremote cluster system, or the name of a remote cluster system.
A name oraddress
Enter the port number that is used to connect to the remotecluster. The default is 14141.
The port
Enter an administrator-level user name and password that is validon the remote cluster.
An administratoruser name andpassword
After you finish specifying options in the Connection Details panel, click Next
For clusters that are configured to use Symantec Product AuthenticationService (secure clusters): In the Connection Details panel, specify the followingoptions for the connection to the remote cluster.
Enter the IP address of the remote cluster, the IP address of aremote cluster system, or the name of a remote cluster system.
A name oraddress
Enter the port number that is used to connect to the remotecluster. The default is 14141.
The port
Use the credentials for the current cluster connection to connectto the remote cluster or enter new credentials.
You must specify the user name, password, domain, and domaintype. If you have connected to the remote cluster before usingthis wizard, you can use the credentials from the previousconnection.
Authenticationcredentials
After you finish specifying options in the Connection Details panel, click Next
6 Click Finish.
The cluster icon changes to indicate that the cluster is now a global cluster.
Administering global service groupsAfter connecting the intended global (local) and the intended remote cluster, youmust convert the local service group that is common to the remote cluster into aglobal group. Use the Global Group Configuration wizard to convert the local
285Administering VCS global cluster configurationsAdministering global service groups
service group into a global service group. This wizard also enables you to revertglobal groups back into local groups.
Administering global groups requires the following conditions:
■ A service group that is intended to serve as the global group must have thesame name on the local cluster and on the remote cluster.
■ You must know the administrator user name and password for the local clusterand the remote cluster in the global cluster configuration.
You can administer VCS global clusters when viewing the following:
■ All global clusters in a site
■ All global service groups in a site
■ All global service groups in a cluster
■ All resources in a global service group
You can create a global service group when you view the details of one servicegroup.
Converting local service groups to global service groupsThe Global Group Configuration wizard enables you to convert a local servicegroup into a global service group.
Before running the Global Group Configuration wizard on a service group, ensurethat you do the following (you can perform either step first):
■ Use the Remote Cluster Configuration wizard to create a global and a remotecluster
■ For each service group on the local cluster that you intend to make global,configure an identical service group on the remote cluster.
See “Adding a remote cluster to a local cluster” on page 283.
See “Adding a service group to a cluster” on page 189.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group to beconverted
■ Administrator privileges on the service group to be converted
Note: Before you begin this task, you must view all resources in one non-globalservice group.
Administering VCS global cluster configurationsAdministering global service groups
286
To view the details of one non-global service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required non-globalservice group and then click the service group.
On the details tab bar, this action selects the Status tab by default. It alsodisplays a State Information on Member Systems table and a Resources Listingtable.
To convert a non-global service group to a global service group
1 View all resources in the required non-global service group.
2 In the Configuration task menu, click Configure Global Group.
3 In the Global Group Configuration wizard, read the introductory informationand then click Next.
4 In the Cluster List Configuration panel, under Available Clusters, select theclusters on which the local service group can come online.
To select a cluster, click a cluster and then click > (right-arrow) to move thecluster name under Selected Clusters. The cluster that you select in this stepbecomes the remote cluster.
5 Select the failover policy for the local service group.
The following are the available policies:
Prevents the service group from automatically failing over toanother cluster.
Manual
Enables the service group to fail over to another cluster if it cannotfail over within the cluster or if the entire cluster faults.
Auto
Enables the service group to automatically fail over to anothercluster if it is unable to fail over within the cluster.
Connected
After you select a failover policy, click Next
6 Update the cluster list of the local service group.
Verify or supply the authentication credentials for the local cluster (orclusters) in the list. When you finish the wizard, the VCS Management Consoleconnects to the cluster (or clusters) and updates the list.
287Administering VCS global cluster configurationsAdministering global service groups
7 Update the cluster list of the remote service group.
In the Remote Cluster Authentication panel, verify the required informationfor the remote cluster. To change authentication information, under ExistingClusters, click the remote cluster and then enter the authenticationinformation in the fields to the right. The information that is required in thispanel varies depending upon whether or not the remote cluster is configuredin secure mode. When you finish the wizard, the VCS Management Consoleconnects to the cluster (or clusters) and updates the list.
8 Click No if you want the operation to be completed only if the wizard canconnect to all selected clusters.
9 In the final panel, read the message about the results of the task and thenclick Finish.
Bringing a remote service group onlineThis task enables you to manually put a remote service group into a responsive,functioning state. You can bring a remote service group online on a specific system,or you can bring the service group online anywhere in the remote cluster. If youselect the anywhere option, the console brings the service group online on thefirst available system in the remote cluster.
To perform this task, you must have administrator privileges on the remote clusteror the remote service group.
Note: Before you begin this task, you must view all resources in one global servicegroup.
To view all resources in one global service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required global servicegroup and then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysthe following tables:
■ The status of the global group on each system on which it is configured
■ The status of the global group's remote failover target service group
■ The status of the global group's resources an the local site
Administering VCS global cluster configurationsAdministering global service groups
288
To bring a remote service group online
1 View all resources in the required global service group.
2 In the Remote Operations task menu, click Online.
The Remote Operations menu is available only when you select a global servicegroup in the navigation tree.
3 In the Online Service Group wizard, specify options for the task.
The following options are available:
On the drop-down menu (Select the cluster you want to onlinethis group on), click the cluster on which you want to bring theremote service group online. The cluster options are populatedusing the cluster list for the remote service group.
The remotefailover targetcluster
On the drop-down menu (Select the system you want to onlinethis group on), click the system on which you want to bring theremote service group online. The system options are populatedusing the system list for the remote service group.
If more than one potential target system exists, the Anywhereoption is available. The Anywhere option causes this task to tryeach system in the list until the service group is successfullybrought online.
The remotefailover targetsystem
After you finish specifying options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Taking a remote service group offlineThis task enables you to manually put a remote service group into an unresponsive,nonfunctioning state. You can take a remote service group offline on a specificsystem, or you can take the service group offline anywhere in the remote cluster.If you select the Anywhere option, the console takes the service group offline onthe first system on which it is found to be online.
To perform this task, you must have administrator privileges on the global clusteror service group.
Note: Before you begin this task, you must view the details of one global servicegroup.
289Administering VCS global cluster configurationsAdministering global service groups
To view the details of one global service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required global servicegroup and then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysthe tables that contain the following:
■ The system status for the system where the global group is on line
■ The status of the global group's resources
■ The status of the global group's remote service group
To take a remote service group offline
1 View all resources in the required global service group.
2 In the Remote Operations menu, click Offline.
The Remote Operations menu appears only when you select a global servicegroup in the navigation tree.
3 In the Offline Service Group wizard, specify the following options:
On the drop-down menu (Select the cluster you want to offlinethis group on) , click the cluster on which you want to take theremote service group offline. The cluster options are populatedusing the cluster list for the remote service group.
The remotefailover targetcluster
On the drop-down menu (Select the system you want to offlinethis group on), click the system on which you want to take theremote service group offline. The system options are populatedusing the system list for the remote service group.
If more than one potential target system exists, the Anywhereoption is available. The Anywhere option causes this task to takethe service group offline on the first system on which it is found.
The remotefailover targetsystem
After you finish specifying options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Administering VCS global cluster configurationsAdministering global service groups
290
Switching a remote service groupThis task enables you to take a service group offline on one system in a clusterand bring it online on another system using a single command.
To perform this task, you must have administrator privileges on the global cluster.
Note: Before you begin this task, you must view all resources in one global servicegroup.
To view all resources in one global service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required global servicegroup and then click the service group.
On the details tab bar, this action selects the Status tab by default and displaysthe following tables:
■ The status of the global group on each system on which it is configured
■ The status of the global group's remote failover target service group
■ The status of the global group's resources an the local site
To switch a remote service group to another system
1 View all resources in the required global service group.
2 In the Remote Operations menu, click Switch.
The Remote Operations menu is available only when you select a global servicegroup in the navigation tree
291Administering VCS global cluster configurationsAdministering global service groups
3 In the Switch Service Group wizard, specify the following options for thetask:
On the Select the cluster you want to switch this group todrop-down menu, click the cluster to which you want to switchthe remote service group . The cluster options are populated usingthe cluster list for the remote service group.
The remotefailover targetcluster
On the Select the system you want to online this group ondrop-down menu, click the system to which you want to switchthe remote service group . The system options are populated usingthe system list for the remote service group. The Anywhere optioncauses this task to try every other system in the list until theservice group is successfully brought online.
The remotefailover targetsystem
After you finish specifying options, click OK.
4 In the final panel, read the message about the results of the task and thenclick Close.
Converting global service groups to local service groupsThis task enables you to convert a global service group back into a local servicegroup.
The conversion does the following:
■ Removes the remote cluster from the cluster list of the local global servicegroup
■ Removes the global cluster from the cluster list of the remote service group.
You must have one of the following privileges on the specified objects to performthis task:
■ Administrator privileges on the parent cluster of the service group to beconverted
■ Administrator privileges on the service group to be converted
Note: Before you begin this task, you must view all resources in one global servicegroup.
To view the details of one global service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
Administering VCS global cluster configurationsAdministering global service groups
292
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster to display the required global servicegroup and then click the service group.
On the details tab bar, this action selects the Status tab by default. It alsodisplays a State Information on Member Systems table and a Resources Listingtable.
To convert a global service group to a local service group
1 View all resources in the required global service group.
2 In the Configuration menu, click Make Local.
3 In the Global Group Configuration wizard, read the introductory informationand then click Next.
4 In the Cluster List Configuration panel, under Selected Clusters, select theglobal cluster that you want to make local.
To select a cluster, click a cluster and then click < (left-arrow) to move thecluster name under Available Clusters.
5 Update the cluster list of the remote service group.
In the Remote Cluster Authentication panel, verify the required informationfor the remote cluster. To change authentication information, under ExistingClusters, click the remote cluster and then enter the authenticationinformation in the fields to the right. The information that is required in thispanel varies depending upon whether or not the remote cluster is configuredin secure mode. When you finish the wizard, the VCS Management Consoleconnects to the cluster (or clusters) and updates the list.
6 Click Next.
The wizard performs the service group configuration and updates the clusterlists of both the local and the previously-remote cluster.
7 In the final panel, read the message about the results of the task and thenclick Finish.
Deleting a remote cluster from a local clusterThe VCS Management Console enables you to delete a remote cluster.
This operation involves the following tasks:
■ Taking the wac resource in the ClusterService group offline in the cluster tobe removed from the VCS global cluster configuration. For example, to delete
293Administering VCS global cluster configurationsDeleting a remote cluster from a local cluster
cluster C2 from a global cluster configuration that contains C1 and C2, log onto C2 and take the wac resource offline.
■ Removing the name of the specified cluster (C2) from the cluster lists of allglobal groups. The VCS Management Console updates the cluster lists forheartbeats. Log on to the local cluster (C1) to complete this task using theGlobal Groups Wizard.
■ Removing the cluster (C2) from the local cluster (C1) using the Cluster Statuspage on the local cluster (C1).
You cannot delete a remote cluster if any of the following apply:
■ The cluster is part of a cluster list for a global service group
■ The cluster is part of a global heartbeats list for a global service group
■ The cluster is changing states or is in the connected or synchronizing states
You must have one of the following privileges on the specified objects to performthese three tasks:
■ Administrator privileges on the remote cluster to be deleted
■ Administrator privileges on the global service groups that are configured onthe remote cluster
Taking the wac resource offlineThe first step in removing a global cluster is to take the wac resource offline.
Note: Before you begin this task, you must view all service groups in one remotecluster.
To view all service groups in one remote cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required remote cluster and thenclick the cluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
Administering VCS global cluster configurationsDeleting a remote cluster from a local cluster
294
To take the wac resource offline
1 View all service groups in the required remote cluster.
2 In the navigation tree, click the ClusterService group.
This action opens the Status tab for the ClusterService group by default.
3 On the Status tab, click the Resources detail link.
4 In the Resources Listing table, click the linked name of the wac resource.
5 In the Operations menu, click Offline.
6 In the Offline Resource wizard, on the drop-down menu, select the systemon which you want to take the wac resource offline.
7 Click OK.
8 In the final panel, read the message about the results of the task and thenclick Close.
You are now ready to view the details of the global service group so that youcan delete the cluster from the global group's cluster list.
Removing the cluster from group and heartbeat cluster listsThe second step in removing a remote cluster is to prevent it from being consideredas a failover target. Remove the remote cluster from the cluster lists of each globalservice group and remote service group that participates in this global relationship.
See “Converting global service groups to local service groups” on page 292.
You must repeat this procedure for all global service groups that are configuredin the cluster. When you are finished, you are ready to view the details of theremote cluster so that you can remove it from the local cluster.
Removing the remote cluster from the local clusterThe third step in removing a remote cluster is to remove, or unlink, that clusterfrom the local cluster.
Note: Before you begin this task, you must view all service groups in one globalcluster
To view all service groups in one global cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
295Administering VCS global cluster configurationsDeleting a remote cluster from a local cluster
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to display the required global cluster and thenclick the cluster.
Click the global (local) cluster that is the counterpart to the remote clusterthat you are removing from the global relationship.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To remove a remote cluster from the local cluster
1 View all service groups in the required global (local) cluster.
2 In the Configuration task menu, click Add/Delete Remote Cluster.
3 In the Remote Cluster Configuration wizard, click the cluster to delete andthen click Next.
The cluster that you want to delete cannot be in a connected, synchronizing,or transitioning state.
4 Update the global cluster list of the global cluster.
Verify or supply the authentication credentials for the global cluster. TheVCS Management Console connects to that cluster and updates the list atboth sites when you finish the wizard.
5 In the Remote Cluster Authentication panel, verify the required informationfor the remote cluster. To change authentication information, under ExistingClusters, click the remote cluster and then enter the authenticationinformation in the fields to the right. The information that is required in thispanel varies depending upon whether or not the remote cluster is configuredin secure mode.
6 Click Next.
7 Click Finish.
Administering global heartbeatsIn all clusters, heartbeats are regular signals that are transmitted among clusternodes over the private network. On each cluster node, VCS uses heartbeats tokeep track of which systems in the cluster are online.
For a global cluster, you explicitly configure a global heartbeat to monitor thehealth of the remote cluster and the global cluster. A global heartbeat is a list ofclusters. TheVCS Management Console listens for the heartbeats of the clustersin this list. The heartbeat signals confirm that communications with each cluster
Administering VCS global cluster configurationsAdministering global heartbeats
296
are valid and that each cluster is in an online state.The VCS Management Consoleshows the status of each heartbeat on the Readiness tab.
You must configure at least one cluster heartbeat for each global cluster. You mayadd additional heartbeats as a precautionary measure. The console maintains thecluster heartbeats that you configure as persistent objects in the database.
Adding a global heartbeatThis task enables you to configure a global heartbeat that monitors the health ofthe local and remote clusters in a global cluster configuration.
To perform this task, you must have administrator privileges on the local andremote cluster.
Note: Before you begin this task, you must view all service groups in one cluster.
To view all service groups in one cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required global cluster and then clickthe cluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To add a global heartbeat
1 View all service groups in the required cluster.
2 On the details tab bar, click the Readiness tab.
3 On the Readiness tab, click the Heartbeats detail link.
4 On the Configuration menu, click Add Heartbeat.
297Administering VCS global cluster configurationsAdministering global heartbeats
5 In the Add Heartbeat wizard, specify the following options for the heartbeat:
Enter a name for the heartbeat.The heartbeatname
In the Cluster List for Heartbeat table, check the check box foreach cluster that you want to participate in the heartbeat. Clearthe check box to exclude clusters from the heartbeat list.
The globalclusters to add tothe cluster listfor the heartbeat
In the Settings column, click ... (edit) to specify the value for theArguments attribute, the timeout options, and the interval options.Click Save to exit these options and save your selections.
The Argumentsattribute value,interval, andtimeout options
After you finish specifying options, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
To edit a global heartbeat
1 View all service groups in the required cluster.
2 On the details tab bar, click the Readiness tab.
3 On the Readiness tab, click the Heartbeats detail link.
4 In the Heartbeats Listing table, in the Edit column, click ... (edit).
5 In the Edit Heartbeat wizard, specify the following options for the heartbeat:
Enter a name for the heartbeat.The heartbeatname
In the Cluster List for Heartbeat table, check the check box foreach cluster that you want to participate in the heartbeat. Clearthe check box to exclude clusters from the heartbeat list.
The globalclusters to add tothe cluster listfor the heartbeat
In the Settings column, click ... (edit) to specify the value for theArguments attribute, the timeout options, and the interval options.Click Save to exit these options and save your selections.
The Argumentsattribute value,interval, andtimeout options
After you finish specifying options, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Administering VCS global cluster configurationsAdministering global heartbeats
298
Deleting a global heartbeatThis task enables you to delete the heartbeat list that the console uses to monitorthe health of the local cluster and the remote cluster. You cannot delete a heartbeatif it is the only remaining heartbeat in a global cluster configuration.
To perform this task, you must have administrator privileges on the global cluster.
Note: Before you begin this task, you must view all service groups in one clusterthat is a member of a global cluster configuration.
To view all service groups in one global cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site to show the required global cluster and then clickthe cluster.
On the details tab bar, this action selects the Status tab and the Groups detaillink by default and displays a Groups Listing table.
To delete a global heartbeat
1 View all service groups in the required cluster.
2 On the details tab bar, click the Readiness tab.
3 On the Readiness tab, click the Heartbeats detail link.
4 On the Configuration menu, click Delete Heartbeat.
5 In the Heartbeats Listing table, click X in the row that contains the heartbeatthat you want to delete.
6 In the Delete Heartbeat wizard, click OK to confirm that you want to deletethe heartbeat.
7 In the final panel, read the message about the results of the task and thenclick Close.
Migrating a site (local site disaster recovery)This task enables you to bring global service groups in the local site online ontheir failover target clusters at the remote site. You must select which site is thelocal site. The Migrate Site task is an extension of VCS global cluster technology,and is part of the VCS Management Console DR solution.
299Administering VCS global cluster configurationsMigrating a site (local site disaster recovery)
Note:Although this task is designed to enable local site disaster recovery, you canalso use it to migrate healthy, online service groups.
When to use site migration for DRMigrating a site has specific criteria.
Use the Migrate Site task for DR under the following conditions:
■ A site that contains global clusters faults
■ The service groups in those clusters cannot be failed over normally within thelocal site (because of widespread faulting or inadequate resources)
■ The faulted clusters still communicate
Under these conditions, you can attempt to fail the local service groups over topreconfigured remote clusters. You can migrate only those service groups thatare ONLINE, FAULTED, or PARTIAL. PARTIAL indicates that a service group isonline on at least one system and is FAULTED on none. The service group attributeClusterList lists, in order of preference, the remote clusters that can bring a globalservice group online.
The Migrate Site task is most effectively used when global clusters in a site haveserious problems, but still communicate. You must move critical service groupsto the target failover clusters that are designated for them at this time.
Migrating the siteThis task enables you to select the global service groups in one site that are onlineor faulted on a global cluster. You can perform this task on either the enterpriseSummary tab or the site Summary tab. If you start from the site Summary tab,the default site selection in the task wizard is the currently selected site in thenavigation tree.
Note: Before you use the Migrate Site wizard, you must define one or more valuesfor the site tag. Afterwards, you must assign a site tag value to the appropriateclusters.
See “Administering sites” on page 176.
See “Editing tags on selected clusters” on page 181.
You must have administrator privileges on the global cluster and remote clusterto perform this task.
Administering VCS global cluster configurationsMigrating a site (local site disaster recovery)
300
To migrate a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 In the Operations menu, click Migrate site.
5 In the Migrate Site wizard, click Next.
6 In the Site Selection panel, on the Site drop-down menu, click the site thatyou want to migrate and then click Next.
7 In the Global Application Group Selection panel, select the service groupsyou want to failover to a remote cluster.
If you select a stretch service group, you must also selected a target systemfrom the drop-down menu on the right side of the panel.
8 Click Next.
9 In the Completion of Migrate Site Wizard panel, review the information andthen click Finish.
This action fails over the selected groups to the remote site.
Recovering a failed site (remote site disasterrecovery)
This task enables you to bring failed service groups at a remote site online at thelocal site.
The Recover Failed Site feature is an extension of VCS global cluster technology,and is part of the VCS Management Console HA/DR solution.
See “About VCS global clusters” on page 279.
When to use failed site recoveryRecovering a failed site has specific criteria.
Use failed site recovery only under the following conditions:
■ A remote site that contains global clusters fails unexpectedly
■ Communications with the remote site have been lost
Under these conditions, you can attempt to bring the failed remote service groupsonline on preconfigured global (local) clusters. The service group attribute
301Administering VCS global cluster configurationsRecovering a failed site (remote site disaster recovery)
ClusterList lists, in order of preference, the local clusters that can bring a failedremote service group online.
Use Recover Failed Site only if remote clusters at another site suddenly and totallyfail and cannot communicate. A sudden and total cluster failure is a failure thatdoes not allow normal failover to occur within the remote site.
Recovering the siteThe Recover Failed Site task enables you to select the global service groups thatconform to the following criteria:
■ The global service group is in the selected remote site
■ The global service group was last online on a remote global cluster that stillhas the authority but which is now failed
■ The global service group is offline on the local cluster
You can perform this task on either the enterprise Summary tab or the siteSummary tab. If you start from the site Summary tab, the default site selectionin the task wizard is the currently selected site in the navigation tree.
Note: Before you use the Recover Failed Site wizard, you must define one or morevalues for the site tag and then assign a site tag value to the appropriate clusters.
See “Administering tags” on page 173.
See “Editing tags on selected clusters” on page 181.
To recover a failed site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click Enterprise.
4 In the Operations menu, click Recover Failed Site.
5 In the Recover Failed Site wizard, read the introductory informaiton and thenclick Next.
6 In the Site Selection panel, on the Site drop-down menu, click the site thatexperienced the failure and then click Next.
Administering VCS global cluster configurationsRecovering a failed site (remote site disaster recovery)
302
7 In the Global Application Group Selection panel, select the service groupsyou want to recover at the selected site and then click Next.
8 In the Completion of Online Site Wizard panel, review the information andthen click Finish.
This action brings each selected service groups online at its global failovertarget site.
303Administering VCS global cluster configurationsRecovering a failed site (remote site disaster recovery)
Administering VCS global cluster configurationsRecovering a failed site (remote site disaster recovery)
304
Administering stretchcluster configurations
This chapter includes the following topics:
■ About stretch cluster administration
■ Configuring a stretch cluster
■ Unconfiguring a stretch cluster
■ Configuring a stretch service group
About stretch cluster administrationA stretch cluster is a single VCS cluster that spans two sites. A stretch cluster canhave shared storage or local storage at each site. If local storage is used, datareplication is usually configured between the two sites. This type of cluster iscalled a replicated data cluster (RDC).
The navigation tree displays stretch clusters in hybrid sites. You can easilyrecognize hybrid sites because their names are composed of two individual sitenames. A colon separates the site names. These sites are the two sites that thestretch cluster spans.
See “About sites and cluster types” on page 23.
Stretch clusters behave like VCS global clusters in many respects. You can migratesites, recover failed sites, and perform DR fire drills if the clusters are properlyconfigured.
See “Migrating a site (local site disaster recovery)” on page 299.
See “Recovering a failed site (remote site disaster recovery)” on page 301.
10Chapter
See “About running DR fire drills” on page 343.
However, stretch cluster are still one cluster. Operations such as switch and offlineare performed using the Operations menu instead of the Remote Operations menu.
Configuring a stretch clusterThe Mark/Unmark Stretch Cluster task enables you to designate and configure acluster as a stretch cluster. You must have already set site tags to the values ofthe sites that you intend to assign to the cluster systems.
See “Configuring sites” on page 122.
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view the details of one cluster.
To view the details of one cluster
1 On the main tab bar, click the Manage tab.
2 On the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and click the required cluster.
This action displays the Status tab by default. A Groups Listing table showsthe service groups that are configured in the cluster.
To configure a cluster as a stretch cluster
1 View the details of the required single-site HA cluster
2 On the Status tab, on the Configuration menu, click Mark/Edit StretchCluster.
3 In the Sites for a Stretch (Campus) Cluster dialog box, use the drop-downmenus to specify a site for each listed system.
4 Click OK.
The new hybrid site appears in the navigation tree. The new stretch clusterappears in the new hybrid site.
Unconfiguring a stretch clusterThis task enables you to reconfigure a stretch cluster into an HA cluster.
See “About sites and cluster types” on page 23.
Administering stretch cluster configurationsConfiguring a stretch cluster
306
To perform this task, you must have administrator privileges on the cluster.
Note: Before you begin this task, you must view the details of one cluster.
To view the details of one cluster
1 On the main tab bar, click the Manage tab.
2 On the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and click the required cluster.
This action displays the Status tab by default. A Groups Listing table showsthe service groups that are configured in the cluster.
To unconfigure a stretch cluster
1 View the details of the required stretch cluster
2 On the Status tab, on the Configuration menu, click UnmarkStretchCluster.
3 In the Convert Stretch Cluster to Non-Stretch dialog box, on the drop-downmenu, specify the single site into which you want to consolidate the systemsin the stretch cluster.
4 Click OK.
All of the service groups and systems of the former stretch cluster now appearin the single site that you specified. The hybrid site that contained the stretchcluster is no longer available.
Configuring a stretch service groupAfter you configure a stretch cluster, you can configure a stretch service group.No special menu command exists for configuring a stretch service group. Theprocess is exactly like configuring a single-site HA service group in a cluster withone exception. The exception is in how you build the stretch service group's systemlist. When you build the system list, you must specify at least two systems, onesystem from each site in the hybrid site.
Otherwise, you use the same menu command and the same configuration wizardas you do when you add an HA service group to a single-site cluster.
See “Adding a service group to a cluster” on page 189.
307Administering stretch cluster configurationsConfiguring a stretch service group
Administering stretch cluster configurationsConfiguring a stretch service group
308
Monitoring readiness
This chapter includes the following topics:
■ About HA and DR readiness
■ About fire drills
■ Viewing readiness
■ Updating readiness
About HA and DR readinessReadiness status (readiness) is the measure of a service group's ability to fail overin its intended fashion. Readiness takes into account the service group status, thesystem status, and the remote cluster status that is gathered from consolemonitoring information. The VCS Management Console enables you to monitorand manage the following types of readiness:
High availability readiness indicates one of the following:
■ The ability of a service group to fail over to a system within the localcluster.
■ The ability of a stretch service group to fail over to a system at thelocal site.
See “About sites and cluster types” on page 23.
HA readiness
11Chapter
Disaster recovery readiness indicates one of the following:
■ The ability of a VCS global service group to fail over to a system in itstarget remote cluster at the remote site.
See “About sites and cluster types” on page 23.
See “About VCS global clusters” on page 279.
■ The ability of a service group in a stretch cluster to fail over to a systemin the remote site.
See “About sites and cluster types” on page 23.
DR readiness
Readiness depends upon both the state of service groups and of systems. The VCSManagement Console provides both the HA and the DR readiness information forthe following:
■ VCS global clusters
■ Stretch (campus, metropolitan) clusters
■ VCS global service groups
■ Stretch service groups
■ Sites that contain VCS global service groups
■ Sites that contain stretch service groups
■ The managed enterprise
Note: HA readiness for a stretch or global service group has the same meaning asfor a non-stretch or non-global service group. It is a measure of the service group'sability to fail over within the local site.
About fire drillsA fire drill is a way to measure readiness of service groups on particular system.To measure readiness, fire drills conduct tests on service groups (HA fire drill) orfailovers of special service groups to remote clusters (DR fire drill).
A fire drill evaluates the following:
■ Service group resource configuration and failover viability on an HA clusterat the local site
■ Stretch service group failover within the stretch cluster to a system at theremote site
■ Global service group failover to a system in the target cluster at the remotesite.
Monitoring readinessAbout fire drills
310
The console reports the results for each service group on which a fire drill runs.The console also combines the results and reports them as composite readinessfor clusters, sites, and the managed enterprise. These results are displayed on theenterprise summary and site summary pages.
Note: Fire drills do not test system readiness directly. However, if a system isdown or in a partial state, the fire drill cannot run, and the fire drill reports afailure. Console monitoring reports most of the information that is used for systemreadiness.
About HA fire drillsTo configure high availability for a database or an application, you change severalinfrastructure and configuration settings on multiple systems. To maintain theseinfrastructure settings and configuration settings is a challenge because clusterenvironments can be subject to constant change. Administrators often add disks,create new disk groups and volumes, and add new cluster nodes or new NICs toupgrade and maintain the infrastructure.
Updating the cluster's VCS configuration with the changing physical configurationand infrastructure is critical. High availability (HA) fire drills detect discrepanciesbetween the VCS configuration and the underlying physical configuration andinfrastructure on a node. Such discrepancies might prevent bringing up a servicegroup online on a specific node. Ultimately, the HA fire drill provides data thatis used to update the HA readiness pages in the console.
Note: The HA fire drill task is supported on VCS 4.x and VCS 5.x (but not VCS 4.0)clusters. It is not supported on Windows clusters.
How HA fire drills workThe HA fire drill operation (HA fire drill) uses the Action entry point of the VCSagents to perform checks on resources. These checks verify that the resourcesthat are defined in the VCS configuration (main.cf file) have the requiredinfrastructure to fail over to another node.
For example, an infrastructure check for the mount resource verifies the existenceof the mount point (drive letter) defined in the resource's MountPath attribute.The check verifies that the specified node is a viable failover target that is capableof hosting the service group.
311Monitoring readinessAbout fire drills
HA fire drill checks the resources in one service group and runs on each systemin the service group's system list. That is, it runs on each system that hosts theservice group.
Note: A service group's system list can contain only the systems that are in theparent cluster. HA fire drill does not run on other clusters that host the servicegroup. To run HA fire drill for the group on another cluster, select the group withinthe other cluster while the group is online.
To understand the HA fire drill operation, consider a two-system service group.The service group is online on system sys1 and is configured for failover on systemsys2. For this configuration, the HA fire drill reports success only if all of theresource checks pass on sys2. If only some or none of the checks pass on sys2, theHA fire drill reports failure. However, if a third system sys3 is added, morepossibilities exist:
Readiness of servicegroup on sys1
HA fire drill resultResource checkresults on sys3
Resource checkresults on sys2
Medium (transparent; nocolor) because the servicegroup on sys1 can fail overto sys3
PartialAll checks passAll or some checksfail
Medium (transparent; nocolor) because the servicegroup on sys1 can fail overto sys2
ParitalAll or some checksfail
All checks pass
Low (red) because theservice group on sys3 hasnowhere to fail over
FailedAll or some checksfail
All or some checksfail
High (green) because theservice group on sys1 canfail over to either sys2 orsys3
SuccessAll checks passAll checks pass
Therefore, in the three-system scenario, sys2 or sys3 can go offline and the servicegroup on sys1 is still able to fail over. The HA fire drill fails only if both sys2 andsys3 go offline.
To run an HA fire drill, the service group must be both of the following:
■ Online somewhere in the cluster
Monitoring readinessAbout fire drills
312
■ Composed or partially composed of the resource types that are under themanagement of the agents that support HA fire drill.
To run a fire drill through the fire drill scheduler, the service group must also beenabled for automatic fire drills.
VCS agents support HA fire drill through an HAFD section of their XMLconfiguration file. Each agent's HAFD configuration section defines checks forthe resource type that the agent manages. VCS agents that do not have the HAFDconfiguration section do not support HA fire drill.
A list of VCS agents that support HA fire drill and their checks is available. See“Agents with HAFD support” in the VCS User's Guide.
The HAFD section of the agents' XML configuration file specifies the following:
■ Category of the resource (Application, Network, File System, Storage,Replication) which is used in reports and resource type data tables
■ A list of resource checks
■ The name and description of the checks
■ Whether VCS can fix the cause of a failed check
■ A description string for the fix
Although the agent configuration file defines the resource checks, the consolemaintains them in the resource type objects in the database.
The following table describes other resource checks:
These checks determine whether the resources that are listed in the VCSconfiguration are available on a given system. Each resource type mayhave multiple checks. You can run an infrastructure check only whenthe service group is online. Therefore, HA fire drills require that theservice group be online somewhere in the cluster.
Infrastructurechecks
These checks determine whether what is available on the host is underVCS control.
Completenesschecks
These checks determine whether the same versions of resources are oneach of the systems.
System checks
Verifying agent HA fire drill checks for resource typesEach VCS agent manages all the resources of a specific resource type. During anHA fire drill, an agent applies any resource checks that are defined in it to all theresources that it manages. You can browse for and verify checks by resource type.
313Monitoring readinessAbout fire drills
You can also browse for and verify resource checks by service group. The servicegroup method is also how you implement any automated resource check fixes orget advice on how to implement a manual fix.
See “Viewing HA readiness details for a service group (running fixes)” on page 327.
To verify the HA fire drill checks for a resource type
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand a site and cluster to display the service groups and then click a servicegroup.
Click a service group with the resources that you want to investigate.
5 In the Resources Listing table, in the Type column, click a resource type forwhich resource checks are defined.
6 On the details tab bar, click the HA Readiness Checks tab.
This action displays a table of resource checks for a single resource type ina single cluster. The table contains a list of all defined checks including thename, description, a description of the fix, and whether the agent supplies afix.
About HA fire drill resultsThe console uses HA fire drill results to update the HA readiness tables for servicegroups, clusters, sites, and the enterprise. For each agent action that has anautomatic fix defined, the console provides a description of what was done. Foreach action that has no automatic fix, the console provides a description of themanual fix. If the HA fire drill was run against a simulated cluster.
The results from each HA fire drill that is run persist in the VCS ManagementConsoledatabase. The Resource table in the database stores the results, which areavailable to any user that has a reporting privilege.
An HA fire drill generates results about a service group for each system in theservice group's system list. Therefore, results may exist for each system in theservice group's system list.
See “How HA fire drills work” on page 311.
You can also view the cluster engine logs for HA fire drill results.
See “About viewing HA readiness” on page 318.
In the log, the results consist of a timestamp and either a success flag or adescription of the failure.
Monitoring readinessAbout fire drills
314
About notification for failed HA fire drillsYou may create a notification policy for HA fire drill using the VCS ManagementConsolenotifier. A new type of event that represents HA fire drill failure is availablein the group notification event list. The HA fire drill event type triggers ordinarynotifications as well if the notifications are configured in the local managementserver.
See “Creating a policy ” on page 382.
Upon receipt of the notification, the user navigates to the Group Details page forthe target service group. The HA Fire Drill Details table provides links for fixingproblems.
Configuring an HA fire drillHA fire drills run on the service groups that have resources of a type for whichresource checks are defined. The resource checks are defined in the resourcetypes' agents.
For an agent to support HA fire drill, the resource checks must be defined in theagent configuration file. The VCS documentation has information on definingthese checks.
See the Veritas Cluster Server Administrator's Guide.
About DR fire drillsThe DR fire drill feature is a disaster recovery (DR) solution that is implementedusing VCS global clusters. A DR fire drill is a zero-downtime test that mimics theconfiguration, application data, and failover behavior of critical application servicegroups. A successful DR fire drill proves that it is possible for a critical applicationservice group to fail over properly.
The Run DR Fire Drill task enables you to do the following:
■ Verify that replication for an application works correctly.
■ Verify that a secondary DR application service group can be brought onlinesuccessfully.
Three cluster objects play a role in a DR fire drill:
315Monitoring readinessAbout fire drills
A service group on the cluster that contains the applicationresources and the replication source. The primaryapplication group is also called the Authority. The Authoritycontains only the resources for the application and itsassociated local storage, not for the replication to the remotestorage.
Primary application group
The counterpart to the global primary application group.This service group resides on a remote cluster that isconfigured as a failover target for the global cluster. Thissecond cluster is the replication target.
Secondary application group
A service group on the same remote cluster as the secondaryapplication group. The fire drill group contains similarresources to the primary application group. The disk groupin the fire drill group is (usually) a snapshot of the associatedstorage instead of the actual replication target.
All resources in the fire drill group have an _fd suffix.
Fire drill group
How DR fire drills workThe DR fire drill operation tests the fault-readiness of a service group by mimickinga failover from the primary site to the secondary site. For VCS global clusters,these sites are the local site and the remote site, respectively. The DR fire drillruns without causing any of the following:
■ Interruption of the application at the primary site
■ Disruption of user access
■ Interruption of the flow of replicated data
■ Resynchronization of the secondary site
The DR fire drill operation employs a fire drill service group on the secondarysite. The configuration of the fire drill service group closely corresponds to theconfiguration of the original application service group.
The objective of the DR fire drill is to bring the fire drill service group online atthe secondary site. This result demonstrates the ability of the similarly-configuredapplication service group to fail over and come online at the secondary site.
When the DR fire drill group comes online, it uses a snapshot of the applicationdata. A snapshot is a point-in-time copy of the replicated production data for theapplication.
Fire drill service groups do not interact with outside clients or with other instancesof resources. Therefore, they can come online safely even when the applicationservice group is online.
Monitoring readinessAbout fire drills
316
When you run a DR fire drill, ensure that you do the following:
■ Conduct the DR fire drill at the secondary site only.Do not bring the fire drill service group online on the node that hosts theoriginal application.
■ Set an offline local dependency between the fire drill service group and theapplication service group in the remote cluster.This action helps to ensure that a fire drill does not block an application failoverin case a disaster strikes the primary site.
About DR fire drill resultsThe console uses DR fire drill results to update the HA and DR readiness tablesfor service groups, clusters, sites, and the enterprise. These results are availableto any user that has reporting privileges.
You can also view DR fire drill results in the cluster engine logs and on the DRReadiness Details page.
See “Viewing logs ” on page 274.
See “Viewing DR readiness details for a service group” on page 339.
In the log, the results consist of a timestamp and either a success flag or adescription of the failure.
Recognizing and viewing the fire drill groupThe fire drill group is named with the suffix _fd. If the primary application groupis oraclegroup, the fire drill group is oraclegroup_fd.
The fire drill group has an attribute, UserStrGlobal, that is available on theProperties tab. The value of this attribute is FD:app_group_name, whereapp_grp_name is the name of the global primary application group.
If a DR fire drill is configured for a global cluster, the Groups Listing table showsthe label Fire Drill in the Other Info column. This table appears on the cluster'sStatus tab.
To view DR fire drill groups for a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand an appropriate site and locate an appropriate cluster.
To view DR fire drill results, the cluster must be a global cluster. It must alsohave a DR fire drill group configured at the remote site.
317Monitoring readinessAbout fire drills
5 Click the cluster.
6 On the details tab bar, click Status.
7 In the Groups Listing table, inspect the Other Info column for the Fire Drilllabel.
This label indicates that the service group that is represented in that row isa fire drill group.
Configuring a DR fire drillFor detailed instructions on how to set up a fire drill, see the following documents:
■ Veritas Storage Foundation and High Availability Solutions HA and DisasterRecovery Solutions Guide for Microsoft SQL
■ Veritas Storage Foundation and High Availability Solutions HA and DisasterRecovery Solutions Guide for Microsoft Exchange
■ Veritas Storage Foundation and High Availability Solutions, Solutions Guide
Viewing readinessYou can view HA readiness and DR readiness for the managed enterprise, a site,cluster, or a service group. Viewing readiness enables you to quickly and visuallyevaluate the state and viability of your high availability environment.
About viewing HA readinessFor the enterprise, sites, clusters, and service groups, you can view HA readinessseparately from DR readiness. The VCS Management Console determines HAreadiness from the results of the most recently-run HA fire drill checks. Theconsole represents results of HA fire drill checks as one of the following HA firedrill states.
Icon descriptionDescriptionHA fire drill state
Green fire alarm bell withwhite check mark
All HA fire drill checks havepassed on all systems in thecluster. Therefore, theservice group can fail over toany system in the cluster.
SUCCESS
Monitoring readinessViewing readiness
318
Icon descriptionDescriptionHA fire drill state
Half-orange and half-whitefire alarm bell
Some or all of the HA firedrill checks have failed onsome systems, but all havepassed on at least onesystem. Therefore, the groupcan fail over to that system.
PARTIAL
Red fire alarm bell with whiteX
Some or all of the HA firedrill checks have failed onsome or all systems in thecluster. Therefore, thepossibility that the servicegroup can fail oversuccessfully to any of thesystems in the cluster issignificantly reduced.
FAILURE
Yellow fire alarm bell withblack !(exclamation point)
No HA fire drill checks aredefined for the resourcetypes in this service group.
NO CHECK
Light yellow fire alarm bellwith black ? (question mark)
No HA fire drill has been runon this service group.
NO RUN
The following figures show the fire alarm bell icons as they appear in the console:
For the enterprise, bar graphs represent HA fire drill state totals for all servicegroups.
For sites and clusters, tables show HA fire drill states for each individual servicegroup in the site or cluster.
319Monitoring readinessViewing readiness
For service groups, a table shows the service group and the HA fire drill states foreach check that the HA fire drill performs. This table shows HA fire drill statesfor each system in the cluster that hosts the service group.
Except for sites and the enterprise, the console shows HA readiness in tables. Thecolor of a table cell indicates the overall readiness of the service group at aparticular site or on a particular system. The following are the colors and theirmeaning.
State of HA readiness is HIGH on this system.
This state indicates that all applicable HA fire drill checks passed on thissystem.
Green
State of HA readiness is UNKNOWN on this system; no HA readinessinformation exists for this system.
This state indicates one or both of the following:
■ No HA fire drill checks are defined for the resource types that arepresent in this service group
■ No HA fire drill has ever been run on this system
No color(transparent)
State of HA readiness is LOW.
This state indicates that one or more of all the applicable HA fire drillchecks have failed on that system.
Red
The Legend menu shows these colors. The Legend menu is available on anyReadiness tab.
Viewing HA readiness for the enterpriseHA readiness for the enterprise is available when you view the enterprise summarypage. On this page, the Group HA Readiness panel contains bar graphs. These bargraphs represent the total number of clusters in each possible HA fire drill statethroughout the managed enterprise.
To view HA readiness for the enterprise
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch.
This action displays the Summary tab by default. The Group HA Readinesspanel is located on the right side of the right pane of the console.
Monitoring readinessViewing readiness
320
Viewing HA readiness for a siteHA readiness for a site is available when you view a site's summary page. On thispage, the Group HA Readiness panel contains bar graphs. These bar graphsrepresent the total number of clusters in each possible HA fire drill state in theentire site.
To view HA readiness for a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch, and if it is collapsed, expand it.
4 Click a site.
This action displays the Summary tab by default. The Group HA Readinesspanel is located on the right side of the right pane of the console.
Viewing HA readiness for a clusterHA readiness for a cluster is available when you view a cluster's readiness detailspage. A Groups Listing table provides the readiness of each service group versuseach system on which the service group is configured.
Figure 11-1 shows an example of an HA readiness Groups Listing table for a clusterwith service groups online on several systems:
Figure 11-1 HA readiness only for a cluster
The following are the columns and data in a cluster HA readiness table (HAReadiness Status of Local Groups):
The service group name—also a link to the service group's detailspage
Name
321Monitoring readinessViewing readiness
High availability fire drill status
This column shows an HA fire drill status icon for the last run HAfire drill.
HA
The name of the first system or next system in the cluster. Thiscolumn repeats for each subsequent system in the cluster
This column contains the overall status icons for each instance ofthe service group on each system in the cluster.
Note: These are service group status icons, not fire drill status icons.However, you can mouse over these icons to display HA readinessinformation.
system_N_name
The cluster HA readiness table is an excellent way to view overall changes incluster status. The following figures show how icons and colors change accordingto failovers and changes in system availability.
Figure 11-2 shows a service group switch operation in progress. The service groupshows a PARTIAL status icon as it goes offline.
Figure 11-2 Cluster HA readiness table with a switch in progress
Figure 11-3 shows a service group after a switch.
Monitoring readinessViewing readiness
322
Figure 11-3 Cluster HA readiness table showing results of switch
Figure 11-4 shows a system fault and the resulting failover of its service groupsto system sys1.
Figure 11-4 Cluster HA readiness table showing a system fault
To view HA readiness for a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand an appropriate site and locate an appropriate cluster.
To view HA fire drill results, the cluster must host at least one resource of atype for which resource checks are defined.
5 Click the cluster.
6 On the details tab bar, click Readiness.
This action selects the HA Readiness only detail link by default and displaysthe HA Readiness Status of Local Groups table.
323Monitoring readinessViewing readiness
Viewing HA readiness for a service groupHA readiness for a service group is available when you view a service group'sreadiness details page. HA readiness is shown in a separate table for each systemon which the service group is configured. Each table enables you to view the resultsof categories of resource checks that were performed during the last HA fire drill.
Each table has one column, five rows, and shows the following:
Name of the system on which service group is configuredHeader row
Contains the following:
■ The service group name
■ A status icon for the service group—online, partial, faulted, oroffline
■ A fire drill status icon that indicates the consolidated resultsof the last run HA fire drill
The color of this row indicates the readiness of the servicegroup—high, medium, or low.
Service group row
Contains a fire drill status icon that indicates the results of theapplication resource checks that were performed during the lastrun fire drill. This fire drill status is used to formulate theconsolidated fire drill status that is shown in the service grouprow.
Application row
Contains a fire drill status icon that indicates the results of thestorage resource checks that were performed during the last runfire drill. This fire drill status is used to formulate the consolidatedfire drill status that is shown in the service group row.
Storage row
Contains a fire drill status icon that indicates the results of thenetwork resource checks that were performed during the last runfire drill. This fire drill status is used to formulate the consolidatedfire drill status that is shown in the service group row.
Network row
Color indicates the readiness of the system. Online systems havegreen borders (readiness high) and offline or faulted systems havered borders (readiness low).
Table border
The following figures show some of the status display versatility of the HAreadiness page for a service group.
Figure 11-5shows the HA Readiness table stack for a service group.
Monitoring readinessViewing readiness
324
Figure 11-5 HA readiness for a service group
The tables are stacked so that one is always on top of the others. The color of theservice group row (first row) indicates the readiness of the service group. Thecolor of the table border indicates the readiness of the system—green for high,red for low.
Clicking a table moves it to the top of the stack. You can also right-click the iconsin a table to display a context menu of the operations that are currently availablefor that service group.
Figure 11-6 shows the same HA readiness stack after the red table (faulted system)is clicked.
325Monitoring readinessViewing readiness
Figure 11-6 Viewing a faulted system with an offline service group
Figure 11-7 shows how the example stack appears if the system is online and onlythe service group is faulted or offline.
Figure 11-7 Viewing an online system with an offline service group
The top system table now has a green border.
Monitoring readinessViewing readiness
326
To view HA readiness for a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand an appropriate site and cluster and locate an appropriate servicegroup.
To view HA fire drill results, the service group must contain at least oneresource of a type for which resource checks are defined.
5 Click the service group.
6 On the details tab bar, click Readiness.
This action selects the HA Readiness detail link by default and displays thesystem table stack.
ViewingHA readiness details for a service group (running fixes)You can view log results of an HA fire drill. This information helps you to seeexactly which checks failed and which succeeded. If a resource's agent defines afix for an unsuccessful check, you can run the fix by clicking a link in the log table.
Note: This procedure uses menus. You can also click HA readiness icons in tablesto view HA readiness details.
To view HA readiness details for a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand an appropriate site and cluster and locate a service group with aresource that is of the required resource type.
To view HA fire drill results, the service group must contain at least oneresource of a type for which resource checks are defined.
5 Click the service group.
6 On the details tab bar, click Readiness.
7 On the Readiness tab, click the HA Readiness Details link.
This action displays the log results of the last run HA fire drill. If no HA firedrill has been run, or if no checks are defined for the resources in this servicegroup, no results are available.
327Monitoring readinessViewing readiness
To run a fix for an unsuccessful HA fire drill check
1 Navigate to the HA Readiness Details page for a service group.
2 In the log table, find an unsuccessful resource check that has a link that hasa Fix link or an Advice link.
3 Do one of the following:
■ Click Fix to run an automated fix.
■ Click Advice to learn about a manual fix.
About viewing HA and DR readinessDR readiness is always presented along with some HA readiness information. Thetwo combine to show the overall readiness of a stretch service group or globalservice group. The combination enables you to better evaluate total readinessthan would viewing the remote failover side of the configuration only. ShowingHA readiness and DR readiness together also enables you to observe the processand results of certain operations. These operations include failover on a globalservice group and DR fire drill.
Although DR readiness is always shown with some HA readiness data, the HAreadiness-only pages contain more detailed HA information.
See “About viewing HA readiness” on page 318.
You can view HA and DR readiness for the following:
■ The enterprise, if it contains VCS global clusters or stretch clusters
■ Sites that contain VCS global clusters or stretch clusters
■ Hybrid sites—hybrid sites contain stretch clusters only
■ VCS global clusters
■ Stretch clusters
■ VCS global service groups
■ Stretch service groups
Note: A stretch cluster is considered a DR solution, and a stretch cluster has a DRreadiness status. However, a stretch cluster does not support DR fire drills becauseno remote cluster exists to host a fire drill group. The same is true for a stretchservice group.
Monitoring readinessViewing readiness
328
The VCS Management Console determines DR readiness from the results of DRfire drill checks and service group status at the remote site. The console representsresults of DR fire drill checks as one of the following DR fire drill states.
Icon descriptionDescriptionDR fire drill state
Green fire alarm bell with awhite check mark
Most recent fire drill run wassuccessful
SUCCESS
Light yellow fire alarm bellwith black arrows pointingcounter-clockwise around thebell.
The DR fire drill is still inprogress.
RUNNING
Red fire alarm bell with whiteX
DR fire drill was unsuccessfulFAILED
Light yellow fire alarm bellwith black !(exclamationpoint)
No DR fire drill results areavailable, reasonunknown—one possibility isthat it has not been run
UNKNOWN
Light yellow fire alarm bellwith grey crescent wrench
One or more of the manyrequirements for DR fire drillare not configured for thisservice group
NOT CONFIGURED
The following figures show the fire alarm bell icons as they appear in the console:
Except for the enterprise, the console shows HA and DR readiness in tables. Thecolor of a table cell indicates the overall readiness of the service group at aparticular site or on a particular system. The following are the colors and theirmeaning:
329Monitoring readinessViewing readiness
State of DR readiness is HIGH on this system.
This state indicates that the remote fire drill group successfully cameonline at the remote site.
Green
State of DR readiness is UNKNOWN on this system.
This state indicates that no DR readiness information is available forthis system.
No color(transparent)
State of DR readiness is LOW on this system.
This state indicates that the remote fire drill group did not come onlineat the remote site.
Red
The Legend menu shows these colors. The Legend menu is available on anyReadiness tab.
Viewing HA and DR readiness for a siteHA and DR readiness for a site is available when you view a site's readiness detailspage. A Groups Listing table provides the readiness of each service group versuseach site at which the service group is configured. If DR configurations (stretchservice groups and global service groups) are included, readiness for the remotesites is also included.
Figure 11-8 shows a site readiness table with a global service group and the sitecolumns that separate the local site data from the remote site data.
Figure 11-8 HA and DR readiness for a site
A site column shows data only for the service groups that are configured at thatsite. A site column shows the following message for all service groups that arenot configured at that site:
Not configured at this site
Monitoring readinessViewing readiness
330
For a single-site HA service group, one site column shows data and all othercolumns show the not-configured message. For a stretch service group or globalservice group, two site columns show data and all other columns show thenot-configured message.
If no DR configurations are present, a site HA and DR readiness table shows onlyone site.
Figure 11-9 on page 331.shows a site readiness table for a site that contains onlyHA configurations (no stretch clusters or global clusters):
Figure 11-9 HA and DR readiness for a site with no DR configured
You can click an HA fire drill status icon or a DR fire drill status icon to viewreadiness for that service group. You can right-click these icons to display a contextmenu of the operations that are currently available for that service group.
The DM icon graphically represents data transfer between two storage enclosures.It indicates that replication is configured between the local site and remote siteof a stretch cluster or global cluster. It does not indicate the status of thereplication.
The following are the columns and data in an HA and a DR readiness table for asite (Groups Listing):
The service group nameName
331Monitoring readinessViewing readiness
The name of the site at which the service group is configured. This columncontains the remaining columns that are listed in this table as subcolumns.
The table contains twoSite columns for each stretch service group or globalservice group. One contains the local data, and the other contains the remotedata.
If multiple stretch service groups or global service groups are configuredamong different sites, the table contains as many Site columns as necessary.
Site
The name of the service group's parent clusterCluster
The operational status of the service group
This column contains an operational status icon that indicates the onlineor offline status of the service group. Global service groups and stretchservice groups always show an operational status icon in a second Sitecolumn. HA service groups show an operational status icon at one site andshow Not Configured for all other sites, if any.
Roll over this icon for offline systems to see the results of the last run HAfire drill.
Status
High Availability
This column contains an HA fire drill status icon that indicates HA readinessat that site for an HA, global, or stretch service group.
Roll over this icon for more information about the last run HA fire drill orabout resource checks.
HA
Disaster Recovery
This column contains a DR fire drill status icon that indicates DR readinessat that site for a global or a stretch service group.
Roll over this icon for more information on the last run DR fire drill.
DR
Data Mobility
This column contains a replication icon that indicates that replication isconfigured for a global service group or stretch service group. Replication,when used, is configured between the storage at the local site and the remotesite.
DM
To view HA and DR readiness for a site
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
Monitoring readinessViewing readiness
332
4 Locate an appropriate site.
The site must contain a cluster that hosts a stretch service group or globalservice group. The service group must have a DR fire drill group configuredat its remote site.
5 Click the site.
6 On the details tab bar, click Readiness.
This action displays a Groups Listing table that shows service group statusand DR file drill status.
Viewing HA and DR readiness for a clusterHA and DR readiness for a cluster is available when you view a cluster's readinessdetails page. DR readiness is available only for the DR cluster configurations:stretch clusters and global clusters. These are the only configurations that supportsite-to-site failover, which is the basis of a DR solution.
A table shows the readiness of each service group versus each system on whichthe service group is configured. The table is labeled either Global groups Statusor Stretch cluster global groups Status. The following is an example of an HA andDR readiness table for a global cluster:
Figure 11-10 shows an example of an HA and DR readiness table for a globalcluster with one global service group.
Figure 11-10 HA and DR readiness for a cluster
A site column shows data only for the service groups that are configured at thatsite. A site column shows the following message for all service groups that arenot configured at that site:
Not configured at this site
You can click an HA fire drill status icon or a DR fire drill status icon to viewreadiness for that service group. You can right-click these icons to display a contextmenu of the operations that are currently available for that service group.
333Monitoring readinessViewing readiness
Note: The DM icon graphically represents data transfer between two storageenclosures. It indicates that replication is configured between the local site andremote site of a stretch cluster or global cluster. It does not directly indicate thestatus of the replication. Mouse over the DM icon to view the replication status.
The following are the columns and data in the DR readiness table for a cluster:
The service group nameName
The name of the site at which the service group is configured. This columncontains the remaining columns that are listed in this table as subcolumns.
The table contains two Site columns for each stretch service group or globalservice group. One contains the local data, and the other contains theremote data.
If multiple stretch service groups or global service groups are configuredamong different sites, the table contains as manySite columns as necessary.
Site
The operational status of the service group
This column contains an operational status icon that indicates the onlineor offline status of the service group. Global service groups and stretchservice groups always show an operational status icon in two Site columns.HA service groups show an operational status icon at one site and showNot Configured for all other sites, if any.
Status
High Availability
This column contains an HA fire drill status icon that indicates HA readinessfor an HA, global, or stretch service group.
HA
Disaster Recovery
This column contains a DR fire drill status icon that indicates DR readinessfor a global or a stretch service group.
DR
Data Mobility
This column contains a replication icon that indicates that replication isconfigured for a global service group or stretch service group. Replication,when used, is configured between the storage at the local site and theremote site.
DM
To view HA and DR readiness for a cluster
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
Monitoring readinessViewing readiness
334
4 Expand an appropriate site and click a stretch cluster or global cluster.
5 On the details tab bar, click Readiness.
6 On the Readiness tab, click the HA & DR Readiness detail link.
Viewing HA and DR readiness for a service groupHA and DR readiness for a service group is available when you view a servicegroup's readiness details page. DR readiness is available only for the DRconfigurations: stretch service groups and global service groups. These are theonly configurations that support site-to-site failover, which is the basis of a DRsolution.
HA and DR readiness is shown in a separate site graphic for each site at whichthe service group is configured. For stretch service groups, only two site graphicsare shown: one for the local site and one for the remote site. Each site graphicenables you to view the results of the last run DR fire drill. For global servicegroups, two sites are also usually shown; however, more sites are possible if theVCS agent supports them. One such agent is as the VCS agent for EMC SRDF/Star.
Each site graphic has the following elements that show the following information:
The site panel serves as a backdrop and visual container for mostof the other elements in the graphic. It shows the name of the siteat which service group is configured
Site panel
The span site bar shows the name of the service group's parentstretch cluster or global cluster. It spans the local site and theremote site graphics, indicating that the cluster is configured atboth sites.
Span site bar
335Monitoring readinessViewing readiness
The service group table contains the following rows:
■ The service group row. This row shows a status icon for theservice group—online, partial, faulted, or offline. It also showsa DR fire drill status icon that indicates the consolidated resultsof the last run DR fire drill. The color of this row indicates thereadiness of the service group—high, medium, or low.
Roll over this icon to see where the service group is online.
■ The systems row. This row shows the number of systems onwhich the service group is configured.
Roll over the system icon in this row to see the names of thesystems at this site.
■ The storage row. This row indicates whether or not localstorage is configured at the site. If the storage row is emply,the service group's parent cluster uses shared storage. Thestorage row always shows a storage icon if replication isconfigured.
Note: In the site graphic, the color of the table border does notindicate system readiness or any other state for any object.
Service group table
The intercluster heartbeats line connects the site graphics acrossthe top. It indicates that global heartbeats are configured betweenthe local cluster and the remote cluster. A green wave form onthe line indicates that the intercluster heartbeats function.
Roll over the wave form to check if the intercluster heartbeats arealive.
Intercluster heartbeatsline
The replication line connects the site graphics across the bottom.It indicates that replication is configured between the storage atboth sites. A label indicates the type of replication, such as EMCSRDF or Hitachi Truecopy.
If no replication is configured, the replication line is not shownand is replaced with a label that indicates that replication is notconfigured.
Replication line
Figure 11-11 shows the HA and the DR readiness tables for a service group asviewed from the local site.
Monitoring readinessViewing readiness
336
Figure 11-11 HADR: Local and remote sites from local perspective
In this image, DRSiteA is the site that is selected in the navigation tree. The DRfire drill status icon shows a check at the remote site, indicating that the last runDR fire drill was successful.
Figure 11-12 shows the HA and the DR readiness tables for a service group asviewed from the remote site.
337Monitoring readinessViewing readiness
Figure 11-12 HADR: Local and remote sites from remote perspective
In this image, DRSiteB is the site that is selected in the navigation tree. The DRfire drill status icon shows a question mark at DRSiteB, indicating that the statusis unknown. This result is expected because the system at DRSiteA still has theauthority for the service group.
To view HA and DR readiness for a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand a site that contains stretch clusters or global clusters.
5 Expand a stretch cluster or a global cluster.
6 Click a stretch service group or a global service group.
7 On the details tab bar, click Readiness.
8 On the Readiness tab, click the HA & DR Readiness detail link.
This action displays the site graphics for the service group.
Monitoring readinessViewing readiness
338
Viewing DR readiness details for a service groupYou can view log results of a DR fire drill. This information helps you to see exactlywhich checks failed and which succeeded.
To view HA and DR readiness details for a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand a site that contains stretch clusters or global clusters.
5 Expand a stretch cluster or a global cluster.
6 Click a stretch service group or a global service group.
7 On the details tab bar, click Readiness.
8 On the Readiness tab, click the DR Readiness Details link.
This action displays the log results of the last run DR fire drill. If no DR firedrill group is configured on any remote cluster, you receive a message thatstates this fact. The message also has a link to a list of resources that can helpyou to properly configure resources if a DR fire drill fails.
Updating readinessTo update readiness means to update the information in the readiness tables.Readiness tables are matrices of service groups versus systems or service groupsversus sites. The readiness information that is available in each table cell resultsfrom the most recenlty-run fire drill and system monitoring by the console. Toupdate readiness, you must run or schedule the proper type of fire drill on theone or more service groups of interest.
About running HA fire drillsThe HA fire drill operation runs on a single system at a single site on the localmanagement server. You can run an HA fire drill on online service groups at anytime. HA fire drills also run automatically according to a default schedule or acustom schedule that you specify. You can disable or enable automatic HA firedrills on several selected service groups at once or on one service group at a time.
See “Disabling automatic HA fire drill checks” on page 341.
See “Enabling automatic HA fire drill checks” on page 342.
339Monitoring readinessUpdating readiness
Note: If you run an HA fire drill on a global service group, it runs at the local siteonly.
Some HA fire drill resource checks offer manual solutions or fix operations in theevent that the check fails. Users require only group operator privileges to run fixoperations.
Running an HA fire drill on selected service groups in the enterpriseThis task enables you to select any combination of HA and global service groupsin the enterprise regardless of cluster membership.
You can also run an HA fire drill from the following locations in the VCSManagement Console:
■ On the Readiness tab with a cluster selected in the navigation tree.The HA fire drill operation is available on the Operations task menu.
■ On the Readiness tab with a service group selected in the navigation treeThe HA fire drill operation is available on the Operations task menu.
■ From HA fire drill icons on the HA readiness tables that are available on theReadiness tab through theHA Readiness Only detail link.The HA fire drill operation is available when you right-click an HA fire drillicon.
To run an HA fire drill on selected service groups in the enterprise
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch.
4 On the details tab bar, click Groups.
5 In the Groups Listing table, do one of the following:
■ To select one or more service groups, check the check box next to eachrequired service group.
■ To select all service groups, check the check box at the top of the table.
6 In the Operations task menu, click Run HA Fire Drill.
7 On the details tab bar, click the Logs tab to view the log messages about thefire drill.
Monitoring readinessUpdating readiness
340
Scheduling an HA fire drillThe VCS Management Console has a default schedule for running HA fire drillsto update readiness data. You can modify this schedule for a cluster or a servicegroup. The following procedure starts the task from a cluster, but the steps aftercluster selection are the same if you select a service group. The only difference isthat you can select multiple service groups when you run this task on a cluster.
To edit the default HA fire drill schedule
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch, and if it is collapsed, expand it.
4 Expand the appropriate site and click the required cluster.
5 On the details tab bar, click the Readiness tab.
6 Click the HA Readiness detail link
7 On the Configuration menu, click Edit Global HA Fire Drill Schedule.
8 In the Edit HA Fire Drill Schedule wizard, read the introductory informationand then click Next.
9 In the next wizard panel, check Schedule the task.
10 In the EffectiveDate edit box, enter the date on which you want the scheduleto take effect.
You can also click the calendar icon to the right of the edit box to select thedate from a calendar.
11 Set the recurrence pattern options: click one ofDaily, Weekly, Monthly, orSpecific Dates.
These options specify when and how often the HA fire drill recurs. The Daily,Weekly, Monthly, and Specific Dates options each offer different inputcontrols that are appropriate for that type of recurrence. Specify all therequired information for the option that you select and then click Next.
12 In the Completing the HA Fire Drill Schedule panel, review your schedulespecifications and then click Finish.
Disabling automatic HA fire drill checksYou can disable the automatic HA fire drill checks for a cluster or a service group.Automatic HA fire drills recur according to the default schedule or to a schedulethat you specify using the Edit Global HA Fire Drill configuration task.
See “Scheduling an HA fire drill” on page 341.
341Monitoring readinessUpdating readiness
The following procedure starts the task from a cluster, but the steps after clusterselection are the same if you select a service group. The only difference is thatyou can select multiple service groups when you run this task on a cluster.
To disable automatic HA fire drill checks
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch , and if it is collapsed, expand it.
4 Expand the appropriate site and click the required cluster.
5 On the details tab bar, click the Readiness tab.
6 Click the HA Readiness detail link
7 On the Configuration task menu, click Disableauto-HAFireDrill forGroup.
8 In the Disable auto-HA Readiness Checks dialog box, ensure that you wantto disable the checks for the specified service groups and then click OK.
Enabling automatic HA fire drill checksYou can enable the automatic HA fire drill checks for a cluster or a service groupon which the checks are disabled. Automatic HA fire drills recur according to thedefault schedule or to a schedule that you specify using the Edit Global HA FireDrill configuration task.
See “Scheduling an HA fire drill” on page 341.
The following procedure starts the task from a cluster, but the steps after clusterselection are the same if you select a service group. The only difference is thatyou can select multiple service groups when you run this task on a cluster.
To enable automatic HA fire drill checks
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch , and if it is collapsed, expand it.
4 Expand the appropriate site and click the required cluster.
5 On the details tab bar, click the Readiness tab.
6 Click the HA Readiness detail link
7 On the Configuration task menu, click Enable auto-HAFireDrill forGroup.
8 In the Enable auto-HA Readiness Checks dialog box, ensure that you want toenable the checks for the specified service groups and then click OK.
Monitoring readinessUpdating readiness
342
About running DR fire drillsBefore you can run a DR fire drill, you must configure a DR fire drill group.Configure this group at the remote site of a global service group.
Before you can configure the fire drill group, you must do the following:
■ Configure the local (primary) and remote (secondary) stretch service groupsor global service groups.
■ Set up the replication for the storage at the primary and the secondary sites
You configure the fire drill group using the FDSETUP command-line wizard.
See theVeritasCluster ServerUser'sGuide for information on configuring DR firedrills.
Note: Ensure that the DR fire drill group, which is configured at the remote site,is offline before you run a DR fire drill. If it is online from a previously successfulfire drill, the next fire drill does not run. The objective of a DR fire drill is to ensurethat the DR fire drill group can come online.
Figure 11-13 shows a global cluster with a DR fire drill group configured at theremote site.
Figure 11-13 Global service group with DR fire drill group
Figure 11-14 shows the selection of the global service group in preparation forrunning the DR fire drill. The DR fire drill status icon at the remote site showsthat DR is configured there.
Figure 11-14 Global service group selected for DR fire drill
343Monitoring readinessUpdating readiness
Figure 11-15 shows the results of a successful DR fire drill in the HA and DRreadiness table for the global cluster.
Figure 11-15 A successful DR fire drill
To avoid confusing or unexpected visual results in the readiness tables, Symantecrecommends the following guidelines for DR fire drills:
■ Run the DR fire drill from the perspective of the cluster.Select a stretch or global cluster in the navigation tree or click table links untila stretch or global cluster shows in the navigation bar.
■ Run the DR fire drill with the primary application group online at the localsite.
■ Configure only one fire drill group at the remote site and none at the local site.
Running a DR fire drillThis task enables you to test the ability of the DR fire drill group to come onlineat the remote site. This test yields only two types of readiness: high (green) or low(red), each corresponding to whether or not the _fd group comes online.
■ If you are on one of the primary group's details pages, navigate up one levelto the parent cluster. View the DR fire drill status icon in for the primary groupin theDR column..
■ If you are on the cluster status (all groups in cluster) page, view the DR firedrill status icon in the DR column of the cluster on which the primary groupis online.
■ For all readiness pages, view the DR fire drill status icon in the site columnfor the cluster where the DR fire drill ran. Site columns also contain the clustername in the header.
To run a DR fire drill
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
Monitoring readinessUpdating readiness
344
4 Expand an appropriate site and then expand a global cluster.
5 Click a global cluster .
On the details tab bar, this action selects the Status tab by default.
6 In the Remote Operations task menu, click Run DR Fire Drill.
To stop a fire drill in progress, click Stop Fire Drill.
7 In the Run DR Fire Drill wizard, do the following:
■ In the top drop-down menu, select the cluster and site on which you wantto run the DR fire drill.In a normal two-site global cluster with the DR fire drill (_fd) groupconfigured at the remote site, you have only one selection in this menu.
■ In the bottom drop-down menu, specify the system at the remote site onwhich you want to run the fire drill.In a typical DR fire drill configuration, the DR fire drill group is configuredon one system, but can be configured on any or all systems.
■ If you want to take the fire drill group offline after a successful run, checkReset fire drill test after successful run.
After you finish specifying these optiions, click OK.
8 Inspect the results of the DR fire drill in the global cluster's HA and DRreadiness table.
The DR fire drill status icon at the remote site indictes success or failure.
9 On the details tab bar, click the Logs tab to view the log messages about thefire drill and resource details.
Halting a DR fire drillThis task enables you to halt a DR fire drill if necessary.
To halt a DR fire drill
1 In the navigation tree, select the global cluster at the local site.
This cluster is the one from which you initiated the DR fire drill. This clustermight already be selected.
2 On the Remote Operations menu, click Stop DR Fire Drill.
Clearing the fault on a DR fire drill groupThis task enables you to clear the fault on a DR fire drill group in the event thata DR fire drill fails.
345Monitoring readinessUpdating readiness
To clear the fault on a DR fire drill group
1 In the navigation tree, select the global cluster at the local site from whichthe fire drill was initiated.
2 On the Remote Operations menu, click Clear DR Fire Drill Group.
This action clears the fault on the _fd group at the remote site.
Monitoring readinessUpdating readiness
346
Administering reports
This chapter includes the following topics:
■ About reporting
■ Administering report jobs
■ Administering report outputs
■ About report types
About reportingThe VCS Management Console reporting feature enables you to generate reportsabout cluster performance and management history. The console gathers datafor reports from the management server database.
Report jobs specify how and when to generate a report, and report outputs arethe results of running a report job. You create the report jobs, which areautomatically saved to the database along with any outputs. The VCS ManagementConsole supports several types of reports:
Table 12-1 Types of reports
DescriptionReport type
An inventory of installed enterprise VCS agents, and optionally,bundled VCS agents on each selected cluster. The console sortsthe agents by cluster. For each agent, displays information fromthe agent information file. The agent information includes version,minimum VCS version, agent type, vendor, files installed withagent, and nodes where the agent is installed.
Agent Inventory
12Chapter
Table 12-1 Types of reports (continued)
DescriptionReport type
A summary of all agents that are installed on the selected clusters.The console sorts the information by agent. For each agent, thissummary includes the clusters where the agent is installed, andthe groups that contain resources of that type.
Agent Usage
A listing of all event information, representing changes that aremade to the selected clusters over a specified time period.
Cluster Activity
A tabular report that displays the current value of selectedattributes for each of the selected clusters. Each cluster isrepresented as a single row in the attributes table.
Cluster Attribute
A summary of configuration information about the selectedclusters. May be used in a manner similar to a "run book".
Cluster Inventory
A detailed analysis of the configuration of the selected clustersand their service groups. This report includes configurationproblems. A summary chart displays the configured clusters andgroups with the number of errors and warnings.
Configuration Analysis
A summary of the schedules that are defined for the managementserver, including maintenance windows and scheduled reports.Information includes all objects that are associated with eachschedule.
Current Schedules
Statistics about resource failures, gathered for each of the selectedclusters over the specified date range. A "failure" refers to anoffline or a faulted status. The report shows failures by resourcetype, node, and group, plus time to recovery.
Failure Summary
Statistics about resource failures, gathered for each of the selectedgroups over the specified date range. A "failure" refers to an offlineor a faulted status. The report shows failures by resource type,node, and resource, plus time to recovery.
Failure Summary byGroup
Fault statistics for each resource type, including faults per weekand faults per resource. Purpose is to help locate possible faulttrends.
Fault Trending
A listing of all event information, representing changes that aremade to the selected groups over a specified time period.
Group Activity
A tabular report that displays the current value of selectedattributes for each of the selected groups. Each group isrepresented as a single row in the resulting attributes table.
Group Attribute
Administering reportsAbout reporting
348
Table 12-1 Types of reports (continued)
DescriptionReport type
A listing of all event information, representing changes that aremade to the selected resources over a specified time period.
Resource Activity
A tabular report that displays the current value of selectedattributes for each of the selected resources. Each resource isrepresented as a single row in the resulting attributes table.
Resource Attribute
Analysis of uptime, which is the amount of time the that selectedgroups were accessible to the user over a time period. You canspecify time periods to exclude from the overall uptime calculation.Excluded time periods are called maintenance windows. You canalso exclude individual resources from the calculation.
Uptime Analysis
A table of all virtual IP addresses that the resources in the selectedclusters use. Information about each IP address includes theassociated group, resource, node, subnet mask, and MAC address.
Virtual IP Usage
A table of successful failovers in single-site HA service groups,stretch service groups, and global service groups.
Successful Failovers
A table of all configured intercluster heartbeats and their status.Heartbeats
A link to Symantec resources for evaluating the current licensesin your enterprise.
VIAS License Report
Administering report jobsReport jobs are stored, user-defined specifications for generating report outputs.You can run a report job at arbitrary times or on a schedule. A report job generatesa stored, dated output each time it is run. Report jobs include the followinginformation:
Brief descriptor of one of several reports that are provided withthe product; specifies data to be reported
Report Type
Report job name, supplied by the userJob Name
Report job description, supplied by the userDescription
The time period of the report’s data; only used by some reporttypes
Time Range (somereport types)
Cluster objects on which to base the report; the object type dependson the report type
Selected Objects
349Administering reportsAdministering report jobs
Optional specification of dates for the report job to runautomatically; several recurrence patterns are available
Schedule
The user that created the report jobOwner
Whether or not the report job is set to run at the intervals thatare specified for it
Enabled
You can create, delete, run, enable, disable, and clone report jobs.
Viewing a list of report jobsThe Reports tab displays a list of stored report jobs.
The Reports tab contains the following information about each job:
■ Job name
■ Report type
■ Last available output
■ How many times the job has been run (historical runs)
■ Whether or not the maximum number of outputs are stored
■ Whether or not the report runs on a schedule
■ Whether or not the report schedule is enabled
■ The user account that owns the report
To view stored report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click the All Reports branch, and if it is collapsed,expand it.
In the Last Run column, icons next to the date and time indicate whether thereport job is running, complete, or failed.
Specifying new report job optionsThe VCS Management Console provides a wizard that guides you through thesteps for creating a new report job. You can create report jobs from eighteenpredefined report types. After you choose a predefined report type, you can providethe job specifics. These include scheduling and details about the target objectsthat serve as the subject of the report.
See “About reporting” on page 347.
Administering reportsAdministering report jobs
350
Report job scheduling optionsThe wizard that you use to create and modify report jobs offers many options forspecifying a report job schedule. You must know exactly what information theseoptions require and how to enter them using the wizard controls. To fully exploitthe flexibility of the scheduling feature, you must gain familiarity with thescheduling options.
You may want to refer to these option descriptions during the first few times youdo the following:
■ Create a report job
■ Schedule a report job
■ Edit the time range of a report job
Note:Not all of the scheduling options are relevant to all report types and thereforemight not appear when you schedule a report job.
Schedule the report optionThe Schedule the Report option specifies whether or not you want to create aschedule for running the report job. If you want to set up a schedule, check theSchedule the Report check box. This action activates additional scheduling options.If you want to run a report only when you want and do not want to schedule it,leave this check box clear.
Effective date and time optionThe Effective date and time option specifies the date you want the report scheduleto become active. In the Effective date: box, click the calendar icon to display acalendar and then select an effective date. Depending on your selections, thestarting date for the report schedule can be different, but the report does not rununtil after the effective date.
Start time optionThe Start Time option specifies the time at which you want the report to startrunning. Use the two drop-down menus to select the hour and minutes of the starttime. On all dates that it runs, the report runs at this start time.
Recurrence pattern optionsYou can select one recurrence pattern. The report job runs on all specified datesthat of that pattern.
351Administering reportsAdministering report jobs
You can specify the following options:
Enter the number of days (for example, every 2 days or every 15 days)between runs of the report.
Daily
Select the number of weeks between each run and then select the days ofeach week. For example, suppose that you specify the report job to recurevery two weeks and then click Monday and Friday. The report would runevery Monday and Friday every two weeks.
Weekly
Select a specific date of the month for the report to run. For example, if youselect 15 then, the report runs on the fifteenth of each month.
Monthly
Select specific dates throughout a month or a year for the report to run. Forexample, you can specify that the report run specifically on September 12,2007 and January 18, 2008. Click the calendar icon next to the Selected Datebox to display a calendar. Click a date on which to start the maintenancewindow. Click Add to add it to the Specific Dates box. You can continueadding specific dates in this manner.
To delete a particular date, highlight the date in the Specific Dates box andthen click Remove. You can select multiple dates by holding down the Ctrlkey and clicking on the required dates.
Specificdates
Time range optionsThe Time Range option specifies the reporting time period. The resulting reportincludes the data (stored in the database) that was collected over that period oftime.
You can specify any of the following options:
Enter a number and then select hour, day,week, month, or year. This number andamount of time specify a time range, startingthat amount of time ago, and ending now.For example, the last 1 day is a time rangestarting 24 hours ago.
Last
Select hour, day, week, month, or year toreport on the current hour, day (today),week, month, or year.
Current
Administering reportsAdministering report jobs
352
Specify the From and To information for thespecific period. You can choose to report onthe events that take place on a certain day,at a certain time. You can also choose toreport the events that take place on a certainday.
Specific period
Uncheck this option if you do not want toinclude maintenance windows in the timerange.
See “Creating and deleting maintenancewindows ” on page 403.
Include Maintenance Windows (this optionis checked by default)
Using the target object chooserFor some report types, the job creation wizard requires you to select the clusterobjects (which include attributes) from which the report retrieves data. To facilitateyour selection, the wizard offers a control that is called a chooser. A choosercontains two boxes with large left- and right-arrows between them. The boxescontain expandable trees of the available cluster objects. The trees work like thenavigation tree on the Manage tab.
353Administering reportsAdministering report jobs
To use the object chooser
1 Do the following to specify the required objects:
Click + (plus) next to an object to expandit into the lower-level objects that itcontains.
In the Available Objects (or AvailableAttributes) box, locate the target objectsto use for the report.
Check each required object. If you checkan unexpanded object (an object with a +sign) you automatically check all objectsthat are within the checked parent object.
Check the target objects to use for thereport.
You do not have to decide which objects can be correctly specified for thereport. The trees display only those objects that are appropriate for theselected report type.
2 After locating and specifying the target objects for the report, do the followingto select the specified objects:
This action adds the specified objects tothe Selected Objects (or SelectedAttributes) box
To the right of the Available Objects box,click the right-arrow.
This action moves a selction back underAvailable Objects.
To deselect an object, check the object inthe Selected Objects box and then clickthe left-arrow .
You can repeat this procedure to move selections between each box until thelist contains the objects that you want.
Creating the jobAfter you understand how to specify target objects and scheduling information,you are ready to create the report job. The following task is general and is meantto accommodate the many types of reports that you can create. If you encounteran unfamiliar option, refer to the report job scheduling and target objectinformation.
See “Report job scheduling options” on page 351.
See “Using the target object chooser” on page 353.
To create a new report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
Administering reportsAdministering report jobs
354
3 In the Configuration task menu, click Create a New Report Job.
4 In the Welcome to the Report Job Creation Wizard panel, read the introductionand then click Next.
5 In the Report Information panel, in the Name edit box, enter a name for thereport job.
6 In the Report Description edit box, enter a description for the report job.
7 On the Report Type drop-down menu, click one of the predefined report types.
See “About reporting” on page 347.
8 If you clicked Agent Inventory for the report type, perform the followingaction. Otherwise, continue with the next numbered step.
If you want to include bundled agents in the agent inventory report, checkDisplay Bundled Agents.
9 If you want to set a maximum number of outputs to be stored for the job,perform the following actions. Otherwise, click Next.
■ Check Limit archiving of previous runs (outputs) for this report to.
■ Enter the maximum number of outputs into the Limit to box; you mayenter numbers in the range of one to 999.
■ Click Next.
10 At each subsequent step in the wizard, follow the instructions in each paneland enter the requested information exactly as described, and then click Next.
The remaining panels appear in the following order:
■ Object selection: This panel appears for all report types.
■ Attribute selection: This panel appears only for cluster, service group,and resource attribute report types.
■ Time range: This panel appears only for uptime analysis reports andcluster, service group, and resource activity reports.
■ Start date and time: This panel appears for all report types.
■ Email Notification: This panel appears for all report types. The defaultemail adresses are populated from the notifier.
11 In the CompletingtheReport JobCreationWizard panel, read the summaryabout the information that you specified in the panel sequence. Click Backto make changes if necessary.
12 Click Finish.
355Administering reportsAdministering report jobs
Viewing a report jobThis task enables you to view the attributes and values of a report job. Report jobshave several lists of attributes and values that define report content andscheduling.
When you create a report job, you specify target objects from which the reportjob gathers data. The console stores target objects as values of the Selected Objectsattribute, which is one of the attributes that define a report job.
To view a report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the table in the details pane, click a linked report job name.
The attribute table displays the report job attributes and values. Editableattributes have a ...(edit) icon in the Edit column of the table. You can alsoedit these attributes using corresponding items on the Configuration menu.
Modifying a report jobThis task enables you to modify some of the attributes of a report job. Editableattributes have an ... (edit) icon in the Edit column of the report job attribute table.
Note:You can also edit parts of a report job using menu items on the Configurationmenu. When you view the details of a job, you can edit the name, description,target objects, schedule, and time range of the job.
See “Report job scheduling options” on page 351.
See “Using the target object chooser” on page 353.
To modify a report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, click a linked job name.
4 In the attributes table, locate the attribute that you want to modify and thenclick the ... (edit) icon.
Administering reportsAdministering report jobs
356
5 In the panel that appears, specify new attribute information as required.
The contents of the panel depends upon the attribute that you selected. Eachpanel is one of those that you use when you create a report job, such as Nameand Description or Start Date and Time.
6 After you finish specifying report job options, click Apply.
Deleting report jobsThese tasks enable you to delete one or more report jobs. This task does not deletereport outputs previously generated by a job. However, in the Report Runs table,the deleted report job name no longer links to any job details (attributes andvalues).
To delete selected report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, select the report jobs.
Do one of the following:
■ To select one or more report jobs, check the check box next to eachrequired job.
■ To select all report jobs, check the check box at the top of the table.
4 On the Configuration menu, click Delete Selected Jobs.
5 To delete the jobs, click OK.
To delete a specific report job after reviewing its definition
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, click a linked job name.
4 On the Configuration menu, click Delete the Report Job.
Running a report job to generate a report outputThese tasks enable you to immediately run a report job and generate a reportoutput. Running a report in this way does not affect any scheduled runs of anyjob. When a job run is complete, a new report output is available.
357Administering reportsAdministering report jobs
To run selected report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, do one of the following:
■ To select one or more report jobs, check the check box next to eachrequired job.
■ To select all report jobs, check the check box at the top of the table.
4 In the Operations menu, click Run Selected Jobs.
5 In the Run Selected Jobs panel, click OK.
The report job starts and runs in the background.
6 In the final panel, read the message about the results of the task and thenclick Close.
You can view the output on the Historical Runs tab. This tab contains a newentry in the table with the current date, time, and the name of the job youran. On the Reports tab, in the Reports table, the Last Run value for the jobis also updated.
To run a specific report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, click a linked report job name.
4 On the Operations task menu, click Run the Report Job.
Enabling and disabling report jobsThese tasks enable you to enable and disable a report job schedule. A report jobis enabled by default when it is created. If a schedule is specified for a report job,it remains in place, but the job does not run.
Disabling a report job does not prevent manual runs of the job. You can use theRun command at any time to generate output from a disabled job. Use the EnableSelected Jobs task to turn on a disabled job.
To disable selected report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, select the report jobs.
Administering reportsAdministering report jobs
358
Do one of the following:
■ To select one or more report jobs, check the check box next to eachrequired job.
■ To select all report jobs, check the check box at the top of the table.
4 In the Operations menu, click Disable Selected Jobs.
5 In the Disable Selected Jobs panel, click OK to disable the jobs.
6 In the final panel, read the message about the results of the task and thenclick Close.
To disable a specific report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Expand the report type that contains the required report job and thenright-click the report job.
4 On the context menu, click Disable Report Job.
5 To confirm that you want to disable the report job, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
To enable selected report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, do one of the following:
■ To select one or more report jobs, check the check box next to eachrequired job.
■ To select all report jobs, check the check box at the top of the table.
4 On the Operations menu, click Enable Selected Jobs.
5 In the Enable Selected Jobs panel, click OK to enable the jobs.
If you receive the message, "None of the selected report jobs can be enabled.They are either not scheduled or already enabled," click OK to close the task.Otherwise, proceed to the next step.
6 In the final panel, read the message about the results of the task and thenclick Close.
359Administering reportsAdministering report jobs
To enable a specific report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Expand the report type that contains the required report job and thenright-click the report job.
4 On the menu, click Enable Report Job.
5 To confirm that you want to enable the report job, click OK.
Cloning report jobsThese tasks enable you to create copies of report jobs. You can modify copied, orcloned, jobs as you would any other job. Cloning report jobs is useful if you havejob specifications. These include a target objects list that needs to be the same formultiple report jobs.
Note: Schedule information is not cloned. If you want to schedule a cloned job,edit its Schedule attribute in the Report Job Definition tab to create a new schedule.
To clone selected report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, do one of the following:
■ To select one or more report jobs, check the check box next to eachrequired job.
■ To select all report jobs, check the check box at the top of the table.
4 On the Configuration menu, click Clone.
5 To confirm that you want to clone the jobs, click OK.
The Reports table displays new entries with the same job names as the jobsthat you cloned, but prefixed with "Copy of ". The Last Available Output valuefor the new jobs is None. You can modify job attributes, such as the job nameor the target objects on the Report Definition tab.
To clone a specific report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, click a linked report job name.
Administering reportsAdministering report jobs
360
4 On the Configuration menu, click Clone Report Job.
5 To confirm that you want to clone the job, click OK.
The Reports table displays a new entry, with the same job name as the jobthat you cloned, but prefixed with "Copy of ". The Last Available Output valuefor the new job is None. You can modify job attributes, such as the job nameor the target objects on the Report Definition tab.
Filtering the report jobs tableYou can filter the table in the Report details tab by the user account that createdthe report job.
To filter report jobs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 In the Reports Filter filter panel, select the owner you want from the Ownerdrop-down menu.
5 Click Apply.
Granting and revoking reporting privilegesManagement server administrators can grant reporting privileges and revokedthe same.
See “Granting and revoking reporting privileges” on page 361.
Administering report outputsReport outputs are the retrieved and formatted data that result from running areport job on its target objects. One report job that is run several times createsmany report outputs. Report outputs are stored in the database and can be viewedat any time. New report outputs can be generated from any job at any time. Somereport types report data over a time range (for example, Cluster Activity). Othertypes provide a current snapshot of data (for example, Agent Inventory). All reporttypes require you to choose cluster objects on which to report (target objects),and give you the option to schedule the report.
“Administering report jobs” on page 349.
361Administering reportsAdministering report outputs
Note: Object names in report outputs are now linked to the status page for thatobject. The Selected Objects for report output section of each ouput lists links tothe target objects that are defined in the report job. The body of a report outputmay also contain additional links. This feature enables you to quickly navigate toan object that may be experiencing a problem.
Viewing outputs of a report jobYou can view the stored output of a report at any time. Report jobs produce astored output each time they run. You can also view sample report outputs foreach report type.
To view the latest run using the Reports table
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 In the Reports table, click linked report job name.
4 On the details tab bar, click Latest Run.
To view the latest run using the navigation tree
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Expand the report type that contains the required report job and then clickthe report job.
To view historical runs of a specific type
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 On the details tab bar, click Historical Runs.
The Report Runs table shows all runs of report jobs of the type that youselected.
To view sample outputs of a specific type
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
Administering reportsAdministering report outputs
362
4 On the details tab bar, click Sample Reports.
5 In the Sample Reports table, click a sample report link to view the sampleoutput in the corresponding export format.
The Sample Reports table contains links to sample outputs of the selectedreport type in each available export format.
Exporting a report outputYou can export a report output to the follwoing formats:
■ Adobe Acrobat (PDF)
■ Microsoft Excel
■ Microsoft PowerPoint (PPT)
■ Comma-separated values (CSV)
■ Microsoft Word (DOC)
Note: Before you begin this procedure, you must have run at least one report jobat least once. Otherwise, no report job output is available for export
This procedure describes how to export a report output after you select a reporttype in the navigation tree. You can also select a report job and then export theoutput (if any) from the Last Run tab or the Historical Runs tab. The HistoricalRuns tab enables you to select more than one output, as does this procedure.
To export a report job
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 In the Reports table, do one of the following:
■ To select one or more outputs, check the check box next to each requiredoutput.
■ To select all outputs, check the check box at the top of the table.
5 On the Export menu, click the required output format.
6 Click OK.
7 In the Operation Result panel, read the message about the results of the exportand then click Finish.
363Administering reportsAdministering report outputs
Emailing exported report outputsYou can email export a report output to the follwoing formats:
■ Adobe Acrobat (PDF)
■ Microsoft Excel
■ Microsoft PowerPoint (PPT)
■ Comma-separated values (CSV)
■ Microsoft Word (DOC)
Note: Before you begin this procedure, you must have run at least one report jobat least once. You must then have exported at least one output. Otherwise, noexported output is available for emailing.
To email exported report job outputs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 On the details tab bar, click Historical Runs.
5 In the Report Runs table, do one of the following:
■ To select one or more outputs, check the check box next to each requiredoutput.
■ To select all outputs, check the check box at the top of the table.
6 On the Operations menu, click Email All Exports.
7 In the Email Exported Outputs panel, read the message about the date, time,and content of the exports to ensure correctness and then click OK.
8 In the final panel, read the message about the results of the operation andthen click Finish.
Viewing exported outputs for a report job runYou can view formatted, exported report runs in the Report Runs table.
To view an exported report run in various formats
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
Administering reportsAdministering report outputs
364
4 On the details tab bar, click Historical Runs.
5 In the Report Runs table, in the Output Format column, click a clear, brightformat icon to view the last exported output of that format. Click a shadedicon to export the output to that format.
Shaded icons indicate that the report job output has not been exported tothat format. Clear, bright icons indicate that an exported output is availablein that format.
Filtering the Report Runs tableYou can filter the table in the Historical Runs tab by state and run time.
To filter report outputs of a specific type
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 On the details tab bar, click Historical Runs.
The Report Runs table shows all runs of report jobs of the type that youselected
5 In the Reports Run Filter panel, select the outputs that you want to view bystate.
Select the states that you want to view by checking one or all of the followingcheck boxes:
■ Running – lists report outputs in progress
■ Successful – lists successfully completed outputs
■ Failed – lists failed outputs
6 In the Time drop-down menu, select the time interval over which you wantto view report runs.
The following are the available time intervals:
■ All Report Runs – lists all runs of the selected report type since the consoleinstallation, that have not been deleted.
■ Last Day – lists all runs that occurred during the most recent calendarday, 12am to 12pm.
■ Last Week – lists all runs that occurred during the most recent calendarweek, Sunday through Saturday.
7 Click Apply.
365Administering reportsAdministering report outputs
Deleting selected report outputsThis task enables you to delete outputs (historical runs of a report type) from themanagement server database.
Note: Deleting a report output does not delete the report job that generated theoutput.
To delete selected report outputs
1 On the main tab bar, click Reports.
2 In the navigation tree, click All Reports.
3 Click a report type.
4 On the details tab bar, click Historical Runs.
5 In the Report Runs table, do one of the following:
■ To select one or more outputs, check the check box next to each requiredoutput.
■ To select all outputs, check the check box at the top of the table.
6 On the Configuration menu, click Delete Selected Outputs.
7 In the Delete Output wizard, click OK.
8 In the final panel, read the message about the results of the task and thenclick Close.
About report typesThe following topics describe the contents and purpose of each report type andinclude the following:
■ About tracking VCS agents across the enterprise with reports
■ About managing cluster configurations with reports
■ About analyzing failures for patterns, problems, and trends with reports
■ About managing uptime of service groups with reports
■ About tracking cluster activity with reports
■ About tracking HA and DR performance and DR heartbeats
Administering reportsAbout report types
366
About tracking VCS agents across the enterprise with reportsYou can track VCS agents across the enterprise.
The following reporting topics cover tracking VCS agents:
■ About tracking agents by cluster using the Agent Inventory report
■ About tracking agents by name using the Agent Usage report
About tracking agents by cluster using the Agent InventoryreportThe Agent Inventory report contains information about installed VCS agents oneach selected cluster. This information is acquired by reading the agentinformation file transmitted to the management server during the cluster snapshotoperation. If the cluster does not contain any agent information files, the reportstates that no information is available. Typically, VCS version other than 4.0 onSolaris do not contain any agent information files. All others require a specialinformation file generation utility. Agent information includes: name, version,minimum VCS version, agent type (script or DLL), vendor, files installed with theagent, and nodes on which the agent is installed.
About tracking agents by name using the Agent Usage reportThe Agent Usage report displays a summary of all the agents that are installedon the selected clusters.
The top of the report shows summary of all the installed agents on the cluster.Clicking on the navigation link of an agent takes you to summary area for thatagent.
For each agent, you can view the cluster name, the platform, the VCS versionnumber, and the groups that contain resources of that type.
About managing cluster configurations with reportsYou can manage cluster configurations using reports.
The following reporting topics cover reviewing and evaluating possible changesto cluster configurations:
■ About reporting cluster basics
■ About finding cluster configuration problems
■ About reviewing cluster attributes
■ About reviewing group attributes
367Administering reportsAbout report types
■ About reviewing resource attributes
■ About tracking cluster IPs
About reporting cluster basicsThe Cluster Inventory report shows a variety of configuration information aboutthe selected clusters. Ideally, this report is used in a fashion similar to a run book.Information that is displayed about the selected clusters include: the operatingsystem, the VCS version number, the cluster IP address, the cluster UUID, thecluster notification list, the wide area connection information, enabled featureoptions, and the VCS mode of the cluster. The table describes additionalinformation about each cluster, including: systems in the cluster, nodes ID of eachsystem, license type, processor type, operating system, and system informationstring.
About finding cluster configuration problemsThe Configuration Analysis report analyzes configuration aspects of the selectedcluster and its groups. It also reports on a number of possible configurationproblems. For each configured cluster and group within the cluster, the reportdisplays the state of the object at the time the report is run.
The top of the report is a summary chart displaying all the configured clustersand groups along with the number of errors and warnings generated.
The report performs a series of tests on the configuration.
Each test results in one of the following possible verdicts:
■ Passed: The configuration is within the realm of normalcy.
■ Failed: Something is wrong with the configuration.
■ Warning: An aspect of the configuration is suspect, but not necessarily wrong.
■ Unknown: Configuration information pertaining to the test is unavailable.
Underneath the results for each test, the report displays a chart of information.This chart information provides the detailed results of sub-tests that are used toreach the verdict of the test, when possible.
The following are the tests that are performed on a cluster:
■ Ensures that OS versions are consistent across nodes, the local, and the remote.
■ Ensures that ClusterService group has its Tag attribute set to CSG if it containsthe connector resource (wac).
■ Ensures that notifier and VRTSWebApp resources (if part of ClusterService)are set to non-critical, and have OnlineRetryLimit set to some non-zero value.
Administering reportsAbout report types
368
■ Ensures that there are at least two private heartbeats that are configured andoperational.
■ Ensures that heartbeats are defined for each remote cluster.
The following are the tests that are performed on a service group:
■ Ensures that the resources that are Persistent or OnOnly do not have childresources.
■ Validates the resource dependencies (IP over NIC, etc.).
■ Verifies the system list. Checks that each system in the system list exists, isonline, and is not faulted. Displays the results in a chart.
■ Verifies the remote system list. Checks that each system in the remote systemlist exists, is online, and is not faulted. Displays the results in a chart.
■ Verifies that auto-start is set for the group. If auto-start is not set, it does notindicate a failure but a warning.
■ Verifies that the group is not frozen on any of the nodes.
■ Verifies that the MAC address is consistent with the NIC resource.
■ Verifies that MountV resources refer to an actual VMDg resource.
■ Verifies that a global cluster group ClusterList is a subset of the cluster'sClusterList.
■ Verifies that a global cluster group has the same name as its remotecounterpart.
■ Verifies that only one group in a global cluster (local or remote) has the"authority" attribute set. (Both groups with authority are evidence of atakeover.)
■ Verifies that systems in a group's remote system list are configured in theclusters that are listed in the ClusterList.
About reviewing cluster attributesThe Cluster Attribute report requires the user to select clusters and clusterattributes on which to report. The report output displays the current value ofthese attributes for each of the selected clusters. Each cluster is represented as asingle row in the resulting table of attributes. This table also includes the clustername and the values of the selected attributes. Clusters have attributes such asconfiguration, major and minor versions, and VCS mode.
369Administering reportsAbout report types
About reviewing group attributesThe Group Attribute report requires the user to select groups and group attributeson which to report. The report output displays the current value of these attributesfor each of the selected groups. Each group is represented as a single row in theresulting table of attributes, which includes the group name and the values of theselected attributes. Groups have attributes such as system list, state, whether ornot the systems in the group are enabled, and number of retries.
About reviewing resource attributesThe Resource Attribute report requires the user to select resources and resourceattributes on which to report. The report output displays the current value ofthese attributes for each of the selected resources. Each resource is representedas a single row in the resulting table of attributes. This table also includes theresource name and the values of the selected attributes. Resources have attributessuch as state, critical/non-critical, last resource online, and resource flags.
About tracking cluster IPsThe Virtual IP Usage report displays all virtual IP addresses that are in use forresources in the selected clusters. For each IP address, a table provides theassociated group, resource, node, subnet mask, and MAC address.
About analyzing failures for patterns, problems, and trends with reportsYou can analyze failures for trends, patterns, and problematic recurrences.
The following reporting topics cover identifying trends and patterns:
■ About reviewing cluster failure summary
■ About reviewing cluster failures by service group
■ About reviewing faults
About reviewing cluster failure summaryThe Failure Summary report contains statistical information about resourcefailures. These statistics are gathered for each of the selected objects over thespecified date range. A "failure" in this report refers to any offline status, eitherbecause of a fault or a manual command. The report shows failures by resourcetype, failures by node, failures by group, plus min/max/average time to recover.
Administering reportsAbout report types
370
About reviewing cluster failures by service groupThe Failure Summary by Group report contains statistics about resource failures.These statistics are gathered for each of the selected objects over the specifieddate range. A "failure" in this report refers to any offline status, either becauseof a fault or a manual command. The report shows failures by resource type,failures by node, failures by specific resource, plus min/max/average time torecover.
About reviewing faultsThe Fault Trending report displays fault statistics for each resource type. A faultin this report refers to faulted resource types. For a given resource type, the faultsper week and faults per resource numbers can help you locate possible fault trends.
The top of the chart shows a pie chart, which accounts for the percent of resourcetypes that faulted over the specified time.
The histochart shows the resource type faults over the course of time.
When you hover your mouse over any given area in the pie chart or any of thegraphs, you get additional information. For example, if you hover your mouseover an area in the pie chart, fault percentages are presented. For example, if anarea shows 40 percent, that means the resource type has faulted 40 percent ofthe time. If you hover your mouse over an area of a graph, the total number offaults for a given day are presented. In the graph, if more than one color isrepresented in a day, those colors represent the number of resource type faultsfor that day.
About managing uptime of service groups with reportsYou can manage and report service group uptime.
The following reporting topics cover service group uptime management:
■ About reviewing uptime statistics
■ About reviewing schedule Information
About reviewing uptime statisticsThe Uptime Analysis report provides information on the amount of time an objectis accessible to a user. You can report down to the group level, and you have theoption to specify which resources within a group affect the overall uptimecalculation. You can exclude non-critical resources from uptime calculations.
The top of the report shows the group name and uptime percentage. If you clicka linked group name, you are taken to the uptime information for that group.
371Administering reportsAbout report types
The first graph includes the overall uptime information for the service group andmaintenance window information. The next graph shows uptime information foreach resource in the group. When you hover your mouse over any given area ina graph, you see additional information. For example, if you hover your mouseover a green area, you see information about how long that particular group orresource is online.
If you have scheduled maintenance windows, they are not calculated as downtime,because they have been defined.
See “About managing uptime of service groups with reports” on page 371.
See “Creating and deleting maintenance windows ” on page 403.
A legend follows each graph so you can determine the various states of each groupand its resources.
The following are descriptions of the various states:
■ green: Online
■ light grey: Offline
■ red: Faulted
■ orange: Partial
■ light blue: Coming up
■ light yellow: Faulting
■ unknown: Dark green
■ black: Maintenance
Following the graph is a chart, which represents the same information, plus onlinetotals and total time for each group.
Note:All calculations are rounded to the next highest number. Anything less than1% does not show in the chart. It is considered in the overall calculation, but itdoes not show as faulted.
About reviewing schedule InformationThe Current Schedules report displays information about the schedules that aredefined on the management server. All objects that are associated with theseschedules are displayed. Schedules include: the name, the description, the startdate, the type of schedule, and whether or not it is enabled, whether or not it isperiodic, the duration, repeat parameters, specific dates, and assigned objects.
Administering reportsAbout report types
372
About tracking cluster activity with reportsYou can track cluster activity.
The following reporting tasks topics cover tracking cluster activity:
■ About reviewing cluster activity
■ About reviewing group activity
■ About reviewing resource activity
About reviewing cluster activityThe Cluster Activity report collects the list of all event information (if events areconfigured to be transmitted to the management server) that define the changesthat are made to selected clusters over a specified period of time.
Note: By default, only error-level event messages are sent to the managementserver; this report output may have a small number of event entries.
About reviewing group activityThe Group Activity report collects the list of all event information (if events areconfigured to be transmitted to the management server) that define the changesthat are made to selected groups over a specified period of time.
Note: By default, only error-level event messages are sent to the managementserver; this report output may have a small number of event entries.
About reviewing resource activityThe Resource Activity report collects the list of all event information (if eventsare configured to be transmitted to the management server) that define thechanges that are made to selected resources over a specified period of time.
Note: By default, only error-level event messages are sent to the managementserver; this report output may have a small number of event entries.
About tracking HA and DR performance and DR heartbeatsYou can view how successful local failovers and failovers in DR configurationshave been. You can also view the health of intercluster heartbeats.
373Administering reportsAbout report types
About reviewing successful failoversThe Successful Failovers report collects the list of all event information that isrelated to a successful failover.
Data is provided for the following:
■ A serivce group that fails over within a local cluster
■ A stretch service group that fails over within a stretch cluster to the remotesite
■ A global service that fails over to its preconfigured target remote cluster
About reviewing heartbeatsThe Heartbeats report collects the list of all configured intercluster heartbeatsand reports their status.
Administering reportsAbout report types
374
Administering notification
This chapter includes the following topics:
■ About events, policies, and notifications
■ About configuring SNMP consoles to receive traps
■ Configuring notification settings
■ Viewing a list of policies
■ Viewing policy details
■ Creating a policy
■ Editing a policy
■ Deleting a policy
■ Disabling a policy
■ Enabling a policy
■ Exporting policies
■ Importing policies
■ Viewing alerts
■ About the alert popup
About events, policies, and notificationsThe VCS Management Console monitors clusters, generates events, and respondsto events by sending notifications or performing an action. Cluster problems orchanges in cluster configuration or state can cause the management server togenerate an event and initiate a response.
13Chapter
The VCS Management Console enables you to create and configure notificationpolicies. The management server uses policies to determine how it responds toan event.
The event-response process occurs in the following three steps:
■ The management server generates events when it receives the cluster statusupdates that indicate problems or issues of sufficient severity.
■ The management server evaluates the events against the conditions that arespecified in all policies.
■ For each policy condition that is met, the management server generates analert and performs a response, which are specified in the policy.
The management server can respond to events by sending SNMP traps, by sendingemails, or by running custom scripts.
Note: Ensure that you place all custom scripts in the $data_dir/CustomScriptsfolder.
To create notification policies, you must be a management server user withadministrator privilege. Management server administrators can also view, edit,or delete their own policies or those created by other administrators. All configuredpolicies are in effect at all times regardless of the administrator that created them.
Note: Notification policies may not work properly if the management serverdatabase contains duplicate cluster names.
You must specify the following conditions in a policy configuration:
Specifies the type of cluster objects to which the policy applies.
The following are the available object types:
■ cluster
■ service group
■ service groups and associated resources and systems
■ system
■ resource
Object type condition
Administering notificationAbout events, policies, and notifications
376
Specifies the object filters. It is based on the object type you haveselected.
The following are the available filter conditions:
■ All objects
■ A list of objects that you specify
■ A list of operating systems that you specify, if the object typeis system
■ A list of resource types that you specify, if the object type isresource
Filter condition
Specifies the events to which the policy applies. The possibleevents vary by cluster object. If you do not specify an eventcondition, the policy applies to all events.
Event condition
Specifies the event severities to which the policy applies.
The following are the available severities of an event:
■ Critical
■ Error
■ Warning
■ Information.
If you do not specify an event severity, the policy applies to eventsof all severities.
Severity condition
You must specify an event for the event condition. The following are all the eventsthat the management server can monitor:
Cluster faulted
Cluster exited
Cluster joined
Cluster events
System exited
System joined
System faulted
System in jeopardy
System out of jeopardy
System events
377Administering notificationAbout events, policies, and notifications
Resource faulted
Resource monitor timed out
Resource offline ineffective
Resource in administrator wait
Resource restarting
Resource offline
Resource state unknown
Resource online
Resource flags none
Resource events
Group offline
Group concurrency violation
Group partial online
Initiated group offline
Group online
Group fault
Initiated group online
Service group HA fire drill failed
Service group DR fire drill failed
Service group events
Notifications are recorded in a log, which is stored in the management serverdatabase. You can view a table of log entries for notification events. Each log entryis a response to a management server generated event.
To navigate to the event log entries
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click Logs.
The Notification Logs table contains the log entries.
You can configure a policy to send SMTP emails or SNMP traps to specifiedrecipients, such as your personal email account or an SNMP console. You canalso configure a policy to run a custom script each time a qualifying eventoccurs.
The management server monitors the events that are generated only by thecluster objects that it manages. You cannot write policies for remotemanagement servers.
Administering notificationAbout events, policies, and notifications
378
About configuring SNMP consoles to receive trapsThe VCS Management Console includes two SNMP-specific files: cmc.mib andcmc_trapd, which are created in /opt/VRTScmcm/conf/snmp/ for Solaris andLinux. For Windows, these files are created in C:\ProgramFiles\Symantic\VRTScmcm\conf\SNMP.
The file cmc.mib is the textual MIB for the VCS Management Console supportedbuilt-in traps. Load this MIB into your SNMP console to add it to the list ofrecognized traps.
The file cmc_trapd is specific to the HP OpenView Network Node Manager (NNM)SNMP console. It includes the sample events that are configured for the built-inSNMP traps that are supported by the VCS Management Console. To merge theseevents with those configured for SNMP traps, type the following on the systemthat is running the HP OpenView Network Node Manager:
xnmevents -merge cmc_trapd
When you merge events, the SNMP traps that are sent by the management serverappear in the HP OpenView NNM SNMP console.
For more information on xnmevents, see the HP OpenView documentation.
Configuring notification settingsThe notification system enables you to receive notifications even when you areaway from the VCS Management Console. You can configure the managementserver to send SMTP emails and SNMP traps to both an SMTP and an SNMPrecipient.
Configuring SMTP notificationThis task enables you to configure a recipient for an SNMP notification. Therecipient is an email account.
To configure the SMTP recipient
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click the Settings tab.
3 In the Configuration menu, click Edit SMTP Settings.
379Administering notificationAbout configuring SNMP consoles to receive traps
4 In the Edit SMTP Settings wizard, specify the following options:
Specify the fully-qualified SMTP server name to use for outgoingemail notifications.
SMTP Server
Specify an alternate SMTP server to use if the main server that isspecified in SMTP Server is not available.
SecondarySMTP Server
Specify the text to use for the path of email headers.SMTP FromPath
Specify the text to use for the return path of the email header.Failure email is sent to this path.
SMTP ReturnPath
Specify the connection timeout for both the main and the secondarySMTP servers.
SMTP serverTimeout
Specify a recipient email address to configure by default whencreating a policy. You can specify one or more other addresses whencreating a policy.
Default emailAddress
Check this option to attempt to validate the default email addressor the addresses that are specified in policy configurations.
Send VRFYcommand tovalidate users
After you finish specifying options, click OK
5 In the final panel, read the message about the results of the task and thenclick Close.
Testing the SMTP settingsThis task enables you to send a test email to one or more configured SMTPrecipients.
To test the SMTP settings
1 On the main tab bar, click theNotification tab.
2 On the details tab bar, click the Settings tab.
3 In the Configuration menu, click Test SMTP Settings.
4 In the Test SMTP Settings wizard, choose to send an email or to activate anotification policy.
5 Depending upon your selection in step 4, do one of the following:
■ Specify a recipient email address for the test notification.
■ Select a notification policy from the list.
Administering notificationConfiguring notification settings
380
6 Click OK.
7 In the final panel, read the message about the results of the task and thenclick Close.
Configuring SNMP notificationThe SNMP recipient is usually an SNMP systems management console, most likelyat a remote location.
To configure the SNMP recipient
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click the Settings tab.
3 In the Configuration menu, click Edit SNMP Settings.
4 In the Edit SNMP Settings wizard, specify the following information:
Specify the community property for SNMP traps. The defaultcommunity is public.
SNMPCommunity
Specify the UDP port of the SNMP manager that you intend to receivethe SNMP traps. The default port is 162.
SNMP trapport
Specify a system name or IP address of a system that hosts an SNMPmanagement console. You can select one or more other consoleswhen creating a policy.
Default SNMPconsole
5 Click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Viewing a list of policiesThe notification polices page (default page on the Notification tab) contains a listof all the policies that are configured in the management server database.
In the Notification Policies table, each row represents one policy. The first fivecolumns contain the following specific policy information:
Name of the policyPolicy name
Status of the policy, either enabled or disabledStatus
The clusters that contain objects to which the policy appliesClusters
381Administering notificationViewing a list of policies
The objects to which the policy applies; either all objects, or one objecttype
Scope
User-authored description textDescription
To view the list of policies
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click the Policies tab.
This action displays the Notification Policies table.
Viewing policy detailsPolicy details are a record of the selections that are made during the most recentrun of the Notification Policy Configuration wizard. This wizard is used in creatingand editing a policy. You can view policy details in the Notification Policy Detailsview.
To navigate to the Notification Policy Details view
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click the Policies tab.
3 In the Notification Policies table, click a linked policy name.
This action shows the policy details, which includes settings for the following:
■ Policy name
■ Status
■ Description
■ Cluster selection
■ Object selection
■ Event selection
■ email recipients
■ SNMP console recipients
■ The code for the custom script, if any script is defined
Creating a policyThis task enables you to create a notification policy.
Administering notificationViewing policy details
382
Note: The procedure for creating a policy is almost identical to editing a policy,with one exception: If you edit a policy, you cannot change the name of the policy,only the description.
To create a policy
1 On the main tab bar, click the Notification tab.
2 On the details tab bar, click the Policies tab.
3 On the Configuration menu, click Add Notification Policy.
4 In the Notification Policy Configuration wizard, read the introductoryinformation and then click Next.
5 In the Enter a Name and Description panel, specify options for the policy.
The following are the available options:
Enter a name for the policy. Policy names are currently restrictedto English. The character limit for names is 50 and the name muststart with a letter. The name box does not accept special characters,except for _ (underscore) and - (em-dash).
Policy Name
You may enter descriptions in your language. The character limitfor descriptions is 250 and special characters are allowed. If you usethis procedure to edit a policy, you cannot change the policy name,only the description.
Description
In the Create Policy For list box, click the object type to which thepolicy applies. You can make only one selection from the CreatePolicy For list box.
Create PolicyFor
After you finish specifying options, click Next
6 In the Cluster Selection panel, click either AllClusters or SelectedClusters.
If you click Selected Clusters, the wizard presents a list of clusters. Check therequired clusters and then click Next.
7 In the Object Selection panel, click either All objects or Selected objects, whereobjects is the object type you selected in step 5.
If you click Selected <objects>, the wizard presents a list of those objects.Check the required objects and then click Next.
383Administering notificationCreating a policy
8 In the Event Selection panel, click All Events, Selected Events, or Eventswith Selected Severities.
If you click Selected Events or Events with Selected Severities, the wizardpresents a list of events or severities. Check the required events or severitiesand then click Next.
9 In the Notification Recipients panel, specify the email addresses and SNMPconsoles (console host name or IP address) that you want to receivenotifications.
To add a recipient, click + (plus). To remove a recipient, click a recipient andthen click - (minus).
The console adds the default email address that you entered when youspecified SMTP settings to this list of email recipients. If you do not specifyany email recipients, the management server does not use the default emailaddress. You must specify at least one email recipient in this list to enableemail notification, including notification to the default email address.
See “Configuring notification settings” on page 379.
If you want the policy to run a custom script upon notification, specify thefully-qualified path name and script name.
After you finish specifying recipients, click Next.
10 In the Override Default Settings panel, do one of the following:
■ To continue and modify the default settings, click Next
To exit the wizard, click Finish.
Editing a policyYou use the same wizard to edit and create a policy.
Note: In the following procedure, instead of clicking a linked policy name, youcan click the ... (edit) option in the Edit column.
To edit a policy
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 In the Notification Policies table, click a linked policy name.
Administering notificationEditing a policy
384
4 On the Configuration menu, click Edit Notification Policy.
5 In the Notification Policy Configuration wizard, follow each step exactly asdescribed for this wizard in the procedure for creating a policy. TheNotification Policy Configuration wizard steps begin with step 4 in thatprocedure.
See “Creating a policy ” on page 382.
Deleting a policyYou use the Notification Polices table to delete a policy.
Note: In the following procedure, instead of clicking a linked policy name, youcan click X (delete) in the Delete column.
To delete a policy
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 In the Notification Policies table, click a linked policy name.
4 On the Configuration task menu, click Delete Notification Policy.
5 In the Delete Notification Policy wizard, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Disabling a policyThis task allows you to disable a policy. You must disable policies one at a time.
If you don’t want the management server to enforce a policy but also do not wantto delete the policy configuration, you can disable the policy. A disabled policyremains configured in the database, but the management server does not enforcethe policy.
To disable a policy
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 In the Notification Policies table, click a linked policy name.
4 On the Operations menu, click Disable Notification Policy.
385Administering notificationDeleting a policy
5 In the Disable Notification Policy wizard, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Enabling a policyThis task allows you to enable a disabled policy. You must enable policies one ata time.
The console automatically enables policies after they are created. However, policiescan be disabled at any time.
If a policy is enabled, the management server evaluates all events against theconditions in that policy. If the policy conditions are met, the management serverenforces the policy.
To enable selected policies
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 In the Notification Policies table, click a linked policy name.
4 On the Operations menu, click Enable Notification Policy.
5 In the Enable Notification Policy wizard, click OK.
6 In the final panel, read the message about the results of the task and thenclick Close.
Exporting policiesThis task enables you to export policies to an .xml file on the management server.You can export all the policies that are shown in the Notification Policies table.You must export all the policies at once. You cannot export single policies orselected policies.
If you want to export only one policy or selected policies to another managementserver, you must do the following:
■ On the source management server, export all policies to an .xml file.
■ On the destination management server, import all policies from the .xml file
■ On the destination management server, delete the unwanted policiesindividually.
Administering notificationEnabling a policy
386
To export policies
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 On the Configuration menu, click Export Notification Policies.
4 In your native operating system's download or save panel, specify thedestination path in which to create the exported .xml file.
5 Click OK.
Importing policiesThis task enables you to import previously exported policies into a managementserver. Use the import task together with the export task to quickly create thesame policies on several management servers.
See “Exporting policies ” on page 386.
Note:You cannot import Global-type policies originally created in CommandCentralAvailability because the VCS Management Console does not support this policytype.
To import policies
1 On the main tab bar, click the Notification tab
2 On the details tab bar, click the Policies tab.
3 On the Configuration menu, click Import Notification Policies.
4 In the Import Notification Policies wizard, specify a file to import.
Enter a path and a file name for the .xml file into the Select File box, or clickBrowse to search for the file.
5 Check Discard Duplicate Policies if you want to avoid creating redundantpolicies in the database.
6 Click OK.
7 In the final panel, read the message about the results of the task and thenclick Close.
Viewing alertsYou can view alerts on the logs page of a cluster object.
387Administering notificationImporting policies
See “Viewing logs ” on page 274.
You can also view alerts on the Readiness tab of a cluster.
To view alerts on the Readiness tab
1 In the navigation tree, click a cluster.
2 On the details tab bar, click Readiness.
3 Click the Alerts detail link.
This action displays the Alerts Listing table for the cluster.
About the alert popupEach time that the VCS Management Console generates an alert, a popup appearsthat describes the alert. You can disable this popup for the current session. Ifdisabled, you can enable this option when you view the Alerts Listing table on theReadiness tab of a cluster. The Take Action option may be available on the alertpopup if an action is defined in the alert's notification policy.
If you enable or disable the alert popup, the setting persists only for the currentsession.
To enable the alert popup
1 View the Alerts Listing table for a cluster.
Viewing alerts
2 On the Operations menu, click Show alert popup.
3 In the Show All Alerts dialog box, read the message about the setting persistingonly for the current session, and then click OK.
To disable the alert popup
1 View the Alerts Listing table for a cluster.
Viewing alerts
2 On the Operations menu, click HIde alert popup.
3 In the HIde All Alerts dialog box, read the message about the setting persistingonly for the current session, and then click OK.
Administering notificationAbout the alert popup
388
Searching the database
This chapter includes the following topics:
■ About the search feature
■ Conducting a search
About the search featureThe VCS Management Console offers a search feature that enables you to findany item or object in the VCS Management Console. The search feature retrievesdata from the management server database. User privileges restricts searchresults; the search feature returns only those results that your user privilegespermits you to view.
Conducting a searchThe search feature uses text-based comparison. You can perform a search usingeither the search bar or the Search tab.
The search bar is located on the main tab bar, and contains a text entry box anda Search option. (You may need to scroll right to see these controls on somesystems.) The search bar is available for all pages except those on the Search tab.
Note: On the Manage tab, in the navigation tree, another search box is availableon the Service Groups and the Systems sub tabs. This search control enables youto search objects in the navigation tree only.
The Search tab is located on the main tab bar. Pages on the Search tab contain atext entry box and a Search option and offer some filtering options that the searchbar does not.
14Chapter
The search feature displays results in one or more of the search pages, which younavigate to using the details tabs on the Search tab. These tabs are labeled Clusters,Groups, Systems, Resources, Resource Types, and Logs. Each tab contains a tablethat lists the search results, or hits, in the corresponding object category. Bydefault, the console takes you to the search pages after each search. The destinationpage is the page that was most recently visited.
Searches are limited to text strings.Use a space character to separate two or morestrings. The Exact Match option matches strings exactly and excludes substrings.The Match All Terms option matches strings exactly and includes substrings. TheHighlight option visually emphasizes textual matches.
To understand how Exact Match and Match All Terms work alone and together,consider an object, object1, with attribute path = /tmp/f3. Consider also object2with attribute path = /tmp/f4. The following table shows the results of searchingfor different strings with different combinations of these settings:
path f3path f3path f3path f3Search strings
clearedclearedcheckedcheckedExact match option settings
clearedcheckedclearedcheckedMatch all terms option settings
object1, object2object1nonenoneSearch results
To minimize the number of candidate occurrences, check Exact Match and MatchAll Terms.
The search feature does not currently support the following:
■ Direct textual entry of Boolean operators
■ Direct textual entry of wildcards
■ Query expressions
To perform a search using the search bar
1 In the text entry box, type one, or more text strings that you want to find.
Use a space character to separate text strings.
2 Click Search.
3 Visit each search view to see the hits in each object category.
Your particular destination view depends on which search view was mostrecently visited. Click the other secondary tabs (Clusters, Groups, and so on)to visit the other search views.
Searching the databaseConducting a search
390
To perform a search using the Search tab
1 On the main tab bar, click Search.
2 On the details tab bar, click the object category (Clusters, Groups, and so on)in which you want to begin your search.
3 In the text entry box, type one or more text strings that you want to find.
Use a space character to separate text strings.
4 Check one or more search options and then click Search.
The following are the available search options:
Requires each search result to match atleast one whole search string. This optionexcludes occurrences in which a searchstring is part of a longer string.
Exact Match
Requires each search result to match allsearch terms (strings). The behavior ofthis option depends on the setting of theExact Match option.
See “Conducting a search” on page 389.
Match All Terms
Highlights the string occurrences in thesearch result tables.
Highlight
5 Visit each search view to see the hits in each object category.
Your first results are displayed in the same page in which you started thesearch. Click the other details tabs (Clusters, Groups, and so on) to see anyhits the other search pages.
After you perform a search, changing the Exact Match, Match All Terms, andHighlight option settings automatically updates the results.
391Searching the databaseConducting a search
Searching the databaseConducting a search
392
Administering the database
This chapter includes the following topics:
■ Viewing information about the database
■ Pruning the database
■ Backing up the database
■ Restoring the database from a backup
■ Modifying guest access to the database
Viewing information about the databaseThe database administration pages contain information about the VCSManagement Console database. The VCS Management Console database isembedded in the management server. The management server database is arepository of data for all cluster objects. The cluster objects include clusters,service groups, and resources and all management server objects such as users,tags, and report jobs.
Information in the database administration pages includes the followinginformation categories:
■ Database StatusThis category includes the following information:
■ Creation date: Date the database was first created.
■ Database name: Name of the database.
■ Database path: Physical location (full directory path) of the database ondisk.
■ Date of last successful backup: Date of the most recent successful backupof the database.
15Chapter
■ Last backup file: Name of the most recent backup file.
■ Oldest report output: Name of the oldest report job output.
■ Server name: Name of the database server process.
■ Size, allocated: The physical space that is reserved for the database (in MB).
■ Size, used (approximate): Actual size of the database (in MB).
■ Space on volume, available: Space remaining on the volume on which thedatabase file was installed.
■ Status of current backup: Outcome of most recent backup of the database.
■ Status of current prune: Outcome of most recent prune of the database.This status includes the number of the records that are deleted, if successful.
■ Database Guest AccessThis category includes the following information:
■ Guest access: Indicates whether guest access is enabled or disabled.
■ Guest account name: User name of an account with guest database access.
■ Database server InformationThis category includes the following information:
■ IP Address: Port: IP address and port number of the database server process.
■ Server name: Name of the database server process.
■ Server version: Version of the database server process.
Pruning the databaseYou can prune or remove historical information from the database to reduce thedatabase size.
The pruning task enables you to remove the following objects from the databasethat were created within a specified time period:
■ All cluster objects and data
■ All management server configuration data
■ All schedules
■ All notifications
■ All report outputs
■ All log entries
Administering the databasePruning the database
394
The time period can be either the life of the database, or from the beginningthrough some number of years, months, weeks, or days ago.
To prune the database
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Database tab
3 In the Operations menu, click Prune the database.
4 In the Select the historical data to be removed dialog box, on the Type of Datadrop-down menu, click the type of data to be removed.
The following are the available types:
This option specifies historical clusterdata. Historical cluster data includes: (1)the cluster and the management serverobjects deleted by the user, and (2)historical attribute and tag values. Thecurrent values of attributes and tags arenot removed.
Cluster data and Report outputs
This option specifies report outputs, notthe associated report jobs.
Report outputs only
This option specifies log entries only, butincludes all entries and does notdiscriminate based upon the object orevent that generated the entry.
Log entries only
See “About reporting” on page 347.
395Administering the databasePruning the database
5 Under Remove data older than, do the following:
ClickOlder than one day.To clear all historical cluster data
Click the second option, which is set to 1year by default. Enter a different numberin place of 1. On the drop-down menu,click year, month, week, or day.
Time intervals begin at the date when theoldest data was stored. They end at a laterdate as specified by the length of theinterval.
For example, assume that you enter thenumber 2 and select month. The databaseis pruned beginning with the oldest dataand ending with data stored two monthsafter the oldest data.
To select a specific time interval
6 Click OK.
7 To confirm that you want to prune the database, click OK again.
When the pruning operation is finished, the management server updates theStatus of current prune value in the Database Status table. This value alsoindicates whether the prune was successful and the number of records deleted.
Backing up the databaseBacking up the database is necessary. Backups enable you to recover crucialconfiguration and historical data in the event of a failure. You can back up thedatabase using the VCS Management Console or the CLI. During the backup task,an archived copy of the database file and the associated transaction log file arebacked up to a physically separate location. This location can be a tape drive or adisc drive.
Note: The CLI does not support the gadb -backup command for directories withnon-English characters.
To back up the database using the VCS Management Console
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Database tab
3 In the Operations menu, click Backup database to a File.
Administering the databaseBacking up the database
396
4 In the wizard panel, enter a drive and path name into the Directory/tapedrive text box.
If the directory path you specify does not exist, the database backup commanddoes not create it.
5 In the next panel, read the message about the progress of the backup andthen click Finish.
To back up the database to a file using the command line
◆ At the command prompt, enter the following command:
gadb -backup -to archive
This command creates an archive backup file. This file contains both thedatabase and the transaction log. The database archive file is created in thedirectory path. This path is specified by archive. The database archive filename is of the form:
VCSMC_backup_yyyy-mm-dd_hh_mi_ss.zip
The timestamp portion is in GMT.
Restoring the database from a backupRestoring the database from a backup returns the database to the state it was inwhen the backup was performed. The restoration task restores the database fileand the associated transaction log file from an archive tape backup or archivedisk backup.
Prerequisite tasks for using the gadbrestore commandDo not attempt to restore the database using the gadbrestore command until youhave performed these prerequisite tasks. Otherwise, you may lose data.
Before restoring the management server database from an archive backup, youmust do the following:
■ Stop the management server
■ Detach the database
■ Rename the current database data and log files or move them to a temporarydirectory
If you do not rename or move the database files, the gadbrestore command findsthat they already exist and generates an error message.
The following is the message for UNIX platforms:
397Administering the databaseRestoring the database from a backup
CMC (cli.database.dirAlreadyExist): Data directory "opt/VRTScmcm/data" already exist. Please delete it and try again.
The following is the message for Windows platforms:
CMC (cli.database.fileAlreadyExist): VCSMC.db already exist in
the location: C:\Program Files\Symantec\VRTScmcm\database\Data.
On UNIX platforms, use the vxdbms_start_db.pl program to detach and re-attachthe database.
You must first set up your environment before using this program. For the tcshor csh shells, use the following source vxdbms environment variable:
./opt/VRTSdbms3/vxdbms_env.csh.
On Windows platforms, use the vxdbms_start_db.exe program to detach andre-attach the database.
To stop the management server on UNIX platforms
◆ On the management server host system, obtain a command prompt. Then,enter the following command on one line:
/etc/init.d/vxcmcweb stop
To stop the management server on Windows platforms
1 On the management server host system, click Start > Programs >Administrative Tools > Services.
2 In the Services manager, in the list of services, click Veritas ClusterManagement Console.
You may have to scroll through the list to locate this service.
3 Click Action > Stop.
To detach the database on UNIX platforms
◆ On the management server host system, obtain a command prompt. Then,enter the following command on one line:
/opt/VRTSdbms3/bin/vxdbms_start_db.pl \VERITAS_DBMS3_host-name
-stop CCAvailDb -force
where host-name is the host name portion of the ASA server name.
Administering the databaseRestoring the database from a backup
398
To detach the database on Windows platforms
◆ On the management server host system, obtain a command prompt. Then,enter the following command on one line:
C:\Program Files\VERITAS\vxdbms3\Win32\vxdbms_start_db.exe
"C:\Program Files\VERITAS\vxdbms3" VERITAS_DBMS3_host-name -stop
CCAvailDb -force
where host-name is the host name portion of the ASA server name.
Arguments for the gadbrestore commandThe gadbrestore command requires several input arguments.
On Windows platforms, the data file is located in the VCS Management Consoleinstallation directory in the database\Data directory. Specify this directory as thevalue for the -data argument of the gadbrestore command.
On UNIX platforms, the data and log files are located in the /db directory in theVCS Management Console installation directory. Specify this directory as thevalue for the -data argument of the gadbrestore command.
Specify the archive backup file name as the value for the -archive argument. Youmust specify the backup file name in the following format:
/backup-path/VCSMC_backup_yyyy-mm-dd_hh_mi_ss>.zip
where backup-path and yyyy-mm-dd_hh_mi_ss are the variables that denote thepath to the backup file and the timestamp , respectively.
Note: If a path contains a space, you must double-quote that path when specifyingthe arguments to the gadbrestore command.
The following is an example for UNIX platforms:
gadbrestore -archive /var/backups/VCSMC_backup_2006-03
-07_11_45_17.zip\ -data /opt/VRTScmcm/data
The following is an example for Windows platforms:
gadbrestore -archive C:\Backups\CCAvailDbBackUp@2006-07-
07_11_45_17.zip -data "C:\Program Files \Symantec\VRTScmcm\database\Data"
399Administering the databaseRestoring the database from a backup
Restoring the database using the gadbrestore commandYou can restore the database from the command line only. You must log on to themanagement server as a user with administrative privileges to use the gadbrestorecommand.
Note: The CLI does not support the gadbrestore command for directories withnon-English characters.
To restore the database from a backup
1 Log in to the management server host system as a user with administrativeprivileges.
On UNIX platforms, the administrative user account is root.
On Windows platforms, the administrative user account is Administrator.
2 Obtain a command prompt and then enter the following command on oneline:
gadbrestore -archive ArchiveFile -data DatabaseDataDir
3 After successfully restoring the database, reattach the database and thenrestart the management server process.
Modifying guest access to the databaseThe management server is preconfigured with a guest user account. This guestuser account can be used for external database access only. A management serveradministrator can enable this account. The guest user account name isCCAVAILGUEST. When the account is enabled, the management serveradministrator sets the password.
To modify guest access
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Database tab
Administering the databaseModifying guest access to the database
400
3 In the Configuration menu, click Modify Guest Access.
4 In the Database Access for Guests dialog box, select one of the followingactions:
Enables the guest user account for thedatabase.
Enable database access
Disables the guest user account for thedatabase.
Disable database access
Enables you to change the password forthe guest user account for the database.If you select Change password, you mustenter and then confirm a valid databasepassword.
Change password
After you select an action, click OK.
401Administering the databaseModifying guest access to the database
Administering the databaseModifying guest access to the database
402
Administering maintenance
This chapter includes the following topics:
■ Creating and deleting maintenance windows
■ Assigning and unassigning maintenance windows
Creating and deleting maintenance windowsCreating a maintenance window enables you to designate an interval of downtimefor conducting planned cluster maintenance. Uptime calculations in reports areadjusted for this planned downtime interval. Notifications are also suppressedduring a maintenance window interval. Maintenance windows are assigned onthe Management Server details tab, which is located on the Administration maintab.
On the Management Server tab, the Maintenance Window details link navigatesto a page that includes information about the currently confgured maintenancewindows in the local management server. This server is the management serverto which you are currently logged on.
The maintenance window table is on the Maintenance Windows details page.
To view maintenance window details
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Management Server tab.
16Chapter
3 Click the Maintenance Windows details link.
4 In the Maintenance Windows table, in the Name column, click a linkedmaintenance window name.
This action displays the Window Schedule and Associated Groups tables.
In the Associated Groups table, click a linked service group or cluster nameto view the status of that object.
To create a maintenance window
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Management Server tab.
3 Click the Maintenance Window details link.
4 In the Configuration menu, click Create a Maintenance Window.
5 In the Create Maintenance Window Wizard panel, read the introductoryinformation and then click Next.
6 In the Name and Description panel, enter a name and optional descriptionfor the maintenance window and then click Next.
7 If you do not want the objects to which the window is applied to sendnotifications during the maintenance window, check Disable notificationsduring downtime.
8 In the Start Time and Date panel, specify the required start date, start time,and duration interval using the appropriate controls.
To choose a start date from a calendar, click the calendar icon to the right ofthe Effective date text box.
Administering maintenanceCreating and deleting maintenance windows
404
9 Click the required recurrence interval and then set the values for each interval.The following table lists the recurrence intervals and describes how to setthe values for each:
When selected, an entry field appears that enables you to specifya number of days between each maintenance window occurrence.
Daily
When selected, an entry field appears that enables you to specifythe number of weeks between each maintenance window. A checkbox also appears for each day of the week, enabling you to specifyone or more days for each specified week.
Weekly
When selected, an entry field appears that enables you to specifya date for each month.
Monthly
When selected, an entry field and calendar icon appear, enablingyou to specify a specific date. An Add and Delete icon also appear,enabling you to add or delete the dates that you specify to orfrom a list.
Specific dates
10 In the Completion of Create Maintenance Window Wizard panel, review thesummary information about the maintenance window that you specified, andthen click Finish.
To edit a maintenance window
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Management Server tab.
3 In the Maintenance Windows table, in the Edit column, click ... (edit).
4 Specify the required start date, start time, and duration interval using theappropriate controls.
To choose a start date from a calendar, click the calendar icon to the right ofthe Effective date text box.
5 Select a recurrence option and then set the values.
You can select only one recurrence option per maintenance window. Toimplement multiple recurrence patterns, you must create multiplemaintenance windows.
6 If you do not want the objects to which the window is applied to sendnotifications during the maintenance window, check Disable notificationsduring downtime.
405Administering maintenanceCreating and deleting maintenance windows
7 In the Name and Description panel, enter any changes to the name anddescription for the maintenance window and then click Next.
8 In the final panel, review the summary information about the maintenancewindow you specified and then click Finish.
To delete a maintenance window
1 On the main tab bar, click the Administration tab.
2 On the details tab bar, click the Management Server tab.
3 Click the Mantenance Windows detail link.
4 In the Maintenance Windows table, do one of the following:
■ To select one or more maintenance windows, check the check box next toeach required maintenance window.
■ To select all maintenance windows, check the check box at the top of thetable.
5 In the Configuration menu, click Delete Maintenance Windows.
6 In the Delete Selected Maintenance Windows panel, review the list ofmaintenance windows to be deleted and then click OK.
Assigning and unassigning maintenance windowsYou can assign maintenance windows only to service groups. During a maintenancewindow, users typically switch the service group to another system and then backto the original system after the window expires. You must first create amaintenance window before you can assign it to a service group.
See “Creating and deleting maintenance windows ” on page 403.
To assign a maintenance window to a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster and then click the required servicegroup.
5 In the Operations menu, click Assign/Unassign Maintenance....
6 In the Add or remove maintenance windows panel, click Select an existingmaintenance window.
Administering maintenanceAssigning and unassigning maintenance windows
406
7 In the Available list, check the maintenance window to be assigned to thecurrently-selected service group.
You may check more than one available maintenance window.
8 Click the right-arrow.
This action moves the selected maintenance window to the Assigned list.
9 Click OK.
To unassign a maintenance window from a service group
1 On the main tab bar, click the Manage tab.
2 In the navigation tree, click the Service Groups tab.
3 Click the Enterprise branch and if it is collapsed, expand it.
4 Expand the appropriate site and cluster and then click the required servicegroup.
5 In the Operations menu, click Assign/Unassign Maintenance Window.
6 In the Add or remove maintenance windows panel, click Select an existingmaintenance window.
7 In the Assigned list, check the maintenance window to be deleted from thecurrently-selected service group.
You may check more than one assigned maintenance window.
8 Click the left-arrow.
This action moves the selected maintenance window to the Available list.
9 Click OK.
407Administering maintenanceAssigning and unassigning maintenance windows
Administering maintenanceAssigning and unassigning maintenance windows
408
Accessibility
This appendix includes the following topics:
■ Navigating the VCS Management Console
■ Accessibility features in GUI controls
Navigating the VCS Management ConsoleYou can use your keyboard to view information and perform operations byselecting a variety of different controls in the VCS Management Console.
Examples of selectable controls include the following:
■ Tabs and subtabs
■ Navigational links at the top of the content pane
■ Column headings in tables
■ Hyperlinked objects in tables
■ Areas, such as bars in a graph, in graphical reports
■ Alert categories in the Alerts panel
■ Controls in the header such as Logout, About, and Help
■ Refresh icon
The current active control is enclosed with a rectangle. This rectangle has dottedlines. An area with these dotted lines is said to have the focus. Use the Tab key tomove focus from one control to another.
The following are general rules for navigating the console and performingoperations:
■ Pressing the Tab key moves the focus to the next active area or control
AAppendix
■ Pressing the Enter key activates the item that has focus
■ In a drop-down list, press the arrow keys to move up and down the list
■ When a check box has focus, press the space bar to check or clear the box
In addition to these features, the normal accessibility features of your Web browserare also available.
Accessibility features in GUI controlsIn the VCS Management Console graphical user interface (GUI), the current activecontrol has focus. You can use the Tab key to move focus from one control toanother.
When a radio button has focus, use the up and down arrow keys to move focus toa different radio button. When a radio button has focus, pressing the Enter keyactivates or selects the radio button.
When a drop-down menu has focus, use the up and down arrow keys to moveamong the selections. Press the Enter key to make your selection.
When a check box has focus, press the space bar to check or clear the box.
When a text box has focus, use your keyboard to type text in the box.
AccessibilityAccessibility features in GUI controls
410
Object states
This appendix includes the following topics:
■ About object states
About object statesThe VCS Management Console maps each possible state of an object type to anappropriate consolidated state. The VCS Management Console reports theconsolidated state.
Table B-1 displays the possible states for the cluster objects in the console.
Table B-1 Cluster object states and consolidated states
Consolidated stateState or state distribution onsystems
Object type
PARTIALINITCluster
DISCONNECTEDLOCAL_VCS_BUILDCluster
DISCONNECTEDMASTER_CONNECTCluster
DISCONNECTEDSLAVE_BUILDCluster
CONNECTEDRUNNINGCluster
DISCONNECTEDEXITINGCluster
DISCONNECTEDEXITEDCluster
DISCONNECTEDFAULTEDCluster
PARTIALONLINE > 1 AND FAULTED > 1Service group
ONLINEONLINE > 1 AND FAULTED = 0Service group
BAppendix
Table B-1 Cluster object states and consolidated states (continued)
Consolidated stateState or state distribution onsystems
Object type
FAULTEDFAULTED > 1 AND ONLINE = 0Service group
PARTIALPARTIAL > 1 AND FAULTED = 0AND ONLINE = 0
Service group
OFFLINEOFFLINE > 1 AND FAULTED = 0AND ONLINE = 0 AND PARTIAL=0
Service group
NONEDEFAULTService group
ONLINERUNNINGSystem
FAULTEDFAULTEDSystem
NONEUNKNOWNSystem
OFFLINEDEFAULTSystem
ONLINEONLINE > 1Resource
FAULTEDFAULTED > 1 AND ONLINE = 0Resource
OFFLINEOFFLINE > 1 AND FAULTED = 0AND ONLINE = 0
Resource
NONEDEFAULTResource
Table B-2 displays the possible states for the management server objects in theconsole.
Table B-2 Management server states and consolidated states
Consolidated stateState distribution onsystems
Object type
ONLINERUNNINGManagement server
OFFLINEINITManagement server
OFFLINELOCAL_MASTER_BUILDManagement server
OFFLINEREMOTE_MASTER_BUILDManagement server
OFFLINEEXITINGManagement server
Object statesAbout object states
412
Table B-2 Management server states and consolidated states (continued)
Consolidated stateState distribution onsystems
Object type
OFFLINEEXITEDManagement server
NONEINQUIRYManagement server
NONEUNKNOWNManagement server
PARTIALLOST_HBManagement server
PARTIALLOST_CONNManagement server
FAULTEDDEFAULTManagement server
STATELESSSTATELESSResource type
STATELESSSTATELESSSchedule
STATELESSSTATELESSUser
413Object statesAbout object states
Object statesAbout object states
414
Command line interface
This appendix includes the following topics:
■ Introduction to the command-line interface (CLI)
■ CLI usage
■ CLI commands
Introduction to the command-line interface (CLI)The command-line interface (CLI) is a non-graphical user interface to the VCSManagement Console. You perform tasks in the CLI by entering commands,arguments, and options at your operating system command prompt. You mustrun CLI commands on the management server host system.
Note: Both the UNIX and Windows platforms support the CLI.
On Solaris, the CLI commands are in the following directory:
/opt/VRTS/bin
On Windows, the CLI commands are in the following directory:
C:\Program Files\Symantec\VRTScmcm\bin
Add this directory to your PATH environment variable so that you can run CLIcommands from any directory.
Note: When upgrading the VCS Management Console from 5.0 to 5.5, you need tochange the PATH environment variable to point to the new directory to be ableto run the CLI from any directory.
CAppendix
Users who upgrade from 5.0 to 5.5 on Windows platforms must also change thePATH environment variable to point to the new directory.
You can use the CLI commands to obtain information and perform tasks on bothmanagement server objects and cluster objects. This chapter contains a referenceof CLI commands and usage.
Table C-1 displays both management server and cluster objects and the CLIcommands that are used to perform tasks upon them. Each command is describedin detail in this appendix.
Table C-1 Objects and CLI commands
CLI command(s)Object
gaserver
galogin
galogout
Management servers
gaclusClusters
gasysSystems
gagrpGroups
garesResources
gatypeResource Types
gadb
gadbrestore
Management server database
gauserManagement server users
gaconfCluster configurations
You must log on to the management server before you can use the CLI using thegalogin command.
CLI usageThis section discusses the following CLI usage information.
■ Notations for CLI object names:See “Notations for object names in the CLI ” on page 417.
■ Use of qualified and unqualified names:
Command line interfaceCLI usage
416
See “Use of qualified and unqualified names ” on page 418.
■ Output option summary:See “Output options summary ” on page 418.
■ Version output option:See “Version output option” on page 419.
Notations for object names in the CLIThe CLI uses the following object notations in the Help option of CLI commands.
Table C-2 describes the generic CLI notations.
Table C-2 Generic object notations
DefinitionGeneric CLI Notations
Optional item[ item ]
A list of one or more items, separated by spaces.item...
Unqualified name of object. No parent specifications.
For example, <clus-name> is a cluster name such asClusNW43.
<object-name>
Qualified name of object. Includes the parent specifications.
For example, <clus> might be PersonnelMS:ClusNW43.
<object>
<server> | <clus> | <grp> | <type> | <sys> | <res><qualified-name>
Table C-3 describes the specific object CLI notations.
Table C-3 Specific object notations
ExpansionDefinitionDoc NotationSpecific object CLI Notations
serverManagement servername
server<server>
[server:]clus-nameCluster namecluster<clus>
[[server:]clus-name:]grpGroup namegrp<grp>
[[server:]clus-name:]typeResource type nametype<type>
[[server:]clus-name:]sysSystem namesys<sys>
[[server:]clus-name:]res-nameResource nameres<res>
417Command line interfaceCLI usage
Table C-3 Specific object notations (continued)
ExpansionDefinitionDoc NotationSpecific object CLI Notations
attr-nameAttribute nameattr<attr>
Use of qualified and unqualified namesYou can use the -help option on any command to display the exact options andobject specifications for that command.
The following rules for object specification are common across all commands:
■ <qualified-name> ::= <server> | <cluster> | <grp> | <type> | <sys> | <res>If the name is not fully qualified, the first object that matches the name isused.
■ Limit the use of qualified names (such as server:cluster:group) to thosecommand elements that require only one object. These elements include optionssuch as -value and -state.
■ For the -list and -display options, specify unqualified names only.
■ For the -display option, you can specify a list of unqualified names. If youspecify the name, then objects that have any one of the names are displayed.If you do not specify any names, all objects are displayed (subject to the limitsthat are imposed by other options).
Output options summaryCommands that output cluster object information usually offer the four outputoptions that are described below. When available, the output options (-list, -display,-value, and -state) are the first options in the Help output for the command. Othercommand options affect command operation and take action on cluster objects.
Table C-4 displays the various output options.
Command line interfaceCLI usage
418
Table C-4 Output options
What objects are chosenWhat is displayedOption
Objects may be filtered.
If -server <server> is given, onlyobjects in that server are selected. If-clus <cluster> is given, only objectsin that cluster are selected, etc. A listtable may be empty if the filter objectname (server or cluster) does notexist.
Lists all objects of the type, limitedby the other options. Displays theancestors’ names. For example, forgroups, the group name, cluster nameand management server names aredisplayed.
-list
Objects may be filtered.
If -server <server> is given only theseobjects in that server is selected. If-clus <clus-name> is given, only thoseobjects in a cluster with the givenname is selected, etc.
Displays all attributes of all theobjects of the type, limited by theother options. For local attributes,values for all contexts are shown.
-display
You specify exactly one object bygiving a qualified name.
Displays a single attribute value fora single object. If the attribute islocal, the -sys option is required.
-value
You specify exactly one object bygiving a qualified name.
Displays a single state value. If theattribute is local, the -sys option isrequired.
-state
Version output optionThe version output option [-version] returns the management server versionnumber when appended to any CLI command.
For example:
gaxxx [-version]
CLI commandsThese sections describe the various CLI commands that are used to obtaininformation and perform tasks on both the management server objects and clusterobjects.
Table C-5 describes the CLI commands.
419Command line interfaceCLI commands
Table C-5 CLI commands
DescriptionCLI command
Provides a connection to the local management server.
For additional information:
See galogin on page 422.
galogin
Removes a connection to the local management server.
For additional information:
See galogout on page 424.
galogout
Provides managed cluster information and operations
For additional information:
See gaclus on page 425.
gaclus
Performs the configuration file operations
For additional information:
See gaconf on page 428.
gaconf
Provides information about the database and performs databaseoperations on the local management server
For additional information:
See gadb on page 429.
gadb
Restores the database from an archive
For additional information:
See gadbrestore on page 432.
gadbrestore
Gathers system state and cluster configuration information fortroubleshooting purposes
For additional information :
See gagetcf on page 433.
gagetcf
Provides service group information and performs service groupoperations on the local management server
For additional information:
See gagrp on page 434.
gagrp
Command line interfaceCLI commands
420
Table C-5 CLI commands (continued)
DescriptionCLI command
Provides information about resources and performs resourceoperations on the local management server
For additional information:
See gares on page 441.
gares
Provides information about the local management server and performsmanagement server operations
For additional information:
See gaserver on page 445.
gaserver
Provides cluster system information and performs system operationson the local management server
For additional information:
See gasys on page 449.
gasys
Provides resource type information and performs resource operationson the local management server
For additional information:
See gatype on page 452.
gatype
Provides user information and operations
For additional information:
See gauser on page 455.
gauser
421Command line interfaceCLI commands
galogingalogin – provides a connection to the local management server
SYNOPSISgalogin -username domain domainType [-passfile "path to password
file"]
galogin -username@domain@domainType [-passfile <file_name>]
galogin -help
DescriptionThe galogin command provides a user context for all subsequent commands tobe run. All commands following the galogin command are run in context of theusername used in the galogin command.
The galogin command can also be entered with the username, domain, domaintype, and passfile as arguments. The passfile argument is the path to the passwordfile.
If thegalogin command is entered without options or arguments, then thegalogincommand prompts the user for a username, password, domain name, and domaintype. If the responses are correct, then the user is authenticated and can runsubsequent commands using this context.
Optionsusername domain domainType [-passfile "path to password file"]
Provides a connection to the local management server, a task which includesuser authentication
username@domain@domainType [-passfile <file_name>]Provides a connection to the local management server, a task which includesuser authentication
-helpProvides basic command usage information. Version and copyrightinformation only for this command.
ExamplesLog in to the local management server as the user "Administrator".
Command line interfacegalogin
422
galogin
Enter user name: root
Enter domain name: thor310.veritas.com
Enter domain type [ Windows | nis | nisplus | unixpwd | ldap ]:
unixpwd
Enter password:
Connecting to Management Server...
Login successful.
Log in using the other command options as described above.
galogin v006274@enterprise@Windows
Enter password:
Connecting to Management Server...
Login successful.
------------------------------------------
galogin v006274@enterprise@Windows -passfile "c:\passwd.txt"
Connecting to Management Server...
Login successful.
See alsogalogout
423Command line interfacegalogin
galogoutgalogout – removes a connection to the local management server
SYNOPSISgalogout [-help]
DescriptionThe galogout command removes the users context for running the VCSManagement Console commands. Any subsequent commands will requiregaloginto be run again.
The galogout command takes no options or arguments.
Options-help
Provides basic command usage information. Version and copyrightinformation only for this command.
ExamplesLogout from the local management server.
galogout
Logout successful.
See alsogalogin
Command line interfacegalogout
424
gaclusgaclus – provides managed cluster information and operations
SYNOPSISgaclus -list [-server server]
gaclus -display [cluster...] [-server server]
gaclus -state [cluster...] [-server server]
gaclus -value cluster attr
gaclus [-help]
DescriptionThe gaclus command provides various cluster information as requested, includingparent information and attribute values.
Options-list [-server server]
Lists all clusters or only those clusters managed by the specified managementserver.
No argument indicates all clusters managed by all management servers.
[-server server] indicates clusters managed by management server server.
The output includes a header row and one row for each cluster. Each rowcontains the cluster name and its parent management server name. Theheader looks like:
#Cluster Server
-display [cluster...] [-server server]Displays all cluster attribute values for the specified clusters. You can specifyindividual cluster names, clusters managed by a particular managementserver, or all managed clusters.
No argument indicates clusters managed by all management servers.
[cluster ...] is a list of one or more clusters.
[-server server] indicates all clusters managed by the management serverserver.
425Command line interfacegaclus
The output includes a header row and one row for each cluster. Each rowcontains the cluster name, parent management server name, attribute name,attribute scope, and attribute value. The header looks like:
#Cluster Server Attribute Scope Value
-state [cluster...] [-server server]Displays the state of the specified clusters. You can specify individual clusternames, clusters managed by a particular a management server, or all managedclusters.
No argument indicates clusters managed by all management servers. Theoutput lists the state values requested.
[cluster ...] is a list of one or more clusters.
[-server server] indicates all clusters managed by the management serverserver.
-value cluster attrDisplays the value of attribute attr on cluster cluster. The output is thesingle attribute value requested.
-helpProvides basic command usage information.
ExamplesList the clusters in the management server qasite171.
gaclus -list -server qasite171
#Cluster Server
VCSCluster01 qasite171
Clus163_164 qasite171
Display the cluster attribute values for the cluster Clus401_402.
gaclus -display Clus401_402
#Cluster Server Attribute Scope Value
Clus401_402 MSHOU Administrators global administrator
Clus401_402 MSHOU AllowNativeCliUsers global 0
Clus401_402 MSHOU ClusterLocation global
Clus401_402 MSHOU ClusterName global Clus401_402
Clus401_402 MSHOU ClusterOwner global
Clus401_402 MSHOU CompareRSM global 0
Command line interfacegaclus
426
Clus401_402 MSHOU CounterInterval global 5
Clus401_402 MSHOU DumpingMembership global 0
Clus401_402 MSHOU EngineClass global RT
Clus401_402 MSHOU EnginePriority global
Clus401_402 MSHOU GUIAddress global none
Clus401_402 MSHOU GroupLimit global 200
Clus401_402 MSHOU HAConnectInterval global 5
Clus401_402 MSHOU HacliUserLevel global NONE
Clus401_402 MSHOU LastIAA global 0
Clus401_402 MSHOU LockMemory global ALL
Clus401_402 MSHOU LogSize global 33554432
Clus401_402 MSHOU MajorVersion global 2
Clus401_402 MSHOU MSConnectInterval global 5
Clus401_402 MSHOU MinorVersion globaClus401_402 MSHOU Notifier
global Host: none Queue: 30 Severity: Information State: none
Clus401_402 MSHOU PanicOnNoMem global 0
Clus401_402 MSHOU PrintMsg global 0
Clus401_402 MSHOU ProcessClass global TS
Clus401_402 MSHOU ProcessPriority global
Clus401_402 MSHOU ReadOnly global 1
Clus401_402 MSHOU ResourceLimit global 5000
Clus401_402 MSHOU SourceFile global .\main.cf
Clus401_402 MSHOU State global 4
Clus401_402 MSHOU SysName global
Clus401_402 MSHOU SystemList global
Clus401_402 MSHOU TimeoutIAA global 180
Clus401_402 MSHOU TypeLimit global 100
Clus401_402 MSHOU UserNames global administrator Clus401_402
MSHOU VCSMode global VCS\Clus401_402 MSHOU VCSNotifierState
global none Clus401_402 MSHOU lastVCSLog global 1970-01-
01T00:00:00.0Z
Display the value of the attribute ResourceLimit for the cluster VCSCluster01.
gaclus -value VCSCluster01 ResourceLimit
output is:
5000
427Command line interfacegaclus
gaconfgaconf – performs configuration file operations.
SYNOPSISgaconf -makerw [cluster]
gaconf -dump [-makero] [cluster]
gaconf [-help]
DescriptionThis command allows (1) change of configuration on the target cluster to read-write(-makerw), save of configuration changes to cluster main.cf file (-dump), andchange of configuration to read-only (-dump -makero).
Options-makerw
Makes the target cluster configuration read/write.
-makeroMakes the configuration file read only.
-dump [-makero]Saves and makes read-only.
-helpProvides basic command usage information.
Command line interfacegaconf
428
gadbgadb – provides information about the database and performs database operationson the local management server
SYNOPSISgadb -grant CCAVAILGUEST [pwd]
gadb -modify CCAVAILGUEST [pwd]
gadb -revoke CCAVAILGUEST
gadb -backup -to archive
gadb -info
gadb -prune DataType -oldest [Integer TimeUnit | -all]
DescriptionThe gadb command provides information about the management server database.Operational commands, such as backup and prune, provide standard databaseadministration. You can also grant, modify, or revoke access from an externalguest account.
Options-grant CCAVAILGUEST [pwd]
Gives the guest account (CCAVAILGUEST) access to the database. pwd is thepassword you can specify for the account.
-modify CCAVAILGUEST [pwd]Modifies the guest account’s password to the one specified.
-revoke CCAVAILGUESTRemoves the guest account access to the database.
-backup -to archiveSaves a backup copy of the database and the transaction log. The database isbacked up to the archive file archive, which includes the file directory path.The transaction log is saved to \CCAvailDb\Log\CCAvailDb.log under theinstallation directory.
-infoProvides detailed information on the database including name, size, location,backup status, prune status, and oldest record dates.
429Command line interfacegadb
-prune DataType -oldest [Integer TimeUnit | -all]Removes specified data from the database. You specify the type and age ofdata to remove. Data older than the specified time interval, which is evaluatedstarting today, is removed.
DataType s is either Clusters, Log, or Rptout and specifies the type of datato remove:
Clusters indicates to remove cluster historical data only. Log entries andreport outputs (except for those associated with deleted report jobs) are notremoved. Specifically, cluster historical data includes:
--Objects that have been deleted by the user including deleted cluster objects,deleted report jobs, and their associated outputs.
--Historical values in the time period. This means that the latest values ofattributes are not removed, even if in the specified time period.
Log indicates to remove log entries only.
Rptout indicates to remove report outputs only.
-oldest [Integer TimeUnit | -all]
Starting today, remove data that is older than the indicated time period, orspecify all data.
Integer is the number of years, months, weeks, or days to remove.
TimeUnit is year, month, week, or day, corresponding to the Integer specified.
-all indicates to remove all data (over time) of the specified type.
ExamplesDisplay general information about the local management server database.
gadb -info
#Database Information
Database Status
Attribute Value
Creation date May 21, 2004 3:53:11 PM
Database name CCAvailDb
Database path
C:\PROGRA~1\VERITAS\COMMAN~1\AVAILA~1\CCAVAI~1\Data
Date of last successful backup Not available
Oldest log May 21, 2004 3:45:40 PM
Command line interfacegadb
430
Oldest report output May 22, 2004 6:00:03 PM
Server name VERITAS_DBMS_HOUWIN407
Size, allocated 8.461MB
Size, used (approximate) 6.656MB
Space on volume, available 13,423.035MB
Status of current backup Undefined
Status of current prune Undefined
Database Guest Access
Attribute Value
Guest access Disabled
Guest account name CCAVAILGUEST
Database Server information
Attribute Value
IP Address:Port 10.141.11.107:2993
Server name VERITAS_DBMS_HOUWIN407
Server version 2.00.028
See alsogadbrestore
431Command line interfacegadb
gadbrestoregadbrestore – restores the database from an archive
SYNOPSISgadbrestore -archive archive file -data DatabaseDataDir
DescriptionThe gadbrestore command restores the management server database from apreviously saved archive.
Option-archive ArchiveFile -data DatabaseDataDir
This option specifies the full path and file name of an existing databasearchive, as well as the directory of the CCAvailDb.db database that is to berestored from the archive. This path and file name includes a .1 extension.If the database backup resulted in more than one archive file, other archivefiles with extensions .2, .3, and so on are in the same directory.
See alsogadb
Command line interfacegadbrestore
432
gagetcfgagetcf – gathers system state and cluster configuration information fortroubleshooting purposes
SYNOPSISgagetcf - to dir directory
gagetcf [-help]
DescriptionThe gagetcf command gathers information (log files) about the managementserver, cluster, and the status of resources. To run this script, enter the commandon each system. The output from this script is placed in a tar file on each clustersystem.
Options-to dir -directory
Specifies the directory to place the tar files.
-helpProvides basic command usage information.
433Command line interfacegagetcf
gagrpgagrp – provides service group information and performs service group operationson the local management server
SYNOPSISgagrp -list [-clus cluster] [-server server]
gagrp -display [grp...] [-clus cluster][-server server]
gagrp -state [grp...] [-clus cluster][-server server]
gagrp -value grp attr [-sys sys]
gagrp -clearadminwait [-fault] grp -sys sysname
gagrp -clear grp [-sys sys]
gagrp -clear grp [-sys sys] [-rclus cluster | -localclus]
gagrp -online <grp> -sys <sys-name> [-propogate][-ejectlowpri]
[-force] [-nopre][-checkpartial <sys-name>][-rclus <cluster>]
gagrp -online <grp> -any [-force] [-ejectlowpri][-checkpartial
<sys-name>][-rclus <cluster>]
gagrp -offline grp -sys sys [-ifprobed] [-force]
gagrp -offline grp -any [-ifprobed] [-force]
gagrp -switch grp [-to sys] [-torclus cluster]
gagrp -switch grp -any [-clus cluster]
gagrp -switch grp [-ejectlowpri] [-to sys] [-torclus <cluster>]
gagrp -switch grp [-ejectlowpri] -any [-torclus cluster]
gagrp -freeze grp [-persistent]
gagrp -freeze grp [-rclus cluster | -localclus]
gagrp -unfreeze grp [-persistent]
gagrp -enable grp [-sys sys]
gagrp -disable grp [-sys sys]
gagrp -enableresources grp
gagrp -disableresources grp
gagrp -flush grp -sys sys
gagrp -autoenable grp -sys sys
gagrp [-help]
DescriptionThe gagrp command provides information about service groups, including parentobject data and attribute values. Operational commands, such as online, offline,switch, freeze, and enable, take the same actions that they do in VCS. These
Command line interfacegagrp
434
commands are forwarded to the VCS engine, and any limitations and errors thatare returned are from VCS.
Options-list [-clus cluster] [-server server]
Lists all groups, groups in a specific cluster, or groups managed by a specificmanagement server.
No argument indicates all groups managed by all management servers.
[-clus cluster] indicates all groups in the cluster cluster.
[-server server] indicates all groups managed by the management serverserver.
The output includes a header row and one row for each group. Each rowcontains the group, parent cluster, and parent management server names.The header looks like:
#Group Cluster Server
-display [grp...] [-clus cluster] [-server server]Displays all group attribute values for the specified groups. You can specifyindividual group names, groups in a specific cluster, or groups managed bya specific management server.
No argument indicates all groups managed by all management servers.
[grp ...] is a list of one or more groups.
[-clus cluster] indicates all groups in the cluster cluster.
[-server server] indicates all groups in the management server server.
The output includes a header row and one row for each group. Each rowcontains the group name, parent cluster name, parent management servername, attribute name, attribute scope, and attribute value. The header lookslike:
#Group Cluster Server Attribute Scope Value
-state [grp...] [-clus cluster] [-server server]Displays the state of the specified groups in all contexts (on all systems). Youcan specify group names, groups in a specific cluster, or groups managed bya specific management server.
No argument indicates all groups managed by all management servers.
[grp ...] is a list of one or more groups.
435Command line interfacegagrp
[-clus cluster] indicates all groups in the cluster cluster.
[-server server] indicates all groups managed by the management serverserver.
The output is the state values for all specified groups on all systems. Theheader looks like:
#Group Cluster Server Attribute System Value
The value under the Attribute header is always state.
-value grp attr [-sys sys]Displays the value of attribute attr on the group grp. The output is the singleattribute value requested.
[-sys sys] indicates a specific system sys; it is required for local attributes(which vary per system.) and not required for global attributes.
-clearadminwait [-fault] grp -sys sysnamegagrp -clear grp [-sys sys]Resources may enter an ADMIN_WAIT state in a service group due to any ofthe following reasons:
■ 0 = The offline function did not complete within the expected time.
■ 1 = The offline function was ineffective.
■ 2 = The online function did not complete within the expected time.
■ 3 = The online function was ineffective.
■ 4 = The resource was taken offline unexpectedly.
■ 5 = The monitor function consistently failed to complete within theexpected time.
This command clears the ADMIN_WAIT state for all resources. If VCScontinues to detect resources that are not in the required state, it resets theresources to the ADMIN_WAIT state. Issue the command with -fault optionto stop VCS from setting the resource to the ADMIN_WAIT state. Thiscommand (with the -fault option) has the following results:
■ If the resadminwait trigger was called for reasons 0 or 1, the resourcestate is set as ONLINE|UNABLE_TO_OFFLINE.
■ If the resadminwait trigger was called for reasons 2, 3, or 4, the resourcestate is set as FAULTED. Please note that when resources are set asFAULTED for these reasons, the clean function is not called.
-clear grp [-sys sys] [-rclus cluster | -localclus]Clears all faulted, non-persistent resources in the group grp on the systemsys, or on all systems if no system is specified for a remote cluster cluster
Command line interfacegagrp
436
or local cluster. Initiates a state change from FAULTED to OFFLINE, andautomatically initiates an online process if one was previously blocked.
-online grp -sys sys [-propogate] [-ejectlowpri] [-force] [-nopre] [-checkpartial sys][-rclus cluster]
Starts the group grp and brings its resources online on the system sys.
-sys sys indicates the system where you want to bring the group online. Useeither the -any or the -sys argument, not both.
[-force] indicates to bring the group online for the first time or to overridecluster authority.
[-nopre] indicates that the group can be brought online (normally determinedby the PreOnline event trigger).
[-checkpartial sys] indicates to bring online only those resources alreadyonline on the system sys.
[-rclus cluster] applies to global groups only; indicates to bring the grouponline on a system in the remote cluster cluster.
-online grp -any [-force] [-ejectlowpri] [-checkpartial sys] [-rclus cluster]Starts the group grp and brings its resources online on any system in thecluster.
-any indicates to bring the group online on any system in the cluster. Useeither the -any or the -sys argument, not both.
[-force] indicates to bring the group online for the first time or to overridecluster authority.
[-checkpartial sys] indicates to bring online only those resources alreadyonline on the system sys.
[-rclus cluster] applies to global groups only; indicates to bring the grouponline on a system in the remote cluster cluster.
-offline grp -sys sys [-ifprobed] [-force]Takes the group grp offline on the system sys. Use either the -any or the -sysargument, not both.
[-ifprobed] indicates to take the group offline only if all resources are probed(monitored to determine status) on the system.
[-force]indicates to take the group offline for the first time or to overridecluster authority
437Command line interfacegagrp
-offline grp -any [-ifprobed] [-force]Takes the group grp offline on any system. Use either the -any or the -sysargument, not both.
-switch grp [-to sys] [-torclus cluster]Switches the group grp to the system sys, or, in the case of a global group,to the remote cluster cluster.
-switch grp -any [-clus cluster]Switches the group grp to any system in cluster cluster.
-switch grp [-ejectlowpri] [-to sys] [-torclus cluster]Switches the group grp to the system sys, or, in the case of a global group,to the remote cluster cluster.
-switch grp [-ejectlowpri] -any [-torclus cluster]Switches the group grp to any system in the cluster, or, in the case of a globalgroup, to any system in the remote cluster cluster.
-freeze grp [-persistent]Freezes the group grp using the VCS freeze command.
[-persistent]indicates the freeze is maintained after a system is rebooted,or the engine is stopped and restarted. NOTE that the configuration must beread-write to use this option.
-freeze grp [-rclus cluster | -localclus]Freezes the group grp using the VCS freeze command on the remote clustercluster or on a local cluster.
-unfreeze grp [-persistent]Unfreezes the group grp using the VCS unfreeze command.
-enable grp [-sys sys]Enables the group grp on the system sys or on all systems. A group can bebrought online only if it is enabled.
-disable grp [-sys sys]Disables the group grp on the system sys or on all systems. A group cannotbe brought online or switched if it is disabled.
-enableresources grpEnables all resources of the group grp. A resource can be monitored only ifit is enabled.
-disableresources grpDisables all resources of the group grp. A resource cannot be monitored if itis disabled.
Command line interfacegagrp
438
-flush grp -sys sysClears the internal state of VCS for the group grp on the system sys. Usedwhen a group is waiting for a resource to come online.
-autoenable grp -sys sysAutoenables a group grp that is autodisabled on system sys. Groups areautodisabled until VCS probes all of the resources and determines if they areready to bring online. You may need to autoenable a group in certain situationswhere VCS does not.
-helpProvides basic command usage information.
ExamplesList all groups.
gagrp -list
#Group Cluster Server
ClusterService Clus163_164 QaSite407
FSGRP1 Clus163_164 QaSite407
SQL_GRP Clus163_164 QaSite407
SQL_GRP2 Clus163_164 QaSite407
CCAvail Clus163_164 QaSite407
Display the state of all groups.
gagrp -state
#GroupClusterServerAttributeSystemValue
AGroupSunClus1DiamondStateglobalOFFLINE
CCAvailSunClus1DiamondStatehousun7ONLINE
CCAvailSunClus1DiamondState housun9OFFLINE
ClusterServiceSunClus1DiamondState housun7 ONLINE
ClusterServiceSunClus1DiamondState housun9 OFFLINE
LfileSunClus1DiamondState housun7 ONLINE
LfileSunClus1DiamondState housun9 OFFLINE
NBU_2SunClus1DiamondState housun7 PARTIAL
NBU_2SunClus1DiamondState housun9 PARTIAL|STOPPING
Oracle_1SunClus1DiamondState housun7 OFFLINE
Oracle_1SunClus1DiamondState housun9 OFFLINE
TestGrpSunClus1DiamondState housun7 OFFLINE
TestGrpSunClus1DiamondState housun9 OFFLINE
WfileSunClus1DiamondState housun7 OFFLINE
WfileSunClus1DiamondState housun9 OFFLINE
439Command line interfacegagrp
db2_GRPSunClus1DiamondState housun7 OFFLINE
db2_GRPSunClus1DiamondState housun9 OFFLINE
Command line interfacegagrp
440
garesgares – provides information about resources and performs resource operationson the local management server
SYNOPSISgares -list [-grp grp] [-clus cluster]
gares -display [res-name...] [-grp grp] [-clus cluster]
gares -state [res-name...] [-grp grp] [-clus cluster]
gares -value res attr [-sys sys]
gares -clear res [-sys sys]
gares -online [-force] res -sys sys
gares -offline [-ignoreparent | -parentprop] res -sys sys
gares -refreshinfo res [-sys sys] [-rclus cluster]
gares -flushinfo res [-sys sys] [-rclus cluster]
gares -offprop [-ignoreparent] res -sys sys
gares -probe res -sys sys
gares -override res staticattribute
gares -undo_override res staticattribute
gares [-help]
DescriptionThe gares command provides information about resources, including parentobject data and attribute values. Operational commands, such as online, offline,and probe, take the same actions that they do in VCS. The commands are forwardedto the VCS engine, and any limitations and errors that are returned are from VCS.
Options-list [-grp grp] [-clus cluster]
Lists all resources, resources in a specific group, resources in a specific cluster,or resources managed by a specific management server.
No argument indicates all resources managed by all management servers.
[-grp grp] indicates all resources within the group grp.
[-clus cluster] indicates all resources within the cluster cluster.
The output includes a header row and one row for each resource. Each rowcontains the resource name, parent group, parent cluster, and parentmanagement server names. The header looks like:
441Command line interfacegares
#Resource Group Cluster
-display [res-name...][-grp grp][-clus cluster]Displays all resource attribute values for the specified resources. You canspecify individual resource names, resources in a specific group, or resourcesin a specific cluster.
No argument indicates all resources managed by all management servers.
[res-name ...] is a list of one or more resources.
[-grp grp] indicates all resources in the group grp.
[-clus cluster] indicates all resources in this cluster cluster.
The output includes a header row and one row for each resource. Each rowcontains the resource name, parent group name, parent cluster name, parentmanagement server name, attribute name, attribute scope, and attributevalue. The header looks like:
#Resource Group Cluster Attribute Scope Value
-state [res-name...] [-grp grp] [-clus cluster]Displays the state of the specified resources in all contexts (on all systems).You can specify resource names, resources in a specific group, resources ina specific cluster, or resources managed by a specific management server.
No argument indicates all resources managed by all management servers.
[res-name ...] is a list of one or more resources.
[-grp grp] indicates all resources in the group grp.
[-clus cluster] indicates all resources in the cluster cluster.
The output is the state values for all specified resources on all systems. Theheader looks like:
#Resource Group Cluster Attribute System Value
The value under the Attribute header is always state.
-value res attr [-sys sys]Displays the value of attribute attr on a resource res. The output is the singleattribute value requested.
[-sys sys] indicates a specific system sys; it is required for local attributes(which vary per system) and not required for global attributes.
Command line interfacegares
442
-clear res [-sys sys]Clears the resource res on the system sys, or on all systems if no system isspecified. Initiates a state change from FAULTED to OFFLINE, andautomatically initiates an online process if one was previously blocked.
-online [-force] res -sys sysBrings the resource res online on the system sys.
[-force] indicates to bring the resource online for the first time or to overridecluster authority.
-offline [-ignoreparent | -parentprop] res -sys sysTakes the resource res offline on the system sys.
[-ignoreparent] indicates to take the resource offline even if its parentresources in the group are online. This option does not work if taking theresources offline violates the group dependency.
-refreshinfo res [-sys sys] [-rclus cluster]Updates the value of the ResourceInfo attribute for the resource res if theresource is online.
[-sys sys] indicates a system name other than local system(s).
[-rclus cluster] indicates a remote cluster.
If no system or remote cluster is specified, this occurs on local system(s)where the resource is online.
-flushinfo res [-sys sys] [-rclus cluster]Flushes the value of the ResourceInfo attribute for the resource res if theresource is online. As a service group is brought online or taken offline, theresources within the group are brought online and taken offline. If the onlineor offline operation hangs on a particular resource, flush the service groupto halt the operation on the resources waiting to go online or offline. Flushinga service group typically leaves the cluster in a partial state. After completingthis process, resolve the issue with the particular resource (if necessary) andproceed with starting or stopping the service group..
[-sys sys] indicates a system name other than local system(s).
[-rclus cluster] indicates a remote cluster.
If no system or remote cluster is specified, this occurs on local system(s)where the resource is online.
-offprop [-ignoreparent] res -sys sysTakes the resource res offline and propagates the command to its childrenon the system sys.
443Command line interfacegares
-probe res -sys sysMonitors the resource res on the system sys to determine its status.
-override res staticattributeOverride a resource type's static attribute.
-undo_override res staticattributeUndo the override on a resource type's static attribute.
-helpProvides basic command usage information.
EXAMPLESList all resources.
gares -list
#Resource Group Cluster Server
webip ClusterService W2KClus121_122 QaSite181
VRTSweb ClusterService W2KClus121_122 QaSite181
FS_DISKRES FS_TEST W2KClus121_122 QaSite181
FS_FILESHARE FS_TEST W2KClus121_122 QaSite181
FS_IP FS_TEST W2KClus121_122 QaSite181
FS_LANMAN FS_TEST W2KClus121_122 QaSite181
FS_MOUNT FS_TEST W2KClus121_122 QaSite181
FS_NIC FS_TEST W2KClus121_122 QaSite181
CCAvail_ClusterConfig CCAvail W2KClus121_122 QaSite181
CCAvail_ClusterMonitor CCAvail W2KClus121_122 QaSite181
Command line interfacegares
444
gaservergaserver– provides information about the local management server and performsmanagement server operations
SYNOPSISgaserver -list [-local]
gaserver -display [server...]
gaserver -state [server...]
gaserver -value server attr
gaserver -add id name address [port] -import certificate_file
gaserver -import certificate file site name
gaserver -delete server
gaserver -delete -id id
gaserver -delete [-local]
gaserver -listab
gaserver -addab address [port]
gaserver -deleteab address
gaserver -addclus -clusterhost host [-clusterport port] [-securitytype
vcs*/vxss] -username username -password password [-domain domain]
[-domaintype domaintype] [-broker broker:port] [-site site name]
[-makeadmin true*/false]
gaserver [-help]
DescriptionThegaserver command provides information about the local management server,including attribute values. A modify option enables you to change the port numberand IP address of the management server. Options are also available to add andremove peer management servers.
Options-list [-local]
Lists all peer management servers.
The output includes a header row and one row for each management serverwith server name, IP address, Port number (always 14145), and ID. The headerlooks like:
#Name Address Port ID
445Command line interfacegaserver
-display [server...]Displays all management server attribute values for the specified servers.No argument indicates all management servers.
[server...] is a list of one or more management servers.
The output includes a header row and one row for each cluster. Each rowcontains the cluster name, parent management server name, attribute name,attribute scope, and attribute value. The header looks like:
#Server[home] Attribute Scope Value
-state [server...]Displays the state of the specified management servers.
[server...] is a list of one or more management servers.
The output is the single state value requested.
-value server attrDisplays the value of attribute attr on the management server server. Theoutput is the single attribute value requested.
-add id name address [port]Adds the specified management server name to the enterprise. id is themanagement server id.
-import certificate_fileImports the authentication broker certificate file from one peer managementserver to the other when upgrading a peer management server to version 5.1or later.
-import certificate file site nameImports the authentication broker certificate file from one peer managementserver to the other when upgrading a peer management server to version 5.1or later.
-delete serverRemoves the management server server from the enterprise. The namedmanagement server will not be re-connected once it is disconnected.
-delete -id idRemoves a peer management server by id rather than by name. This commandis especially useful for removing a peer management server with the samename as another.
-delete [-local]Removes the local management server from the enterprise. The managementserver will form an enterprise consisting of one management server (itself).
Command line interfacegaserver
446
-listabLists all existing Symantec Product Authentication Service authenticationbrokers in a table.
The output includes a header row and one row for each authentication broker.Each row contains an IP address and port number. The header looks like:
#Address Port
-addab address [port]Adds a new Symantec Product Authentication Service authentication broker.No validation is performed.
-deleteab addressDeletes an existing Symantec Product Authentication Service authenticationbroker. The address specified must match one displayed in -listab output.
-clusterhost hostThe name / IP address of the VCS system to connect to.
-clusterport portThis is an optional parameter. The VCS port (Default is 14141).
-securitytypeParameter for the security type. For example: vcs--classic VCS authentication,vxss - secure cluster using VxSS
-username username, -password passwordOnly these two parameters are needed for classic vcs clusters.
-domain domain, -domaintype domaintype, -broker broker:portThese parameters are required only if adding secure clusters.
-site siteOptional name of the site the cluster should be added to. If the site does notexist, a new one will be created.
-makeadminDenotes whether the user issuing this command should be made anadministrator on the newly added cluster. The galogin command shouldhave been issued earlier.
-helpProvides basic command usage information.
EXAMPLESList all management servers and attributes.
447Command line interfacegaserver
gaserver -list
#Name Address Port ID
QaSite407 10.141.11.107 14145 be2b0098-d9b9-4bd8-b00e-
27b9f53db080
Command line interfacegaserver
448
gasysgasys – provides cluster system information and performs system operations onthe local management server
SYNOPSISgasys -list [-clus cluster] [-server server]
gasys -display [sys...] [-clus cluster] [-server server]
gasys -state [sys...] [-clus cluster] [-server server]
gasys -value sys attr
gasys -freeze sys [-persistent] [-evacuate]
gasys -unfreeze sys [-persistent]
gasys [-help]
DescriptionThe gasys command provides information about systems, including parent objectdata and attribute values. Operational commands, such as freeze, take the sameactions that they do in VCS. The commands are forwarded to the VCS engine, andany limitations and errors that are returned are from VCS.
Options-list [-clus cluster] [-server server]
Lists all systems, systems in a specific cluster, or systems managed by aspecific management server.
No argument indicates all systems managed by all management servers.
[-clus cluster] indicates all systems in the cluster cluster.
[-server server] indicates all systems in the management server server.
The output includes a header row and one row for each system. Each rowcontains the system, parent cluster, and parent management server names.The header looks like:
#System Cluster Server
Note: This list may be empty if you supply a cluster or management servername that does not exist in the enterprise.
449Command line interfacegasys
-display [sys...] [-clus cluster] [-server server]Displays all system attribute values for the specified systems. You can specifysystem names, systems in a specific cluster, or systems managed by a specificmanagement server.
No argument indicates all systems managed by all management servers.
[sys ...] is a list of one or more systems.
[-clus cluster] indicates all systems in the cluster cluster.
[-server server] indicates all systems managed by the management serverserver.
The output includes a header row and one row for each system. Each rowcontains the system name, parent cluster name, parent management servername, attribute name, attribute scope, and attribute value. The header lookslike:
#System Cluster Server Attribute Scope Value
-state [sys...] [-clus cluster] [-server server]Displays the state of the specified systems. You must specify sys if state is alocal attribute; sys is optional if state is a global attribute. You can specifyindividual system names, systems in a specific cluster, or systems managedby a specific management server.
No argument indicates all systems managed by all management servers.
[sys ...] is a list of one or more systems.
[-clus cluster] indicates all systems in the cluster cluster.
[-server server] indicates all systems managed by the management serverserver.
The output includes a header row and one row for each system. Each rowcontains the system name, parent cluster name, parent management servername, attribute name, attribute scope, and attribute value. The header lookslike:
#System Cluster Server Attribute Scope Value
The value under the Attribute header is always state.
-value sys attrDisplays the value of attribute attr on the system sys. The output is the singleattribute value requested.
Command line interfacegasys
450
-freeze sys [-persistent] [-evacuate]Freezes the system sys using the VCS freeze command. Groups are thenprevented from being brought online on this system.
[-persistent] indicates to remember the frozen state when the cluster isrebooted.
[-evacuate] fails over any active groups to another system in the clusterbefore freezing the system.
-unfreeze sys [-persistent]Unfreezes the system sys using the VCS unfreeze command.
-helpProvides basic command usage information.
EXAMPLESList all systems and their parents.
gasys -list
#System Cluster Server
HOUWIN163 Clus163_164 QaSite407
HOUWIN164 Clus163_164 QaSite407
Freeze the system HOUWIN163.
gasys -freeze HOUWIN163
Success
451Command line interfacegasys
gatypegatype – provides resource type information and performs resource operationson the local management server
SYNOPSISgatype -list [-clus cluster] [-server server]
gatype -display [type...] [-clus cluster] [-server server]
gatype -value type attr [-sys sys]
gatype [-help]
DescriptionThe gatype command provides information about resource types including parentobject data and attribute values.
Options-list [-clus cluster] [-server server]
Lists all resource types, types in a specific group, types in a specific cluster,or types managed by a specific management server.
No argument indicates all resource types managed by all management servers.
[-clus cluster] indicates all resource types in the cluster cluster.
[-server server] indicates all resource types managed by the managementserver server.
The output includes a header row and one row for each resource type. Eachrow contains the resource type, parent cluster, and parent management servernames. The header looks like:
#Type Cluster Server
-display [type...] [-clus cluster] [-server server]Displays all resource type attribute values for the specified type. You canspecify individual resource type names, types in a specific group, types in aspecific cluster, or types managed by a specific management server.
No argument indicates all resource types in all clusters.
[type ...] is a list of one or more resource types.
[-clus cluster] indicates all resource types in the cluster cluster.
Command line interfacegatype
452
[-server server] indicates all resource types managed by the managementserver server.
The output includes a header row and one row for each resource type. Eachrow contains the resource type name, parent cluster name, parentmanagement server name, attribute name, attribute scope, and attributevalue. The header looks like:
#Type Cluster Server Attribute Scope Value
-value type attr [-sys sys]Displays the value of attribute attr on the resource type type. The output isthe single attribute value requested.
[-sys sys] indicates a specific system sys; it is required for local attributes(which vary per system.) and not required for global attributes.
-helpProvides basic command usage information.
ExamplesList all resource types and parents.
gatype -list
#Type Cluster Server
CompositeFileShare Clus163_164 QaSite407
DiskRes Clus163_164 QaSite407
E2KProtocol Clus163_164 QaSite407
E2KService Clus163_164 QaSite407
ElifNone Clus163_164 QaSite407
Exchange Clus163_164 QaSite407
FileNone Clus163_164 QaSite407
FileOnOff Clus163_164 QaSite407
FileOnOnly Clus163_164 QaSite407
FileShare Clus163_164 QaSite407
GenericService Clus163_164 QaSite407
IP Clus163_164 QaSite407
IPMultiNicPlus Clus163_164 QaSite407
Lanman Clus163_164 QaSite407
Mount Clus163_164 QaSite407
MountV Clus163_164 QaSite407
NIC Clus163_164 QaSite407
NotifierMngr Clus163_164 QaSite407
453Command line interfacegatype
Oracle Clus163_164 QaSite407
Phantom Clus163_164 QaSite407
PrintShare Clus163_164 QaSite407
PrintSpool Clus163_164 QaSite407
Process Clus163_164 QaSite407
Proxy Clus163_164 QaSite407
RegRep Clus163_164 QaSite407
SQLServer2000 Clus163_164 QaSite407
ServiceMonitor Clus163_164 QaSite407
Sqlnet Clus163_164 QaSite407
VMDg Clus163_164 QaSite407
ClusterMonitorConfig Clus163_164 QaSite407
Command line interfacegatype
454
gausergauser – provides user information and operations
SYNOPSISgauser -list
gauser -add name domain domainType
gauser -delete name domain domainType
gauser -admin name domain domainType
gauser [-help]
DescriptionThe gauser command provides a listing of the management server user accountswith their domain information. These are the domain user accounts that havebeen added to the management server. You can add and delete users with thegauser command.
Options-list
Lists users in this management server.
The output includes a header row and one row for each user. Each row containsthe user name, domain, and domain type. The header looks like:
#Name Domain Type
-add user-name domain domainTypeAdds the useruser-name to this management server with guest access rights.
name is the domain user name you want to add.
domain is the name of the domain for this user
domainType is the domain type (nt, nis, nisplus, vx, or unixpwd) of the specifieddomain
-delete name domain domainTypeRemoves the specified user from this management server
name is the user name you want to remove.
domain is the name of the domain for this user
455Command line interfacegauser
domainType is the domain type (nt, nis, nisplus, vx, or unixpwd) of the specifieddomain
-admin name domain domainTypeAdds the specified user with Administrator access rights to this managementserver. You do not need to log in (using galogin) to the management serverbefore using this command, but you must be logged in on the system as amember of the Administrators group (Windows) or with an uid of 0 (UNIX).If the user account already exists, then its access rights are set toAdministrator for this management server.
Note: Use the -administrator option of gauser if you have lost youradministrator account name or password. It allows you to add an administratoraccount without logging in.
Note:You must be logged in on the system as a member of the Administratorsgroup (Windows) or with an uid of 0 (UNIX) to use this command.
name is the Administrator user name you want to add.
domain is the name of the domain for this user
domainType is the domain type (nt, nis, nisplus, vx, or unixpwd) of the specifieddomain
-helpProvides basic command usage information.
ExamplesList all users in the local management server.
gauser -list
#Name Domain Type
Administrator HOULAB nt
Command line interfacegauser
456
Creating custom reports
This appendix includes the following topics:
■ Accessing the database information
■ About database schema object descriptions
■ About published database schema objects
■ Example statements
Accessing the database informationTo enable custom reporting, you must connect to the VCS Management Consolemanagement server database. Connect using an appropriate third-party databaseapplication. To use the third-party application, you must register the ODBC driverand then create an ODBC data source. You must also consult the documentationfor the third-party application to learn how to set up a connection to an externaldatabase.
Registering the ODBC driverYou must register the ODBC driver for ASA 10 before you can connect to thedatabase through ODBC. The required files are installed on the management serverbut the driver is not registered.
On Windows platforms, the files are in the following directory
C:\Program Files\Symantec\VRTScmcm\asa10\win32
Creating the ODBC data sourceUse the following procedure to create an ODBC data source for the VCSManagement Console management server database. Use this data source with a
DAppendix
third-party database application to generate custom reports from data in the guesttable views.
To create an ODBC data source on Windows platforms
1 Open the ODBC Data Source Administrator tool by selectingStart>Programs>Administrative Tools>Data Sources (ODBC)
2 Click the System DSN or User DSN tab, and then click Add.
3 Select the SQL Anywhere 10 driver and click Finish.
4 In the ODBC Adaptive Server Anywhere Configuration dialog box, enter aname for the data source, such as CMC Guest DSN.
5 Click the Login tab to configure logon information.
The User ID is CCAVAILGUEST. The password must be the same as the oneused to configure guest database access. You cannot connect to themanagement server database using the DSN unless the account is enabled.
See “Modifying guest access to the database ” on page 400.
6 Click the Database tab to configure database information.
The database server name is of the form CMC_ms_host_14994, wherems_hostis the host name of the management server host system. The database nameis VCSMCDb
Ensure that Stop database after last disconnect is unchecked.
7 Click the Network tab to configure network information.
Check the TCP/IP check box only. Ensure that no other protocols are checked.
Specify the following options in the options field: host=ms_host; port=14994
where ms_host is the host name of the management server host system.
8 Click the ODBC tab and test the connection.
A pop-up message about the Autostop parameters appears. Click Yes tocontinue the test.
If a pop-up message does not appear, ensure that Stop database after lastdisconnect is unchecked before you continue.
If the configuration is correct, you receive the following message:
Connection successful
9 Click OK to create the data source.
Creating custom reportsAccessing the database information
458
About database schema object descriptionsTable D-1 describes the published database schema objects.
Table D-1 Objects in the database schema
DescriptionObject
Only one enterprise object exists per database. This object is replicatedand made the same for all connected management servers.
Enterprise
Only one management server object exists per database. This objectcontains information about the local management server.
MServer
More than one schedule object can exist in the database. This objectcontains schedule information on the objects that are managed by thelocal management server.
Schedule
More than one cluster object can exist in the database. This objectcontains information about the clusters that are managed by the localmanagement server.
Cluster
More than one node object can exist in the database. This objectcontains information on the clustered nodes that are managed by thelocal management server.
Node
More than one resource type object can exist in the database. Thisobject contains information on the clustered resource types that aremanaged by the local management server.
Resource type
More than one service group object can exist in the database. Thisobject contains information on the clustered service groups that aremanaged by the local management server.
Group
More than one resource object can exist in the database. This objectcontains information on the group resources that are managed by thelocal management server
Resource
This object contains information about an event on a managed objector a user command on the local management server. Events onenterprise objects are not available.
Log
About published database schema objectsInformation in the database is presented in the views that contain historical andcurrent information about managed objects. Information about an object is storedas an attribute of the object.
459Creating custom reportsAbout database schema object descriptions
The user name, password, and data are case sensitive, but the names of the objectsare not. All database dates are stored in Greenwich Mean Time.
Information in the database can be read externally from the published databaseobjects. The following subsections describe each database object type.
Note:Use only the published list of database schema objects to retrieve informationfrom the database. Only the published database objects are maintained andcompatible from release to release of the VCS Management Console. Other objectsare subject to change without notice.
K2VW_ENTERPRISETable D-2 includes the available attribute information on this object type.
Table D-2 K2VW_ENTERPRISE Attribute Information
DescriptionAttribute
Not available.ConsolidatedState
Possible site extended attribute values.Site
Possible region extended attribute values.Region
Possible line of business (LOB) extended attribute values.LOB
Possible department extended attribute values.Department
Map of names of all extended attributes (name=object type. Forexample, LOB=4).
ExtendedAttributes
Fully qualified object name.fqn
Map of remote site IDs to connection information.RemoteSites
Map of application name to string representation of descriptionand list of groups.
Applications
Set of all application types.ApplicationType
Table D-3 includes the data available in the K2VW_ENTERPRISE table.
Creating custom reportsAbout published database schema objects
460
Table D-3 K2VW_ENTERPRISE Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject in the view.
IntegerObjectID
Name of the object.Varchar (256)ObjectName
Date the object was created.TimestampDateCreated
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_MServersTable D-4 includes the available attribute information on this object type.
461Creating custom reportsAbout published database schema objects
Table D-4 K2VW_MServer Attribute Information
DescriptionAttribute
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Fully qualified object name.fqn
Name of system where local management server isinstalled and running.
SysName
Port for local management server.Port
Array of time windows when the management server isdown.
DowntimeWindows
Platform name for management server.Platform
Version of the management server.Version
State of management server.State
State of management server.ConsolidatedState
State of management server before last transition.PreviousConsolidatedState
Last time the management server recorded its online state(in milliseconds).
UptimeTick
Table D-5 includes the data in the K2VW_MServer table.
Table D-5 K2VW_MServer Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Universal unique identifier of the object.Varchar (256)ObjectUuid
Name of the object.Varchar (256)ObjectName
Date the object was created.TimestampDateCreated
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Creating custom reportsAbout published database schema objects
462
Table D-5 K2VW_MServer Table Information (continued)
DescriptionData TypeColumn
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_ClustersTable D-6 includes the available attribute information on this object type.
Table D-6 K2VW_Cluster Attribute Information
DescriptionAttribute
Note: Refer to theVeritas Cluster Server Administrator’sGuide for a complete list of VCS attributes.
All VCS attributes on thecluster except for thefollowing: GlobalCounter,ClusterTime.
Cluster extended attribute "Site."Site
463Creating custom reportsAbout published database schema objects
Table D-6 K2VW_Cluster Attribute Information (continued)
DescriptionAttribute
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Periods of time when there is a configured maintenancewindow.
Maintenance
State of management server.ConsolidatedState
Fully qualified object name.fqn
Map of remote cluster names to remote cluster states.Global clusters only.
RClusterNameList
State of management server before last transition.PreviousConsolidatedState
Type of cluster. Value is ‘VCS’ for VCS clusters.ClusterType
Cluster extended attribute "Region."Region
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Platform name for the cluster.Platform
Map of remote cluster IDs to remote cluster states. Globalclusters only.
RClusterList
Table D-7 includes the data available in the K2VW_Cluster table.
Table D-7 K2VW_Cluster Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Universal unique identifier of the object.Varchar (256)ObjectUuid
Name of the object.Varchar (256)ObjectName
The parent of a cluster object is amanagement server object. This columncontains the unique database ID for theparent of this object.
IntegerParentID
Date the object was created.TimestampDateCreated
Creating custom reportsAbout published database schema objects
464
Table D-7 K2VW_Cluster Table Information (continued)
DescriptionData TypeColumn
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_GroupsTable D-8 includes the available attribute information on this object type.
Table D-8 K2VW_Group Attribute Information
DescriptionAttribute
Note: Refer to theVeritas Cluster Server Administrator’sGuide for a complete list of VCS attributes.
All VCS attributes on thegroup.
465Creating custom reportsAbout published database schema objects
Table D-8 K2VW_Group Attribute Information (continued)
DescriptionAttribute
Group extended attribute "Department."Department
Group extended attribute "LOB."LOB
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Fully qualified object name.fqn
Configured maintenance window for this group.MaintenanceWindow
State of management server.ConsolidatedState
State of management server before last transition.PreviousConsolidatedState
Table D-9 includes the data available in the K2VW_Group table.
Table D-9 K2VW_Group Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Name of the object.Varchar (256)ObjectName
The parent of a group object is a Clusterobject. This column contains the uniquedatabase ID for the parent of this object.
IntegerParentID
Date the object was created.TimestampDateCreated
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Creating custom reportsAbout published database schema objects
466
Table D-9 K2VW_Group Table Information (continued)
DescriptionData TypeColumn
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_NodesTable D-10 includes the available attribute information on this object type.
Table D-10 K2VW_Node Attribute Information
DescriptionAttribute
Note: Refer to theVeritas Cluster Server Administrator’sGuide for a complete list of VCS attributes.
All VCS attributes on the nodeexcept for the following:LoadTimeCounter.
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Fully qualified object name.fqn
Platform name of the node.Platform
State of management server.ConsolidatedState
467Creating custom reportsAbout published database schema objects
Table D-10 K2VW_Node Attribute Information (continued)
DescriptionAttribute
State of management server before last transition.PreviousConsolidatedState
Table D-11 includes the data available in the K2VW_Nodetable.
Table D-11 K2VW_Node Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Name of the object.Varchar (256)ObjectName
The parent of a node object is a Clusterobject. This column contains the uniquedatabase ID for the parent of this object.
IntegerParentID
Date the object was created.TimestampDateCreated
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
Creating custom reportsAbout published database schema objects
468
Table D-11 K2VW_Node Table Information (continued)
DescriptionData TypeColumn
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_ResourceTypesTable D-12 includes the available attribute information on this object type.
Table D-12 K2VW_ResourceType Attribute Information
DescriptionAttribute
Note: Refer to theVeritas Cluster Server Administrator’sGuide for a complete list of VCS attributes.
All VCS attributes on theresource type.
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Fully qualified object name.fqn
Table D-13 includes the data available in the K2VW_ResourceType table.
Table D-13 K2VW_ResourceType Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Name of the object.Varchar (256)ObjectName
The parent of a resource type object is aCluster object. This column contains theunique database ID for the parent of thisobject.
IntegerParentID
Date the object was created.TimestampDateCreated
469Creating custom reportsAbout published database schema objects
Table D-13 K2VW_ResourceType Table Information (continued)
DescriptionData TypeColumn
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_ResourcesTable D-14 includes the available attribute information on this object type.
Creating custom reportsAbout published database schema objects
470
Table D-14 K2VW_Resources Attribute Information
DescriptionAttribute
Note: Refer to the Veritas Cluster ServerAdministrator’s Guide for a complete list of VCSattributes.
All VCS attributes on the resourceexcept for the following: Signaled,MonitorTimeStats.
Map of user IDs to users right on this object.Explicit may be empty.
explicitUserAccessRight
Map of user IDs to users right on this object.Effective=explicit or is inherited from parentseffective.
effectiveUserAccessRight
Fully qualified object name.fqn
Don’t include resource in uptime calculations.ExcludeFromUptimeReport
IDs of children.ChildDependencies
IDs of parents.ParentDependencies
State of management server.ConsolidatedState
State of management server before last transition.PreviousConsolidatedState
ID of resource type for this resource.resourceType
Table D-15 includes the data available in the K2VW_Resource table.
Table D-15 K2VW_Resource Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Name of the object.Varchar (256)ObjectName
The parent of a resource object is a Groupobject. This column contains the uniquedatabase ID for the parent of this object.
IntegerParentID
Date the object was created.TimestampDateCreated
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
471Creating custom reportsAbout published database schema objects
Table D-15 K2VW_Resource Table Information (continued)
DescriptionData TypeColumn
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_SchedulesTable D-16 includes the available attribute information on this object type.
Table D-16 K2VW_Schedules Attribute Information
DescriptionAttribute
Map of user IDs to users right on this object. Explicit maybe empty.
explicitUserAccessRight
Map of user IDs to users right on this object.Effective=explicit or is inherited from parents effective.
effectiveUserAccessRight
Fully qualified object name.fqn
Creating custom reportsAbout published database schema objects
472
Table D-16 K2VW_Schedules Attribute Information (continued)
DescriptionAttribute
Description of the schedule objectDescription
The date on which the schedule object takes effectEffectiveDate
Starting time for the schedule objectStartTime
Repeat interval in days for the schedule objectRepeatInterval
Day of the week for the schedule object (Sunday = 1, ...,Saturday = 7)
DayOfWeek
Day of the month for the schedule object (1 - 31)DayOfMonth
Specific date for the schedule objectSpecificDate
Boolean flag which determines if the schedule periodicallyrepeats
IsPeriodic
Boolean flag which determines if the schedule is enabledIsEnabled
Event to fire.Event
Table D-17 includes the data available in the K2VW_Schedule table.
Table D-17 K2VW_Schedule Table Information
DescriptionData TypeColumn
Unique database ID that identifies eachobject of this type in the database.
IntegerObjectID
Unique database ID that identifies eachobject of this type in the database.
Varchar (256)ObjectUuid
Name of the object.Varchar (256)ObjectName
The parent of a schedule object is aCluster object. This column contains theunique database ID for the parent of thisobject.
IntegerParentID
Date the object was created.TimestampDateCreated
Date the object was deleted. If NULL, theobject is not deleted.
TimestampDateDeleted
Name of an attribute on the object.Varchar (256)AttributeName
473Creating custom reportsAbout published database schema objects
Table D-17 K2VW_Schedule Table Information (continued)
DescriptionData TypeColumn
Dimension of the attribute. Can be any ofthe following values: Scalar attribute,Association attribute, Key List attribute,or Vector attribute.
Varchar (50)AttributeDimension
Actual data type of the attribute values.Varchar (50)AttributeType
Specifies the scope of the attribute. Anattribute can be either locally scoped orglobally scoped.
Varchar (50)AttributeScope
Date the attribute was modified.TimestampAttributeDatemodified
Specifies if the attribute is a historicalrecord (‘OLD’) or if it is a current record(‘NEW’).
Varchar (3)AttributeState
The context for an attribute value.Depending on the attribute dimension, itmay contain a NULL value.
Varchar (512)AttributeContext
The key for an attribute value. Dependingon the attribute dimension, it may containa NULL value.
Varchar (512)Attributekey
The attribute values. Depending on theattribute dimension, it may contain aNULL value.
Varchar (512)AttributeValue
K2VW_LogsLogs do not have attribute information.
Table D-18 includes the data available in the K2VW_Logs table.
Table D-18 K2VW_Logs Table Information
DescriptionData TypeColumn
Object type for which the log was generated.Varchar (15)ObjectType
Unique database ID that identifies the object forwhich the log was generated.
IntegerObjectID
Date the log was generated.TimestampEntryDate
Creating custom reportsAbout published database schema objects
474
Table D-18 K2VW_Logs Table Information (continued)
DescriptionData TypeColumn
Name of the user whose action generated the log.Long VarcharUserName
Application-specific ID for the log message.Varchar (50)LogID
Source of the log/event for CommandCentralAvailability or VCS.
Varch (15)LogSource
The log message text.Long VarcharLogLevel
Arguments on the log messages text that arestored in .xml format.
Long VarcharLogArgs
Example statementsThe following section includes examples of Structured Query Language (SQL)statements to retrieve information using the published database schema objects.
Example 1To retrieve a list of currently managed clusters:
SELECT distinct a.ObjectName, a.ObjectUuid, a.DateCreated, b.ObjectName
‘Parent(Site)’
FROM K2VW_Clusters a
JOIN K2VW_MServers b ON a.ParentID = b.ObjectID
WHERE a.DateDeleted IS NULL
ORDER BY a.ObjectUuid
Example 2To retrieve a list of current cluster users on managed clusters:
SELECT distinct a.ObjectName, a.ObjectUuid, b.ObjectName ‘Parent(Site)’,a.attributeKey Users FROM K2VW_Clusters a
JOIN K2VW_MServers b ON a.ParentID = b.ObjectID
WHERE a.DateDeleted IS NULL
AND a.attributename = ‘UserNames’
AND a.attributeState = ‘NEW’
475Creating custom reportsExample statements
ORDER BY a.ObjectUuid
Example 3To retrieve basic uptime information on a specific managed cluster:
SELECT distinct a.ObjectName, a.ObjectUuid, b.ObjectName ‘Parent(Site)’,
(CASE a.attributeValue
WHEN ‘0’ then ‘STATE_CLUSTER_INIT’
WHEN ‘1’ then ‘STATE_CLUSTER_LOCAL_VCS_BUILD’
WHEN ‘2’ then ‘STATE_CLUSTER_MASTER_CONNECT’
WHEN ‘3’ then ‘STATE_CLUSTER_SLAVE_BUILD’
WHEN ‘4’ then ‘STATE_CLUSTER_RUNNING’
WHEN ‘5’ then ‘STATE_CLUSTER_EXITING’
WHEN ‘6’ then ‘STATE_CLUSTER_EXITED’
WHEN ‘7’ then ‘STATE_CLUSTER_FAULTED’
WHEN ‘8’ then ‘STATE_CLUSTER_DEAD’
ELSE ‘Unknown’
END) State, a.AttributedateModified timestamp
FROM K2VW_Clusters a
JOIN K2VW_MServers b ON a.ParentID = b.ObjectID
Creating custom reportsExample statements
476
Symantec ProductAuthentication Service rootbroker tasks
This appendix includes the following topics:
■ About the Symantec Product Authentication Service
■ Setting up an authentication broker on the management server
■ Setting up trust between two authentication brokers
About the Symantec Product Authentication ServiceSymantec Product Authentication Service (AT) securely authenticates useraccounts and secures communication between cluster nodes and client software,including the VCS Management Console. The Symantec Product AuthenticationService uses digital certificates for user account authentication and SSL to encryptcommunication over the public network.
The user accounts are local operating system and domain user accounts. The VCSManagement Console does not require native or proprietary user accounts.
The main components of the Symantec Product Authentication Service includethe root broker and authentication brokers.
Authentication service overviewThe Symantec Product Authentication Service is deployed as a hierarchy ofcomponents consisting of a root broker at the top level, one or more authenticationbrokers, and including multiple authentication entities.
EAppendix
The root broker implements the functionality that is associated with a registrationauthority. The registration authority is the entity that sends requests to the rootbroker to determine whether the authentication brokers are valid. Thetrustworthiness of authentication brokers is vouched with the valid authenticationentities (principals).
Authentication brokers implement the certificate authority functionality, whichfollows a security model similar to the public key infrastructure (PKI). Theauthentication brokers issue and sign the certificates that are used to prove theidentities of entities (such as computers, users, and services) that interact withSymantec products. The certification authority issues the product credentials tothe requesting authentication entities (principals) based on the registrationauthority's validity check.
As stated above, all communications between brokers and entities use the securesocket layer (SSL) protocol.
Root and Authentication brokersThe root broker is the first broker that is established. The root broker resides atthe top level of the authentication hierarchy. The root broker vouches for itselfwith a self-signed root certificate, and is the most trusted certification authority.The root broker implements a registration authority to validate authenticationbrokers, and has a private domain repository with the authentication principalsthat represent authentication brokers.
An authentication broker differs from a root broker in that is serves as both anintermediate registration authority and as a certification authority. As aregistration authority, it determines whether authentication principals are valid.As a certification authority, it issues product credentials to the requestingauthentication clients (such as users or services) based on the registrationauthority's validity check of a client's authentication principals.
The certificate of an authentication broker is signed by the root broker. Theauthentication broker authenticates only clients—it cannot authenticate otherauthentication brokers. The authentication broker resides one level below theroot broker in the authentication hierarchy.
Setting up an authentication broker on themanagement server
Symantec Product Authentication Service can be installed in three modes on amanagement server: root broker mode, authentication broker mode (AB), or both(R+AB).
Symantec Product Authentication Service root broker tasksSetting up an authentication broker on the management server
478
For information about setting up an authentication broker on the managementserver (authentication broker mode or AB):
See “Installing the authentication broker on the management server” on page 48.
For information about setting up a root broker, or an authentication broker androot broker on the management server (root-plus-authentication-broker mode orR+AB):
See “Installing the root broker” on page 43.
Setting up trust between two authentication brokersThe authentication brokers on a secure-mode cluster and on the local managementserver might use different root brokers. In this situation, the management servercannot log into the secure cluster. You must set up trust between theauthentication broker on the management server and the authentication brokerthat is installed on each cluster node.
To set up the trust relationship
1 Identify which two systems with authentication brokers are to participate inthe trust relationship.
Trust must be set up from each cluster node where the management serverwill connect to the management server's authentication broker (the otherdirection is automatic).
2 On one of the two systems, run the following command (the dashes precedingthe command options are double dashes):
vssat setuptrust --broker systemname:2821 --securitylevel medium
Where systemname is the DNS server name or the IP address of the second(other) system.
479Symantec Product Authentication Service root broker tasksSetting up trust between two authentication brokers
3 On the second (other) system, obtain a command prompt and enter thefollowing command:
vssat setuptrust --broker systemname:2821 --securitylevel medium
Where systemname is the DNS server name or the IP address of the firstsystem.
4 You will be prompted to verify the root hash of the broker when you aresetting up trust. Proceed to verify the root hash.
Note: Every authentication hierarchy has a 40-byte electronic signature thatis called a root hash that uniquely identifies the root broker. The root hashis stored in a binary file (root_hash), and an authentication command isavailable to display the hash value. Use the vssat showbrokerhash commandto display the hash value.
Symantec Product Authentication Service root broker tasksSetting up trust between two authentication brokers
480
CMCServerConfig agent
This appendix includes the following topics:
■ About the CMCServerConfig agent
■ Sample configuration for the CMCServerConfig agent
■ Resource dependency diagram
About the CMCServerConfig agentThe CMCServerConfig agent monitors a resource of type CMCServerConfig. TheCMCServerConfig resource is part of the CMC_MS service group. The CMC_MSservice group includes the management server resources when the managementserver is installed in a highly-available (clustered) configuration. TheCMCServerConfigType.cf file defines the attributes for the CMCServerConfigagent.
Table F-1 includes the two attributes that are defined in theCMCServerConfigType.cf file.
Table F-1 Attributes
DescriptionAttribute
The data location for the management server.
Type and dimension: string-scalar
Example: DataLoc = "N:\\\\data"
DataLoc
The debug setting for the agent (whether or not debugging is enabledfor the agent).
Type and dimension: boolean
Example: AgentDebug = 0
AgentDebug
FAppendix
The following example of the resource type definition is for both UNIX andWindows.
type CMCServerConfig (
static ArgList[] = { AgentDebug, DataLoc }
boolean AgentDebug = 0
str DataLoc
)
Sample configuration for theCMCServerConfig agentThis example is the main.cf file for both UNIX and Windows.
include "CMCServerConfigType.cf"
include "types.cf"
cluster winclus (
UserNames = {
"CMC_HAD@[email protected]" =
266582666526668,
"CMC@[email protected]" = password }
Administrators = { "CMC_HAD@[email protected]",
"CMC@[email protected]" }
SecureClus = 1
)
system WINVCS95 (
)
system WINVCS96 (
)
group CMC_MS (
SystemList = { WINVCS95 = 0, WINVCS96 = 1 }
Frozen = 1
AutoStartList = { WINVCS95, WINVCS96 }
)
CMCServerConfig CMC_Config (
DataLoc = "N:\\\\data"
)
GenericService CMCWebApp (
ServiceName = CMCweb
RestartLimit = 3
OnlineWaitLimit = 5
OnlineRetryLimit = 3
)
IP CMC_IP (
CMCServerConfig agentSample configuration for the CMCServerConfig agent
482
Address = "10.198.91.196"
SubNetMask = "255.255.248.0"
MACAddress @WINVCS95 = "00-18-8B-75-A8-37"
MACAddress @WINVCS96 = "00-18-8B-75-C4-3C"
)
MountV CMC_Mount (
MountPath = "N:"
VolumeName = cmc_vol
VMDGResName = CMC_DG
)
NIC CMC_Nic (
MACAddress @WINVCS95 = "00-18-8B-75-A8-37"
MACAddress @WINVCS96 = "00-18-8B-75-C4-3C"
)
Process CMC_DB (
StartProgram = "\"C:\\Program Files\\Symantec\\VRTScmcm
\\bin\\vxcmcweb.bat\" start_db "
StopProgram = "\"C:\\Program Files\\Symantec\\VRTScmcm
\\bin\\vxcmcweb.bat\" stop_db "
CleanProgram = "\"C:\\Program Files\\Symantec\\VRTScmcm
\\bin\\vxcmcweb.bat\" stop_db_force "
MonitorProgram = "\"C:\\Program Files\\Symantec\\VRTScmcm
\\bin\\vxcmcweb.bat\" monitor_db "
RestartLimit = 3
OnlineWaitLimit = 5
OnlineRetryLimit = 3
)
VMDg CMC_DG (
DiskGroupName = cmc_dg
)
CMC_IP requires CMC_Nic
CMC_Mount requires CMC_DG
CMC_Config requires CMC_Mount
CMC_DB requires CMC_Config
CMCWebApp requires CMC_IP
CMCWebApp requires CMC_DB
Resource dependency diagramThe following diagram shows the dependencies in the CMC_MS service group.
483CMCServerConfig agentResource dependency diagram
CMCServerConfig agentResource dependency diagram
484
Troubleshooting
This appendix includes the following topics:
■ Installation issues and recommendations
■ Configuration issues and recommendations
■ Operational issues and recommendations
■ User issues and recommendations
■ Console display issues and recommendations
■ Resolving localization issues
■ Log file locations
Installation issues and recommendationsThis topic contains known installation issues. Use this section to supplement theinstallation information in this guide.
Avoid concurrent installationsUnder no circumstances should you attempt to install the VCS ManagementConsole while other installation programs for any other products are running.Such attempts can result in an installation that appears to be successful, but isnot.
VCS 4.3 upgradeIf you install VCS 4.3 on Windows platforms, the VCS Management Consolerequires that you upgrade Symantec Product Authentication Service (formerlyVSS). If you subsequently perform an uninstallation of VCS, you receive the
GAppendix
message that the uninstall operation can only be performed on installed products.The uninstallation program is looking for an old version of VSS. This messagecan be ignored.
Installation user account privileges issue for WindowsDuring management server setup, the installer assigns the privilege ofmanagement server administrator to the user account that you specify as theinitial user. Symantec recommends that you specify Administrator on Windowssystems. If you specify a domain-level user as the initial user, Administrator isnot automatically designated as management server administrator. If you wantAdministrator to be a management server administrator, you must explicitlyassign that privilege to Administrator in the VCS Management Console.
Exception message during management server upgradeDuring a management server upgrade, you might see the following error afteryou click Finish:
Exception upgrading database : [Error executing script C:\\Program
Files\\Symantec\\VRTScmcm\\data\db\db_upgrade.bat]
Ignore the error and click Finish again. You receive the following message:
Applying Configuration - Please Wait
After a while, you should receive the following message:
Configuration Successful
You can now restart the management server and log in.
Specifying host names with installcmc causes failureSpecifying a host name after the installcmc command causes the installation tofail. Do not specify any IP address or host name on the command line with theinstallcmc command. Do not specify any address or any system name informationuntil the installation program prompts you for it.
Symantec Product Authentication Service post-upgrade versionsUpgrading the management server also upgrades the version of the SymantecProduct Authentication service. The following table shows the original and theupgraded versions.
TroubleshootingInstallation issues and recommendations
486
Table G-1 Symantec Product Authentication Service post-upgrade versions
Post-upgrade SymantecProduct AuthenticationService version
Post-upgrademanagementserver version
Symantec ProductAuthentication Serviceversion
Managementserver version
4.4.12.05.14.3.23.0UxRT 5.0
4.4.12.05.14.3.23.0UxRT 5.0MP1
4.4.12.05.14.3.28.4WxRT 5.0
4.4.12.05.14.3.28.4WxRT 5.0MP1
4.3.28.4Freshly installed 5.1
Configuration issues and recommendationsThis topic contains known issues about console and cluster configuration.
Cluster configuration state after cluster user additionIf you are a management server administrator and add yourself as a cluster user,the cluster configuration is left in a read-write state. To return the configurationto a read-only state, use the Save Configuration task in the cluster details summarypage and specify the read-only option.
DNS configurationYour network and DNS configuration must provide proper name resolution. Ifnot, the management server is not able to resolve cluster host names when itattempts to connect to the clusters.
Improperly configured network and name resolution services can create similarissues in the Cluster Management Console and other Storage Foundation andHigh Availability Solutions 5.0 products.
Configuring a clustered management server on Firefox 2.0If you use the Firefox 2.0 browser to configure a clustered management server,you receive an erroneous security warning. This warning appears after you selectthe Clustered MS option and click Next. The warning’s Close button also does notwork. You may ignore this warning and close it by clicking the red X in the warningbox.
487TroubleshootingConfiguration issues and recommendations
Operational issues and recommendationsThis topic contains known issues about command operation.
VCS Management Console controls not immediately activeIn some versions of Internet Explorer, GUI controls (icons, drop-down lists, radioicons, and so on) may require that you click them once to make them active. Thissymptom occurs in flash screens, pop-up windows, and wizards. Controls thatrequire this activating click show the following message when you roll over themwith your mouse pointer:
Press SpaceBar or Click to activate this Control
Cluster status is offline during snapshotDuring cluster synchronization, the VCS Management Console receives updatesof cluster data called snapshots. It uses these snapshots to refresh the manycluster administration views. The management server initiates the snapshot.
If a cluster initializes or comes up during a snapshot, the management servercannot connect to it. Consequently, the VCS Management Console shows thecluster in an OFFLINE state.
Very large clusters may not load into the consoleTo accommodate very large clusters, increase the value of theloadClusterQueryTimeout property in the management server configuration file.The management server generates this file upon startup.
The ManagementServer.conf file is located in the following paths:
■ For Solaris/opt/VRTScmcm/data/conf
■ For WindowsC:\Program Files\Symantec\VRTScmcm\data\conf
The default paths might have changed during configuration.
Note: The output of the vxcmcweb script is currently English-only.
TroubleshootingOperational issues and recommendations
488
To increase the value of the loadClusterQueryTimeout property
1 Stop the VCS Management Console.
On Solaris platforms, enter the following command:
/opt/VRTScmcm/bin/vxcmcweb stop
On Windows platforms, click Start > Programs > Administrative Tools >Services and use the Windows Services manager to stop the Veritas VCSManagement Console service.
2 Add the following line to the file ManagementServer.conf:
loadClusterQueryTimeout=60000
Adjust the value as needed to allow complete initial load of your clusterinformation.
3 Start the VCS Management Console.
On UNIX platforms, enter the following command:
/opt/VRTScmcm/bin/vxcmcweb start
On Windows platforms, click Start > Programs > Administrative Tools >Services and use the Windows Services manager to start the Veritas VCSManagement Console service.
Reports stop running on very large configurationsTo accommodate reporting on very large configurations, increase the value of thereport.worker.maxheap property. This property is in the management serverconfiguration file, ManagementServer.conf. The management server generatesthis file upon startup.
The ManagementServer.conf file is located in the following paths:
■ For Solaris/opt/VRTScmcm/data/conf
■ For WindowsC:\Program Files\Symantec\VRTScmcm\data\conf
The default paths might have changed during configuration.
Note: The output of the vxcmcweb script is currently English-only.
489TroubleshootingOperational issues and recommendations
To increase the value of the report.worker.maxheap property
1 Stop the VCS Management Console.
On Solaris platforms, enter the following command:
/opt/VRTScmcm/bin/vxcmcweb stop
On Windows platforms, click Start > Programs > Administrative Tools >Services and use the Windows Services manager to stop the Veritas VCSManagement Console service.
2 Add the following line to the file ManagementServer.conf:
report.worker.maxheap = 1024
3 Start the VCS Management Console.
On Solaris platforms, enter the following command:
/opt/VRTScmcm/bin/vxcmcweb start
On Windows platforms, click Start > Programs > Administrative Tools >Services and use the Windows Services manager to start the Veritas VCSManagement Console service.
Discovering clusters allows one authentication domainIf you attempt to discover and add secure-mode clusters over an IP range, theconsole might discover several clusters in different domains. However, the consolestill lets you specify only one domain for authentication and subsequent addition.To add clusters in multiple domains over a given IP range, you must run the wizardfor each domain.
Currently, for a given set of credentials (user name, password, and domain) youcan add an entire set of clusters in a single pass. This is the case if all the clustershave the same user.
User issues and recommendationsThis topic contains known user authentication and configuration issues.
NIS user group authentication issueIn some circumstances, the authentication service may not authenticate NIS usergroups as expected. If you require a fix for this issue, please request a patch forthe Symantec Product Authentication Service.
TroubleshootingUser issues and recommendations
490
OS user password requirementThe VCS Management Console does not support blank passwords.
OS group reporting privileges issueIf you add reporting privileges to an existing user group that has guest privilegeson the management server, the action has no effect. If users in that group log onto the console, they do not have reporting privileges.
To implement the workaround
1 Delete the OS user group from the management server.
It is not necessary to delete the group from any clusters.
2 Add the OS user group back to the management server with the requiredprivileges.
VCSMC administrator user limitationA VCSMC administrator (OS user with administrator privilege) can delete anyother cluster user. However, if a VCSMC administrator adds himself as a clusteradministrator on a cluster, then the administrator cannot remove himself as auser of the cluster.
Console display issues and recommendationsThis topic contains known display issues.
Navigation tree context menu issueIf you right-click objects in the navigation tree, a context menu appears withcommonly-used operations for that object.
The Online operation and the Clear Fault operation may be available on the contextmenu for a service group that has no resources. However, if you use thesecommands in this situation, the console generates an error message, and the groupremains in its original state.
Attributes added in VCS CLI may not display as expectedThe following VCS CLI command adds a static attribute to a resource type:
haattr -add -static resourcetype attr [valuetype]
491TroubleshootingConsole display issues and recommendations
Static attributes that are added with this command appear only when you viewall attributes for a resource type. These attributes do not appear when you viewall attributes for a resource.
Table blank but filter panels report service groupsGroups Listing tables, which list service groups for the enterprise, sites, andclusters, might appear blank if the clusters are in the SYNCHRONIZING state.This is the state in which the console receives updates through snapshots. If thesnapshot is not yet over, it is possible that the console has the state-wise totalsfor the filter panel, but not enough information to populate the table.
Random characters displayed on https loginRandom characters may initially display in some browsers when you log on usingthe URL https://IPaddress:14443. This is a temporary, anomalous result that isnot related to the console.
VCS version numbers indicate engine versionThe console has access to only to the EngineVersion attribute of VCS. This is theversion number that displays in the console status tables.
However, different VCS releases can have the same engine version. Therefore, itcan be difficult to determine the exact product version on a given platform fromthe engine version.
This issue does not affect the management server version number that is displayedin the management server installation history table.
Very large dependency trees may not display quicklyService group and resource dependency trees with very large numbers of objectsmay take a long time to display. If the tree is large enough, the time that is requiredto draw it may infringe upon the next snapshot and synchronization interval. Inthis case, the console might not be able to display the tree.
Resolving localization issuesThis topic contains the information that can help to address the common languageissues that may arise in the GUI. Issues may arise in the login page or in themanagement pages of the console.
TroubleshootingResolving localization issues
492
Viewing VCS 5.0 logs in JapaneseTo view VCS 5.0 logs in Japanese in the VCS Management Console, ensure thatyou install a Japanese language pack on the managed clusters. If you do not, theVCS 5.0 logs appear in English, even if you specify Japanese in the Select Languagemenu during logon.
Note: To make Japanese available in the Select Language menu, you must installthe VCS Management Console Japanese language pack on the management serverhost.
Installing the Japanese language pack on Windows has no effectIf you install the language pack on a Windows management server host, you mustrestart the management server for the language pack to take effect.
To restart the management server
1 Click Start > Programs > Administrative Tools > Services.
2 In the Services manager, in the list of services, click Veritas ClusterManagement Console.
You may have to scroll through the list to locate this service.
3 Click Action > Restart.
This action stops and then starts the Veritas VCS Management Console serviceand the dependent Symantec Web Server service. Allow the services a fewmoments to restart. Otherwise, if you try to use the console too soon afterrestarting, you may receive the following message:
The connection was refused when attempting to contact
system:14443
where system is the name of the management server host.
Maintaining reliable access to the databaseThe management server may have find it difficult to connect to the database
This issue may occur under the following conditions:
■ You install the VCS Management Console on a Windows system
■ The language for non-Unicode programs on that system is set to a languageother than the native language of the system.
493TroubleshootingResolving localization issues
To correct the configuration, you must reset the language to match the nativelanguage of the operating system and then reinstall the VCS Management Console.
To restore reliable access to the database
1 Open the Windows Control Panel and double-click Regional and LanguageOptions. In the Language for non-Unicode programs section, click theAdvanced tab and then select a language other than English (United States).
2 Reinstall the VCS Management Console.
Localizing the web serverTo localize the base web server, you must separately install the VRTSweb Japaneselanguage pack after you install the VCS Management Console Japanese languagepack.
Log file locationsReviewing log files can often help you to resolve issues.
The following are the management server log files:
■ UNIX
/var/VRTScmcm/log
■ Windows
CMC_HOME\log
Replace CMC_HOME with the path where CMC is installed.
The following are the installation log files:
■ UNIX
/opt/VRTS/install/logs/NAME_OF_SCRIPT UNIQUE_HASH
Replace NAME_OF_SCRIPT with an appropriate script file name, such asinstallcmc, uninstallcmc, installer, installvcs, or uninstallvcs.
Replace UNIQUE_HASH with the hash of the root broker that is used by themanagement server.
■ Windows
C:\Documents and Settings\All Users\Application
Data\Veritas\VPI\log
TroubleshootingLog file locations
494
Administering SymantecWeb Server
This appendix includes the following topics:
■ About Symantec Web Server
■ Configuring ports for VRTSweb
■ Managing VRTSweb SSL certificates
■ Configuring SMTP notification for VRTSweb
■ Modifying the maximum heap size for VRTSweb
About Symantec Web ServerThe VCS Management Console runs in its own web server called VRTSweb.
The following are the installation paths for VRTSweb.
■ For UNIX:/opt/VRTScmcm/VRTSweb
■ For Windows:C:\Program Files\Symantec\VRTScmcm\VRTSweb
This appendix describes how to administer VRTSweb and provides instructionsfor common configuration tasks.
You administer the VRTSweb from the command line;
Run commands from the following paths.
■ For UNIX:/opt/VRTScmcm/VRTSweb/bin/
HAppendix
■ For Windows:C:\Program Files\Symantec\VRTScmcm\VRTSweb\bin\
Configuring ports for VRTSwebYou can view, add, edit, or remove ports for VRTSweb.
About VRTSweb portsVRTSweb serves HTML content on a secure SSL HTTPS port.
The following is the default port:
■ 14443 (HTTPS) – Secure SSL port. VRTSweb presents a self-signed SSLcertificate (issued by Symantec) to the browser. You must accept the certificatebefore accessing the secure Web console. The SSL protocol prevents malicioususers from sniffing Web console data from the network.
In addition to the SSL port, there is a port for internal use:
■ 14444 – Administrative port.
If you use these ports for another application on the system, configure VRTSwebto use different ports.
Retrieving the list of VRTSweb portsYou can retrieve the list of ports that are configured for VRTSweb.
To retrieve the list
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui listports
The output displays the list of configured ports and their protocols. It doesnot include the administrative port 14444.
Adding ports for VRTSwebYou can add ports for use by VRTSweb.
To add a port
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui addport portno protocol bind_ip_address
Administering Symantec Web ServerConfiguring ports for VRTSweb
496
The following are the variable definitions:
■ portno – The port number to be added.
■ protocol – The protocol for the port. HTTP specifies a normal HTTP port,HTTPS specifies a secure SSL port.Web servers using the HTTP port can be accessed athttp://hostname:portno/.Web servers using the HTTPS port can be accessed athttps://hostname:portno/.
■ bind_ip_address – Optional variable. Specifies that the new port be boundto a particular IP address instead of each IP address on the system. Usethis option to restrict Web server access to specific administrativesubnets.The IP address must be available on the system before the Webserver starts.
The following is a command example for adding a port:
webgui addport 443 HTTPS 101.1.1.2
Deleting portsYou can delete unused ports from VRTSweb.
To delete a port
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui delport <portno> [bind_ip_address]
The variable portno represents the port number to be deleted. If the port wasbound to a particular IP address, use the bind_ip_address option.
You must ensure that at least one port remains configured for the Web server.
The following are command examples of deleting a port:
webgui delport 443 101.1.1.2
webgui delport 80
Changing the administrative portYou can change the administrative port for VRTSweb.
497Administering Symantec Web ServerConfiguring ports for VRTSweb
To change the administrative port
1 If the management server is clustered, freeze the CMC_MS service group.
2 Stop the Web server.
On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui stop force
3 Set the administrative port to a new value:
webgui adminport new_port_no
4 Restart the Web server:
webgui restart
5 If the management server is clustered, unfreeze the CMC_MS service group.
Managing VRTSweb SSL certificatesVRTSweb presents a self-signed SSL certificate (issued by Symantec) whenVRTSweb serves content over the secure port. You can view, customize, and exportthese certificates.
Note: Commands that modify the certificate requires that you restart VRTSweb.
Viewing SSL certificate informationYou can display information about the configured SSL certificate.
To view information about the SSL certificate
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui cert display
Creating a self-signed SSL certificateYou can create a customized self-signed SSL certificate for VRTSweb.
Administering Symantec Web ServerManaging VRTSweb SSL certificates
498
To create a self-signed SSL certificate
1 On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui cert create
2 Follow the prompts to create a new certificate.
3 Restart the server for the new certificate to take effect:
webgui restart
Exporting the SSL certificate to a fileYou can export the public key that is associated with an SSL certificate to a file.You can then import the key to other applications to establish trust with theVRTSweb instance.
To export the SSL certificate to a file
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui cert export cert_file [rfc]
If the VRTSweb SSL certificate does not exist, the command prompts you tocreate one. If you specify the RFC option, the key output is encoded in aprintable format. This is defined by the Internet RFC 1421 standard.
For a UNIX command example:
webgui cert export /myapp/vrtsweb.cer rfc
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui cert export C:\myapp\vrtsweb.cer rfc
Configuring a CA-signed SSL certificateBy default, VRTSweb presents a self-signed SSL certificate every time you accessVRTSweb over the SSL port. You can install a certificate that is signed by aCertificate Authority (CA) like Verisign.com or Thawte.com.
499Administering Symantec Web ServerManaging VRTSweb SSL certificates
To configure a CA-signed SSL certificate
1 If you do not have a self-signed certificate with the information that the CAcan verify, create a certificate. Issue the following command:
webgui cert create
See “Creating a self-signed SSL certificate” on page 498.
2 Generate a Certificate Signing Request (CSR) for the certificate. On the systemwhere VRTSweb is installed, run the following command from the VRTSwebinstall directory:
webgui cert certreq certreq_file
The variable certreq_file specifies the file to which the CSR is written. Thefile is written using the Public-Key Cryptography Standard PKCS#10.
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui cert certreq /myapp/vrtsweb.csr
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui cert certreq c:\myapp\vrtsweb.cs
3 Submit the CSR to a certification authority, who issues a CA-signed certificate.
Administering Symantec Web ServerManaging VRTSweb SSL certificates
500
4 Import the CA-issued certificate to VRTSweb. On the system where VRTSwebis installed, run the following command from the VRTSweb install directory:
webgui import ca_cert_file
The variable cert_file represents the certificate that is issued by thecertification authority.
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui cert import /myapp/vrtsweb.cer
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui cert import c:\myapp\vrtsweb.cer
Note that the import command fails if the CA root certificate is not a part ofthe trust store that is associated with VRTSweb. If the command fails, addthe CA root certificate to the VRTSweb trust store:
webgui cert trust ca_root_cert_file
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui cert trust /myapp/caroot.cer
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui cert trust c:\myapp\caroot.cer
Once the certificate that is used to sign the CSR is added to VRTSweb truststore, you can import the CA-assigned certificate into VRTSweb.
5 Restart VRTSweb:
webgui restart
Cloning the VRTSweb SSL certificateYou can clone the VRTSweb SSL key pair into a keystore and use the clonedVRTSweb certificate for another application or Web server.
Visit the following URL for more information about keystores:
http://java.sun.com
501Administering Symantec Web ServerManaging VRTSweb SSL certificates
To clone the VRTSweb SSL certificate
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui cert clone keystore storepass alias keypass
If a clone keystore exists, the command renames it to keystore.old. If theVRTSweb SSL certificate does not exist, the command prompts you to createone.
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui webgui cert clone
/myapp/myserv.keystore mystorepass myalias mykeypass
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui cert clone c:\myapp\myserv.keystore
mystorepass myalias mykeypass
Configuring SMTP notification for VRTSwebYou can configure VRTSweb to send out email notifications about the events thatare associated with the Web server.
The following are examples of Web server events:
■ The Web server is starting/stopping [severity: INFORMATION]
■ The Web console is starting/stopping [severity: INFORMATION]
■ The Web server's allocated heap size very close to the maximum allowed[severity: SEVERE]
To send an email notification, VRTSweb needs to know the IP address or hostnameof a configured SMTP server. The SMTP server address applies to all Web consolesrunning on the Web server. You do not need to configure the SMTP server atmultiple places.
Retrieving the name of the configured SMTP serverYou can retrieve the name of the SMTP server that is configured for VRTSweb.
Administering Symantec Web ServerConfiguring SMTP notification for VRTSweb
502
To retrieve the name of the SMTP server
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui smtp getserver
The command displays the SMTP server address or hostname, if it isconfigured.
Setting the SMTP serverYou can configure an SMTP server for VRTSweb.
To set the SMTP server
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui smtp setserver server_ip/hostname
webgui smtp delserver
Thesetserver command sets the SMTP server to the specified hostname/IPaddress. The delserver command deletes the SMTP server setting anddisables SMTP notification.
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui smtp setserver
smtphost.company.com
/opt/VRTScmcm/VRTSweb/bin/webgui smtp setserver 101.1.2.3
/opt/VRTScmcm/VRTSweb/bin/webgui smtp delserver
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui smtp setserver smtphost.company.com
%VRTSWEB_HOME%\bin> webgui smtp setserver 101.1.2.3
%VRTSWEB_HOME%\bin> webgui smtp delserver
Retrieving SMTP settingsYou can retrieve configuration information for VRTSweb SMTP notification.
503Administering Symantec Web ServerConfiguring SMTP notification for VRTSweb
To retrieve SMTP recipients
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui smtp listrcpt
This command retrieves the email addresses of the configured recipients,the notification severity level, and the notification locale.
Adding an SMTP recipientYou can add a user to receive SMTP notifications from VRTSweb.
To add an SMTP recipient
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui smtp addrcpt email\
[severity=<INFO|WARN|ERROR|SEVERE>] \
[locale=<en|any_other_installed_locale>]
The following are the variable definitions:
■ The variable email represents the email address of the new recipient.
■ The optional attribute severity represents the threshold for receiving Webserver events. It can assume one of the following values:INFO|WARN|ERROR|SEVERE. If no value is specified for this attribute, ittakes the default ERROR level.
■ The optional attribute locale specifies the locale in which the notificationis to be sent. If no value is specified for this attribute, it takes the defaultlocale of the system.
For a UNIX command example:
/opt/VRTScmcm/VRTSweb/bin/webgui smtp addrcpt
[email protected] severity=INFO locale=ja_JP
/opt/VRTScmcm/VRTSweb/bin/webgui smtp addrcpt
[email protected] severity=ERROR
/opt/VRTScmcm/VRTSweb/bin/webgui smtp addrcpt
For a Windows command example:
%VRTSWEB_HOME%\bin> webgui smtp addrcpt [email protected]
severity=INFO locale=ja_JP
Administering Symantec Web ServerConfiguring SMTP notification for VRTSweb
504
%VRTSWEB_HOME%\bin> webgui smtp addrcpt [email protected]
severity=ERROR
%VRTSWEB_HOME%\bin> webgui smtp addrcpt [email protected]
Deleting an SMTP recipientYou can delete an SMTP recipient to prevent VRTSweb from sending notificationsto the recipient.
To delete an SMTP recipient
◆ On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui smtp delrcpt email
The variable email represents the email address of the recipient to be deleted.
For a command example:
webgui smtp delrcpt [email protected]
Modifying the maximum heap size for VRTSwebThe default maximum allowed heap size for the VRTSWeb Java Virtual Machine(JVM) is 1500MB on Solaris and 1600MB on Windows. You may need to modifythis limit for large configurations or for when a large number of consoles sharethe same VRTSweb instance.
You can modify the maximum heap size only from the command line.
505Administering Symantec Web ServerModifying the maximum heap size for VRTSweb
To modify the maximum heap size
1 On the system where VRTSweb is installed, run the following command fromthe bin subdirectory in the VRTSweb install directory:
webgui maxheap new_size_in_MB
For example:
webgui maxheap 1800
2 Restart the Web server after specifying a new limit using the followingcommand:
webgui restart
3 View the current limit using the following command:
webgui maxheap
Administering Symantec Web ServerModifying the maximum heap size for VRTSweb
506
Aaccess
multiple pages of data tables 156accessibility
Cluster Management Console 409dialog windows 410tools 410
addusers 168
Agent Inventory report 367Agent Usage report 367agents
tracking with reports 367alerts
critical 149errors 149information 149viewing 149warning 149
attributesmodifying 239modifying Cluster Management Console 180modifying groups 202
Bback up
database to a file 396
Cclear
maintenance windows from groups 406clone
report job 360cluster
deleting 182removing 182
Cluster Activity report 373Cluster Attribute report 369Cluster Inventory report 368
Cluster Management Consoleadministering resources 251administering service groups 212definition 19icon conventions 156logging out 138managing cluster configuration 185, 211, 251modifying attributes 180, 239tracking agents with reports 367
clustersconfiguring 178viewing 178
commandsgaclus 425gaconf 428gadb 429gadbrestore 432gagetcf 433gagrp 434galogin 422galogout 424gares 441gaserver 445gasys 449gatype 452gauser 455notations for object names 417
configurationclosing from Cluster Management Console 186opening from Cluster Management Console 185saving from Cluster Management Console 186
Configuration Analysis report 368configure
clusters 178connect
to VCS Management Console 136console
accessibility 409VCS Management Console 136
consolidated states 22conventions
Cluster Management Console icons 156
Index
createmaintenance windows 403notification policy 382report job 350
criticalalerts 149
Current Schedules report 372
Ddata
tables 156database
backing up to a file 396modifying guest access 400pruning 394restoring 397
deleteclusters 182maintenance windows 403policy 385report job 357
dependenciesbetween resources 229
detailspolicy 382
dialog windowsaccessibility 410
disablepolicy 385report job 358
Eenable
policy 385report job 358
errorsalerts 149
exportpolicy 386
FFailure Summary by Group report 371Failure Summary report 370Fault Trending report 371files
backing up database 396filter
report jobs 361, 365
freezegroups 204–205systems 240, 242
Ggaclus
command 425gaconf
command 428gadb
command 429gadbrestore
command 432gagetcf
command 433gagrp
command 434galogin
command 422galogout
command 424gares
command 441gaserver
command 445gasys
command 449gatype
command 452gauser
command 455global clusters
adding from the VCS Management Console 283deleting from VCS Management Console 293
global heartbeatsadministering from Cluster Management
Console 297deleting from VCS Management Console 299
global service groupsadministering from Cluster Management
Console 285grant
report permissions 166, 361Group Activity report 373Group Attribute report 370groups
clearing maintenance windows 406freezing 204–205modifying attributes 202
Index508
groups (continued)unfreezing 204–205
guestsmodifying access to database 400
Hheap size for VRTSweb 505Heartbeats report 374
Iicons
Cluster Management Console conventions 156import
policy 387information
alerts 149initial user 121installing
management server 60management server, Solaris 61
Jjobs
cloning report 360creating report 350deleting report 357disabling report 358enabling report 358filtering report 361, 365reports 349running report 357
Llists
viewing policies 381viewing report jobs 350
logout 138
logsviewing 274
Mmaintenance windows
clearing from groups 406creating 403deleting 403
Management Consoleinstalling 60
management servertrust between 479uninstalling 107upgrading on Solaris 73
migrateservice group on VMware 218
modifyattributes 180, 239group attributes 202guest access to database 400tags 203
Nname
qualified 418unqualified 418user 136
notification policycreating 382
Oobject names
command notations 417object states 22outputs
options summary 418reports 361
Ppanels
viewing alerts 149password 136peers 479permissions
granting report 166, 361policies
deleting 385disabling 385enabling 385exporting 386importing 387list 381viewing details 382
prunedatabase 394
509Index
Qqualified
name 418
Rrecovery
site 301remove
clusters 182report permissions 166, 361
reportsAgent Inventory 367Agent Usage 367cloning jobs 360Cluster Activity 373Cluster Attribute 369Cluster Inventory 368Configuration Analysis 368creating jobs 350Current Schedules 372deleting jobs 357disabling jobs 358enabling jobs 358failovers 374Failure Summary 370Failure Summary by Group 371Fault Trending 371filtering jobs 361, 365granting permissions 166, 361Group Activity 373Group Attribute 370heartbeats 374job list 350jobs 349outputs 361Resource Activity 373Resource Attribute 370revoking permissions 166, 361running jobs 357tracking VCS agents 367types 366understanding jobs 349understanding outputs 361Uptime Analysis 371Virtual IP Usage 370
Resource Activity report 373Resource Attribute report 370resource dependencies
creating from Cluster Management Console 225
resource dependencies (continued)removing from Cluster Management
Console 228resources
administering from Cluster ManagementConsole 251
bringing online from Cluster ManagementConsole 258
clearing faults from Cluster ManagementConsole 263
probing from Cluster Management Console 264unlinking 229unlinking from Cluster Management
Console 228restore
database 397run
report job 357
Ssearch 389
conducting 275, 389definition 389
searches 389server
logging out of the Cluster ManagementConsole 138
service groupmigrate on VMware 218
service groupsadding from Cluster Management Console 213administering from Cluster Management
Console 212bringing online from Cluster Management
Console 215clearing from Cluster Management Console 207,
232disabling from Cluster Management Console 221enabling from Cluster Management Console 222enabling from VCS Management Console 222flushing from Java Console 235
siterecovery 301
SMTP notificationconfiguring for VRTSweb 502
SMTP serverretrieving name of 502
sortingdata tables 155
Index510
statesconsolidated 22object 22
Successful Failovers report 374summary
output options 418systems
freezing 240, 242freezing from VCS Management Console 243unfreezing 240, 242unfreezing from VCS Management Console 244
Ttables
accessing multiple pages 156sorting data 155
tagsmodifying 203
toolsaccessibility 410
trackVCS agents with reports 367
trust relationship 479
Uunfreeze
groups 204–205systems 240, 242
uninstallingmanagement server 107
unqualifiedname 418
updatescontrolling view 157
upgradingmanagement server
Solaris 73Uptime Analysis report 371user
adding 168name 136
VVCS Management Console
connecting to 136Veritas Cluster Management Console
modifying attributes 180, 239
viewalerts 149clusters 178logs 274policy details 382policy list 381report jobs list 350
viewscontrolling updates 157
Virtual IP Usage report 370VRTSweb
adding ports 496adding SMTP recipients 504deleting ports 497deleting SMTP recipients 505notification for 502ports for 496retrieving ports 496setting heap size 505setting SMTP server 503
Wwarn
alerts 149
511Index
