vcs_ig

7/27/2019 vcs_ig

1/135

7/27/2019 vcs_ig

2/135

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 and slogansare trademarks of VERITAS Software Corporation in the USA and/or other countries.Other product names and/or slogans mentioned herein may be trademarks or registeredtrademarks or their respective companies.

VERITAS Software Corporation.350 Ellis St.Mountain View, CA 94043Phone 650.527.8000Fax 650.527.2908http://www.veritas.com
http://www.veritas.com/http://www.veritas.com/

7/27/2019 vcs_ig

3/135

iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

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

VCS Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Multiple Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

LLT and GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Two Types of Channels: Network and Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Preexisting Network Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5VCS Seeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Preparing to Install VCS 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preparation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Downloading Solaris Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Hardware Requirements for a VCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Supported Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Setting Up the Private Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Setting Up Shared Storage: SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Setting Up Shared Storage: Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Disabling the Abort Sequence on SPARC Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Setting the Path Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

7/27/2019 vcs_ig

4/135

iv VERITAS Cluster Server 3.5 Installation Guide

Enabling Communication Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Preparing NFS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Major and Minor Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Checking Major and Minor Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Obtaining License Keys for VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Using the VERITAS vLicenseTM Web Site to Obtain a License Key . . . . . . . . . . 16

Faxing the License Key Request Form to Obtain a License Key . . . . . . . . . . . . . 16

Preparing Cluster Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Required Cluster Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Virtual IP Address for the Cluster Manager (Web Console) . . . . . . . . . . . . . . . . 17

Information for Configuring SMTP Notification . . . . . . . . . . . . . . . . . . . . . . . . . 18

Information for Configuring SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3. Using the VCS Installation Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

VCS Installation Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

The installvcs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Install Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Example System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Using installvcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Starting the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Verifying System Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Licensing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Checking Java Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Starting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuring the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring SMTP Email Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring SNMP Trap Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Configuring VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7/27/2019 vcs_ig

5/135

Contents v

Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Verifying the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Using installvcs in a Secure Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Using installvcs to Perform Unattended Installations . . . . . . . . . . . . . . . . . . . . . . . .36

Using installvcs to Install Without Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using installvcs to Configure Without Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using installvcs to Upgrade from Version 1.3.0 or 2.0 . . . . . . . . . . . . . . . . . . . . . . . . 37

Using installvcs to Upgrade VCS QuickStart to VCS 3.5 . . . . . . . . . . . . . . . . . . . . . .37

Using licensevcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using uninstallvcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Running uninstallvcs from the VCS 3.5 CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 4. Manually Installing and Configuring VCS . . . . . . . . . . . . . . . . . . . . . . . . .43

