Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.2 Guida di Installazione

Navigare online o scaricare Guida di Installazione per Sistemi operativi Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.2. Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.2 Installation guide Manuale Utente

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa

Sommario

Pagina 2

1.5 SAP OverviewIn an SAP NetWeaver environment, these single points of failure (SPOF) must be considered: Database SAP Central Services Instance (

Pagina 3 - Table of Contents

To ensure that the (A)SCS "follows" the ERS instance, the follow-service dependency wasimplemented in RHCS.The SAP System Mount Directory sh

Pagina 4

 Cluster Servers: (2) Fujitsu Siemens Rx220 Storage: EMC CLARiiON SAN Infrastructure: QLogicSAP Installation: SAP NetWeaver 2004, WebAS ABAP on

Pagina 5

3.3 Network RequirementsThere should be at least two Network Interface Cards (NIC), whether embedded or added toeach server. Where multiple network i

Pagina 6

In the event of a major network problem, cluster partitioning (aka: split-brain situation) canoccur. Each partition can no longer communicate with nod

Pagina 7 - 1 Executive Summary

The quorum disk daemon (qdiskd) runs on each node in the cluster, periodically evaluating itsown health and then placing its state information into an

Pagina 8 - 1.3 Acronyms

GFS runs on each node in a cluster. As with all file systems, it is basically a kernel modulethat runs on top of the Virtual File System (VFS) layer o

Pagina 9 - 1.4 Reference Documentation

Please note, that the SCSI fencing mechanism requires persistent SCSI reservations. Pleasecontact Red Hat technical support and your storage hardware

Pagina 10 - 1.5 SAP Overview

On a clustered volume group, the following command can be used to create a cluster awaremirror:# lvcreate -m1 -L 1G -n my_new_lv my_vg 4.10 Cluster Re

Pagina 11 - 2 Testbed Environment

Compared to other cluster concepts, the management and operation is straightforward. Withclassic application clusters, the complexity of management is

Pagina 12 - 3 Hardware Requirements

Deploying Highly Available SAP® Servers using Red Hat® Cluster Suite1801 Varsity DriveRaleigh NC 27606-2072 USAPhone: +1 919 754 3700Phone: 888 733 4

Pagina 13 - 4 Red Hat Cluster Basics

fence device, disable ACPI Soft-Off for that node. Otherwise, if ACPI Soft-Off is enabled, anintegrated fence device can take four or more seconds to

Pagina 14 - 4.4 Qdisk

5.2.3 Hosts fileThe /etc/hosts file for each cluster member should contain an entry defining localhost. If theexternal host name of the system is def

Pagina 15 - 4.5 GFS

5.3.3.1 LVM ConfigurationThe LVM configuration file /etc/lvm/lvm.conf must be modified to enable the use of CLVM.1. By default, the LVM commands scan

Pagina 16 - 4.7 Fencing

mechanism In a cluster setup, lockproto:=lock_dlmFurther information about the gfs_mkfs option can be obtained from the gfs:mkfs(8) manpage.The follow

Pagina 17 - 4.8 CLVM

gpgkey=http://download.atix.de/yum/comoonics/comoonics-RPM-GPG.keyInstall the required open-sharedroot software packages:# yum install comoonics-booti

Pagina 18 - 4.14 Management

2. Update the ccs cluster configuration:# ccs_tool update /etc/cluster/cluster.confThe <cluster> tag should define the following attributes:Attr

Pagina 19 - 5.1 OS Customizations

Attribute Descriptionto CMAN when it has a high enough score. log_level Controls the verbosity of the quorum daemon in thesystem logs. 0 = emergenc

Pagina 20 - 5.2 Network Configuration

For more detailed information, refer to the qdisk man page.If device mapper multipath is used together with qdiskd, the values for tko and interval mu

Pagina 21 - 5.3 Storage Configuration

fencing mechanism are encapsulated within the <fence> tag. Each fencing mechanism isdefined by the <method> tag.Please refer to the man pa

Pagina 22 - 5.3.4 GFS

After the installation of the first node is complete, the installation must be transferred to ashared root device and some modifications must be perfo

Pagina 23 - 5.4.1 Core Cluster Software

Table of Contents 1 Executive Summary...7

Pagina 24

6.1.2 SAP Virtual IP AddressesSAP NetWeaver is typically installed via the graphical installation tool sapinst. Beforebeginning the installation, det

Pagina 25 - 5.5.2 Qdisk

Follow the database file system configuration recommendations from the SAP installationguide. It is recommended to have physically different mount poi

Pagina 26

Depending on the Installation Master CD that was used for the SAP installation, the loginprofiles for the SAP administrator user (<sid>adm) and

Pagina 27 - 5.5.4 Cluster Nodes

As a general requirement, the SAP parameter es/implementation must be set to "std" in theSAP DEFAULT.PFL file. See SAP Note 941735. The SAP

Pagina 28 - # service cman start

6.2.2 SAP Virtual IP AddressesSAP NetWeaver is typically installed via the graphical installation tool sapinst. Beforebeginning the installation, det

Pagina 29 - 6 SAP Installation

The transport directory /usr/sap/trans should also be exported via NFS according to your SAPlandscape. 6.2.3.4 Before Starting the SAP InstallationBef

Pagina 30 - 6.1.3 SAP File Systems

Copy the files /etc/oratab and /etc/oraInst.loc to the GFS mount point /oracle and create linksto them. 6.2.5.3 SAP ProfilesThe most important SAP pro

Pagina 31

6.3 Shared Root and Shared Storage with GFS 6.3.1 SAP ArchitectureFollowing the established SAP documentation is highly recommended: SAP Installatio

Pagina 32

The database directories can also completely reside on GFS. Follow the database file systemsetup recommendations from the SAP installation guide. It i

Pagina 33 - 6.2.1 SAP Architecture

6.3.5.2 SAP ProfilesThe most important SAP profile parameter for a clustered SAP system is SAPLOCALHOST.After the installation with sapinst, ensure t

Pagina 34 - 6.2.3 SAP File Systems

5.1.2 ACPI...19 5.1.3 Firewall...

Pagina 35

The following resource types will be defined to provide the high availability functionality forSAP. 7.2 ConfigurationThe resource group manager is con

Pagina 36

basic configuration schema:<rm> <failoverdomains> <failoverdomain name="name" restricted="[0|1]" ordered=&quo

Pagina 37 - 6.3.3 SAP File Systems

7.4 Cluster Resources and ServicesThere are many types of cluster resources that can be configured. Resources are bundledtogether to highly available

Pagina 38

7.4.1 IPThe ip resource defines an ipv4 or ipv6 network address. The following attributes can bedefined:Attribute Description Requiredaddress IPv4 or

Pagina 39 - 7 Resource Manager

Attribute Description Requiredreferencemountpoint Path within file system hierarchy at which tomount this file system.Yesdevice Block device, file sys

Pagina 40 - 7.3 Failover Domains

standalone web dispatcher instance which will fail to work with the resource agent. The nextversion of the agent can have a parameter that could be us

Pagina 41

Attribute Description Requiredafter the default SAP installation. DEFAULT:/usr/sap/<SID>/<INSTANCE>/exeor /usr/sap/<SID>/SYS/exe/run

Pagina 42

Attribute Description Requiredbe more important that the ABAPinstance be up and running. A failure ofthe JAVA instance will not cause afailover of the

Pagina 43 - or cifs) No

