+ All Categories
Home > Documents > VERITAS Cluster Server 3.5 Bundled Agents - SORT Home · PDF fileVolume Agent ... Cluster...

VERITAS Cluster Server 3.5 Bundled Agents - SORT Home · PDF fileVolume Agent ... Cluster...

Date post: 11-Mar-2018
Category:
Upload: vuanh
View: 229 times
Download: 1 times
Share this document with a friend
64
October 2002 N09207G VERITAS Cluster Server 3.5 Bundled Agents Reference Guide HP-UX
Transcript

VERITAS Cluster Server™ 3.5Bundled Agents

Reference Guide

HP-UX

October 2002N09207G

Disclaimer

The information contained in this publication is subject to change without notice.VERITAS Software Corporation makes no warranty of any kind with regard to thismanual, including, but not limited to, the implied warranties of merchantability andfitness for a particular purpose. VERITAS Software Corporation shall not be liable forerrors contained herein or for incidental or consequential damages in connection with thefurnishing, performance, or use of this manual.

Copyright

Copyright © 1998-2002 VERITAS Software Corporation. All Rights Reserved. VERITAS,VERITAS SOFTWARE, the VERITAS logo and all other VERITAS product names andslogans are trademarks or registered trademarks of VERITAS Software Corporation in theUSA and/or other countries. Other product names and/or slogans mentioned herein maybe trademarks or registered trademarks of their respective companies.

VERITAS Software Corporation350 Ellis StreetMountain View, CA 94043Phone 650–527–8000Fax 650–527-2908www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

VCS Enterprise and Storage Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Resources and Their Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Modifying Agents and Their Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Categories of Bundled Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Basic Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Application Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

VCS Infrastructure and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. VCS Bundled Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Application Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Sample 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Sample 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

DiskGroup Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Setting the noautoimport Flag for a Disk Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

iii

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

ElifNone Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

FileNone Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

FileOnOff Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

FileOnOnly Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