Manually Installing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Obtaining License Keys for VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Installing VCS using pkgadd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Using licensevcs to Enter License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Replacing a VCS Demo License with a Permanent License . . . . . . . . . . . . . . . . . . . .46

Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring LLT and GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring Low Latency Transport (LLT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting Up /etc/llthosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Setting Up /etc/llttab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

LLT Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Additional Considerations for LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring Group Membership and Atomic Broadcast (GAB) . . . . . . . . . . . . . . . 50

Configuring Membership Heartbeat Regions on Disk (optional) . . . . . . . . . . . . . . . . . 51Editing the /etc/gabtab File to Add Heartbeat Regions . . . . . . . . . . . . . . . . . . . . . .51

7/27/2019 vcs_ig

6/135

vi VERITAS Cluster Server 3.5 Installation Guide

Adding GAB Disk Region Signatures (Optional) for Integrity . . . . . . . . . . . . . . . . 54

Example, Configuring and Checking for a Signature . . . . . . . . . . . . . . . . . . . . . 54

Initializing File Systems and Disk Groups on Shared Storage . . . . . . . . . . . . . . . . . 54

Configuring Disk Regions on Volume Manager Disks . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Example, main.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Editing the main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Starting LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Starting GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Modifying the VCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring the ClusterService Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Removing VCS Packages Using pkgrm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5. Verifying the Installation of VCS 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Verifying the Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

LLT and GAB Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

/etc/llthosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

/etc/llttab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

/etc/gabtab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

main.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

main.cf Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Verifying LLT, GAB, and Cluster Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Verifying LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Using lltstat -n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Using lltstat -nvv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Verifying GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Verifying the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

hasys -display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Accessing the VCS Cluster Manager (Web Console) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7/27/2019 vcs_ig

7/135

Contents vii

Accessing the VCS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Installing the VCS Java Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Installing the Java Console on UNIX (Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Installing the Java Console on a Windows Workstation . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 6. Manually Upgrading VCS to Release 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . 77

Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Shutting Down VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Removing Previous VCS Packages Using pkgrm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Manually Installing VCS 3.5 (See Chapter 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Restoring Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Licensing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Starting LLT, GAB, and VCS (See Chapter 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading to the VCS 3.5 Java Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Change in Location and Syntax of the PreOnline Trigger . . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 7. Adding and Removing Cluster Systems . . . . . . . . . . . . . . . . . . . . . . . . . .91

Adding a Node to a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Removing a Node from a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Example of Removing a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Chapter 8. Installing VCS on a Single System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Creating a Single-System Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Setting the Path Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Running licensevcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Renaming the LLT and GAB Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Modifying the Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Setting Up Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

types.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7/27/2019 vcs_ig

8/135

viii VERITAS Cluster Server 3.5 Installation Guide

Editing the main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Verifying Single-Node Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Adding a System to a Single-System Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Setting Up a System to Join the Single System Cluster . . . . . . . . . . . . . . . . . . . . . . 106

Installing VxVM, VxFS if Necessary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Installing and Configuring Ethernet Cards for Private Network . . . . . . . . . . . . . 107

Configuring the Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Bringing Up the Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Installing VCS on the New System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Running licensevcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Create Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Reconfiguring VCS on the Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Verifying Configuration on Both Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Appendix A. Advanced Topics Related to Installing VCS . . . . . . . . . . . . . . . . . . . 113

Reconciling Major/Minor Numbers for NFS Shared Disks . . . . . . . . . . . . . . . . . . . . . 113

Major and Minor Numbers Assigned to Block Devices . . . . . . . . . . . . . . . . . . . 113

Checking Major and Minor Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

If Major and Minor Numbers Do Not Match . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Upgrading Solaris Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

7/27/2019 vcs_ig

9/135

ix

Preface

This guide provides information on how to install VERITAS Cluster Server (VCS)version 3.5 on the Solaris operating system, versions 2.6, 2.7, 2.8, and 2.9. It is intended forsystem and network administrators responsible for installing and configuring VCS.

If VCS 3.5 is an upgrade to your current configuration, refer to Chapter 5 for upgradeprocedures.

x For information on the hardware and software supported by VCS 3.5, and a briefoverview of the features of VCS 3.5, see VERITAS Cluster Server Release Notes.

x For information on using and configuring VCS, see the VERITAS Cluster Server UsersGuide.

x For information on using VCS bundled agents, see the VCS Bundled Agents ReferenceGuide.

x For more information on the API provided by the VCS agent framework, and forinstructions on how to build and test an agent, see the VERITAS Cluster Server AgentDevelopers Guide.

How This Guide Is Organized

Chapter 1, Introduction on page 1 describes VCS briefly; for a more comprehensivedescription of VCS, see the VERITAS Cluster Server Users Guide.

Chapter 2, Preparing to Install VCS 3.5 on page 7 describes what needs to be done

before installing VCS 3.5. It also provides a flowchart that visually presents the activitiesinvolved with installing VCS 3.5, whether you are installing VCS for the first time orupgrading. It describes the supported hardware and software. It describes installing andconfiguring your hardware, including setting up the private network and configuringshared storage. It outlines the information you need to have on hand when you startinstallation.

Chapter 3, Using the VCS Installation Utilities on page 19 describes using an interactive

script to install VCS 3.5 on all cluster systems, and describes verifying your installation. Itdescribes starting VCS.

7/27/2019 vcs_ig

10/135

Technical Support

x VERITAS Cluster Server 3.5 Installation Guide

Chapter 4, Manually Installing and Configuring VCS on page 43 describes an alternatemethod of installing VCS in the cluster one system at a time.

Chapter 5, Verifying the Installation of VCS 3.5 on page 63 describes how verify thecluster and its communication components LLT and GAB.

Chapter 6, Manually Upgrading VCS to Release 3.5 on page 77 describes how toupgrade your cluster from earlier versions of VCS. Chapter 6 has links with Chapters 3and 4.

Chapter 7, Adding and Removing Cluster Systems on page 91 describes the necessarycommands to use and the configuration files to edit for adding or removing cluster

systems.

Chapter 8, Installing VCS on a Single System on page 101 describes setting up a singlesystem with VCS 3.5. It also describes adding a system to form a multiple system cluster.

Appendix A, Advanced Topics Related to Installing VCS on page 113 discusses someadvance topics related to installing VCS.

Technical Support

For assistance with any VERITAS product, contact Technical Support:

U.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 countrys contact information.

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

To learn more about VERITAS and its products, visit http://support.veritas.com.
http://support.veritas.com/http://support.veritas.com/http://support.veritas.com/http://support.veritas.com/http://support.veritas.com/http://support.veritas.com/http://support.veritas.com/

7/27/2019 vcs_ig

11/135

Chapter , xi

Conventions

Conventions

Typeface Usage

courier computer output, files, attribute names, device names, and directories

courier

(bold)user input and commands, keywords in grammar syntax

italic new terms, titles, emphasis

italic variables within a command

Symbol Usage

% C shell prompt

$ Bourne/Korn shell prompt

# Superuser prompt (for all shells)

7/27/2019 vcs_ig

12/135

Conventions

xii VERITAS Cluster Server 3.5 Installation Guide

7/27/2019 vcs_ig

13/135

1

Introduction 1VERITAS Cluster Server (VCS) is a high-availability solution for cluster configurations.

VCS enables you to monitor systems and application services, and to restart services on adifferent system when hardware or software fails.

VCS Basics

A single VCS cluster consists of multiple systems connected in various combinations to

shared storage devices. VCS monitors and controls applications running in the cluster,and restarts applications in response to a variety of hardware or software faults. Clientapplications continue operation with little or no downtime. In some cases, such as NFS,this continuation is transparent to high-level applications and to users. In other cases, theoperation must be retried; for example, a Web page must be reloaded.

The illustration on page 2 shows a typical VCS configuration of four systems connected toshared storage. Client workstations receive service over the public network fromapplications running on the VCS systems. VCS monitors the systems and their services.VCS systems in the cluster communicate over a private network.

7/27/2019 vcs_ig

14/135

VCS Basics

2 VERITAS Cluster Server 3.5 Installation Guide

Example of a Four-System VCS Cluster

Client

VCS Private

Public Network

VCS Systems

Workstation

Network

Shared Storage

Client

Workstation

7/27/2019 vcs_ig

15/135

Chapter 1, Introduction 3

VCS Basics

Multiple Systems

VCS runs in a replicated state on each system in the cluster. A private network enables thesystems to share identical state information about all resources and to recognize whichsystems are active, which are joining or leaving the cluster, and which have failed. For theprivate network, two communication channels are required to guard against networkpartitions.

Shared Storage

A VCS hardware configuration typically consists of multiple systems connected to sharedstorage via I/O channels. Shared storage provides multiple systems an access path to thesame data, and enables VCS to restart applications on alternate systems when a systemfails, thus ensuring high availability.

The figures below illustrate the flexibility of VCS shared storage configurations. (Note thatVCS systems can only access storage that is physically attached.)

Two Examples of Shared Storage Configurations

Fully Shared Storage Distributed Shared Storage

7/27/2019 vcs_ig

16/135

VCS Basics


LLT and GAB

VCS uses two components, LLT and GAB, to share data over private networks amongsystems. These components provide the performance and reliability required by VCS.

x LLT (Low Latency Transport) provides fast, kernel-to-kernel communications, andmonitors network connections. The system administrator configures LLT by creatinga configuration file (llttab) that describes the systems in the cluster and the privatenetwork links among them.

x GAB (Group Membership and Atomic Broadcast) provides the global message orderrequired to maintain a synchronized state among the systems, and monitors diskcommunications such as that required by the VCS heartbeat utility. The systemadministrator configures GAB driver by creating a configuration file (gabtab).

See LLT and GAB Configuration Files on page 63.

Two Types of Channels: Network and Shared Disks

For the VCS private network, there are two types of channels available for heartbeating:network connections and heartbeat regions on shared disks. The shared disk regionheartbeat channel is used for heartbeating only, not for transmitting information as arenetwork channels. For information on configuring heartbeat regions on shared disks, seeConfiguring Membership Heartbeat Regions on Disk (optional) on page 51.

Each cluster configuration requires at least two channels between systems, one of whichmust be a network connection. The remaining channels may be a combination of networkconnections and heartbeat regions on shared disks.

This requirement for two channels protects your cluster against network partitioning.(For more about network partitioning, refer to the VERITAS Cluster Server Users Guide.)We recommend configuring at least one heartbeat disk region on each I/O chain shared

between systems in addition to private network connections.

The following illustration shows a two-system VCS cluster in which sysA and sysB havetwo private network connections and another connection via the heartbeat disk region on

one of the shared disks. If one of the network connections fails, two channels remain. Ifboth network connections fail, the condition is in jeopardy, but connectivity remains viathe heartbeat disk.

7/27/2019 vcs_ig

17/135

Chapter 1, Introduction 5

VCS Basics

Two Systems Connected by Two Ethernet Connections and a Heartbeat Disk Region

Preexisting Network Partitions

Apreexisting network partition refers to a failure in communication channels that occurswhile the systems are down and VCS cannot respond. When the systems are booted, VCSis vulnerable to network partitioning, regardless of the cause of the failure.

VCS Seeding

To protect your cluster from a preexisting network partition, VCS employs the concept ofa seed. By default, when a system comes up, it is not seeded. Systems can be seededautomatically or manually. Note that only systems that have been seeded can run VCS.

Systems are seeded automatically in one of two ways:

x When an unseeded system communicates with a seeded system.

x When all systems in the cluster are unseeded and able to communicate with eachother.

VCS requires that you declare the number of systems to participate in the cluster. Whenthe last system is booted, the cluster seeds and start VCS on all systems. Systems can then

be brought down and restarted in any combination. Seeding is automatic as long as atleast one instance of VCS is running somewhere in the cluster. Manual seeding is requiredonly to run VCS from a cold start (all systems down) when not all systems are available.

Public Network

VCS Private Network:

Shared Disks

sysA sysB

Partition with VCSHeartbeat Region

Two Ethernet Connections

7/27/2019 vcs_ig

18/135

VCS Basics


7/27/2019 vcs_ig

19/135

7

Preparing to Install VCS 3.5 2This chapter describes the basic preparation tasks for setting up a VCS cluster and

installing the VCS 3.5 software.

If you are upgrading, and your cluster is already set up, you can run the installvcsutility, which detects the presence of your current VCS installation and upgrades VCS torelease 3.5. If you cannot use the provided utilities to install or upgrade VCS, refer toChapter 4, Manually Installing and Configuring VCS or Chapter 6, ManuallyUpgrading VCS to Release 3.5.

Preparation Tasks

The following tasks are required in preparation for installing VCS:

Reviewing the hardware requirements

Reviewing the list of supported software

Setting up the private network

Setting up the shared storage

Preparing NFS Services

Disabling the abort sequence

Obtaining VCS License Keys

Setting the Path Variable

Enabling ssh/rsh Communication between systems

Preparing Cluster Information

Downloading Solaris Patches

Before running theinstallvcs utility, download and install the latest Solaris patches for

the Java Run Time Environment. You can obtain the patches from:http://java.sun.com/j2se/1.3/install-solaris-patches.html.

7/27/2019 vcs_ig

20/135

Preparation Tasks


Hardware Requirements for a VCS Cluster

A VCS cluster requires the following hardware:

Supported Software

x Solaris 2.6, 7, 8 (32-bit and 64-bit), and 9 (32-bit and 64-bit) operating systems

x For each platform, we recommend applying the latest cumulative operating systempatches available from Sun. See the following site:

http://sunsolve.Sun.COM

x VERITAS Volume Manager

(VxVM) 3.1.1P1, 3.2, 3.5

x VERITAS File System

(VxFS) 3.4 Patch 2, 3.5

Note Within the cluster, all systems must use the same operating system version and patch level.

Item Description

VCS systems SPARC systems running Solaris 2.6 or later.

CD-ROM drive One CD-ROM drive on each system, or a drive accessible to each.

Disks Typical VCS configurations require shared disks to supportapplications that migrate between systems in the cluster.

Disk space Each VCS system must have at least 170 megabytes of free space in the/opt file system. This includes space to run VCS, LLT, GAB, the WebConsole, and the Java Console.

Ethernet controllers In addition to the built-in public Ethernet controller, VCS requires at

least one more Ethernet interface per system. Two additionalinterfaces are recommended.

Fibre Channel or SCSIhost bus adapters

VCS requires at least one built-in SCSI adapter per system to access theoperating system disks, and at least one additional SCSI or FibreChannel Host Bus Adapter per system for shared data disks.

RAM Each VCS system requires at least 128 megabytes.

7/27/2019 vcs_ig

21/135

Chapter 2, Preparing to Install VCS 3.5 9

Preparation Tasks

Setting Up the Private Network

1. Install the required Ethernet network interface cards.

2. Connect the VCS private Ethernet controllers on each system. Use cross-over Ethernetcables (supported only on two systems), or independent hubs, for each VCScommunication network. Ensure hubs are powered from separate sources. On eachsystem, use two independent network cards to provide redundancy.

Private network setups: two-node cluster and four-node cluster

3. Test network connections by temporarily assigning network addresses and usetelnet or ping to verify communications.

LLT uses its own protocol, and does not use TCP/IP. Therefore, to ensure the privatenetwork connections are used only for LLT communication and not for TCP/IP traffic,unplumb and unconfigure the temporary addresses after testing.

The installvcs script, described in Chapter 3, configures the private network in thecluster during installation.

Note Because of their performance characteristics, network switches are recommendedfor clusters supporting the VERITAS SANPoint Foundation Suite and VERITASDBE/AC for Oracle, which make extensive use of the private cluster interconnectsfor distributed locking. See the VERITAS Cluster Server Users Guide and review thechapter on VCS performance considerations.

Public Network

Private NetworkPrivate

Public Network

NetworkHubs

7/27/2019 vcs_ig

22/135

Preparation Tasks


Setting Up Shared Storage: SCSI

1. Install the required SCSI controllers.

2. To probe your shared SCSI buses and select IDs for the systems, cable the shareddevices to one system and terminate the SCSI bus.

a. From the EEPROM prompt (ok) type the following commands:

ok show-devs

okprobe-scsi-all

b. Select a unique SCSI ID for each system on the shared SCSI bus. The priority ofSCSI IDs is 7 to 0, followed by 15 to 8. Use high-priority IDs for the systems, andlow-priority IDs for devices such as disks and tape drives. For example, use 7, 6,5, and so forth, for the systems, and use the remaining IDs for devices.

3. Modify the configuration file of the shared SCSI driver on each system.

a. Identify the three-letter name and device parent for the shared SCSI controller.Type the following command on the system connected to the shared devices:

# ls -l shared_disk_partition

The variable shared_disk_partitionrefers to the device path for any device on theshared SCSI bus.

For example, type:# ls -l /dev/dsk/c1t0d0s3

Output resembles:

lrwxrwxrwx 1 root root 53 Dec 03 11:10

/dev/dsk/c1t0d0s3 -> ../../

devices/sbus@1f,0/QLGC,isp@0,10000/sd@0,0:d,raw

Common SCSI driver names include isp (in bold text in the preceding sampleoutput) and fas (not shown).

Note that the parent name /sbus@1f,0 (also in bold text in the precedingsample output) includes the slash after the word devices, and extends to, butdoes not include, the slash preceding the driver name.

7/27/2019 vcs_ig

23/135


Preparation Tasks

b. Identify the register property values for the shared SCSI controller. Type thefollowing command on the system connected to the shared devices:

#prtconf -v

Output resembles:

QLGC,isp, instance #0

...

Register Specifications:

Bus Type=0x0, Address=0x10000, Size=1c2

...

c. Modify /kernel/drv/driver_name.conf on each system to set the SCSI ID forthe system to use on the shared bus. (Create this file if it does not exist.)

name="driver_name" parent="parent_name"

reg=register_property_values

scsi-initiator-id=scsi_id;

For example, the file/kernel/drv/isp.conf

for the system with SCSI ID 5would resemble:

name="isp" parent="/sbus@1f,0"

reg=0x0,0x10000,1c2

scsi-initiator-id=5;

4. Shut down all systems in the cluster.

5. Cable the shared devices. Two-system clusters can be cabled with the devices betweenthem, as illustrated in the figure below:

Disable SCSI termination on systems that are not positioned at the ends of the SCSIchain. Most single-ended SCSI controllers autodetect to disable termination, or areconfigured through software. Differential SCSI controllers typically require that youremove resistors from the controller card. For more information, refer to the

documentation on controllers configured in your systems.

SCSI Bus

Shared Disks

Termination

Terminatio

n

System A System B

P i T k

7/27/2019 vcs_ig

24/135

Preparation Tasks


6. Boot each system:

okboot -r

Watch for console messages from the driver changing the SCSI ID. For example:

isp0: initiator SCSI ID now 5

7. Use the prtvtoc(1M) command to test the connection from each system to theshared devices.

For example, type:

#prtvtoc /dev/dsk/c1t0d0s0

Output from this command confirms the connection between the system on whichyou typed the command and the disk.

Setting Up Shared Storage: Fibre Channel

1. Install the required FC-AL controllers.

2. Connect the FC-AL controllers and the shared storage devices to the same hub orswitch. If a fibre switch is being used, be sure that no zoning is implemented whichwould prevent both systems from seeing all shared devices required to run the criticalapplication.

3. Boot each system with the reconfigure devices option:

okboot -r

4. Once both systems have booted, use the format(1m) command to verify that eachsystem can see all shared devices.

- If Volume Manager is being used, the same number of external disk devices must

appear, but device nodes (c#t#d#) may differ.- If Volume Manger is not being used, the same number of external disk devices

must appear and device nodes must be identical for all devices on both systems.

P ti T k

7/27/2019 vcs_ig

25/135


Preparation Tasks

Disabling the Abort Sequence on SPARC Systems

Sun SPARC systems provide the following console-abort sequences that enable you to halt

and continue the processor:

x L1-A or STOP-A on the keyboard,

or,

x BREAK on the serial console input device.

Each command can then followed by a response ofgo at the ok prompt to enable thesystem to continue.

VCS does not support continuing operations after the processor has been stopped by theabort sequence because data corruption may result. Specifically, when a system is haltedwith the abort sequence it stops producing heartbeats. The other systems in the clusterthen consider the system failed and take over its services. If the system is later enabledwith go, it continues writing to shared storage as before, even though its applicationshave been restarted on other systems.

In Solaris 2.6, Sun introduced support for disabling the abort sequence. We recommenddisabling the keyboard-abort sequence on systems running Solaris 2.6 or greater. To dothis:

1. Add the following line to the /etc/default/kbd file (create the file if it does notexist):

KEYBOARD_ABORT=disable

2. Reboot.

3. If necessary, refer to the kbd(1) manual page for details.

Preparation Tasks

7/27/2019 vcs_ig

26/135

Preparation Tasks


Setting the Path Variable

The installation and other commands are located in the /sbin, /usr/sbin, and

/opt/VRTSvcs/bin directories. Add these directories to your PATH environmentvariable:

If you are using the Bourne Shell (sh or ksh), use the following command:

$ PATH=/sbin:/usr/sbin:/opt/VRTSvcs/bin:$PATH; export PATH

If you are using the C Shell (csh or tcsh), use the following command:

% setenv PATH /sbin:/usr/sbin:/opt/VRTSvcs/bin:$PATH

Enabling Communication Between Systems

When VCS is installed using the installvcs utility, communication between systems isrequired to install and configure the entire cluster at one time. Permissions must begranted for the system on which is installvcs is run to issue ssh or rsh commands asroot on all systems in the cluster. Ifssh is used to communicate between systems, it must

be configured in a way such that it operates without requests for passwords orpassphrases.

If system communication is not possible between systems using ssh or rsh, refer toUsing installvcs in a Secure Environment on page 34 or Manually Installing VCS onpage 43.

Preparation Tasks

7/27/2019 vcs_ig

27/135


Preparation Tasks

Preparing NFS Services

Your configuration may include disks on the shared bus that support NFS. File systems

exported by NFS can be configured on disk partitions or on VERITAS Volume Managervolumes. An example disk partition name is /dev/dsk/c1t1d0s3. An example volumename is /dev/vx/dsk/shareddg/vol3. Each name represents the block device onwhich the file system is to be mounted.

Major and Minor Numbers

Block devices providing NFS service must have the same major and minor numbers oneach system. Major and minor numbers are used by Solaris to identify the logical partitionor disk slice. NFS also uses them to identify the exported file system. Major and minornumbers must be checked to ensure that the NFS identity for the file system is the samewhen exported from each system.

Checking Major and Minor Numbers

1. Use the following command on all systems exporting an NFS file system. Thiscommand displays the major and minor numbers for the block device. For VxVMvolumes, you must first import the associated shared disk group on each system.

# ls -lL block_device

The variable block_devicerefers to a partition on which a file system is mounted forexport via NFS. Use this command on each NFS file system. For example, type:

# ls -lL /dev/dsk/c1t1d0s3

Output on System A resembles:

crw-r----- 1 root sys 32,134 Dec 3 11:50 /dev/dsk/c1t1d0s3

Output on System B resembles:

crw-r----- 1 root sys 32,134 Dec 3 11:55 /dev/dsk/c1t1d0s3

e

Note that the major numbers, 32, and the minor numbers, 134, match.

2. If either the major or the minor numbers do not match, proceed to install VCS 3.5 and,when installation succeeds, reconcile the major numbers using the haremajorcommand. Refer to Reconciling Major/Minor Numbers for NFS Shared Disks onpage 113 to reconcile minor numbers that do not match.

3. Check major and minor numbers on each block device used for NFS.

Preparation Tasks

7/27/2019 vcs_ig

28/135

p


Obtaining License Keys for VCS

VCS is a licensed software product. The installvcs utility prompts you for a license

key for each system. You cannot use your VERITAS software product until you havecompleted the licensing process. Use either method described in the following twosections to obtain a valid license key.

Using the VERITAS vLicenseTM Web Site to Obtain a License Key

You can obtain your license key most efficiently using the VERITAS vLicense web site.

The License Key Request Form (LKRF) has all the information needed to establish a UserAccount on vLicense and generate your license key. The LKRF is a one-page insertincluded with the CD in your product package. You must have this form to obtain asoftware license key for your VERITAS product.

Note Do not discard the License Key Request Form. If you have lost or do not have the formfor any reason, email [email protected].

The License Key Request Form contains information unique to your VERITAS softwarepurchase. To obtain your software license key, you need the following information shownon the form:

x Your VERITAS customer number

x Your order number

x Your serial number

Follow the appropriate instructions on the vLicense web site to obtain your license keydepending on whether you are a new or previous user of vLicense:

1. Access the web site at http://vlicense.veritas.com.

2. Log in or create a new login, as necessary.

3. Follow the instructions on the pages as they are displayed.

When you receive the generated license key, you can proceed with installation.

Faxing the License Key Request Form to Obtain a License Key

If you do not have Internet access, you can fax the LKRF to VERITAS. Be advised thatfaxing the form generally requires several business days to process in order to provide alicense key.

Before faxing, sign and date the form in the appropriate spaces. Fax it to the numbershown on the form.

Preparation Tasks
http://vlicense.veritas.com/http://vlicense.veritas.com/

7/27/2019 vcs_ig

29/135


p

Preparing Cluster Information

As you run the installvcs utility, be prepared to answer prompts so that the

installation can proceed smoothly and successfully. Use the following sections to guideyou in preparing for the installation of VCS 3.5. The cluster information is also necessaryto perform manual configuration if VCS is installed using pkgadd.

If you wish to install VCS packages on systems, but are not yet ready to configure the VCScluster, refer to Using installvcs to Install Without Configuration on page 37. At a latertime, when Cluster Information is available, the procedures located in Using installvcs toConfigure Without Installation on page 37 can be used to configure the cluster.

Required Cluster Information

Be prepared to provide the following information about the cluster and its systems:

A name for the cluster; the name must begin with a letter of the alphabet (a-z, A-Z).

A unique ID number for the cluster. Within the site containing the cluster, each clustermust have a unique ID.

The host names of the systems in the cluster.

Valid license keys for each system in the cluster, or a valid site license key.

Device names of the network interface cards used by theprivate networks amongsystems.

Virtual IP Address for the Cluster Manager (Web Console)You have the option to configure the Web-based Cluster Manager (Web Console). The WebConsole is a graphical user interface that enables cluster monitoring and administration. Ifyou choose this option, you must provide:

The device name for the NIC providing public network access.

A virtual IP address associated with the NIC. This virtual IP address becomes aresource for use by the ClusterService group that includes the VCS Cluster Manager

(Web Console). The Cluster Virtual IP address can fail over to another clustersystem, making the Web Console highly available.

The subnet used with the Virtual Address.

Preparation Tasks

7/27/2019 vcs_ig

30/135


Information for Configuring SMTP Notification

You have the option to configure SMTP email notification of VCS events by the VCS

Notifier component. If you choose SMTP notification, be prepared to answer prompts forthe following information:

The domain-based address of the SMTP server that is to send notification email aboutthe events within the cluster. For example, smtp.xyzstar.com.

The email address of each SMTP recipient to be notified. For example,[email protected].

The minimum severity of events for SMTP email notification. Events have four levelsof severity: Information, Warning, Error, and SevereError.

Information for Configuring SNMP Notification

You have the option to configure SNMP trap notification of VCS events by the VCSNotifier component. If you choose SNMP notification, be prepared to answer prompts forthe following information:

The port number for the SNMP trap daemon; by default this is 162.

The machine name for each SNMP console.

The minimum severity of events for SNMP trap notification. Events have four levelsof severity: Information, Warning, Error, and SevereError.

7/27/2019 vcs_ig

31/135

19

Using the VCS Installation Utilities 3

VCS Installation Utilities

Installing VCS manually without mistakes can be difficult. Therefore, utilities have beendeveloped to simplify the procedure. The three VCS installation utilities are:

x installvcs - a program that prompts for necessary information and installs andconfigures VCS

Proper installation of VCS consists of the following tasks:

- Licensing of VCS- Installing VCS packages on multiple cluster systems

- Creating several detailed configuration files on each system

- Starting all VCS processes

x licensevcs - a program that installs a VCS license key on cluster systems

x uninstallvcs - a program that uninstalls VCS packages.

All three VCS installation utilities are perl scripts that can be run at the command line.

The installvcs Utility

7/27/2019 vcs_ig

32/135



The VCS installation utility, installvcs, is interactive. Using information you supply, it

installs VCS packages and documentation on each cluster system. The utility alsoconfigures VCS and its communication services and gives you the option to configure theWeb-based Cluster Manager (Web Console) and the SNMP and SMTP notificationfeatures in the cluster.

The installvcs utility can be used to perform any of the following procedures:

x Installing and configuring VCS on all systems when ssh/rsh communication isenabled

x Installing and configuring VCS system by system in secure environments

x Performing an unattended installation

x Installing VCS packages without configuration

x Configuring VCS without installation.

x Upgrading an existing 1.3.0 or 2.0 cluster to version 3.5

x Upgrading a VCS QuickStart cluster to Standard VCS.

The installvcs utility does not install the VCS Java Console. Refer to Installing theVCS Java Console on page 74 to install the VRTScscm package.

As you use the installvcs utility, you can review summaries that let you confirm theinformation you have provided. You can stop the installation after reviewing thesummaries and restart the installation. Installation of VCS packages takes place only afteryou have confirmed the information. If the installation process is stopped beforesuccessful completion, partially installed VCS files must be removed before running theinstallvcs utility again. See Using uninstallvcs on page 40.

The installation program does not configure GAB Disk heartbeat regions. This proceduremust be done manually. Refer to Configuring Membership Heartbeat Regions on Disk(optional) on page 51.


7/27/2019 vcs_ig

33/135

Chapter 3, Using the VCS Installation Utilities 21

Install Procedures

The installvcs utility installs VCS when it is able to execute commands as root

between systems using either ssh or rsh. The installation program typically installs VCSby performing the following steps:

x Starting the installation

x Verifying communication

x Licensing VCS

x Checking the system before installation

x Configuring the cluster

x Configuring cluster manager (Web Console)

x Configuring SMTP email notification

x Configuring SNMP trap notification

x Installing VCS

x Configuring VCS

x Starting VCS

Certain program steps are skipped or performed differently when various installvcsoptions are used.

Note Ifssh is used for communication between systems, it must be configured such thatno prompts for passwords, passphrases, or confirmations occur. Any prompting byssh causes installvcs to hang.


7/27/2019 vcs_ig

34/135


Example System Installation

The following illustration shows two systems,north and south, on which VCS is to run.

For this example, the clusters name is VCSCluster2 and the clusters ID is 2.

An example two-system cluster on which VCS is to be installed

Public Network

VCS Private Network

north south

qfe:1qfe:1

qfe:0 qfe:0

Cluster Name: VCSCluster2

Cluster ID: 2

hme0hme0


7/27/2019 vcs_ig

35/135


Using installvcs

The installvcs utility installs VCS over the network. You must have permissions to

remotely log in as root on each of the systems where VCS is to be installed.

Note As you use the installvcs utility, you can review summaries that let you confirmthe information you have provided. You can stop the installation after reviewing thesummaries and restart the installation. Installation of VCS packages takes placeonly after you have confirmed the information. However, partially installed VCSfiles must be removed before running the installvcs utility again. See Usinguninstallvcs on page 40.

Starting the Installation Utility

1. Log in as root user on a system connected by the network to the systems where VCS isto be installed. The system from which VCS is installed need not be part of the cluster.

2.Insert the CD with the VCS software into a drive connected to the system.- If you are running Solaris volume-management software, the software

automatically mounts the CD as /cdrom/cdrom0. Type the command:

# cd /cdrom/cdrom0

- If you are not running Solaris volume-management software, you must mountthe CD manually. For example:

#mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom

Where, in this example, /dev/dsk/c0t6d0s2 is the name for the CD drive.

# cd /cdrom/cluster_server

3. Start the VCS installation utility by entering:

# ./installvcs

4. The utility starts by prompting for the names of the systems in the cluster.

Enter the names of the systems on which VCS is to be installed

separated by spaces (example: system1 system2):

north south


7/27/2019 vcs_ig

36/135


Verifying System Communication

5. The utility verifies that the systems you specify can communicate via ssh or rsh. If

ssh binaries are found, the program confirms that ssh is set up to operate withoutrequests for passwords or passphrases.

Checking for ssh on north ........................ .. not found

Checking OS version on north ........................ SunOS 5.8

Verifying communication with south ............ ping successful

Attempting rsh with south ...................... rsh successful

Checking OS version on south ........................ SunOS 5.8

Creating /tmp subdirectory on south.. /tmp subdirectory created

Using /usr/bin/rsh and /usr/bin/rcp to communicate with south

Communication check completed successfully

Licensing VCS

6. The installation utility verifies the license status of each system. If a VCS license isfound on the system, you are prompted about whether you want to use that license orenter a new license.

If no license is found, or you would like to enter a new license, enter a license keywhen prompted.

VCS licensing verification:

Checking north ........................ No license key found

Enter the license key for north: XXXX-XXXX-XXXX-XXXX-XXXX-XXX

Valid VCS Single Node Permanent key entered for north

Registering key XXXX-XXXX-XXXX-XXXX-XXXX-XXX on north .. Done

Checking south ........................ No license key found

Enter the license key for south: XXXX-XXXX-XXXX-XXXX-XXXX-XXX

Valid VCS Single Node Permanent key entered for southRegistering key XXXX-XXXX-XXXX-XXXX-XXXX-XXX on south .. Done

Proceed when VCS licensing completes successfully.


7/27/2019 vcs_ig

37/135


Checking Java Patches

7. The script reminds you to check for the latest patches from Sun:

The GUI modules of VCS use the Java Run Time Environment(1.3)

from Sun and require that some Solaris patches be installed to

function properly. You can find information about these patches

and instructions for downloading them at:

http://java.sun.com/j2se/1.3/install-solaris-patches.html

Starting Installation

8. When you are prompted, you can have the installation of the software begin.

Are you ready to start the Cluster installation now? (Y)

9. For each system, the installation program checks if any of the packages to be installedare already present.

Checking current installation on north:

Checking VRTSvcsw ..........................Not installed

Checking VRTSweb ...........................Not installed

.

.

Checking current installation on south:

Checking VRTSvcsw ..........................Not installed

.

Installation check completed successfully

10. For each system, the installation utility checks for the necessary file system space. Ifthe required space is not available, the installation terminates. The utility checks forthe existence of separate volumes or partitions for /opt and /usr. If they do notexist, or if the space in them is insufficient, the utility checks for the space in /, using

the space there if it is available. See the table for Hardware Requirements on page 9for file system space requirements.

Checking file system space on north:

Checking /opt ................ No /opt volume or partition

Checking /usr ................ No /usr volume or partition

Checking /var ................... required space available

Checking / ...................... required space available

http://java.sun.com/j2se/1.3/install-solaris-patches.htmlhttp://../hp/ig/02instprq.pdfhttp://../hp/ig/02instprq.pdfhttp://../hp/ig/02instprq.pdfhttp://../hp/ig/02instprq.pdfhttp://java.sun.com/j2se/1.3/install-solaris-patches.html

7/27/2019 vcs_ig

38/135


Checking file system space on south:

Checking /tmp.................... required space availableChecking /opt ................ No /opt volume or partition

Checking /usr ................ No /usr volume or partition

Checking /var ................... required space available

Checking / ...................... required space available

File system verification completed successfully

11. For each system, the installation utility checks that VCS processes are not running onthe systems. Any running VCS processes are stopped or killed by installvcs.

Note If you are running VxFS version 3.4 and have not installed the VxFS 3.4 Patch 2,GAB or LLT may not stop properly and you may have to reboot your system toinstall VCS successfully.

Stopping VCS processes on north:

Checking VCS .................................... not running

Checking hashadow ............................... not running

Checking CmdServer .............................. not running

Checking Web GUI processes....................... not running

Checking notifier processes ..................... not running

Checking GAB .................................... not running

Checking LLT .................................... not running

Stopping VCS processes on south:

Checking VCS .................................... not running

Checking hashadow ............................... not running

Checking CmdServer .............................. not running

Checking Web GUI processes....................... not running

Checking notifier processes ..................... not running

Checking GAB .................................... not running

Checking LLT .................................... not running

VCS processes are stopped


7/27/2019 vcs_ig

39/135


Configuring the Cluster

12. The program lists the information required to start installation:

To configure VCS the following is required:

A unique Cluster name

A unique Cluster ID number between 0-255

Two NIC cards on each system used for private network links

Are you ready to configure VCS on these systems? (Y)

Select Y to start installing and configuring VCS on the systems. If you enter N,VCS packages are installed on the systems without configuration.

13. The installation program prompts you for the cluster name and identification:

Enter the unique Cluster Name: vcs_cluster2

Enter the unique Cluster ID number between 0-255: 7

14. After you enter the cluster ID number, the program discovers and lists all NICs on thefirst system:

Discovering NICs on north: ..... discovered hme0 qfe0 qfe1

qfe2 qfe3

Enter the NIC for the first private network heartbeat link on

north: (hme0 qfe0 qfe1 qfe2 qfe3) qfe0

Enter the NIC for the second private network heartbeat link onnorth: (hme0 qfe1 qfe2 qfe3) qfe1

Are you using the same NICs for private heartbeat links on all

systems? (Y)

If you answer N, the program prompts for the NICs of each system.


7/27/2019 vcs_ig

40/135


15. The installation program asks you to verify the cluster information:

Cluster information verification:

Cluster Name: vcs_cluster2

Cluster ID Number: 7

Private Network Heartbeat Links for north: link1=qfe0

link2=qfe1

Private Network Heartbeat Links for south: link1=qfe0

link2=qfe1

Is this information correct? (Y)

If you enter N, the program returns to the screen describing the installationrequirements (step 12).

Configuring Cluster Manager

16. The installation program describes the information required to configure Cluster

Manager (Web Console):The following information is required to configure the Cluster

Manager:

A public NIC used by each system in the cluster

A Virtual IP address and netmask for the Cluster Manager

Do you want to configure the Cluster Manager (Web Console) (Y)

Press Return to configure Cluster Manager (Web Console) on the systems. You canenter N and skip configuring Cluster Manager and the program advances you tothe screen enabling you to configure SMTP notification.

17. Confirm that you want to use the discovered public NIC on the first system andindicate whether all systems use the same public NIC.

Active NIC devices discovered on north: hme0

Enter the NIC for the Cluster Manager (Web Console) to use onnorth: (hme0)

Is hme0 the public NIC used for all systems (Y)

18. Enter the virtual IP address to be used by Cluster Manager:

Enter the Virtual IP address for the Cluster Manager:

10.180.88.199

You can confirm the default netmask, or enter another:Enter the netmask for IP 10.180.88.199: (255.0.0.0)


19 Th i t ll ti k t if th Cl t M i f ti
http://-/?-http://-/?-

7/27/2019 vcs_ig

41/135


19. The installation program asks you to verify the Cluster Manager information:

Cluster Manager (Web Console) verification:

NIC: hme0

IP: 10.180.88.199

Netmask: 255.0.0.0


To indicate the information is correct, press Return. Otherwise, enter N and theprogram returns to the screen describing the Cluster Manager requirements (step 16).

Configuring SMTP Email Notification

20. The installation program describes the information required to configure the SMTPnotification feature of VCS:

The following information is required to configure SMTP

notification:

The domain based address of the SMTP server

The email address of each SMTP recipient

A minimum severity level of messages to send to each

recipient

Do you want to configure SMTP notification? (Y) y

You can enter N and skip configuring SMTP notification. The program advancesyou to the screen enabling you to configure SNMP notification (see step 23).

21. Respond to the prompts and provide information to configure SMTP notification.

Enter the domain based address of the SMTP server (example:

smtp.yourcompany.com) smtp.xyzstar.com

Enter the email address of the SMTP recipient [email protected]

Enter the minimum severity of events for which mail should be

sent to [email protected]: [I=Information, W=Warning, E=Error,S=SevereError] w

Would you like to add another SMTP recipient? (N) y

Enter the email address of the SMTP recipient [email protected]

Enter the minimum severity of events for which mail should be

sent to [email protected]: [I=Information, W=Warning,

E=Error, S=SevereError] e

Would you like to add another SMTP recipient? (N)


22 Verify that the SMTP notification information is correct
http://-/?-http://-/?-http://-/?-http://-/?-

7/27/2019 vcs_ig

42/135


22. Verify that the SMTP notification information is correct.

SMTP notification verification:

SMTP Address: smtp.xyzstar.com

Recipient: [email protected] email for Warning or

higher events

Recipient: [email protected] email for Error or

higher events


Press Return if the information is correct. Otherwise, enter N and the programreturns to the screen describing the SMTP notification requirements (see step 20). Youcan bypass configuration of SMTP notification or reenter the information.

Configuring SNMP Trap Notification

23. The installation program describes the information required to configure the SNMP

notification feature of VCS:The following information is required to configure SNMP

notification:

System names of SNMP console(s) to receive VCS trap messages

SNMP trap daemon port numbers for each console

A minimum severity level of messages to send to each console

Do you want to configure SNMP notification? (Y)

You can enter n and skip configuring SNMP notification. The installation programstarts installation; see step 26.

24. Respond to the prompts and provide information to configure SNMP notification.

Enter the SNMP trap daemon port (162)

Please enter the SNMP console system name saturn

Enter the minimum severity of events for which SNMP traps shouldbe sent to thor99: [I=Information, W=Warning, E=Error,

S=SevereError] e

Would you like to add another SNMP console? (N) y

Please enter the SNMP console system name jupiter

Enter the minimum severity of events for which SNMP traps should

be sent to thor98: [I=Information, W=Warning, E=Error,

S=SevereError] s

Would you like to add another SNMP console? (N)


25 Verify that the SNMP notification information is correct
http://-/?-http://-/?-http://-/?-http://-/?-

7/27/2019 vcs_ig

43/135


25. Verify that the SNMP notification information is correct.

SNMP notification verification:

SNMP Port: 162

Console: saturn receives SNMP traps for Error or higher events

Console: jupiter receives SNMP traps for SevereError or higher

events


Press Return if the information is correct. If the information is incorrect, enter N andthe program returns to the screen describing the SNMP notification requirements (seestep 23). You can either bypass configuration of SNMP notification or reenter theinformation.

Installing VCS

26. After you have verified that the information you have entered is correct, theinstallation program begins installing the packages on the first system:

Installing VCS on north:

Installing VRTSvlic package ........................... Done

Installing VRTSperl package ........................... Done

Installing VRTSllt package ............................ Done

Installing VRTSgab package ............................ Done

Installing VRTSvcs package ............................ Done

Installing VRTSvcsmg package .......................... Done

Installing VRTSvcsag package .......................... Done

Installing VRTSvcsdc package .......................... Done

Installing VRTSvcsmn package .......................... Done

Installing VRTSweb package ............................ Done

Installing VRTSvcsw package ........................... Done

The same packages are installed on each machine in the cluster:Installing VCS on south:

Copying VRTSvlic binaries ............................. Done

Installing VRTSvlic package ........................... Done

Copying VRTSperl binaries ............................. Done

Installing VRTSperl package ........................... Done

.

.Package installation completed successfully


Configuring VCS
http://-/?-http://-/?-

7/27/2019 vcs_ig

44/135


Configuring VCS

27. The installation program continues by creating configuration files and copying them

to each system:

Configuring VCS ...................................... Done

Copying VCS configuration files to north.............. Done

Copying VCS configuration files to south.............. Done

Configuration files copied successfully

Starting VCS

28. You can now start VCS and its components on each system:

Do you want to start the cluster components now? (Y)

Starting VCS on north

Starting LLT ...................................... StartedStarting GAB ...................................... Started

Starting VCS ...................................... Started

Starting VCS on south

Starting LLT ...................................... Started

Starting GAB ...................................... Started

Starting VCS ...................................... Started

VCS Startup completed successfully


29. When VCS installation completes, the installation program reports on:

7/27/2019 vcs_ig

45/135


p , p g p

- The backup configuration files named with the extension init.name_of_cluster.For example, the file /etc/llttab in the installation example has a backup filenamed:

/etc/llttab.init.vcs_cluster2

- The URL and the login information for Cluster Manager (Web Console), if youchose to configure it. Typically this resembles:

http://10.180.88.199:8181/vcs

You can access the Web Console using the User Name: admin and thePassword: password. Use the /opt/VRTSvcs/bin/hauser command to addnew users.

- The location of a VCS installation report, which is named/var/VRTSvcs/installvcsReport.name_of_cluster. For example:

/var/VRTSvcs/installvcsReport.vcs_cluster2

- Additional instructions which may be necessary to complete startup or

installation on other systems.- VCS installation completes.

VCS installation completed successfully

Verifying the Cluster

When installvcs is used, it is expected that VCS and all components are properlyconfigured and can start correctly. To verify that your cluster is operating properlyfollowing installation, you may perform the steps listed in Verifying LLT on page 67,Verifying GAB on page 70, and Verifying the Cluster on page 71.


Using installvcs in a Secure Environment

7/27/2019 vcs_ig

46/135


Using installvcs in a Secure Environment

In secure enterprise environments, ssh or rsh communication is not allowed between

systems. In such cases, installvcs installs and configures VCS only on systems withwhich it can communicate (most often the local system only). When installation iscomplete, a configuration file is created and copied to the other systems so the installationprogram can configure other systems identically without prompting for informationagain.

Perform the following steps to use installvcs in a secure environment.

1. On one system in the cluster perform the steps listed in Using installvcs on page 23.In step 5 on page 24, the inability to communicate between systems is detected and asystem confirmation is offered:

Verifying communication with south .......... ping successful

Attempting rsh with south ............... Cannot rsh to south

north cannot communicate with or does not have ssh/rsh

permissions with the following systems: south

Would you like to install VCS on system(s) north only and

create an automated installation file for system(s) south? (Y)

Enter Y to proceed with the installation.

2. Enter all cluster information in the steps that follow step 5 on page 24. VCS is installedand configured on systems where communication is possible. Once installation iscomplete, the installation program reports that cluster information is stored within

the /var/VRTSvcs/VCSvars.pm file.

Note Until VCS is installed and started on all systems in the cluster, the followingappears when VCS is started: VCS:11306:Did not receive clustermembership, manual intervention may be needed for seeding

3. Copy the /var/VRTSvcs/VCSvars.pm file to a directory such as /tmp on all

systems yet to be installed.


4. On another system, follow the steps listed in Starting the Installation Utility on

7/27/2019 vcs_ig

47/135


page 23, but modify the command in step 3 on page 23 by starting VCS installationusing the -configfile option:

# ./installvcs -configfile /tmp

A summary of the configuration information is listed before the installation begins:

A VCSvars.pm file exists on this system with the following

information:

Cluster Name: VCSCluster2


Systems: north south

Installing VCS on system south only

5. Repeat step 4 until VCS has been installed on all systems in the cluster.


Using installvcs to Perform Unattended Installations
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-

7/27/2019 vcs_ig

48/135


g

The installvcs with the -configfile option andVCSvars.pm file is useful not only

for installing and configuring VCS within a secure environment. You can manually enterinformation into a VCSvars.pm file and use the -configfile option to performunattended installations. An example VCSvars.pm file is listed below:

$CLUSTERVARS=1;

@SYSTEMLIST=("north","south");

$LKEY{"north"}="NJZZ-X2PU-V42V-R3TO-YHXP-P6C";

$LKEY{"south"}="NJZZ-YRPC-78BD-D363-BQS3-PPC";

$CPM="VCS";

$CLUSTERNAME="VCSCluster2";$CLUSTERID=2;

$LLTLINKS{"north"}="link qfe0 /dev/qfe:0 - ether - -

link qfe1 /dev/qfe:1 - ether - -";

$LLTLINKS{"south"}="link qfe0 /dev/qfe:0 - ether - -

link qfe1 /dev/qfe:1 - ether - -";

$WEBIP="10.180.88.199";

$WEBNM="255.0.0.0";

$CSGNIC{"_ALLSYSTEMS_"}="hme0";$SMTPADD="smtp.xyzstar.com";

@SMTPSEV=("\ozzie\@xyzstar.com\ = Warning,

\harriet\@xyzstar.com\ = Error");

$SNMPPORT=162;

@SNMPSEV=("\saturn\ = Error, \jupiter\ = SevereError");

Ifssh is used instead ofrsh for system communications during an unintendedinstallation, the $USESSH must be declared in the VCS vars.pm file:

$USESSH-1;


Using installvcs to Install Without Configuration

7/27/2019 vcs_ig

49/135


In certain situations, users may choose to install the VCS packages on a system before they

are ready for cluster configuration. During such situations, the installvcs-installonly option can be used. The installation program licenses and installs VCS onthe systems entered without creating any VCS configuration files.

Using installvcs to Configure Without Installation

When VCS has been installed without configuration, use the installvcs-configonly

option to configure VCS when you are ready for cluster configuration. Theinstallvcs utility prompts for cluster information as described in Using installvcs onpage 23 and creates VCS configuration files without performing installation.

Using installvcs to Upgrade from Version 1.3.0 or 2.0

When you run installvcs on cluster systems that run VCS version 1.3.0 or 2.0, you areguided through an upgrade procedure. For VCS 2.0, before starting the actual installation,the utility updates the cluster configuration (including the ClusterService group andthe types.cf) to match version 3.5. For VCS 1.3.0, you must manually configure theClusterService group. After stopping VCS on all systems and uninstalling theprevious version, installvcs installs and starts VCS version 3.5.

In a secure environment, run the installvcs utility on each system to upgrade a clusterto VCS 3.5. On the first system, the utility updates the configuration and stops the cluster

before upgrading the system. On the other systems, it uninstalls the previous version and

installs VCS 3.5. Once the final system is upgraded and started, the upgrade is complete.

VCS versions prior to 1.3.0 must be upgraded manually using the procedures listed inManually Upgrading VCS to Release 3.5 on page 77.

Using installvcs to Upgrade VCS QuickStart to VCS 3.5

Use theinstallvcs -qstovcs

option to upgrade systems running VCS QuickStartversion 2.0 or 3.5 to VCS 3.5. During the upgrade procedure, you must add a VCS licensekey to the systems. Once the systems are properly licensed, the utility modifies theconfiguration, stops VCS QuickStart, removes the packages for VCS QuickStart (whichinclude the Configuration Wizards and the Web GUI), and adds the VCS packages fordocumentation and the Web GUI. When restarted, the cluster runs VCS enabled with fullfunctionality.

Using licensevcs

Using licensevcs

7/27/2019 vcs_ig

50/135


VCS licensing is usually performed at the initial point of installation. However, there are

two cases in which a VCS license may need to be added or updated:x VCS is installed manually

x A Demo License is upgraded to a Demo Extension or a Permanent License

You can use the licensevcs utility to add a VCS license key on a system or update thelicense key on a running cluster. Use the following procedure:

1. If you can execute commands as root on the remote systems in the cluster using sshor rsh, you can run licensevcs on one system and add or update the license on allsystems in the cluster. If you cannot execute commands as root on the remote systems,go to step 4.

2. Enter the command to start licensevcs:

# cd /opt/VRTSvcs/install

# ./licensevcs

3. The licensing procedure is identical to the first steps of the installvcs utility (seeStarting the Installation Utility on page 23). If you are adding VCS manually, theutility prompts you for the names of the systems. If you are updating the demolicense, the utility determines the cluster system lists via discovery from theconfiguration files. If system communication is verified, you are prompted for a VCSlicense for each system:

Enter the license key for north:NJZZ-X2PU-V42V-R3TO-YHXP-P6C

Valid VCS Single Node Permanent key entered for north

Registering key NJZZ-X2PU-V42V-R3TO-YHXP-P6C on north ... Done

Enter the license key for south:NJZZ-YRPC-78BD-D363-BQS3-PPC

Valid VCS Single Node Permanent key entered for south

Registering key NJZZ-YRPC-78BD-D363-BQS3-PPC on south... Done

Note Relicensing systems using VCS version 3.5 no longer requires that VCS be stoppedand restarted.

4. If you cannot execute commands as root on the remote systems in the cluster usingssh or rsh, you must run licensevcs on each cluster system.

Note If you use the vxlicinst utility to install a VCS site license, make sure you run iton every node of the cluster. The vxlicinst utility does not automatically

propagate a site license to the remote nodes of the cluster.

Checking Licensing Information on the System

Checking Licensing Information on the System

7/27/2019 vcs_ig

51/135


You can use the utility vxlicrep to display information about the licenses on a system.

For example, enter:# cd /opt/VRTS/bin

# ./vxlicrep

VERITAS License Manager vxlicrep utility version 3.00.004

Copyright (C) VERITAS Software Corp 2002. All Rights reserved.

Creating a report on all VERITAS products installed on this system

-----------------***********************-----------------

License Key = NXUZ-X2PU-V53V-R3WO-YHXP-P6C

Product Name = VERITAS Cluster Server

Serial Number = 1249

License Type = PERMANENT

OEM ID = 478

Features :=

Platform = Solaris

Version = 3.5

Tier = 0

Reserved = 0

Mode = VCS

From the output, you can determine the license key, the type of license, the product forwhich it applies, and its expiration date, if any. Demo keys have expiration dates,permanent keys and site keys do not.

Using uninstallvcs

Using uninstallvcs

7/27/2019 vcs_ig

52/135


Before removing VCS from any system in the cluster, shutdown applications such as the

Java Console or any VCS enterprise agents that depend on VCS.The uninstallvcs program does not remove shared packages such as VRTSllt,VRTSgab, and VRTSweb if they are also used as a part of other VERITAS softwareprograms. The uninstallvcs program does not automatically uninstall VCS enterpriseagents, but offers uninstallation if proper package dependencies on VRTSvcs are found.See the documentation for the specific enterprise agent for instructions on removing it if itis not uninstalled by uninstallvcs.

Use the following procedure to uninstall VCS:

1. If you can execute commands as root on the remote systems in the cluster using sshor rsh, uninstallvcs can be run on one system to uninstall VCS on all systems inthe cluster. If you cannot execute commands as root on remote systems in the clusterusing ssh or rsh, uninstallvcs must be run on each system in the cluster.

2. Enter the command to start uninstallvcs:

# cd /opt/VRTSvcs/install

# ./uninstallvcs

3. The script begins by presenting information from VCS configuration files present onthe local system and offering uninstallation of those systems:

VCS configuration files exist on this system with the following

information:

Cluster Name: VCScluster2


Systems: north south

Service Groups: ClusterService groupA groupB

Do you want to uninstall VCS from all of the systems in this

cluster?(Y)

Enter Y to uninstall VCS on these systems. If you enter N or if no VCSconfiguration files are found on the local system, the utility prompts you for a list ofsystems to uninstall.

Note Before removing VCS from fewer than all systems in a cluster, make sure that noservice groups are running on the systems from which VCS is uninstalled. You mustalso reconfigure VCS on the remaining systems. Refer to Adding and RemovingNodes on page 55 for instructions on how to remove systems from a cluster.

Using uninstallvcs

4. The uninstallvcs utility continues by verifying communication between systemsand checking the installation to determine the packages to be uninstalled. If packages,

7/27/2019 vcs_ig

53/135


g p g p gsuch as enterprise agents, are found to be dependent on a VCS package, you are

prompted on whether you want them removed:.

.

.

Checking VRTSvcs ..................... version 3.5 installed

Checking VRTSvcs dependencies .................... VRTSvcsor

Do you want to uninstall VRTSvcsor which is dependent on

package VRTSvcs? (Y)

Enter Y if you wish to remove the designated package.

5. After the utility verifies that uninstallation can proceed, it stops the processes on eachsystem.

installation check completed successfully

.

.Stopping VCS processes on north:

Checking VCS ..................................... not running

Checking CmdServer ................................... running

Killing CmdServer ....................................... Done

Checking Web GUI processes ....................... not running

Checking notifier processes ......

vcs_ig

Documents

Transcript of vcs_ig