inst-9211-lec_manual.pdf

7/24/2019 Inst-9211-lec_manual.pdf

1/194


2/194

#ro$rietary State%ent Copyright 2010 Novell, Inc. All rights reserved.

Novell, Inc., has intellectual property rights relating to technology embodied inthe product that is described in this document. In particular, and withoutlimitation, these intellectual property rights may include one or more o the !.".patents listed on the Novell Legal Patents Web page(http://www.novell.com/company/legal/patents/) and one or moreadditional patents or pending patent applications in the !.". and in othercountries.

No part o this publication may be reproduced, photocopied, stored on a retrievalsystem, or transmitted without the e#press written consent o the publisher.

Novell, Inc.$0$ %yman "treet, "uite &00%altham, 'A 02$&1!.".A.www.novell.com

&ovell 'ra(e%ar)sFor Novell trademarks see the Novell !rademark and "ervice #ark list(http://www.novell.com/company/legal/trademarks/tmlist.html) .

'hir(*#arty aterialsAll third(party trademar)s are the property o their respective owners.

So+tware #iracy*hroughout the world, unauthori+ed duplication o so tware is sub ect to bothcriminal and civil penalties.

I you )now o illegal copying o so tware, contact your local "o twareAntipiracy -otline. For the $otline n%mber &or yo%r area access Novell'sWorld Wide Web page (http://www.novell.com) and look &or the piracypage %nder Programs.r, contact Novell/s anti(piracy head uarters in the !.". at 00( I3A*4" 56$6(*+,-) or + 0+1 0- .

,isclai%er Novell, Inc., ma)es no representations or warranties with respect to the contentsor use o this documentation, and speci ically disclaims any e#press or impliedwarranties o merchantability or itness or any particular purpose.

7urther, Novell, Inc., reserves the right to revise this publication and to ma)echanges to its content, at any time, without obligation to noti y any person orentity o such revisions or changes. 7urther, Novell, Inc., ma)es norepresentations or warranties with respect to any so tware, and speci icallydisclaims any e#press or implied warranties o merchantability or itness or anyparticular purpose. 7urther, Novell, Inc., reserves the right to ma)e changes toany and all parts o Novell so tware, at any time, without any obligation to noti yany person or entity o such changes.

Any products or technical in ormation provided under this Agreement may besub ect to !.". e#port controls and the trade laws o other countries. 8ou agree tocomply with all e#port control regulations and to obtain any re uired licenses orclassi ication to e#port, re(e#port or import deliverables. 8ou agree not to e#portor re(e#port to entities on the current !.". e#port e#clusion lists or to anyembargoed or terrorist countries as speci ied in the !.". e#port laws. 8ou agreeto not use deliverables or prohibited nuclear, missile, or chemical biologicalweaponry end %ses. "ee the Novell 2nternational !rade "ervices Webpage (http://www.novell.com/in&o/e3ports/) &or more in&ormation one3porting Novell so tware. Novell assumes no responsibility or your ailure toobtain any necessary e#port approvals.

*his Novell *raining 'anual is published solely to instruct students in the use oNovell networ)ing so tware. Although third(party application so tware pac)agesare used in Novell training courses, th is is or demonstration purposes only andshall not constitute an endorsement o an y o these so tware applications.

7urther, Novell, Inc. does not represent itsel as having any particular e#pertisein these application so tware pac)ages and any use by students o the same shallbe done at the st%dent's own risk.
http://www.novell.com/http://www.novell.com/


3/194

Contents

Copying all or part of this manual, or distributing such copies, is strictly prohibited.To report suspected copying, please call 1-800-PIRATES.

5Version 1

SECTION 1 Introduction to HA Clustering in SLE11 7

SECTION 2 Install and Configure HA Clustering in SLE11 37

SECTION 3 Introduction to the Cluster Information Base 53

SECTION 4 Introduction to Cluster Resources 75

SECTION 5 Manage Clustered Storage with a SAN 95

SECTION 6 Splitbrain Avoidance and Management 111

