VERITAS Cluster Server 4.0 Bundled Agents Reference Guide for AIX

7/28/2019 VERITAS Cluster Server 4.0 Bundled Agents Reference Guide for AIX

1/106

August 2004

N10186J

VERITAS Cluster Server 4.0

Bundled Agents Reference Guide

AIX


2/106

ii VERITAS Cluster Server Bundled Agents Reference Guide

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 this manual, including, but not limited to,the implied warranties of merchantability and fitness for a particular purpose. VERITAS SoftwareCorporation shall not be liable for errors contained herein or for incidental or consequential damagesin connection with the furnishing, performance, or use of this manual.

VERITAS Legal Notice

Copyright 1998-2004 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS

Software, the VERITAS logo, VERITAS VERITAS Cluster Server, and all other VERITAS productnames and slogans are trademarks or registered trademarks of VERITAS Software Corporation.VERITAS, the VERITAS Logo, and VERITAS Cluster Server Reg. U.S. Pat. & Tm. Off. Other productnames and/or slogans mentioned herein may be trademarks or registered trademarks of theirrespective companies.

VERITAS Software Corporation350 Ellis StreetMountain View, CA 94043USAPhone 6505278000 Fax 6505272901www.veritas.com

Third-Party Copyrights

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with thatentity. For the purposes of this definition, "control" means ( i) the power, direct or indirect, to cause the direction or management of such entity,whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of suchentity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source,and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiledobject code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright noticethat is included in or attached to the work.

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorialrevisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License,

Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work andDerivative Works thereof.
http://www.veritas.com/http://www.veritas.com/


3/106

VERITAS Cluster Server Bundled Agents Reference Guide iii

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work orDerivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or LegalEntity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal,or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, sourcecode control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improvingthe Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not aContribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor andsubsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform,sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell,

import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarilyinfringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. IfYou institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contributionincorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License forthat Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or withoutmodifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from

the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readablecopy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works,in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form ordocumentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever suchthird-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You mayadd Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work,provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use,reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, anddistribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You tothe Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above,nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding suchContributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, exceptas required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor providesits Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including,without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULARPURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated

with Your exercise of permissions under this License.8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required byapplicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, includingany direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability touse the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all othercommercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge afee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in acceptingsuch obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if Youagree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor byreason of your accepting any such warranty or additional liability.


4/106

iv VERITAS Cluster Server Bundled Agents Reference Guide

Data Encryption Standard (DES)

Support for data encryption in VCS is based on the MIT Data Encryption Standard (DES) under the following copyright:

Copyright 1990 Dennis Ferguson. All rights reserved.Commercial use is permitted only if products that are derived from or include this software are made available for purchase and/or use inCanada. Otherwise, redistribution and use in source and binary forms are permitted.

Copyright 1985, 1986, 1987, 1988, 1990 by the Massachusetts Institute of Technology. All rights reserved.

Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibilityof any person or organization contemplating export to obtain such a license before exporting.

WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and withoutfee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission noticeappear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the softwarewithout specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided as

is without express or implied warranty.

SNMP Software

SNMP support in VCS is based on CMU SNMP v2 under the following copyright:

Copyright 1989, 1991, 1992 by Carnegie Mellon University

All Rights Reserved

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, providedthat the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supportingdocumentation, and that the name of CMU not be used in advertising or publicity pertaining to distribution of the software without specific,written prior permission.

CMU DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CMU BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIALDAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OFCONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCEOF THIS SOFTWARE.


5/106

v

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

VCS Enterprise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

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

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

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

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

Categories of Bundled Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Application Control Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

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

Global Cluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Networking Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

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

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

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

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

State Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Required Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


6/106

vi VERITAS Cluster Server Bundled Agents Reference Guide

Optional Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

Application Agent Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

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

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

State Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Required Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Optional Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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

Info Entry Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

DNS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Required Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Online Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Monitor Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

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

Sample Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ElifNone Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Entry Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18


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



7/106

Contents vii

FileNone Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Entry Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Required Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19


FileOnOff Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


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


FileOnOnly Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


IP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22



Optional Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

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

Sample Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

IPMultiNIC Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25



8/106

viii VERITAS Cluster Server Bundled Agents Reference Guide



Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Sample Configuration: IPMultiNIC and MultiNICA . . . . . . . . . . . . . . . . . . . . . . . . 27

IPMultiNICB Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28



Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Sample Configuration: MultiNICB and IPMultiNICB . . . . . . . . . . . . . . . . . . . . . . . . 30

LVMVG Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31




Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


Notes on the LVMVG Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Mount Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38




Info Entry Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40


Listing File Systems in /etc/filesystems on AIX 5.1c . . . . . . . . . . . . . . . . . . . . . . . . 41


9/106

Contents ix

MultiNICA Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43



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

Sample Configuration: MultiNICA and IPMultiNIC . . . . . . . . . . . . . . . . . . . . . . . . . 45

MultiNICB Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


Required Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Optional Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

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

Checklist for Using MultiNICB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Advantages of MultiNICB and IPMultiNICB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Limitations of MultiNICB and IPMultiNICB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

