# ./installvcs -precheck galaxy nebula | Symantec 5 manual

50Preparing to install VCS Performing preinstallation tasks

To check the systems

1Navigate to the folder that contains the installvcs program. See “Mounting the product disc” on page 49.

2Start the pre-installation check:

# ./installvcs -precheck galaxy nebula

The program proceeds in a noninteractive mode to examine the systems for licenses, RPMs, disk space, and system-to-system communications.

3Review the output as the program displays the results of the check and saves the results of the check in a log file.

Image 50

Symantec 5 manual # ./installvcs -precheck galaxy nebula

Contents

Veritas Cluster Server Installation Guide Veritas Cluster Server Installation Guide Legal Notice Symantec Corporation Ellis Street Mountain View, CA Technical Support Contacting Technical Support Documentation feedback Customer serviceLicensing and registration Maintenance agreement resources Additional enterprise services Contents Contents Chapter Configuring VCS clusters for data integrity Chapter Adding and removing cluster nodes 121 171 Index 173 Contents This chapter includes the following topics About Veritas Cluster ServerAbout VCS basics Example of a four-node VCS cluster About multiple nodesAbout shared storage About network channels for heartbeating See About the LLT and GAB configuration files onAbout LLT and GAB About preexisting network partitions About VCS seeding About VCS notifications About VCS featuresVeritas Installation Assessment Service About global clusters You can add the following optional components to VCS About VCS optional componentsAbout I/O fencing About Symantec Product Authentication Service AT About Cluster Manager Java Console See Preparing to configure the clusters in secure mode onSee Installing the Java Console on About Veritas Cluster Server Management Console About VCS optional components Page 1lists the hardware requirements for a VCS cluster About planning to install VCSHardware requirements Description Required disk spaceHardware requirements for a VCS cluster Supported operating systems Kernel Architecture Required Linux RPMs for VCS Rhel Supported software Planning to install VCS Supported software About preparing to install VCS Preparing to configure the clusters in secure mode 1depicts the flow of configuring VCS cluster in secure mode Workflow to configure VCS cluster in secure mode This task Preparatory tasks to configure a cluster in secure modeTasks # ./installer Installing the root broker for the security infrastructureSee About Symantec Product Authentication Service AT on Venus # vssat showalltrustedcreds Venus # vssat showprpl --pdrtype root \ Creating encrypted files for the security infrastructure Venus # vssat showbrokerhash Addprpl command For example RootBroker # vssat createpkg \ Performing preinstallation tasks Https//licensing.symantec.com Obtaining VCS license keysTask Reference Setting up the private network You can use network switches instead of hubsPage Configuring SuSE network interfaces See About installing and configuring VCS on # cd /etc/sysconfig Run the commandWhere ethX is the interface name For example # ifconfig -a # cd /etc/sysconfig/network Setting up inter-system communication# ifconfig eth0 # ssh-keygen -t dsa Setting up ssh on cluster systemsAccept the default location of ~/.ssh/iddsa # chmod 755 ~/.ssh Setting up shared storageSee About setting up disk-based I/O fencing on # exec /usr/bin/ssh-agent $SHELL # ssh-add For the C Shell csh or tcsh, type Setting the Path variableSetting the Manpath variable Case of a panic, the node will reboot after 10 seconds Setting the kernel.panic tunableOptimizing LLT media speed settings on private NICs # mount -o ro /dev/cdrom /mnt/cdrom Performing automated pre-installation checkMounting the product disc # ./installvcs -precheck galaxy nebula About installing and configuring VCS VCS Example vcscluster27 To configure Veritas Cluster Server you needExample galaxy, nebula Var/tmp/privatedir/roothash To configure VCS clusters in secure mode optional, you needTo configure Smtp email notification optional, you need Optional VCS RPMs To configure Snmp trap notification optional, you needTo configure global clusters optional, you need VRTSvcsmn Manual pages for VCS commands About the VCS installation programOptional features of the installvcs program See About preparing to install VCS on Installvcs command usage takes the following form Interacting with the installvcs programAbout installvcs program command options Optional action Reference Installvcs system1 system2... options Option and Syntax Description Nooptionalpkgs Installing VCS using installonly option Configuring VCS using configure option 3lists the installation and the configuration tasks Installing and configuring VCS 5.0 RU3See Configuring the basic cluster on Overview of tasks Starting the software installation # ./installvcs -rsh Specifying systems for installationStart the installvcs program # cd /clusterserver Licensing VCS See Checking licensing information on the system on Choosing VCS RPMs for installation Enter keys for additional product features Choosing to install VCS RPMs or configure VCS Starting the software configuration See Configuring VCS using configure option on # ./installvcs -configure Specifying systems for configurationConfiguring the basic cluster # cd /dvdrom/clusterserverPage Configuring the cluster in secure mode Root@east.symantecexample.com East.symantecexample.comSymantecexample.com Root/roothash Adding VCS users Configuring Smtp email notificationEnter the user’s name, password, and level of privileges To add a user, enter y at the prompt See Configuring Snmp trap notification on If you do not want to add, answer n Configuring Snmp trap notificationSee Configuring global clusters on Verify and confirm the Smtp notification information Configuring global clusters Verify and confirm the Snmp notification information Installing VCS RPMs See Creating VCS configuration files on Creating VCS configuration files Verifying the NIC configuration Set the Persistentname for all the NICs Completing the installationStarting VCS File description VCS node authentication broker Hardware requirements for the Java Console Installing the Java ConsoleSoftware requirements for the Java Console See Software requirements for the Java Console on Navigate to the folder that contains the RPMs Installing the Java Console on Linux for IBM PowerInstalling the Java Console on a Windows system # cd /mnt/cdrom/distarch/clusterserver/rpms Installing VCS Simulator on Windows systems Installing VCS SimulatorInstalling VCS Simulator on Unix systems Software requirements for VCS Simulator Reviewing the installation Verifying and updating licenses on the system Verifying the cluster after installationSee About verifying the VCS installation on Checking licensing information on the system # cd /opt/VRTS/bin Updating product licenses using vxlicinstReplacing a VCS demo license with a permanent license # hastop -all -force Start VCS on each node Accessing the VCS documentationTo access the VCS documentation # hastart Configuring VCS clusters for data integrity About configuring VCS clusters for data integrity About coordination points About I/O fencing componentsAbout data disks See About data disks on About setting up disk-based I/O fencing 1illustrates the tasks involved to configure I/O fencing Workflow to configure disk-based I/O fencing I/O fencing configuration files include Preparing to configure disk-based I/O fencing Initializing disks as VxVM disks # fdisk -l # vxddladm listsupport all Libnamevidpid Example specifies the CDS format Identifying disks to use as coordinator disksChecking shared disks for I/O fencing See Testing the disks using vxfentsthdw utility on Verifying that the nodes have access to the same diskTesting the shared disks for SCSI-3 # /opt/VRTSvcs/vxfen/bin/vxfentsthdw Testing the disks using vxfentsthdw utilitySee Removing permissions for communication on Dev/sdr If you use rsh for communication# /opt/VRTSvcs/vxfen/bin/vxfentsthdw -n # vxdg init vxfencoorddg sdx sdy sdz Setting up disk-based I/O fencing manuallySetting up coordinator disk groups # vxdg -g vxfencoorddg set coordinator=on Deport the coordinator disk group Creating I/O fencing configuration filesFor raw device configuration Stop VCS on all nodes Modifying VCS configuration to use I/O fencingMake a backup copy of the main.cf file Start VCS Verifying I/O fencing configuration# hacf -verify /etc/VRTSvcs/conf/config # /etc/init.d/vxfen start Removing permissions for communication # vxfenadm -dPage About verifying the VCS installation About the LLT and GAB configuration files Galaxy Nebula About the VCS configuration file main.cf Sample main.cf file for VCS clusters Page Sample main.cf file for global clusters ClusterAddress = Application wac IP gcoip NIC csgnic Gcoip requires csgnicWac requires gcoip See Setting the Path variable on Verifying the LLT, GAB, and VCS configuration filesVerify the content of the configuration files Verifying LLT, GAB, and cluster operation Output on galaxy resembles Verifying LLTSee Verifying the cluster on Output on nebula resembles Eth1 UP Verifying GAB Output resembles Verifying the cluster Verifying the cluster nodes Current Eth1 UP eth2 UP About adding and removing nodes Adding a node to a cluster Setting up the hardware See Adding a license key on Preparing for a manual installation when adding a node Installing VCS RPMs for a manual installation See Mounting the product disc on SLES10/ppc64, required Rpms Adding a license keyChecking licensing information on the system See Configuring the authentication broker on node saturn on Setting up the node to run in secure modeSee Configuring LLT and GAB on See Setting up VCS related security configuration on Configuring the authentication broker on node saturn Configuring LLT and GAB Setting up VCS related security configuration If the file on one of the existing nodes resembles On the new system, run the command# /sbin/lltconfig -c Add the new system to the cluster To verify GAB On the new node, run the commandAdding the node to the existing cluster Stop VCS on the new node Removing a node from a clusterStarting VCS and verifying the cluster Start VCS on the new node Verifying the status of nodes and service groups # hastatus -summary Deleting the departing node from VCS configurationCheck the status of the systems and the service groups # haconf -makerw # hagrp -unlink grp4 grp1 # hagrp -switch grp3 -to nebula# hagrp -dep Delete the node from the cluster Save the configuration, making it read onlyCheck the status # hagrp -delete grp4 Modifying configuration files on each remaining node Removing security credentials from the leaving node # /etc/init.d/gab stop # /etc/init.d/llt stop Stop GAB and LLTTo determine the RPMs to remove, enter # rpm -qa grep Vrts Remove the LLT and GAB configuration files # rm /etc/llttab # rm /etc/gabtab # rm /etc/llthosts About installing VCS on a single node Creating a single-node cluster using the installer program Tasks to create a single-node cluster using the installer Preparing for a single node installationStarting the installer for the single node cluster See Starting the software installation on See Licensing VCS on Installing the VCS software manually on a single nodeCreating a single-node cluster manually Set the path variable Verifying single-node operation Renaming the LLT and GAB startup filesModifying the startup files # hastart -onenode Adding a node to a single-node cluster Setting up a node to join the single-node cluster Installing VxVM or VxFS if necessary Display the service groups currently configured Configuring the shared storageSee Setting up shared storage on Bringing up the existing node Stop VCS on Node a Configuring LLTFreeze the service groups Rename the GAB and LLT startup files so they can be used LLT directives Setting up /etc/llthostsSetting up /etc/llttab See LLT directives on Directive Description Additional considerations for LLTLLT directives Reconfigure VCS on the existing nodes Configuring GAB when adding a node to a single node clusterReconfiguring VCS on the existing node Starting LLT and GAB Verifying configuration on both nodes Start the VCS on Node B Unfreeze the service groupsImplement the new two-node configuration Verify that VCS is up on both nodesPage See About adding and removing nodes on About the uninstallvcs programPreparing to uninstall VCS Removing VCS 5.0 RU3 RPMs Uninstalling VCS 5.0 RU3# cd /opt/VRTS/install # ./uninstallvcs Running uninstallvcs from the VCS 5.0 RU3 disc Uninstallvcs program is not available in /opt/VRTS/install Configuring LLT over UDP Using the UDP layer for LLTWhen to use LLT over UDP Following checklist is to configure LLT over UDP Broadcast address in the /etc/llttab file Link command in the /etc/llttab fileSee Sample configuration links crossing IP routers on See Broadcast address in the /etc/llttab file on Set-addr command in the /etc/llttab file Table A-2describes the fields of the set-addr command # setparms ipaddress Configuring the netmask for LLTSelecting UDP ports For second network interface Configuring the broadcast address for LLTSample configuration direct-attached links # cat /etc/llttab UDP File for Node 1 resembles Sample configuration links crossing IP routers Figure A-2 Performing automated VCS installations /etc/llttab file on Node 0 resembles Or, in the case of an integer value Syntax in the response fileExample response file Or, in the case of a list Response file variable definitions Table A-3 Response file variables Variable Description $CPICFGOPTLICENSE $CPICFGOPTPKGPATH $CPICFGKEYS Table A-3 See Installing and configuring VCS 5.0 RU3 on $CPICFGOPTUNINSTALL # ./installvcs -responsefile /tmp/installvcs-uui.response Index GAB RAM VCS