SECTION 7 Configure Safe Logical Clusterd Storage 131

SECTION 8 Configure Active Active Clusters Storage 159


4/194

"High Availability Clustering with the SLE HA Extension 11"


Version 16


5/194


7Version 1

Introduction to HA Clustering in SLE11

S E C T I O N 1 Introduction to HA Clustering in SLE11

Notes:


6/194



Version 18

Notes:


7/194


9Version 1


Notes:


8/194



Version 110

Notes:


9/194


11Version 1


Notes:


10/194



Version 112

Notes:


11/194


13Version 1


Notes:


12/194



Version 114

Notes:


13/194


15Version 1


Notes:


14/194



Version 116

Notes:


15/194


17Version 1


Notes:


16/194



Version 118

Notes:


17/194


19Version 1


Notes:


18/194



Version 120

Notes:


19/194


21Version 1


Notes:


20/194



Version 122

Notes:


21/194


23Version 1


Notes:


22/194



Version 124

Notes:


23/194


25Version 1


Notes:


24/194



Version 126

Notes:


25/194


27Version 1


Notes:


26/194



Version 128

Notes:


27/194


29Version 1


Notes:

Acronyms:

CRM = Cluster Resource Manager

DC = Designated Controller (master node)


28/194



Version 130

Notes:

Acronyms:



CIB = Cluster Information Base


29/194


30/194



Version 132

Notes:

Acronyms:




PE = Policy Engine

STONITH = Shoot The Other Node In The Head (Fencing daemon)


31/194


33Version 1


Notes:

Acronyms:




PE = Policy Engine


LRM = Local Resource Manager


32/194



Version 134

Notes:

Acronyms:




PE = Policy Engine



RA = Resource Agent


33/194


35Version 1


Notes:

Acronyms:




PE = Policy Engine



RA = Resource Agent

OpenAIS = Cluster membership daemon


34/194



Version 136

Notes:

Acronyms:




PE = Policy Engine



RA = Resource Agent


35/194


37Version 1

Install and Configure HA Clustering in SLE11

S E C T I O N 2 Install and Configure HA Clustering inSLE11

Notes:


36/194



Version 138

Notes:


37/194


39Version 1


Notes:


38/194



Version 140

Notes:


39/194


41Version 1


Notes:


40/194



Version 142

Notes:


41/194


43Version 1


Notes:


42/194



Version 144

Notes:


43/194


45Version 1


Notes:


44/194



Version 146

Notes:


45/194


47Version 1


Notes:


46/194



Version 148

Notes:


47/194


49Version 1


Notes:


48/194



Version 150

Notes:


49/194


51Version 1


Notes:


50/194



Version 152

Notes:


51/194


53Version 1

Introduction to the Cluster Information Base

S E C T I O N 3 Introduction to the Cluster Information Base

Notes:


52/194



Version 154

Notes:


53/194


55Version 1


Notes:


54/194



Version 156

Notes:

Example CIB XML from a running 2 node cluster


55/194


57Version 1


Notes:

The Cluster Information Base consists of two main parts and . The tag also contains important information about the cluster.

-Stores the cluster configuration information

-This is stored on disk so that it can be loaded into memory when the heartbeatdaemon starts

-This portion of the CIB is persistent

-Stores the current state of the cluster

-This is dynamically generated and therefore never stored on disk

-This portion of the CIB is dynamically generated.

The section contains information about the state of the cluster as known by anindividual node.


56/194



Version 158

Notes:

The Section:

admin_epoch=

-Can be defined by the administrator to force the CIB on one node to override allother CIBs

-The CIB on the node with the highest admin_epoch will be synchronized to all othercluster nodes

epoch=

-Automatically updated after a re-election of the DC

-The epoch value on a cluster node must agree with the other cluster nodes for thatnode to have quorum

num_updates=

-Automatically updated after any change to the CIB


57/194


59Version 1



58/194



Version 160

Notes:

The configuration section contains 4 main sections:

-contains general cluster configuration values

-if empty the defaults apply

-contains a list of cluster nodes