How MultiNICB Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Sample Configuration: MultiNICB and IPMultiNICB . . . . . . . . . . . . . . . . . . . . . . . . 54

NFS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55



Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56


NIC Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


10/106

x VERITAS Cluster Server Bundled Agents Reference Guide




Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


NotifierMngr Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60




Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Phantom Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65


Process Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67




Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68


Proxy Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70



11/106

Contents xi


Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71


ServiceGroupHB Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73


Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Share Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77




Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78


Volume Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


VRTSWebApp Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Entry Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80


Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81


Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


12/106

xii VERITAS Cluster Server Bundled Agents Reference Guide


13/106

xiii

Preface

This guide provides reference information for the VCS agents bundled with VERITAS

Cluster Server (VCS) software on the AIX operating system. The guide providesinformation on configuring and using bundled agents.

How This Guide Is Organized

Chapter 1, Introduction on page 1 introduces the bundled agents.

Chapter 2, VCS Bundled Agents on page 5 describes each of the bundled agents.


14/106

Conventions

xiv VERITAS Cluster Server Bundled Agents Reference Guide

Conventions

Convention Usage Example

monospace Used for path names, commands,output, directory and file names,functions, and parameters.

Read tunables from the/etc/vx/tunefstab file.

See the ls(1) manual page for moreinformation.

monospace(bold)

Indicates user input. # ls pubsC:\> dir pubs

italic Identifies book titles, new terms,emphasized text, and variablesreplaced with a name or value.

See the Users Guide for details.

The variable system_name indicates thesystem on which to enter the command.

bold Depicts GUI objects, such as fields,

list boxes, menu selections, etc. Alsodepicts GUI commands.

Enter your password in the Password

field.Press Return.

blue text Indicates hypertext links. See Getting Help on page xv.

# Unix superuser prompt (all shells). # cp /pubs/4.0/user_book/release_mgnt/4.0/archive


15/106

Preface xv

Getting Help

Getting Help

For technical assistance, visit http://support.veritas.com and select phone or emailsupport. This site also provides access to resources such as TechNotes, product alerts,software downloads, hardware compatibility lists, and our customer email notificationservice. Use the Knowledge Base Search feature to access additional product information,including current and past releases of VERITAS documentation.

Additional Resources

For license information, software updates and sales contacts, visit

https://my.veritas.com/productcenter/ContactVeritas.jsp. For information onpurchasing product documentation, visit http://webstore.veritas.com.

Documentation Feedback

Your feedback on product documentation is important to us. Send suggestions forimprovements and reports on errors or omissions to [email protected] title and part number of the document (located in the lower left corner of the titlepage), and chapter and section titles of the text on which you are reporting. Our goal is toensure customer satisfaction by providing effective, quality documentation. For assistancewith topics other than documentation, visit http://support.veritas.com.

VCS Enterprise Agents

VCS enterprise agents are not included with the VCS software, but are sold separately.Contact your VERITAS sales representative for details on these agents or additionalagents under development:

DB2 UDB

NetBackup

Oracle
http://support.veritas.com/https://my.veritas.com/productcenter/ContactVeritas.jsphttp://webstore.veritas.com/mailto:[email protected]?subject=Title:%20VCS%20Bundled%20Agents%20Reference%20Guide%20for%20AIX%20%20Part%20Number:%20N10186Jhttp://support.veritas.com/http://support.veritas.com/mailto:[email protected]?subject=Title:%20VCS%20Bundled%20Agents%20Reference%20Guide%20for%20AIX%20%20Part%20Number:%20N10186Jhttp://webstore.veritas.com/https://my.veritas.com/productcenter/ContactVeritas.jsphttp://support.veritas.com/


16/106

VCS Enterprise Agents

xvi VERITAS Cluster Server Bundled Agents Reference Guide


17/106

1

Introduction 1Bundled agents are VCS processes that manage resources of predefined resource types

according 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 4.0 Users Guide for general information on VCSagents.

Resources and Their Attributes

Resources 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 is

designed to control the resource. The VCS configuration file,main.cf, contains thevalues for the resource attributes and has an include directive to the types.cf file.

An attributes 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, and youset the attribute Address to monitor the specific IP address.


18/106

Entry Points

2 VERITAS Cluster Server Bundled Agents Reference Guide

Entry Points

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 many agents and is calledautomatically by the framework when all ongoing actions associated with a resource must

be terminated and the resource must be taken offline (perhaps forcibly).

Refer to the VERITAS Cluster Server Agent Developers Guide for more information on entrypoints and the VCS agent framework. Refer to the VERITAS Cluster Server Users Guide formore information on VCS attributes.

Modifying Agents and Their Resources

Use 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 4.0 Users Guide for instructions on how to completethese tasks.

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

Categories of Bundled Agents

VCS enables you to use bundled agents for networking, basic storage, application control,

and VCS infrastructure and support functions:

Application Control Agents

Application Agent on page 6

Process Agent on page 67

Basic Storage Agents

DiskGroup Agent on page 11

LVMVG Agent on page 31

Mount Agent on page 38

NFS Agent on page 55

Share Agent on page 77

Volume Agent on page 79


