Symantec 5 Verifying the cluster

To verify GAB

1To verify that GAB operates, type the following command on each node:

/sbin/gabconfig -a

2Review the output of the command:

■If GAB operates, the following GAB port membership information is

returned:

GAB Port Memberships

===================================

Port a gen a36e0003 membership 01

Port h gen fd570002 membership 01

■If GAB does not operate, the command does not return any GAB port

membership information:

GAB Port Memberships

===================================

■Ifonly one network is connected, the command returns the following GAB

port membership information:

GAB Port Memberships

===================================

Port a gen a36e0003 membership 01

Port a gen a36e0003 jeopardy 1

Port h gen fd570002 membership 01

Port h gen fd570002 jeopardy 1

Verifying the cluster

Verify the status of the cluster using the hastatus command. This command

returns the system state and the group state.

Refer to the hastatus(1M) manual page.

Referto the Veritas Cluster Server User's Guide for a description of system states

and the transitions between them.

117Verifyingthe VCS installation

VerifyingLLT, GAB, and cluster operation

Contents

Main Veritas Cluster Server Installation Guide Legal Notice Page Technical Support Contacting Technical Support Licensing and registration Customer service Documentation feedback Maintenance agreement resources Additional enterprise services Contents Technical Support Chapter 1 Introducing Veritas Cluster Server Chapter 2 Planning to install VCS Chapter 3 Preparing to install VCS Chapter 4 Installing and configuring VCS Chapter 5 Configuring VCS clusters for data integrity Chapter 6 Verifying the VCS installation Chapter 7 Adding and removing cluster nodes Chapter 8 Installing VCS on a single node Chapter 9 Uninstalling VCS Appendix A Advanced VCS installation topics Index Page Introducing Veritas Cluster Server About Veritas Cluster Server About VCS basics About multiple nodes About shared storage About LLT and GAB About network channels for heartbeating About preexisting network partitions About VCS seeding About VCS features Veritas Installation Assessment Service About VCS notifications About global clusters About I/O fencing About VCS optional components About Symantec Product Authentication Service (AT) About Cluster Manager (Java Console) About Veritas Cluster Server Management Console About VCS Simulator Page Page Planning to install VCS About planning to install VCS Hardware requirements Required disk space Supported operating systems Required Linux RPMs for VCS Supported software Page Preparing to install VCS About preparing to install VCS Preparing to configure the clusters in secure mode Page Figure 3-1 Workflow to configure VCS cluster in secure mode Table 3-1 lists the preparatory tasks in the order which the AT and VCS administrators must perform. Table 3-1 Preparatorytasks to configure a cluster in secure mode Who performs this task Tasks Installing the root broker for the security infrastructure 9 10 11 12 Creating authentication broker accounts on root broker system 1 2 3 Creating encrypted files for the security infrastructure 1 2 3 4 each node in the cluster. 5 6 Preparing the installation system for the security infrastructure Performing preinstallation tasks Obtaining VCS license keys Setting up the private network 1 2 3 4 Configuring SuSE network interfaces 1 2 3 4 5 1 Setting up inter-system communication Setting up ssh on cluster systems Configuring ssh 1 2 3 4 5 Setting up shared storage Setting the PATH variable Setting the MANPATH variable Setting the kernel.panic tunable 1 2 Optimizing LLT media speed settings on private NICs Guidelines for setting the media speed of the LLT interconnects Mounting the product disc 1 2 3 4 Page Installing and configuring VCS About installing and configuring VCS Getting your VCS installation and configuration information ready mode, you need: Optional VCS RPMs The optional VCS RPMs include the following packages: About the VCS installation program Optional features of the installvcs program Interacting with the installvcs program About installvcs program command options Note: Table 4-2 installvcsoptions (continued) DescriptionOption and Syntax Installing VCS using installonly option Configuring VCS using configure option Installing and configuring VCS 5.0 RU3 Overview of tasks Table 4-3 Installationand configuration tasks Starting the software installation Youcan install VCS using the Veritas product installer or the installvcs program. Specifying systems for installation 1 2 Licensing VCS 1 2 3 4 Choosing VCS RPMs for installation 1 2 3 Choosing to install VCS RPMs or configure VCS Starting the software configuration 1 2 3 Specifying systems for configuration 1 2 Configuring the basic cluster 1 2 3 4 5 6 Configuring the cluster in secure mode 1 2 3 Adding VCS users 1 2 3 4 5 1 2 3 4 5 Configuring SNMP trap notification 1 2 3 4 Configuring global clusters 1 2 3 4 Installing VCS RPMs Creating VCS configuration files Verifying the NIC configuration Starting VCS Completing the installation About enabling LDAP authentication for clusters that run in secure mode Page Installing the Java Console Software requirements for the Java Console Hardware requirements for the Java Console Installing the Java Console on Linux for IBM Power 1 2 3 4 Installing VCS Simulator Software requirements for VCS Simulator Installing VCS Simulator on UNIX systems Installing VCS Simulator on Windows systems 1 2 Reviewing the installation Verifying the cluster after installation Verifying and updating licenses on the system Checking licensing information on the system 1 2 Updating product licenses using vxlicinst Replacing a VCS demo license with a permanent license 1 2 3 Accessing the VCS documentation Configuring VCS clusters for data integrity About configuring VCS clusters for data integrity About I/O fencing components About data disks About coordination points About setting up disk-based I/O fencing Page Page Preparing to configure disk-based I/O fencing Initializing disks as VxVM disks 1 2 3 4 5 Identifying disks to use as coordinator disks 1 2 Checking shared disks for I/O fencing Verifying that the nodes have access to the same disk 1 2 Testing the disks using vxfentsthdw utility 1 2 3 4 5 6 7 Setting up disk-based I/O fencing manually Setting up coordinator disk groups 1 2 3 Creating I/O fencing configuration files 1 2 3 Modifying VCS configuration to use I/O fencing 1 2 3 4 Verifying I/O fencing configuration Removing permissions for communication Page Verifying the VCS installation About verifying the VCS installation About the LLT and GAB configuration files Page About the VCS configuration file main.cf Sample main.cf file for VCS clusters Page Sample main.cf file for global clusters In the following main.cf file example, bold text highlights global cluster specific entries. Page Verifying the LLT, GAB, and VCS configuration files 1 2 Verifying LLT, GAB, and cluster operation 1 2 Verifying LLT 1 2 3 4 5 6 Verifying GAB 1 2 Verifying the cluster 1 2 Verifying the cluster nodes Page Page Adding and removing cluster nodes About adding and removing nodes Adding a node to a cluster Setting up the hardware 1 2 Preparing for a manual installation when adding a node Installing VCS RPMs for a manual installation Adding a license key Checking licensing information on the system Setting up the node to run in secure mode 1 2 3 4 Configuring the authentication broker on node saturn 1 2 3 4 5 Configuring LLT and GAB 1 2 3 1 2 1 Adding the node to the existing cluster 1 2 Starting VCS and verifying the cluster Removing a node from a cluster Table 7-3 Tasksthat are involved in removing a node Verifying the status of nodes and service groups Start by issuing the following commands from one of the nodes to remain, node galaxy or node nebula. 1 2 Deleting the departing node from VCS configuration 1 2 3 4 5 6 7 8 9 10 Modifying configuration files on each remaining node 1 2 Removing security credentials from the leaving node 1 2 Unloading LLT and GAB and removing VCS on the departing node 1 2 3 4 5 Installing VCS on a single node About installing VCS on a single node Creating a single-node cluster using the installer program Preparing for a single node installation Starting the installer for the single node cluster Creating a single-node cluster manually Setting the path variable for a manual single node installation Installing the VCS software manually on a single node Renaming the LLT and GAB startup files Modifying the startup files Verifying single-node operation 1 2 Adding a node to a single-node cluster Setting up a node to join the single-node cluster 1 2 Installing VxVM or VxFS if necessary Installing and configuring Ethernet cards for private network Configuring the shared storage Bringing up the existing node 5 6 7 Installing the VCS software manually when adding a node to a single node cluster Configuring LLT Setting up /etc/llthosts Setting up /etc/llttab LLT directives Table 8-4 LLTdirectives DescriptionDirective For more information about LLT directives, refer to the llttab(4) manual page. Additional considerations for LLT Configuring GAB when adding a node to a single node cluster Starting LLT and GAB 1 2 Reconfiguring VCS on the existing node Verifying configuration on both nodes Page Page Uninstalling VCS About the uninstallvcs program Preparing to uninstall VCS Uninstalling VCS 5.0 RU3 Removing VCS 5.0 RU3 RPMs 1 2 3 4 Running uninstallvcs from the VCS 5.0 RU3 disc Page Advanced VCS installation topics Using the UDP layer for LLT When to use LLT over UDP Configuring LLT over UDP A Broadcast address in the /etc/llttab file The link command in the /etc/llttab file The set-addr command in the /etc/llttab file Selecting UDP ports Configuring the netmask for LLT Configuring the broadcast address for LLT Sample configuration: direct-attached links Page Sample configuration: links crossing IP routers Performing automated VCS installations 1 2 Syntax in the response file Example response file Response file variable definitions Table A-3 Responsefile variables Page Page Page Page Installing VCS with a response file where ssh or rsh are disabled 1 2 3 4 5 6 7 8 9 Index A C D E F G H I J M N O P R U V