-contains a list of cluster resources

-contains a list of cluster resource constraints


59/194


61Version 1


Notes:

-contains general cluster configuration values

-if empty the defaults apply


60/194



Version 162

Notes:

-contains a list of cluster nodes


61/194


63Version 1


Notes:

-contains a list of cluster resources


62/194



Version 164

Notes:

-contains a list of cluster resource constraints


63/194


65Version 1


Notes:

The Section:

The status section contains information about the current state of the cluster. Thistypically will include entries for the nodes currently joined to the cluster as well asthe resources running on those nodes.


64/194



Version 166

Notes:

The Section:

The section contains information about the current status of a clusternode


65/194


67Version 1


Notes:

The Section:

The section of the section contains entries for each resourcethat is running on that node or has run on that node.


66/194



Version 168

Notes:


67/194


69Version 1


Notes:


68/194



Version 170

Notes:

The CRM_GUI is a graphical cluster management utility.


69/194


71Version 1


Notes:

The crm_mon command is no-interactive ans does nothing more than to display thecurrent state of the cluster (nodes and resource). The default refresh time is 15seconds. This can be changed using the -i option.

Example: crm_mon -i 1 (for a 1 second refresh)


70/194



Version 172

Notes:

The crm command has a number of sub functions that are used to manage the cluster.Here are some examples of how the crm command can be used:

Resource Management:

crm resource is used to manage cluster resources

Resource Configuration:

crm configure is used to configure cluster resources

Node Configuration:

crm node is used to configure cluster nodes


71/194


73Version 1


Notes:


72/194



Version 174

Notes:


73/194


75Version 1

Introduction to Cluster Resources

S E C T I O N 4 Introduction to Cluster Resources

Notes:


74/194



Version 176

Notes:


75/194


77Version 1


Notes:


76/194



Version 178

Notes:

Note: stonith can also be a resource agent type but it is only used for stonith devices.


77/194


79Version 1


Notes:


78/194



Version 180

Notes:


79/194


81Version 1


Notes:

LSB scripts:

-These scripts support only the start, stop, restart, reload, force-reload, and status parameters.

Example:


80/194



Version 182

Notes:

Heartbeat scripts:

Example:


81/194


83Version 1


Notes:

OCF scripts:

-These scripts are categorized by provider (or the component with witch they are packaged)

--(providers include, heartbeat, lvm2, ocfs2, pacemaker)

-The scripts exist in subdirectories named for the respective provider, of /usr/lib/ocf/resource.d/

-These scripts allow for parameters to be passed in when the script is run. Thisenables you to define parameters for the script to operate on such as the IP addressand NIC to operate on, etc.

-To display all of the parameters that an OCF script can accept the meta-data parameter can be used when calling an OCF script from the CLI.

Example:

/usr/lib/ocf/resource.d/heartbeat/Ipaddr2 metadata

-To test if certain values will work with the script the validate-all parameter can beused when calling an OCF script from the CLI.


82/194



Version 184

-The values that are passed in from the CLI are always proceeded byOCF_RESKEY_

Example:

OCF_ROOT=/usr/lib/ocf OCF_RESKEY_ip=10.0.0.1 OCF_RESKEY_nic=eth0 /usr/lib/ocf/resource.d/heartbeat/Ipaddr2 validate-all


83/194


85Version 1


Notes:

STONITH scripts:

-These can be either scripts or binaries.

Example:


84/194



Version 186

Notes:


85/194


87Version 1


Notes:

attribute definitions:

id = Unique identifying value

class = Type of resource agent being used (i.e. ocf, lsb, heartbeat, etc.). Defineslocation

(in the file system) to start looking for the agent referenced in the type = field

type = The name of the resource agent script being called

provider = The subdirectory of the path defined by the class that contains the script

parameters are passed to the LRM

parameters are passed to the RA scripts


86/194



Version 188

Notes:


87/194


89Version 1


Notes:


88/194



Version 190

Notes:

Clone resources are an extension of primitive resources and therefor include them intheir definitions.

