SUSE Linux Enterprise High Availability 15 SP7
This guide is intended for administrators who need to set up, configure, and maintain clusters with SUSE® Linux Enterprise High Availability. For quick and efficient configuration and administration, the product includes both a graphical user interface and a command line interface (CLI). For performing key tasks, both approaches are covered in this guide. Thus, you can choose the appropriate tool that matches your needs.
Publication Date:
September 25, 2025
- Preface
- I Installation and setup
- 1 Product overview
- 2 Installation overview
- 3 System requirements and recommendations
- 4 Logging in to the cluster nodes
- 5 Installing SUSE Linux Enterprise High Availability
- 6 Using the bootstrap scripts
- 7 Using the YaST cluster module
- 7.1 Definition of terms
- 7.2 Starting the YaST module
- 7.3 Defining the communication channels
- 7.4 Configuring an arbitrator for quorum decisions
- 7.5 Defining authentication settings
- 7.6 Configuring Csync2 to synchronize files
- 7.7 Synchronizing connection status between cluster nodes
- 7.8 Configuring services
- 7.9 Transferring the configuration to all nodes
- 7.10 Bringing the cluster online
- 8 Deploying nodes with AutoYaST
- II Configuration and administration
- 9 Configuration and administration basics
- 10 Configuring cluster resources
- 10.1 Types of resources
- 10.2 Supported resource agent classes
- 10.3 Timeout values
- 10.4 Creating primitive resources
- 10.5 Creating resource groups
- 10.6 Creating clone resources
- 10.7 Creating promotable clones (multi-state resources)
- 10.8 Creating resource templates
- 10.9 Creating STONITH resources
- 10.10 Configuring resource monitoring
- 10.11 Loading resources from a file
- 10.12 Resource options (meta attributes)
- 10.13 Instance attributes (parameters)
- 10.14 Resource operations
- 11 Configuring resource constraints
- 11.1 Types of constraints
- 11.2 Scores and infinity
- 11.3 Resource templates and constraints
- 11.4 Adding location constraints
- 11.5 Adding colocation constraints
- 11.6 Adding order constraints
- 11.7 Using resource sets to define constraints
- 11.8 Specifying resource failover nodes
- 11.9 Specifying resource failback nodes (resource stickiness)
- 11.10 Placing resources based on their load impact
- 11.11 For more information
- 12 Managing cluster resources
- 13 Managing services on remote hosts
- 14 Adding or modifying resource agents
- 15 Monitoring clusters
- 16 Fencing and STONITH
- 17 Storage protection and SBD
- 17.1 Conceptual overview
- 17.2 Overview of manually setting up SBD
- 17.3 Requirements and restrictions
- 17.4 Number of SBD devices
- 17.5 Calculation of timeouts
- 17.6 Setting up the watchdog
- 17.7 Setting up SBD with devices
- 17.8 Setting up diskless SBD
- 17.9 Testing SBD and fencing
- 17.10 Additional mechanisms for storage protection
- 17.11 Changing SBD configuration
- 17.12 For more information
- 18 QDevice and QNetd
- 19 Access control lists
- 20 Network device bonding
- 21 Load balancing
- 22 High Availability for virtualization
- 23 Geo clusters (multi-site clusters)
- III Storage and data replication
- IV Maintenance and upgrade
- 32 Executing maintenance tasks
- 32.1 Preparing and finishing maintenance work
- 32.2 Different options for maintenance tasks
- 32.3 Putting the cluster into maintenance mode
- 32.4 Stopping the cluster services for the whole cluster
- 32.5 Putting a node into maintenance mode
- 32.6 Putting a node into standby mode
- 32.7 Stopping the cluster services on a node
- 32.8 Putting a resource into maintenance mode
- 32.9 Putting a resource into unmanaged mode
- 32.10 Rebooting a cluster node while in maintenance mode
- 33 Upgrading your cluster and updating software packages
- 32 Executing maintenance tasks
- V Appendix
- Glossary
- E GNU licenses
List of Figures
- 1.1 Three-server cluster
- 1.2 Three-server cluster after one server fails
- 1.3 Architecture
- 1.4 Typical Fibre Channel cluster configuration
- 1.5 Typical iSCSI cluster configuration
- 1.6 Typical cluster configuration without shared storage
- 7.1 YaST —multicast configuration
- 7.2 YaST —unicast configuration
- 7.3 YaST —Corosync QDevice
- 7.4 YaST —security
- 7.5 YaST —Csync2
- 7.6 YaST —
conntrackd - 7.7 YaST —services
- 9.1 Hawk2—cluster configuration
- 9.2 Hawk2—wizard for Apache web server
- 9.3 Hawk2 batch mode activated
- 9.4 Hawk2 batch mode—injected invents and configuration changes
- 10.1 Hawk2—primitive resource
- 10.2 Group resource
- 10.3 Hawk2—resource group
- 10.4 Hawk2—clone resource
- 10.5 Hawk2—STONITH resource
- 10.6 Operation values
- 10.7 Hawk2—resource details
- 11.1 Hawk2—location constraint
- 11.2 Hawk2—colocation constraint
- 11.3 Hawk2—order constraint
- 11.4 Hawk2—two resource sets in a colocation constraint
- 11.5 Hawk2: meta attributes for resource failover
- 11.6 Hawk2: meta attributes for resource failback
- 11.7 Hawk2: edit node utilization attributes
- 12.1 Hawk2—editing a primitive resource
- 12.2 Hawk2—tag
- 15.1 Hawk2—cluster status
- 15.2 Hawk2 dashboard with one cluster site (
amsterdam) - 15.3 Hawk2 add cluster details
- 15.4 Recent events table
- 15.5 Hawk2—history explorer main view
- 15.6 Hawk2 report details
- 19.1 Hawk2 Create Role
- 19.2 Hawk2 Edit ACL Target
- 21.1 YaST IP load balancing—global parameters
- 21.2 YaST IP load balancing—virtual services
- 25.1 Hawk2 summary screen of OCFS2 CIB changes
- 26.1 Hawk2 summary screen of GFS2 CIB changes
- 27.1 Position of DRBD within Linux
- 27.2 Resource configuration
- 27.3 Resource stacking
- 27.4 Showing a good connection by
drbdmon - 27.5 Showing a bad connection by
drbdmon - 28.1 Setup of a shared disk with Cluster LVM
- 30.1 Structure of a CTDB cluster
- 33.1 Overview of supported upgrade paths
List of Tables
List of Examples
- 9.1 Excerpt of Corosync configuration for a two-node cluster
- 9.2 Excerpt of Corosync configuration for an n-node cluster
- 9.3 A simple
crmshshell script - 10.1 Resource group for a web server
- 11.1 A resource set for location constraints
- 11.2 A chain of colocated resources
- 11.3 A chain of ordered resources
- 11.4 A chain of ordered resources expressed as resource set
- 11.5 Migration threshold—process flow
- 11.6 Creating resource agents for KVM with
hv_memorydisabled - 11.7 Creating resource agents for Xen with
host_memorydisabled - 13.1 Configuring resources for monitoring plug-ins
- 16.1 Configuration of an IBM RSA lights-out device
- 16.2 Configuration of a UPS fencing device
- 16.3 Configuration of a Kdump device
- 17.1 Formula for disk-based SBD timeout calculation
- 17.2 Formula for diskless SBD timeout calculation
- 18.1 Status of QDevice
- 18.2 Status of QNetd server
- 19.1 Excerpt of a cluster configuration in XML
- 21.1 Simple ldirectord configuration
- 27.1 Configuration of a three-node stacked DRBD resource
- 31.1 Using an NFS server to store the file backup
- 31.2 Backing up Btrfs subvolumes with
tar - 31.3 Using third-party backup tools like EMC NetWorker
- 31.4 Backing up multipath devices
- 31.5 Booting your system with UEFI
- 31.6 Creating a recovery system with a basic
tarbackup - 31.7 Creating a recovery system with a third-party backup
- A1 Stopped resources
Copyright © 2006–2025 SUSE LLC e colaboradores. Todos os direitos reservados.
Permissão concedida para copiar, distribuir e/ou modificar este documento sob os termos da Licença GNU de Documentação Livre, Versão 1.2 ou (por sua opção) versão 1.3; com a Seção Invariante sendo estas informações de copyright e a licença. Uma cópia da versão 1.2 da licença está incluída na seção intitulada “GNU Free Documentation License” (Licença GNU de Documentação Livre).
Para saber as marcas registradas da SUSE, visite https://www.suse.com/company/legal/. Todas as marcas registradas de terceiros pertencem aos seus respectivos proprietários. Os símbolos de marca registrada (®, ™ etc.) indicam marcas registradas da SUSE e de suas afiliadas. Os asteriscos (*) indicam marcas registradas de terceiros.
Todas as informações deste manual foram compiladas com a maior atenção possível aos detalhes. Entretanto, isso não garante uma precisão absoluta. A SUSE LLC, suas afiliadas, os autores ou tradutores não serão responsáveis por possíveis erros nem pelas consequências resultantes de tais erros.