Manuale d’uso / di manutenzione del prodotto 5 del fabbricante Symantec
Vai alla pagina of 176
Veritas Cluster Server Installation Guide Linux for IBM Power 5.0 Release Update 3.
Veritas Cluster Server Installation Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Product version: 5.0 RU3 Document version: 5.0RU3.0 Legal Notice Copyright © 2009 Symantec Corporation.
Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com.
Technical Support Symantec Technical Support maintains support centers globally. Technical Support ’ s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base.
■ Version and patch level ■ Network topology ■ Router, gateway, and IP address information ■ Problem description: ■ Error messages and log files ■ Troubleshooting that was performed before.
Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows: customercare_apac@symantec.com Asia-Pacific and Japan semea@symantec.
Technical Support ............................................................................................... 4 Chapter 1 Introducing Veritas Cluster Server .................................. 1 3 A b o u t V e r i t a s C l u s t e r S e r v e r .
Creating authentication broker accounts on root broker s y s t e m ........................................................................... 3 4 Creating encrypted files for the security infrastructure . . . . . . . . . . . . . . . . . 35 Preparing the installation system for the security i n f r a s t r u c t u r e .
A d d i n g V C S u s e r s ................................................................... 7 1 C o n f i g u r i n g S M T P e m a i l n o t i f i c a t i o n ......................................... 7 1 C o n f i g u r i n g S N M P t r a p n o t i f i c a t i o n .
Verifying LLT, GAB, and cluster operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 V e r i f y i n g L L T ...................................................................... 1 1 4 V e r i f y i n g G A B ....
B r i n g i n g u p t h e e x i s t i n g n o d e ................................................. 1 4 5 Installing the VCS software manually when adding a node to a s i n g l e n o d e c l u s t e r ..................................................
Contents 12.
Introducing Veritas Cluster Server This chapter includes the following topics: ■ About Veritas Cluster Server ■ About VCS basics ■ About VCS features ■ About VCS optional components About Veritas Cluster Server Veritas ™ Cluster Server by Symantec is a high-availability solution for cluster configurations.
Figure 1-1 illustrates a typical VCS configuration of four nodes that are connected to shared storage. Figure 1-1 Example of a four-node VCS cluster Client workstation Client workstation Public network Shared storage VCS private network VCS nodes Client workstations receive service over the public network from applications running on VCS nodes.
Figure 1-2 Two examples of shared storage configurations Fully shared storage Distributed shared storage About LLT and GAB VCS uses two components, LLT and GAB, to share data over private networks among systems. These components provide the performance and reliability that VCS requires.
Figure 1-3 illustrates a two-node VCS cluster where the nodes galaxy and nebula have two private network connections. Figure 1-3 Two Ethernet connections connecting two nodes VCS private network: two .
About VCS features You can use the Veritas Installation Assessment Service to assess your setup for VCS installation. See “ Veritas Installation Assessment Service ” on page 17. VCS offers the following features that you can configure during VCS configuration: See “ About VCS notifications ” on page 17.
About I/O fencing I/O fencing protects the data on shared disks when nodes in a cluster detect a change in the cluster membership that indicates a split brain condition.
Figure 1-4 Typical VCS setup with optional components Symantec Product Authentication Service root broker VCS cluster 1 VCS cluster 2 VCS Management Console management server Optional About Symantec P.
See “ Preparing to configure the clusters in secure mode ” on page 29. About Cluster Manager (Java Console) Cluster Manager (Java Console) offers complete administration capabilities for your cluster.
configurations for Windows, Linux, and Solaris clusters. VCS Simulator also enables creating and testing global clusters. You can administer VCS Simulator from the Java Console or from the command line.
Introducing Veritas Cluster Server About VCS optional components 22.
Planning to install VCS This chapter includes the following topics: ■ About planning to install VCS ■ Hardware requirements ■ Supported operating systems ■ Supported software About planning to install VCS Every node where you want to install VCS must meet the hardware and software requirements.
Table 2-1 Hardware requirements for a VCS cluster Description Item From 1 to 32 Linux PPC systems running the supported Linux PPC operating system version.
Note: If you do not have enough free space in /var, then use the installvcs command with tmppath option. Make sure that the specified tmppath file system has the required free space. Supported operating systems VCS operates on the Linux operating systems and kernels distributed by Red Hat and SUSE.
Required Linux RPMs for VCS Make sure you installed the following operating system-specific RPMs on the systems where you want to install or upgrade VCS. VCS will support any updates made to the following RPMs, provided the RPMs maintain the ABI compatibility.
Supported software Veritas Cluster Server supports the previous and next versions of Storage Foundation to facilitate product upgrades, when available. VCS supports the following volume managers and files systems: ■ ext2, ext3, reiserfs, NFS, NFSv4, and bind on LVM2, Veritas Volume Manager (VxVM) 5.
Planning to install VCS Supported software 28.
Preparing to install VCS This chapter includes the following topics: ■ About preparing to install VCS ■ Preparing to configure the clusters in secure mode ■ Performing preinstallation tasks Abou.
■ The system clocks of the root broker and authentication brokers must be in sync. The installvcs program provides the following configuration modes: The root broker system must allow rsh or ssh passwordless login to use this mode.
Figure 3-1 Workflow to configure VCS cluster in secure mode Configure the cluster in secure mode Review AT concepts and gather required information Install root broker on a stable system Select a mode.
Table 3-1 Preparatory tasks to configure a cluster in secure mode Who performs this task Tasks VCS administrator Decide one of the following configuration modes to set up a cluster in secure mode: ■ Automatic mode ■ Semi-automatic mode ■ Manual mode AT administrator Install the root broker on a stable system in the enterprise.
Installing the root broker for the security infrastructure Install the root broker only if you plan to use AT to configure the cluster in secure mode. The root broker administrator must install and configure the root broker before you configure the Authentication Service for VCS.
9 Enter y when the installer prompts you to configure the Symantec Product Authentication Service. 10 Press the Enter key to start the Authentication Server processes. Do you want to start Symantec Product Authentication Service processes now? [y,n,q] y 11 Enter an encryption key.
■ If the output displays the following error, then the account for the given authentication broker is not created on this root broker: "Failed To Get Attributes For Principal" Proceed to step 3 . 3 Create a principal account for each authentication broker in the cluster.
The value for the authentication broker identity, which you provided to create authentication broker principal on the root broker system. This is the value for the --prplname option of the addprpl command. See “ Creating authentication broker accounts on root broker system ” on page 34.
Note that for security purposes, the command to create the output file for the encrypted file deletes the input file. 5 For each node in the cluster, create the output file for the encrypted file from the root broker system using the following command.
Do the following: ■ Copy the root_hash file that you fetched to the system from where you plan to install VCS. Note the path of the root hash file that you copied to the installation system. ■ Gather the root broker information such as name, fully qualified domain name, domain, and port from the AT administrator.
Table 3-2 Preinstallation tasks (continued) Reference Task See “ Optimizing LLT media speed settings on private NICs ” on page 48. Review basic instructions to optimize LLT media speeds. See “ Guidelines for setting the media speed of the LLT interconnects ” on page 48.
You can only install the Symantec software products for which you have purchased a license. The enclosed software discs might include other products for which you have not purchased a license. Setting up the private network VCS requires you to set up a private network between the systems that form a cluster.
Figure 3-3 Private network setup with crossed links Crossed link Public network Private networks To set up the private network 1 Install the required network interface cards (NICs). Create aggregated interfaces if you want to use these to set up private network.
■ The systems can access the shared storage. 4 Test the network connections. Temporarily assign network addresses and use telnet or ping to verify communications. LLT uses its own protocol, and does not use TCP/IP. So, you must ensure that the private network connections are used only for LLT communication and not for TCP/IP traffic.
To configure persistent interface names for network devices 1 Navigate to the hotplug file in the /etc/sysconfig directory: # cd /etc/sysconfig 2 Open the hotplug file in an editor.
collisions:0 txqueuelen:1000 RX bytes:35401016 (33.7 Mb) TX bytes:999899 (976.4 Kb) Base address:0xdce0 Memory:fcf20000-fcf40000 If a file named etc/sysconfig/network/ifcfg-eth-id-00:02:B3:DB:38:FE does not exist, do the following task: ■ Create the file.
where you run installvcs program. This privilege facilitates to issue ssh or rsh commands on all systems in the cluster. If ssh is used to communicate between systems, it must be configured in a way such that it operates without requests for passwords or passphrases.
4 When the command prompts, enter a passphrase and confirm it. 5 Change the permissions of the .ssh directory by typing: # chmod 755 ~/.ssh 6 The file ~/.ssh/id_dsa.pub contains a line that begins with ssh_dss and ends with the name of the system on which it was created.
See also the Veritas Cluster Server User's Guide for a description of I/O fencing. Setting the PATH variable Installation commands as well as other commands reside in the /sbin, /usr/sbin, /opt/VRTS/bin, and /opt/VRTSvcs/bin directories. Add these directories to your PATH environment variable.
Setting the kernel.panic tunable By default, the kernel.panic tunable is set to zero. Therefore the kernel does not reboot automatically if a node panics. To ensure that the node reboots automatically after it panics, this tunable must be set to a non zero value.
Mounting the product disc You must have superuser (root) privileges to load the VCS software. To mount the product disc 1 Log in as superuser on a system where you want to install VCS. The system from which you install VCS need not be part of the cluster.
To check the systems 1 Navigate to the folder that contains the installvcs program. See “ Mounting the product disc ” on page 49. 2 Start 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.
Installing and configuring VCS This chapter includes the following topics: ■ About installing and configuring VCS ■ Getting your VCS installation and configuration information ready ■ About the VCS installation program ■ Installing and configuring VCS 5.
Getting your VCS installation and configuration information ready The VCS installation and configuration program prompts you for information about certain VCS components.
■ To configure VCS clusters in secure mode (optional), you need: ■ The name of the Root Broker system Example: east See “ About Symantec Product Authentication Service (AT) ” on page 19. ■ Access to the Root Broker system without use of a password.
The domain-based address of the SMTP server The SMTP server sends notification emails about the events within the cluster. Example: smtp.symantecexample.com Example: john@symantecexample.com The email address of each SMTP recipient to be notified Events have four levels of severity: I=Information, W=Warning, E=Error, and S=SevereError.
■ VRTSvcsmn — Manual pages for VCS commands About the VCS installation program You can access the installvcs program from the command line or through the Veritas product installer.
Table 4-1 installvcs optional features (continued) Reference Optional action See “ Installing VCS with a response file where ssh or rsh are disabled ” on page 171. Perform secure installations using the values that are stored in a configuration file.
installvcs [ system1 system2 ... ] [ options ] Table 4-2 lists the installvcs command options. Table 4-2 installvcs options Description Option and Syntax Configure VCS after using -installonly option to install VCS. See “ Configuring VCS using configure option ” on page 59.
Table 4-2 installvcs options (continued) Description Option and Syntax Specifies that the optional product RPMs such as man pages and documentation need not be installed. -nooptionalpkgs Bypass starting VCS after completing installation and configuration.
Table 4-2 installvcs options (continued) Description Option and Syntax Specifies that rsh and rcp are to be used for communication between systems instead of ssh and scp .
cluster configuration. The installvcs program prompts for cluster information, and creates VCS configuration files without performing installation. See “ Configuring the basic cluster ” on page 67. The -configure option can be used to reconfigure a VCS cluster.
Table 4-3 Installation and configuration tasks Reference Task ■ See “ Starting the software installation ” on page 61. ■ See “ Specifying systems for installation ” on page 62. ■ See “ Licensing VCS ” on page 63. ■ See “ Choosing VCS RPMs for installation ” on page 64.
Note: The system from where you install VCS must run the same Linux distribution as the target systems. To install VCS using the product installer 1 Confirm that you are logged in as the superuser and mounted the product disc. 2 Start the installer. # .
To specify system names for installation 1 Enter the names of the systems where you want to install VCS. Enter the system names separated by spaces on which to install VCS: galaxy nebula For a single node installation, enter one name for the system. See “ Creating a single-node cluster using the installer program ” on page 139.
3 Enter keys for additional product features. Do you want to enter another license key for galaxy? [y,n,q,?] (n) y Enter a VCS license key for galaxy: [?] XXXX-XXXX-XXXX-XXXX-XXX XXXX-XXXX-XXXX-XXXX-X.
To install VCS RPMs 1 Review the output as the installer checks the RPMs that are already installed. 2 Choose the VCS RPMs that you want to install. Select the RPMs to be installed on all systems? [1-3,q,?] (3) 2 Based on what RPMs you want to install, enter one of the following: Installs only the required VCS RPMs.
To install VCS packages now and configure VCS later 1 If you do not want to configure VCS now, enter n at the prompt. Are you ready to configure VCS? [y,n,q] (y) n The utility checks for the required file system space and makes sure that any processes that are running do not conflict with the installation.
To configure VCS using the installvcs program 1 Confirm that you are logged in as the superuser and mounted the product disc. 2 Navigate to the folder that contains the installvcs program. # cd /dvdrom/cluster_server 3 Start the installvcs program. # .
To configure the cluster 1 Review the configuration instructions that the installer presents. 2 Enter the unique cluster name and cluster ID. Enter the unique cluster name: [?] clus1 Enter the unique Cluster ID number between 0-65535: [b,?] 7 3 Review the NICs available on the first system as the installer discovers and reports them.
5 Choose whether to use the same NIC details to configure private heartbeat links on other systems. Are you using the same NICs for private heartbeat links on all systems? [y,n,q,b,?] (y) If you want to use the NIC details that you entered for galaxy, make sure the same NICs are available on each system.
Enter the name of the Root Broker system when prompted. Requires a remote access to the Root Broker. Review the output as the installer verifies communication with the Root Broker system, checks vxatd process and version, and checks security domain. Option 1 .
See Veritas Cluster Server User's Guide for more information. Adding VCS users If you have enabled Symantec Product Authentication Service, you do not need to add VCS users now. Otherwise, on systems operating under an English locale, you can add VCS users at this time.
Refer to the Veritas Cluster Server User ’ s Guide for more information. To configure SMTP email notification 1 Review the required information to configure the SMTP email notification.
■ If you do not want to add, answer n . Would you like to add another SMTP recipient? [y,n,q,b] (n) 5 Verify and confirm the SMTP notification information. SMTP Address: smtp.example.com Recipient: ozzie@example.com receives email for Warning or higher events Recipient: harriet@example.
Enter the SNMP console system name: [b,?] saturn ■ Enter the minimum security level of messages to be sent to each console. Enter the minimum severity of events for which SNMP traps should be sent to saturn [I=Information, W=Warning, E=Error, S=SevereError]: [b,?] E 4 Add more SNMP consoles, if necessary.
information to the VCS configuration file. You must perform additional configuration tasks to set up a global cluster. See Veritas Cluster Server User's Guide for instructions to set up VCS global clusters. Note: If you installed a HA/DR license to set up replicated data cluster or campus cluster, skip this installer option.
for installation are not met, the utility stops and indicates the actions that are required to proceed with the process. Review the output as the installer uninstalls any previous versions and installs the VCS 5.
CPI WARNING V-9-122-1021 No PERSISTENT_NAME set for NIC with MAC address 00:11:43:33:17:28 (present name eth0), though config file exists! CPI WARNING V-9-122-1022 No config file for NIC with MAC addr.
Table 4-4 File description Description File ■ Lists the RPMs that are installed on each system. ■ Describes the cluster and its configured resources. ■ Provides the information for managing the cluster. summary file Details the entire installation.
Figure 4-2 Client communication with LDAP servers VCS node (authentication broker) VCS client 1. When a user runs HA commands, AT initiates user authentication with the authentication broker. 4. AT issues the credentials to the user to proceed with the command.
■ Distinguished name for the user container (for example, UserBaseDN=ou=people,dc=comp,dc=com) ■ Distinguished name for the group container (for example, GroupBaseDN=ou=group,dc=comp,dc=com) Installing the Java Console You can administer VCS using the VCS Java-based graphical user interface, Java Console.
Note: Symantec recommends using Pentium III, 400MHz, 256MB RAM, and 800x600 display resolution. The version of the Java ™ 2 Runtime Environment (JRE) requires 32 megabytes of RAM. This version is supported on the Intel Pentium platforms that run the Linux kernel v 2.
3 Go to windowsVCSWindowsInstallersClusterManager. 4 Open the language folder of your choice, for example EN. 5 Double-click setup.exe. 6 The Veritas Cluster Manager Install Wizard guides you through the installation process. Installing VCS Simulator You can administer VCS Simulator from the Java Console or from the command line.
To install VCS Simulator on Windows systems 1 Insert the VCS installation disc into a drive. 2 Navigate to the path of the Simulator installer file: your_platform_architecturecluster_serverwindows VCSWindowsInstallersSimulator 3 Double-click the installer file.
Verifying the cluster after installation When you have used installvcs program and chosen to configure and start VCS, VCS and all components are properly configured and can start correctly. You must verify that your cluster operates properly after the installation.
Reserved = 0 Mode = VCS Updating product licenses using vxlicinst You can use the vxlicinst command to add the VCS license key on each node. If you have VCS already installed and configured and you use a demo license, you can replace the demo license.
4 Make sure demo licenses are replaced on all cluster nodes before starting VCS. # cd /opt/VRTS/bin # ./vxlicrep 5 Start VCS on each node: # hastart Accessing the VCS documentation The software disc contains the documentation for VCS in Portable Document Format (PDF) in the cluster_server/docs directory.
Configuring VCS clusters for data integrity This chapter includes the following topics: ■ About configuring VCS clusters for data integrity ■ About I/O fencing components ■ About setting up disk.
If a system is so busy that it appears to stop responding, the other nodes could declare it as dead. This declaration may also occur for the nodes that use the hardware that supports a "break" and "resume" function.
Disks that act as coordination points are called coordinator disks. Coordinator disks are three standard disks or LUNs set aside for I/O fencing during cluster reconfiguration. Coordinator disks do not serve any other storage purpose in the VCS configuration.
Figure 5-1 Workflow to configure disk-based I/O fencing Initialize disks as VxVM disks Identify disks to use as coordinator disks Set up coordinator disk group Create I/O fencing configuration files M.
For the latest information on supported hardware visit the following URL: http://entsupport.symantec.com/docs/283161 ■ Each of the coordinator disks must use a physically separate disk or LUN. Symantec recommends using the smallest possible LUNs for coordinator disks.
When you run the vxfen startup file to start I/O fencing, the script creates this /etc/vxfentab file on each node with a list of all paths to each coordinator disk.
Refer to the installation guide that comes with the Storage Foundation product that you use. Perform the following preparatory tasks to configure I/O fencing: See “ Initializing disks as VxVM disks ” on page 93. Initialize disks as VxVM disks See “ Identifying disks to use as coordinator disks ” on page 95.
3 Verify that the ASL for the disk array is installed on each of the nodes. Run the following command on each node and examine the output to verify the installation of ASL. The following output is a sample: # vxddladm listsupport all LIBNAME VID PID ================================================================================= libvx3par.
4 Scan all disk drives and their attributes, update the VxVM device list, and reconfigure DMP with the new devices. Type: # vxdisk scandisks See the Veritas Volume Manager documentation for details on how to add and configure disks.
command option verifies that the same serial number for the LUN is returned on all paths to the LUN. Make sure to test the disks that serve as coordinator disks. The vxfentsthdw utility has additional options suitable for testing many disks. Review the options for testing the disk groups ( -g ) and the disks that are listed in a file ( -f ).
The same serial number information should appear when you enter the equivalent command on node B using the /dev/sdy path. On a disk from another manufacturer, Hitachi Data Systems, the output is diffe.
■ If you use rsh for communication: # /opt/VRTSvcs/vxfen/bin/vxfentsthdw -n 3 The script warns that the tests overwrite data on the disks. After you review the overview and the warning, confirm to continue the process and enter the node names. Warning: The tests overwrite and destroy data on the disks unless you use the -r option.
Setting up disk-based I/O fencing manually Make sure you completed the preparatory tasks before you set up I/O fencing. Tasks that are involved in setting up I/O fencing include: Table 5-1 Tasks to set up I/O fencing manually Description Action See “ Setting up coordinator disk groups ” on page 99.
3 Deport the coordinator disk group: # vxdg deport vxfencoorddg 4 Import the disk group with the -t option to avoid automatically importing it when the nodes restart: # vxdg -t import vxfencoorddg 5 Deport the disk group.
# cp /etc/vxfen.d/vxfenmode_scsi3_raw /etc/vxfenmode 3 To check the updated /etc/vxfenmode configuration, enter the following command on one of the nodes.
6 Save and close the file. 7 Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf: # hacf -verify /etc/VRTSvcs/conf/config 8 Using rcp or another utility, copy the VCS configuration file from a node (for example, galaxy) to the remaining cluster nodes.
To verify I/O fencing configuration ◆ On one of the nodes, type: # vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: SCSI3 Fen.
Configuring VCS clusters for data integrity Setting up disk-based I/O fencing manually 104.
Verifying the VCS installation This chapter includes the following topics: ■ About verifying the VCS installation ■ About the LLT and GAB configuration files ■ About the VCS configuration file main.
The file llthosts is a database that contains one entry per system. This file links the LLT system ID (in the first column) with the LLT host name. This file is identical on each node in the cluster.
Note: The use of the -c -x option for /sbin/gabconfig is not recommended. About the VCS configuration file main.cf The VCS configuration file /etc/VRTSvcs/conf/config/main.cf is created during the installation process. See “ Sample main.cf file for VCS clusters ” on page 108.
Refer to the Veritas Cluster Server User's Guide to review the configuration concepts, and descriptions of main.cf and types.cf files for Linux for IBM Power systems. Sample main.cf file for VCS clusters The following sample main.cf file is for a secure cluster that is managed locally by the Cluster Management Console.
NIC csgnic ( Device = eth0 NetworkHosts = { "192.168.1.17", "192.168.1.18" } ) NotifierMngr ntfr ( SnmpConsoles = { "saturn" = Error, "jupiter" = SevereError } SmtpServer = "smtp.example.com" SmtpRecipients = { "ozzie@example.
SystemList = { galaxy = 0, nebula = 1 } Parallel = 1 OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) Phantom phantom_vxss ( ) ProcessOnOnly vxatd ( IgnoreArgs = 1 PathName = "/opt/VRTSat/bin/vxatd" ) // resource dependency tree // // group VxSS // { // Phantom phantom_vxss // ProcessOnOnly vxatd // } Sample main.
. . In the following main.cf file example, bold text highlights global cluster specific entries. include "types.cf" cluster vcs03 ( ClusterAddress = "10.
Device = eth0 ) NotifierMngr ntfr ( SnmpConsoles = { vcslab4079 = SevereError } SmtpServer = "smtp.veritas.com" SmtpRecipients = { "johndoe@veritas.
PathName = "/opt/VRTSat/bin/vxatd" ) // resource dependency tree // // group VxSS // { // Phantom phantom_vxss // ProcessOnOnly vxatd // } Verifying the LLT, GAB, and VCS configuration files Make sure that the LLT, GAB, and VCS configuration files contain the information you provided during VCS installation and configuration.
3 Verify LLT operation. See “ Verifying LLT ” on page 114. 4 Verify GAB operation. See “ Verifying GAB ” on page 116. 5 Verify the cluster operation. See “ Verifying the cluster ” on page 117. Verifying LLT Use the lltstat command to verify that links are active for LLT.
5 To view additional information about LLT, run the lltstat -nvv command on each node. For example, run the following command on the node galaxy in a two-node cluster: lltstat -nvv | more The output o.
However, the output in the example shows different details for the node nebula. The private network connection is possibly broken or the information in the /etc/llttab file may be incorrect. 6 To obtain information about the ports open for LLT, type lltstat -p on any node.
To verify GAB 1 To verify that GAB operates, type the following command on each node: /sbin/gabconfig -a 2 Review the output of the command: ■ If GAB operates, the following GAB port membership info.
To verify the cluster 1 To verify the status of the cluster, type the following command: hastatus -summary The output resembles: -- SYSTEM STATE -- System State Frozen A galaxy RUNNING 0 A nebula RUNN.
The example shows the output when the command is run on the node galaxy. The list continues with similar information for nebula (not shown) and any other nodes in the cluster.
Value Attribute #System Limits galaxy eth1 UP eth2 UP LinkHbStatus galaxy 0 LoadTimeCounter galaxy 600 LoadTimeThreshold galaxy 80 LoadWarningLevel galaxy 0 NoAutoDisable galaxy 0 NodeId galaxy 1 OnGrpCnt galaxy 120 ShutdownTimeout galaxy ./main.cf SourceFile galaxy Linux:galaxy,#1 SMP Mon Dec 12 18:32:25 UTC 2005,2.
Adding and removing cluster nodes This chapter includes the following topics: ■ About adding and removing nodes ■ Adding a node to a cluster ■ Removing a node from a cluster About adding and removing nodes After you install VCS and create a cluster, you can add and remove nodes from the cluster.
Table 7-1 Tasks that are involved in adding a node to a cluster (continued) Reference Task See “ Preparing for a manual installation when adding a node ” on page 123. See “ Installing VCS RPMs for a manual installation ” on page 124. Install the software manually.
Figure 7-1 Adding a node to a two-node cluster using two switches Public network Private network New node: saturn To set up the hardware 1 Connect the VCS private Ethernet controllers. Perform the following tasks as necessary: ■ When you add nodes to a two-node cluster, use independent switches or hubs for the private network connections.
See “ Mounting the product disc ” on page 49. To prepare for installation ◆ Depending on the OS distribution, replace the dist in the command with rhel5 or sles10. Replace the arch in the command with ppc64. # cd /mnt/cdrom/ dist_arch /cluster_server/rpms Installing VCS RPMs for a manual installation VCS has both required and optional RPMs.
# rpm -i VRTScutil-5.0.33.00-RU3_GENERIC.noarch.rpm # rpm -i VRTSatClient-4.3.28.0-0.ppc.rpm # rpm -i VRTSatServer-4.3.28.0-0.ppc.rpm ■ SLES10/ppc64, required RPMS # rpm -i VRTSvlic-3.02.33.4-0.ppc64.rpm # rpm -i VRTSperl-5.10.0.1-SLES10.ppc64.rpm # rpm -i VRTSspt-5.
Setting up the node to run in secure mode You must follow this procedure only if you are adding a node to a cluster that is running in secure mode. If you are adding a node to a cluster that is not running in a secure mode, proceed with configuring LLT and GAB.
# vssat deletecred --domain type:domainname --prplname prplname For example: # vssat deletecred --domain vx:root@RB2.brokers.example.com --prplname saturn.nodes.example.com Configuring the authentication broker on node saturn Configure a new authentication broker (AB) on node saturn.
4 Configure AB on node saturn to talk to RB1. # vxatd -o -a -n prplname -p password -x vx -y domainname -q rootbroker -z 2821 -h roothash_file_path For example: # vxatd -o -a -n saturn.nodes.example.com -p flurbdicate -x vx -y root@RB1.brokers.example.
■ If the file on one of the existing nodes resembles: 0 galaxy 1 nebula ■ Update the file for all nodes, including the new one, resembling: 0 galaxy 1 nebula 2 saturn 2 Create the file /etc/llttab on the new node, making sure that line beginning " set-node " specifies the new node.
The -n flag indicates to VCS the number of nodes that must be ready to form a cluster before VCS starts. 2 On the new node, run the command, to configure GAB: # /sbin/gabconfig -c To verify GAB 1 On the new node, run the command: # /sbin/gabconfig -a The output should indicate that port a membership shows all nodes including the new node.
3 Stop VCS on the new node: # hastop -sys saturn 4 Copy the main.cf file from an existing node to your new node: # rcp /etc/VRTSvcs/conf/config/main.cf saturn:/etc/VRTSvcs/conf/config/ 5 Start VCS on the new node: # hastart 6 If necessary, modify any new system attributes.
Table 7-3 Tasks that are involved in removing a node Reference Task See “ Verifying the status of nodes and service groups ” on page 132. ■ Back up the configuration file. ■ Check the status of the nodes and the service groups. See “ Deleting the departing node from VCS configuration ” on page 133.
To verify the status of the nodes and the service groups 1 Make a backup copy of the current configuration file, main.cf. # cp -p /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.goodcopy 2 Check the status of the systems and the service groups.
To remove or switch service groups from the departing node 1 Switch failover service groups from the departing node. You can switch grp3 from node saturn to node nebula. # hagrp -switch grp3 -to nebula 2 Check for any dependencies involving any service groups that run on the departing node; for example, grp4 runs only on the departing node.
6 Delete the departing node from the SystemList of service groups grp3 and grp4. # hagrp -modify grp3 SystemList -delete saturn # hagrp -modify grp4 SystemList -delete saturn 7 For the service groups that run only on the departing node, delete the resources from the group before you delete the group.
Modifying configuration files on each remaining node Perform the following tasks on each of the remaining nodes of the cluster. To modify the configuration files on a remaining node 1 If necessary, modify the /etc/gabtab file. No change is required to this file if the /sbin/gabconfig command has only the argument -c .
Unloading LLT and GAB and removing VCS on the departing node Perform the tasks on the node that is departing the cluster. If you have configured VCS as part of the Storage Foundation and High Availability products, you may have to delete other dependent RPMs before you can delete all of the following ones.
# rpm -e VRTSvlic # rpm -e VRTSperl # rpm -e VRTSpbx # rpm -e VRTSicsco # rpm -e VRTSatServer # rpm -e VRTSatClient 5 Remove the LLT and GAB configuration files.
Installing VCS on a single node This chapter includes the following topics: ■ About installing VCS on a single node ■ Creating a single-node cluster using the installer program ■ Creating a single-node cluster manually ■ Adding a node to a single-node cluster About installing VCS on a single node You can install VCS 5.
Table 8-1 Tasks to create a single-node cluster using the installer Reference Task See “ Preparing for a single node installation ” on page 140. Prepare for installation. See “ Starting the installer for the single node cluster ” on page 140. Install the VCS software on the system using the installer.
Answer y if you plan to incorporate the single node cluster into a multi-node cluster in the future. Continue with the installation. See “ Licensing VCS ” on page 63. Creating a single-node cluster manually Table 8-2 specifies the tasks that you need to perform to install VCS on a single node.
■ See “ Preparing for a manual installation when adding a node ” on page 123. ■ See “ Installing VCS RPMs for a manual installation ” on page 124.
Adding a node to a single-node cluster All nodes in the new cluster must run the same version of VCS. The example procedure refers to the existing single-node VCS node as Node A. The node that is to join Node A to form a multiple-node cluster is Node B.
Setting up a node to join the single-node cluster The new node to join the existing single node running VCS must run the same version of operating system and patch level. To set up a node to join the single-node cluster 1 Do one of the following tasks: ■ If VCS is not currently running on Node B, proceed to step 2 .
To install and configure Ethernet cards for private network 1 Shut down VCS on Node A. # hastop -local 2 Shut down the node to get to the OK prompt: # shutdown -r now 3 Install the Ethernet card on Node A. If you want to use aggregated interface to set up private network, configure aggregated interface.
5 Freeze the service groups. # hagrp -freeze group -persistent Repeat this command for each service group in step 4. 6 Make the configuration read-only. # haconf -dump -makero 7 Stop VCS on Node A. # hastop -local -force 8 Edit the VCS system configuration file /etc/sysconfig/vcs, and remove the "-onenode" option.
It handles the following tasks: ■ Traffic distribution ■ Heartbeat traffic Configured as described in the following sections. Setting up /etc/llthosts The file llthosts(4M) is a database. This file contains one entry per system that links the LLT system ID (in the first column) with the LLT host name.
Table 8-4 LLT directives Description Directive Assigns the system ID or symbolic name. The system ID number must be unique for each system in the cluster, and must be in the range 0-31. The symbolic name corresponds to the system ID in the /etc/llthosts file.
Configuring GAB when adding a node to a single node cluster VCS uses the Group Membership Services/Atomic Broadcast (GAB) protocol for cluster membership and reliable cluster communications.
To reconfigure VCS on existing nodes 1 On Node A, create the files /etc/llttab, /etc/llthosts, and /etc/gabtab. Use the files that are created on Node B as a guide, customizing the /etc/llttab for Node A. 2 Start LLT on Node A. # /etc/init.d/llt start 3 Start GAB on Node A.
To verify the nodes' configuration 1 On Node B, check the cluster membership. # gabconfig -a 2 Start the VCS on Node B. # hastart 3 Verify that VCS is up on both nodes. # hastatus 4 List the service groups. # hagrp -list 5 Unfreeze the service groups.
Installing VCS on a single node Adding a node to a single-node cluster 152.
Uninstalling VCS This chapter includes the following topics: ■ About the uninstallvcs program ■ Preparing to uninstall VCS ■ Uninstalling VCS 5.0 RU3 About the uninstallvcs program You can uninstall VCS from all nodes in the cluster or from specific nodes in the cluster using the uninstallvcs program.
■ If you have manually edited any of the VCS configuration files, you need to reformat them. Uninstalling VCS 5.0 RU3 You must meet the following conditions to use the uninstallvcs program to uninstall VCS on all nodes in the cluster at one time: ■ Make sure that the communication exists between systems.
3 Enter the names of the systems from which you want to uninstall VCS. The program performs system verification checks and asks to stop all running VCS processes. 4 Enter y to stop all the VCS processes. The program proceeds with uninstalling the software.
■ The uninstallvcs program is not available in /opt/VRTS/install. Uninstalling VCS Uninstalling VCS 5.0 RU3 156.
Advanced VCS installation topics This appendix includes the following topics: ■ Using the UDP layer for LLT ■ Performing automated VCS installations ■ Installing VCS with a response file where ssh or rsh are disabled Using the UDP layer for LLT VCS 5.
■ Make sure that the LLT private links are on different physical networks. If the LLT private links are not on different physical networks, then make sure that the links are on separate subnets. Set the broadcast address in /etc/llttab explicitly depending on the subnet for each link.
■ See “ Sample configuration: direct-attached links ” on page 161. ■ See “ Sample configuration: links crossing IP routers ” on page 163. Table A-1 describes the fields of the link command that are shown in the /etc/llttab file examples. Note that some of the fields differ from the command for standard LLT links.
Table A-2 Field description for set-addr command in /etc/llttab Description Field The ID of the cluster node; for example, 0. node-id The string that LLT uses to identify the link; for example link1, link2,.... link tag-name IP address assigned to the link for the peer node.
For example, with the following interfaces: ■ For first network interface IP address=192.168.30.1, Broadcast address=192.168.30.255, Netmask=255.255.255.0 ■ For second network interface IP address=192.168.31.1, Broadcast address=192.168.31.255, Netmask=Mask:255.
Figure A-1 A typical configuration of direct-attached links that use LLT over UDP UDP Endpoint eth1; UDP Port = 50001; IP = 192.1.3.1; Link Tag = link2 UDP Endpoint eth2; UDP Port = 50000; IP = 192.1.2.1; Link Tag = link1 eth1; 192.1.3.2; Link Tag = link2 eth2; 192.
link link1 udp - udp 50000 - 192.1.2.2 192.1.2.255 link link2 udp - udp 50001 - 192.1.3.2 192.1.3.255 Sample configuration: links crossing IP routers Figure A-2 depicts a typical configuration of links crossing an IP router employing LLT over UDP. The illustration shows two nodes of a four-node cluster.
set-addr 3 link1 192.1.7.3 set-addr 3 link2 192.1.8.3 #disable LLT broadcasts set-bcasthb 0 set-arp 0 The /etc/llttab file on Node 0 resembles: set-node Node0 set-cluster 1 link link1 udp - udp 50000 - 192.1.1.1 - link link2 udp - udp 50001 - 192.1.2.
To perform automated installation 1 Navigate to the folder containing the installvcs program. # cd /mnt/cdrom/cluster_server 2 Start the installation from one of the cluster systems where you have copied the response file. # ./installvcs -responsefile /tmp/ response_file Where /tmp/response_file is the response file ’ s full path name.
$CPI::CFG{CMC_SERVICE_PASSWORD}="U2FsdVkX18v...n0hTSWwodThc+rX"; $CPI::CFG{ENCRYPTED}="U2FsdGVkX1+k2DHcnW7b6...ghdh+zW4G0WFIJA="; $CPI::CFG{KEYS}{east}=[ qw(XXXX-XXXX-XXXX-XXXX-XXX.
Table A-3 Response file variables (continued) Description Variable List of systems on which the product is to be installed, uninstalled, or configured. List or scalar: list Optional or required: required $CPI::CFG{SYSTEMS} List of systems to be recognized in configuration if secure environment prevents all systems from being installed at once.
Table A-3 Response file variables (continued) Description Variable Defines a location, typically an NFS mount, from which all remote systems can install product depots.
Table A-3 Response file variables (continued) Description Variable List of keys to be registered on the system. List or scalar: list Optional or required: optional $CPI::CFG{KEYS} {SYSTEM} Mentions the location where the log files are to be copied. The default location is /opt/VRTS/install/logs.
Table A-3 Response file variables (continued) Description Variable Defines the minimum severity level of messages (Information, Warning, Error, SevereError) that listed SMTP recipients are to receive. Note that the ordering of severity levels must match that of the addresses of SMTP recipients.
Table A-3 Response file variables (continued) Description Variable List of systems where VCS must be uninstalled. List or scalar: scalar Optional or required: optional $CPI::CFG{OPT}{UNINSTALL} Instal.
5 After the installation is complete, review the installer report. The installer stores the installvcs- universaluniqueidentifier response file in the /opt/VRTS/install/logs/installvcs- universaluniqueidentifier /.response directory where universaluniqueidentifier is a variable to uniquely identify the file.
A about global clusters 17 adding users 71 adding node to a one-node cluster 143 attributes UseFence 101 C cables cross-over Ethernet 123 cluster creating a single-node cluster installer 139 manual 14.
F fibre channel 23 G GAB description 15 manual configuration 149 port membership information 116 verifying 116 gabconfig command 116, 149 -a (verifying GAB) 116 gabtab file creating 149 verifying afte.
llttab file verifying after installation 105 M MAC addresses 40 main.cf file contents after installation 108 MANPATH variable setting 47 manual installation preparing 123 media speed 48 optimizing 48 .
starting installation installvcs program 62 Veritas product installer 62 starting VCS 77 storage fully shared vs. distributed 14 shared 14 switches 40 Symantec Product Authentication Service 19, 33, 6.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Symantec 5 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Symantec 5 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Symantec 5 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Symantec 5 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Symantec 5, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Symantec 5.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Symantec 5. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Symantec 5 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
