This guide is intended for administrators who need to set up, configure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. 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.
- Preface
- I Installation and setup
- II Configuration and administration
- 5 Configuration and administration basics
- 6 Configuring and managing cluster resources with Hawk2
- 6.1 Hawk2 requirements
- 6.2 Logging in
- 6.3 Hawk2 overview: main elements
- 6.4 Configuring global cluster options
- 6.5 Configuring cluster resources
- 6.6 Configuring constraints
- 6.7 Managing cluster resources
- 6.8 Monitoring clusters
- 6.9 Using the batch mode
- 6.10 Viewing the cluster history
- 6.11 Verifying cluster health
- 7 Configuring and managing cluster resources (command line)
- 8 Adding or modifying resource agents
- 9 Fencing and STONITH
- 10 Storage protection and SBD
- 10.1 Conceptual overview
- 10.2 Overview of manually setting up SBD
- 10.3 Requirements
- 10.4 Number of SBD devices
- 10.5 Calculation of timeouts
- 10.6 Setting up the watchdog
- 10.7 Setting up SBD with devices
- 10.8 Setting up diskless SBD
- 10.9 Testing SBD and fencing
- 10.10 Additional mechanisms for storage protection
- 10.11 For more information
- 11 QDevice and QNetd
- 12 Access control lists
- 13 Network device bonding
- 14 Load balancing
- 15 Geo clusters (multi-site clusters)
- III Storage and data replication
- 16 Distributed Lock Manager (DLM)
- 17 OCFS2
- 18 GFS2
- 19 DRBD
- 19.1 Conceptual overview
- 19.2 Installing DRBD services
- 19.3 Setting up DRBD service
- 19.4 Migrating from DRBD 8 to DRBD 9
- 19.5 Creating a stacked DRBD device
- 19.6 Using resource-level fencing with STONITH
- 19.7 Testing the DRBD service
- 19.8 Monitoring DRBD devices
- 19.9 Tuning DRBD
- 19.10 Troubleshooting DRBD
- 19.11 For more information
- 20 Cluster logical volume manager (Cluster LVM)
- 21 Cluster multi-device (Cluster MD)
- 22 Samba clustering
- 23 Disaster recovery with ReaR (Relax-and-Recover)
- IV Maintenance and upgrade
- 24 Executing maintenance tasks
- 24.1 Implications of taking down a cluster node
- 24.2 Different options for maintenance tasks
- 24.3 Preparing and finishing maintenance work
- 24.4 Putting the cluster in maintenance mode
- 24.5 Stopping the cluster services for the whole cluster
- 24.6 Putting a node in maintenance mode
- 24.7 Putting a node in standby mode
- 24.8 Putting a resource into maintenance mode
- 24.9 Putting a resource into unmanaged mode
- 24.10 Rebooting a cluster node while in maintenance mode
- 25 Upgrading your cluster and updating software packages
- 24 Executing maintenance tasks
- V Appendix
- Glossary
- E GNU licenses
- 1.1 Three-server cluster
- 1.2 Three-server cluster after one server fails
- 1.3 Typical Fibre Channel cluster configuration
- 1.4 Typical iSCSI cluster configuration
- 1.5 Typical cluster configuration without shared storage
- 1.6 Architecture
- 4.1 YaST —multicast configuration
- 4.2 YaST —unicast configuration
- 4.3 YaST —security
- 4.4 YaST —
conntrackd - 4.5 YaST —services
- 4.6 YaST —Csync2
- 5.1 Group resource
- 6.1 Hawk2—cluster configuration
- 6.2 Hawk2—wizard for Apache web server
- 6.3 Hawk2—primitive resource
- 6.4 Hawk2—editing a primitive resource
- 6.5 Hawk2—STONITH resource
- 6.6 Hawk2—resource group
- 6.7 Hawk2—clone resource
- 6.8 Hawk2—tag
- 6.9 Hawk2—resource details
- 6.10 Hawk2—location constraint
- 6.11 Hawk2—colocation constraint
- 6.12 Hawk2—order constraint
- 6.13 Hawk2—two resource sets in a colocation constraint
- 6.14 Hawk2—cluster status
- 6.15 Hawk2 dashboard with one cluster site (
amsterdam) - 6.16 Hawk2 batch mode activated
- 6.17 Hawk2 batch mode—injected invents and configuration changes
- 6.18 Hawk2—history explorer main view
- 9.1 Classes of fencing
- 14.1 YaST IP load balancing—global parameters
- 14.2 YaST IP load balancing—virtual services
- 19.1 Position of DRBD within Linux
- 19.2 Resource configuration
- 19.3 Resource stacking
- 19.4 Showing a good connection by
drbdmon - 19.5 Showing a bad connection by
drbdmon - 20.1 Setup of a shared disk with Cluster LVM
- 22.1 Structure of a CTDB cluster
- 2.1 System roles and installed patterns
- 5.1 Resource operation properties
- 7.1 Common parameters
- 8.1 Failure recovery types
- 8.2 OCF return codes
- 10.1 Commonly used watchdog drivers
- 12.1 Operator role—access types and XPath expressions
- 17.1 OCFS2 utilities
- 17.2 Important OCFS2 parameters
- 18.1 GFS2 utilities
- 18.2 Important GFS2 parameters
- 5.1 Excerpt of Corosync configuration for a two-node cluster
- 5.2 Excerpt of Corosync configuration for an n-node cluster
- 5.3 Resource group for a web server
- 5.4 A resource set for location constraints
- 5.5 A chain of colocated resources
- 5.6 A chain of ordered resources
- 5.7 A chain of ordered resources expressed as resource set
- 5.8 Migration threshold—process flow
- 5.9 Example configuration for load-balanced placing
- 5.10 Configuring resources for monitoring plug-ins
- 7.1 A simple crmsh shell script
- 9.1 Configuration of an IBM RSA lights-out device
- 9.2 Configuration of a UPS fencing device
- 9.3 Configuration of a Kdump device
- 10.1 Formula for timeout calculation
- 11.1 Status of QDevice
- 11.2 Status of QNetd server
- 12.1 Excerpt of a cluster configuration in XML
- 14.1 Simple ldirectord configuration
- 19.1 Configuration of a three-node stacked DRBD resource
- 19.2 Configuration of DRBD with resource-level fencing using the Cluster Information Base (CIB)
- 23.1 Using an NFS server to store the file backup
- 23.2 Using third-party backup tools like EMC NetWorker
- A.1 Stopped resources
Copyright © 2006–2022 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see http://www.suse.com/company/legal/. All third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.