19/106

Chapter 1, Introduction


3

Global Cluster Support

DNS Agent on page 14

Wide Area Heartbeat

While global clusters require the Wide Area Heartbeat agent, it is not a standard VCSagent for monitoring VCS resources. It is documented in the VCS Users Guide sectionon global clusters.

Networking Agents

IP Agent on page 22

IPMultiNIC Agent on page 25

IPMultiNICB Agent on page 28

MultiNICA Agent on page 43

MultiNICB Agent on page 47

NIC Agent on page 57

VCS Infrastructure and Support Agents

ElifNone Agent on page 18

FileNone Agent on page 19

FileOnOff Agent on page 20

FileOnOnly Agent on page 21

NotifierMngr Agent on page 60

Phantom Agent on page 65

Proxy Agent on page 70

ServiceGroupHB Agent on page 73

VRTSWebApp Agent on page 80


20/106




21/106

5

VCS Bundled Agents 2This chapter provides information on the VCS bundled agents. Described for each

bundled agent are its resource types, entry points, state definitions, and modifiableattributes. The tables associated with bundled agents indicate required and optionalattributes. Included are its resource type, defined in the types.cf file, and a sampleconfiguration in themain.cf file.


22/106

Application Agent


Application Agent

Description

Brings applications online, takes them offline, and monitors their status. Enables you tospecify different executables for the online, offline, and monitor routines. (An applicationhas an executable to start it and an executable to stop it.) The executables must existlocally on each node. By default, an application runs in the context of root. Specify theuser name to run an application in a user context.

The agent starts and stops the application with user-specified programs. You can monitorthe 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

OnlineRuns the StartProgram with the specified parameters in the specified usercontext.

OfflineRuns the StopProgram with the specified parameters in the specified user

context. MonitorIf MonitorProgram is specified, the agent executes the user-defined

MonitorProgram in the user-specified context. If PidFiles is specified, the routineverifies that the process ID found in each listed file is running. If MonitorProcesses isspecified, the routine verifies that each listed process is running in the user-specifiedcontext.

MonitorProgram must return ONLINE to employ any other monitoring method. Any

one, two, or three of these attributes can be used to monitor the application. If any oneprocess specified in either PidFiles or MonitorProcesses is determined not to berunning, the monitor returns OFFLINE.

CleanKills processes specified in PidFiles or MonitorProcesses. Ensures that onlythose processes (specified in MonitorProcesses) running with the user ID specified inthe User attribute are killed. If the CleanProgram is defined, the agent executes theCleanProgram.


23/106

Chapter 2, VCS Bundled Agents

Application Agent

7

State Definitions

ONLINEIndicates that all processes specified in PidFiles and MonitorProcesses are

running and that the MonitorProgram returns ONLINE.

OFFLINEIndicates that at least one process specified in PidFiles or MonitorProcessesis not running, or that the MonitorProgram returns OFFLINE.

UNKNOWNIndicates that the applications state is indeterminable.

Required Attributes

Required Attributes Type and

Dimension

Definition

StartProgram string-scalar The executable, created locally on each node, whichstarts the application. Specify the complete path of theexecutable. Command-line arguments (if applicable)

follow the name of the executable, separated byspaces.

StopProgram string-scalar The executable, created locally on each node, whichstops the application. Specify the complete path of theexecutable. Command-line arguments (if applicable)follow the name of the executable, separated byspaces.

At least one of thefollowing attributes:

MonitorProcesses

MonitorProgram

PidFiles

See descriptionsunder OptionalAttributes onpage 8.

See descriptions Optional Attributes on page 8.

A li i A


24/106

Application Agent


Optional Attributes

OptionalAttributes

Type andDimension

Definition

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

MonitorProcesses string-vector A list of processes to be monitored and cleaned. Eachprocess name is the name of an executable. Qualify theexecutable name with its complete path if the path is usedto start the executable.

The process name must be the full command lineargument displayed by the ps -u user -o args |

more command for the process.

MonitorProgram string-scalar The executable, created locally on each node, which

monitors the application. Specify the complete path of theexecutable. Command-line arguments (if applicable)follow the name of the executable, separated by spaces.

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

PidFiles string-vector A list of PID files that contain the process ID of theprocesses to be monitored and cleaned. These files areapplication-generated files. Each PID file contains one PIDthat is 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 agentsmonitor script may return an incorrect result. If thisoccurs, increase the ToleranceLimit in the resource

definition.

User string-scalar The user whose id is used to run StartProgram,StopProgram, MonitorProgram, and CleanProgram. Theprocesses specified in the MonitorProcesses list must runin the context of the specified user. Monitor checks theprocesses to make sure they run in this context.

Default is "root".

A li ti A t


25/106


Application Agent

9

Type Definition

type Application (

static str ArgList[] = { User, StartProgram, StopProgram,CleanProgram, MonitorProgram, PidFiles, MonitorProcesses }

str Userstr StartProgramstr StopProgramstr CleanProgramstr MonitorProgramstr PidFiles[]

str MonitorProcesses[])

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, so the root user is used. The executablesamba isused to start and stop the application, with start and stop as the command-linearguments, respectively. The executable sambaMonitor monitors the application anduses all as its command-line argument. In addition, the processes smbd and nmbd aremonitored.

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" })