Attribute Description RequiredPOST_STOP_USEREXIT uses. Those programs can include bywriting an OCF resource agent into theHeartbeat cluster. However,

Pagina 44 - 7.4.4 SAPInstance

Attribute Description RequiredDIR_EXECUTABLE The full qualified path to the SAP kernel.The resource agent requires the startdband the R3trans executab

Pagina 45 -  GREEN = everything is fine

6.1.5.4 SAP Release-specific Post-processing...33 6.1.5.5 Before Starting the Cluster...

Pagina 46

Attribute Description RequiredNot fort use with Oracle as it will result inunwanted failovers in the case of a stuckarchiver. DEFAULT: falseAUTOMATIC_

Pagina 47

Attribute Description RequiredThis is required only if theDBJ2EE_ONLY parameter is set to true. It will be automatically read from thebootstrap.proper

Pagina 48 - 7.4.5 SAPDatabase

7.5 Dependencies 7.5.1 Resource DependenciesThe resources within a cluster service follow two different dependency rules. First, the nesting within t

Pagina 49

7.5.2.2 Follow Service DependencyThe follow service dependency makes use of rgmanager's RIND event scripting mechanism.In order to activate the

Pagina 50

8 Cluster Management 8.1 CMANThe basic cluster operation can be verified using the cman_tool utility 8.1.1 cman_tool statusThe cman_tool status comma

