Symantec 5 specs

68Installing and configuring VCS Installing and configuring VCS 5.0 RU3

To configure the cluster

1Review the configuration instructions that the installer presents.

2Enter the unique cluster name and cluster ID.

Enter the unique cluster name: [?] clus1

Enter the unique Cluster ID number between 0-65535: [b,?] 7

3Review the NICs available on the first system as the installer discovers and reports them.

The private heartbeats can either use NIC or aggregated interfaces. To use aggregated interfaces for private heartbeat, enter the name of the aggregated interface. To use a NIC for private heartbeat, enter a NIC which is not part of an aggregated interface.

4Enter the network interface card details for the private heartbeat links.

You can choose the network interface cards or the aggregated interfaces that the installer discovers.

See “Starting VCS” on page 77.

You must not enter the network interface card that is used for the public network (typically eth0.)

Enter the NIC for the first private heartbeat NIC on galaxy: [b,?] eth1

Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y)

Enter the NIC for the second private heartbeat NIC on galaxy: [b,?] eth2

Would you like to configure a third private heartbeat link? [y,n,q,b,?](n)

Do you want to configure an additional low priority heartbeat link? [y,n,q,b,?] (n)

Image 68

Symantec 5 manual

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 features Veritas Installation Assessment ServiceAbout VCS notifications 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 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 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 Run the command Where ethX is the interface name For example# cd /etc/sysconfig # 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 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 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 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 Set the Persistentname for all the NICs Completing the installationStarting VCS 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 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 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 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 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 = Application wac IP gcoip NIC csgnic Gcoip requires csgnicWac requires gcoip 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 SLES10/ppc64, required Rpms Adding a license keyChecking licensing information on the system 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 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 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 # 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 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 Directive Description Additional considerations for LLTLLT directives 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 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 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 # setparms ipaddress Configuring the netmask for LLTSelecting UDP ports 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