Application Agent


26/106

Application Agent


Application Agent Error Messages

Message Tag Description

File${VCS_HOME}/bin/Application/functions not found.

A Check if file${VCS_HOME}/bin/Application/functions exists and has properpermissions.

User user does not exist. B Check if the specified user exists on the localsystems.

Start Program does not exist oris not executable.

B Check if the specified StartProgram exists andthe user specified permission to execute it.

No Start Program specified. B No Start Program is specified in the resourcedefinition and hence cannot bring theresource online.

None of the parameters(MonitorProgram, PidFiles,MonitorProcesses) are specifiedto monitor the application.

B Nothing is specified to monitor the resource.Specify at least one parameter to monitor theresource.

Monitor Program does not existor is not executable.

B Check if the specified MonitorProgram existsand the specified user has permission toexecute it.

Stop Program does not exist oris not executable. B Check if the specified StopProgram exists andthe specified user has permission to executeit.

No Stop Program specified. B No Stop Program is specified in the resourcedefinition and hence cannot take the resourceoffline.

Clean Program does not exist or

is not executable.

B Check if the specified CleanProgram exists

and the specified user has permission toexecute it.

DiskGroup Agent


27/106


DiskGroup Agent

11

DiskGroup Agent

Description

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

Entry Points

OnlineImports the disk group using the vxdg command.

OfflineDeports the disk group using the vxdg command.

MonitorDetermines if the disk group is online or offline using the vxdg command.If the disk group was imported with noautoimport=off, the group to which thedisk group belongs is taken offline (assuming the group is not frozen).

If the monitor hangs, no attempt takes place to take the disk group offline. The

dependent groups can be taken offline (provided the disk group is functional) and theresnotoff trigger can be called.

CleanSee Entry Points on page 2 for more information on the Clean entry point.

InfoThe DiskGroup info entry point gets information from the Volume Managerand displays the type and free size for the DiskGroup resource.

State Definitions

ONLINEIndicates that the disk group is imported.

OFFLINEIndicates that the disk group is not imported.

UNKNOWNIndicates that a problem exists either with the configuration or the abilityto determine the status of the resource.

Required Attribute

Required Attribute Type and

Dimension

Definition

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

Volume Manager, for example: diskgroup1.

DiskGroup Agent


28/106

p g


Optional Attributes

Setting the noautoimport Flag for a Disk Group

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

Note Be aware that when you enable a disk group configured as a DiskGroup resourcethat does not have the noautoimport flag set to true, VCS forcibly deports the diskgroup and reimports it with the noautoimport flag set to true. This may disruptapplications running on the disk group.

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

#vxprint -ldisk_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:

To deport the disk group, enter:

#vxdg deportdisk_group

To import the disk group, specifying the noautoimport flag be set to true to ensure thedisk group is not automatically imported, enter:

#vxdg -t importdisk_group

Optional Attributes Type andDimension

Definition

StartVolumes string-scalar If value is 1, the DiskGroup online script starts allvolumes belonging to that disk group after importingthe group.

Default is 1.

StopVolumes string-scalar If value is 1, the DiskGroup offline script stops allvolumes belonging to that disk group beforedeporting the group.

Default is 1.

DiskGroup Agent


29/106


p g

13

Info Entry Point

The following steps are necessary to initiate the info entry point by setting the InfoInterval

timing to a value greater than 0, for example:

# haconf -makerw# hatype -modify DiskGroup InfoInterval 60

In this case, the info entry point executes every 60 seconds. The command to retrieveinformation about the DiskType and FreeSize of the DiskGroup resource is:

# hares -value diskgroupres ResourceInfo

Output includes the following information:

DiskType slicedFreeSize 35354136

Type Definition

type DiskGroup (

static int OnlineRetryLimit = 1static str ArgList[] = { DiskGroup, StartVolumes, StopVolumes,

MonitorOnly, MonitorReservation,tempUseFence}

str DiskGroupstr StartVolumes = 1str StopVolumes = 1static int NumThreads = 1

boolean MonitorReservation = 0temp str tempUseFence = "INVALID"

)

Sample Configuration

DiskGroup dg1 (

DiskGroup = testdg_1)

DNS Agent


30/106


DNS Agent

If an application that is required to be available across the wide area is a server for an IP

address, and if this application is failed over to another subnet, the IP address from thedowned host cannot be effectively moved. A better solution is to update the canonicalname mapping in the DNS name server with the hostname of the system where theapplication is now online.

Description

Updates the canonical name mapping in the domain name server when failing overapplications across subnets (wide-area failover).

Entry Points

MonitorIf the online lock file exists, the monitor queries the name servers for theCNAME record for the Alias and reports back ONLINE if the response from at least one

of the name servers contains the same canonical name associated with the alias asspecified in the HostName attribute. If not, the monitor reports resource OFFLINE.