clone_node_max :The maximum number of instances of the resource that areallowed to run per node.

clone_max :The maximum number of instances of the resource that are allowed torun in the cluster


89/194


91Version 1


Notes:

Master/Slave resources are also an extension of primitive resources and thereforeinclude them in their definition


90/194


91/194


93Version 1


Notes:


92/194



Version 194

Notes:


93/194


95Version 1

Manage Clustered Storage with a SAN

S E C T I O N 5 Manage Clustered Storage with a SAN

Notes:


94/194



Version 196

Notes:


95/194


97Version 1


Notes:


96/194



Version 198

Notes:


97/194


99Version 1


Notes:


98/194



Version 1100

Notes:


99/194


101Version 1


Notes:


100/194


101/194


103Version 1


Notes:

Fibre channel hardware is expensive and complex to manage. SLES iSCSI lets youconsolidate storage and improve the management of your storage infrastructure onthe well known TCP/IP infrastructure. It is a lower cost, more flexible alternative tofibre channel. With SLES iSCSI, you can easily add storage and repartition existingstorage between systems and logical groupings. If one user volume is growing toorapidly, storage from another area can be allocated to it.

Some of the benefits of implementing iSCSI include

Low-cost hardware requirements

Longer distance storage connectivity

Easy-to-manage SAN solution

Scalability and flexibility

Reduced SAN management training requirements

Increased flexibility in storage management and growth

Ability to create a SAN from existing direct-attached storage servers


102/194



Version 1104

Notes:


103/194


105Version 1


Notes:


104/194



Version 1106

Notes:


105/194


107Version 1


Notes:


106/194



Version 1108

Notes:


107/194


108/194



Version 1110

Notes:


109/194


111Version 1

Splitbrain Avoidance and Management

S E C T I O N 6 Splitbrain Avoidance and Management

Notes:


110/194



Version 1112

Notes:


111/194


113Version 1


Notes:


112/194



Version 1114

Notes:


113/194


115Version 1


Notes:


114/194



Version 1116

Notes:


115/194


117Version 1


Notes:


116/194



Version 1118

Notes:


117/194


119Version 1


Notes:


118/194



Version 1120

Notes:


119/194


121Version 1


Notes:

Typically the STONITH action should be to power off or panic the offendingmachine. Common STONITH devices used in production are network managed

power switches and remote server administration boards (DRAC, RILO, etc.)


120/194



Version 1122

Notes:


121/194


123Version 1


Notes:

The SBD daemons purpose is to monitor a specific part of a shared disk for a poison pill and shutdown or restart the cluster node if it is present. This shared disk, wheninitialized, will contain slots for each cluster node to monitor. The first time theSBD daemon starts on a node it will attempt to claim a slot on the SBD device.This is portion of the disk that it will monitor for poison pills.

In the SLE HAE, the openais init script will attempt to start the SBD daemon beforestarting any other part of the cluster stack. If the SBD daemon cannot start, the rest ofthe cluster stack will not start. The init script will only attempt to start the SBDdaemon if the /etc/sysconfig/sbd file exists.

The /etc/sysconfig/sbd file contains two variables:

SBD_DEVICE= (device file used as the SBD device.)

SBD_OPTS= (CLI options to pass to the SBD daemon when it is launched)

The device used as the SBD_DEVICE can be very small because each slot is nolarger than 1 disk block. It is also recommended that you refer to the SBD deice by its

persistent device name (found in /dev/disk/)

You should also enable the SBD daemon to use the watchdog device. The watchdogis used to ensure that th SBD daemon can communicate with the shared storage. If itcannot, the watchdog will fire causing the node to reboot. (For this reason you maywish to NOT have the cluster stack start automatically at boot time to avoid a possibleinfinite reboot loop if the SBD device is not accessible.)


122/194



Version 1124

To enable the watchdog, you first must ensure that the appropriate wachdog kernelmodule softdog kernel module loads at boot time (common watchdog kernelmodules: softdog =generic watchdog device, hpwdt =HP hardware watchdog device,iTCO_wdt =Intel hardware watchdog device). You can do this by adding the kernelmodule to the MODULES_LOADED_ON_BOOT= line of the /etc/sysconfig/kernel

