Home > Documents > VERITAS Cluster Server™ 4.0 Install guide

VERITAS Cluster Server™ 4.0 Install guide

Date post: 30-May-2018
Category:
Author: amsreeku
View: 220 times
Download: 0 times
Share this document with a friend
Embed Size (px)

of 224

Transcript
  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    1/224

    January 2004

    N10051F

    VERITAS Cluster Server 4.0

    Installation Guide

    Solaris

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    2/224

    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-2003 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS

    logo, VERITAS Cluster Server, and all other VERITAS product names and slogans are trademarks orregistered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS logo, Reg. U.S.Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks orregistered trademarks of their respective companies.

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

    Third-Party Copyrights

    Apache Software

    This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

    The Apache Software License, Version 1.1

    Copyright (c) 1999 The Apache Software Foundation. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution.

    3. The end-user documentation included with the redistribution, if any, must include the following acknowledgement:

    This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

    Alternately, this acknowledgement may appear in the software itself, if and wherever such third-party acknowledgements normally appear.

    4. The names The Jakarta Project, Tomcat, and Apache Software Foundation must not be used to endorse or promote products derived fromthis software without prior written permission. For written permission, please contact [email protected]

    5. Products derived from this software may not be called Apache nor may Apache appear in their names without prior written permissionof the Apache Group.

    THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALLTHE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more informationon the Apache Software Foundation, please see http://www.apache.org/.

    ii VERITAS Cluster Server Installation Guide

    http://www.veritas.com/http://www.veritas.com/
  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    3/224

    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 r ights 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.

    VERITAS Cluster Server Installation Guide iii

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    4/224

    iv VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    5/224

    Contents

    Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

    How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

    Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

    Telephone and Fax Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

    Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

    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 . . . . . . . . . . . . . . . . . . . . . . . . . . 4Preexisting Network Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

    VCS Seeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

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

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

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

    Supported Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

    Setting the PATH Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

    Setting Up the Private Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

    Using Network Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

    Setting Up Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Setting Up Shared Storage: SCSI Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

    v

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    6/224

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

    Disabling the Abort Sequence on SPARC Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    Enabling Communication Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

    Preparing NFS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Major and Minor Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Checking Major and Minor Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

    Obtaining License Keys for VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    Using the VERITAS vLicenseTM Web Site to Obtain License Key . . . . . . . . . . . . . . . 17

    Faxing the License Key Request Form to Obtain License Key . . . . . . . . . . . . . . . . . 17

    Patches Required for Java Run Time Environment from Sun . . . . . . . . . . . . . . . . . . . . 18

    Preparing to Use installvcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

    Choosing Optional Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18I/O Fencing (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Required Cluster Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

    Virtual IP Address for Cluster Manager (Web Console) . . . . . . . . . . . . . . . . . . . . . . 19

    Information for Configuring SMTP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Information for Configuring SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

    Information for the Global Cluster Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

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

    VCS Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

    Optional Features of the installvcs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

    Using the installvcs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Interacting with the installvcs Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Upgrading VCS Using the installvcs Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

    Example VCS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    Mounting the Software Disc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

    Running the VERITAS Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Running the installvcs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    vi VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    7/224

    Using the installvcs -precheck Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

    Starting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

    Performing Initial System Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    Installing the VERITAS Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 27

    Verifying VCS Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

    Choosing Optional Packages Before Adding VCS Packages . . . . . . . . . . . . . . . . 29

    Configuring the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

    Adding VCS Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

    Configuring Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

    Configuring SMTP Email Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

    Configuring SNMP Trap Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

    Configuring the Global Cluster Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

    Installing the VCS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Creating VCS Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

    Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

    Verifying the Cluster After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

    Installing Language Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

    Using installvcs in a Secure Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

    Using installvcs to Perform Unattended Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

    Syntax Used in Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

    Example Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

    Response File Variable Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

    Using installvcs to Install Without Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Using installvcs to Configure Without Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Using installvcs to Upgrade to VCS 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

    Upgrading from VCS 1.3.0, 2.0, or 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

    Starting the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

    Checking Upgrade Requirements and Changing Passwords . . . . . . . . . . . . . . . 52

    Removing VCS 3.5 Packages, Installing VCS 4.0 Packages . . . . . . . . . . . . . . . . . 53

    Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

    Contents vii

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    8/224

    Summarizing the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

    Upgrading from VCS 1.3.0, 2.0, or 3.5 in a Secure Environment . . . . . . . . . . . . . . . 55

    Upgrading from GCM 1.2 or 3.5 to VCS 4.0 with the Global Cluster Option . . . . 56

    Starting the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

    Adding the Infrastructure Packages and Checking Licenses . . . . . . . . . . . . . . . 57

    Checking Upgrade Requirements and Changing Passwords . . . . . . . . . . . . . . . 58

    Capturing the GCM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    Completing Check of Upgrade Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

    Removing VCS 3.5 Packages, Installing VCS 4.0 Packages . . . . . . . . . . . . . . . . . 60

    Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

    Completing Upgrade from CGM to VCS 4.0 Global Cluster . . . . . . . . . . . . . . . 61

    Summarizing the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

    Completing the Upgrade of GCM to VCS 4.0 with GCO . . . . . . . . . . . . . . . . . . . . . 62Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    Using vxlicinst to Update Product Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

    Using Other Options of installvcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

    Using uninstallvcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

    Running uninstallvcs from the VCS 4.0 CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

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

    Manually Installing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

    Requirements for Installing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    Disk Space for Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    Installing VCS Software Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

    Installing the Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

    Installing VCS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

    Installing VCS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

    Installing Language Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

    Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Installing Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

    viii VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    9/224

    Adding a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

    Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

    Configuring LLT and GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

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

    Setting Up /etc/llthosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

    Setting Up /etc/llttab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

    LLT Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

    Additional Considerations for LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

    Configuring Membership Heartbeat Regions on Disk (optional) . . . . . . . . . . . . . . . . . 80

    Editing the /etc/gabtab File to Add Heartbeat Regions . . . . . . . . . . . . . . . . . . . . . .80

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

    Example, Configuring and Checking for a Signature . . . . . . . . . . . . . . . . . . . . . .83Initializing File Systems and Disk Groups on Shared Storage . . . . . . . . . . . . . . . . . 83

    Configuring Heartbeat Disk Regions on VxVM Disks . . . . . . . . . . . . . . . . . . . . . . . .84

    Configuring VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

    Editing the main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

    Example, main.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

    Starting LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

    Starting GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

    Starting VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

    Modifying the VCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

    Configuring the ClusterService Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

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

    Removing VCS Packages Using pkgrm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

    Chapter 5. Verifying the Installation of VCS 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

    Verifying LLT and GAB Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

    /etc/llthosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

    /etc/llttab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

    Contents ix

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    10/224

    /etc/gabtab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

    Verifying the main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

    main.cf Example, for Clusters Without the GCO Option . . . . . . . . . . . . . . . . . . . . . 96

    main.cf Example, for Clusters With the GCO Option . . . . . . . . . . . . . . . . . . . . . . . . 97

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

    Verifying LLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

    Using lltstat -n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

    Using lltstat -nvv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

    Verifying GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

    Verifying the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

    hasys -display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

    Accessing the VCS Cluster Manager (Web Console) . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

    Accessing the VCS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Installing the VCS Java Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

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

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

    Chapter 6. Setting Up I/O Fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

    Requirements for Using I/O Fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

    Verifying Storage Supports SCSI-III Persistent Reservations . . . . . . . . . . . . . . . . . . . . 107

    Adding Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

    Verifying that Systems See the Same Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

    Verifying Shared Storage Arrays Using the vxfentsthdw Utility . . . . . . . . . . . . . 110

    General Guidelines for Using vxfentsthdw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Using the -r Option for Non-destructive Testing . . . . . . . . . . . . . . . . . . . . . . . . 111

    Using the -m Option: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

    Using the -f Option: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

    Using the -g Option: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

    Setting Up Coordinator Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

    Requirements for Coordinator Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

    x VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    11/224

    Configuring a Disk Group Containing Coordinator Disks . . . . . . . . . . . . . . . . . . . 114

    Editing VCS Configuration to Add the UseFence Attribute . . . . . . . . . . . . . . . . . . . . .116

    Adding or Removing Coordinator Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

    How I/O Fencing Works in Different Event Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . 119

    The vxfenadm Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

    Registration Key Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

    Troubleshooting I/O Fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

    vxfentsthdw Fails When SCSI TEST UNIT READY Command Fails . . . . . . . . . . 124

    vxfentsthdw Fails When Prior Registration Key Exists on Disk . . . . . . . . . . . . . . . 124

    Node is Unable to Join Cluster While Another Node is Being Ejected . . . . . . . . . 125

    Removing Existing Keys From Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

    System Panics to Prevent Potential Data Corruption . . . . . . . . . . . . . . . . . . . . . . . .126

    How vxfen Driver Checks for Pre-existing Split Brain Condition . . . . . . . . . . 126Case 1: System 2 Up, System 1 Ejected (Actual Potential Split Brain) . . . . . . . 127

    Case 2: System 2 Down, System 1 Ejected (Apparent Potential Split Brain) . . 127

    Using vxfenclearpre Command to Clear Keys After Split Brain . . . . . . . . . . . . . . . 128

    Chapter 7. Manually Upgrading VCS to Release 4.0 . . . . . . . . . . . . . . . . . . . . . . . .129

    Obtaining a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

    Shutting Down VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

    Removing Previous VCS Packages Using pkgrm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

    Manually Installing VCS 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

    Restoring Previous Configuration Files to VCS 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

    Licensing VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Starting LLT, GAB, and VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

    Upgrading to the VCS 4.0 Java Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

    Manually Updating VCS User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

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

    Contents xi

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    12/224

    Chapter 8. Adding and Removing Cluster Systems . . . . . . . . . . . . . . . . . . . . . . . . 143

    Adding a Node to a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

    Setting up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

    Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

    Preparing the Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

    Installing the Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

    Installing VCS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

    Installing VCS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

    Adding a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

    Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . 147

    Configuring LLT and GAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

    Removing a Node from a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

    Example of Removing a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

    Chapter 9. Installing VCS on a Single System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

    Creating a Single-System Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

    Setting the Path Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

    Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

    Preparing the Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

    Installing the Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

    Installing VCS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

    Installing VCS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

    Adding a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

    Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . 161Renaming the LLT and GAB Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

    Modifying the Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

    Setting Up Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

    main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

    types.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

    Editing the main.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

    xii VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    13/224

    Verifying Single-Node Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

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

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

    Installing VxVM, VxFS if Necessary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

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

    Configuring the Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

    Bringing Up the Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

    Installing VCS on the New System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

    Preparing the Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

    Installing the Infrastructure Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

    Installing VCS Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

    Installing VCS Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

    Adding a License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Checking Licensing Information on the System . . . . . . . . . . . . . . . . . . . . . . . . . 172

    Create Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

    Reconfiguring VCS on the Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

    Verifying Configuration on Both Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

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

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

    Upgrading Solaris Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

    LLT Over UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

    When to Use LLT Over UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

    Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Configuring LLT over UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

    The link Command in the /etc/llttab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

    The set-addr Command in the /etc/llttab File . . . . . . . . . . . . . . . . . . . . . . . . . . 185

    Selecting UDP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

    Sample Configuration: Direct-Attached Links . . . . . . . . . . . . . . . . . . . . . . . . . . .187

    Sample Configuration: Links Crossing IP Routers . . . . . . . . . . . . . . . . . . . . . . . 188

    Contents xiii

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    14/224

    Appendix B. Upgrading From VCS QuickStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

    Upgrading From VCS QuickStart 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

    Uninstall VCS QuickStart 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

    Saving the Existing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

    Install VCS 4.0 Using -installonly Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

    Restoring QuickStart 3.5 Configuration for use with VCS 4.0 . . . . . . . . . . . . . . . . 194

    Starting LLT, GAB, and VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

    Updating User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

    Upgrading From VCS QuickStart 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

    Saving the Existing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

    Uninstalling VCS QuickStart 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

    Installing VCS 4.0 Using the -installonly Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

    Restoring QuickStart 2.0 Configuration for Use with VCS 4.0 . . . . . . . . . . . . . . . . 199Restore llttab, llthosts, and gabtab on all Nodes in the Cluster . . . . . . . . . . . . . . . 201

    Starting LLT, GAB, and VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

    Updating User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

    Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

    xiv VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    15/224

    Preface

    This guide provides information on how to install VERITAS Cluster Server (VCS)

    version 4.0 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.

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

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

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

    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 OrganizedChapter 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 4.0 on page 7 describes what needs to be donebefore installing VCS 4.0. It describes the supported hardware and software. It describesinstalling and configuring your hardware, including setting up the private network andconfiguring shared storage. It outlines the information you need to have on hand whenyou start installation.

    Chapter 3. Using the VCS Installation Utilities on page 21describes using an interactivescript to install VCS 4.0 on all cluster systems, and describes verifying your installation. Itdescribes starting VCS.

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

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

    xv

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    16/224

    Getting Help

    Chapter 6. Setting Up I/O Fencing on page 107 describes how to set up I/O fencing ofshared storage.

    Chapter 7. Manually Upgrading VCS to Release 4.0 on page 129 describes how toupgrade your cluster from earlier versions of VCS.

    Chapter 8. Adding and Removing Cluster Systems on page 143describes the necessarycommands to use and the configuration files to edit for adding or removing clustersystems.

    Chapter 9. Installing VCS on a Single System on page 157 describes setting up a singlesystem with VCS 4.0. It also describes adding a system to form a multiple system cluster.

    Appendix A. Advanced Topics Related to Installing VCS on page 175presents someadvanced topics related to installing VCS.

    Appendix B. Upgrading From VCS QuickStart on page 191describes procedure toupgrade to VCS 4.0 from VCS QuickStart.

    Getting HelpFor technical assistance, visit the VERITAS Technical Services Web site athttp://support.veritas.com. From there you can:

    Contact the VERITAS Technical Services staff and post questions to them. Download the latest patches and utilities. View the VCS Frequently Asked Questions (FAQ) page. Search the knowledge base for answers to technical support questions. Receive automatic notice of product updates. Learn about VCS training. Read white papers related to VCS. Access the latest product documentation and technical notes.

    Telephone and Fax Support

    Telephone and fax support for VCS is available only with a valid support contract. Tocontact Technical Services, dial the appropriate phone number listed on the TechnicalSupport Guide included in the product box. Have your product license information readyto ensure you are routed to the proper support personnel.

    xvi VERITAS Cluster Server Installation Guide

    http://support.veritas.com/http://support.veritas.com/
  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    17/224

    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 commandSymbol Usage

    % C shell prompt

    $ Bourne/Korn shell prompt

    # Superuser prompt (for all shells)

    Preface xvii

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    18/224

    Conventions

    xviii VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    19/224

    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.

    1

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    20/224

    VCS Basics

    Client

    VCS Private

    Public Network

    VCS Systems

    Workstation

    Network

    Shared Storage

    Client

    Workstation

    Example of a Four-System VCS Cluster

    2 VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    21/224

    VCS Basics

    Multiple Systems

    VCS runs in a replicated state on each system in the cluster. A private network enables the

    systems 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.)

    Fully Shared Storage Distributed Shared Storage

    Two Examples of Shared Storage Configurations

    Chapter 1, Introduction 3

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    22/224

    VCS Basics

    LLT and GAB

    VCS uses two components, LLT and GAB, to share data over private networks among

    systems. These components provide the performance and reliability required by VCS.

    LLT (Low Latency Transport) provides fast, kernel-to-kernel communications, andmonitors network connections. The system administrator configures LLT by creatingthe configuration files /etc/llthosts, which lists all the systems in the cluster, and/etc/llttab, which describes the local systems private network links to the othersystems in the cluster.

    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 (/etc/gabtab).

    See Verifying LLT and GAB Configuration Files on page 93.

    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 80.

    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 onone of the shared disks. If one of the network connections fails, two channels remain. If

    both network connections fail, the condition is in jeopardy, but connectivity remains viathe heartbeat disk.

    4 VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    23/224

    VCS Basics

    Public Network

    VCS Private Network:

    Shared Disks

    sysA sysB

    Partition with VCSHeartbeat Region

    Two Ethernet Connections

    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:

    When an unseeded system communicates with a seeded system. When all systems in the cluster are unseeded and able to communicate with each

    other.

    VCS requires that you declare the number of systems to participate in the cluster. Whenthe last system is starts and joins the cluster, the cluster seeds and starts VCS on allsystems. Systems can then be brought down and restarted in any combination. Seedingremains in effect as long as at least one instance of VCS is running somewhere in thecluster. Manual seeding is required only to run VCS from a cold start (all systems down)

    when one or more systems of the cluster are unavailable. VCS does not start servicegroups on a system until it is seeded.

    Chapter 1, Introduction 5

    VCS B i

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    24/224

    VCS Basics

    6 VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    25/224

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

    installing the VCS 4.0 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 4.0. If you cannot use the provided utilities to install or upgrade VCS, refer toManually Installing and Configuring VCS on page 69, or Manually Upgrading VCS toRelease 4.0 on page 129.

    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 Disabling the abort sequence Setting the Path Variable Enabling ssh/rsh Communication between systems Preparing NFS Services Obtaining VCS License Keys Preparing Cluster Information

    7

    Hardware Requirements for a VCS Cluster

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    26/224

    Hardware Requirements for a VCS Cluster

    Hardware Requirements for a VCS Cluster

    A VCS cluster requires the following hardware:

    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 support applicationsthat migrate between systems in the cluster.

    Disk space Each VCS system must have at least 180 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 additional interfaces arerecommended.

    Fibre Channel or VCS requires at least one built-in SCSI adapter per system to access theSCSI host bus operating system disks, and at least one additional SCSI or Fibre Channeladapters Host Bus Adapter per system for shared data disks.

    RAM Each VCS system requires at least 256 megabytes.

    8 VERITAS Cluster Server Installation Guide

    Supported Software

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    27/224

    Supported Software

    Supported Software

    Solaris 2.6, 7, 8 (32-bit and 64-bit), and 9 (32-bit and 64-bit) operating systems For each platform, we recommend applying the latest cumulative operating system

    patches available from Sun. See the following site:

    http://sunsolve.Sun.COM

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

    VERITAS Volume Manager (VxVM), 3.2, 3.5, 4.0 VERITAS File System (VxFS) 3.4 Patch 2, 3.5, 4.0

    Setting the PATH Variable

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

    /opt/VRTS/bin, and /opt/VRTSvcs/bin directories. Add these directories to yourPATH environment variable:

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

    $ PATH=/sbin:/usr/sbin:/opt/VRTS/bin:/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/VRTS/bin:/opt/VRTSvcs/bin:$PATH

    Chapter 2, Preparing to Install VCS 4.0 9

    Setting Up the Private Network

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    28/224

    g p

    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.

    During the process of setting up heartbeat connections, note that a chance for datacorruption exists if a failure removes all communications between the systems andstill leaves the systems running and capable of accessing shared storage.

    Public Network

    Private NetworkPrivate

    Public Network

    Network

    Hubs

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

    3. Configure the Ethernet devices used for the private network such that theauto-negotiation protocol is not used. This helps ensure a more stable configurationwith cross-over cables.

    You can do this in one of two ways: by editing the /etc/system file to disableauto-negotiation on all Ethernet devices system-wide, or by creating a qfe.conf file

    in the /kernel/drv directory to disable auto-negotiation for the individual devicesused for private network. Refer to the Sun Ethernet driver product documentation forinformation on these methods to configure device driver parameters.

    4. 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.

    10 VERITAS Cluster Server Installation Guide

    Setting Up Shared Storage

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    29/224

    g p g

    The installvcs script, described in Using the VCS Installation Utilities onpage 21, configures the private network in the cluster during installation. If you areinstalling VCS manually, refer to Manually Installing and Configuring VCS on

    page 69 for information about configuring LLT for the private network links.

    Using Network Switches

    Network switches may be used in place of hubs. However, by default, Sun systems assignthe same MAC address to all interfaces. Thus, connecting two or more interfaces to anetwork switch can cause problems. For example, if IP is configured on one interface and

    LLT on another, and both interfaces are connected to a switch (assuming separateVLANs), the duplicate MAC address on the two switch ports can cause the switch toincorrectly redirect IP traffic to the LLT interface and vice-versa. To avoid this, configurethe system to assign unique MAC addresses by setting the eeprom(1M) parameterlocal-mac-address? to true.

    Note Because of their performance characteristics, network switches are recommendedfor clusters supporting the VERITAS Storage Foundation Cluster File System and

    VERITAS Storage Foundation for Oracle RAC, which make extensive use of theprivate cluster interconnects for distributed locking. See the VERITAS Cluster ServerUsers Guide and review the chapter on VCS performance considerations.

    Setting Up Shared Storage

    The following sections describe setting up SCSI and Fibre Channel devices that are sharedamong the cluster systems.

    If you intend to use VCS I/O fencing, the disks you use must support SCSI-III persistentreservations. In addition, you must configure a coordinator disk group. See Setting UpI/O Fencing on page 107 for information on verifying SCSI-III persistent reservationsupport. See also the VERITAS Cluster Server Users Guide for a description of I/O fencing.

    Chapter 2, Preparing to Install VCS 4.0 11

    Setting Up Shared Storage

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    30/224

    Setting Up Shared Storage: SCSI Disks

    When SCSI devices are used for storage shared between nodes, the SCSI address, or SCSI

    initiator ID, of each node must be unique. Since each node typically has the default SCSIaddress of 7, the addresses of one or more nodes must be changed to avoid a conflict. Inthe following example, two nodes share SCSI devices. The SCSI address of one node ischanged to 5 by using nvedit commands to edit the nvramrc script.

    1. Install the required SCSI host adapters on each node that connects to the storage, andmake cable connections to the storage. Refer to the documentation shipped with thehost adapters, the storage, and the systems.

    2. With both nodes powered off, power on the storage devices.

    3. Power on one system, but do not allow it to boot. Halt the system, if necessary, so thatyou can use the ok prompt. (Note that, to avoid address conflicts, it is important thatonly one system be running at a time.)

    4. Find the paths to the host adapters:

    {0} ok show-disks...b) /[email protected],0/QLGC,[email protected],10000/sd

    The example output shows the path to one host adapter. You must include the pathinformation, excluding the /sd directory, in the nvramrc script (see step 5). Thepath information varies from system to system.

    5. Edit the nvramrc script on to change the scsi-initiator-id to 5. (The Solaris

    OpenBoot 3.x Command Reference Manual contains a full list of nvedit commands andkeystrokes.) For example:

    {0} ok nvedit

    As you edit the script, note the following points:

    Each line is numbered, 0:, 1:, 2:, and so on, as you enter the nvedit commands. On the line where the scsi-initiator-id is set, insert exactly one space after

    the first quotation mark and before scsi-initiator-id.

    In this example, edit the nvramrc script as follows:

    0: probe-all1: cd /[email protected],0/QLGC,[email protected],100002: 5 " scsi-initiator-id" integer-property3: device-end4: install-console

    5: banner6:

    12 VERITAS Cluster Server Installation Guide

    Setting Up Shared Storage

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    31/224

    6. Store the changes you make to the nvramrc script. The changes you make aretemporary until you store them.

    {0} ok nvstoreIf you are not sure of the changes you made, you can re-edit the script without risk

    before you store it. You can display the contents of the nvramrc script by entering:

    {0} okprintenv nvramrc

    You can re-edit the file to make corrections:

    {0} ok nvedit

    Or, if necessary, discard the changes by entering:

    {0} ok nvquit

    7. Instruct the OpenBoot PROM Monitor to use the nvramrc script on the node.

    {0} ok setenv use-nvramrc? true

    8. Reboot the node. Halt the system, if necessary, so that you can use the ok prompt.

    9. Verify that the scsi-initiator-id has changed. Go to the ok prompt. Use theoutput of the show-disks command to find the paths for the host adapters. Then,display the properties for the paths. For example:

    {0} ok show-disks...b) /[email protected],0/QLGC,[email protected],10000/sd{0} ok cd /[email protected],0/QLGC,[email protected],10000{0} ok .propertiesscsi-initiator-id 00000005

    Permit the system to continue booting.

    10. Boot the second node, halting the system, if necessary, to use the ok prompt. Verifythat the scsi-initiator-id is 7. Use the output of the show-disks command tofind the paths for the host adapters. Then, display the properties for that paths. Forexample:

    {0} ok show-disks...b) /[email protected],0/QLGC,[email protected],10000/sd{0} ok cd /[email protected],0/QLGC,[email protected],10000{0} ok .propertiesscsi-initiator-id 00000007

    Permit the system to continue booting.

    If you have more than two systems sharing the SCSI bus, use the same procedure, makingsure that the storage devices are powered on before any of the systems, and that only onenode is running at one time until each nodes address is set to a unique value.

    Chapter 2, Preparing to Install VCS 4.0 13

    Setting Up Shared Storage

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    32/224

    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 all systems from seeing all shared devices required to run the criticalapplication.

    3. Boot each system with the reconfigure devices option:

    ok boot -r

    4. Once all 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 mustappear, but device nodes (c#t#d#s#) may differ.

    If Volume Manger is not being used, the same number of external disk devicesmust appear and device nodes must be identical for all devices on all systems.

    14 VERITAS Cluster Server Installation Guide

    Disabling the Abort Sequence on SPARC Systems

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    33/224

    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:

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

    BREAK on the serial console input device.Each command can then followed by a response of go 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 not exist):

    KEYBOARD_ABORT=disable

    2. Reboot.

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

    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. If ssh 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 42 or Manually Installing VCS onpage 69.

    Chapter 2, Preparing to Install VCS 4.0 15

    Preparing NFS Services

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    34/224

    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_deviceThe variable block_device refers to a partition on which a file system is mounted for

    export 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

    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 4.0 and,when installation succeeds, reconcile the major numbers using the haremajorcommand. Refer to Reconciling Major/Minor Numbers for NFS Shared Disks onpage 175 to reconcile minor numbers that do not match.

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

    16 VERITAS Cluster Server Installation Guide

    Obtaining License Keys for VCS

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    35/224

    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 have completedthe licensing process. Use either method described in the following two sections to obtaina valid license key.

    Using the VERITAS vLicenseTM Web Site to Obtain License Key

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

    The License Key Request Form has all the information needed to establish a User Accounton vLicense and generate your license key. The License Key Request Form is a one-pageinsert included 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 theform for 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:

    Your VERITAS customer number Your order number Your serial numberFollow 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 License Key

    If you do not have Internet access, you can fax the License Key Request Form to VERITAS.Be advised that faxing the form generally requires several business days to process in

    order to provide a license key. Before faxing, sign and date the form in the appropriatespaces. Fax it to the number shown on the form.

    Chapter 2, Preparing to Install VCS 4.0 17

    Patches Required for Java Run Time Environment from Sun

    http://vlicense.veritas.com/http://vlicense.veritas.com/
  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    36/224

    Patches Required for Java Run Time Environment from Sun

    The GUI modules for VCS use the Java Run Time Environment from Sun Microsystems.

    You need to obtain and install the latest Solaris patches to enable the modules to functionproperly. You can obtain the patches from:

    http://java.sun.com/j2se/1.4.2/download.html

    Preparing to Use installvcs

    As you run the installvcs utility, be prepared to answer prompts so that theinstallation can proceed smoothly and successfully. Use the following sections to guideyou in preparing for the installation of VCS 4.0.

    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 49. Later,when you have cluster information available, use the procedures located in Usinginstallvcs to Configure Without Installation on page 49.

    License Key

    Be prepared to enter your VCS license key when prompted. See Obtaining License Keysfor VCS on page 17.

    Choosing Optional PackagesThe optional packages included with VCS include:

    Manual pages for VCS commands (VRTSvcsmn) VCS documentation (VRTSvcsdc) I/O fencing (VRTSvxfen) VERITAS Enterprise Administrator (VRTSobgui) The VCS simulator (VRTSvcssim) The VCS Cluster Manager (VRTScscm)

    18 VERITAS Cluster Server Installation Guide

    Preparing to Use installvcs

    http://java.sun.com/j2se/1.4.2/download.htmlhttp://java.sun.com/j2se/1.4.2/download.html
  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    37/224

    I/O Fencing (Optional)

    If the I/O fencing option is selected, the installvcs utility installs the VCS I/O fencing

    driver,VRTSvxfen. After completing VCS installation, you must do the following to usethe I/O fencing feature:

    Install a version of VERITAS Volume Manager (VxVM) that licenses SCSI-IIIpersistent reservations.

    Use supported disks for shared storage and set up a disk group of coordinator disks.These activities are described in Setting Up I/O Fencing on page 107.

    The VCS Users Guide describes I/O fencing in detail. I/O fencing protects the data onshared disks. When nodes in a cluster detect a change in cluster membership that couldindicate a split brain condition, the fencing operation proceeds to determine which nodesare to retain access to the shared storage and which nodes are to be ejected from thecluster, thus preventing possible data corruption.

    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)and contain only the characters a through z, A through Z, and 1through 0, hyphen (-),and underscore (_).

    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 or demo license key. Device names of the NICs used by the private networks among systems.

    Virtual IP Address for 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 a

    resource for use by the ClusterService group that includes the VCS Cluster Manager(Web Console). The Cluster Virtual IP address can fail over to another cluster

    system, making the Web Console highly available.

    The subnet used with the Virtual Address.Chapter 2, Preparing to Install VCS 4.0 19

    Preparing to Use installvcs

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    38/224

    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.

    The VCS Users Guide describes SMTP notification in detail; see the chapter on notification.

    Information for Configuring SNMP Notification

    You have the option to configure SNMP trap notification of VCS events by the VCS

    Notifier 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 levels

    of severity: Information, Warning, Error, and SevereError.

    The VCS Users Guide describes SNMP notification in detail; see the chapter onnotification.

    Information for the Global Cluster Option

    You have the option to configure the Global Cluster feature. The Global Cluster featureprovides the ability to fail over applications between geographically distributed clusters

    when disaster occurs. The Global Cluster feature requires a license that you can addduring the installation.

    If you choose the Global Cluster option, the installer allows you to choose whether or notto use the same NIC, virtual IP address, and netmask as are configured for theClusterService group, which are the defaults. If you choose not to use the samenetworking information, you must specify appropriate values for the NIC, virtual IPaddress, and netmask when you are prompted.

    20 VERITAS Cluster Server Installation Guide

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    39/224

    Using the VCS Installation Utilities 3You can install VERITAS Cluster Server on clusters of up to 32 systems. The following

    sections show an example installation on two systems, north and south. You can installthe product two ways:

    The VERITAS Installation Menu (see Running the VERITAS Installer on page 25) The installsvcs script (see Running the installvcs Utility on page 25)

    VCS Installation Utility

    The installvcs program, which can be run at the command line, or accessed by usingthe VERITAS Installation Menu, manages the following tasks:

    Licensing of VCS Installing VCS packages on multiple cluster systems Configuring VCS, creating several detailed configuration files on each system Starting VCS processesThe uninstallvcs program, a companion to installvcs, uninstalls VCS packages.

    Optional Features of the installvcs Utility

    The installvcs utility can also perform the following actions:

    Check the systems to verify they meet the requirements to install VCS. Upgrade VCS to version 4.0 if VCS currently runs on a cluster. Upgrade cluster systems running GCM 1.2/3.5 to VCS 4.0, provided the GCM

    configuration is standard, that is, created with the aid of GCM configuration wizards;customized GCM configurations require the assistance of a VERITAS consultant.

    Install VCS packages without configuring VCS, or, configure VCS without installingpackages.

    Perform secure or automated installations using values stored in a configuration file.21

    Using the installvcs Utility

    U i h i ll U ili

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    40/224

    Using the installvcs Utility

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

    its prompts, it installs VCS packages on each cluster system and configures VCS and itscommunication services. During the installation, you can select the optional I/O fencingfeature and optional VCS documentation packages, and choose to configure the optionalWeb-based Cluster Manager (Web Console), the optional SNMP and SMTP notificationfeatures in the cluster, and the optional wide area Global Cluster feature. See Preparingto Use installvcs on page 18 for highlights of the information for which installvcsprompts you.

    Interacting with the installvcs Script

    As you run the script, you are prompted to answer yes or no questions that are typicallyfollowed by a set of responses resembling[y, n, q, ?] (y). The response withinparentheses is the default, which you may select by pressing Return. By entering the ?character, you can get help to answer the prompt. By entering q, you can quit theinstallation.

    Note Installation of VCS packages takes place only after you have confirmed theinformation. However, partially installed VCS files must be removed beforerunning the installvcs utility again. See Using uninstallvcs on page 65.

    At some points during the installation, the installer prompts you to type information andexpects your responses to be within a certain range or in a specific format. The installerprovides examples. If you are prompted to enter an item from a list, enter your selection

    exactly as it is shown in the list.

    When the installer prompts you to answer a series of questions related to a configurationactivity, you can enter the b character to return back to the first prompt in the series.When the installer displays a set of information items you have entered, you areprompted to confirm it. If you answer n, the script lets you re-enter all of theinformation for the set.The installvcs utility does not configure GAB Disk heartbeatregions. This procedure must be done manually. Refer to Configuring Membership

    Heartbeat Regions on Disk (optional) on page 80.

    22 VERITAS Cluster Server Installation Guide

    Using the installvcs Utility

    U di VCS U i th i t ll S i t

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    41/224

    Upgrading VCS Using the installvcs Script

    If you are currently running a VCS cluster, including a cluster running GCM 1.2/3.5, you

    can run the installer to upgrade to VCS 4.0. The utility detects the current configurationand prompts you to indicate whether you want to upgrade. While the installer is not ableto verify the validity of the existing configuration, it is able to run extensive upgraderequirement checks before proceeding.

    If you are running GCM 1.2 or 3.5, review this section on using the installvcsutility and then see Upgrading from GCM 1.2 or 3.5 to VCS 4.0 with the GlobalCluster Option on page 56.

    If you are running VCS 1.3.0, 2.0, or 3.5, see Using installvcs to Upgrade to VCS 4.0on page 49.

    Chapter 3, Using the VCS Installation Utilities 23

    Example VCS Installation

    Example VCS Installation

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    42/224

    Example VCS Installation

    In the example installation that follows, all optional features are chosen, including the

    Cluster Manager, SMTP notification, SNMP notification, and Global Cluster option.Thefollowing illustration shows two systems, north and south, on which VCS is to run. Forthis example, the clusters name is vcs_cluster2 and the clusters ID is 7.

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

    north southqfe:0 qfe:0

    qfe:1 qfe:1Cluster Name: vcs_cluster2

    VCS Private NetworkCluster ID: 7

    hme0 hme0

    Public Network

    Mounting the Software Disc1. Log in as root user on a system connected by the network to the systems where VCS is

    to be installed. The system from which VCS is installed need not be part of the cluster.

    Note If you are running installvcs to upgrade an existing cluster running GCM,mount the CD and run the installer from the GCM master node. See Upgradingfrom GCM 1.2 or 3.5 to VCS 4.0 with the Global Cluster Option on page 56.

    2. Insert the software disc with the VCS software into a drive connected to the system.The Solaris volume-management software automatically mounts the CD as/cdrom/cdrom0. Type the command:

    # cd /cdrom/cdrom0

    24 VERITAS Cluster Server Installation Guide

    Example VCS Installation

    Running the VERITAS Installer

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    43/224

    Running the VERITAS Installer

    You can start the installation of VCS two ways:

    Use the installvcs utility directly; skip to Running the installvcs Utility, or Use the VERITAS installer utility on the CD-ROM. Refer to the following procedure:To use the installer:

    1. Log in as root user with the CD-ROM mounted at /cdrom/cdrom0.

    2. Enter the following command to start the installer:

    # ./installer

    3. The installer begins by displaying copyright information.

    4. From the opening Selection Menu, choose I to choose Install/Upgrade a Product.

    5. From the displayed list of products to install, choose: VERITAS Cluster Server.

    6. When the installation program begins, it starts the product installation script bypresenting a copyright message and prompting you for the names of the systemswhere you want to install VCS. Skip to step 4 on page 26 to continue the installation.

    Running the installvcs Utility

    With the software disc mounted, you can start the installvcs utility. If you currentlyhave VCS 1.3.0, 2.0. or 3.5 installed on your cluster systems, the utility can upgrade thesystems to 4.0. See Using installvcs to Upgrade to VCS 4.0 on page 49.

    Using the installvcs -precheck Option

    Before beginning the installation of VCS software, you can verify that the systems onwhich you want to install are ready for installation. The command to start thepre-installation check is:

    installvcs -precheck system1 system2 ...For example:

    # ./installvcs -precheck north south

    The utility proceeds in an non-interactive mode, examining the systems for licenses,packages, disk space, and system-to-system communications. The utility displays theresults of the check and saves the results of the check in a log file.

    Chapter 3, Using the VCS Installation Utilities 25

    Example VCS Installation

    Starting Software Installation

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    44/224

    Starting Software Installation

    1. Change to the directory where you can start the installvcs utility:

    # cd cluster_server

    2. Start the VCS installation utility by entering:

    # ./installvcs

    3. The installer begins with the following introduction:

    VERITAS CLUSTER SERVER 4.0 INSTALLATION PROGRAM

    Copyright (c) 2003 VERITAS Software Corporation. All rightsreserved.

    VERITAS, the VERITAS Logo and all other VERITAS product namesand slogans are trademarks or registered trademarks of VERITASSoftware Corporation. VERITAS and the VERITAS Logo Reg. U.S.Pat. & Tm. Off. Other product names and/or slogans mentioned

    herein may be trademarks or registered trademarks of theirrespective companies.

    4. The utility prompts for the names of the systems in the cluster.

    Enter the system names separated by spaces on which to installVCS: north south

    26 VERITAS Cluster Server Installation Guide

    Example VCS Installation

    Performing Initial System Checks

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    45/224

    Performing Initial System Checks

    5. The installer verifies that the systems you specify use the proper operating system

    and that they are configured with ssh or rsh for system-to system communication. Ifthe installer finds ssh binaries, it confirms that ssh is set up to operate withoutrequests for passwords or passphrases.

    Checking OS version on north ......................... SunOS 5.9Checking VRTSvcs package ........................ not installed

    Verifying communication with south ............ ping successfulAttempting rsh with south ....................... rsh successfulAttempting rcp with south ....................... rcp successfulChecking OS version on south ........................ SunOS 5.9Checking VRTSvcs package ........................ not installedCreating log directory on south .......................... Done

    Logs for installvcs are being created in/var/tmp/installvcsdate_time.

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

    systems.

    Initial system check completed successfully.

    Installing the VERITAS Infrastructure Packages

    6. The infrastructure packages are installed after the installer verifies they are not

    already installed and that disk space is available:Installing VERITAS Infrastructure packages on north:

    Checking VRTSvlic package .................... not installedChecking VRTScpi package ..................... not installedChecking file system space ........ required space availableInstalling VRTScpi 4.0.4 on north ..................... DoneInstalling VRTSvlic 3.02.005d on north ................ Done

    Installing VERITAS Infrastructure packages on south:Checking VRTSvlic package .....................not installedChecking VRTScpi package ..................... not installedChecking file system space ........ required space availableCopying VRTScpi package to south....................... DoneInstalling VRTScpi 4.0.4 on south...................... DoneCopying VRTSvlic.tar.gz to south ...................... DoneInstalling VRTSvlic 3.02.005d on south ................ Done

    VERITAS Infrastructure packages installed successfully.

    Chapter 3, Using the VCS Installation Utilities 27

    Example VCS Installation

    Verifying VCS Licenses

  • 8/14/2019 VERITAS Cluster Server 4.0 Install guide

    46/224

    y g

    7. The installer checks for VCS license keys currently in place on each system. You can

    enter a VCS license and add licenses for additional product features, such as theGlobal Cluster option.

    Each system requires a VCS product license before installation.License keys for additional product features should also be addedat this time.

    Some license keys are node locke


Recommended