OnlineQueries the authoritative name server of the domain for CNAME records.

OfflineRemoves the online lock file created by the online function.

OpenRemoves the online lock file if the online lock file exists, and the CNAME recordon the name server does not contain the expected alias/canonical name mapping.

CleanRemoves the online lock file, if present.

DNS Agent


31/106

Chapter 2, VCS Bundled Agents 15

Required Attributes

Online Query

If the canonical name in the response CNAME record does not match the one specified forthe resource, online tries to update the CNAME record on all authoritative master nameservers in its domain (those master name servers that can be reached and on which it hasupdate permission). If the DNS update was successful or was not necessary on at least oneof the name servers, the online function creates an online lock file. The monitor functionchecks for the existence of this file. The online lock file is not created if no name server inthe domain could be updated.

If the PrimaryMasters attribute is specified, Online tries to update the name serversspecified in the PrimaryMasters attribute since the primary master is a stealth serverwhich is not listed in the zone's NS record.

In BIND 8, the primary master name server on receiving an update sends notification(NOTIFY) to all its slave servers asking them to pick up the update.

Required Attributes Type andDimension

Description

Domain string-scalar String representing the domain name, for example:veritas.com.

Alias string-scalar String representing the alias to the canonical name,for example: www is the alias to the canonical namemtv.veritas.com in the earlier example.

HostName string-scalar String representing canonical name of a system/IPaddress, for example: mtv.veritas.com, hro.veritas.com.

TTL integer-scalar Non-zero integer value representing the "Time ToLive" value, in seconds, for the DNS entries in thezone being updated. Default is 1 day.

StealthMasters string-keylist The list of primary master name servers in the

domain. This is optional if the primary master nameserver is listed in the zones NS record. If the primarymaster name server is a stealth server, the attributemust be defined.

Note A stealth server is a name server that isauthoritative for a zone, but is not listed in thatzones NS records.

DNS Agent


32/106


Monitor Scenarios

Note The DNS agent supports BIND version 8 and above.

Type Definition

type DNS (static str ArgList[] = { Domain, Alias, HostName, TTL,

StealthMasters}str Domainstr Aliasstr HostNameint TTL = 86400 // i.e: 1 daystr StealthMasters[]

)

Sample Scenario

As an example, consider the VERITAS corporate web server. A person using a webbrowser specifies the URL www.veritas.com to view the VERITAS web page (wherewww.veritas.com maps to the canonical name mtv.veritas.com, which is a host inMountain View running the web server). The browser, in turn, retrieves the IP address forthe web server by querying the domain name servers. If the web server forwww.veritas.com is failed over from Mountain View to Heathrow, the domain name

servers need to be updated with the new canonical name mapping so that clients (webbrowsers) are directed to Heathrow instead of Mountain View. In case of a failover, theDNS agent should update the name server to change the mapping of www.veritas.com,from mtv.veritas.com to the canonical name of the standby machine in Heathrow (e.g.hro.veritas.com).

Online lock file exists Expected CNAME RR Monitor returns

NO N/A OFFLINE

YES NO OFFLINE

YES YES ONLINE

DNS Agent


33/106



Heres a sample configuration for DNS.