Pagina 51

dlm 1 root 00040001 none [1 2] dlm 1 clvmd 00020001 none [1] dlm 1 rhc_a

Pagina 52 - 7.5 Dependencies

8.2.2 clusvcadmThe resource manager services can be controlled by the clusvcadm command. The basicoperations are: clusvcadm -e <service> -m &l

Pagina 53

8.3.2 Update initrdIn a sharedroot cluster, the cluster configuration file /etc/cluster/cluster.conf must be copiedinto the initrd. Therefore the pro

Pagina 54 - 8 Cluster Management

enterprisecopy/localclone.xmlFor detailed information regarding the comoonics enterprise software solution, please consultthe Comoonics Enterprise Cop

Pagina 55 - 8.2 rgmanager

</clusternodes> <fencedevices> <fencedevice name="ipmi" agent="fence_ipmilan" auth="password"logi

Pagina 56 - 8.3 Open-Sharedroot

7.4.3 FS...44 7.4.4 SAPInstance

Pagina 57 - 8.3.3 Cluster Clone

evalfile("/usr/local/cluster/follow-service.sl"); follow_service("service:rhc_ascs", "service:rhc_ers",&

Pagina 58 - Appendix A: cluster.conf

## Device attributes for EMC CLARiiON device { vendor "DGC " product "*" getuid_call

Pagina 59

multipath { wwid 360060160eda50800a155ad9b6a54db11 alias DGC_012 } multipath { wwid 360060160eda508009f55ad9b6a54db11 alias DGC_013 } mult

Pagina 60 - Appendix B: multipath.conf

scan = [ "/dev/mapper" ] # If several entries in the scanned directories correspond to the # same block device and the tools nee

Pagina 61

# It is safe to delete the contents: the tools regenerate it. # (The old setting 'cache' is still respected if neither of # thes

Pagina 62 - Appendix C: lvm.conf

# What level of log messages should we send to the log file and/orsyslog? # There are 6 syslog-like log levels currently in use - 2 to 7inclus

Pagina 63

archive_dir = "/etc/lvm/archive" # What is the minimum number of archive files you wish to keep ? retain_min = 10 # What

Pagina 64 - 64

"lvm2". # The command line override is -M1 or -M2. # Defaults to "lvm1" if compiled in, else "lvm2". # forma

Pagina 65

# For now, you need to set this up yourself first (e.g., with'dmsetup') # For example, you could make it return I/O errors using the

Pagina 66 - 66

# Currently this is not implemented properly and behaves # similarly to: # # "allocate_anywhere" - Ope

Pagina 67

1 Executive SummaryThis paper details the deployment of a highly available SAP service on a Red Hat EnterpriseLinux 5 cluster. After an introduction

Pagina 68 - 68

# Event daemon # # dmeventd { # mirror_library is the library used when monitoring a mirror device. # # "libdevmapper-event-lvm2mirro

Pagina 69

1.2 AudienceThis document addresses SAP certified technical consultants for SAP NetWeaver withexperience in HA systems. Access to SAP information res

Pagina 70 - 70

RHCS Red Hat Cluster SuiteRHEL Red Hat Enterprise LinuxRIND Rind Is Not DependenciesSAN Storage Area NetworkSCS SAP Central Services Instance (for J

Commenti su questo manuale

Nessun commento