$Cpicfgkeys | Symantec 5 guide

		Advanced VCS installation topics 169
		Performing automated VCS installations
Table A-3	Response file variables (continued)
Variable		Description
$CPI::CFG{KEYS}		List of keys to be registered on the system.
{SYSTEM}		List or scalar: list
		Optional or required: optional
$CPI::CFG{OPT_LOGPATH}		Mentions the location where the log files are to be
		copied. The default location is /opt/VRTS/install/logs.
		List or scalar: scalar
		Optional or required: optional
$CPI::CFG{CONFIGURE}		Performs the configuration if the RPMs are already
		installed using the -installonlyoption.

List or scalar: scalar

$CPI::CFG{VCS_LLTLINK#} {SYSTEM}

Optional or required: optional

Defines the NIC to be used for a private heartbeat link on each system. Two LLT links are required per system (LLTLINK1 and LLTLINK2). Up to four LLT links can be configured.

List or scalar: scalar

Optional or required: required

$CPI::CFG{VCS_LLTLINKLOWPRI} {SYSTEM}

Defines a low priority heartbeat link. Typically, LLTLINKLOWPRI is used on a public network link to provide an additional layer of communication.

List or scalar: scalar

	Optional or required: optional
$CPI::CFG{VCS_SMTPSERVER}	Defines the domain-based hostname (example:
	smtp.symantecexample.com) of the SMTP server to be
	used for Web notification.
	List or scalar: scalar
	Optional or required: optional
$CPI::CFG{VCS_SMTPRECP}	List of full email addresses (example:
	user@symantecexample.com) of SMTP recipients.
	List or scalar: list
	Optional or required: optional

Image 169

Symantec 5 manual $Cpicfgkeys

Contents

Veritas Cluster Server Installation Guide Legal Notice Veritas Cluster Server Installation Guide Symantec Corporation Ellis Street Mountain View, CA Contacting Technical Support Technical Support Licensing and registration Customer serviceDocumentation feedback Additional enterprise services Maintenance agreement resources Contents Contents Chapter Configuring VCS clusters for data integrity 121 Chapter Adding and removing cluster nodes Index 173 171 Contents About VCS basics About Veritas Cluster ServerThis chapter includes the following topics About shared storage About multiple nodesExample of a four-node VCS cluster About LLT and GAB See About the LLT and GAB configuration files onAbout network channels for heartbeating About VCS seeding About preexisting network partitions Veritas Installation Assessment Service About VCS featuresAbout VCS notifications About global clusters About I/O fencing About VCS optional componentsYou can add the following optional components to VCS About Symantec Product Authentication Service AT See Installing the Java Console on See Preparing to configure the clusters in secure mode onAbout Cluster Manager Java Console About Veritas Cluster Server Management Console About VCS optional components Page Hardware requirements About planning to install VCS1lists the hardware requirements for a VCS cluster Hardware requirements for a VCS cluster Required disk spaceDescription Kernel Architecture Supported operating systems Rhel Required Linux RPMs for VCS Supported software Planning to install VCS Supported software Preparing to configure the clusters in secure mode About preparing to install VCS 1depicts the flow of configuring VCS cluster in secure mode Workflow to configure VCS cluster in secure mode Tasks Preparatory tasks to configure a cluster in secure modeThis task See About Symantec Product Authentication Service AT on Installing the root broker for the security infrastructure# ./installer Venus # vssat showprpl --pdrtype root \ Venus # vssat showalltrustedcreds Venus # vssat showbrokerhash Creating encrypted files for the security infrastructure Addprpl command RootBroker # vssat createpkg \ For example Performing preinstallation tasks Task Reference Obtaining VCS license keysHttps//licensing.symantec.com You can use network switches instead of hubs Setting up the private networkPage See About installing and configuring VCS on Configuring SuSE network interfaces Where ethX is the interface name For example Run the command# cd /etc/sysconfig # ifconfig -a # ifconfig eth0 Setting up inter-system communication# cd /etc/sysconfig/network Accept the default location of ~/.ssh/iddsa Setting up ssh on cluster systems# ssh-keygen -t dsa See About setting up disk-based I/O fencing on Setting up shared storage# chmod 755 ~/.ssh # exec /usr/bin/ssh-agent $SHELL # ssh-add Setting the Manpath variable Setting the Path variableFor the C Shell csh or tcsh, type Optimizing LLT media speed settings on private NICs Setting the kernel.panic tunableCase of a panic, the node will reboot after 10 seconds Mounting the product disc Performing automated pre-installation check# mount -o ro /dev/cdrom /mnt/cdrom # ./installvcs -precheck galaxy nebula VCS About installing and configuring VCS Example galaxy, nebula To configure Veritas Cluster Server you needExample vcscluster27 To configure Smtp email notification optional, you need To configure VCS clusters in secure mode optional, you needVar/tmp/privatedir/roothash To configure global clusters optional, you need To configure Snmp trap notification optional, you needOptional VCS RPMs Optional features of the installvcs program About the VCS installation programVRTSvcsmn Manual pages for VCS commands See About preparing to install VCS on About installvcs program command options Interacting with the installvcs programInstallvcs command usage takes the following form Optional action Reference Installvcs system1 system2... options Nooptionalpkgs Option and Syntax Description Configuring VCS using configure option Installing VCS using installonly option See Configuring the basic cluster on Installing and configuring VCS 5.0 RU33lists the installation and the configuration tasks Overview of tasks Starting the software installation Start the installvcs program Specifying systems for installation# ./installvcs -rsh # cd /clusterserver See Checking licensing information on the system on Licensing VCS Enter keys for additional product features Choosing VCS RPMs for installation Choosing to install VCS RPMs or configure VCS See Configuring VCS using configure option on Starting the software configuration Configuring the basic cluster Specifying systems for configuration# ./installvcs -configure # cd /dvdrom/clusterserverPage Configuring the cluster in secure mode Symantecexample.com East.symantecexample.comRoot@east.symantecexample.com Root/roothash Enter the user’s name, password, and level of privileges Configuring Smtp email notificationAdding VCS users To add a user, enter y at the prompt See Configuring Snmp trap notification on See Configuring global clusters on Configuring Snmp trap notificationIf you do not want to add, answer n Verify and confirm the Smtp notification information Verify and confirm the Snmp notification information Configuring global clusters See Creating VCS configuration files on Installing VCS RPMs Verifying the NIC configuration Creating VCS configuration files Starting VCS Completing the installationSet the Persistentname for all the NICs File description VCS node authentication broker Software requirements for the Java Console Installing the Java ConsoleHardware requirements for the Java Console See Software requirements for the Java Console on Installing the Java Console on a Windows system Installing the Java Console on Linux for IBM PowerNavigate to the folder that contains the RPMs # cd /mnt/cdrom/distarch/clusterserver/rpms Installing VCS Simulator on Unix systems Installing VCS SimulatorInstalling VCS Simulator on Windows systems Software requirements for VCS Simulator Reviewing the installation See About verifying the VCS installation on Verifying the cluster after installationVerifying and updating licenses on the system Checking licensing information on the system Replacing a VCS demo license with a permanent license Updating product licenses using vxlicinst# cd /opt/VRTS/bin # hastop -all -force To access the VCS documentation Accessing the VCS documentationStart VCS on each node # hastart About configuring VCS clusters for data integrity Configuring VCS clusters for data integrity About data disks About I/O fencing componentsAbout coordination points See About data disks on 1illustrates the tasks involved to configure I/O fencing About setting up disk-based 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 # fdisk -l Initializing disks as VxVM disks Libnamevidpid # vxddladm listsupport all Checking shared disks for I/O fencing Identifying disks to use as coordinator disksExample specifies the CDS format Testing the shared disks for SCSI-3 Verifying that the nodes have access to the same diskSee Testing the disks using vxfentsthdw utility on See Removing permissions for communication on Testing the disks using vxfentsthdw utility# /opt/VRTSvcs/vxfen/bin/vxfentsthdw # /opt/VRTSvcs/vxfen/bin/vxfentsthdw -n If you use rsh for communicationDev/sdr Setting up coordinator disk groups Setting up disk-based I/O fencing manually# vxdg init vxfencoorddg sdx sdy sdz # vxdg -g vxfencoorddg set coordinator=on For raw device configuration Creating I/O fencing configuration filesDeport the coordinator disk group Make a backup copy of the main.cf file Modifying VCS configuration to use I/O fencingStop VCS on all nodes # hacf -verify /etc/VRTSvcs/conf/config Verifying I/O fencing configurationStart VCS # /etc/init.d/vxfen start # vxfenadm -d Removing permissions for communicationPage About the LLT and GAB configuration files About verifying the VCS installation 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 = Wac requires gcoip Gcoip requires csgnicApplication wac IP gcoip NIC csgnic Verify the content of the configuration files Verifying the LLT, GAB, and VCS configuration filesSee Setting the Path variable on Verifying LLT, GAB, and cluster operation See Verifying the cluster on Verifying LLTOutput on galaxy resembles Output on nebula resembles Eth1 UP Output resembles Verifying GAB Verifying the cluster Verifying the cluster nodes Current Eth1 UP eth2 UP Adding a node to a cluster About adding and removing nodes See Adding a license key on Setting up the hardware Preparing for a manual installation when adding a node See Mounting the product disc on Installing VCS RPMs for a manual installation Checking licensing information on the system Adding a license keySLES10/ppc64, required Rpms See Configuring LLT and GAB on Setting up the node to run in secure modeSee Configuring the authentication broker on node saturn on See Setting up VCS related security configuration on Configuring the authentication broker on node saturn Setting up VCS related security configuration Configuring LLT and GAB # /sbin/lltconfig -c On the new system, run the commandIf the file on one of the existing nodes resembles Adding the node to the existing cluster To verify GAB On the new node, run the commandAdd the new system to the cluster Starting VCS and verifying the cluster Removing a node from a clusterStop VCS on the new node Start VCS on the new node Verifying the status of nodes and service groups Check the status of the systems and the service groups Deleting the departing node from VCS configuration# hastatus -summary # hagrp -dep # hagrp -switch grp3 -to nebula# haconf -makerw # hagrp -unlink grp4 grp1 Check the status Save the configuration, making it read onlyDelete the node from the cluster # hagrp -delete grp4 Removing security credentials from the leaving node Modifying configuration files on each remaining node To determine the RPMs to remove, enter Stop GAB and LLT# /etc/init.d/gab stop # /etc/init.d/llt stop # rpm -qa grep Vrts # rm /etc/llttab # rm /etc/gabtab # rm /etc/llthosts Remove the LLT and GAB configuration files Creating a single-node cluster using the installer program About installing VCS on a single node Starting the installer for the single node cluster Preparing for a single node installationTasks to create a single-node cluster using the installer See Starting the software installation on Creating a single-node cluster manually Installing the VCS software manually on a single nodeSee Licensing VCS on Set the path variable Modifying the startup files Renaming the LLT and GAB startup filesVerifying single-node operation # hastart -onenode Adding a node to a single-node cluster Installing VxVM or VxFS if necessary Setting up a node to join the single-node cluster See Setting up shared storage on Configuring the shared storageDisplay the service groups currently configured Bringing up the existing node Freeze the service groups Configuring LLTStop VCS on Node a Rename the GAB and LLT startup files so they can be used Setting up /etc/llttab Setting up /etc/llthostsLLT directives See LLT directives on LLT directives Additional considerations for LLTDirective Description Reconfiguring VCS on the existing node Configuring GAB when adding a node to a single node clusterReconfigure VCS on the existing nodes Starting LLT and GAB Verifying configuration on both nodes Implement the new two-node configuration Unfreeze the service groupsStart the VCS on Node B Verify that VCS is up on both nodesPage Preparing to uninstall VCS About the uninstallvcs programSee About adding and removing nodes on # cd /opt/VRTS/install # ./uninstallvcs Uninstalling VCS 5.0 RU3Removing VCS 5.0 RU3 RPMs Running uninstallvcs from the VCS 5.0 RU3 disc Uninstallvcs program is not available in /opt/VRTS/install When to use LLT over UDP Using the UDP layer for LLTConfiguring LLT over UDP Following checklist is to configure LLT over UDP See Sample configuration links crossing IP routers on Link command in the /etc/llttab fileBroadcast address in the /etc/llttab file See Broadcast address in the /etc/llttab file on Table A-2describes the fields of the set-addr command Set-addr command in the /etc/llttab file Selecting UDP ports Configuring the netmask for LLT# setparms ipaddress Sample configuration direct-attached links Configuring the broadcast address for LLTFor second network interface # cat /etc/llttab File for Node 1 resembles UDP Figure A-2 Sample configuration links crossing IP routers /etc/llttab file on Node 0 resembles Performing automated VCS installations Example response file Syntax in the response fileOr, in the case of an integer value Or, in the case of a list Table A-3 Response file variables Variable Description Response file variable definitions $CPICFGOPTLICENSE $CPICFGOPTPKGPATH $CPICFGKEYS Table A-3 $CPICFGOPTUNINSTALL See Installing and configuring VCS 5.0 RU3 on # ./installvcs -responsefile /tmp/installvcs-uui.response Index GAB RAM VCS