DNS www (Domain = "example.com"Alias = wwwHostname = wwwvirtual1

Bringing the "www" resource online updates the authoritative nameservers for domain"example.com" with the following CNAME record:

wwwCNAMEwwwvirtual1

Thus all DNS lookups for www.example.com are resolved to wwwvirtual1.example.com.

ElifNone Agent


34/106


ElifNone Agent

Description

Monitors a file.

Entry Point

MonitorChecks if the specified file exists. If it does, the agent reports as offline. If itdoes not, the agent reports as online.

Required Attribute

Type Definition

type ElifNone (

static str ArgList[] = { PathName }static int OfflineMonitorInterval = 60static str Operations = Nonestr PathName

)


ElifNOne tmp_file01 (PathName = "/tmp/file01"

)


Dimension

Definition

PathName string-scalar Specifies the complete pathname. Starts with the slash(/) that precedes the file name.

FileNone Agent


35/106


FileNone Agent

Description

Monitors a file.

Entry Point

MonitorChecks if the specified file exists. If it does, the agent reports as online. If itdoes not, the agent reports as offline.

Required Attribute

Type Definition

type FileNone (

static int AutoStart = 1static str ArgList[] = { PathName }static int OfflineMonitorInterval = 60static str Operations = Nonestr PathName

)

Sample ConfigurationFileNone tmp_file01 (PathName = "/tmp/file01")


Dimension

Definition


FileOnOff Agent


36/106


FileOnOff Agent

Description

Creates, removes, and monitors files.

Entry Points

OnlineCreates an empty file with the specified name (if one does not already exist).

OfflineRemoves the specified file.



Required Attribute

Type Definition

type FileOnOff (str PathNamestatic str ArgList[] = { PathName }

)


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


Dimension

Definition


FileOnOnly Agent


37/106


FileOnOnly Agent

Description

Creates and monitors files.

Entry Points

OnlineCreates an empty file with the specified name (if one already does not exist).



Required Attribute

Type Definition

type FileOnOnly (static str ArgList[] = { PathName }static str Operations = OnOnlystr PathName

)


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


Dimension

Definition


IP Agent


38/106


IP Agent

Description

Manages the configuration of a virtual IP address and its subnet mask on an interface. Thevirtual IP address must not be one currently in use.

Use the IP Agent to support EtherChannel configurations. The virtual interfaceconfigured through EtherChannel should be used for the "Device" parameter. The NICagent should also be used to monitor the status of the EtherChannel virtual interface.

Entry Points

OnlineChecks if the IP address is in use by another system. Uses ifconfig to setthe IP address on a unique alias on the interface.

OfflineBrings down the IP address associated with the specified interface.

MonitorMonitors the interface to test if the IP address associated with the interfaceis in the UP state.

State Definitions

ONLINEIndicates that the device is up and the specified IP address is assigned to thedevice.

OFFLINEIndicates that the device is down or the specified IP address is not assignedto the device.

UNKNOWNIndicates that the device name or the IP address is not specified in theconfiguration file (main.cf).

IP Agent


39/106


Required Attributes

Optional Attribute

Type Definition

type IP (str Devicestr Addressstr NetMaskstr Optionsstatic str ArgList[] = { Device, Address, NetMask, Options }

)

Required Attributes Type andDimension

Definition

Address string-scalar Virtual IP address associated with the interface. Thevirtual IP address is different from the base andadministrative IP addresses of the interface.

For example: "172.29.9.24".

Device string-scalar Name of the NIC device associated with the IP

address, for example: en0.

Use ifconfig -a to display a list of NICs that areup and the IP addresses assigned to each NIC.

NetMask string-scalar The subnet mask associated with the IP address. Thevalue of NetMask may be specified in decimal (base10) or hexadecimal (base 16).

For example: "255.255.255.0".

Optional Attribute Type and

Dimension

Definition

Options string-scalar Options for the ifconfig command.For example:metric n mtu m.

IP Agent

S C


40/106


Sample Configurations

Sample 1: NetMask in decimal (base 10)

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

Sample 2: NetMask in hexadecimal (base 16)

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

IPMultiNIC Agent

IPM ltiNIC A t


41/106


IPMultiNIC Agent

Description

Manages and monitors a virtual (logical) IP address configured as an alias on oneinterface of a MultiNICA resource. This agent monitors the logical IP address. If theinterface is faulted, the IPMultiNIC agent works with the MultiNICA resource to fail overto a backup interface. If multiple service groups have IPMultiNICs associated with thesame MultiNICA resource, only one group has the MultiNICA resource. The other groupshave Proxy resources pointing to it.

Entry Points

OnlineConfigures a virtual IP address on one interface of the MultiNICA resource.

OfflineRemoves a virtual IP address from one interface of the MultiNICA resource.

MonitorChecks if the virtual IP address is configured on one interface of theMultiNICA resource.

State Definitions

ONLINEIndicates that the specified IP address is assigned to the device.

OFFLINEIndicates that the specified IP address is not assigned to the device.

UNKNOWNIndicates that the IP address is not specified in the configuration file(main.cf).

IPMultiNIC Agent

Required Attributes


42/106


Required Attributes

Optional Attribute

Type Definition

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

NetMask, Options,"MultiNICAResName:Probed",MultiNICAResName }

str Addressstr NetMaskstr Optionsstr MultiNICAResName

)

Required Attributes Type andDimension Definition

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

For example: "172.29.9.100".

MultiNICAResName string-scalar Name of associated MultiNICA resource thatdetermines the active NIC.

For example: MultiNICA_grp1.

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

Optional Attribute Type and

Dimension

Definition

Options string-scalar The ifconfig options for the virtual IP address.

For example:mtu m.

IPMultiNIC Agent

Sample Configuration: IPMultiNIC and MultiNICA


43/106


Sample Configuration: IPMultiNIC and MultiNICA

For more information on this example, refer to Sample Configuration: MultiNICA and

IPMultiNIC on page 45.group grp1 (SystemList = { sysa, sysb }AutoStartList = { sysa })MultiNICA mnic ([email protected]={en0="10.128.8.42", en1="10.128.8.42" }[email protected]={en0="10.128.8.43", en1="10.128.8.43" }

NetMask = "255.255.255.0"Gateway = "10.128.1.1"BroadcastAddr = "10.128.8.255")

IPMultiNIC ip1 (Address="10.128.10.14"NetMask = "255.255.255.0"

MultiNICAResName = mnic)

ip1 requires mnic

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

)IPMultiNIC ip2 (Address="10.128.9.4"NetMask = "255.255.255.0"MultiNICAResName = mnicOptions = "mtu m")

Proxy proxy (

TargetResName = mnic)

ip2 requires proxy

IPMultiNICB Agent

IPMultiNICB Agent


44/106


IPMultiNICB Agent