file (or by adding modprobe KERNEL_MODULE_NAME to the /etc/init.d/ boot.local file). You then need to add -W to SBD_OPTS= variable in the /etc/ sysconfig/sbd file.

If your SBD device resides on a multipath group, you may need to adjust the timeoutsSBD uses, as MPIO's path down detection can cause delays.

After the msgwait timeout, the message is assumed to have been delivered to thenode. For multipath, this should be the time required for MPIO to detect a path failureand switch to the next path. You may have to test this in your environment.

The node will perform suicide if it has not updated the watchdog timer fast enough;the watchdog timeout must be shorter than the msgwait timeout - half the value is a

good rule of thumb. To do this add the following to the SBD_OPTS= variable in the / etc/sysconfig/sbd file:

-1 -4


123/194


125Version 1


Notes:

To enable SBD fencing, once the daemon is running, you must create a STONITHcluster resource for SBD.

As with all STONITH resources, a single instance is sufficient. If the cluster nodethat is currently running the SBD resource needs to be fenced (in the case of a split-

brain), another instance of the SBD resource will be stared to perform the fencingaction (due to the node with the split-brain not being able to perform any action

because it does not have quorum).


124/194



Version 1126

Notes:


125/194


127Version 1


Notes:


126/194



Version 1128

Notes:


127/194


129Version 1


Notes:


128/194



Version 1130


129/194


131Version 1

Configure Safe Logical Clusterd Storage

S E C T I O N 7 Configure Safe Logical Clusterd Storage

Notes:


130/194



Version 1132

Notes:


131/194


133Version 1


Notes:


132/194



Version 1134

Notes:


133/194


135Version 1


Notes:


134/194



Version 1136

Notes:


135/194


136/194



Version 1138

Notes:


137/194


139Version 1


Notes:


138/194



Version 1140

Notes:


139/194


141Version 1


Notes:


140/194



Version 1142

Notes:


141/194


143Version 1


Notes:


142/194



Version 1144

Notes:


143/194


145Version 1


Notes:


144/194



Version 1146

Notes:


145/194


147Version 1


Notes:


146/194


147/194


149Version 1


Notes:


148/194



Version 1150

Notes:


149/194


151Version 1


Notes:


150/194



Version 1152

Notes:


151/194


153Version 1


Notes:


152/194



Version 1154

Notes:


153/194


155Version 1


Notes:


154/194



Version 1156

Notes:


155/194


157Version 1


Notes:


156/194



Version 1158

Notes:


157/194


159Version 1

Configure Active Active Clusters Storage

S E C T I O N 8 Configure Active Active Clusters Storage

Notes:


158/194



Version 1160

Notes:


159/194


160/194



Version 1162

Notes:


161/194


163Version 1


Notes:


162/194



Version 1164

Notes:


163/194


164/194



Version 1166

Notes:


165/194


167Version 1


Notes:


166/194



Version 1168

Notes:


167/194


169Version 1


Notes:


168/194



Version 1170

Notes:


169/194


171Version 1


Notes:


170/194



Version 1172

Notes:


171/194


173Version 1


Notes:


172/194



Version 1174

Notes:


173/194


175Version 1


Notes:


174/194



Version 1176

Notes:


175/194


177Version 1


Notes:


176/194


177/194


179Version 1


Notes:


178/194



Version 1180

Notes:


179/194


180/194



Version 1182

Notes:


181/194


182/194



Version 1184

Notes:


183/194


185Version 1


Notes:


184/194



Version 1186

Notes:


185/194


187Version 1


Notes:


186/194



Version 1188

Notes:


187/194


188/194


189/194


191Version 1


Notes:


190/194



Version 1192

Notes:


191/194


193Version 1


Notes:


192/194



Version 1194

Notes:


193/194


195Version 1


Notes:


194/194


inst-9211-lec_manual.pdf

Documents