VERITAS Cluster Server

3.5 for Solaris

Lesson 2
Installing VERITAS Cluster Server

Overview
Troubleshooting

Using Volume
Manager
Event
Notification
Service Group
Basics
Introduction
VCS_3.5_Solaris_R3.5_2002091
5

Cluster
Communication

Faults and
Failovers
Preparing
Resources

Terms
and
Concepts

Installing
Applications
Resources
and Agents

Installing
VCS

Managing
Cluster
Services

NFS
Resources
Using
Cluster
Manager
2-2

Objectives
After completing this lesson, you will be able to:
Describe VCS software, hardware, and licensing
prerequisites.
Describe the general VCS hardware
requirements.
Configure SCSI controllers for a shared disk
storage environment.
Add VCS executable and manual page paths to
the environment variables.
Install VCS using the installation script.
VCS_3.5_Solaris_R3.5_2002091
5

2-3

Software and Hardware

Requirements
Software:

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

Recommended:
Solaris patches
VERITAS Volume Manager (VxVM) 3.1.1 P2 and P3, 3.2, and
3.5
VERITAS File System (VxFS) 3.3.x, 3.4 P2, and 3.5

Hardware:
Check latest VCS release notes.
Contact VERITAS Support.

Licenses:
Obtain license keys using VERITAS vLicense or by contacting
your sales representative.
Contact VERITAS Support for upgrades.
VCS_3.5_Solaris_R3.5_2002091
5

2-4

General Hardware Layout

Private Ethernet Heartbeat Links
OS Disk
NICS

NICS

OS

SCSI1

SCSI2
Shared Data
Disks
SCSI2

SCSI1

NICS

NICS

Public Network
SYSTEM A
VCS_3.5_Solaris_R3.5_2002091
5

SYSTEM B
2-5

SCSI Controller Configuration

OS Disk
scsi-initiator-id

SCSI Target
IDs:
2

SCSI1
3

Shared Data Disks

OS
Disk

7
4
SCSI2

SYSTEM A
VCS_3.5_Solaris_R3.5_2002091
5

0
7

1
SCSI2

SCSI1 5

scsi-initiator-id

SYSTEM B
2-6

SCSI Controller Setup

Use unique SCSI IDs for each system.
Check the scsi-initiator-id setting
using the eeprom command.
Change the scsi-initiator-id if needed.
Controller ID can also be changed on a
controller-by-controller basis.

VCS_3.5_Solaris_R3.5_2002091
5

2-7

Setting Environment Variables

For Bourne or Korn shell (sh or ksh):
PATH
PATH=$PATH:/sbin:/usr/sbin:/opt/VRTSvcs/bin
export PATH
MANPATH
MANPATH=$MANPATH:/opt/VRTS/man
export MANPATH
Add to /.profile

For C shell (csh or tcsh):

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

MANPATH
setenv MANPATH $MANPATH:/opt/VRTS/man
VCS_3.5_Solaris_R3.5_2002091
5

2-8

The installvcs Utility

Uses pkgadd to install the VCS packages on all the systems in
the cluster:
VRTScscm

VRTSvcsag

VRTSvlic

VRTSgab

VRTSvcsmg

VRTSweb

VRTSllt

VRTSvcsmn

VRTSvcsdc

VRTSperl

VRTSvcsor

VRTSvcs

VRTSvcsw

Requires remote root access to other systems in the cluster

while the script is being run (/.rhosts file)
Note: Can remove .rhosts files after VCS installation.
Configures two private network links for VCS communications
Brings the cluster up without any services
VCS_3.5_Solaris_R3.5_2002091
5

2-9

Installation Settings
Information required by installvcs:

Cluster name
Cluster number
System names
License key
Network ports for private network
Web Console configuration:
Virtual IP address
Subnet mask
Network interface
SMTP/SNMP notification configuration (discussed later)
VCS_3.5_Solaris_R3.5_2002091
5

2-10

Starting VCS Installation

# ./installvcs
Enter the names of the systems on which VCS is to be
installed separated by spaces (example: system1
system2): train7 train8
Checking for ssh on train7................ not found
Checking OS version on train7............. SunOS 5.8
Verifying communication with train8. ping successful
Attempting rsh with train8.......... rsh successful
Checking OS version on train8............. SunOS 5.8
Creating /tmp subdirectory on train8...... /tmp
subdirectory created
Using /usr/bin/rsh and /usr/bin/rcp to communicate
with train8
Communication check completed successfully
VCS_3.5_Solaris_R3.5_2002091
5

2-11

Licensing VCS
VCS licensing verification:
Checking train7 ............... No license key found
Enter the license key for train7 : XXXX-XXXX-XXXX-XXXXXXXX-XXX
Valid VCS Single Node Permanent key entered for train7
Registering key XXXX-XXXX-XXXX-XXXX-XXXX-XXX on train7 ..
Done
Checking train8 ............... No license key found
Enter the license key for train8 : XXXX-XXXX-XXXX-XXXXXXXX-XXX
Valid VCS Single Node Permanent key entered for train8
Registering key XXXX-XXXX-XXXX-XXXX-XXXX-XXX on train8 ..
Done
VCS_3.5_Solaris_R3.5_2002091
5

2-12

Configuring the Cluster

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)
Y
Enter the unique Cluster Name: mycluster
Enter the unique Cluster ID number between 0-255:
200

VCS_3.5_Solaris_R3.5_2002091
5

2-13

Configuring the Private Network

Discovering NICs on train7: ..... discovered hme0
qfe0 qfe1 qfe2 qfe3
Enter the NIC for the first private network
heartbeat link on train7 : (hme0 qfe0 qfe1 qfe2 qfe3) hme0
Enter the NIC for the second private network
heartbeat link on train7 : (hme0 qfe1 qfe2 qfe3)
qfe0
Are you using the same NICs for private heartbeat
links on all systems? (Y) Y

VCS_3.5_Solaris_R3.5_2002091
5

2-14

Configuring the 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) Y
Active NIC devices discovered on north: hme0
Enter the NIC for the Cluster Manager (Web Console) to
use on train7: (hme0)
Is hme0 the public NIC used for all systems (Y) Y
Enter the Virtual IP address for the Cluster Manager:
192.168.27.9
Enter the netmask for IP 192.168.27.9: (255.255.255.0)
255.255.255.0
VCS_3.5_Solaris_R3.5_2002091
5

2-15

Completing VCS Installation

Do you want to start the cluster components now? (Y) Y
Starting VCS on train7
Starting LLT ...................................... Started
Starting GAB ...................................... Started
Starting VCS ...................................... Started
Starting VCS on train8
Starting LLT ...................................... Started
Starting GAB ...................................... Started
Starting VCS ...................................... Started
VCS Startup completed successfully

VCS_3.5_Solaris_R3.5_2002091
5

2-16

Summary
You should now be able to:
Describe VCS software, hardware, and licensing
prerequisites.
Describe the general VCS hardware
requirements.
Configure SCSI controllers for a shared disk
storage environment.
Add VCS executable and manual page paths to
the environment variables.
Install VCS using the installation script.
VCS_3.5_Solaris_R3.5_2002091
5

2-17

Lab 2: Installing VCS

OS Disk
scsi-initiator-id

SCSI Target
IDs:

SCSI1 5

0
7

1
SCSI2

SCSI1
3

Shared Data Disks

OS
Disk

scsi-initiator-id

7
4
SCSI2

Train 1

Train 2

# ./installvcs
VCS_3.5_Solaris_R3.5_2002091
5

2-18