IP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sample 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sample 2: NetMask in decimal (base 10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sample 3: NetMask in hexadecimal (base 16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

IPMultiNIC Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Sample Configuration, IPMultiNIC and MultiNICA . . . . . . . . . . . . . . . . . . . . . . . . . 20

LVMCombo Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

LVMLogicalVolume Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

LVMVolumeGroup Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

iv VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Mount Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

MultiNICA Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Notes about Using MultiNICA Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Sample Configuration: MultiNICA and IPMultiNIC . . . . . . . . . . . . . . . . . . . . . . . . . 31

NFS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

NIC Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Requirements for NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

NotifierMngr Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Phantom Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Sample 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Sample 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Process Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Sample 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Sample 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Proxy Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Contents v

Sample 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Sample 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Sample 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

ServiceGroupHB Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Share Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Volume Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

VRTSWebApp Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

vi VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Preface

This document provides reference for the VCS agents bundled with the VCS software.

For information on purchasing VCS agents or other VERITAS products, contact yourVERITAS sales representative:

U.S. and Canadian Customers: 1-800-327-2232

International Customers: +1 (407) 531-7501 or consult the Web (http://www.veritas.com)for the VERITAS sales office in your area.

Email: [email protected]

VCS Enterprise and Storage AgentsVCS enterprise and storage agents are not included with the VCS software, but are soldseparately. Contact your VERITAS sales representative for details on these agents oradditional agents under development:

� Informix

� NetBackup

� Oracle

� Sybase

vii

Technical Support

Technical SupportU.S. and Canada: call 1-800-342-0652.

Europe, the Middle East, or Asia: visit the Technical Support Web site athttp://support.veritas.com for a list of each country’s contact information.

Software updates, TechNotes, product alerts, and hardware compatibility lists are alsoavailable from http://support.veritas.com.

To learn more about VERITAS and what we offer, visit http://www.veritas.com.

Conventions

Typeface/Font Usage

courier Computer output, command references in text

courier (bold) User input and commands, keywords in grammar syntax

italic New terms, book titles, emphasis

italic Variables

Symbol Usage

# UNIX superuser prompt (for all shells)

viii VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Introduction

1 Bundled agents are VCS processes that manage resources of predefined resource typesaccording to commands received from the VCS engine, HAD. These agents are a part ofVCS, and are installed when VCS is installed. A system has one agent per resource typethat monitors all resources of that type; for example, a single IP agent manages all IPresources.

When the agent starts, it obtains the necessary configuration information from VCS. Theagent then periodically monitors the resources, and updates VCS with the resource status.

Agents typically:

✔ Bring resources online.

✔ Take resources offline.

✔ Monitor resources and report state changes to VCS.

Note Refer to the VERITAS Cluster Server 3.5 User’s Guide for general information on VCSagents.

Resources and Their AttributesResources are the key parts of a system and are known by their type, such as a disk, avolume, or an IP address. VCS includes a set of resource types, which are defined in thetypes.cf file by a collection of attributes. Each type has a corresponding agent that isdesigned to control the resource. The VCS configuration file, main.cf, contains the valuesfor the resource attributes and has an include directive to the types.cf file.

An attribute’s given value configures the resource to function in a specific way. Bymodifying the value of a resource attribute, you can change the way the VCS agentmanages the resource. For example, the IP agent monitors an IP address resource. Thespecific address to be monitored is identified by the attribute “Address” whose value isthe specific IP address.

1

Modifying Agents and Their Resources

Modifying Agents and Their ResourcesUse Cluster Manager (Java Console), Cluster Manager (Web Console), or the VCScommand line to dynamically modify the configuration of the resources managed by anagent. See the VERITAS Cluster Server 3.5 User’s Guide for instructions on how to completethese tasks.

VCS enables you to edit the main.cf file directly. To implement these changes, make sureto restart VCS.

Categories of Bundled AgentsVCS enables you to use bundled agents for networking, basic storage, application control,and VCS infrastructure and support functions:

Networking

� IP

� IPMultiNIC

� MultiNICA

� NIC

Basic Storage

� DiskGroup

� LVMCombo

� LVMLogicalVolume

� LVMVolumeGroup

� Mount

� NFS

� Share

� Volume

2 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Categories of Bundled Agents

Application Control

� Application

� Process

VCS Infrastructure and Support

� NotifierMngr

� Phantom

� Proxy

� ServiceGroupHB

� VRTSWebApp

� ElifNone

� FileNone

� FileOnOff

� FileOnOnly

Chapter 1, Introduction 3

Categories of Bundled Agents

4 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

VCS Bundled Agents

2 The tables in this chapter provide information on resource types, entry points (see below),state definitions, and modifiable attributes for VCS bundled agents. The tables indicatewhich attributes are required and which are optional. The resource type as it is defined inthe types.cf file is included along with a sample of the configuration in the main.cf file.

An entry point is a plug-in that is called when an event occurs within the VCS agent. TheVCS engine uses entry points to manipulate resources. In addition to the online, offline, andmonitor entry points, the clean entry point applies to most agents and is calledautomatically by the framework when all ongoing actions associated with a resource mustbe terminated and the resource must be taken offline (perhaps forcibly).

Refer to the VERITAS Cluster Server 3.5 Agent Developer’s Guide for more information onentry points and the VCS agent framework. Refer to the VERITAS Cluster Server 3.5 User’sGuide for more information on VCS attributes.

5

Application Agent

Application Agent

Description Brings applications online, takes them offline, and monitors their status. Enablesyou to specify different executables for the online, offline, and monitor routines.(An application has an executable to start it and an executable to stop it.) Theexecutables must exist locally on each node. By default, an application runs inthe context of root. Specify the user name to run an application in a user context.

The agent starts and stops the application with user-specified programs.Monitor the application in the following ways:

� Use the monitor program

� Specify a list of processes to be monitored

� Specify a list of process ID files to be monitored

� All or some of the above

Entry Points � Online—Runs the StartProgram with the specified parameters in thespecified user context.

� Offline—Runs the StopProgram with the specified parameters in thespecified user context.

� Monitor—If MonitorProgram is specified, the agent executes theuser-defined MonitorProgram in the user-specified context. If PidFiles isspecified, the routine verifies that the process ID found in each listed file isrunning. If MonitorProcesses is specified, the routine verifies that each listedprocess is running in the user-specified context.

MonitorProgram must return ONLINE to employ any other monitoringmethod. Any one, two, or three of these attributes can be used to monitor theapplication. If any one process specified in either PidFiles orMonitorProcesses is determined not to be running, the monitor returnsOFFLINE.

� Clean—Kills processes specified in PidFiles or MonitorProcesses. Ensuresthat only those processes (specified in MonitorProcesses) running with theuser ID specified in the User attribute are killed. If the CleanProgram isdefined, the agent executes the CleanProgram.

State Definitions ONLINE—Indicates that all processes specified in PidFiles and MonitorProcessesare running and that the MonitorProgram returns ONLINE.

OFFLINE—Indicates that at least one process specified in PidFiles orMonitorProcesses is not running, or that the MonitorProgram returns OFFLINE.

UNKNOWN—Indicates that the application’s state is indeterminable.

6 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Application Agent

Required Attributes Type andDimension

Definition

StartProgram string-scalar The executable, created locally on each node, that starts theapplication. Specify the complete path of the executable.Command-line arguments (if applicable) follow the name ofthe executable, separated by spaces.

StopProgram string-scalar The executable, created locally on each node, that stops theapplication. Specify the complete path of the executable.Command-line arguments (if applicable) follow the name ofthe executable, separated by spaces.

At least one of thefollowing attributes:

� MonitorProcesses

� MonitorProgram

� PIDFiles

See descriptions underOptional Attributes.

see below see below

Optional Attributes Type andDimension

Definition

CleanProgram string-scalar The executable, created locally on each node, that forcibly stopsthe application. Specify the complete path of the executable.Command-line arguments (if applicable) follow the name ofthe executable, separated by spaces.

MonitorProcesses string-vector A list of processes to be monitored and cleaned. Each processname is the name of an executable. Qualify the executable namewith its complete path if the path is used to start the executable.

The process name must be the full command line argumentdisplayed by the ps -u <user> -o args | morecommand for the process.

MonitorProgram string-scalar The executable, created locally on each node, that will monitorthe application. Specify the complete path of the executable.Command-line arguments (if applicable) follow the name ofthe executable, separated by spaces.

MonitorProgram can return the following VCSAgResStatevalues: OFFLINE values is 100; ONLINE values are from 101 to 110(depending on the confidence level); 110 equals confidencelevel of 100%. Any other value = UNKNOWN.

Chapter 2, VCS Bundled Agents 7

Application Agent

Type Definition

type Application (static str ArgList[] = { User, StartProgram, StopProgram,

CleanProgram, MonitorProgram, PidFiles, MonitorProcesses }

str User = rootstr StartProgramstr StopProgramstr CleanProgramstr MonitorProgramstr PidFiles[]str MonitorProcesses[]

)

PidFiles string-vector A list of pid files that contain the process ID of the processes tobe monitored and cleaned. These files areapplication-generated files. Each PID file contains one PIDwhich will be monitored. Specify the complete path of each pidfile in the list.

The process ID can change when the process restarts. If theapplication takes time to update the pid file, the agent’smonitor script may return an incorrect result. If this occurs,increase the ToleranceLimit in the resource definition.

User string-scalar The user whose ID is used to run StartProgram, StopProgram,MonitorProgram, and CleanProgram. The processes specifiedin the MonitorProcesses list must run in the context of thespecified user. Monitor checks the processes to make sure theyrun in this context.

Default is "root".

8 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Application Agent

Sample Configurations

Sample 1

In this example, the executable samba is configured as StartProgram and StopProgram,with start and stop specified as command-line arguments respectively. The agent isconfigured to monitor two processes: a process specified by the pid smbd.pid, and theprocess nmbd.

Application samba_app (User = "root"StartProgram = "/usr/sbin/samba start"StopProgram = "/usr/sbin/samba stop"PidFiles = { "/var/lock/samba/smbd.pid" }MonitorProcesses = { "nmbd" }

)

Sample 2

In this example, no user is specified; as a result, the configuration uses the root user. Theexecutable samba starts and stops the application, with start and stop as thecommand-line arguments respectively. The executable sambaMonitor monitors theapplication and uses all as its command-line argument. The agent monitors the smbdand nmbd processes.

Application samba_app2 (StartProgram = "/usr/sbin/samba start"StopProgram = "/usr/sbin/samba stop"CleanProgram = "/usr/sbin/samba force stop"MonitorProgram = "/usr/local/bin/sambaMonitor all"MonitorProcesses = { "smbd", "nmbd" }

)

Chapter 2, VCS Bundled Agents 9

Application Agent

Error Messages

Message Tag Description / Recommended Action

None of the parameters (MonitorProgram,PidFiles, MonitorProcesses) are specified tomonitor the application.

B Specify at least one parameter tomonitor the resource.

Program <MonitorProgram/CleanProgram>does not exist.

B Check if the specifiedMonitorProgram/CleanProgram exists.

VCSAgExec() failed, could not executeprogram (MonitorProgram/CleanProgram).

C Check if the user specified haspermission to executeMonitorProgram/CleanProgram.

Abnormal termination of program(MonitorProgram/CleanProgram).

C Check if the user specified haspermission to executeMonitorProgram/CleanProgram.

Error while getting information about user. B Check if the user specified exists on thelocal system.

Memory allocation failed. C Could not allocate memory tomonitor/clean the resource.

No start program defined. B StartProgram is not specified to bringthe resource online.

No stop program defined. B StopProgram is not specified to take theresource offline.

Program (StartProgram/StopProgram) doesnot exist or is not executable.

B Check if the StartProgram/StopProgramexists and is in executable mode.

10 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

DiskGroup Agent

DiskGroup Agent

Description Brings online, takes offline, and monitors a VERITAS Volume Manager (VxVM) diskgroup. This agent uses VxVM commands.

Entry Points � Online—Imports the disk group using the vxdg command.

� Offline—Deports the disk group using the vxdg command.

� Monitor—Determines if the disk group is online or offline using the vxdgcommand.

� Clean—Indicates a condition exists that requires administrator intervention.

State Definitions ONLINE—Indicates that the disk group is imported.

OFFLINE—Indicates that the disk group is not imported.

UNKNOWN—Indicates that a problem exists either with the configuration or the abilityto determine the status of the resource.

Required Attribute Type andDimension

Definition

DiskGroup string-scalar Name of the disk group configured with VERITAS VolumeManager.

For example, diskgroup1.

Optional Attributes Type andDimension

Definition

StartVolumes string-scalar If value is 1, the DiskGroup online script starts all volumesbelonging to that disk group after importing the group.

Default is 1.

StopVolumes string-scalar If value is 1, the DiskGroup offline script stops all volumesbelonging to that disk group before deporting the group.

Default is 1.

Chapter 2, VCS Bundled Agents 11

DiskGroup Agent

Setting the noautoimport Flag for a Disk Group

VCS requires that the noautoimport flag of an imported disk group be explicitly set to“true.” This enables VCS to control the importation and deportation of disk groups asneeded when bringing disk groups online and taking them offline.

Note If you enable a disk group configured as a DiskGroup resource that does not havethe noautoimport flag set to true, VCS forcibly deports the disk group andreimports it with the noautoimport flag set to true. This may disrupt applicationsrunning on the disk group.

To check the status of the noautoimport flag for an imported disk group, type:

# vxprint -l disk_group | grep noautoimport

If the output from this command is blank, the noautoimport flag is set to false and VCSlacks the necessary control.

To explicitly set the noautoimport flag to true, deport the disk group and import it withthe -t option as follows:

Deport the disk group:

# vxdg deport disk_group

Import the disk group, specifying the noautoimport flag be set to true to ensure the diskgroup is not automatically imported:

# vxdg -t import disk_group

Type Definition

type DiskGroup (static int OnlineRetryLimit = 1str DiskGroupNameRule = resource.DiskGroupstatic str ArgList[] = { DiskGroup, StartVolumes, StopVolumes,

MonitorOnly }str StartVolumes = 1str StopVolumes = 1static int NumThreads = 1

)

Sample ConfigurationDiskGroup dg1 (

DiskGroup = testdg_1)

12 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

ElifNone Agent

ElifNone Agent

Type Definition

type ElifNone (static str ArgList[] = { PathName }static int OfflineMonitorInterval = 60NameRule = resource.PathNamestatic str Operations = Nonestr PathName

)

Sample Configuration

ElifNOne tmp_file01 (PathName = "/tmp/file01")

Description Monitors a file.

Entry Point Monitor—Checks if the specified file exists. If it does, the agent reports as OFFLINE. If itdoes not, the agent reports as ONLINE.

Required Attribute Type andDimension

Description

PathName string-scalar Specifies the complete pathname, starting with the slash (/)preceding the file name.

Chapter 2, VCS Bundled Agents 13

FileNone Agent

FileNone Agent

Type Definition

type FileNone (static str ArgList[] = { PathName }static int OfflineMonitorInterval = 60NameRule = resource.PathNamestatic str Operations = Nonestr PathName

)

Sample Configuration

FileNone tmp_file01 (PathName = "/tmp/file01")

Description Monitors a file.

Entry Point Monitor—Checks if the specified file exists. If it does, the agent reports as ONLINE. If itdoes not, the agent reports as OFFLINE.

Required Attribute Type andDimension

Description

PathName string-scalar Specifies the complete pathname, starting with the slash (/)preceding the file name.

14 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

FileOnOff Agent

FileOnOff Agent

Type Definition

type FileOnOff (static str ArgList[] = { PathName }NameRule = resource.PathNamestr PathName

)

Sample ConfigurationFileOnOff tmp_file01 (

PathName = "/tmp/file01")

Description Creates, removes, and monitors files.

Entry Points � Online—Creates an empty file with the specified name (if one does not alreadyexist).

� Offline—Removes the specified file.

� Monitor—Checks if the specified file exists. If it does, the agent reports as ONLINE.If it does not, the agent reports as OFFLINE.

Required Attribute Type andDimension

Description

PathName string-scalar Specifies the complete pathname, starting with the slash (/)preceding the file name.

Chapter 2, VCS Bundled Agents 15

FileOnOnly Agent

FileOnOnly Agent

Type Definition

type FileOnOnly (static str ArgList[] = { PathName }NameRule = resource.PathNamestatic str Operations = OnOnlystr PathName

)

Sample Configuration

FileOnOnly tmp_file02 (PathName = "/tmp/file02")

Description Creates and monitors files.

Entry Points � Online—Creates an empty file with the specified name (if one does not alreadyexist).

� Monitor—Checks if the specified file exists. If it does, the agent reports as ONLINE.If it does not, the agent reports as OFFLINE.

Required Attribute Type andDimension

Description

PathName string-scalar Specifies the complete pathname, starting with the slash (/)preceding the file name.

16 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

IP Agent

IP Agent

Description Manages the process of configuring a virtual IP address and its subnet mask on aninterface. The interface must be plumbed with a physical (or administrative) base IPaddress before a virtual IP address can be assigned. The virtual IP address must notbe one currently in use.

Entry Points � Online—Checks if the IP address is in use by another system. Uses theifconfig command to set the IP address on a unique alias on the interface.

� Offline—Brings down the IP address associated with the specified interface.Uses the ifconfig command to set the interface alias to 0.0.0.0 and the stateto “down.”

� Monitor—Monitors the interface to test if the IP address associated with theinterface is alive.

Required Attributes Type andDimension

Description

Address string-scalar Virtual IP address associated with the interface. (The virtual IPaddress is different from the base and administrative IPaddresses of the interface.)

For example, "172.29.9.24".

Device string-scalar Name of the NIC device associated with the IP address. Containsthe device name without an alias.

For example, lan0.

Optional Attributes Type andDimension

Definition

ArpDelay integer-scalar Number of seconds to sleep between configuring an interface andsending out a broadcast to inform routers about this IP address.

Default is 1.

IfconfigTwice integer-scalar Causes an IP address to be configured twice using an ifconfigup-down-up sequence. Increases the probability of gratuitousARP requests (generated by ifconfig up) to reach clients.

Default is 0.

NetMask string-scalar Netmask associated with the IP address of the resource. Thevalue of the netmask may be specified in decimal (base 10) orhexadecimal (base 16).

Default is "255.0.0.0" (if the ifconfig command is executedwithout a netmask argument).

Note VERITAS recommends that you specify a netmask for eachvirtual interface.

Chapter 2, VCS Bundled Agents 17

IP Agent

Type Definition

type IP (static str ArgList[] = { Device, Address, NetMask, Options,

ArpDelay, IfconfigTwice }NameRule = IP_ + resource.Addressstr Devicestr Addressstr NetMaskstr Optionsint ArpDelay = 1int IfconfigTwice = 0

)

Sample Configurations

Sample 1

IP IP_192_203_47_61 (Device = lan0Address = "192.203.47.61")

Sample 2: NetMask in decimal (base 10)

IP IP_192_203_47_61 (Device = lan0Address = "192.203.47.61"NetMask = "255.255.248.0")

Sample 3: NetMask in hexadecimal (base 16)

IP IP_192_203_47_61 (Device = lan0Address = "192.203.47.61"NetMask = "0xfffff800")

Options string-scalar Options for the ifconfig command.

For example, "broadcast 10.182.15.255".

18 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

IPMultiNIC Agent

IPMultiNIC Agent

Description Monitors the virtual (logical) IP address configured as an alias on one interface of aMultiNICA resource. If the interface faults, the agent works with the MultiNICAresource to fail over the virtual address to a backup interface. If multiple servicegroups have IPMultiNICs associated with the same MultiNICA resource, only onegroup will have the MultiNICA resource. The other groups will have Proxy resourcespointing to it.

Entry Points � Online—Configures a virtual IP address on one interface of the MultiNICAresource.

� Offline—Removes a virtual IP address from one interface of the MultiNICAresource.

� Monitor—Checks if the virtual IP address is configured on one interface of theMultiNICA resource.

State Definitions ONLINE—Indicates that the specified IP address is assigned to the device.

OFFLINE—Indicates that the specified IP address is not assigned to the device.

UNKNOWN—Indicates that the resource is configured inaccurately in the main.cf.

Required Attributes Type andDimension

Description

Address string-scalar Virtual IP address assigned to the active NIC.

MultiNICResName string-scalar Name of associated MultiNICA resource that determines theactive NIC.

Optional Attributes Type andDimension

Description

IfconfigTwice integer-scalar Causes an IP address to be configured twice using an ifconfigup-down-up sequence. Increases the probability of gratuitousARP requests (generated by ifconfig up) to reach clients.

Default is 0.

NetMask string-scalar Netmask for the virtual IP address. The value of the netmaskmay be specified in decimal (base 10) or hexadecimal (base 16).

Default is "255.0.0.0" (if the ifconfig command is executedwithout a netmask argument).

Note VERITAS recommends that you specify a netmask foreach virtual interface.

Options string-scalar Options for the ifconfig command.

For example, "broadcast 10.182.15.255".

Chapter 2, VCS Bundled Agents 19

IPMultiNIC Agent

Type Definition

type IPMultiNIC (static str ArgList[] = { "MultiNICResName:Device", Address,

NetMask, Options, "MultiNICResName:Probed", MultiNICResName, IfconfigTwice }

static int MonitorTimeOut = 120NameRule = IPMultiNIC_ + resource.Addressstr Addressstr NetMaskstr Optionsstr MultiNICResNameint IfconfigTwice = 0

)

Sample Configuration, IPMultiNIC and MultiNICA

For details on the following example, refer to “Sample Configuration: MultiNICA andIPMultiNIC” on page 31.

group grp1 (SystemList = { sysa, sysb }AutoStartList = { sysa })MultiNICA mnic (

Device@sysa = { lan0 = "166.98.16.103", lan3 = "166.98.16.103" }Device@sysb = { lan0 = "166.98.16.104", lan3 = "166.98.16.104" }NetMask = "255.255.255.0"Options = "arp"RouteOptions@sysa = "default 166.98.16.103 0"RouteOptions@sysb = "default 166.98.16.104 0"NetWorkHosts = { "166.11.20.31", "182.1.21.5" })

IPMultiNIC ip1 (Address = "166.98.14.78"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp")

ip1 requires mnic

group grp2 (SystemList = { sysa, sysb }

20 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

IPMultiNIC Agent

AutoStartList = { sysa })

IPMultiNIC ip2 (Address = "166.98.14.79"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp")

Proxy proxy (TargetResName = mnic)

ip2 requires proxy

Chapter 2, VCS Bundled Agents 21

LVMCombo Agent

LVMCombo Agent

Description Defines the logical volumes and volume groups associated with an application.Use LVMCombo as an alternative to LVMLogicalVolume and LVMVolumeGroupwhen defining logical volumes and volume groups. LVMCombo is similar toLVMLogicalVolume and LVMVolumeGroup, but does not enable LVMconfiguration information to be backed up every time resources are brought onlineor taken offline.

Entry Points � Online—Activates the volume group and any of the logical volumes that arenot available. The volume group must be imported by each system in thecluster, but not activated by each system.

This agent does not import volume groups because of the way LVM storesconfiguration information. Use the HP-UX SAM tool to import a volumegroup. (For more information on SAM, refer to the HP manual HP-UX SystemAdministration Tasks.)

� Offline—Deactivates the volume group, but does not deactivate the logicalvolumes. The logical volumes are automatically deactivated when the volumegroup is deactivated.

� Monitor—If the volume group and all of the logical volumes are available, theresource is ONLINE. Otherwise, the resource is OFFLINE.

The monitor entry point does not perform any I/O on disk. If a disk that makesup a logical volume is powered off, the agent will not be aware of this situationuntil the logical volume is marked unavailable. This may occur if the filesystem or the application using the logical volume attempts an I/O operationand fails. LVM can then set the logical volume as unavailable.

Required Attributes Type andDimension

Description

LogicalVolume string-vector List of logical volumes in a volume group.

VolumeGroup string-scalar Name of a volume group.

22 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

LVMCombo Agent

Type Definition

type LVMCombo (static str ArgList[] = { VolumeGroup, LogicalVolumes }NameRule = resource.VolumeGroupstr VolumeGroupstr LogicalVolumes[]

)

Sample Configuration

LVMCombo dg1 (VolumeGroup = dg1LogicalVolumes = { lvol1, lvol2 })

Chapter 2, VCS Bundled Agents 23

LVMLogicalVolume Agent

LVMLogicalVolume Agent

Type Definition

type LVMLogicalVolume (static str ArgList[] = { LogicalVolume, VolumeGroup }NameRule = resource.VolumeGroup + "_" + resource.LogicalVolumestr LogicalVolumestr VolumeGroup

)

Sample Configuration

LVMLogicalVolume sharedg_lvol1 (LogicalVolume = lvol1VolumeGroup = sharedg)

Description Brings online, takes offline, and monitors Logical Volume Manager (LVM) logicalvolumes.

Entry Points � Online—Activates the logical volume with the lvchange command.

� Offline—Deactivates the logical volume with the lvchange command.

� Monitor—Determines if the logical volume is accessible by performing readI/O on the raw logical volume.

Required Attributes Type andDimension

Description

LogicalVolume string-scalar Name of the logical volume.

VolumeGroup string-scalar Name of the volume group containing the logical volume.

24 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

LVMVolumeGroup Agent

LVMVolumeGroup Agent

Type Definition

type LVMVolumeGroup (static str ArgList[] = { VolumeGroup }NameRule = resource.VolumeGroupstr VolumeGroup

)

Sample Configuration

LVMVolumeGroup sharedg (VolumeGroup = sharedg)

Description Activates, deactivates, and monitors Logical Volume Manager (LVM) volumegroups.

Entry Points � Online—Activates a volume group with the vgchange command. The VolumeGroup must be imported by each system in the cluster, but not activated byeach system.

LVMCombo does not import volume groups because of the way LVM storesconfiguration information. Use the HP-UX SAM tool to import a volumegroup. (For more information on SAM, refer to the HP manual HP-UX SystemAdministration Tasks.)

� Offline—Deactivates a volume group with the vgchange command.

� Monitor—Uses the vgdisplay command to determine if the volume group isavailable.

Required Attribute Type andDimension

Description

VolumeGroup string-scalar Name of the volume group configured with LVM.

Chapter 2, VCS Bundled Agents 25

Mount Agent

Mount Agent

Description Brings online, takes offline, and monitors a file system mount point.

Entry Points � Online—Mounts a block device on the directory. If the mount process fails, theagent attempts to run the fsck command on the raw device to remount the blockdevice.

� Offline—Unmounts the file system.

� Monitor—Determines if the file system is mounted. Checks mount status usingthe stat and statvfs commands.

� Clean—See description on page 5.

State Definitions ONLINE—Indicates that the block device is mounted on the specified mount point.

OFFLINE—Indicates that the block device is not mounted on the specified mount point.

UNKNOWN—Indicates that a problem exists with the configuration.

Required Attributes Type andDimension

Description

BlockDevice string-scalar Device for mount point.

FsckOpt string-scalar Options for fsck command. "-y" or "-n" must be included asarguments to fsck; otherwise, the resource cannot come online.VxFS file systems will perform a log replay before a full fsckoperation (enabled by "-y") takes place. Refer to the manual pageon the fsck command for more information.

FSType string-scalar Type of file system. Does not support NFS mounts; supports localmounts only.

For example, vxfs or hfs.

MountPoint string-scalar Directory for mount point.

Optional Attributes Type andDimension

Description

MountOpt string-scalar Options for mount command.

SnapUmount integer-scalar If set to 1, this attribute automatically unmounts VxFS snapshotswhen the file system is unmounted.

Default is 0 (No).

26 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Mount Agent

Type Definition

type Mount (static str ArgList[] = { MountPoint, BlockDevice, FSType,

MountOpt, FsckOpt, SnapUmount }NameRule = resource.MountPointstr MountPointstr BlockDevicestr FSTypestr MountOptstr FsckOptint SnapUmount = 0

)

Sample ConfigurationMount export1 (

MountPoint = "/export1"BlockDevice = "/dev/sharedg/lvol1"FsckOpt = "-y"FSType = "vxfs"MountOpt = "ro")

Chapter 2, VCS Bundled Agents 27

MultiNICA Agent

MultiNICA Agent

Description Represents a set of network interfaces, and provides failover capabilities betweenthem. Each interface in a MultiNICA resource has a base IP address, which can bethe same or different. The MultiNICA agent configures one interface at a time. If theagent does not detect activity on the configured interface, it configures a newinterface and migrates IP aliases to it.

If an interface is associated with a MultiNICA resource, the interface should not beassociated with any other MultiNICA or NIC resource. If the same set of interfacesmust be a part of multiple service groups, configure:

� A MultiNICA resource in one of the service groups.

� Proxy resources that point to the MultiNIC resource in the other service groups.

Entry Point � Monitor—Checks for activity on a configured interface by sampling inputpackets received on that interface. If monitor does not detect activity, it forcesactivity by sending out a broadcast ping. If monitor detects a failure, it migratesto the next interface.

Required Attributes Type andDimension

Description

Device string-association List of interfaces and their base IP addresses.

NetworkHosts string-vector List of hosts on the network that are pinged to determine if thenetwork connection is alive. Enter the IP address of the host(instead of the HostName) to prevent the monitor from timingout (DNS causes the ping to hang).

For example, NetworkHosts = { "166.93.2.1", "166.97.1.2" }.

Optional Attributes Type andDimension

Description

ArpDelay integer-scalar Number of seconds to sleep between configuring an interfaceand sending out a broadcast to inform routers about the base IPaddress.

Default is 1.

28 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

MultiNICA Agent

Handshake-Interval integer-scalar Computes the maximum number of attempts the agent makeseither to ping a host (listed in the NetworkHosts attribute) whenit fails over to a new NIC, or to ping the default broadcastaddress (depending on the attribute configured) when it failsover to a new NIC.

Each attempt, which includes a five second sleep interval, maytake about 10 seconds. A value of 90 does not indicate thatfailover will take 90 seconds.

To prevent spurious failovers, the agent must try to contact ahost on the network several times before marking a NIC asfaulted. The lowest value that can be set for this attribute is 50,or five attempts. Increased values result in longer failover times,whether between the NICs or from system to system in the caseof faulted NICs.

IfconfigTwice integer-scalar Causes an IP address to be configured twice, using anifconfig up-down-up sequence. Increases the probability ofgratuitous ARP requests (caused by ifconfig up) to reachclients.

Default is 0.

NetMask string-scalar Netmask for the base IP address. The value of NetMask may bespecified in decimal (base 10) or hexadecimal (base 16).

Default is "255.0.0.0" (if the ifconfig command is executedwithout a netmask argument).

Note VERITAS recommends that you specify a netmask foreach virtual interface.

Options string-scalar Options for the ifconfig command.

For example, "broadcast 10.182.15.255".

RouteOptions string-scalar String to add a route when configuring an interface. Use onlywhen configuring the local host as the default gateway.

The string contains arguments to the route command. Noroutes are added if this string is set to NULL.

Chapter 2, VCS Bundled Agents 29

MultiNICA Agent

Notes about Using MultiNICA Agent

� If all NICs configured in the Device attribute are down, the MultiNICA agent faultsthe resource after a two to three minute interval. This delay occurs because theMultiNICA agent tests the failed NIC several times before marking the resourceOFFLINE. Messages recorded in the engine log during failover provide a detaileddescription of the events that take place. (The engine log is located in/var/VRTSvcs/log/engine_A.log.)

� The MultiNICA agent supports only one active NIC on one IP subnet; the agent doesnot work with multiple active NICs on the same subnet.

� The primary NIC must be configured before VCS is started. Use the ifconfig(1M)command to configure it manually, or edit the default files provided by the system toautomatically configure the NIC at boot time.

Type Definition

type MultiNICA (static str ArgList[] = { Device, NetMask, ArpDelay, Options,

RouteOptions, MonitorOnly, IfconfigTwice, HandshakeInterval, NetworkHosts }

static int OfflineMonitorInterval = 60static str Operations = Nonestatic int MonitorTimeout = 300NameRule = MultiNICA_ + group.Namestr Device{}str NetMaskint ArpDelay = 1str Optionsstr RouteOptionsint IfconfigTwice = 0int HandshakeInterval = 90str NetworkHosts[]

)

30 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

MultiNICA Agent

Sample Configuration: MultiNICA and IPMultiNIC

In the following example, two machines, sysa and sysb, each have a pair of networkinterfaces, lan0 and lan3. The two interfaces, lan0 and lan3, have the same base, orphysical, IP address. However, the addresses on different hosts can differ. Note the linesbeginning Device@sysa and Device@sysb; the use of different physical addresses showshow to localize an attribute for a particular host.

The MultiNICA resource fails over only the physical IP address to the backup NIC duringa failure. The logical IP addresses are configured by the IPMultiNIC agent. The resourcesip1 and ip2, shown in the following example, have the Address attribute which containsthe logical IP address. If a NIC fails on sysa, the physical IP address and the two logical IPaddresses fails over from lan0 to lan3. If lan3 fails, the address fails back to lan0 if lan0 isreconnected.

However, if both the NICs on sysa are disconnected, the MultiNICA and IPMultiNICresources work in tandem to fault the group on sysa. The entire group now fails over tosysb.

If you have more than one group using the MultiNICA resource, the second group can usea Proxy resource to point to the MultiNICA resource in the first group. This preventsredundant monitoring of the NICs on the same system. The IPMultiNIC resource isalways made dependent on the MultiNICA resource. See “IPMultiNIC Agent” onpage 19.

group grp1 (SystemList = { sysa, sysb }AutoStartList = { sysa })MultiNICA mnic (

Device@sysa = { lan0 = "166.98.16.103", lan3 = "166.98.16.103" }Device@sysb = { lan0 = "166.98.16.104", lan3 = "166.98.16.104" }NetMask = "255.255.255.0"Options = "arp"RouteOptions@sysa = "default 166.98.16.103 0"RouteOptions@sysb = "default 166.98.16.104 0"NetWorkHosts = { "166.11.20.31", "182.1.21.5" })

IPMultiNIC ip1 (Address = "166.98.14.78"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp")

ip1 requires mnic

Chapter 2, VCS Bundled Agents 31

MultiNICA Agent

group grp2 (SystemList = { sysa, sysb }AutoStartList = { sysa })

IPMultiNIC ip2 (Address = "166.98.14.79"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp")

Proxy proxy (TargetResName = mnic)

ip2 requires proxy

32 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

NFS Agent

NFS Agent

Description Starts and monitors the nfsd, rpc.mountd, rpc.lockd, and rpc.statd processes requiredby all exported NFS file systems. Supports NFS versions 2 and 3.

Entry Points � Online—Checks if nfsd, rpc.mountd, rpc.lockd, and rpc.statd processes arerunning. If they are not running, the agent starts the processes and exits.

� Monitor—Monitors versions 2 and 3 of the nfsd process, versions 1, 2, and 3 of therpc.mountd process, versions 1, 3, and 4 of the rpc.lockd process, and version 1 ofthe rpc.statd process. Monitors TCP and UDP versions of the processes by sendingRPC (Remote Procedure Call) calls clnt_create and clnt_call to the RPC server. Ifcalls succeed, the resource is reported ONLINE.

� Clean—Kills all NFS-related processes (mentioned in the Online entry pointdescription) and restarts them.

Optional Attributes Type andDimension

Definition

Nservers integer-scalar Specifies the number of concurrent NFS requests the server canhandle.

Default is 4.

Protocol string-scalar Selects the transport on which NFS service runs. Use the followingoptions:

� All (start NFS service over both UDP and TCP)

� UDP (start NFS service over only UDP)

� TCP (start NFS service over only TCP)

Note The TCP option is not supported in this release. Use the UDPor All option instead.

Chapter 2, VCS Bundled Agents 33

NFS Agent

Type Definition

type NFS (int Nservers = 4NameRule = "NFS_" + group.Name + "_" + resource.Nserversstatic str ArgList[] = { Nservers, Protocol}static str Operations = OnOnlystatic int RestartLimit = 1str Protocol = all

)

Sample Configuration

NFS NFS_groupx (Nservers = 8Protocol = udp)

34 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

NIC Agent

NIC Agent

Description Monitors the configured NIC. If a network link fails, or if a problem ariseswith the device card, the resource is marked OFFLINE. The NIC listed inthe Device attribute must have an administration IP address, which is thedefault IP address assigned to the physical interface of a host on anetwork. This agent does not configure network routes or administrationIP addresses.

Entry Point � Monitor—Tests the network card and network link. Pings the hostslisted in the NetworkHosts attribute. If monitor successfully pings atleast one host in the list, the resource is marked ONLINE.

State Definitions ONLINE—Indicates that the NIC is working.

OFFLINE—Indicates that the NIC has failed.

UNKNOWN—Indicates that the device is not configured or is configuredincorrectly.

Required Attributes Type andDimension

Definition

Device string-scalar Name of the NIC.

For example, lan0.

NetworkHosts string-vector List of hosts on the network. The agent pings thehosts to determine if the network connection isalive. Enter the IP address of the host instead ofthe HostName to prevent the monitor from timingout (DNS problems cause the ping to hang).

For example, 166.96.15.22.

Optional Attribute Type andDimension

Definition

NetworkType string-scalar Type of network. VCS currently only supportsEthernet (ether).

Chapter 2, VCS Bundled Agents 35

NIC Agent

Requirements for NIC

✔ Verify that each NIC has the correct administrative IP address and subnet mask.

✔ Verify that each NIC does not have built-in failover support. If it does, disable it. (Ifnecessary, refer to the NIC documentation.)

Type Definition

type NIC (static str ArgList[] = { Device, NetworkType, NetworkHosts }NameRule = group.Name + "_" + resource.Devicestatic int OfflineMonitorInterval = 60static str Operations = Nonestr Devicestr NetworkTypestr NetworkHosts[]

)

Sample Configuration

NIC groupx_lan0 (Device = lan0NetworkHosts = { "166.11.20.31", "182.1.21.5" })

36 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

NotifierMngr Agent

NotifierMngr Agent

Description Starts, stops, and monitors a notifier process, making it highly available. The notifierprocess manages the reception of messages from VCS and GCM and the delivery ofthose messages to SNMP consoles and SMTP servers. See the VERITAS Cluster ServerUser’s Guide for a description of types of events that generate notification. See thenotifier(1) manual page to configure notification from the command line.

Note The attributes of the NotifierMngr agent cannot be dynamically changed usingthe hares -modify command. Changes made using this command areeffective after notifier is restarted.

Entry Points � Online—Starts the notifier process with its required arguments.

� Offline—VCS sends a SIGABORT. If the process does not exit within one second,VCS sends a SIGKILL.

� Monitor—Monitors the notifier process.

� Clean—Sends SIGKILL.

State Definitions ONLINE—Indicates that the Notifier process is running.

OFFLINE—Indicates that the Notifier process is not running.

UNKNOWN—Indicates that the user did not specify the required attribute for theresource.

Required Attributes Type andDimension

Description

SnmpConsoles string-association

Specifies the machine name of the SNMP manager and the severitylevel of the messages to be delivered to the SNMP manager. Theseverity levels of messages are Information, Warning, Error, andSevereError. Specifying a given severity level for messages generatesdelivery of all messages of equal or higher severity.

For example,

"172.29.10.89" = Error, "172.29.10.56" = Information

Note SnmpConsoles is a required attribute if SmtpServer is notspecified; otherwise, SnmpConsoles is an optional attribute. Theuser can specify both SnmpConsoles and SmtpServer ifnecessary.

SmtpServer string-scalar Specifies the machine name of the SMTP server.

Note SmtpServer is a required attribute if SnmpConsoles is notspecified; otherwise, SmtpServer is an optional attribute. Theuser can specify both SmtpServer and SnmpConsoles ifnecessary.

Chapter 2, VCS Bundled Agents 37

NotifierMngr Agent

Optional Attributes Type andDimension

Description

MessagesQueue integer-scalar Size of the VCS engine’s message queue.

Default is 30.

NotifierListeningPort integer-scalar Any valid TCP/IP port numbers that are not used.

Default is 14144.

SnmpdTrapPort integer-scalar Port to which SNMP traps are sent. The value specified for thisattribute is used for all consoles if more than one SNMP console isspecified.

Default is 162.

SnmpCommunity string-scalar Specifies the community ID for the SNMP manager.

Default is "public".

SmtpRecipients string-association

Specifies the email address to which information is sent and theseverity level of the messages to be received. The severity levels ofmessages are Information, Warning, Error, and SevereError.Specifying a given severity level for messages indicates that allmessages of equal or higher severity are received.

For example,

"[email protected]" = SevereError, "[email protected]" = Warning

Note SmtpRecipients is a required attribute if SmtpServer is specified.

EngineListeningPort integer-scalar Change this attribute if the VCS engine is listening on a port otherthan its default port.

Default is 14141.

38 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

NotifierMngr Agent

Type Definition

type NotifierMngr (static int RestartLimit = 3static str ArgList [] = { EngineListeningPort, MessagesQueue,

NotifierListeningPort, SnmpdTrapPort, SnmpCommunity, SnmpConsoles, SmtpServer, SmtpRecipients }

NameRule = resource.PathNameint EngineListeningPort = 14141int MessagesQueue = 30int NotifierListeningPort = 14144int SnmpdTrapPort = 162str SnmpCommunity = "public"str SnmpConsoles{}str SmtpServerstr SmtpRecipients{}

)

Sample Configuration

In the following configuration, the NotifierMngr agent is configured to run with tworesource groups, NicGrp and Grp1. NicGrp contains the NIC resource and a Phantomresource that enables VCS to determine the online and offline status of the group. (See“Phantom Agent” on page 41 for more information on verifying the status of groups thatonly contain OnOnly or Persistent resources (such as the NIC resource). NicGrp must beenabled to run as a parallel group on both systems.

Grp1 contains the NotifierMngr resource (ntfr) and a Proxy resource (nicproxy),configured for the NIC resource in the first group. In this example, NotifierMngr has adependency on the Proxy resource.

Note Only one instance of the notifier process can run in a cluster; the process cannot runin a parallel group.

The NotifierMngr resource sets up notification for all events to the SnmpConsole(snmpserv). In this example, only messages of SevereError level are sent to theSmptServer (smtp.your_company.com), and the recipient(vcsadmin@your_company.com).

Chapter 2, VCS Bundled Agents 39

NotifierMngr Agent

system north

system south

group NicGrp (SystemList = { north, south}AutoStartList = { north }Parallel = 1)

Phantom my_phantom ()

NIC NicGrp_en0 (Enabled = 1Device = en0NetworkType = ether)

group Grp1 (SystemList = { north, south }AutoStartList = { north })

Proxy nicproxy(TargetResName = "NicGrp_en0")

NotifierMngr ntfr (SnmpConsoles = { snmpserv = Information }SmtpServer = "smtp.your_company.com"SmtpRecipients = { "vcsadmin@your_company.com" = SevereError })

ntfr requires nicproxy

// resource dependency tree//// group Grp1// {// NotifierMngr ntfr// {// Proxy nicproxy// }// }

40 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Phantom Agent

Phantom Agent

Type Definition

type Phantom (static str ArgList[] = { Dummy }NameRule = Phantom_ + group.Namestr Dummy

)

Note The Dummy attribute is for VCS use only and is not configurable.

Sample Configurations

Sample 1

Phantom ()

Description Enables VCS to determine the status of service groups that do not include OnOffresources (resources that VCS can start and stop as required) by providing a “dummy”resource that can be brought online and taken offline. VCS cannot assess the status ofservice groups that only contain None (Persistent) and OnOnly resources because thestate of these resources is not considered in the process of determining whether agroup is online.

Include the Phantom resource in service groups that do not have OnOff resources.Service groups that do not include OnOff resources as members are not broughtonline, even if their member resources are brought online. Refer to the VERITASCluster Server User's Guide for information on resource categories.

Entry Point � Monitor—Determines status based on the status of its service group.

Chapter 2, VCS Bundled Agents 41

Phantom Agent

Sample 2

The following example shows a complete configuration file (main.cf), in which theFileNone resource and the Phantom resource are in the same group.

include "types.cf"

cluster PhantomCluster

system sysa

system sysb

group phantomgroup ( SystemList = { sysa, sysb } AutoStartList = { sysa } )

FileNone my_file_none (PathName = "/tmp/file_none" ) Phantom my_phantom ( )

// resource dependency tree // // group maingroup // { // Phantom my_Phantom // FileNone my_file_none // }

42 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Process Agent

Process Agent

Type Definition

type Process (static str ArgList[] = { PathName, Arguments }NameRule = resource.PathNamestr PathNamestr Arguments

)

Description Starts, stops, and monitors a process specified by the user.

Entry Points � Online—Starts the process with optional arguments.

� Offline—Terminates the process with a SIGTERM. If the process does not exit, VCSsends a SIGKILL.

� Monitor—Checks to see if the process is alive by scanning the process table for thename of the executable pathname and argument list. The procfs interface limits thematch to the initial 80 characters.

Required Attribute Type andDimension

Description

PathName string-scalar Defines complete pathname to access an executable program; thepath includes the program name. If a process is controlled by ascript, the PathName defines the complete path to the shell.

Pathname must not exceed 80 characters.

Optional Attribute Type andDimension

Description

Arguments string-scalar Passes arguments to the process. If a process is controlled by ascript, the script is passed as an argument. Multiple argumentsmust be separated by a single space. A string cannot accommodatemore than one space between arguments, nor allow for leading ortrailing whitespace characters. Arguments must not exceed 80characters (total).

Chapter 2, VCS Bundled Agents 43

Process Agent

Sample Configurations

Sample 1

Process usr_lib_sendmail (PathName = "/usr/lib/sendmail"Arguments = "bd q1h")

Sample 2

include "types.cf"

cluster ProcessCluster (...group ProcessGroup (

SystemList = { sysa, sysb }AutoStartList = { sysa })

Process Process1 (PathName = "/usr/local/bin/myprog"Arguments = "arg1 arg2")

Process Process2 (PathName = "/bin/csh"Arguments = "/tmp/funscript/myscript")

// resource dependency tree//// group ProcessGroup// {// Process Process1// Process Process2// }

44 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Proxy Agent

Proxy Agent

Type Definition

type proxy (static str ArgList[] = { TargetResName, TargetSysname,

"TargetResName:Probed", TargetResName:State }

NameRule = Proxy_ + resource.TargetResNamestatic int OfflineMonitorInterval = 60static str Operations = Nonestr TargetResNamestr TargetSysName

)

Description Mirrors the state of another resource on a local or remote system. Provides a means tospecify and modify one resource and have it reflected by its proxies.

Entry Point � Monitor—Determines status based on the target resource status.

Required Attribute Type andDimension

Description

TargetResName string-scalar Name of the target resource whose status is mirrored by Proxyresource. The target resource must be in a different resource groupfrom the Proxy resource.

Optional Attribute Type andDimension

Description

TargetSysName string-scalar Mirror the status of the TargetResName on system specified by theTargetSysName variable. If this attribute is not specified, the Proxyresource assumes the system is local.

Chapter 2, VCS Bundled Agents 45

Proxy Agent

Sample Configurations

Sample 1

// Proxy resource to mirror the state of the resource// tmp_VRTSvcs_file1 on the local system.

Proxy proxy1 (TargetResName = "tmp_VRTSvcs_file1")

Sample 2

// Proxy resource to mirror the state of the resource// tmp_VRTSvcs_file1 on sys1.

Proxy proxy1(TargetResName = "tmp_VRTSvcs_file1"TargetSysName = "sys1")

Sample 3

// Proxy agent to mirror the state of the resource mnic on// the local system; note that target resource is in grp1,// proxy in grp2; a target resource and its proxy cannot be in// the same group.

group grp1 (SystemList = { sysa, sysb }AutoStartList = { sysa })

MultiNICA mnic (Device@sysa = { lan0 = "166.98.16.103",lan3 = "166.98.16.103" }Device@sysb = { lan0 = "166.98.16.104",lan3 = "166.98.16.104" }NetMask = "255.255.255.0"Options = "arp"RouteOptions@sysa = "default 166.98.16.103 0"RouteOptions@sysb = "default 166.98.16.104 0"NetWorkHosts = { "166.11.20.31", "182.1.21.5" })

IPMultiNIC ip1 (Address = "166.98.14.78"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp"

46 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Proxy Agent

)

ip1 requires mnic

group grp2 (SystemList = { sysa, sysb }AutoStartList = { sysa })

IPMultiNIC ip2 (Address = "166.98.14.79"NetMask = "255.255.255.0"MultiNICResName = mnicOptions = "arp")

Proxy proxy (TargetResName = mnic)

ip2 requires proxy

Chapter 2, VCS Bundled Agents 47

ServiceGroupHB Agent

ServiceGroupHB Agent

Description Starts, stops, and monitors disk-based heartbeats associated with service groups. Seethe VERITAS Cluster Server 3.5 User’s Guide for details.

The heartbeat region resides on a block device (typically a logical volume) and consistsof 128 blocks starting on the specified block number (see Disks attribute). The localsystem, via the ServiceGroupHB agent, tries to obtain “ownership” of the availabledisks as specified by the Disks attribute. The system gains ownership of a device whenit determines that the device is available and not owned by another system.

When the system’s disk ownership meets the requirement of the AllOrNone attribute,the agent brings the resource online and monitors the resource. If disk ownership fallsbelow the AllOrNone requirement, VCS tries to fail over the group to another system.

Entry Points � Online—Brings resource online after ownership of the required number of disks orblock devices is obtained.

� Offline—Takes resource offline after relinquishing ownership of previouslyacquired disks.

� Clean—Takes resource offline and relinquishes ownership of previously acquireddisks.

� Open—Creates logical disk objects based on Disks attribute at VCS startup.

� Close—At VCS shutdown, deletes the logical disk objects created by Open.

� Monitor—Periodically checks if local system has ownership of required number ofdisks.

Required Attributes Type andDimension

Description

Disks string-vector Specifies, in paired values, the block device (typically a logicalvolume) and the starting block location to use for the heartbeat. Forexample, if the block device /dev/vg01/lvol_hb is used for theheartbeat region, and the starting block is 16, the paired set ofvalues is /dev/vg01/lvol_hb, 16.

A block device partition containing one or more heartbeat regionscannot be used for any other purpose. If the same device is used formore than one heartbeat region, starting block numbers must be atleast 64K (128 disk blocks) apart.

AllOrNone boolean-scalar Specifies number of block devices for which ownership is requiredto bring the resource online:

� all available devices (AllOrNone = 1)

� a simple majority of available devices (AllOrNone = 0)

Default is 1.

48 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

ServiceGroupHB Agent

Type Definition

type ServiceGroupHB (static str ArgList[] = { Disks, AllOrNone }static int OnlineRetryLimit = 5NameRule = ""str Disks[]boolean AllOrNone = 1

)

Sample Configuration

In this example, the volumes /dev/vg01/hb_vol1, /dev/vg01/hb_vol2, and/dev/vg01/hb_vol3 have service group heartbeat regions beginning at block 64 forservice group groupz. The device /dev/vg01/hb_vol1 has a second heartbeat regionbeginning at block 192 for service group groupy.

The AllOrNone attribute is set to 0 for sghb1, specifying that the service group can comeonline with ownership of two disks.

.system sysa.system sysb...group groupz (..

)

ServiceGroupHB sghb1 (Disks = { /dev/vg01/hb_vol1, 64, /dev/vg01/hb_vol2, 64,

/dev/vg01/hb_vol3, 64 }AllorNone = 0)

Mount exp1MountPoint = "/soup"BlockDevice = "/dev/vg01/vol4"FSType = ufsMountOpt = rw)

group groupy (.

Chapter 2, VCS Bundled Agents 49

ServiceGroupHB Agent

.)

.ServiceGroupHB sghb2 (

Disks = { /dev/vg01/hb_vol1, 192 })

Mount exp2MountPoint = "/nuts"BlockDevice = "/dev/vg01/lvol5"FSType = ufsMountOpt = rw)

.

exp1 requires sghb1exp2 requires sghb2

// resource dependency tree////// group groupz// {// Mount exp1// {// ServiceGroupHB sghb1// }// }// group groupy// {// Mount exp2// {// ServiceGroupHB sghb2// }// }

50 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Share Agent

Share Agent

Type Definition

type Share (static str ArgList[] = { PathName, Options }NameRule = nfs + resource.PathNamestr PathNamestr Options

)

Sample ConfigurationShare nfsshare1x (

PathName = "/share1x")

Description Shares, unshares, and monitors a single local resource for exporting an NFS filesystem to be mounted by remote systems.

Entry Points � Online—Shares an NFS file system.

� Offline—Unshares an NFS file system.

� Monitor—Reads /etc/xtab file and looks for an entry for the file systemspecified by PathName. If the entry exists, monitor returns ONLINE.

Required Attribute Type andDimension

Description

PathName string-scalar Pathname of the file system to be shared.

Optional Attribute Type andDimension

Description

Options string-scalar Options for the exportfs command.

Chapter 2, VCS Bundled Agents 51

Volume Agent

Volume Agent

Type Definition

type Volume (static str ArgList[] = { Volume, DiskGroup }NameRule = resource.DiskGroup + "_" + resource.Volumestr Volumestr DiskGroupstatic int NumThreads = 1

)

Sample ConfigurationVolume sharedg_vol3 (

Volume = vol3DiskGroup = sharedg)

Description Brings online, takes offline, and monitors a VERITAS Volume Manager (VxVM)volume.

Entry Points � Online—Starts the volume using the vxrecover command.

� Offline—Stops the volume using the vxvol command.

� Monitor—Determines if the volume is online or offline by reading a block from theraw device interface to the volume.

� Clean—See description on page 5.

Required Attributes Type andDimension

Description

DiskGroup string-scalar Name of the disk group which contains the volume.

For example, DG1.

Volume string-scalar Name of the volume.

For example, DG1Vol1.

52 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

VRTSWebApp Agent

VRTSWebApp Agent

Description Brings Web applications online, takes them offline, and monitors their status. Theapplication is a Java Web application conforming to the Servlet Specification 2.2 andruns inside of the Java Web server installed as a part of the VRTSweb package. Thisagent is used to monitor the Web Consoles of various VERITAS products, such asVCS, GCM, and VVR.

Entry Points Online—Starts the Web application with the specified parameters. If the Web server isnot already running, it will first start the server.

Offline—Removes the Web application from the Web server. If no other Webapplication is running, it shuts down the Web server.

Monitor—Checks if the specified Web application is currently running inside the Webserver. If the application is running, monitor reports ONLINE. If the application is notrunning, monitor reports OFFLINE.

Clean—Removes the Web application from the Web server. If no other Webapplication is running, it shuts down the Web server.

Required Attributes Type andDimension

Description

AppName string-scalar Name of the application as it appears in the Web server.

For example, for GCM, use "gcm"; for VCS, use "vcs". Access theapplications at: http://hostname:8181/gcm orhttp://localhost:8181/vcs.

InstallDir string-scalar Path to the Web application installation. The Web applicationmust be installed as a .war file with the same name as theAppName parameter; the "vcs" application must be installed asvcs.war. This attribute should point to the directory thatcontains this .war file.

For example, if AppName is "vcs" and InstallDir is"/opt/VRTSweb/VERITAS", the agent constructs the path forthe Web application as /opt/VRTSweb/VERITAS/vcs.war.

TimeForOnline integer-scalar The time the Web application takes to start after it is loaded intothe Web server. This parameter is returned as the exit value ofthe online script, which inform VCS of the time it needs to waitbefore calling monitor on the Web application resource. Thisattribute is typically at least five seconds.

Chapter 2, VCS Bundled Agents 53

VRTSWebApp Agent

Type Definitiontype VRTSWebApp (static str ArgList[] = { AppName, InstallDir,TimeForOnline }NameRule = VRTSWebApp + "_Web_Application"str AppNamestr InstallDirint TimeForOnlinestatic int NumThreads = 1

)

Sample ConfigurationVRTSWebApp VCSweb (AppName = "vcs"InstallDir = "/opt/VRTSweb/VERITAS"TimeForOnline = 5)

54 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5

Index

AAgents

Application 6bundled 1defining 1DiskGroup 11ElifNone 13enterprise viiFileNone 14FileOnOff 15FileOnOnly 16IP 17IPMultiNIC 19LVMCombo 22LVMLogicalVolume 24LVMVolumeGroup 25Mount 26MultiNICA 28NFS 33NIC 35NotifierMngr 37Phantom 41Process 43Proxy 45ServiceGroupHB 48Share 51Volume 52VRTSWebApp 53

Application agent 6Applications

managing 6Attributes

modifying 1

BBundled agents

categories of 2defining 1

CCluster Manager (Java Console)

modifying attributes 2Cluster Manager (Web Console)

modifying attributes 2monitoring 53

Commandsexportfs 51fsck 26hares -modify 37ifconfig 17, 18, 19, 29, 30lvchange 24mount 26noautoimport 12stat 26statvfs 26vgchange 25vgdisplay 25vxdg 11vxrecover 52vxvol 52

Configuration filesmain.cf 1, 5, 19, 42modifying 2types.cf 1, 5

DDisk groups

managing 11DiskGroup agent 11Disks

heartbeat 48

EElifNone agent 13Enterprise agents viiEntry points

defining 5

55

FFile systems

mount point 26NFS sharing 51types 26

FileNone agent 14FileOnOff agent 15FileOnOnly agent 16Files

monitoring 13, 14, 15, 16

HHeartbeat

disk regions 48

IIP address

base 28configuring 17, 19

IP agent 17IPMultiNIC agent 19

LLVMCombo agent 22LVMLogicalVolume agent 24LVMVolumeGroup agent 25

Mmain.cf 1, 5, 19, 42Mount agent 26MultiNICA agent 28

NNFS agent 33NIC agent 35Notifier process

managing 37NotifierMngr agent 37

PPhantom agent 41Process agent 43Proxy agent 45

RResource types

relation to agents 1Resources

description of 1relation to entry points 5

SServiceGroupHB agent 48Share agent 51SMTP servers

receiving messages 37SNMP consoles

receiving messages 37

Ttypes.cf 1, 5

VVolume agent 52Volume Manager (VxVM)

managing a disk group 11VRTSWebApp agent 53

WWeb Consoles

monitoring 53

56 VERITAS Cluster Server Bundled Agents Reference Guide, 3.5


Recommended