DescriptionMonitors a virtual (logical) IP address that is configured as an alias on one of the interfacesof a MultiNICB resource. The IPMultiNICB resource is configured as a failover servicegroup that is dependent on the MultiNICB resource. If the physical interface where thelogical IP address is configured is marked DOWN by the MultiNICB agent, the resource isreported OFFLINE. If multiple service groups have IPMultiNICB resources associatedwith the same MultiNICB resource, only one group has the MultiNICB resource. The

other service groups have a Proxy resource pointing to that MultiNICB resource.The minimal configuration for this agent consists of the failover IP address, the subnetmask, and the name of the MultiNICB resource that it depends on. Refer to SampleConfiguration: MultiNICB and IPMultiNICB on page 30 for an example of this type ofconfiguration.

The haipswitch Utility

You can use the "/opt/VRTSvcs/bin/IPMultiNICB/haipswitch utility to switch IPaddresses between MultiNICB interfaces on the same system. Running the utility with the-h flag gives an example of usage.

EtherChannel Support

Do not use IPMultiNICB with the EtherChannel. Instead, use the NIC and IP agents.

Entry Points

OpenData structures necessary for monitoring the network interfaces are created.

OnlineIP address is brought online on the NIC recommended by the MultiNICBresource.

MonitorChecks the existence of the IP address. If the address exists, queries theMultiNICB resource for status. The address is failed over to another NIC if necessary.

OfflineIP address is de-configured.

CleanIP address is de-configured.

CloseData structures used by the monitor entry point are freed.

Attr_ChangedUpdates the data structures used for monitoring the NICs.

IPMultiNICB Agent

State Definitions


45/106


State Definitions

ONLINEIndicates the IP address is available on a NIC defined as good by the

MultiNICB resource. OFFLINEThe IP address is not available.

FAULTEDThe IP address could not be brought online, usually due to all NICs in theMultiNICB resource faulting.

UNKNOWNIndicates an unrecoverable error condition in the monitor entry point.

Required Attributes

Required Attributes Type and

Dimension

Definition

Address string Defines the dotted decimal failover IP address.

This IP address must be different than the base or test

IP addresses in the MultiNICB resource.Note The IPMultiNICB agent automatically assigns

the failover IP address. Do not configure this IPaddress before the IPMultiNICB agent goes online.If the IP address is already configured, the agentwill return an error.

NetMask string Defines the subnet mask for the failover IP address.

MultiNICBResName string Contains the name of the MultiNICB resource that theIPMultiNICB resource depends on.

IPMultiNICB Agent

Type Definition


46/106


Type Definition

type IPMultiNICB (

static int MonitorTimeout = 120static int OfflineMonitorInterval = 60static int MonitorInterval = 10static str ArgList[] = { Address, NetMask, MultiNICBResName,"MultiNICBResName:Probed" }str Addressstr NetMaskstr MultiNICBResName

)

Sample Configuration: MultiNICB and IPMultiNICB

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

MultiNICB MNICB_grp1 ([email protected] = { en0 = "10.128.8.42", en1 = "10.128.8.43" }[email protected] = { en0 = "10.128.8.44", en1 = "10.128.8.45" }NetworkHosts = "10.128.8.10 10.128.8.45"LinkTestRatio = 1)

IPMultiNICB ip1 (Address = "10.128.10.14"

Netmask = "255.255.255.0"MultiNICBResName = MNICB_grp1)

ip1 requires MNICB_grp1

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

)IPMultiNICB ip2 (Address = "10.128.10.15"Netmask = "255.255.255.0"MultiNICBResName = MNICB_grp1)

Proxy MNICB_proxy (TargetResName = MNICB_grp1

)ip2 requires MNICB_proxy

LVMVG Agent

LVMVG Agent


47/106


LVMVG Agent

Description

Activates, deactivates, and monitors a Logical Volume Manager (LVM) volume group.The LVMVG agent ensures the ODM is in sync with any changes to the volume groupsince it was last imported on the system. Refer to Notes on the LVMVG Agent onpage 34 for important information on this agent.

Entry Points

OnlineActivates the volume group. The Online entry point expects that the volumegroup is already imported on the system. If the volume group had been modified on asystem where it was previously active, the Online entry point detects this. It thensyncs up the ODM on the system where you want to bring the volume group resourceonline.

Offline

Deactivates the volume group. MonitorDetermines the volume groups state (activated or deactivated) and

availability for read/write operations.


State Definitions

ONLINEIndicates that the volume group is activated.

OFFLINEIndicates that the volume group is deactivated.

LVMVG Agent

Required Attributes


48/106


q

Optional Attributes

Required Attributes Type andDimension Definition

MajorNumber integer-scalar Integer that represents the major number of thevolume group. To ensure NFS functions properly,assign the same major number to the volume groupon each system in the cluster.

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

For example: testvg1.

Optional Attributes Type and

Dimension

Definition

OwnerName string-scalar Attribute used to specify the volume owner s name.

Default is root.

If set, the owners name is applied to the volumegroup and all of its logical volumes.

GroupName string-scalar Attribute used to specify the volumes group.

Default is system.

If set, the groupss name is applied to the volumegroup and all of its logical volumes.

