Eth1 UP eth2 UP | Symantec 5 manual

120Verifying the VCS installation

Verifying LLT, GAB, and cluster operation

#System	Attribute	Value
galaxy	Limits
galaxy	LinkHbStatus	eth1 UP eth2 UP
galaxy	LoadTimeCounter	0
galaxy	LoadTimeThreshold	600
galaxy	LoadWarningLevel	80
galaxy	NoAutoDisable	0
galaxy	NodeId	0
galaxy	OnGrpCnt	1
galaxy	ShutdownTimeout	120
galaxy	SourceFile	./main.cf
galaxy	SysInfo	Linux:galaxy,#1 SMP Mon Dec 12
		18:32:25 UTC
		2005,2.6.5-7.244-pseries64,ppc64
galaxy	SysName	galaxy
galaxy	SysState	RUNNING
galaxy	SystemLocation
galaxy	SystemOwner
galaxy	TFrozen	0
galaxy	TRSE	0
galaxy	UpDownState	Up
galaxy	UserInt	0
galaxy	UserStr
galaxy	VCSFeatures	DR
galaxy	VCSMode	VCS

Image 120

Symantec 5 manual Eth1 UP eth2 UP

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 Customer service Licensing and registrationDocumentation feedback 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 About Veritas Cluster Server About VCS basicsThis chapter includes the following topics About multiple nodes About shared storageExample of a four-node VCS cluster See About the LLT and GAB configuration files on About LLT and GABAbout network channels for heartbeating About preexisting network partitions About VCS seeding About VCS features Veritas Installation Assessment ServiceAbout VCS notifications About global clusters About VCS optional components About I/O fencingYou can add the following optional components to VCS About Symantec Product Authentication Service AT See Preparing to configure the clusters in secure mode on See Installing the Java Console onAbout Cluster Manager Java Console About Veritas Cluster Server Management Console About VCS optional components Page About planning to install VCS Hardware requirements1lists the hardware requirements for a VCS cluster Required disk space Hardware requirements for a VCS clusterDescription 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 Preparatory tasks to configure a cluster in secure mode TasksThis task Installing the root broker for the security infrastructure See About Symantec Product Authentication Service AT on# ./installer 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 Obtaining VCS license keys Task ReferenceHttps//licensing.symantec.com Setting up the private network You can use network switches instead of hubsPage Configuring SuSE network interfaces See About installing and configuring VCS on Run the command Where ethX is the interface name For example# cd /etc/sysconfig # ifconfig -a Setting up inter-system communication # ifconfig eth0# cd /etc/sysconfig/network Setting up ssh on cluster systems Accept the default location of ~/.ssh/iddsa# ssh-keygen -t dsa Setting up shared storage See About setting up disk-based I/O fencing on# chmod 755 ~/.ssh # exec /usr/bin/ssh-agent $SHELL # ssh-add Setting the Path variable Setting the Manpath variableFor the C Shell csh or tcsh, type Setting the kernel.panic tunable Optimizing LLT media speed settings on private NICsCase of a panic, the node will reboot after 10 seconds Performing automated pre-installation check Mounting the product disc# mount -o ro /dev/cdrom /mnt/cdrom # ./installvcs -precheck galaxy nebula About installing and configuring VCS VCS To configure Veritas Cluster Server you need Example galaxy, nebulaExample vcscluster27 To configure VCS clusters in secure mode optional, you need To configure Smtp email notification optional, you needVar/tmp/privatedir/roothash To configure Snmp trap notification optional, you need To configure global clusters optional, you needOptional VCS RPMs About the VCS installation program Optional features of the installvcs programVRTSvcsmn Manual pages for VCS commands See About preparing to install VCS on Interacting with the installvcs program About installvcs program command optionsInstallvcs command usage takes the following form Optional action Reference Installvcs system1 system2... options Option and Syntax Description Nooptionalpkgs Installing VCS using installonly option Configuring VCS using configure option Installing and configuring VCS 5.0 RU3 See Configuring the basic cluster on3lists the installation and the configuration tasks Overview of tasks Starting the software installation Specifying systems for installation Start the installvcs program# ./installvcs -rsh # 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 Specifying systems for configuration Configuring the basic cluster# ./installvcs -configure # cd /dvdrom/clusterserverPage Configuring the cluster in secure mode East.symantecexample.com Symantecexample.comRoot@east.symantecexample.com Root/roothash Configuring Smtp email notification Enter the user’s name, password, and level of privilegesAdding VCS users To add a user, enter y at the prompt See Configuring Snmp trap notification on Configuring Snmp trap notification See Configuring global clusters onIf you do not want to add, answer n 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 Completing the installation Starting VCSSet the Persistentname for all the NICs File description VCS node authentication broker Installing the Java Console Software requirements for the Java ConsoleHardware requirements for the Java Console See Software requirements for the Java Console on Installing the Java Console on Linux for IBM Power Installing the Java Console on a Windows systemNavigate to the folder that contains the RPMs # cd /mnt/cdrom/distarch/clusterserver/rpms Installing VCS Simulator Installing VCS Simulator on Unix systemsInstalling VCS Simulator on Windows systems Software requirements for VCS Simulator Reviewing the installation Verifying the cluster after installation See About verifying the VCS installation onVerifying and updating licenses on the system Checking licensing information on the system Updating product licenses using vxlicinst Replacing a VCS demo license with a permanent license# cd /opt/VRTS/bin # hastop -all -force Accessing the VCS documentation To access the VCS documentationStart VCS on each node # hastart Configuring VCS clusters for data integrity About configuring VCS clusters for data integrity About I/O fencing components About data disksAbout coordination points 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 Identifying disks to use as coordinator disks Checking shared disks for I/O fencingExample specifies the CDS format Verifying that the nodes have access to the same disk Testing the shared disks for SCSI-3See Testing the disks using vxfentsthdw utility on Testing the disks using vxfentsthdw utility See Removing permissions for communication on# /opt/VRTSvcs/vxfen/bin/vxfentsthdw If you use rsh for communication # /opt/VRTSvcs/vxfen/bin/vxfentsthdw -nDev/sdr Setting up disk-based I/O fencing manually Setting up coordinator disk groups# vxdg init vxfencoorddg sdx sdy sdz # vxdg -g vxfencoorddg set coordinator=on Creating I/O fencing configuration files For raw device configurationDeport the coordinator disk group Modifying VCS configuration to use I/O fencing Make a backup copy of the main.cf fileStop VCS on all nodes Verifying I/O fencing configuration # hacf -verify /etc/VRTSvcs/conf/configStart VCS # /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 = Gcoip requires csgnic Wac requires gcoipApplication wac IP gcoip NIC csgnic Verifying the LLT, GAB, and VCS configuration files Verify the content of the configuration filesSee Setting the Path variable on Verifying LLT, GAB, and cluster operation Verifying LLT See Verifying the cluster onOutput on galaxy resembles 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 Adding a license key Checking licensing information on the systemSLES10/ppc64, required Rpms Setting up the node to run in secure mode See Configuring LLT and GAB onSee Configuring the authentication broker on node saturn 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 On the new system, run the command # /sbin/lltconfig -cIf the file on one of the existing nodes resembles To verify GAB On the new node, run the command Adding the node to the existing clusterAdd the new system to the cluster Removing a node from a cluster Starting VCS and verifying the clusterStop VCS on the new node Start VCS on the new node Verifying the status of nodes and service groups Deleting the departing node from VCS configuration Check the status of the systems and the service groups# hastatus -summary # hagrp -switch grp3 -to nebula # hagrp -dep# haconf -makerw # hagrp -unlink grp4 grp1 Save the configuration, making it read only Check the statusDelete the node from the cluster # hagrp -delete grp4 Modifying configuration files on each remaining node Removing security credentials from the leaving node Stop GAB and LLT To determine the RPMs to remove, enter# /etc/init.d/gab stop # /etc/init.d/llt stop # 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 Preparing for a single node installation Starting the installer for the single node clusterTasks to create a single-node cluster using the installer See Starting the software installation on Installing the VCS software manually on a single node Creating a single-node cluster manuallySee Licensing VCS on Set the path variable Renaming the LLT and GAB startup files Modifying the startup filesVerifying single-node operation # 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 Configuring the shared storage See Setting up shared storage onDisplay the service groups currently configured Bringing up the existing node Configuring LLT Freeze the service groupsStop VCS on Node a Rename the GAB and LLT startup files so they can be used Setting up /etc/llthosts Setting up /etc/llttabLLT directives See LLT directives on Additional considerations for LLT LLT directivesDirective Description Configuring GAB when adding a node to a single node cluster Reconfiguring VCS on the existing nodeReconfigure VCS on the existing nodes Starting LLT and GAB Verifying configuration on both nodes Unfreeze the service groups Implement the new two-node configurationStart the VCS on Node B Verify that VCS is up on both nodesPage About the uninstallvcs program Preparing to uninstall VCSSee About adding and removing nodes on Uninstalling VCS 5.0 RU3 # cd /opt/VRTS/install # ./uninstallvcsRemoving VCS 5.0 RU3 RPMs Running uninstallvcs from the VCS 5.0 RU3 disc Uninstallvcs program is not available in /opt/VRTS/install Using the UDP layer for LLT When to use LLT over UDPConfiguring LLT over UDP Following checklist is to configure LLT over UDP Link command in the /etc/llttab file See Sample configuration links crossing IP routers onBroadcast address in the /etc/llttab file 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 Configuring the netmask for LLT Selecting UDP ports# setparms ipaddress Configuring the broadcast address for LLT Sample configuration direct-attached linksFor second network interface # 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 Syntax in the response file Example response fileOr, in the case of an integer value 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