Mode string-scalar Attribute used to specify permissions for a volumegroup and its logical volumes.

Default is 640.

If set, these permissions are applied to the volumegroup and all of its logical volumes.

ImportvgOpt string-scalar Attribute used to specify options for the importvgcommand.

Default is n. This option indicates the volume groupis not automatically activated when imported.

VaryonvgOpt string-scalar Attribute used to specify options for the varyonvgcommand. By default, this string is empty.

LVMVG Agent

Optional Attributes Type and Definition


49/106


Type Definition

type LVMVG (

static int NumThreads = 1static str ArgList[] = { VolumeGroup, MajorNumber, OwnerName,

GroupName, Mode, ImportvgOpt,VaryonvyOpt, SyncODM }

str VolumeGroupint MajorNumberstr OwnerNamestr GroupName

str Modestr ImportvgOpt = nstr VaryonvgOptint SyncODM = 1

)

SyncODM integer-scalar Integer that specifies whether or not the agentensures the ODM is in sync with any changes tothe volume group.

If set to 1, the agent ensures the ODM is in syncwith the changes to the volume group (if the volumegroup was modified on another system in the cluster).The sync operation occurs on the system where theagent brings the volume group online.

If set to 0, the changes to the volume group areindependent of the ODM.

Default is 1.

Optional Attributes Type and

Dimension

Definition

LVMVG Agent



50/106


system sysA

system sysB

system sysC

group lvmgroup (SystemList = { sysA, sysB }AutoStartList = { sysA }

LVMVG lvmvg_vg1 (VolumeGroup = vg1MajorNumber =

Date post:	03-Apr-2018
Category:	Documents
Author:	nikhil-shet
View:	235 times
Download:	0 times

VERITAS Cluster Server 4.0 Bundled Agents Reference Guide for AIX

Documents

Veritas InfoScale Foundation, Availability, Storage … InfoScale Foundation, Availability, Storage and Enterprise Solutions 7.0, 7.0.1 (AIX, Linux, Solaris), and DMP for VMware 7.0

Veritas High Availability Agent for Oracle Installation ... · N18473J Veritas™ High Availability Agent for Oracle Installation and Configuration Guide AIX 5.0

Veritas Cluster Server 6vox.veritas.com/legacyfs/online/veritasdata/SM B12.pdf · AIX WPAR –Application agents •Sybase –IMF updates •Agent Framework update for Custom Agent

VERITAS Confidential Copyright © 2004 VERITAS Software Corporation. All Rights Reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS.

Veritas Storage Foundation and High Availability … Storage Foundation and High Availability Solutions Release Notes AIX 5.1 Rolling Patch 1

Veritas ClusterServerAgent for Sybase Installation and Configuration Guide · · 2015-09-03for Sybase Installation and Configuration Guide AIX 6.0 ... Product version: VCS 6.0 Document

Veritas™ Cluster Server Bundled Agents Reference Guide · Veritas™ Cluster Server Bundled Agents Reference Guide ... Chapter 1 Introducing VCS bundled agents ... 155 NetApp SnapDrive

Veritas ClusterServer6.0.1 Release Notes - AIX · PDF fileRelease Notes - AIX 6.0.1 August2015. Veritas™ClusterServerReleaseNotes Thesoftwaredescribedinthisbookisfurnishedunderalicenseagreementandmaybeused

Veritas InfoScale 7.3 Getting Started Guide - AIX

Veritas InfoScale 7.0 Release Notes - AIX · Ifyouhaveashared(system)WPARconfigured,whenyouinstall, upgrade,oruninstallanySymantecproduct,thefilesetsin theWPARarenotsynchronizedcorrespondingly

Veritas File System Administrator's Guide AIX · Combining mount command options ... Veritas Volume Manager maximum I/O size ... Setting up Veritas Extension for Oracle Disk Manager

Aix-en-Provence Aix Region GB AIX EN PROVENCEat.media.france.fr/sites/default/files/document/press_kit/Presskit Aix... · Aix-en-Provence Aix Region GB Press contact Geraldine Fridrici

Veritas File System Administrator's Guide AIX - Symantecstatic-sort.symanteccloud.com/public/documents/sf/5.1/aix/pdf/vxfs... · Maintenance agreement resources If you want to contact

Oracle 9i RAC Deployment on AIX Using VERITAS Storage ...eval.symantec.com/mktginfo/enterprise/white_papers/IBM_Paper_on... · Oracle 9i RAC Deployment on AIX Using VERITAS Storage

VERITAS Database Edition 1.0.2 for DB2 on AIX Release Notes

Veritas Storage Foundation Tuning Guide - Symantecstatic-sort.symanteccloud.com/.../aix/.../pdf/sf_tuning_51sp1_unix.pdf · Veritas Storage Foundation Tuning Guide AIX, ... Recent

Veritas InfoScale 7.2 Getting Started Guide - AIX

VERITAS Cluster Server 3.5 Bundled Agents - SORT Home · PDF fileVolume Agent ... Cluster Manager (Web Console), or the VCS command line to dynamically modify ... 6 VERITAS Cluster