High Availability Policies Guide

Transcription

1 Tioli System Automation for Multiplatforms High Aailability Policies Guide Version 4 Release 1 SC

2

3 Tioli System Automation for Multiplatforms High Aailability Policies Guide Version 4 Release 1 SC

4 Note! Before using this information and the product it supports, read the information in Notices on page 167. Before using this information and the product it supports, read the information in Notices on page 167. This edition of System Automation for Multiplatforms High Aailability Policies Guide applies to Version 4, Release 1, Modification 0 of IBM Tioli System Automation for Multiplatforms, program number 5724 M00, and to all subsequent releases and modifications of this product until otherwise indicated in new editions. This edition replaces SC IBM welcomes your comments. A form for readers' comments may be proided at the back of this publication, or you may address your comments to the following address: IBM Deutschland Research and Deelopment GmbH Department 3282 Schoenaicher Str. 220 D Boeblingen Federal Republic of Germany FAX (Germany): FAX (Other Countries): (+49) Internet eserdoc@de.ibm.com If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: Title and order number of this book Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. Copyright IBM Corporation 2014, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii About this guide ix Who should use this guide ix Where to find more information ix Conentions x ISO x Related RSCT information x How to obtain publications xi How to reach us by xi What's new in this release xiii Chapter 1. SAP Central Serices high aailability policy Planning Single Point of Failure (SPOF) Example of a two-node setup SAP Central Serices high aailability setup options Location of SAP instance directories Database high aailability installation setup.. 10 NFS high-aailability installation setup High aailability impact Installing and setting up Installing a new ASCS, SCS, or Double Stack high aailability SAP system Installing and setting up System Automation for Multiplatforms Installing and setting up the SAP high aailability policy feature Migrating the SAP Central Serices high aailability solution from SA MP V3.2 to V Configuring and actiating SAP Central Serices high aailability policy.. 30 Using the wizard to configure and actiate the SAP Central Serices high aailability policy.. 42 SAP Central Serices high aailability policy parameters Verifying Starting and stopping the SAP Central Serices high aailability solution Failoer scenarios SAP Central Serices high aailability solution checklist Chapter 2. SAP HANA System Replication high aailability policy Planning Single Point of Failure (SPOF) Example of a two-node setup SAP HANA high aailability setup options Database high aailability installation setup.. 87 NFS high aailability installation setup High aailability impact SAP HANA documentation references Installing and setting up Installing a new HANA database high aailability SAP system Installing and setting up System Automation for Multiplatforms Installing and setting up the SAP high aailability policy feature Installing a new ASCS, SCS, or Double Stack high aailability SAP system Configuring and actiating SAP HANA System Replication automation.. 90 Using the wizard to configure and actiate the SAP HANA high aailability policy SAP HANA high aailability policy parameters 94 Verifying Starting and stopping the SAP HANA high aailability solution Testing SAP HANA System Replication failoer scenarios Chapter 3. NFS high aailability policy 101 Planning the NFS serer automation Installing and setting up the NFS serer for automation Configuring the NFS serer components NFS serer processes Using a shared disk for configuration data Using a shared disk for exported data Configuring file systems within the same olume group on AIX NFS serer irtual IP address Configuring and actiating the NFS serer high aailability policy NFS serer high aailability policy NFS serer policy parameters Using the wizard to configure and actiate the NFS serer high aailability policy Verifying the NFS serer high aailability policy 125 Chapter 4. Oracle high aailability policy Planning the Oracle database automation and high aailability Installing and setting up the Oracle database Installing the Oracle database software Configuring the indiidual Oracle database components Configuring and actiating the Oracle database high aailability policy Oracle database high aailability policy Copyright IBM Corp. 2014, 2016 iii

6 Oracle policy high aailability and automation preparation Oracle database high aailability policy parameters Using the wizard to configure and actiate the Oracle database high aailability policy Verifying the Oracle database high aailability policy Chapter 5. Using the wizard to configure and actiate the policy Starting the Policy Setup Wizard Migrating between an old and a new template Oeriew dialog Dialog elements Skipped parameters Parameter dialog Dialog elements Entering alues Single alue Multiple alues Value selection Decision Option parameters Wizard dialog flow Parameter help information Enable and disable help information for all parameter dialogs Display help information in selected parameter dialogs Closing the wizard Actiating the policy Chapter 6. Troubleshooting the SAP high aailability solution No alid license aailable when actiating SAP Central Serices high aailability policy Chapter 7. Troubleshooting the Oracle high aailability policy Oracle database listener does not start up Problem Explanation Solution Oracle database process is monitored unknown 161 Explanation Solution Chapter 8. Troubleshooting the NFS tiebreaker NFS tiebreaker on Linux NFS tiebreaker on AIX Using IBM Support Assistant Installing IBM Support Assistant and the Tioli System Automation for Multiplatforms plug-in Notices Trademarks Index i Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

7 Figures 1. Symbols used in this guide x 2. Components of a distributed SAP system 2 3. Example of a two-node setup ABAP (ASCS) high aailability setup Jaa (SCS) high aailability setup Double Stack high aailability setup Initial startup of (A)SCS Failure of (A)SCS and recoery of the enqueue table Moement of the Enqueue Replication Serer ASCS high aailability policy SCS high aailability policy for Jaa Resources of the Double Stack (ABAP and Jaa SCS) high aailability policy Relationships between the Enqueue and Message Serers and the Enqueue Replication Serer Example of a two-node setup System Replication oeriew with single nodes Resources of the SAP HANA high aailability policy NFS serer parts Components to be configured when automating an NFS serer NFS serer high aailability policy NFS serer high aailability policy sample scenario High aailability architecture for an Oracle database Oracle database high aailability policy Oeriew dialog Parameter dialog #3 without alue definition Parameter dialog #3 with alue definition Single alue prompt Multiple alues prompt Value selection mode Decision prompt Option parameter in oeriew dialog Option parameter dialog Nested parameter dialog Wizard dialog flow Help information in parameter dialogs Policy actiation in the wizard Copyright IBM Corp. 2014, 2016

8 i Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

9 Tables 1. Highlighting conentions used in this book x 2. ABAP resources and the corresponding components Jaa resources and the corresponding components Double-Stack resources and the corresponding components Fully implemented high aailability solution for SAP Start_Program_<NR> and Restart_Program_<NR> alues of SAP profiles Resources and resource groups of the ASCS high aailability policy Description and examples of placeholders for ABAP resource names Resources and resource groups of the Jaa SCS high aailability policy Description and examples of placeholders for JAVA resource names Location for the SAP high aailability XML template files ABAP policy parameters Jaa policy parameters Double-Stack resources and the corresponding components Planned Outages Unplanned outages SAP high aailability solution checklist Documentation reference SAP HANA System Replication parts to automate Location for the SAP HANA high aailability XML template file SAP HANA System Replication HA policy parameters Planned Outages Unplanned outages NFS serer parts which are automated by the NFS serer high aailability policy NFS serer high aailability policy relationships NFS serer high aailability policy parameters (AIX) NFS serer high aailability policy parameters (Linux) Oracle database high aailability resources Oracle database high aailability policy relationships Oracle database high aailability policy parameters Help information text of the Setup Policy Wizard Copyright IBM Corp. 2014, 2016 ii

10 iii Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

11 About this guide Who should use this guide This guide explains how to implement and use the policy-based automated recoery capabilities that are proided by IBM Tioli System Automation for Multiplatforms (System Automation for Multiplatforms). System Automation for Multiplatforms proides high-aailability for resources on AIX clusters (on IBM System p ), Linux clusters (on IBM System x, System z, System i, and System p), and Windows clusters (on IBM System x). This guide is intended for system administrators and operators who want to use the automation and failoer capabilities of System Automation for Multiplatforms. Where to find more information The Tioli System Automation library comprises the following books, including this publication, describing Tioli System Automation for Multiplatforms: System Automation for Multiplatforms Administrator's and User's Guide, SC Tioli System Automation for Multiplatforms Installation and Configuration Guide, SC Tioli System Automation for Multiplatforms Reference Guide, SC Tioli System Automation for Multiplatforms High Aailability Policies Guide, SC You can download the complete documentation at The Tioli System Automation library contains the following books, including this one, describing System Automation Application Manager: System Automation Application Manager Administrator's and User's Guide, SC System Automation Application Manager Installation and Configuration Guide, SC System Automation Application Manager Reference and Problem Determination Guide, SC You can download the books at: The IBM Tioli System Automation home page contains useful up-to-date information, including support links and downloads for maintenance packages. You will find the IBM Tioli System Automation home page at: Copyright IBM Corp. 2014, 2016 ix

12 Conentions The following highlighting conentions are used in this book: Table 1. Highlighting conentions used in this book Bold Italic monospace Identifies commands, subroutines, keywords, files, structures, directories, and other items whose names are predefined by the system. Also identifies graphical objects such as buttons, labels, and icons that the user selects. Identifies parameters whose actual names or alues are to be supplied by the user. Identifies examples of specific data alues, examples of text similar to what you might see displayed, examples of portions of program code similar to what you might write as a programmer, messages from the system, or information you should actually type. This manual uses symbols to show resources, resource groups, equialencies, and relationships. The symbols used are as follows: Figure 1. Symbols used in this guide ISO 9000 Related RSCT information ISO 9000 registered quality systems were used in the deelopment and manufacturing of this product. The following IBM Reliable Scalable Cluster Technology (RSCT) publications are aailable on the System Automation for Multiplatforms CD: RSCT Administration Guide RSCT for AIX 5L : Technical Reference RSCT for Multiplatforms: Technical Reference RSCT Messages RSCT Diagnosis Guide For more information about RSCT, see IBM Cluster systems. For more information, see the Linux on IBM zseries and S/390 : High Aailability for z/vm and Linux IBM Redpaper. x Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

13 How to obtain publications How to reach us by The System Automation for Multiplatforms publications are also aailable (alid at the time of release) at these Web sites: If you would like to contact us by , send your comments to About this guide xi

14 xii Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

15 What's new in this release Get a quick oeriew about the new features of System Automation for Multiplatforms ersion Improed operations on the command line with new samcc command System Automation for Multiplatforms ersion adds a new command samcc, which can be used as operations console on the command line interface. For more information, see. Additional platforms support System Automation for Multiplatforms ersion supports the following new platforms: SUSE SLES 12 (64-bit) Red Hat RHEL 7 (64-bit) Ubuntu (64-bit): System x, Power Systems (Little Endian only) System Automation for Multiplatforms ersion supports the following new platforms: Red Hat RHEL 7.1 on Power Systems Little Endian (64-bit) System Automation for Multiplatforms ersion supports the following new platforms: AIX 7.2 For more information, see System Automation for Multiplatforms Installation and Configuration Guide. Improed high aailability policy for SAP The SAP Central Serices high aailability policy is aailable as System Automation for Multiplatforms optional feature, which is priced separately. This SAP Central Serices high aailability policy is now adapted to SAP Netweaer technology. The user can start and stop the SAP Netweaer stack by using the SAP user interface without interfering with the System Automation policy. The SAP Software Update Manager is able to update the Netweaer solution without the need to disable System Automation during the update process. Supported SAP configuration options: Jaa, ABAP, and DUAL stack support for SAP Central Serices failoer. Additionally, the following configuration options are supported: Application serer (restart in place of primary and additional application serer) SAP router failoer SAP Web Dispatcher failoer Start after dependency support to database System Automation for Multiplatforms ersion adds support for: SAP HANA System Replication failoer The supported SAP kernel ersion is 7.20 or higher. For more information, see System Automation for Multiplatforms High Aailability Policies Guide. Copyright IBM Corp. 2014, 2016 xiii

16 Gathering information about application failures The samwhy program is a simple and easy-to-use tool that offers the detection of application failures and their analysis for applications that are controlled by System Automation. samwhy helps the operator to understand what happened and proides an explanation why System Automation reacted the way it did. For more information, see System Automation for Multiplatforms Reference Guide. High aailability of the end-to-end automation adapter is simplified An extra automation policy or irtual IP address is not required any more. For more information, see System Automation for Multiplatforms Installation and Configuration Guide. Run the end-to-end automation adapter with a non-root user By default, the end-to-end automation adapter runs with a root user. Now the adapter can also be set up to run with a non-root user. For more information, see System Automation for Multiplatforms Installation and Configuration Guide. xi Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

17 Chapter 1. SAP Central Serices high aailability policy You can define SAP Central Serices high aailability policies for your SAP installation. The topics in this section describe the process. Planning This topic explains the high aailability concepts for a SAP system. It proides information about which SAP Central Serices high aailability policy to choose depending on the planned SAP installation. The main reason for this high aailability setup is to reduce the downtime of an SAP system in case of software or hardware failures. The high aailability solution for SAP uses System Automation for Multiplatforms to automate all SAP components. System Automation for Multiplatforms detects failed components and restarts or initiates a failoer. This setup will also help to reduce the operational complexity of an SAP enironment and to aoid operator errors resulting from this complexity. Single Point of Failure (SPOF) In a distributed or standard SAP installation the SAP Central Serices, the database serer, and the NFS serer are single points of failures (SPOFs). To minimize the impact of SPOF serices outages, it is necessary to setup redundancy. Run one or more standby serers to which each of the SPOF serices can be failed oer and restarted independently. Each SPOF serice must be associated with its own irtual host name, which is started where the serice runs. Clients reconnect to the same host name independently of where the SPOF serice runs. The following SAP components are aailable for a distributed SAP system. Copyright IBM Corp. 2014,

18 Figure 2. Components of a distributed SAP system (A)SCS node The (A)SCS node consists of the stand-alone components Enqueue Serer (ES) and Message Serer (MS) that operate as SAP Central Serices instance. Depending on the SAP solution the (A)SCS node contains the ABAP, Jaa, or both components. An SAP Instance Agent is running for each instance. SAP uses the following terms and abbreiations: ASCS SAP Central Serices for ABAP instances. SCS SAP Central Serices for Jaa instances. (A)SCS SAP Central Serices for ABAP or Jaa instances. Primary AS node The Primary AS node consists of the Primary Application Serer (PAS) instance that is running the SAP Serices Dialog, Update, Batch, Gateway, and Spool. An Instance Agent accompanies the Primary Application Serer. Note: In a standard non-distributed SAP system all the main instances (SCS, PAS, and database) run on the same node. Additional Application Serer node Additional AS nodes are optional. They host the Additional Application Serer (AAS) instances, which were called Dialog Instance (DI) in releases prior then SAP kernel 7.1. You can hae one or more Additional Application Serers. Again an Instance Agent accompanies each Additional Application Serer. 2 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

19 Web Dispatcher and SAProuter node The optional Web Dispatcher and SAProuter nodes run the SAP Web Dispatcher (WD) and SAProuter, which are used as proxies to access the other SAP instances. An Instance Agent is running for the Web Dispatcher. Host Agents One SAP Host Agent runs on each node that hosts SAP-proided components. Database node The database node holds the database instance. The database product can be IBM DB2 or another SAP supported database. NFS node The NFS node runs the NFS serer. It can also be a NAS deice, which exports the NFS file systems. SAP clients The SAP clients connect directly to the Application Serers or to an optional Web Dispatcher. For more information about the SAP components, see High aailability impact on page 12. Example of a two-node setup The minimum hardware setup consists of a two-node System Automation for Multiplatforms domain. The two nodes are either two physical machines or two LPARs running on different physical machines. The systems must be connected ia network and need to access the database and SAP data. Data can be proided by a SAN attached disk subsystem, which is connected to each node using fiber channel (FC). Figure 3 on page 4 shows an example of a two-node System Automation for Multiplatforms domain. It shows all the main SAP instances and the corresponding failoer groups of a SAP ABAP system. Chapter 1. SAP Central Serices high aailability policy 3

20 Figure 3. Example of a two-node setup Each machine or LPAR must be capable to run all instances. These are the main SAP instances, which must be made highly aailable by System Automation for Multiplatforms. High aailability for application serers is achieed by haing at least two application serer instances (PAS and AAS) as fixed resources. If your setup contains the database serer and SAProuter or SAP Web Dispatcher, make them highly aailable as well. 4 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

21 SAP Central Serices high aailability setup options System Automation for Multiplatforms supports three different SAP Central Serices high aailability installation setups: ABAP (ASCS) high aailability installation Jaa (SCS) high aailability installation Double-stack (ASCS and SCS) high aailability installation Select the high aailability installation that matches your SAP installation. Note: To transform your existing SAP into a highly aailable SAP, keep your existing SAP up and running until the newly installed SAP Central Serices high aailability setup is tested. ABAP (ASCS) high aailability setup This ABAP (ASCS) high aailability setup is used for ABAP only SAP solutions. Figure 4. ABAP (ASCS) high aailability setup ABAP (ASCS) high aailability setup The ASCS high aailability setup consists of at least two SCS nodes which run the ASCS and ERS instances. Under regular conditions the ERS will always be started on the node where the ASCS is not running. This failoer setup has no downtime due to fast failure detection and in-memory data exchange between ES and ERS in case the ASCS must be Chapter 1. SAP Central Serices high aailability policy 5

22 moed to the failoer node. During the failoer, the irtual IP address for the ASCS is moed to the failoer node too, so its addressing remains unchanged. Primary and Additional AS node The Primary AS node and the Additional AS nodes consist of ABAP Application Serers which will be restarted in place in case of software failures. Protection against hardware outages is done by setting up multiple Application Serers on different hardware. Therefore the System Automation for Multiplatforms concept for SAP high aailability does not consider failoers of Application Serers to other nodes because Application Serer restarts take a lot of time. Other Application Serers must be sized to take the additional workload from failing serers. Web Dispatcher and SAProuter node (optional) The Web Dispatcher and SAP router high aailability setups consists of at least two nodes which run the instances in a failoer setup. The components are key for the clients to access the Application Serers, so in case of a failure the instance failoer to standby nodes includes their irtual IP addresses too. Database high aailability setup The database high aailability setup is explained in Database high aailability installation setup on page 10. NFS high aailability setup The NFS high aailability setup is explained in NFS high-aailability installation setup on page 11. Setup a ASCS SAP high aailability solution with the following components. Table 2. ABAP resources and the corresponding components ABAP Resources SAP component ABAP resources ABAP SAP Central Serices (ASCS) instances using an own irtual host name on two nodes. Enqueue Replication Serer using an own irtual host name on two nodes. Database Serer instances using an own irtual host name on two nodes. Primary Application Serer for ABAP instance on first node. Additional Application Serer for ABAP instances on other nodes. ABAP independent resources (optional) Host Agent Web Dispatcher instances using an own irtual host name on two nodes. SAProuter setup on two nodes. Jaa (SCS) high aailability setup This Jaa (SCS) high aailability setup is used for Jaa only SAP solutions. 6 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

23 Figure 5. Jaa (SCS) high aailability setup Jaa (SCS) high aailability setup The Jaa (SCS) high aailability setup consists of at least two SCS nodes, which run the SCS and ERS instances. Under regular conditions, the ERS is always started on the node where the SCS is not running. This failoer setup has no downtime due to fast failure detection and in-memory data exchange between ES and ERS in case the SCS must be moed to the failoer node. During the failoer, the irtual IP address for the SCS is moed to the failoer node too, so its addressing remains unchanged. Primary and Additional AS node The Primary AS node and the Additional AS nodes consist of Jaa Application Serers, which are restarted in place in case of software failures. Protection against hardware failures is done by setting up multiple Application Serers on different hardware. Therefore, the System Automation for Multiplatforms concept for SAP high aailability does not consider failoers of Application Serers to other nodes because Application Serer restarts take a lot of time. Other Application Serers must be sized to take the additional workload from failing serers. Web Dispatcher and SAProuter node (optional) The Web Dispatcher and SAP router high aailability setups consists of at least two nodes, which run the instances in a failoer setup. The components are key for the clients to access the Application Serers, so in case of a failure the instance failoer to standby nodes includes their irtual IP addresses too. Chapter 1. SAP Central Serices high aailability policy 7

24 Database high aailability setup The database high aailability setup is explained in Database high aailability installation setup on page 10. NFS high aailability setup The NFS high aailability setup is explained in NFS high-aailability installation setup on page 11. Set up a Jaa SCS SAP high aailability solution with the following components. Table 3. Jaa resources and the corresponding components Jaa Resources SAP component Jaa resources Jaa SAP Central Serices (SCS) instances, which use an own irtual host name on two nodes. Enqueue Replication Serer, which uses an own irtual host name on two nodes. Database serer instances, which uses an own irtual host name on two nodes. Primary Application Serer for Jaa instance on first node. Additional application serer for Jaa instances on other nodes. Jaa independent resources (optional) Host Agent Web Dispatcher instances, which use an own irtual host name on two nodes. SAProuter setup on two nodes. Double-Stack (ASCS and SCS) high aailability setup This Double-Stack high aailability setup is used for Double-Stack SAP solutions. Figure 6. Double Stack high aailability setup 8 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

25 (A)SCS high aailability setup The Double-Stack installation contains all the components of both the ABAP and Jaa installation. A Double-Stack system has two SAP Central Serices instances in parallel: an ABAP SCS and a Jaa SCS. Each of them works the same way as the ABAP only and Jaa only setups. During the failoer, the corresponding two irtual IP addresses for the ASCS and SCS are moed to the failoer node as well. Primary and Additional AS node A Double-Stack Application Serer comprises one SAP instance that runs an ABAP and a Jaa Application Serer in parallel. Within a System Automation for Multiplatforms domain, the Double Stack Application Serer instance is automated as two Application Serer resources. The StartAfter relationship is defined between the Jaa Application Serer and the ABAP Application Serer. This StartAfter relationship causes that starting the Jaa Application Serer automatically triggers the prior start of the ABAP Application Serer. Web Dispatcher and SAProuter node (optional) The Web Dispatcher and SAP router high aailability setups consist of at least two nodes, which run the Web Dispatcher and SAP Router instances in a failoer setup. Both components are essential for the clients to access the Application Serers. Therefore, the failoer of one instance to standby nodes includes the corresponding irtual IP address as well. Database high aailability setup The database high aailability setup is explained in Database high aailability installation setup on page 10. NFS high aailability setup The NFS high aailability setup is explained in NFS high-aailability installation setup on page 11. Table 4. Double-Stack resources and the corresponding components Double Stack resources ABAP resource Jaa resources SAP component ABAP SAP Central Serices (ASCS) instances use an own irtual host name on two nodes. Jaa SAP Central Serices (SCS) instances use an own irtual host name on two nodes. ABAP and Jaa common resources Independent resources (optional) Both Enqueue Replication Serers hae their own irtual host name on two nodes. Database serer instances use an own irtual host name on two nodes. Primary Application Serer for ABAP and Jaa instance on first node. Additional Application Serer for ABAP and Jaa instances on other nodes. Host Agent Web Dispatcher instances use an own irtual host name on two nodes. SAProuter setup on two nodes. Chapter 1. SAP Central Serices high aailability policy 9

26 Location of SAP instance directories The SAP instance directories /usr/sap/<sapsid>/<instancename> must be located on a local file system. NFS or other distributed file systems are not allowed or accepted. Database high aailability installation setup You can choose between a database installation within the same System Automation for Multiplatforms cluster together with the SAP installation or a database installation on a separate cluster of its own. SAP Central Serices and database in the same high aailability cluster If you choose to install the database on the same System Automation for Multiplatforms cluster as SAP, you can run them on the same or on different systems. (A)SCS and database running on the same nodes (2 or 3 nodes): Use this setup only if your workload is small enough, so that the database and the SAP Enqueue Serer can run on one system and the SAP Primary Application Serer on the other system. (A)SCS and database running on different nodes in same cluster (4 or more nodes): Use this setup to separate the workload of the SAP installation and the database serer to different systems. Additional nodes can be joined into this cluster to host Additional Application Serers within this high aailability setup. When using the policy wizard to define your SAP high aailability policy, it is recommended to select a "StartAfter" relationship between the SAP Application Serers and the database serer. This relationship will let the database serer start before the SAP Application Serers are started. This helps to aoid the problem of haing an Application Serer started without a database running, which would require a restart of the Application Serer. SAP Central Serices and database on different high aailability clusters You can hae the SAP installation and the database in different System Automation for Multiplatforms high aailability clusters. Adantages: 1. The setup and maintenance of the database high aailability cluster is independent from the SAP high aailability cluster. 2. Separate non-root user authorizations for cluster commands against DB2 and SAP resources can be better applied when using separate System Automation for Multiplatforms clusters. Note: In case you hae a DB2 database you can use the SAP installer to install DB2 and System Automation for Multiplatforms together on the database nodes. For more information, refer to High aailability for DB2 and other databases on page 11. As a drawback, although there are functional dependencies between SAP and its database, they cannot be mapped to high aailability relationships across two clusters with System Automation for Multiplatforms. Such cross-cluster 10 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

27 relationships can be implemented with the System Automation Application Manager product. High aailability for DB2 and other databases You can either use DB2 for your high aailability setup or use other databases. DB2 high aailability setup In a high aailability enironment a DB2 high aailability setup is required. You can use the System Automation for Multiplatforms software which is bundled with DB2. Note: If the DB2 database runs in the same cluster together with the SAP software, the DB2-bundled System Automation for Multiplatforms license cannot be used, because it allows the automation of DB2 only. So you must ensure that you hae a full System Automation for Multiplatforms license for each cluster node. Use the DB2 high aailability setup wizard which is shipped with the SAP product. You can find the DB2 high aailability setup installation information in the following chapter of the SAP Installation & Upgrade Guide. An SAP user ID and password are required to access the SAP documentation. SAP NetWeaer SAP NetWeaer 7.0 (2004s) Installation (2 -Installation -SAP NetWeaer Systems) SAP NetWeaer PI 7.1 Installation (2 -Installation -SAP NetWeaer Systems) System Automation for Multiplatforms-DB2 for LUW SAP NetWeaer 7.3 Installation (2 -Installation -SAP NetWeaer Systems) System Automation for Multiplatforms-DB2 for LUW SAP NetWeaer 7.4 Installation (2 -Installation -SAP NetWeaer Systems) System Automation for Multiplatforms-DB2 for LUW Further links: How to setup and run a DB2 LUW database serer or client see SAP Note No : DB6: Installation SA MP For more information about high aailability with SAP on DB2, refer to IBM DB2 for LUW Cluster Using IBM Tioli SA MP SAP Community Network link: High Aailability with SAP on DB2: IBM DB2 for LUW Cluster Using IBM Tioli SAMP High aailability with other databases System Automation for Multiplatforms can be used to automate the start, stop, monitor, restart and failoer of database serers other than DB2. Chapter 2, SAP HANA System Replication high aailability policy, on page 85 Chapter 4, Oracle high aailability policy, on page 127 NFS high-aailability installation setup Two central NFS shares are essential for an SAP system: Chapter 1. SAP Central Serices high aailability policy 11

28 /sapmnt/<sid>: Required to share binary files and configuration data for the application serers. /usr/sap/trans: Must be shared in a logical transport landscape so that the source SAP system can write the transport files to the share and the target systems can pick them up from this location. You hae the following three options for an NFS high aailability setup: 1. Use System Automation for Multiplatforms for the NFS high-aailability cluster. 2. Use an existing NFS high-aailability cluster. 3. Use a Network Attached Storage (NAS) deice with integrated high aailability capabilities. It is preferred to install the NFS serer HA setup outside of the SAP HA cluster to reduce the complexity and preent setup problems. Starting with ersion you can run the NFS serer on the same cluster nodes as the SAP HA solution if the following conditions apply: If the NFS serer is installed with an HA setup, it is required to use the NFS HA policy which is bundled with System Automation for Multiplatforms. Configure the SAPCPE tool to copy all binary files required for local SAP instance monitoring (sapcontrol / sapstartsr) to the local SAP instance directories. For more information, see SAP documentation. The SAP setup and NFS setup must pass a manual failoer test without System Automation for Multiplatforms policy being actiated. This manual failoer test includes: Fail oer all SAP Central Serices resources without NFS serer failoer. For more information, see Verifying the initial installation on page 21. Fail oer all NFS serer resources without SAP Central Serices failoer: shared disk, IP address, and all NFS serer processes. Use the SAP GUI to check whether the Central Serices are working correct before and after the manual failoer. The start of SAP by System Automation for Multiplatforms is not successful if the NFS serer is not up and running. In case the NFS serer runs in a separate high-aailability cluster, it is not possible to define a StartAfter relationship across two clusters with System Automation for Multiplatforms. Such a cross-cluster relationship can be implemented with the System Automation Application Manager. Make sure to configure all nodes in the SAP high aailability solution cluster as NFS clients. Use the automounter to configure the NFS clients. The SAP Central Serices high aailability policy does not keep the NFS mount points high aailable, therefore it is required to use the automounter for keeping the NFS mount points high aailable. An NFS high aailability policy is part of the SAP high aailability solution that is proided by System Automation for Multiplatforms. For more information, see Chapter 3, NFS high aailability policy, on page 101. High aailability impact This topic discusses the impact of arious failure scenarios of the SAP system components when using System Automation for Multiplatforms to automate 12 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

29 recoery. Manual recoery actions are minimized which otherwise would cause SAP transactions to timeout and roll back. Note: There is no single point of failure anymore if System Automation for Multiplatforms is used for automation. The impact of a failure has a local scope; it is limited to the transactions currently using the failing resource. The SAP system remains aailable. Without System Automation the impact on the SAP system would be much worse from what is shown in the Impact column in the table below. Without System Automation all recoery actions would hae to be done manually. Manual recoery actions usually take longer and are error prone under the pressure of a system outage. In Table 5 the following abbreiations are used: SA: actions taken automatically and instantaneously by IBM Tioli System Automation for Multiplatforms User: actions taken by the user Table 5. Fully implemented high aailability solution for SAP Failing resource Impact Actions Database Rollback of transactions SA: Restart or Failoer Database Remote application serers fail (Optional setup in same high oer automatically to the other aailability cluster) database node User: Restart transactions Enqueue Serer No impact. SA: Failoer Enqueue Serer Enqueue Replication Serer Refer to Enqueue Serer and Enqueue Replication Serer on page 14. No impact. Refer to Enqueue Serer and Enqueue Replication Serer on page 14. Remote application serers automatically reconnect to the other database node. SA: Restart Enqueue Replication Serer Message Serer No impact on most transactions Application Serer instance Certain transactions inhibited (for example, SM66) Update/batch workload balancing inhibited Group logon inhibited Transactions on this instance are lost Rollback of database updates User sessions on this instance are lost SA: Restart Message Serer SA: failoer optional SAP restart feature enabled. User: Connect to another Application Serer instance User: Restart transactions SA: Restart Application Serer instance Chapter 1. SAP Central Serices high aailability policy 13

30 Table 5. Fully implemented high aailability solution for SAP (continued) Failing resource Impact Actions SAP-Gateway (ABAP only) No impact on most transactions Connections to registered serers inhibited until they hae reconnected to the SAP-Gateway Web Dispatcher User sessions (ia HTTP) lost Re-connection inhibited SA: Restart SAP-Gateway SA: Restart or Failoer Web Dispatcher User: Reconnect SAProuter User sessions (ia SAProuter) lost Re-connection inhibited NFS serer, NAS deice Refer to NFS serer on page 17. If data was written to file, last written data is in doubt SA: Restart or Failoer SAProuter User: Reconnect SA: Restart or Failoer NFS serer Enqueue Serer and Enqueue Replication Serer The aailability of the Enqueue Serer is key for a SAP system. If the Enqueue Serer cannot be reached, the SAP system is not operational since most transactions fail to run. The Enqueue Serer is a standalone component and does not require access to the database. An application serer instance connects directly to the Enqueue Serer by using a irtual host name. When connected, the Enqueue Serer on system 1 transmits replication data to the Enqueue Replication Serer on system 2 which stores the data in a shadow enqueue table residing in shared memory. In case the Enqueue Serer fails, the shadow enqueue table on the Enqueue Replication Serer is used to rebuild the tables and data structures for the recoered Enqueue Serer that is started on the same node. The Enqueue Replication Serer stops after transferring the data to the recoered Enqueue Serer. If the Enqueue Replication Serer is unaailable, the SAP system continues to be up and running, but no shadow enqueue table is maintained as a backup. The Enqueue Replication Serer runs on a different system than the Enqueue Serer to keep the enqueue table and its shadow backup apart. The multithreaded architecture of the standalone Enqueue Serer allows parallel processing and replication. The I/O processing for the TCP/IP communication is distributed oer seeral I/O threads which allows a ery high throughput. The following figure shows the principal TCP/IP communication paths between the Application Serer instances, the Enqueue Serer, and Message Serers. 14 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

31 Figure 7. Initial startup of (A)SCS If system 1 fails, system 2 takes oer the role of the first one as shown in Figure 8 on page 16: 1. The irtual IP address related to the Enqueue and Message Serers is taken oer to system Enqueue and Message Serers are restarted on system The enqueue table is rebuilt from the shadow table hosted by the Enqueue Replication Serer. 4. The Enqueue Replication Serer stops after the Enqueue Serer has rebuild the enqueue table. 5. The Application Serers reconnect to the Enqueue Serer and the Message Serer. System Automation for Multiplatforms will handle this complete failoer process. The failoer is fully transparent to the application. Enqueue locks are presered and transactions continue to run. Chapter 1. SAP Central Serices high aailability policy 15

32 Figure 8. Failure of (A)SCS and recoery of the enqueue table After a successful failoer of the Enqueue Serer, the Enqueue Replication Serer is no longer needed on system 2 and therefore stops itself. If another system is aailable, the Enqueue Replication Serer is started by System Automation for Multiplatforms on that system and a new shadow enqueue table is established. This is shown in Figure 9 Figure 9. Moement of the Enqueue Replication Serer Database host If the database serer is not aailable, the entire SAP system becomes unaailable. The database host maintains the persistent storage for the entire SAP system. Once the database is aailable again, all uncommitted transactions are rolled back and the SAP system continues to run. 16 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

33 Installing and setting up System Automation for Multiplatforms can be used to automate the start, stop, monitor, restart, and failoer of the database serer. For more information, refer to High aailability for DB2 and other databases on page 11. NFS serer A SAP high aailability setup requires shared access for directories like global, profile, and trans. On UNIX and Linux systems you need NFS to share files. As a result, the aailability of the file systems together with the NFS serer is critical. Note: NFS file access is not transactional. There is no commit or rollback logic. In case of system failure or communication loss there is no guarantee that the last written data has been stored on disk. System Automation for Multiplatforms can be used to automate the start, stop, monitor, restart and failoer of the NFS serer. For more information, refer to NFS high-aailability installation setup on page 11. SAP Host Agent The SAP Host Agent is a tool that you can use for monitoring and controlling SAP and non-sap instances, operating systems, and databases. It is installed automatically during the installation of new SAP instances with SAP kernel 7.20 or higher. The SAP Host Agent proides features for SAP instance discoery and inentory, instance control, database monitoring and management, and operating system monitoring using saposcol. It aids in system or instance proisioning by hosting the infrastructure of SAP NetWeaer Landscape Virtualization Management (LVM). SAP Web Dispatcher The Web Dispatcher is the entry point for all external HTTP requests and the interface between all HTTP clients and the SAP system. The Web Dispatcher can work as load balancer for incoming requests which are distributed among all aailable application serers. When the SAP Web Dispatcher fails, clients cannot connect to the SAP subsystems using HTTP request. SAProuter The SAProuter controls the access between the external network and the SAP subsystem. In case of a failure of the SAProuter, no connections can be processed using this proxy. Before you set up your SAP enironment for high aailability, you must plan for the installation option which best suits your system. The following three installation options apply if you want to setup a SAP high aailability solution: Chapter 1. SAP Central Serices high aailability policy 17

34 Installing a new high aailability SAP system Install a new system using the sapinst installation option High-Aailability System. This option is described in detail in the following topic: Installing a new ASCS, SCS, or Double Stack high aailability SAP system. Exporting an existing non-high aailability SAP system Export an existing non-high aailability SAP system and import it into a new high aailability SAP system using the system copy feature of sapinst. See the SAP documentation for assistance. Post-installation tasks Setup your NFS high aailability serer. For more information, see NFS high-aailability installation setup on page 11. You can also perform this task before you start the SAP installation. Setup your database high aailability serer. For more information, see Database high aailability installation setup on page 10. Installing a new ASCS, SCS, or Double Stack high aailability SAP system This topic describes a new installation of an ASCS, SCS, or Double Stack high aailability SAP system. SAP NetWeaer 7.0 or higher with a kernel ersion of at least 7.20 is required. This description is based on a two node cluster architecture with a primary and a failoer node. For more information about the ASCS, SCS, or Double Stack high aailability SAP system setups, refer to SAP Central Serices high aailability setup options on page 5. Prerequisites Follow the prerequisites before you start the installation of the ASCS, SCS, or Double Stack high aailability SAP system. Before you begin, make sure that you follow the guidelines: 1. Use unique instance numbers for eery instance you install on a single host for one SAPSID. The SAP installation does not work if you did not use unique instance numbers. 2. The installation tasks for the primary and failoer node contain ASCS and SCS installation tasks. Depending on your application stack (ABAP only, Jaa only) you might skip the ASCS or SCS installation tasks. For a Double Stack system, install ASCS and SCS. 3. The SAP product documentation installation guide documents to install the switchoer software after you installed the Central Serices Instance. If you use System Automation for Multiplatforms, skip this step until you installed and erified the complete SAP system. 4. For more information, see SAP Note Installing Systems based on NetWeaer ersion 7.3 and higher: UNIX. Prerequisite installation tasks: 18 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

35 Note: The SAP installation tool sapinst is also called Software Proisioning Manager in the SAP documentation. Create a separate directory for eery installation task to store installation logs and traces. Switch into this directory before you start sapinst. Ensure to set the correct ulimits and umask alues for your enironment as it is documented in the SAP product installation guide. Ensure to configure the automounter on all nodes to connect to the NFS serer and automatically mount the default SAP directory /sapmnt before you start sapinst. For more information about NFS, see NFS high-aailability installation setup on page 11. Register permanent entries for the irtual host names in the DNS serer. Ensure that the network interfaces that you want to use hae the same name on each system. For each irtual IP address defined in the high aailability policy, an equialency of network interfaces is created. Only network interfaces with the same name on each node can be part of each equialency. Temporarily define and actiate all required irtual IP addresses on the physical host where you want to start the installation before you start sapinst. Be sure to remoe the irtual IP addresses after the installation is completed. Incorrect behaior of the SAP high aailability solution occurs if you leae the irtual IP addresses permanently defined. Initial installation on primary node Use the sapinst command to execute the following tasks for the installation option SAP Systems > High-Aailability System. For some installation tasks its required to start sapinst with a irtual host name. 1. Actiate all irtual IP addresses corresponding to the irtual host names before starting the installations. 2. Central Serices Instance for ABAP (ASCS) or Jaa (SCS): sapinst SAPINST_USE_HOSTNAME=<irtual (A)SCS host name> 3. Enqueue Replication Serer instances (ERS) for ASCS or SCS sapinst SAPINST_USE_HOSTNAME=<irtual ERS host name> 4. Database instance sapinst SAPINST_USE_HOSTNAME=<irtual DB host name> 5. Primary Application Serer instance sapinst 6. Web Dispatcher instance (optional) sapinst SAPINST_USE_HOSTNAME=<irtual Web Dispatcher host name> 7. Remoe all irtual IP addresses that hae been actiated before. Initial installation on failoer node To install SAP on the failoer node, perform the following steps: 1. Actiate all irtual IP addresses corresponding to the irtual host names before starting the installation. 2. Use the sapinst command to execute the following tasks with the installation option System Copy Target System - High-Aailability System. Central Serices Instance for ABAP (ASCS) or Jaa (SCS): sapinst SAPINST_USE_HOSTNAME=<irtual (A)SCS host name> Enqueue Replication Serer instances (ERS) for ASCS or SCS sapinst SAPINST_USE_HOSTNAME=<irtual ERS host name> Database instance Chapter 1. SAP Central Serices high aailability policy 19

36 sapinst SAPINST_USE_HOSTNAME=<irtual DB host name> 3. Use the sapinst command to execute the following installation tasks using the installation option SAP-System > High-Aailability System: Additional Application Serer instance (old name: Dialog Instance) sapinst Web Dispatcher instance (optional): Remoe the existing Web Dispatcher SAPSID directory on /sapmnt and install with the same SAPSID and instance ID on the second node again. sapinst SAPINST_USE_HOSTNAME=<irtual Web Dispatcher host name> 4. Remoe all irtual IP addresses that hae been actiated before. Configuring SAP profiles Configure the SAP profiles to comply with the high aailability solution proided by System Automation for Multiplatforms. Disable autostart of all SAP instances in all their profiles by commenting the line Autostart = 1. To share the enqueue backup file within the Linux or AIX cluster, store the file in the NFS-mounted /sapmnt/<sid>/global directory. Iit can be accessed from all nodes in the cluster where the Enqueue Serer can start. Add the following parameter to the (A)SCS profile for sharing the enqueue backup files between nodes: enque/backup_file = $(DIR_GLOBAL)/ENQBCK(A)SCS All SAP ABAP serices that run on the Primary Application Serer installation must also be manually configured in the instance profiles of the Additional Application Serer. SAP ABAP serices: Batch serice Update/Update two serice Spool serice Through this setup, all SAP ABAP serices are running on each Application Serer and are no single points of failure (SPOF) any more. The SAP high aailability connector must be enabled in the default profile. This step requires that System Automation for Multiplatforms is already installed on the cluster nodes, so it probably must be done later. For more information about how to enable the SAP high aailability connector for your platform, see Enabling the SAP high aailability Connector on page 27. It is required to disable the SAP restart capability for the Enqueue Serer and the Enqueue Replication Serer in the appropriate profiles. Otherwise, the automatic restart of SAP by using the command startsapsr mismatches with System Automation for Multiplatforms start function and causes problems with the automation. Set the SAP profile parameter for EN and ERS to Start_Program_<NR> in the EN and ERS profiles in the /sapmnt/<sid>/profile directory. For all serers other than EN and ERS, set the SAP profile parameters Restart_Program_<NR>.If Start_Program is defined, then Initial start is started by startsapsr framework. 20 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

37 Recoery start is started by System Automation for Multiplatforms. Resources can start either in place or resources can fail oer. If Restart_Program is defined, then Initial start is started by startsapsr framework Recoery start is started by startsapsr framework. Resources can start in place. Table 6. Start_Program_<NR> and Restart_Program_<NR> alues of SAP profiles. Components Start_Program_<NR> Restart_Program_<NR> Enqueue Serer Message Serer Enqueue Replication Serer Application Serer ABAP Gateway (in DVEBMGS profile) Jaa Gateway (in SCS profile) Web dispatcher X X X X X X X Optional: Faster message serer logon group handling during restart. When the SAP messsage serer is restarted, for example as part of a maintenance operation, it takes some time until the messages serer recoered the information about SAP logon groups. Users and RFC connections using these logon groups can not log on during this time. By implementing SAP Note Message Serer: sae logon groups feature you can shorten this delay. Verifying the initial installation The following steps erify the correct setup of the ERS replication. The commands listed with each erification step assume an ASCS setup. If you erify a Jaa setup replace the following instance names: ASCS with SCS DVEBMGS with J D with J The syntax of the ifconfig commands shown in the samples below applies to the AIX operating system. For Linux, replace the AIX commands with the following Linux commands: Add IP alias AIX: ifconfig <interface_name> <IP_alias> netmask <IP_netmask> alias up Linux: ifconfig <interface_name>:<unique_number> <IP_alias> netmask <IP_netmask> up Delete IP alias AIX: ifconfig <interface_name> <IP_alias> delete Linux: ip addr del <IP_alias> de <interface_name> Prerequisites: Chapter 1. SAP Central Serices high aailability policy 21

38 All instances are stopped. Execute all steps as <sid>adm user. For the erification the SAP system is started and a manual failoer of the ASCS and ERS is executed twice. First a failoer of the ASCS instance from the first node to the second node and then a failoer of the ASCS instance from the second node back to the first node. 1. Verification step: Initial start - ASCS on first node and ERS on second node a. Start the ERS instance on the second node: ifconfig <interface_name> <ERS_IP_alias> netmask <IP_netmask> alias up startsap r3 ERS<ID> b. Start ASCS and the Primary Application Serer instance on the first node: ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up startsap r3 ASCS<ID> startsap r3 DVEBMGS<ID> c. Start the Additional Application Serer instance on the second node: startsap r3 D<ID> d. Check replication status for each ERS instance on the second node using ensmon utility: ensmon pf=/usr/sap/<sid>/ers<id>/profile/<sid>_ers<id>_<node2> Select task Get replication information. The output looks like this...replication is enabled in serer, replication serer is connected. Replication is actie... e. Verify successful start of all Application Serers: Logon to the Primary Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Additional Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Primary Application Serer for Jaa using a web browser. The default is: Logon to the Additional Application Serer for Jaa using a web browser. The default is: 2. Verification step: Change replication direction - (A)SCS on second node and ERS on first node a. Stop Additional Application Serer instance on the second node: stopsap r3 ERS<ID> stopsap r3 D<ID> ifconfig <interface_name> <ERS_IP_alias> delete b. Stop ASCS, ERS and Primary Application Serers instances on the first node: stopsap r3 DVEBMGS<ID> stopsap r3 ASCS<ID> ifconfig <interface_name> <ASCS_IP_alias> delete c. Start ASCS IP instances on the second node: ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up startsap r3 ASCS<ID> d. Start ERS instances on the first node: ifconfig <interface_name> <ERS_IP_alias> netmask <IP_netmask> alias up startsap r3 ERS<ID> 22 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

39 e. Check replication status for each ERS instance on first node using ensmon utility: ensmon pf=/usr/sap/<sid>/ers<id>/profile/<sid>_ers<id>_<node1> Select task Get replication information. The output looks like this...replication is enabled in serer, replication serer is connected. Replication is actie... f. Start the Primary Application Serer instance on the first node: startsap r3 DVEBMGS<ID> g. Start the Additional Application Serer instance on the second node: startsap r3 D<ID> h. Verify successful start of all Application Serers: Logon to the Primary Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Additional Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Primary Application Serer for Jaa using a web browser. The default is: Logon to the Additional Application Serer for Jaa using a web browser. The default is: 3. Verification step: Change replication direction: ASCS on first node and ERS on second node: a. Stop ERS and Primary Application Serer instance on the first node: stopsap r3 DVEBMGS<ID> stopsap r3 ERS<ID> ifconfig <interface_name> <ERS_IP_alias> delete b. Stop ASCS and Additional Application Serers instances on the second node: stopsap r3 D<ID> stopsap r3 ASCS<ID> <irtual ASCS host name> ifconfig <interface_name> <ASCS_IP_alias> delete c. Start ASCS instances on the first node: ifconfig <interface_name> <ASCS_IP_alias> netmask <IP_netmask> alias up startsap r3 ASCS<ID> d. Start ERS instances on the second node: ifconfig <interface_name> <ERS_IP_alias> netmask <IP_netmask> alias up startsap r3 ERS<ID> e. Check replication status for each ERS instance on the second node using ensmon utility: ensmon pf=/usr/sap/<sid>/ers<id>/profile/<sid>_ers<id>_<node2> Select task Get replication information. The output looks like this...replication is enabled in serer, replication serer is connected. Replication is actie... f. Start Primary Application Serer instance on the first node: startsap r3 DVEBMGS<ID> g. Start Additional Application Serer instance on the second node: startsap r3 D<ID> h. Verify successful start of all Application Serers: Chapter 1. SAP Central Serices high aailability policy 23

40 Logon to the Primary Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Additional Application Serer for ABAP using the SAP graphical user interface (SAPGUI). Logon to the Primary Application Serer for Jaa using a web browser. The default is: Logon to the Additional Application Serer for Jaa using a web browser. The default is: After successful erification eerything has to be stopped. All irtual IP addresses hae to be deactiated. Installing and setting up System Automation for Multiplatforms This topic describes the installation and setup of System Automation for Multiplatforms for an automated and highly aailable SAP system. Prerequisites For a list of UNIX and Linux prerequisites, see Tioli System Automation for Multiplatforms Installation and Configuration Guide. Installing System Automation for Multiplatforms on all cluster nodes System Automation for Multiplatforms must be installed on all nodes. Proceed as follows for each node: 1. Verify that your system has the necessary prerequisites for System Automation for Multiplatforms. Enter the following command:./prereqsam This command writes a log to /tmp/prereqsam.<number>.log. Check this log file before you proceed with the installation. 2. Install the System Automation for Multiplatforms software. Enter:./installSAM The command writes a log to /tmp/installsam.<number>.log. Check this log file to erify the installation. 3. Set and export the enironment ariable CT_MANAGEMENT_SCOPE to 2 for all users of System Automation for Multiplatforms. Verify your changed settings. After you logged in, enter: en grep $CT_MANAGEMENT_SCOPE The output should be CT_MANAGEMENT_SCOPE=2 For more information about installing, see Tioli System Automation for Multiplatforms Installation and Configuration Guide. 24 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

41 Granting read and write access for the <sapsid>adm The userid <sapsid>adm must hae the authority to perform System Automation for Multiplatforms commands which are launched by the SAP high aailability interface. To setup the non-root security for the <sapsid>adm user ID, see Tioli System Automation for Multiplatforms Administrator's and User's Guide. It is sufficient to use the role sa_operator. Setting up the domain To set up the IBM Tioli System Automation for Multiplatforms domain perform the following steps: 1. Execute the following command on each node: preprpnode <node1> <node2> 2. Create the SAP domain for IBM Tioli System Automation for Multiplatforms, where sap is the domain name. You can use another name of your choice: mkrpdomain sap <node1> <node2> 3. Start the domain: startrpdomain sap 4. Query the domain until it is displayed as online: lsrpdomain You should see output similar to Name OpState RSCTActieVersion MixedVersions TSPort GSPort sap Online No Ensure that all nodes in the domain are online too: lsrpdomain You should see output similar to Name OpState RSCTVersion node1 Online node2 Online For more information about how to set up a domain, refer to Tioli System Automation for Multiplatforms Administrator's and User's Guide. Setting up the tiebreaker If the number of nodes in the System Automation domain is een, a tiebreaker needs to be defined to sole situations, where the nodes cannot communicate with each other. For more information about how to set up a network tie breaker, refer to Tioli System Automation for Multiplatforms Administrator's and User's Guide. Enabling syslog daemon on AIX AIX only: Actiate syslog daemon to write into /tmp/syslog.out files. The syslog will contain messages written by the System Automation for Multiplatforms scripts. 1. In /etc/syslog.conf actiate or uncomment the entry: *.debug /tmp/syslog.out rotate size 100k files 4 2. Create the log file in case it does not exist: touch /tmp/syslog.out Chapter 1. SAP Central Serices high aailability policy 25

42 3. Restart the syslog daemon. refresh -s syslogd Installing and setting up the SAP high aailability policy feature Find out how to install and set up the SAP high aailability policy feature. Packaging The code of the SAP high aailability policy feature is shipped as part of the System Automation for Multiplatforms product, but you need a separate license to enable the code You get the license by ordering the SAP high aailability policy feature. The name of the license file is sam41sap.lic, which is stored in the following locations of the SAP high aailability policy feature delierable: DVD Install the SAP high aailability policy feature license from the DVD IBM Tioli System Automation for Multiplatforms 4.1 IBM Tioli System Automation for Multiplatforms SAP Policy. The license file is located in the directory SAM4100FeatSAP/license. Electronic delierable If you obtain the SAP high aailability policy feature license through electronic distribution, the license file is named CIVG8ML.txt. Rename or copy the electronic distribution file to sam41sap.lic. Installing the SAP high aailability policy feature license Before you can install the SAP high aailability policy feature license, install the System Automation for Multiplatforms base product as described in Installing System Automation for Multiplatforms on all cluster nodes on page 24. Use the samlicm command to install the SAP high aailability policy feature license on all nodes in the cluster. Execute the following command to install the license on all nodes: samlicm -i <license file location> /sam41sap.lic To erify that the feature license has been successfully installed, issue the following command: samlicm -s The name of the SAP high aailability policy feature should appear as alue of the Product Annotation field in the output of the command. For example:... Product Annotation: SA for MP - SAP Central Serices high aailability policy Creation date: Fri Dec 6 00:00:01 MET 2013 Expiration date: Thu Dec 31 00:00:01 MET For more information about the samlicm command, see System Automation for Multiplatforms Reference Guide. Restrictions If you edit the start, stop, and monitor scripts used in the SAP high aailability policy feature, no support is proided for the modified scripts. 26 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

43 The scripts will still be used to automate your SAP installation, but you will find the message Modified script not supported in the syslog for each modified script. Enabling the SAP high aailability Connector After System Automation for Multiplatforms is installed on all cluster nodes, the SAP high aailability Connector must be configured in the SAP profiles. It is sufficient to enter the required entries into the default profile. Enable the SAP high aailability connector. Otherwise, all start or stop commands of all SAP tools, for example sapcontrol or SAP MC, are reersed by System Automation for Multiplatforms. Depending on whether you hae an AIX or Linux platform, or you are running SAP HANA on Power Linux, add the following entries to the default profile of your SAP system. Replace <SAPSID> with the SAPSID of your SAP System: AIX # # SAP high aailability connector # serice/halib = /usr/sap/<sapsid>/sys/exe/uc/rs6000_64/saphascriptco.o serice/halib_cluster_connector = /usr/sbin/rsct/sapolicies/sap/bin/sap_tsamp_cluster_connector LINUX Replace <your platform> with the appropriate directory name: # # SAP high aailability connector # serice/halib = /usr/sap/<sapsid>/sys/exe/uc/<your platform>/saphascriptco.so serice/halib_cluster_connector = /usr/sbin/rsct/sapolicies/sap/bin/sap_tsamp_cluster_connector SAP HANA on Power Linux # # SAP high aailability connector # serice/halib = /usr/sap/<sapsid>/sys/exe/hdb/saphascriptco.so serice/halib_cluster_connector = /usr/sbin/rsct/sapolicies/sap/bin/sap_tsamp_cluster_connector Refer to SAP Note "SAP high aailability Script Connector Library" for details about the latest patch leel for the SAP high aailability Script Connector Library. Note: For SAP HANA instances: If the file /usr/sap/<sapsid>/sys/exe/hdb/ saphascriptco.so is not included in the HANA installation, extract the file from a Power LINUX SAP Kernel Part I package manually: 1. Identify SAP Kernel ersion (00 - default HANA instance number), enter sapcontrol -nr 00 -function GetVersionInfo 2. Download SAP Kernel Part I package. Use the highest patch leel SAPEXE_<patch_leel>-<number>.SAR. You can find the patch on the SAP Support Portal. 3. Extract saphascriptco.so from SAR file, enter SAPCAR -xf SAPEXE_<patch_leel>-<number>.SAR saphascriptco.so 4. Copy saphascriptco.so to HANA installation, enter cp saphascriptco.so /usr/sap/<sapsid>/sys/exe/hdb/saphascriptco.so 5. Use the HANA installation path in the profile, enter serice/halib = /usr/sap/<sapsid>/sys/exe/hdb/saphascriptco.so Chapter 1. SAP Central Serices high aailability policy 27

44 6. Add the halib_cluster_connector parameter in the profile, enter serice/halib_cluster_connector = /usr/sbin/rsct/sapolicies/sap/bin/sap_tsamp_cluster_connector Note: It is required to setup non-root user security for the <SID>adm user. The sapstartsr process calls the HA connector by using the <SID>adm user. Migrating the SAP Central Serices high aailability solution from SA MP V3.2 to V4.1 The SAP Central Serices high aailability automation policy shipped with System Automation for Multiplatforms ersion 4.1 incorporates major changes in the way the components of a SAP solution are controlled and managed. The new SAP Central Serices high aailability policy makes use of new interfaces and conforms to adisories made by SAP. Because of these changes, a SAP Central Serices high aailability policy generated with System Automation for Multiplatforms 4.1 will show major differences compared to a SAP Central Serices high aailability policy generated with ersion 3.2 Thus the migration process is essentially a way of a smoothly replacing the former policy with a new policy that conforms to the changed methods of controlling a SAP solution: With System Automation for Multiplatforms ersion 4.1 all existing SAP Central Serices high aailability ersion 3.2 policies can still be used and actiated with the following restrictions: Policies are stored as complete policy file in the policy pool. The complete policy file was created with System Automation for Multiplatforms ersion 3.2 from a SAP Central Serices high aailability policy template of the same ersion. These existing SAP Central Serices high aailability policies are usually stored in the System Automation for Multiplatforms policy pool and are not erased or oerwritten when a new release is installed. The start, stop, monitor scripts used by ersion 3.2 SAP Central Serices high aailability policies are still deliered with ersion 4.1, so they do not hae to be saed before migrating. The former SAP Central Serices high aailability policy template files and their related snippets are replaced by new ersions when System Automation for Multiplatforms ersion 4.1 is installed. The new SAP Central Serices high aailability policy wizard contained in System Automation for Multiplatforms ersion 4.1 will not work with the former policy templates. So you cannot use the old template files to generate or change SAP Central Serices high aailability policies ersion 3.2, een if you saed these template files to another location before installing System Automation for Multiplatforms ersion 4.1. Only SAP NetWeaer ersions 7.0 or higher with kernel ersions 7.20 or higher are supported by the SAP Central Serices high aailability solution proided by System Automation for Multiplatforms ersion 4.1. SAP solutions that are based on a SAP Central Instance (CI) implementation are no longer supported by the SAP Central Serices high aailability solution. You need to hae a SAP Central Serices (CS) setup. Upgrading the SAP cluster to System Automation for Multiplatforms ersion 4.1 To upgrade your cluster to the new ersion of System Automation for Multiplatforms, follow the steps described in System Automation for 28 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

45 Multiplatforms Installation and Configuration Guide. You might either migrate the entire domain or use the node-by-node approach. The System Automation for Multiplatforms upgrade will not interfere with the currently running SAP Central Serices high aailability policy, the policy will remain loaded. But for safety reasons be sure to hae the complete XML automation policy file for your SAP Central Serices high aailability setup aailable as a backup, either stored in the System Automation for Multiplatforms policy pool(s) or in another location. The former complete XML automation policy is also working with the new System Automation for Multiplatforms ersion. Granting access for the <sapsid>adm user ID The user ID <sapsid>adm must hae the authority to run System Automation for Multiplatforms commands, which are started by the SAP Central Serices high aailability interface. Refer to System Automation for Multiplatforms Administrator's and User's Guide to set up the non-root security for the <sapsid>adm user ID. It is sufficient to use the role sa_operator. Creating a new SAP high aailability automation policy Use the policy wizard contained in System Automation for Multiplatforms ersion 4.1 to create the SAP high aailability automation policy ersion 4.1 as described in Chapter 5, Using the wizard to configure and actiate the policy, on page 141. The policy wizard will not automatically extract configuration information from your former SAP Central Serices high aailability policy (template) files. You hae to enter again all alues manually, but you are assisted by the haresting functions of the new policy wizard. In addition you can refer to the parameter and alue summary, that was created in HTML format at the time you configured your former ersion 3.2 SAP Central Serices high aailability policy. The file should hae been saed into the policy pool with the same name as the former template file and the added extension.html. Modifying SAP profile parameters Before the new SAP Central Serices high aailability policy can be actiated, you hae to adjust some settings in your SAP profiles: Set the SAP profile parameter for EN and ERS to Start_Program_<NR>. Do NOT set the profile parameter to Restart_Program, otherwise proper recoery by System Automation for Multiplatforms will not work. Set the SAP profile parameters for all other serers to Restart_Program_<NR>. Enabling the SAP high aailability Connector After System Automation for Multiplatforms has been installed on all cluster nodes, the SAP high aailability Connector must be configured in the SAP profiles. It is sufficient to put the required entries into the default profile. Refer to Enabling the SAP high aailability Connector on page 27 for more information about how to add the SAP high aailability Connector for your platform. Chapter 1. SAP Central Serices high aailability policy 29

46 Configuring and actiating Actiating and erifying the SAP Central Serices high aailability policy ersion 4.1 Actiate and erify your new SAP Central Serices high aailability policy: Deactiate your existing policy using the sampolicy -d command. Actiate the new SAP Central Serices high aailability policy as described in Using the wizard to configure and actiate the SAP Central Serices high aailability policy on page 42. Verify the policy as described in Verifying on page 78. The following topics describe how to configure the SAP Central Serices high aailability policy with the sampolicy wizard. When you defined the policy with the correct parameter alues, you can then actiate your SAP Central Serices high aailability solution. SAP Central Serices high aailability policy The SAP Central Serices high aailability policy defines all SAP components as resources and starts and stops them in a well defined sequence to proide high aailability for your SAP system. For each setup described in Planning on page 1 there is a separate policy. See Table 11 on page 42 for a list of the policy files depending on the SAP Central Serices high aailability setup. ABAP Central Serices (ASCS) high aailability policy The ABAP Central Serices (ASCS) high aailability policy consists of equialencies, resource groups, floating and fixed resources, that are connected to each other with arious relationships. Figure 10 on page 31 proides an oeriew of all resources that can be part of a ABAP Central Serices (ASCS) high aailability policy. 30 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

47 Figure 10. ASCS high aailability policy Table 7 proides an oeriew of all resources. See Table 8 on page 33 for a description of the tags used for the resource names as well as examples. Table 7. Resources and resource groups of the ASCS high aailability policy Name Resource name (according to policy naming conentions) Resource Type ABAP Network <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_NETIF Equialency Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed ERS Network Equialency <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_NETIF Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed SAPRouter Network <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_NETIF Equialency Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed Chapter 1. SAP Central Serices high aailability policy 31

48 Table 7. Resources and resource groups of the ASCS high aailability policy (continued) Name Resource name (according to policy naming conentions) Resource Type Web Dispatcher Network <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_NETIF Equialency Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed ABAP SAP Central <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS> Group Serices group top-leel group ABAP SAP Instance Agent <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_SRV Group group ASCS Serice IP <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ip Floating Instance Agent <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_sapstartsr Floating ABAP SAP Central Serices <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ASCS Group group Enqueue Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_es Floating Message Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ASCS>_ms Floating Enqueue Replication <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS> Group Serer group ERS Instance Agent group <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_SRV Group Enqueue Replication Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ip Floating SericeIP Instance Agent <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_sapstartsr Floating Enqueue Replication Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ERS Group group Enqueue Replication Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ers Floating Primary Application Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY> Group top-leel group Primary Application Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_SRV Group Instance Agent group Instance Agent <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_ Fixed sapstartsr Primary Application Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_AS Group group Primary Application Serer <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_as Fixed Additional Application <A_PREFIX>_<SAPSID> <INSTANCE_NAME>_<NODENAME_ADDITIONAL> Group Serer top-leel group Additional Application <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_SRV Group Serer Instance Agent group Instance Agent <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_ Fixed sapstartsr Additional Application <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_AS Group Serer group Additional Application <A_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_as Fixed Serer SAProuter group <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER Group 32 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

49 Table 7. Resources and resource groups of the ASCS high aailability policy (continued) Name Resource name (according to policy naming conentions) Resource Type SAProuter <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_saprouter Floating SAP router Serice IP <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_ip Floating SAP WEB Dispatcher <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD> Group top-leel group SAP WEB Dispatcher <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_SRV Group Instance Agent group SAP Web Dispatcher Serice <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_ip Floating IP Instance Agent <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sapstartsr Floating SAP WEB Dispatcher group <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_WD Group SAP WEB Dispatcher <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sapwebdisp Floating Host Agent Group SAP_HOST_AGENT_<NODENAME> Group Host Agent SAP_HOST_AGENT_<NODENAME>_ha Fixed Table 8. Description and examples of placeholders for ABAP resource names Tag Description Example <A_PREFIX>, Prefix for resources, has to be specified in policy. Use a meaningful alue to easily identify ABAP, SAPROUTER <ROUT_PREFIX>, resources later. <WD_PREFIX> <SAPSID>, SAP System SID LOP <SAPWEBDISP_SID> <INTERFACENAME> Name of a network interface eth0 <NODENAME_PRIMARY>, Hostname of the node on which the AS is running sapnode01 <NODENAME_ADDITIONAL> <NODENAME_1>, <NODENAME_2> Hostnames of the node on which the ASCS Central Serices and the Enqueue Replication Serer are allowed to run sapnode01 <INSTANCE_NAME> SAP Application Serer Instance Name DVEBMGS01 <INSTANCE_NAME_ERS> SAP Enqueue Replication Serer Instance Name ERS10 <INSTANCE_NAME_WD> SAP Web Dispatcher Instance Name WD00 The ABAP SAP Central Serices (ASCS) group: The ABAP SAP Central Serices (ASCS) group contains four floating resources: a SericeIP, the Instance Agent resource, and the ABAP Enqueue and Message Serers. All are tied together by StartAfter (SA) and StopAfter (SO) relationships. When the ASCS group is started, the IP resource is started first. Once the IP resource is online, the Instance Agent resource is started next, followed by the Enqueue Serer and the Message Serer. All resources are contained in collocated groups, so they are always started on the same node. All resources are mandatory group members. No restart is attempted by System Automation for Multiplatforms if one of the resources fails, but a failoer of the whole group is triggered instead. The ABAP Enqueue Replication Serer group: Chapter 1. SAP Central Serices high aailability policy 33

50 The Enqueue Replication Serer group contains three mandatory floating resources: a SericeIP, the Instance Agent resource and the ABAP Enqueue Replication Serer (ERS) itself. All are tied together by StartAfter (SA) and StopAfter (SO) relationships. When the ABAP Enqueue Replication Serer group is started, the SericeIP is started first, followed by Instance Agent and the ABAP enqueue replication serer. Jaa Central Serices (SCS) high aailability policy The Jaa Central Serices (SCS) high aailability policy consists of equialencies, resource groups, floating resources, and fixed resources that are connected to each other with arious relationships. Figure 11. SCS high aailability policy for Jaa Table 9 proides an oeriew of all resources. See Table 10 on page 36 for a description of the tags that are used for the resource names and examples. Table 9. Resources and resource groups of the Jaa SCS high aailability policy Name Resource name (according to policy naming conentions) Resource type Jaa Network Equialency <J_PREFIX>_<SAPSID><INSTANCE_NAME_SCS>_NETIF Equialency 34 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

51 Table 9. Resources and resource groups of the Jaa SCS high aailability policy (continued) Name Resource name (according to policy naming conentions) Resource type Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed ERS Network Equialency <J_PREFIX>_<SAPSID><INSTANCE_NAME_ERS>_NETIF Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed SAPRouter Network <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_NETIF Equialency Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed Web Dispatcher Network <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_NETIF Equialency Equialency Network Interface <INTERFACENAME>:<NODENAME_1> Fixed Network Interface <INTERFACENAME>:<NODENAME_2> Fixed JAVA SAP Central Serices <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS> Group top-leel group Jaa SAP Instance Agent group <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_SRV Group ASCS Serice IP <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_ip Floating Instance Agent <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_sapstartsr Floating Jaa SAP Central serices <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_SCS Group group Enqueue Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_en Floating Message Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_SCS>_ms Floating Enqueue Replication Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS> Group top-leel group Enqueue Replication Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_SRV Group Instance Agent group Enqueue Replication Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ip Floating Serice SericeIP Instance Agent <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_sapstartsr Floating Enqueue Replication Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ERS Group group Enqueue Replication Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_ers Floating Primary Application Serer top-leel group Primary Application Serer Instance Agent group <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_ sapstartsr <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_SRV Group Group Instance Agent <J_PREFIX>_<SAPSID>_<INSTANCE_NAME_ERS>_sapstartsr Floating Primary Application Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_AS Group group Primary Application Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_PRIMARY>_as Fixed Additional Application Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL> Group group Additional Application Serer Instance Agent group <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_SRV Group Chapter 1. SAP Central Serices high aailability policy 35

52 Table 9. Resources and resource groups of the Jaa SCS high aailability policy (continued) Name Resource name (according to policy naming conentions) Resource type Instance Agent <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_ Floating sapstartsr Additional Application Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_AS Group group Additional Application Serer <J_PREFIX>_<SAPSID>_<INSTANCE_NAME>_<NODENAME_ADDITIONAL>_as Fixed SAProuter group <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER Group SAProuter <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_saprouter Floating SAProuter SericeIP <ROUT_PREFIX>_<SAPSID>_SYS_ROUTER_ip Floating SAP Web Dispatcher top-leel <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD> Group group SAP Web Dispatcher Instance <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_SRV Group Agent group SAP Web Dispatcher SericeIP <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_ip Floating Instance Agent <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sapstartsr Floating SAP Web Dispatcher group <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_WD Group SAP Web Dispatcher <WD_PREFIX>_<SAPWEBDISP_SID>_<INSTANCE_NAME_WD>_sapwebdisp Floating Host Agent Group SAP_HOST_AGENT_<NODENAME> Group Host Agent SAP_HOST_AGENT_<NODENAME>_ha Fixed The namings of the SAProuter and the SAP WEB dispatcher are the same for the ABAP and the JAVA policy. For more information, see Table 7 on page 31. Table 10. Description and examples of placeholders for JAVA resource names Tag Description Example <J_PREFIX> Prefix for resources, to be specified in policy. Use a meaningful alue to easily identify resources later. JAVA_XI <ROUT_PREFIX> <WD_PREFIX> <SAPSID>, SAP System SID LOP <SAPWEBDISP_SID> <INTERFACENAME> Name of a network interface eth0 <NODENAME_PRIMARY>, Host name of the node on which the AS is running sapnode01 <NODENAME_ADDITIONAL> <NODENAME_1>, <NODENAME_2> Host names of the node on which the ASCS Central Serices and the Enqueue Replication Serer are allowed to run. sapnode01 <INSTANCE_NAME> SAP Application Serer Instance Name DVEBMGS01 D02 <INSTANCE_NAME_ERS> SAP Enqueue Replication Serer Instance Name ERS10 <INSTANCE_NAME_WD> SAP Web Dispatcher Instance Name WD00 36 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

53 The Jaa SAP Central Serices (SCS) group: The Jaa SAP Central Serices(SCS) group contains four floating resources: a Serice IP, the Instance Agent resource, and the Jaa Enqueue and Message Serers (ES and MS). All are tied together by StartAfter (SA) and StopAfter (SO) relationships. When the SCS group is started, the IP resource is started first. When the IP resource is online, the Instance Agent resource is started next, followed by the Enqueue Serer and the Message Serer. The SAP gateway process is monitored together with the Message Serer resource. All resources are contained in collocated groups, so they are always started on the same node. All resources are mandatory group members. No restart is attempted by System Automation for Multiplatforms if one of the resources fail, but a failoer of the whole group is triggered instead. The Jaa Enqueue Replication Serer group: The Jaa Enqueue Replication Serer group contains three mandatory floating resources: a SericeIP, the Instance Agent resource and the Jaa Enqueue Replication Serer (ERS) itself. All are tied together by StartAfter (SA) and StopAfter (SO) relationships. When the Jaa Enqueue Replication Serer group is started, the SericeIP is started first, followed by Instance Agent and the Jaa Enqueue Replication Serer. Double Stack (ABAP and Jaa SCS) high aailability policy The ABAP and Jaa SCS HA policy consists of equialencies, resource groups, floating resources, and fixed resources. All components are described the table in ABAP Central Serices (ASCS) high aailability policy on page 30 and Jaa Central Serices (SCS) high aailability policy on page 34. Chapter 1. SAP Central Serices high aailability policy 37

54 Figure 12. Resources of the Double Stack (ABAP and Jaa SCS) high aailability policy Instead of two separate ABAP and Jaa Application Serer groups, the Double-Stack policy consists of only one Application Serer group, which contains the Jaa and ABAP Application Serer resources. The Double Stack application serer is logically diided into the ABAP application serer and the Jaa application serer. Within a System Automation for Multiplatforms domain, one Double Stack application serer instance is automated as two logical application serer resources: an ABAP application serer resource and a Jaa application serer resource. There is a close relationship between these two logical application serer resources: The Jaa instance is always started after the ABAP instance. A corresponding StartAfter relationship causes that starting the Jaa instance initiates a preceding start of the ABAP instance. 38 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

55 Parts of the ABAP and Jaa policies with the same behaior This topic describes parts of the ABAP and Jaa policy that show the same behaior and are automated equally, independent of whether they are part of a ABAP or a Jaa policy. Interaction between Enqueue Serer and Enqueue Replication Serer: A set of six relationships between the Enqueue and Message Serers and the Enqueue Replication Serer proide the most important rules for the high aailability of the SAP Central Serices. Figure 13 shows an oeriew of these relationships, which are referred by their numbers as shown in the picture. Figure 13. Relationships between the Enqueue and Message Serers and the Enqueue Replication Serer A set of example scenarios explain the functions of these relationships. For a detailed description of relationships and their properties, see System Automation for Multiplatforms Administrator's and User's Guide. ES and MS always start collocated on the same node because of their common group constraint. Initial Start: all nodes are aailable ERS starts first (because of [1] and [7]), followed by ES and MS in succession. Since ES was not online before the initial start, ES/MS starts on another node than ERS because of [2], relationship [3] and [5] are not Chapter 1. SAP Central Serices high aailability policy 39

56 applicable in this situation. So the shadow enqueue table is maintained by ERS on another node than then the one on which ES is running. Initial Start: only one node is aailable in a two-node cluster Because of [2] and [5] ES/MS and ERS cannot be started on the same node. The competitie situation is resoled by the priorities that are assigned to the groups of ES/MS and ERS. The group that holds ES and MS has a higher priority than the ERS group, thus it is started on the sole node. The IfPossibe condition relaxes relationship [1]. Thus the SAP Central Serices can be made aailable under the aderse conditions. Failure of ES When the Enqueue Serer fails, it brings down all members of its group too because ES is a mandatory member of the group. System Automation for Multiplatforms recoers ES on the node where ERS is running because of [3]. So ES can rebuild its enqueue table from the shadow that was maintained by ERS. Relationship [5] does not apply to this situation nor does relationship [2] since ES was Online before. MS and the other group members follow ES to the node where it was restarted. There is also an optional restart feature for the Enqueue Serer in the SAP profile, which is able to recoer a failed ES on the same node. This restart feature must be disabled. Otherwise, ES does not start on the node where ERS runs, hence the rebuild of the enqueue table is not possible. For more information, see Configuring SAP profiles on page 20. Failure of MS In former SAP releases, System Automation for Multiplatforms can attempt a restart in place on the same node for a failed Message Serer. In the new SAP release, relationship [6] forces the restart of MS on the node where ERS runs, pulling all other group members, including ES to moe to the ERS node. The restart feature for the Message Serer in the SAP profile can be enabled to recoer a failed MS on the same node. For more information, see Configuring SAP profiles on page 20. The described recoery action by System Automation for Multiplatforms is run in case the SAP restart feature was not able to restart MS on its former node. ERS stop or relocation after ES or MS failure recoery As described in the preious paragraphs, a failed ES is restarted on the node where ERS is running. After ES recoered its enqueue table from the shadow table, ERS stops itself and is restarted by System Automation for Multiplatforms in succession. The restart of ERS takes place on the node where the ES is running, for example anticollocated to ES on another node because of [5]. Arrow number [4] allows only a node where the appropriate ES constituent is not Failed Offline, so ES would be startable on that node. All other relationships do not apply here. There is also an optional restart feature for the Enqueue Replication Serer in the SAP profile, which is able to recoer a failed ERS on the same node. This restart feature must be disabled. Otherwise, ERS does not start on another node away from EN. For more information, see Configuring SAP profiles on page 20. ERS failure If ERS fails for any reason in an otherwise up and running SAP system, it is restarted anticollocated to the ES node because of [5]. Arrow number [4] 40 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

57 allows only a node where the appropriate ES constituent is not Failed Offline. All other relationships do not apply. As already mentioned before there is also an optional restart feature for the Enqueue Replication Serer in the SAP profile, which must be disabled. For more information, see Configuring SAP profiles on page 20. The node where ES is running fails This scenario is a similar to Failure of ES, followed by the ERS stop or relocation after ES or MS failure recoery scenario. In a two-node cluster, ERS cannot be restarted on another node as enforced by [5] if the failed ES node is not recoered. The node where ERS is running fails This situation is similar to ERS stop or relocation after ES or MS failure recoery. The restart of ERS is anticollocated on another node because of [5], but in a two-node cluster there is no other node left. ERS cannot be restarted on another node if the failed ERS node is not recoered. The ABAP and Jaa application serer (AS) groups: The application serers are implemented as fixed resources in the automation policy, because moing an AS instance to another node might cause a long downtime for the AS. Since the SAP architecture facilitates to run more than one AS, it is far better to run at least two AS on different hardware to hae the necessary AS redundancy. Each of the application serer groups contains an Instance Agent resource and a fixed application serer (AS) resource as mandatory members. The application serers are in separate groups to not affect each other. All application serer resources hae a StartAfter relationship to their Message Serer because the Message Serer must be online during startup of an application serer. The application serer must read the license key from the Message Serer. Otherwise, a logon to the AS is not possible, which also inhibits to monitor the application serer. It is not required to restart an application serer, if a failure of the Enqueue Serer or Message Serer occurs. The application serer reconnects to the Message Serer automatically. The Primary Application Serer group and the Additional Application Serer groups contain the application serer (AS) resource as non-mandatory member. The start and stop of application serers, especially the Jaa application serers, can take a long time. Therefore, the start and stop command timeouts are to be set to a alue of seconds, depending on ABAP or Jaa AS. The ABAP and Jaa SAProuter group: The SAProuter program is a SAP utility that controls access to SAP systems. The SAProuter group contains two floating resources: SAProuter Serice IP address Chapter 1. SAP Central Serices high aailability policy 41

58 Both are tied together by StartAfter and StopAfter relationships If you start the SAProuter group, the IP resource is started first, followed by the SAProuter resource itsself. All resoures are contained in a collocated group, so they will always be started on the same node. The ABAP and Jaa SAP Web Dispatcher group: The SAP Web Dispatcher program is an SAP utility that controls Web access for SAP ABAP and Jaa systems. The SAP Web Dispatcher group contains three floating resources: SAP Web Dispatcher Serice IP address SAP Web Dispatcher Instance Agent (sapstartsr) All are tied together by StartAfter and StopAfter relationships If you start the SAP Web Dispatcher group, the IP resource is started first, followed by the Instance Agent resource and the Web Dispatcher resource itself. All resources are contained in a collocated group, so they will always be started on the same node. Host agent groups: A SAP Host Agent is running on each cluster node that is able to host SAP serers and instances. With System Automation for Multiplatforms each of these Host Agents is modelled as a fixed resources in its own resource group. No dependencies exist to other SAP serers and instances. Using the wizard to configure and actiate the SAP Central Serices high aailability policy Each SAP Central Serices high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. To configure the template, run the following command: sampolicy w templatefilename Depending on the SAP Central Serices high aailability setup option that you choose, specify one of the following fully qualified XML template file names: Table 11. Location for the SAP high aailability XML template files SAP Central Serices high aailability setup ABAP Jaa Double-Stack XML template file /usr/sbin/rsct/sapolicies/sap/sap_abap_41.tmpl.xml /usr/sbin/rsct/sapolicies/sap/sap_java_41.tmpl.xml /usr/sbin/rsct/sapolicies/sap/sap_doublestack_41.tmpl.xml You must configure a policy pool before you can run the wizard. The wizard stores all modifications to the policy pool. Set your policy pool to /etc/opt/ibm/tsamp/ sam/policypool. Run the wizard by entering the following command: sampolicy -w /usr/sbin/rsct/sapolicies/sap/sap_abap_41.tmpl.xml 42 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

59 The results are stored to /etc/opt/ibm/tsamp/sam/policypool/sap_abap_41.tmpl.xml The next time you start the wizard, use the file that is stored in the policy pool. If you want to start the wizard for the second time, enter the following command: sampolicy -w /etc/opt/ibm/tsamp/sam/policypool/sap_abap_41.tmpl.xml For a detailed description of the sampolicy wizard, see Chapter 5, Using the wizard to configure and actiate the policy, on page 141. SAP Central Serices high aailability policy parameters The following paragraphs list all parameters that hae to be specified for the different policy options. A HTML file containing all parameter descriptions and all currently defined alues is generated each time the wizard is started and finished using the 0 (zero) selection option. For more information, refer to Closing the wizard on page 155. SAP ABAP Central Serices (ASCS) - Enqueue Replication Serer (ERS) high aailability policy (ABAP) Find the ABAP policy parameter description, alue type, and alue. Table 12. ABAP policy parameters # Parameter description Value type Value 1 String Enter the name of your SA MP domain. Note: Value haresting is proided for this parameter. Proide the name of an existing SA MP domain. The SA MP domain will host the SAP resources that will be configured with this template. 2 Select the IP ersion used in the SAP enironment. One of the following alues: IP4 Depending on the IP ersion, either a NetMask for IP4 or a NetPrefix for IP6 has to be specified. IP4 IP6 3 Specify the existing SAP system ID (SID). The SAP system ID consists of 3 characters and is configured during the SAP installation. String Minimum number of characters: 3, maximum number of characters: 3 (plus additional alue checking) 4 Specify your SAP admin user name. Note: Value haresting is proided for this parameter. String (plus additional alue checking) The default SAP admin user's name is composed of the SAP SID (in lower case) and the suffix adm. Chapter 1. SAP Central Serices high aailability policy 43

60 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 5 String SAP_ABAP Enter your desired prefix for all ABAP resources This prefix will be used as a prefix for all SA MP resources that coer ABAP, for example "SAP_ABAP". For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You may consider to encode the SAP solution name, e.g. PI, ECC or SCM, which would result in a prefix like "PI_ABAP".. Enter the nodes where you want to automate your SAP Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. These nodes must be listed by the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. An ASCS resource will be created for each of the specified nodes. Specify the instance name of the SAP Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the ASCS instance. A sample instance name is ASCS00. Specify the irtual host name for the Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. List of alues. Value type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) String Minimum number of characters: 6, maximum number of characters: 6) Hostname 9 10 This host name will be used as a irtual host name for the Central Serices Instance for ABAP (ASCS). Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=irt_hostname- during the ASCS installation. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Note: Value haresting is proided for this parameter. Specify the irtual IP4 address for the SAP Central Serices Instance for ABAP (ASCS). This IP4 address will be used as a irtual IP address for the floating ASCS instance. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Specify the irtual IP6 address for the SAP Central Serices Instance for ABAP (ASCS). This IP6 address will be used as a irtual IP address for the floating ASCS instance. IP ersion 4 address IP ersion 6 address 44 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

61 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 11 IP ersion 4 address This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the netmask for the irtual ASCS instance IP address Enter the netmask for the subnet of the irtual ASCS instance IP address. An example for a netmask is This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the ASCS instance irtual IP address. Enter the NetPrefix for the ASCS instance irtual IP address. An example for a NetPrefix is 80. Specify the network interface name where your ASCS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) Numeric Minimum alue: 0, maximum alue: 128 String (plus additional alue checking) The network interface specifies to which network interface on each node the irtual ASCS instance IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the ASCS instance will be automated. 14 Specify the instance name of the ABAP ERS instance. Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the ABAP ERS instance. A sample instance name is 'ERS12'. 15 Specify the irtual host name of the ABAP ERS instance. Note: Value haresting is proided for this parameter. String Minimum number of characters: 5, maximum number of characters: 5 (plus additional alue checking) String This host name will be used as a irtual host name for the ABAP ERS instance. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the ABAP ERS installation. If the ERS instance was not installed using a irtual host name, then specify the host name of a unique IP address that will be moed together with the ERS. This host name allows the SAP tools to connect to the node currently running the ERS. Chapter 1. SAP Central Serices high aailability policy 45

62 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 16 This parameter will be ignored unless all following conditions are fulfilled: IP ersion 4 address - Parameter # 2 has the alue "IP4" Note: Value haresting is proided for this parameter. Specify the irtual IP4 address for the ABAP enqueue replication serer (ABAP ERS). This IP4 address will be used as a irtual IP address for the ABAP enqueue replication serer (ABAP ERS) instance. 17 This parameter will be ignored unless all following conditions are fulfilled: IP ersion 6 address Parameter # 2 has the alue "IP6" Note: Value haresting is proided for this parameter. Specify the irtual IP6 address for the ABAP enqueue replication serer (ABAP ERS). This IP6 address will be used as a irtual IP address for the ABAP enqueue replication serer (ABAP ERS) instance. 18 This parameter will be ignored unless all following conditions are fulfilled: IP ersion 4 address Parameter # 2 has the alue "IP4" Note: Value haresting is proided for this parameter. Specify the netmask for the irtual ABAP ERS instance IP address. Enter the netmask for the subnet of the irtual ABAP ERS instance IP address. An example for a netmask is " ". 19 This parameter will be ignored unless all following conditions are fulfilled: Parameter # 2 has the alue "IP6" Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the ABAP ERS instance irtual IP address. Enter the NetPrefix for the ABAP ERS instance irtual IP address. An example for a NetPrefix is Specify the network interface name where your ABAP ERS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: String (plus additional alue checking) 21 (remaining part of description is harested from running system) The network interface specifies to which network interface one each node the irtual ABAP ERS instance IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the ABAP ERS instance will be automated. Do you want to automate the ABAP application serers? The ABAP application serers host the applications and sere the user requests. Automation of the ABAP application serers is recommended, but optional. Choose yes if you want to automate the ABAP application serers. {yes no} 46 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

63 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 21.1 List of alues, alue type Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". for each alue: Enter the nodes where you want to automate the application serers. Note: Value haresting is proided for this parameter. These nodes must be listed by the SA MP command "lsrpnode" for the specified domain. You can use either the long or the short name for a node. An SA MP application serer resource will be created for each of the specified nodes. This parameter must hae the same number of alues as the following parameters: Hostname or IP ersion 4 address Parameter # 21, nested parameter 2 Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". Specify all instance names of your application serers. Use the same order as for the nodes in one of the preious questions. Note: Value haresting is proided for this parameter. In this policy, the instance names are used to identify the instance directory that contains all necessary files for the application serer. The naming syntax is DVEBMGS-InstanceID- or D-InstanceID-. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the instance directory for your application serer on node01 first. This parameter must hae the same number of alues as the following parameters: - Parameter # 21, nested parameter 2 Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". List of alues, alue type for each alue: String (plus additional alue checking) Numeric 300 Enter the start timeout alue for your ABAP application serers. The start timeout attribute determines the maximum run time in seconds of the StartCommand. If the StartCommand does not return within the timeout period, System Automation for Multiplatforms kills the StartCommand with the SIGKILL command and logs a message to the system log of the node. The default alue for the ABAP application serers is Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". Numeric 300 Enter the stop timeout alue for your ABAP application serers. With the stop timeout attribute you specify the amount of time in seconds the stop command for your application serers allowed to run before it is killed by Tioli System Automation. The default alue for the ABAP application serers is 300 seconds. Chapter 1. SAP Central Serices high aailability policy 47

64 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 22 This parameter will be ignored unless all following conditions are fulfilled: {yes no} - Parameter # 21 has the alue "yes" Did you configure a irtual host name during installation for at least one of the application serers specified in the preious question? Choose yes if at least one of the application serers has been installed with a irtual host name Optional; a alue for this parameter is only required if parameter #22 has the alue "yes". Specify the irtual host name for each application serer. Use the same order as for the nodes in one of the preious questions. If you installed one of the application serers without a irtual host name, specify the system host name instead. Note: Value haresting is proided for this parameter. This host name will be used as a irtual host name for an application serer. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the irtual host name for your application serer on node01 first. 23 Do you want to automate the SAP Host Agent? SAP Host Agent can be used for monitoring and control of SAP instances and non-sap instances, operating systems, and databases Optional; a alue for this parameter is only required if parameter #23 has the alue "yes". Enter the nodes where you want to automate the SAP Host Agent. Note: Value haresting is proided for this parameter. These nodes must be listed by the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. An SA MP host agent resource will be created for each of the specified nodes. 24 Do you want SA MP to automate your SAP router? SAP router seres as a proxy in a network connection between SAP systems or between SAP systems and external networks. If you answer this question with yes, SA MP will create automation resources for the SAP router Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Enter the desired prefix for the SAP router resources. You are allowed to use the same prefix as for other resources, like JAVA or ABAP. List of alues, alue type for each alue: Hostname {yes no} List of alues, alue type for each alue: Hostname or IP ersion 4 address {yes no} String SAP_ROUTER 48 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

65 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 24.2 Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". List of alues, alue type for each alue: Enter the nodes where you want to automate the SAP router. Note: Value haresting is proided for this parameter. For each of the nodes specified, SA MP will create SAP router resources This parameter will be ignored unless all following conditions are fulfilled: Hostname or IP ersion 4 address (plus additional alue checking) IP ersion 4 address - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the irtual IP4 address that clients will use to connect to the SAP router. This irtual IP4 address is used to reach the SAP router, independent of the system it is currently running on This parameter will be ignored unless all following conditions are fulfilled: IP ersion 6 address - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the irtual IP6 address that clients will use to connect to the SAP router. This irtual IP6 address is used to reach the SAP router, independent of the system it is currently running on This parameter will be ignored unless all following conditions are fulfilled: IP ersion 4 address Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Enter the NetPrefix for the SAP router irtual IP address. Enter the NetPrefix for the SAP router irtual IP address. An example for a NetPrefix is This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Numeric Minimum alue: 0, maximum alue: 128 Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the netmask for the SAP router irtual IP address. Enter the netmask for the subnet of the SAP router irtual IP address. An example for a netmask is " ". Chapter 1. SAP Central Serices high aailability policy 49

66 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 24.7 Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Enter the network interface for the SAP router IP address. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) String (plus additional alue checking) The aailable network interface specifies to which network interfaces the SAP router irtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the SAP router will be automated Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". String Specify the fully qualified SAP router routing table filename. (remaining part of description is harested from running system) Use the location of the NFS deice that contains the routing table file. An example for the fully qualified SAP router routing table filename is /usr/sap/-sapsid-/sys/global/saprouttab. 25 Do you want SA MP to automate the SAP Web Dispatcher? The SAP Web Dispatcher receies HTTP(s) requests from the internet that are targeted for your SAP system. If you answer this question with yes, SA MP will create automation resources for the SAP Web Dispatcher Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Enter the desired prefix for the SAP Web Dispatcher resources. You are allowed to use the same prefix as for other resources, like JAVA or ABAP Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Enter the nodes where you want to automate the SAP Web Dispatcher. You are allowed to use the same prefix as for other resources, like JAVA or ABAP. Note: Value haresting is proided for this parameter. Nodes where the SAP Web Dispatcher is configured and where it will be automated Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the SAP system ID (SAPSID) for the SAP Web Dispatcher. The SAP system ID (SAPSID) for the SAP Web Dispatcher is required to identify the SAP Web Dispatcher correctly. Note: Value haresting is proided for this parameter. {yes no} String List of alues, alue type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) String (plus additional alue checking) SAP_WDISP 50 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

67 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 25.4 Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". String Specify the instance owner username that will be used to execute the start, stop and monitor commands for SAP Web Dispatcher resources. Note: Value haresting is proided for this parameter. The instance owner username is composed of the SAP Web Dispatcher SID and the suffix "adm" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". String Specify the instance name of the SAP Web Dispatcher instance, i.e. 'W00'. This instance name is used for the instance directory that contains all necessary files for the SAP Web Dispatcher instance. Note: Value haresting is proided for this parameter Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". This host name will be used as a irtual host name for the SAP Web Dispatcher. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the irtual host name for your application serer on node01 first. Note: Value haresting is proided for this parameter This parameter will be ignored unless all following conditions are fulfilled: Hostname IP ersion 4 address - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the irtual IP4 address that clients will use to connect to the SAP Web Dispatcher. Note: Value haresting is proided for this parameter. This irtual IP4 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on This parameter will be ignored unless all following conditions are fulfilled: IP ersion 6 address - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the irtual IP6 address that clients will use to connect to the SAP Web Dispatcher. This irtual IP6 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on. Chapter 1. SAP Central Serices high aailability policy 51

68 Table 12. ABAP policy parameters (continued) # Parameter description Value type Value 25.9 This parameter will be ignored unless all following conditions are fulfilled: IP ersion 4 address Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the netmask for the SAP Web Dispatcher irtual IP address. Enter the netmask for the subnet of the SAP Web Dispatcher irtual IP address. An example for a netmask is " " This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Numeric Minimum alue: 0, maximum alue: 128 Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Enter the NetPrefix for the SAP Web Dispatcher IP address. Enter the NetPrefix for the SAP Web Dispatcher IP address. An example for a NetPrefix is Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". String (plus additional alue checking) Specify the network interface on which SAP Web Dispatcher irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) The aailable network interface specifies to which network interfaces the SAP web dispatcher irtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the SAP Web dispatcher instance will be automated. 26 This parameter will be ignored unless all following conditions are fulfilled: {yes no} - Parameter # 21 has the alue "yes" If your database is automated with SA MP in the same cluster, do you want to create startafter relationships for your application serers? A startafter relationship will be created for each Application Serer. If you want to create startafter relationships to a database, the database needs to be automated in the same cluster as SAP Optional; a alue for this parameter is only required if parameter #26 has the alue "yes". String Enter the name of your floating SA MP database resource. This is the name of your floating SA MP database resource, i.e. db2_db2ax0_0-rs. 52 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

69 SAP JAVA Central Serices (SCS) - Enqueue Replication Serer (ERS) high aailability policy (Jaa) Find the Jaa policy parameter description, alue type, and alue. Table 13. Jaa policy parameters # Parameter description Value type Value 1 String Enter the name of your SA MP domain. Note: Value haresting is proided for this parameter. Proide the name of an existing SA MP domain. The SA MP domain will host the SAP resources that will be configured with this template. 2 Select the IP ersion used in the SAP enironment. One of the following alues: IP4 Depending on the IP ersion, either a NetMask for IP4 or a NetPrefix for IP6 has to be specified. IP4 IP6 3 Specify the existing SAP system ID (SID). Note: Value haresting is proided for this parameter. The SAP system ID consists of 3 characters and is configured during the SAP installation. String Minimum number of characters: 3, maximum number of characters: 3 (plus additional alue checking) 4 Specify your SAP instance owner user name. Note: Value haresting is proided for this parameter. String (plus additional alue checking) The default SAP instance owner user's name is composed of the SAP SID (in lower case) and the suffix "adm". 5 Enter your desired prefix for all JAVA resources. String SAP_JAVA This prefix will be used as a prefix for all SA MP resources that coer SAP JAVA components. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You may consider to encode the SAP solution name, e.g. EP (Enterprise Portal), which would result in a prefix like "PE_JAVA". 6 Enter the nodes where you want to automate your SAP Central Serices Instance for JAVA (SCS). Note: Value haresting is proided for this parameter. These nodes must be listed by the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. A SCS resource will be created for each of the specified nodes. List of alues, alue type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) 7 Specify the instance name of the SAP Central Serices Instance for JAVA (SCS). Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the SCS instance. A sample instance name is 'SCS01'. String Minimum number of characters: 5, maximum number of characters: 5 Chapter 1. SAP Central Serices high aailability policy 53

70 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 8 Hostname Specify the irtual host name for the Central Serices Instance for JAVA (SCS). Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Note: Value haresting is proided for this parameter This host name will be used as a irtual host name for the Central Serices Instance for JAVA (SCS). This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Note: Value haresting is proided for this parameter. Specify the irtual IP4 address for the SAP Central Serices Instance for JAVA (SCS). This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Specify the irtual IP6 address for the SAP Central Serices Instance for JAVA (SCS). This IP6 address will be used as a irtual IP address for the floating SAP Central Serices Instance for JAVA (SCS). This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the netmask for the irtual JAVA SCS instance IP address. Enter the netmask for the subnet of the JAVA SCS instance IP address. An example for a netmask is " ". This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the JAVA SCS instance irtual IP address. Enter the NetPrefix for the JAVA SCS instance irtual IP address. An example for a NetPrefix is 80. IP ersion 4 address IP ersion 6 address IP ersion 4 address Numeric Minimum alue: 0, maximum alue: Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

71 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 13 Specify the network interface name where your JAVA SCS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) String (plus additional alue checking) The network interface specifies on which network interface on each node the irtual JAVA SCS instance IP address can be bound to, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the JAVA SCS instance will be automated. 14 Specify the instance name of the JAVA ERS instance. Note: Value haresting is proided for this parameter. 15 This instance name is used for the instance directory that contains all necessary files for the JAVA ERS instance. A sample instance name is 'ERS11'. Specify the irtual host name of SAP JAVA enqueue replication serer (JAVA ERS). Note: Value haresting is proided for this parameter. String Minimum number of characters: 5, maximum number of characters: 5 (plus additional alue checking) String This host name will be used as a irtual host name for the JAVA ERS instance. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the JAVA ERS installation. If the ERS instance was not installed using a irtual host name, then specify the host name of a unique IP address that will be moed together with the ERS. This host name allows the SAP tools to connect to the node currently running the ERS. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the irtual IP4 address for the JAVA enqueue replication serer (JAVA ERS). Note: Value haresting is proided for this parameter. This IP4 address will be used as a irtual IP address for the JAVA enqueue replication serer (JAVA ERS) instance. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Specify the irtual IP6 address for the JAVA enqueue replication serer (JAVA ERS). This IP6 address will be used as a irtual IP address for the JAVA enqueue replication serer (JAVA ERS) instance. IP ersion 4 address IP ersion 6 address Chapter 1. SAP Central Serices high aailability policy 55

72 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 18 IP ersion 4 address This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the netmask for the irtual JAVA ERS instance IP address Enter the netmask for the subnet of the irtual JAVA ERS instance IP address. An example for a netmask is " ". This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the JAVA ERS instance irtual IP address. Enter the NetPrefix for the JAVA ERS instance irtual IP address. An example for a NetPrefix is 80. Specify the network interface name where your JAVA ERS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) The network interface specifies to which network interface one each node the irtual JAVA ERS instance IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the JAVA ERS instance will be automated. Do you want to automate the JAVA application serers? Automation of the JAVA application serers is recommended, but optional. Choose yes if you want to automate the JAVA application serers. Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". Enter the nodes where you want to automate the application serers. Note: Value haresting is proided for this parameter. These nodes must be listed by the SA MP command "lsrpnode" for the specified domain. You can use either the long or the short name for a node. An SA MP application serer resource will be created for each of the specified nodes. This parameter must hae the same number of alues as the following parameters: - Parameter # 21, nested parameter 2 Numeric Minimum alue: 0, maximum alue: 128 String (plus additional alue checking) {yes no} List of alues, alue type for each alue: Hostname or IP ersion 4 address 56 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

73 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 21.2 List of alues, alue type Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". for each alue: Specify all instance names of your application serers. Use the same order as for the nodes in one of the preious questions. Note: Value haresting is proided for this parameter. In this policy, the instance names are used to identify the instance directory that contains all necessary files for the application serer. The naming syntax is J-InstanceID- or JC-InstanceID-. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the instance directory for your application serer on node01 first. This parameter must hae the same number of alues as the following parameters: String (plus additional alue checking) Parameter # 21, nested parameter 1 Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". Enter the start timeout alue for your JAVA application serers. The start timeout attribute determines the maximum run time in seconds of the StartCommand. If the StartCommand does not return within the timeout period, System Automation for Multiplatforms kills the StartCommand with the SIGKILL command and logs a message to the system log of the node. The default alue for the JAVA application serers is 500. Optional; a alue for this parameter is only required if parameter #21 has the alue "yes". Enter the stop timeout alue for your JAVA application serers. With the stop timeout attribute you specify the amount of time in seconds the stop command for your application serers allowed to run before it is killed by Tioli System Automation. The default alue for the JAVA application serers is 360 seconds. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 21 has the alue "yes" Did you configure a irtual host name during installation for at least one of the application serers specified in the preious question? Choose yes if at least one of the application serers has been installed with a irtual host name. Numeric 500 Numeric 360 {yes no} Chapter 1. SAP Central Serices high aailability policy 57

74 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 22.1 List of alues, alue type Optional; a alue for this parameter is only required if parameter #22 has the alue "yes". for each alue: Specify the irtual host name for each application serer. Use the same order as for the nodes in one of the preious questions. If you installed one of the application serers without a irtual host name, specify the system host name instead. Note: Value haresting is proided for this parameter. Hostname This host name will be used as a irtual host name for an application serer. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the irtual host name for your application serer on node01 first. 23 Do you want to automate the SAP Host Agent? {yes no} SAP Host Agent can be used for monitoring and control of SAP instances and non-sap instances, operating systems, and databases Optional; a alue for this parameter is only required if parameter #23 has the alue "yes". Enter the nodes where you want to automate the SAP Host Agent. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Hostname or IP ersion 4 address no These nodes must be listed by the SA MP command "lsrpnode" for the specified domain. You can use either the long or the short name for a node. An SA MP host agent resource will be created for each of the specified nodes. 24 Do you want SA MP to automate your SAP router? {yes no} SAP router seres as a proxy in a network connection between SAP systems or between SAP systems and external networks. If you answer this question with yes, SA MP will create automation resources for the SAP router Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". String SAP_ROUTER Enter the desired prefix for the SAP router resources. You are allowed to use the same prefix as for other resources, like JAVA or ABAP Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Enter the nodes where you want to automate the SAP router. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) For each of the nodes specified, SA MP will create SAP router resources. 58 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

75 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 24.3 IP ersion 4 address This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the irtual IP4 address that clients will use to connect to the SAP router This irtual IP4 address is used to reach the SAP router, independent of the system it is currently running on. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the irtual IP6 address that clients will use to connect to the SAP router. This irtual IP6 address is used to reach the SAP router, independent of the system it is currently running on. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Specify the netmask for the SAP router irtual IP address. Enter the netmask for the subnet of the SAP router irtual IP address. An example for a netmask is " ". Do you want SA MP to automate the SAP Web dispatcher? - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". Enter the NetPrefix for the SAP router irtual IP address. Enter the NetPrefix for the SAP router irtual IP address. An example for a NetPrefix is 80. IP ersion 6 address IP ersion 4 address Numeric Minimum alue: 0, maximum alue: 128 Chapter 1. SAP Central Serices high aailability policy 59

76 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 24.7 String (plus additional Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". alue checking) Enter the network interface for the SAP router IP address. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) The aailable network interface specifies to which network interfaces the SAP router irtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the SAP router will be automated Optional; a alue for this parameter is only required if parameter #24 has the alue "yes". String Specify the fully qualified SAP router routing table filename. Use the location of the NFS deice that contains the routing table file. An example for the fully qualified SAP router routing table filename is /usr/sap/-sapsid-/sys/global/saprouttab. 25 Do you want SA MP to automate the SAP Web Dispatcher? {yes no} The SAP Web dispatcher receies HTTP(s) requests from the internet that are targeted for your SAP system. If you answer this question with yes, SA MP will create automation resources for the SAP Web dispatcher Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". String SAP_WDISP 25.2 Enter the desired prefix for the SAP Web Dispatcher resources. You are allowed to use the same prefix as for other resources, like JAVA or ABAP. Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Enter the nodes where you want to automate the SAP Web Dispatcher. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) 25.3 Nodes where the SAP Web Dispatcher is configured and where it will be automated. Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the SAP system ID (SAPSID) for the SAP Web Dispatcher. The SAP system ID (SAPSID) for the SAP Web Dispatcher is required to identify the SAP Web Dispatcher correctly. Note: Value haresting is proided for this parameter. String (plus additional alue checking) 60 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

77 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 25.4 String (plus additional Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". alue checking) Specify the instance owner username that will be used to execute the start, stop and monitor commands for SAP Web Dispatcher resources. Note: Value haresting is proided for this parameter The instance owner username is composed of the SAP Web Dispatcher SID and the suffix "adm". Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the instance name of the SAP web dispatcher instance, i.e. 'W00'. This instance name is used for the instance directory that contains all necessary files for the SAP web dispatcher instance. Note: Value haresting is proided for this parameter. Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the irtual host name for the SAP Web Dispatcher. This host name will be used as a irtual host name for the SAP Web dispatcher. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions, i.e. if you specified node01 first, then you now hae to specify the irtual host name for your application serer on node01 first. Note: Value haresting is proided for this parameter. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the irtual IP4 address that clients will use to connect to the SAP Web Dispatcher. Note: Value haresting is proided for this parameter. This irtual IP4 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on. String Hostname IP ersion 4 address Chapter 1. SAP Central Serices high aailability policy 61

78 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 25.8 IP ersion 6 address This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the irtual IP6 address that clients will use to connect to the SAP Web Dispatcher This irtual IP6 address is used to reach the SAP Web Dispatcher, independent of the system it is currently running on. This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the netmask for the SAP Web Dispatcher irtual IP address Enter the netmask for the subnet of the SAP Web Dispatcher irtual IP address. An example for a netmask is " ". This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Enter the NetPrefix for the SAP Web Dispatcher IP address. Enter the NetPrefix for the SAP Web Dispatcher IP address. An example for a NetPrefix is 80. Optional; a alue for this parameter is only required if parameter #25 has the alue "yes". Specify the network interface on which SAP Web Dispatcher irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) The aailable network interface specifies to which network interfaces the SAP web dispatcher irtual IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the SAP Web dispatcher instance will be automated. IP ersion 4 address Numeric Minimum alue: 0, maximum alue: 128 String (plus additional alue checking) 62 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

79 Table 13. Jaa policy parameters (continued) # Parameter description Value type Value 26 {yes no} This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 21 has the alue "yes" If your database is automated with SA MP in the same cluster, do you want to create startafter relationships for your application serers? 26.1 A startafter relationship will be created for each Application Serer. If you want to create startafter relationships to a database, the database needs to be automated in the same cluster as SAP. Optional; a alue for this parameter is only required if parameter #26 has the alue "yes". Enter the name of your floating SA MP database resource. This is the name of your floating SA MP database resource, i.e. "db2_db2ax0_0-rs". String SAP ABAP and Jaa Central Serices (ASCS + SCS) - Enqueue Replication Serer (ERS) high aailability policy (Double Stack) Find a parameter description, alue type, and alue of the Double-Stack resources and the corresponding components. Table 14. Double-Stack resources and the corresponding components # Parameter description Value type Value 1 String Enter the name of your System Automation for Multiplatforms domain. Note: Value haresting is proided for this parameter. Proide the name of an existing System Automation for Multiplatforms domain. The System Automation for Multiplatforms domain hosts the SAP resources that are configured with this template. 2 Select the IP ersion that is used in the SAP enironment. One of the following alues: IP4 Depending on the IP ersion, either a NetMask for IP4 or a NetPrefix for IP6 must be specified. IP4 IP6 3 Specify the existing SAP system ID (SID). Note: Value haresting is proided for this parameter. The SAP system ID consists of 3 characters and is configured during the SAP installation. String Minimum number of characters: 3 Maximum number of characters: 3 (plus extra alue checking) Chapter 1. SAP Central Serices high aailability policy 63

80 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 4 String (plus extra alue Specify your SAP instance owner user name. Note: Value haresting is proided for this parameter. checking) The default SAP instance owner user's name is composed of the SAP SID (in lowercase) and the suffix adm. 5 Enter your desired prefix for all ABAP resources. String SAP_ABAP This prefix is used as a prefix for all resources that coer ABAP, for example SAP_ABAP. For operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You might consider encoding the SAP solution name, for example, PI, ECC, or SCM, which results in a prefix like PI_ABAP. 6 Enter the nodes where you want to automate your SAP Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address (plus extra alue checking) These nodes must be listed by the command lsrpnode for the specified domain. You can use either the long or the short name for a node. An ASCS resource is created for each of the specified nodes. 7 Specify the instance name of the SAP Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the ASCS instance. A sample instance name is 'ASCS00'. String Minimum number of characters: 6, maximum number of characters: 6 (plus extra alue checking) 8 Specify the irtual host name for the Central Serices Instance for ABAP (ASCS).Note: Value haresting is proided for this parameter. Host name This host name is used as a irtual host name for the Central Serices Instance for ABAP (ASCS). Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the ASCS installation. 9 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" IP ersion 4 address Specify the irtual IP4 address for the SAP Central Serices Instance for ABAP (ASCS). Note: Value haresting is proided for this parameter. This IP4 address is used as a irtual IP address for the floating ASCS instance. 64 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

81 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 10 IP ersion 6 address This parameter will be ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Specify the irtual IP6 address for the SAP Central Serices Instance for ABAP (ASCS). 11 This IP6 address is used as a irtual IP address for the floating ASCS instance. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the netmask for the irtual ASCS instance IP address. IP ersion 4 address Enter the netmask for the subnet of the irtual ASCS instance IP address. An example for a netmask is " ". 12 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the ASCS instance irtual IP address. Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the ASCS instance irtual IP address. An example for a NetPrefix is Specify the network interface name where your ASCS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) String plus extra alue checking The network interface specifies to which network interface on each node the irtual ASCS instance IP address can be bound. For AIX an example is en0. For Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the ASCS instance is automated. 14 Specify the instance name of the ABAP ERS instance. Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the ABAP ERS instance. A sample instance name is 'ERS12'. String Minimum number of characters: 5, maximum number of characters: 5 (plus extra alue checking) Chapter 1. SAP Central Serices high aailability policy 65

82 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 15 String Specify the irtual host name of the ABAP ERS instance. Note: Value haresting is proided for this parameter. This host name is used as a irtual host name for the ABAP ERS instance. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the ABAP ERS installation. If the ERS instance was not installed by using a irtual host name, then specify the host name of a unique IP address that is moed together with the ERS. This host name allows the SAP tools to connect to the node currently running the ERS. This parameter is ignored unless all following conditions are fulfilled: Parameter # 2 has the alue "IP4" Specify the irtual IP4 address for the ABAP enqueue replication serer (ABAP ERS). Note: Value haresting is proided for this parameter. This IP4 address is used as a irtual IP address for the ABAP enqueue replication serer (ABAP ERS) instance. This parameter is ignored unless all following conditions are fulfilled: Parameter # 2 has the alue "IP6" Specify the irtual IP6 address for the ABAP enqueue replication serer (ABAP ERS). This IP6 address is used as a irtual IP address for the ABAP enqueue replication serer (ABAP ERS) instance. This parameter is ignored unless all following conditions are fulfilled: Parameter # 2 has the alue "IP4" Specify the netmask for the irtual ABAP ERS instance IP address. IP ersion 4 address IP ersion 6 address IP ersion 4 address Enter the netmask for the subnet of the irtual ABAP ERS instance IP address. An example for a netmask is " ". 19 This parameter is ignored unless all following conditions are fulfilled: Parameter # 2 has the alue "IP6" Enter the NetPrefix for the ABAP ERS instance irtual IP address. Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the ABAP ERS instance irtual IP address. An example for a NetPrefix is Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

83 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 20 Specify the network interface name where your ABAP ERS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: remaining part of description is harested from running system String plus extra alue checking The network interface specifies to which network interface one each node the irtual ABAP ERS instance IP address can be bound. For AIX an example is en0. For Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the ABAP ERS instance is automated. 21 Do you want to automate the ABAP and Jaa application serers? {yes no} yes Automation of the ABAP/Jaa application serers is recommended, but optional. Choose yes if you want to automate the ABAP application serers Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Enter the nodes where you want to automate the application serers. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address These nodes must be listed by the System Automation for Multiplatforms command lsrpnode for the specified domain. You can use either the long or the short name for a node. A System Automation for Multiplatforms application serer resource is created for each of the specified nodes. This parameter must hae the same number of alues as the following parameters: Parameter # 21, nested parameter 2 Chapter 1. SAP Central Serices high aailability policy 67

84 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 21.2 Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Specify all instance names of your application serers. Use the same order as for the nodes in one of the preious questions. Note: Value haresting is proided for this parameter. In this policy, the instance names are used to identify the instance directory that contains all necessary files for the application serer. The naming syntax is DVEBMGS-InstanceID- or D-InstanceID-. Use the same order as for the nodes in one of the preious questions. For example if you specified node01 first, then you must specify the instance directory for your application serer on node01 first. List of alues, alue type for each alue: String (plus extra alue checking) This parameter must hae the same number of alues as the following parameters: Parameter # 21, nested parameter Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Numeric 300 Enter the start timeout alue for your ABAP application serers The start timeout attribute determines the maximum run time in seconds of the StartCommand. If the StartCommand does not return within the timeout period, System Automation for Multiplatforms stops the StartCommand with the SIGKILL command and logs a message to the system log of the node. The default alue for the ABAP application serers is 300. Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Enter the stop timeout alue for your ABAP application serers. With the stop timeouts attribute you specify the amount of time in seconds the stop command for your application serers that are allowed to run before it is stopped by System Automation. The default alue for the ABAP application serers is 300 seconds. Numeric Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

85 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 21.5 Numeric 500 Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Enter the start timeout alue for your Jaa application serers The start timeout attribute determines the maximum run time in seconds of the StartCommand. If the StartCommand does not return within the timeout period, System Automation for Multiplatforms kills the StartCommand with the SIGKILL command and logs a message to the system log of the node. The default alue for the Jaa application serers is 500. Optional; a alue for this parameter is only required if parameter # 21 has the alue "yes". Enter the stop timeout alue for your Jaa application serers. Numeric 360 With the stop timeouts attribute, you specify the amount of time in seconds the stop command for your application serers that are allowed to run before it is stopped by System Automation. The default alue for the Jaa application serers is 360 seconds. 22 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 21 has the alue "yes" {yes no} no Did you configure a irtual host name during installation for at least one of the application serers that are specified in the preious question? Choose yes if at least one of the application serers are installed with a irtual host name Optional; a alue for this parameter is only required if parameter # 22 has the alue "yes". List of alues, alue type for each alue: Host name Specify the irtual host name for each application serer. Use the same order as for the nodes in one of the preious questions. If you installed one of the application serers without a irtual host name, specify the system host name instead. Note: Value haresting is proided for this parameter. This host name is used as a irtual host name for an application serer. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions. That is, if you specified node01 first, then you must specify the irtual host name for your application serer on node01 first. Chapter 1. SAP Central Serices high aailability policy 69

86 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 23 String SAP_JAVA Enter your desired prefix for all Jaa resources This prefix is used as a prefix for all System Automation for Multiplatforms resources that coer SAP Jaa components. For operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You might consider encoding the SAP solution name, for example, EP (Enterprise Portal), which would result in a prefix like PE_JAVA. Enter the nodes where you want to automate your SAP Central Serices Instance for Jaa (SCS). Note: Value haresting is proided for this parameter. These nodes must be listed by the System Automation for Multiplatforms command lsrpnode for the specified domain. You can use either the long or the short name for a node. An SCS resource is created for each of the specified nodes. Specify the instance name of the SAP Central Serices Instance for Jaa (SCS). Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the SCS instance. A sample instance name is 'SCS01'. Specify the irtual host name for the Central Serices Instance for Jaa (SCS). Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address (plus extra alue checking) String Host name Minimum number of characters: 5, maximum number of characters: 5 (plus extra alue checking) 27 This host name is used as a irtual host name for the Central Serices Instance for Jaa (SCS). This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the irtual IP4 address for the SAP Central Serices Instance for Jaa (SCS). Note: Value haresting is proided for this parameter. This IP4 address is used as a irtual IP address for the floating SAP Central Serices Instance for Jaa (SCS). IP ersion 4 address 70 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

87 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 28 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" IP ersion 6 address Specify the irtual IP6 address for the SAP Central Serices Instance for Jaa (SCS) This IP6 address is used as a irtual IP address for the floating SAP Central Serices Instance for Jaa (SCS). This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Specify the netmask for the irtual Jaa SCS instance IP address. Enter the netmask for the subnet of the Jaa SCS instance IP address. An example for a netmask is " ". This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the Jaa SCS instance irtual IP address. Enter the NetPrefix for the Jaa SCS instance irtual IP address. An example for a NetPrefix is 80. Specify the network interface name where your Jaa SCS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) IP ersion 4 address Numeric Minimum alue: 0, maximum alue: 128 String (plus extra alue checking) 32 The network interface specifies on which network interface on each node the irtual Jaa SCS instance IP address can be bound to. For AIX, an example is en0. For Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the Jaa SCS instance is automated. Specify the instance name of the Jaa ERS instance. Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the Jaa ERS instance. A sample instance name is 'ERS11'. String Minimum number of characters: 5, maximum number of characters: 5 (plus extra alue checking) Chapter 1. SAP Central Serices high aailability policy 71

88 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 33 String Specify the irtual host name of the SAP Jaa enqueue replication serer (Jaa ERS). Note: Value haresting is proided for this parameter. This host name is used as a irtual host name for the Jaa ERS instance. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the Jaa ERS installation. If the ERS instance was not installed by using a irtual host name, then specify the host name of a unique IP address that is moed together with the ERS. This host name allows the SAP tools to connect to the node currently running the ERS. 34 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" IP ersion 4 address Specify the irtual IP4 address for the Jaa enqueue replication serer (Jaa ERS). Note: Value haresting is proided for this parameter. This IP4 address is used as a irtual IP address for the Jaa enqueue replication serer (Jaa ERS) instance. 35 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" IP ersion 6 address Specify the irtual IP6 address for the Jaa enqueue replication serer (Jaa ERS). This IP6 address is used as a irtual IP address for the Jaa enqueue replication serer (Jaa ERS) instance. 36 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Value type: IP ersion 4 address Specify the netmask for the irtual Jaa ERS instance IP address. Enter the netmask for the subnet of the irtual Jaa ERS instance IP address. An example for a netmask is " ". 37 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Enter the NetPrefix for the Jaa ERS instance irtual IP address. Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the Jaa ERS instance irtual IP address. An example for a NetPrefix is Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

89 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 38 Specify the network interface name where your Jaa ERS instance irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: remaining part of description is harested from running system String (plus extra alue checking) The network interface specifies to which network interface one each node the irtual Jaa ERS instance IP address can be bound. For AIX, an example is en0. For Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the Jaa ERS instance is automated. 39 Do you want to automate the SAP Host Agent? {yes no} yes SAP Host Agent can be used for monitoring and control of SAP instances and non-sap instances, operating systems, and databases Optional; a alue for this parameter is only required if parameter # 39 has the alue "yes". Enter the nodes where you want to automate the SAP Host Agent. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address These nodes must be listed by the System Automation for Multiplatforms command lsrpnode for the specified domain. You can use either the long or the short name for a node. A System Automation for Multiplatforms host agent resource is created for each of the specified nodes. 40 Do you want System Automation for Multiplatforms to automate your SAP router? {yes no} no SAP router seres as a proxy in a network connection between SAP systems or between SAP systems and external networks. If you answer this question with yes, System Automation for Multiplatforms creates automation resources for the SAP router Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". String SAP_ROUTER Enter the desired prefix for the SAP router resources. You are allowed to use the same prefix as for other resources, like Jaa or ABAP. Chapter 1. SAP Central Serices high aailability policy 73

90 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 40.2 Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". Enter the nodes where you want to automate the SAP router. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address (plus extra alue checking) For each of the nodes that are specified, System Automation for Multiplatforms creates SAP router resources. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". Specify the irtual IP4 address that clients use to connect to the SAP router. This irtual IP4 address is used to reach the SAP router, independent of the system it is running on. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". Specify the irtual IP6 address that clients use to connect to the SAP router. This irtual IP6 address is used to reach the SAP router, independent of the system it is running on. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". Specify the netmask for the SAP router irtual IP address. Enter the netmask for the subnet of the SAP router irtual IP address. An example for a netmask is " ". This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". Enter the NetPrefix for the SAP router irtual IP address. Enter the NetPrefix for the SAP router irtual IP address. An example for a NetPrefix is 80. IP ersion 4 address IP ersion 6 address IP ersion 4 address Numeric Minimum alue: 0, maximum alue: Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

91 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 40.7 Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". String (plus extra alue checking) Enter the network interface for the SAP router IP address. The following network interfaces are aailable on your local system: remaining part of description is harested from running system The aailable network interface specifies to which network interfaces the SAP router irtual IP address can be bound. For AIX, an example on a network interface is en0, for Linux, an example of a network interface is eth0. The same network interface name needs to be aailable on all nodes where the SAP router is automated Optional; a alue for this parameter is only required if parameter # 40 has the alue "yes". String Specify the fully qualified SAP router routing table file name. Use the location of the NFS deice that contains the routing table file. An example for the fully qualified SAP router routing table file name is /usr/sap/-sapsid-/sys/ global/saprouttab. 41 Do you want System Automation for Multiplatforms to automate the SAP Web Dispatcher? {yes no} no The SAP Web Dispatcher receies HTTP requests from the internet that are targeted for your SAP system. If you answer this question with yes, System Automation for Multiplatforms creates automation resources for the SAP Web Dispatcher Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". String SAP_WDISP Enter the desired prefix for the SAP Web Dispatcher resources. You are allowed to use the same prefix as for other resources, like Jaa or ABAP Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Enter the nodes where you want to automate the SAP Web Dispatcher. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: Host name or IP ersion 4 address (plus extra alue checking) Nodes where the SAP Web Dispatcher is configured and where it is automated. Chapter 1. SAP Central Serices high aailability policy 75

92 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 41.3 Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". String (plus extra alue checking) Specify the SAP system ID (SAPSID) for the SAP Web Dispatcher. Note: Value haresting is proided for this parameter The SAP system ID (SAPSID) for the SAP Web Dispatcher is required to identify the SAP Web Dispatcher correctly. Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the instance owner user name that is used to run the start, stop, and monitor commands for SAP Web Dispatcher resources. Note: Value haresting is proided for this parameter. The instance owner user name is composed of the SAP Web Dispatcher SID and the suffix adm. Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the instance name of the SAP Web Dispatcher instance, for example 'W00'. Note: Value haresting is proided for this parameter. This instance name is used for the instance directory that contains all necessary files for the SAP Web Dispatcher instance. Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the irtual host name for the SAP Web Dispatcher. Note: Value haresting is proided for this parameter. This host name is used as a irtual host name for the SAP Web Dispatcher. Enter the same irtual host name that was used for sapinst SAPINST_USE_HOSTNAME=-irt_hostname- during the SAP installation. Use the same order as for the nodes in one of the preious questions. For example, if you specified node01 first, then you must specify the irtual host name for your application serer on node01 first. String (plus extra alue checking) String Host name 76 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

93 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value 41.7 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" IP ersion 4 address Optional: a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the irtual IP4 address that clients use to connect to the SAP web dispatcher. Note: Value haresting is proided for this parameter This irtual IP4 address is used to reach the SAP Web Dispatcher, independent of the system it is running on. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the irtual IP6 address that clients use to connect to the SAP Web Dispatcher. This irtual IP6 address is used to reach the SAP Web Dispatcher, independent of the system it is running on. This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP4" Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". Specify the netmask for the SAP Web Dispatcher irtual IP address. IP ersion 6 address IP ersion 4 address Enter the netmask for the subnet of the SAP Web Dispatcher irtual IP address. An example for a netmask is " " This parameter is ignored unless all following conditions are fulfilled: - Parameter # 2 has the alue "IP6" Optional: a alue for this parameter is only required if parameter # 41 has the alue "yes". Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the SAP Web Dispatcher IP address. Enter the NetPrefix for the SAP Web Dispatcher IP address. An example for a NetPrefix is 80. Chapter 1. SAP Central Serices high aailability policy 77

94 Table 14. Double-Stack resources and the corresponding components (continued) # Parameter description Value type Value Optional; a alue for this parameter is only required if parameter # 41 has the alue "yes". String (plus extra alue checking) Specify the network interface on which SAP Web Dispatcher irtual IP address is actiated on each node as alias. The following network interfaces are aailable on your local system: remaining part of description is harested from running system The aailable network interface specifies to which network interfaces the SAP web dispatcher irtual IP address can be bound. For AIX, an example is en0. For Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the SAP Web Dispatcher instance is automated. 42 This parameter is ignored unless all following conditions are fulfilled: - Parameter # 21 has the alue "yes" {yes no} no If your database is automated with System Automation for Multiplatforms in the same cluster, do you want to create startafter relationships for your application serers? A startafter relationship is created for each application serer. If you want to create startafter relationships to a database, the database needs to be automated in the same cluster as SAP Optional; a alue for this parameter is only required if parameter # 42 has the alue "yes". String Enter the name of your floating System Automation for Multiplatforms database resource, for example db2_db2ax0_0-rs. Verifying Start and stop your SAP Central Serices high aailability solution to erify if your installation run successfully. Verify the failoer scenarios for planned and unplanned outages. Starting and stopping the SAP Central Serices high aailability solution You can start your entire SAP system by issuing the command: chrg -o online -s "Name like % " Enter the following command to display your sample SAP ABAP and Jaa high aailability policy: lssam -noequ Output: 78 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

95 ~# lssam -noequ Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00 Nominal=Offline - Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00_ASCS Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en:node1 - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_en:node2 - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms:node1 - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_ms:node2 - Offline IBM.ResourceGroup:SAP_ABAP_AX6_ASCS00_SRV Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsr - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsr:node1 - Offline IBM.Application:SAP_ABAP_AX6_ASCS00_sapstartsr:node2 - Offline IBM.SericeIP:SAP_ABAP_AX6_ASCS00_ip IP= Offline IBM.SericeIP:SAP_ABAP_AX6_ASCS00_ip:node1 - Offline IBM.SericeIP:SAP_ABAP_AX6_ASCS00_ip:node2 Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2 Nominal=Offline - Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2_AS Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_D03_node2_as:node2 - Offline IBM.ResourceGroup:SAP_ABAP_AX6_D03_node2_SRV Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_D03_node2_sapstartsr:node2 Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1 Nominal=Offline - Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1_AS Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_DVEBMGS02_node1_as:node1 - Offline IBM.ResourceGroup:SAP_ABAP_AX6_DVEBMGS02_node1_SRV Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_DVEBMGS02_node1_sapstartsr:node1 Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10 Nominal=Offline - Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10_AERS Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers - Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers:node1 - Offline IBM.Application:SAP_ABAP_AX6_ERS10_ers:node2 - Offline IBM.ResourceGroup:SAP_ABAP_AX6_ERS10_SRV Nominal=Offline - Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsr - Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsr:node1 - Offline IBM.Application:SAP_ABAP_AX6_ERS10_sapstartsr:node2 - Offline IBM.SericeIP:SAP_ABAP_AX6_ERS10_ip IP= Offline IBM.SericeIP:SAP_ABAP_AX6_ERS10_ip:node1 - Offline IBM.SericeIP:SAP_ABAP_AX6_ERS10_ip:node2 Offline IBM.ResourceGroup:SAP_HOST_AGENT_node1 Nominal=Offline - Offline IBM.Application:SAP_HOST_AGENT_node1_ha:node1 Offline IBM.ResourceGroup:SAP_HOST_AGENT_node2 Nominal=Offline - Offline IBM.Application:SAP_HOST_AGENT_node2_ha:node2 Offline IBM.ResourceGroup:SAP_ROUTER_AX6_SYS_ROUTER Nominal=Offline - Offline IBM.Application:SAP_ROUTER_AX6_SYS_ROUTER_saprouter - Offline IBM.Application:SAP_ROUTER_AX6_SYS_ROUTER_saprouter:node1 - Offline IBM.Application:SAP_ROUTER_AX6_SYS_ROUTER_saprouter:node2 - Offline IBM.SericeIP:SAP_ROUTER_AX6_SYS_ROUTER_ip IP= Offline IBM.SericeIP:SAP_ROUTER_AX6_SYS_ROUTER_ip:node1 - Offline IBM.SericeIP:SAP_ROUTER_AX6_SYS_ROUTER_ip:node2 Offline IBM.ResourceGroup:SAP_WDISP_AW6_W00 Nominal=Offline - Offline IBM.ResourceGroup:SAP_WDISP_AW6_W00_WD Nominal=Offline - Offline IBM.Application:SAP_WDISP_AW6_W00_sapwebdisp - Offline IBM.Application:SAP_WDISP_AW6_W00_sapwebdisp:node1 - Offline IBM.Application:SAP_WDISP_AW6_W00_sapwebdisp:node2 - Offline IBM.ResourceGroup:SAP_WDISP_AW6_W00_SRV Nominal=Offline - Offline IBM.Application:SAP_WDISP_AW6_W00_sapstartsr - Offline IBM.Application:SAP_WDISP_AW6_W00_sapstartsr:node1 - Offline IBM.Application:SAP_WDISP_AW6_W00_sapstartsr:node2 - Offline IBM.SericeIP:SAP_WDISP_AW6_W00_ip IP= Offline IBM.SericeIP:SAP_WDISP_AW6_W00_ip:node1 - Offline IBM.SericeIP:SAP_WDISP_AW6_W00_ip:node2 Your high aailability SAP system is now ready for use. To stop your entire SAP system use the command: chrg -o offline -s "Name like % " Chapter 1. SAP Central Serices high aailability policy 79

96 Failoer scenarios The scenarios coer both planned outages (normal operation, maintenance) and unplanned outages (failures). Each scenario should be erified for proper operation. Test setup The following scenarios expect the topology, as defined in the sample policy, to be a cluster with two nodes (node1, node2). We hae floating groups for the SAProuter, Web Dispatcher and the Enqueue and Enqueue Replication serers, and fixed groups for one application serer on each node. You can use the lssam command to monitor the reaction of the system to the actions taken. Scenarios for planned and unplanned outages In Table 15 and Table 16 on page 81 list the important scenarios for planned and unplanned outages. The preconditions for executing the scenarios are listed aboe the Action, Command and Expected result columns. Each scenario is diided into steps, where each steps precondition is the successful completion of the preceding action. The commands to be executed are listed in the Command column. If you hae different naming conentions, you hae to adapt the commands accordingly. The last column of the tables lists the expected result. Refer to ABAP Central Serices (ASCS) high aailability policy on page 30, Jaa Central Serices (SCS) high aailability policy on page 34, and Chapter 5, Using the wizard to configure and actiate the policy, on page 141 for a detailed explanation of the <placeholders> for the resource names within the command column. For the command examples Table 15, replace the ABAP or Jaa prefix depending on whether you hae ABAB or Jaa setup. Also replace DVEBMSG and D for ABAP application serers with J for Jaa application serers. Table 15. Planned Outages Scenario Action Command Expected result Normal operation Precondition: All groups offline Start an SAP system chrg -o online -s "Name like <PREFIX>_% " Stop SAP system AX6 (Re-)Start SAP system AX6 chrg -o offline -s "Name like <PREFIX>_AX6_%'" chrg -o online -s "Name like <PREFIX>_AX6_%'" Stop an SAP system chrg -o offline -s "Name like <PREFIX>_% " ROUTER, WEBDISP, (A)SCS and DVEBMGS/J groups start on node1. ERS and D/J groups start on node2. (A)SCS, ERS, DVEBMGS/J and D/J groups stop. (A)SCS, and ABAP DVEBMGS/J groups start on node1. ERS and D/J groups start on node2. All groups stop. 80 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

97 Table 15. Planned Outages (continued) Scenario Action Command Expected result Maintenance Precondition: ROUTER, WEBDISP, (A)SCS, and DVEBMGS/J groups are online on node1 ERS and D/J online on node2 Moe all resources away from node1 in order to apply operating system or hardware maintenance. Stop and restart Enqueue Replication Serer in order to apply SAP maintenance (code or profile changes). Moe Enqueue Serer in order to apply SAP maintenance (code or profile changes). Stop and restart Primary Application Serer in order to apply SAP maintenance (code or profile changes). samctrl -u a node1 ROUTER, WEBDISP, (A)SCS, and DVEBMGS/J groups stop. Apply maintenance, reboot, etc. samctrl -u d node1 rgreq -o stop <PREFIX>_<SAPSID>_ <INSTANCE_NAME_ERS> rgreq -o cancel <PREFIX>_<SAPSID>_ <INSTANCE_NAME_ERS> rgreq -o moe <PREFIX>_<SAPSID>_ <INSTANCE_NAME_(A)SCS> rgreq -o stop <PREFIX>_<SAPSID>_ <INSTANCE_NAME>_ <NODENAME_PRIMARY> rgreq -o cancel <PREFIX>_<SAPSID>_ <INSTANCE_NAME>_ <NODENAME_PRIMARY> DVEBMGS/J groups hae status Failed Offline. ROUTER and WEBDISP group start on node2. (A)SCS group starts on node2. ERS terminates. ERS groups sacrificed. DVEBMGS/J groups and ERS groups start on node1. ERS groups stop. ERS groups start on node1. (A)SCS group stops on node2 and restarts on node1. ERS on node1 stops after some seconds and is restarted on node2. DVEBMGS/J groups stop. DVEBMGS/J groups restart on node1. Table 16. Unplanned outages Scenario Simulation action/command Expected result Precondition: ROUTER, WEBDISP, (A)SCS and DVEBMGS/J groups online on node1 ERS and D groups online on node2 To simulate a software failure create a script using the name killscript. Add the following content: kill $1 `ps -ef grep $2 grep - grep awk {print $2} ` Failure of the (A)SCS Enqueue Serer node1: killscript -9 en.sap<sapsid>_ <INSTANCE_NAME_(A)SCS> (A)SCS group stops and restarts on node2. ERS ends after some seconds. ERS group stops and restarts on node1. Chapter 1. SAP Central Serices high aailability policy 81

98 Table 16. Unplanned outages (continued) Scenario Simulation action/command Expected result Failure of the Enqueue Replication Serer Failure of the Message Serer Failure of an (A)SCS application serer node1: killscript -9 er.sap<sapsid>_ <INSTANCE_NAME_ERS> node2: killscript -9 ms.sap<sapsid>_ <INSTANCE_NAME_(A)SCS> node1, ASCS: killscript -9 dw.sap<sapsid>_ DVEBMGS<ID> ERS group stops and restarts on node1. (A)SCS MS restarts on node2 if restart is configured in MS profile. (A)SCS MS restarts on node1 if restart is not configured in MS profile. DVEBMGS/J application serers restart on node1. node1, SCS: killscript -2 jc.sap<sapsid>_j<id> Failure of the node where ES is running node2: reboot (A)SCS groups are started on node1. ERS on node1 stops after some seconds and is restarted on node2 as soon as node2 is aailable in the cluster again. SAP Central Serices high aailability solution checklist The following table lists all steps that are required to implement the SAP Central Serices high aailability solution. You can print the table and check the steps that you already completed in the column "Done". Table 17. SAP high aailability solution checklist # Tasks Reference Done 1.1 Configure automounter for NFS SAP data directory. 1.2 Setup IP configuration and irtual host names. 1.3 Set irtual host names manually (= IP-Alias Addresses). 2.1 Install SAP ASCS with irtual host name. 2.2 Install SAP Jaa SCS with irtual host name. 2.3 Install SAP Enqueue Replication Serer using irtual host name. NFS high-aailability installation setup on page 11 Prerequisites on page 18 in Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page 18 Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page 18 Initial installation on primary node on page 19 in Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

99 Table 17. SAP high aailability solution checklist (continued) # Tasks Reference Done 2.4 Install SAP database instance with irtual host name. 2.5 Install SAP Primary Application Serer. 2.6 Install SAP Additional Application Serers. 2.7 Install SAP web Dispatcher (optional) Initial installation on primary node on page 19 in Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page 18 Initial installation on failoer node on page 19 in Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page 18 Initial installation on primary node on page 19 in Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page Verify SAP installation. Verifying the initial installation 2.9 Stop SAP. on page 21 in Installing a new ASCS, SCS, or Double Stack high 2.10 Remoe IP addresses manually. aailability SAP system on page Install SA MP 4.1 or later. Tioli System Automation for Multiplatforms Installation and Configuration Guide 3.2 Create and setup SA MP domain. Setting up the domain on page Actiate SA MP domain. Setting up the domain on page Create network tiebreaker. Setting up the tiebreaker on page Granting System Automation for Multiplatforms access. Granting read and write access for the <sapsid>adm on page Enabling syslog daemon. Enabling syslog daemon on AIX on page Actiate SAP policy feature license. 4.1 Configure database high aailability policies. 4.2 Proide the policy parameters. System Automation for Multiplatforms Installation and Configuration Guide Database high aailability installation setup on page 10 SAP Central Serices high aailability policy parameters on page Configure SAP policies. Using the wizard to configure and actiate the SAP Central Serices high aailability policy on page Start SAP high aailability. Starting and stopping the SAP Central Serices high aailability solution on page Verify the SAP high aailability solution. Verifying on page 78 Chapter 1. SAP Central Serices high aailability policy 83

100 84 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

101 Chapter 2. SAP HANA System Replication high aailability policy You can define SAP HANA System Replication policies for your SAP HANA installation. The topics in this section describe the process. Planning Learn more about the high aailability concepts for an SAP HANA System Replication system. The main reason for this high aailability setup is to reduce the downtime of an SAP HANA system in case of software or hardware failures. The following terms are used: SAP HANA takeoer A takeoer makes sure that an SAP HANA System Replication secondary instance can operate as SAP HANA System Replication primary instance. System Automation failoer Automatic moement of applications from one node to another node within the same cluster. System Automation uses the term node for one specific operating system image. SAP host ersus SAP system SAP uses the term host for one specific operating system image and SAP system in general for one or multiple hosts by using the same SAP System ID (SAPSID). The high aailability solution for SAP HANA System Replication uses System Automation for Multiplatforms to automate all SAP components. System Automation for Multiplatforms detects failed components and restarts them or initiates a failoer. This setup helps to reduce the operational complexity of an SAP enironment and to aoid operator errors, which result from this complexity. Single Point of Failure (SPOF) In a distributed or standard SAP installation, the SAP Central Serices, the database serer, and the NFS serer are single points of failures (SPOFs). For more information, see Single Point of Failure (SPOF) on page 1 in the SAP Central Serices high aailability policy chapter. Example of a two-node setup The minimum hardware setup consists of a two-node System Automation for Multiplatforms domain. The two nodes are either two physical computers or two LPARs that run on different physical computers. System Automation can automate the takeoer of the SAP HANA System Replication setup. Copyright IBM Corp. 2014,

102 Figure 14. Example of a two-node setup System Automation is installed and a high-aailability cluster is set up on the primary and secondary host. If the primary host has an outage, then System Automation triggers the failoer by using the SAP HANA command hdbnsutil -sr_takeoer on the secondary host. Then, the IP address is moed to the new primary host after the old secondary host becomes the new primary host. When the old primary host comes back online, System Automation integrates the old primary host as new secondary host again by using the SAP HANA command hdbnsutil -sr_register. The log replication starts from the new primary host to the new secondary host. SAP HANA high aailability setup options A high aailability (HA) solution is required to automate the failoer of the primary node, including IP address, to the secondary node. 86 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

103 The following picture shows the SAP HANA System Replication setup with single nodes. Figure 15. System Replication oeriew with single nodes Database high aailability installation setup You can choose between an SAP HANA database installation within the same System Automation for Multiplatforms cluster together with the SAP Central Serices installation or a database installation on a separate cluster. For more information, see Database high aailability installation setup on page 10 in the Chapter 1, SAP Central Serices high aailability policy, on page 1 chapter. NFS high aailability installation setup For more information, see NFS high-aailability installation setup on page 11 in the Chapter 1, SAP Central Serices high aailability policy, on page 1 chapter. High aailability impact Learn more about the impact of arious failure scenarios of the SAP system components, when you use System Automation for Multiplatforms to automate recoery. Manual recoery actions are minimized which otherwise would cause SAP transactions to timeout and roll back. For more information, see High aailability impact on page 12 in the Chapter 1, SAP Central Serices high aailability policy, on page 1 chapter. Chapter 2. SAP HANA System Replication high aailability policy 87

104 SAP HANA documentation references The following table lists references to documentation that are used in this document. Use these links, if you need further details about a specific topic. Table 18. Documentation reference Title SAP HANA Administration Guide SAP HANA Serer Installation and Update Guide SAP HANA in Data Centers - Introduction How to Perform System Replication for SAP HANA Network Recommendations for SAP HANA System Replication Introduction to High Aailability for SAP HANA SAP HANA SPS 08 - What s New? Scale-Out, High Aailability and Disaster Recoery SAP Note: FAQ SAP HANA SAP Note: FAQ SAP HANA System Replication Location sap_hana_serer_installation_guide_en.pdf Installing and setting up Before you set up your SAP HANA enironment for high aailability, you must plan for the installation option which best suits your system. Installing a new HANA database high aailability SAP system Install a new HANA database high aailability SAP system. This description is based on a two node cluster architecture with a primary and a failoer node. For more information about HANA database high aailability SAP system setups, see SAP HANA high aailability setup options on page 86. Prerequisites Obsere the following prerequisites before you start the installation of the HANA database high aailability SAP system. The System Automation for Multiplatforms high aailability policy manages the SAP HANA System Replication Single-Node setup. SAP HANA on Power is required. The SAP HANA Scale-Out (Multi-Node Primary) setup and multitier System Replication is not supported. The following SAP restrictions exist for an SAP HANA System Replication setup: Host names for primary instance and secondary instance cannot be the same. SAPSID and Instance numbers for primary and secondary instance must be the same. 88 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

105 Primary instance needs to hae a full backup before you can set up a secondary instance system replication. The restrictions are documented in SAP Note: HANA high aailability disaster tolerance config. Initial installation on primary and secondary node Follow the SAP documentation SAP HANA Serer Installation and Update Guide to install the SAP HANA database on the primary and secondary node. Ensure to follow the prerequisites. Setup System Replication between primary and secondary node Follow the SAP documentation How to Perform System Replication for SAP HANA, Chapter Enable system replication to setup the SAP HANA System Replication on the primary and secondary node. Configuring SAP profiles Configure the SAP profiles to comply with the high aailability solution proided by System Automation for Multiplatforms. Disable autostart of all SAP instances in all their profiles by commenting the line Autostart = 1. The SAP high aailability connector must be enabled in the default profile. This step requires that System Automation for Multiplatforms is already installed on the cluster nodes, so it probably must be done later. For more information about how to enable the SAP high aailability connector for your platform, see Enabling the SAP high aailability Connector on page 29. Verifying the initial installation Follow the SAP documentation How to Perform System Replication for SAP HANA, Chapter System Replication status checks to erify the correct setup of the SAP HANA System Replication. Installing and setting up System Automation for Multiplatforms Find out how to install and set up System Automation for Multiplatforms for an automated and highly aailable SAP system. For more information, see Installing and setting up System Automation for Multiplatforms on page 24 in the chapter Chapter 1, SAP Central Serices high aailability policy, on page 1. Installing and setting up the SAP high aailability policy feature Find out how to install and set up the SAP high aailability policy feature. For more information, see Installing and setting up the SAP high aailability policy feature on page 26 in the Chapter 1, SAP Central Serices high aailability policy, on page 1. Chapter 2. SAP HANA System Replication high aailability policy 89

106 Installing a new ASCS, SCS, or Double Stack high aailability SAP system Find out how to run a new installation of an ASCS, SCS, or Double Stack high aailability SAP system. Configuring and actiating For more information, see Installing a new ASCS, SCS, or Double Stack high aailability SAP system on page 18 in the Chapter 1, SAP Central Serices high aailability policy, on page 1 chapter. The following topics describe how to configure the SAP high aailability policy with the sampolicy wizard. You can actiate your SAP high aailability solution after defining the policy with the correct parameter alues. About this task For more information about how to inoke the sampolicy wizard, see System Automation for Multiplatforms Reference Guide. SAP HANA System Replication automation The SAP HANA high aailability policy defines all SAP components as resources and starts and stops them in a well-defined sequence to proide high aailability for your SAP HANA system. These components must be specified as automated resources in System Automation for Multiplatforms. Figure 16. Resources of the SAP HANA high aailability policy The following tables show each part, which is to be automated and the corresponding System Automation resource class and resource name. It also indicates dependencies among the resources and how each component is connected to the automated resource. 90 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

107 Table 19. SAP HANA System Replication parts to automate Component Resource class and name* Description HDB Primary instance Resource class SAP HANA SR Primary Instance that is represented by System Automation for IBM.Application Multiplatforms floating resource. HDB Secondary instance HDB SericeIP HDB Instance Agent HDB Network Equialency HDB instance status Resource name SAP_HDB_PH1_HDB00_sr_primary_hdb Resource class IBM.Application Resource name SAP_HDB_PH1_HDB00_sr_secondary_hdb Resource class IBM.SericeIP Resource name SAP_HDB_PH1_HDB00_sr_primary_ip Resource class IBM.Application Resource name SAP_HDB_PH1_HDB00_sapstartsr Resource class IBM.Equialency Resource name SAP_HDB_PH1_HDB00_NETIF All members of IBM.Equialency are resources of the class IBM.NetworkInterface, for example eth0. Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_sr_hdb Resource dependency: StartAfter sapstartsr SAP HANA SR Secondary Instance that is represented by System Automation for Multiplatforms floating resource. Resource dependency: StartAfter sapstartsr StartAfter sr_primary_hdb IP address to access Primary Instance from the SAP clients (SAP Application Serers) instance that is represented by System Automation floating resource. Resource dependency: StartAfter sr_primary_hdb DependsOn NETIF SAP web serice framework that is used to start, stop, and monitorhdbdaemon instance that is represented by System Automation concurrent resource. Resource dependency: StopAfter sr_primary_hdb StopAfter sr_secondary_hdb Selecting the network adapters to be used for IBM.SericeIP resource. Status indicates the HDB instance status reported by the sapcontrol utility. Chapter 2. SAP HANA System Replication high aailability policy 91

108 Table 19. SAP HANA System Replication parts to automate (continued) Component Resource class and name* Description Primary configured Resource class Status Online indicates the current configured primary node. IBM.Test Resource name Primary last online Primary replication actie Primary replication syncing Secondary configured Secondary register in progress Secondary takeoer in progress SAP_HDB_PH1_HDB00_sr_primary_configured Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_sr_primary_last_online Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_ sr_primary_replication_actie Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_ sr_primary_replication_syncing Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_ sr_secondary_configured Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_ sr_secondary_register_in_progress Resource class IBM.Test Resource name SAP_HDB_PH1_HDB00_ sr_secondary_takeoer_in_progress Status Online indicates the last configured primary node. Only used if both instances are Offline. Status Online indicates the replication is currently actie between primary and secondary instance. Status Online indicates the replication is currently in status syncing (Saepoint pending). Status Online indicates the current configured secondary node. Status Online indicates the hdb command sr_register is currently running. Status Online indicates the hdb command sr_takeoer is currently running. 92 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

109 Note: Resource names are examples. You can choose the names when you configure the resources. The following components of the software stack in an SAP HANA System Replication installation need to be automated: Primary and Secondary Host with the following processes on each host: hdbdaemon manages the following subprocesses: hdbindexserer hdbnameserer hdbxsengine hdbwebdispatcher hdbcompileserer hdbpreprocessor sapstartsr start, stop, monitor for hdbdaemon IP address to access Primary Host Using the wizard to configure and actiate the SAP HANA high aailability policy This SAP HANA high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. To configure the template, run the following command: sampolicy w templatefilename Specify the following fully qualified XML template file name: Table 20. Location for the SAP HANA high aailability XML template file SAP high aailability setup HANA System Replication XML template file /usr/sbin/rsct/sapolicies/sap/sap_hdb_sr_41.tmpl.xml The wizard stores all modifications to the policy pool. The default location of your policy pool is /etc/opt/ibm/tsamp/sam/policypool. Run the wizard by entering the following command: sampolicy -w /usr/sbin/rsct/sapolicies/sap/sap_hdb_sr_41.tmpl.xml The results are stored to /etc/opt/ibm/tsamp/sam/policypool/sap_hdb_sr_41.tmpl.xml Next time you start the wizard, use the file that is stored in the policy pool. If you want to start the wizard for the second time, enter the following command: sampolicy -w /etc/opt/ibm/tsamp/sam/policypool/sap_hdb_sr_41.tmpl.xml For a detailed description of the sampolicy wizard, see Chapter 5, Using the wizard to configure and actiate the policy, on page 141. Note: The SAP HANA database should be offline before the policy is actiated. Otherwise, the database gets stopped with the policy actiation. Ensure to authorize the <sid>adm user to run System Automation for Multiplatforms cluster commands. For more information, see Granting read and write access for the <sapsid>adm on page 25. Chapter 2. SAP HANA System Replication high aailability policy 93

110 Ensure to hae the IP address that is used for the IBM.SericeIP deactiated, if it was manually added for testing, before the new policy is actiated. SAP HANA high aailability policy parameters This section proides a list of all parameters that hae to be specified for the SAP HANA high aailability policy. An HTML file that contains all parameter descriptions and all currently defined alues is generated each time the wizard is started and finished using the 0 (zero) selection option. For more information, see Closing the wizard on page 155. Table 21. SAP HANA System Replication HA policy parameters # Parameter description Value type Value 1 String Enter the name of your SA MP domain. Note: Value haresting is proided for this parameter. Proide the name of an existing SA MP domain. The SA MP domain will host the SAP resources that will be configured with this template. 2 Enter the nodes where you want to automate SAP HANA. Note: Value haresting is proided for this parameter. List of alues, alue type for each alue: These nodes must be listed by the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. An SA MP SAP HANA resource will be created for each of the specified nodes. The first node in list will be used as primary instance node. The node name is also used for the remotehost parameter within the hdbnsutil command to enable System Replication for the secondary node. Hostname or IP ersion 4 address 3 Select the IP ersion used in the SAP enironment. One of the following alues: IP4 Depending on the IP ersion, either a NetMask for IP4 or a NetPrefix for IP6 has to be specified. IP4 IP6 4 This parameter will be ignored unless all following conditions are fulfilled: Value type: IP ersion 4 address Parameter # 3 has the alue "IP4" Specify the IP4 address that will be used as tiebreaker. This IP4 address is used to resole cluster quorum in case of a cluster split. 5 This parameter will be ignored unless all following conditions are fulfilled: Value type: IP ersion 4 address Parameter # 3 has the alue "IP4" Specify the irtual IP4 address that clients will use to connect to SAP HANA. This irtual IP4 address is used to reach SAP HANA, independent of the system it is currently running on. 94 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

111 Table 21. SAP HANA System Replication HA policy parameters (continued) # Parameter description Value type Value 6 This parameter will be ignored unless all following conditions are fulfilled: Value type: IP ersion 6 address Parameter # 3 has the alue "IP6" Specify the irtual IP6 address that clients will use to connect to SAP HANA. This irtual IP6 address is used to reach SAP HANA, independent of the system it is currently running on. 7 This parameter will be ignored unless all following conditions are fulfilled: Value type: IP ersion 4 address Parameter # 3 has the alue "IP4" Specify the netmask for the SAP HANA irtual IP address. Enter the netmask for the subnet of the SAP HANA irtual IP address. An example for a netmask is " ". 8 This parameter will be ignored unless all following conditions are fulfilled: Parameter # 3 has the alue "IP6" Value type: Numeric Minimum alue: 0, maximum alue: 128 Enter the NetPrefix for the SAP HANA irtual IP address. An example for a NetPrefix is Enter the network interface for the SAP HANA IP address.(remaining part of description is harested from running system) Value type: String (plus additional alue checking) The aailable network interface specifies to which network interfaces the SAP HANA irtual IP address can be bound, for AIX an example is en0, for Linux, an example is eth0. The same network interface name needs to be aailable on all nodes where the SAP HANA will be automated. Specify the existing SAP system ID (SID). Note: Value haresting is proided for this parameter. The SAP system ID consists of 3 characters and is configured during the SAP installation. Specify your SAP instance owner user name. Note: Value haresting is proided for this parameter. Value type: String Minimum number of characters: 3, maximum number of characters: 3 (plus additional alue checking) Value type: String (plus additional alue checking) The default SAP instance owner user's name is composed of the SAP SID (in lower case) and the suffix adm. Chapter 2. SAP HANA System Replication high aailability policy 95

112 Table 21. SAP HANA System Replication HA policy parameters (continued) # Parameter description Value type Value 12 SAP_HDB Enter your desired prefix for all SAP HANA resources. Value type: String This prefix will be used as a prefix for all SA MP resources that coer SAP HANA, for example SAP_HDB. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. You may consider to encode the SAP solution name, e.g. PI, ECC or SCM, which would result in a prefix like PI_HDB. Specify the instance name of the SAP HANA instance. Note: Value haresting is proided for this parameter. This instance name identifies the SAP HANA instance on all cluster nodes. A sample instance name is HDB00. Specify all site names of your SAP HANA nodes. (remaining part of description is harested from running system) Note: Value haresting is proided for this parameter. The site names are used to enable System Replication for the SAP HANA instance. Use the same order as for the list of nodes. A sample site name is dcsite1. Select the log replication mode for SAP HANA System Replication. Note: Value haresting is proided for this parameter. The SAP HANA log replication mode specifies how to send log information to the secondary instance. The modes synchronous (sync), synchronous in memory (syncmem) or asynchronous (async) can be set. Value type: String Minimum number of characters: 5, maximum number of characters: 5 (plus additional alue checking) List of alues, alue type for each alue: String Value type: String Verifying Start and stop your SAP high aailability solution to erify if your installation runs successfully. Verify the failoer scenarios for planned and unplanned outages. Starting and stopping the SAP HANA high aailability solution Start your entire SAP system by entering the command: chrg -o online -s "Name like % " Enter the following command to display your sample SAP HANA aailability policy: lssam Output: [root@p6sa47]# lssam Online IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sapstartsr_rg Nominal=Online - Online IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr - Online IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr:p6sa47 - Online IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr:p6sa48 Online IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sr_primary_rg Nominal=Online - Online IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb - Offline IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb:p6sa47 - Online IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb:p6sa48 96 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

113 - Online IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip - Offline IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip:p6sa47 - Online IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip:p6sa48 Online IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sr_secondary_rg Nominal=Online - Online IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb - Online IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb:p6sa47 - Ineligible IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb:p6sa48 Online IBM.Equialency:SAP_HDB_PH1_HDB00_NETIF - Online IBM.NetworkInterface:eth0:p6sa48 - Online IBM.NetworkInterface:eth0:p6sa47 Online IBM.Equialency:SAP_HDB_PH1_HDB00_STATUS_DASHBOARD - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_hdb:p6sa47 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_hdb:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_configured:p6sa47 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_configured:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_last_online:p6sa47 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_last_online:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_actie:p6sa47 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_actie:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_syncing:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_syncing:p6sa48 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_configured:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_configured:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_register_in_progress:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_register_in_progress:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_takeoer_in_progress:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_takeoer_in_progress:p6sa48 Your high aailability SAP system is now ready for use. To stop your entire SAP system, use the command: chrg -o offline -s "Name like % " Output: [root@p6sa47]# lssam Offline IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sapstartsr_rg Nominal=Offline - Offline IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr - Offline IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr:p6sa47 - Offline IBM.Application:SAP_HDB_PH1_HDB00_sapstartsr:p6sa48 Offline IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sr_primary_rg Nominal=Offline - Ineligible IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb - Ineligible IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb:p6sa47 - Offline IBM.Application:SAP_HDB_PH1_HDB00_sr_primary_hdb:p6sa48 - Offline IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip - Offline IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip:p6sa47 - Offline IBM.SericeIP:SAP_HDB_PH1_HDB00_sr_primary_ip:p6sa48 Offline IBM.ResourceGroup:SAP_HDB_PH1_HDB00_sr_secondary_rg Nominal=Offline - Ineligible IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb - Offline IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb:p6sa47 - Ineligible IBM.Application:SAP_HDB_PH1_HDB00_sr_secondary_hdb:p6sa48 Online IBM.Equialency:SAP_HDB_PH1_HDB00_NETIF - Online IBM.NetworkInterface:eth0:p6sa48 - Online IBM.NetworkInterface:eth0:p6sa47 Online IBM.Equialency:SAP_HDB_PH1_HDB00_STATUS_DASHBOARD - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_hdb:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_hdb:p6sa48 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_configured:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_configured:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_actie:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_actie:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_syncing:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_primary_replication_syncing:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_configured:p6sa47 - Online IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_configured:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_register_in_progress:p6sa47 Chapter 2. SAP HANA System Replication high aailability policy 97

114 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_register_in_progress:p6sa48 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_takeoer_in_progress:p6sa47 - Offline IBM.Test:SAP_HDB_PH1_HDB00_sr_secondary_takeoer_in_progress:p6sa48 Testing SAP HANA System Replication failoer scenarios The scenarios coer both planned outages (normal operation, maintenance) and unplanned outages (failures). Verify each scenario for proper operation. Test setup The following scenarios expect the topology, as defined in the sample policy, to be a cluster with two nodes (node1, node2). We hae floating groups for the primary and secondary hdb instance, and one fixed group for the sapstartsr process on each node. You can use the lssam command to monitor the reaction of the system to the actions taken. Scenarios for planned and unplanned outages Table 22 and Table 23 on page 99 list the important scenarios for planned and unplanned outages. The preconditions for executing the scenarios are listed aboe the Action, Command and Expected result columns. Each scenario is diided into steps, where each steps precondition is the successful completion of the preceding action. The commands to be executed are listed in the Command column. If you hae different naming conentions, you hae to adapt the commands accordingly. The last column of the tables lists the expected result. In the command examples in Table 22, replace the <PREFIX>, <SAPSID>, and <INSTANCE_NAME_HDB> depending on your enironment. Table 22. Planned Outages Scenario Action Command Expected result Normal operation Precondition: All groups offline Start an SAP HANA system Stop SAP HANA system <SAPSID> (Re-)Start SAP HANA system <SAPSID> Stop an SAP HANA system chrg -o online -s "Name like <PREFIX>_% " chrg -o offline -s "Name like <PREFIX>_<SAPSID>_%'" chrg -o online -s "Name like <PREFIX>_<SAPSID>_%'" chrg -o offline -s "Name like <PREFIX>_% " sr_primary_rg group start on node1 sr_secondary_rg group start on node2. Primary and secondary groups stop. sr_primary_rg group start on node1. sr_secondary_rg group start on node2. All groups stop. 98 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

115 Table 22. Planned Outages (continued) Scenario Action Command Expected result Maintenance Precondition: sr_primary_rg group is online on node1 sr_secondary_rg group is online on node2 Moe all resources away from node1 to apply operating system or hardware maintenance. Stop and restart secondary hdb instance to apply SAP Maintenance (code or profile changes). Moe primary hdb instance to apply SAP maintenance (code or profile changes). samctrl -u a node1 sr_primary_rg group stop on node1. Apply maintenance, restart, and so on. samctrl -u d node1 rgreq -o stop <PREFIX>_<SAPSID>_ <INSTANCE_NAME_HDB>_ sr_secondary_rg rgreq -o cancel <PREFIX>_<SAPSID>_ <INSTANCE_NAME_HDB>_ sr_secondary_rg rgreq -o moe <PREFIX>_<SAPSID>_ <INSTANCE_NAME_HDB>_ sr_primary_rg sr_primary_rg group start on node2. sr_secondary_rg group gets sacrificed. sr_secondary_rg group start on node1. Secondary hdb instance groups stop. Secondary hdb instance groups start on node1. Primary hdb instance group stops on node2 and restarts on node1. Secondary hdb instance on node1 stops after some seconds and is restarted on node2. Table 23. Unplanned outages Scenario Simulation action/command Expected result Precondition: sr_primary_rg group is online on node1 sr_secondary_rg group is online on node2 To simulate a software failure, create a script by using the name killscript. Add the following content: kill $1 `ps -ef grep $2 grep - grep awk {print $2} ` Failure of the primary hdb instance. Failure of the secondary hdb instance. Failure of the node where primary hdb instance is running. node1: killscript -9 hdb.sap<sapsid> node1: killscript -9 hdb.sap<sapsid> node2: reboot -fn Primary hdb instance group stops and restarts on node2. Secondary hdb instance group stops and restarts on node1. Secondary hdb instance group stops and restarts on node1. Primary hdb instance groups are started on node1. Secondary hdb instance on node1 stops after some seconds and is restarted on node2 as soon as node2 is aailable in the cluster again. Chapter 2. SAP HANA System Replication high aailability policy 99

116 Table 23. Unplanned outages (continued) Scenario Simulation action/command Expected result Failure of the node where secondary hdb instance is running. node2: reboot -fn Node2 restarts and secondary hdb instance is restarted on node2 as soon as node2 is aailable in the cluster again. Note: In any case, after failed oer to the other node, the HANA clients reconnect to the SAP HANA primary instance and run any task. 100 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

117 Chapter 3. NFS high aailability policy You can define high aailability policies for your NFS serer. The topics in this section describe the process. The Network File System (NFS) is an application to access files exported by an NFS serer to an NFS client as if they existed locally. System Automation can automate a failoer from one NFS serer to another NFS serer. The following must be automated to make an NFS serer highly aailable: NFS serer processes Virtual IP address used to connect to the NFS serer by remote clients. Shared disk for the data to be exported by the NFS serer. Shared disk for the NFS serer specific configuration files, located in the following directory: Linux: /ar/lib/nfs AIX: /etc and /ar/statmon These shared disk(s) must be accessible from all the nodes that potentially host the NFS serer in the cluster. These parts must be specified as automated resources in System Automation. You can find an oeriew on the parts that belong to the policy in Configuring and actiating the NFS serer high aailability policy on page 110. The figure below shows the basic application parts inoled in running an NFS serer: Copyright IBM Corp. 2014,

118 Figure 17. NFS serer parts An NFS serer runs on node-1 in a cluster. It listens to an IP address and a port for requests from NFS clients and exports data to those clients in NFS format. If Node-1 breaks down, operations can be restored by starting the NFS serer on Node-2. It must listen to the same IP address to sere the clients without any interruption. Shared data that was accessible for NFS clients exclusiely from Node-1 must now be exclusiely aailable from Node-2. Planning the NFS serer automation Before you implement NFS serer automation, you must fulfill specific prerequisites and infrastructure requirements. Prerequisites Virtual IP address For each irtual IP address that is defined in the high aailability policy, an equialency of network interfaces will be defined. Only network interfaces with the same network interface name can be part of the equialency. Ensure that the network interfaces you want to use hae the same name on each system. Infrastructure requirements To allow an NFS serer to failoer between different systems the following requirements against the system infrastructure hae to be fulfilled. At least one shared disk is required for the NFS serer high aailability configuration One or more disks contain the data that is exported by the NFS serer. They contain configuration files that the NFS serer requires to run properly and behae identically on all systems. 102 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

119 On a Linux machine the NFS serer uses files located in /ar/lib/nfs to store information about any NFS clients which hae mounted a file system that is exported by this NFS serer and information about file locks. On AIX this information is contained in the files /etc/xtab, /etc/exports, /etc/rmtab and the directory /ar/statmon. This information must persist after a node failoer to the NFS serer, otherwise the NFS clients lose their connections to the NFS serer. The NFS client information is stored in a small file system on a shared disk to keep this information in sync on all nodes. These disk(s) must be accessible by all nodes that are allowed to host the NFS serer, for example if the nodes are connected to a storage deice. Each shared disk has a unique deice name and number. The unique deice name and number must be the same on all nodes. Depending on your operating system, these requirements are: Linux: To transparently fail oer the NFS serer from one host to another on a Linux machine, the shared disk(s) must be connected to each serer with the same unique major and minor number. System Automation for Multiplatforms can only identify the shared disk if all nodes identify the shared disk with the same unique number. The shared disk must hae the same deice name and number on all nodes, for example /de/sdc1. You can determine the major and minor number as follows: #cd /de #ls l sd* The last command will return an output like this <systemname>:/de # ls -l sd* brw-rw root disk 8, :25 sda brw-rw root disk 8, :25 sda1 brw-rw root disk 8, :25 sda2 brw-rw root disk 8, :25 sda3 brw-rw root disk 8, :25 sda4 For sda, the major number is 8 and the minor number is 0. For each file system that resides on such a shared disk, a mount point must be defined within /etc/fstab. For each mount point, an IBM.AgFileSystem resource must exist, either harested by the StorageRM resource manager or user-defined. It is recommended to specify a label for the file system, because this label is taken as resource name for harested IBM.AgFileSystem resources. For more information about the StorageRM, see System Automation for Multiplatforms Administrator's and User's Guide. AIX: On an AIX machine the olume group MAJOR NUMBER must be identical to the olume group containing the shared data on all of the nodes. For details about the MAJOR NUMBER, see the lsg command man pages. Make sure the setup is done accordingly and keep in mind that this is also important for later changes of the configuration of the serers. This applies for eery shared disk hosting data to be exported by the NFS serer. NFS ersion 3 and 4 only are supported for the NFS high aailability policy NFS ersion 4 authentication using Kerberos is not supported. A single node can run only one NFS serer If you want to run consolidation projects, consolidate the exports of seeral NFS serers to one NFS serer instead of placing seeral NFS serers on a single machine. If there is more than one NFS serer resource within a Chapter 3. NFS high aailability policy 103

120 System Automation cluster, then these resources must hae an AntiCollocated relationship to ensure that these NFS serers are neer started on the same node at a time. Installing and setting up the NFS serer for automation Installing and setting up the NFS serer for automation is a two step process. First, you must install the NFS serer software and then configure the indiidual NFS serer components for automation. The NFS serer software is deliered as part of the operating system. Make sure that all required NFS serer packages are installed on all of the systems where you want to automate the NFS serer. For information about configuring and actiating the NFS serer high aailability policy, see Chapter 5, Using the wizard to configure and actiate the policy, on page 141. Configuring the NFS serer components To automate an NFS serer, you must configure the: NFS serer processes on page 105 Configuration data required to manage the connection between the NFS serer and clients: Using a shared disk for configuration data on page 106 Data that will be exported to NFS clients: Using a shared disk for exported data on page 108 Configuring file systems within the same olume group on AIX on page 109 NFS serer irtual IP address on page 109 Figure 18 on page 105 shows the components you must configure in order to automate an NFS serer. 104 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

121 Figure 18. Components to be configured when automating an NFS serer As shown in Figure 18, shared disks are required for that configuration data that is required to manage the: Connection between the NFS serer and clients. Data to be exported to NFS clients. NFS serer processes NFS serer processes are a part of the NFS serer high aailability policy that are required to get automated. Linux systems NFS serer daemons are controlled by an entry in the /etc/init.d or /etc/rc.conf to be started after booting the host. To automate the NFS serer, System Automation must be the only one in control of starting and stopping the NFS serer. Therefore, remoe the respectie references to the daemons from /etc/init.d or /etc/rc.conf: SuSE distribution: Use the runleel editor within yast. RedHat distribution: Use the serice command. This autostart disablement of NFS daemons must be performed on each node that will host the high aailability NFS serer instance. Chapter 3. NFS high aailability policy 105

122 For the NFS serer processes, the NFS serer high aailability policy uses a control script in an IBM.Application resource to start, stop, and monitor the NFS serer processes. This script executes the following existing NFS serer scripts: 1. Start /etc/init.d/nfslock. It will only be executed if it exists. 2. Start /etc/init.d/nfsserer for SuSE distributions and /etc/init.d/nfs for RedHat distributions. For NFS ersion 4, it will also be ensured that the idmapd daemon is started and stopped, and the pipefs file system is mounted and unmounted. The control script creates a modified ersion of the file /etc/init.d/nfslock, which is used to start and stop the rpc.statd. The original ersion will be saed under /etc/init.d/nfslock.sa_linux.org.sae. The only modification performed is to add to the start of rpc.statd the option n followed by the host name for the NFS serer IP address. This modification is performed on start-up of the NFS serer resource and will be remoed when the NFS serer is stopped, where the original file will be copied back. Note: This works only if the host name for the NFS serer is found in the DNS serer or in /etc/hosts, otherwise the script is not able to determine the host name and the rpc.statd can't be started correctly. This is not a concern if an IP address is used rather than a host name. AIX systems The NFS serer sub systems are controlled by the System Resource Controller (SRC), and the start-up behaior can be adjusted using smit(ty). To automate the NFS serer, System Automation must be the only one in control of starting and stopping the NFS serer. Use smit(ty) to preent the following NFS serer sub systems from being start-up at boot time: nfsd rpc.mountd For those NFS serer processes, the NFS serer HA policy uses a script in an IBM.Application resource to start, stop, and monitor the NFS serer processes. Using a shared disk for configuration data The NFS serer relies on a number of configuration files to behae identically on each node and maintain the connection to its clients. These configuration files depend on the operating system. Linux systems Data that is required for the management of the NFS serer is normally stored locally under /ar/lib/nfs on each NFS serer node. To make an NFS serer highly aailable requires this data to be stored on a small file system, that is also located on a shared disk accessible by all the nodes potentially hosting the NFS serer. The following steps must be performed to put the data from /ar/lib/nfs on a file system on a shared disk. Perform the following steps on one node only: 1. Create a partition of about 10 MB on a shared disk using the appropriate partitioning tool for your platform, for example fdisk for Linux on xseries. 2. Format the disk with the file system type of your choice, for example ext Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

123 3. Perform this step on eery node: Create the mount point for this file system on eery node, for example /arlibnfs. #mkdir /arlibnfs 4. Perform the following step on one node only: Mount the newly created file system on the node, copy all files from /ar/lib/nfs to /arlibnfs, and unmount the /arlibnfs file system. #mount -t ext3 /arlibnfs #cp /ar/lib/nfs/* /arlibnfs #umount /arlibnfs 5. Perform this step on eery node: Change to the /ar/lib directory and moe the nfs sub directory to nfs.original for example. Create a link to the /arlibnfs directory. #cd /ar/lib #m nfs nfs.original #ln s /arlibnfs nfs System Automation for Multiplatforms does not keep the configurations of the exported directories for the NFS serer in sync on all nodes in the domain where the NFS serer can run. The configuration of the exported directories is stored in the file /etc/exports. To ensure that this file stays in sync between all nodes that host the NFS serer, there are two options. Keep /etc/exports in sync by copying it to each node after a change. Store the /etc/exports file also in the file system on the shared disk for the configuration data. This requires the creation of a link from the /etc/exports file to the file in on the shared disk, similar as for the /ar/lib/nfs directory as described in 3. Note: When creating file systems on the shared disk, specify mount option mount=false to preent the file system from being mounted during system start. AIX systems Data that is required for the management of the NFS serer is stored locally in the directory /etc and /ar/statmon on each NFS serer node. To make an NFS serer highly aailable this data has to be stored on a small file system, that is also located on a shared disk accessible by all the nodes potentially hosting the NFS serer. The following steps must be performed to put the data from /etc and /ar/statmon on a file system on a shared disk. Perform the following steps on only one node: 1. Create a file system of about 10 MB on a shared disk. 2. Create the mount point for this file system, for example /nfsctrl # mkdir /nfsctrl 3. Mount the newly created file system on one node. 4. Copy the files /etc/xtab, /etc/rmtab, /ar/statmon and optionally /etc/exports to the directory /nfsctrl. 5. Perform this step on eery node: Change to the /etc directory and create backups of the NFS controlling files by renaming them to for example *.original and create links to the files in the /nfsctrl directory, enter: # cd /etc # m xtab xtab.original # m rmtab rmtab.original # ln s /nfsctrl/xtab xtab Chapter 3. NFS high aailability policy 107

124 # ln s /nfsctrl/rmtab rmtab # cd /ar # m statmon statmon.original # ln -s /nfsctrl/statmon statmon If the NFS serer was not started at least once, the files rmtab and xtab do not exist yet. Ensure that the copied files hae the same access rights, the same owner, and belong to the same group as the source files. Make sure that the symbolic links hae the same user ID and group settings as the source files using the chown -h command to change the link. System Automation does not keep the configurations of the exported directories for the NFS serer in sync on the different nodes in the domain where the NFS serer can run. The configuration of the exported directories is stored in the file /etc/exports. To ensure that this file stays in sync between all nodes that host the NFS serer, there are two options. Keep /etc/exports in sync by copying it to each node after a change. Store the /etc/exports file also in the file system on the shared disk for the configuration data. This requires the creation of a link from the /etc/exports file to the file in on the shared disk, similar as for the /nfsctrl directory as described in 5 on page 107 Note: When creating mount points, specify mount option noauto to preent the file system from being mounted during system start. In the smitty, command, answer No to the question Mount AUTOMATICALLY at system restart? For NFS V4, there is an additional file that contains the local NFS domain of the system /etc/nfs/local_domain. You either need to ensure that the local NFS domain is configured on all nodes hosting the NFS serer, or you need to moe the /etc/nfs/local_domain file to the shared disk and create a symbolic link on each node as it is described aboe for the files xtab and rmtab. Using a shared disk for exported data Data that is exported to clients is defined in the /etc/exports file. This data needs to be accessible from each node where the NFS serer potentially runs, therefore these data must be on shared disks. For each file system on a shared disk, a mount point must be defined, for example on AIX in the file /etc/filesystems. For each mount point, an IBM.AgFileSystem resource must exist, either harested by the StorageRM resource manager or user-defined. For more information about the StorageRM, see System Automation for MultiplatformsAdministrator's and User's Guide. Ensure that only file systems on shared disks are listed in /etc/exports. Note: 1. If a shared disk configuration is changed, the StorageRM might not immediately remap these changes into the harested storage resource information. For example, attaching a new deice to use as a shared disk or adding and changing mount points. Run the command refrsrc IBM.Disk or wait at least the configured harest interal of IBM.Disk. The HarestInteral is an attribute of IBM.Disk. The default alue is 1800 seconds. 2. When mount points are created, specify mount option noauto or Mount=false to preent that the file system is mounted during system start. 108 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

125 Configuring file systems within the same olume group on AIX On AIX, file systems that are contained in the same olume group must be mounted sequentially to ensure a successful start when controlled by System Automation for Multiplatforms. Configure the NFS high aailability policy as follows for those file systems: Specify all file systems that are contained in the same olume group as one row for parameter #12. This adds all those file systems to one resource group. Specify startafter/stopafter relationships between these file systems within parameter #14. Define a meaningful sequence of startafter/stopafter relationships. For example, your system has a olume group nfsg. Onnfsg, there are three defined file systems with three different mountpoints: Filesystem 1 with mountpoint /mnt/nfs1 Filesystem 2 with mountpoint /mnt/nfs2 Filesystem 3 with mountpoint /mnt/nfs3 In this example, you must specify: The file systems as one row in parameter #12 of the wizard. Two startafter/stopafter relationships for parameter #14 (for example, between Filesystem 1 and Filesystem 2, and between Filesystem 2 and Filesystem 3). NFS serer irtual IP address A irtual IP address is required to connect NFS clients to an NFS serer by mounting an NFS file system from the NFS serer using the irtual IP address. NFS clients connect to an NFS serer by mounting an NFS file system from the NFS serer, which is determined by the host name or the IP address of the host. When the NFS serer resource is restarted on a different node, then the irtual IP address (represented by class IBM.SericeIP) chooses a network adapter on the other node based on its attributes IPAddress and NetMask, so that the client always connects to the same IP address. Example node-1 network adapter eth netmask network adapter eth netmask node-2 network adapter eth netmask network adapter eth netmask In the aboe configuration, suppose that you only want NFS clients to access the nodes through IP addresses of and Then you must use eth0 of node-1 and node-2 in the IBM.Equialency of IBM.NetworkInterface. The IBM.SericeIP that depends on this equialency can hae any free IP address in the subnet. Check with your network administrator for an IP address that is aailable, for example : nfsserer-ip attributes: IPAddress NetMask NodeNameList {"node-1","node-2"} Chapter 3. NFS high aailability policy 109

126 System Automation for Multiplatforms knows that IBM.SericeIP depends on network interfaces eth0 of node-1 and node-2, chooses a network adapter on the node on which the NFS serer runs, and passes it to IBM.SericeIP, which creates an IP alias on that network adapter. Note: For the setup of the high aailability policy, you should: Gather the network adapters of the nodes, for example using ifconfig and select the ones which should be used by NFS clients to access data through the NFS serer. Get a free IP address and the corresponding netmask from your network administrator. Configuring and actiating the NFS serer high aailability policy System Automation for Multiplatforms proides a predefined NFS serer high aailability policy to automate your NFS serer and keep it highly aailable. Use the sampolicy wizard to tailor the policy to your specific NFS serer configuration and finally actiate this policy. The policy manages all NFS serer components as described in Configuring the NFS serer components on page 104. NFS serer high aailability policy System Automation for Multiplatforms proides a predefined NFS serer high aailability policy that helps you to automate your NFS serer. The NFS serer high aailability policy contains two types of top-leel groups. nfsserer-rg: Contains NFS serer processes, NFS serer configuration data, and irtual IP address. This group exists only once in an NFS serer high aailability policy. filesys-data: Contains the file system that is exported to NFS clients. The group has one or more occurrences in an NFS serer high aailability policy. The separation of the file systems from the NFS serer itself and the separation into more than one resource group preents an outage of the NFS serer in case of an unrecoerable failure of one indiidual file system. 110 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

127 Figure 19. NFS serer high aailability policy The table lists all resources contained in the policy: Table 24. NFS serer parts which are automated by the NFS serer high aailability policy Name Resource name Description NFS serer group 1 IBM.ResourceGroup/ <PREFIX>-rg Group for all releant NFS serer parts. NFS serer processes 2 NFS serer configuration data 3 Virtual IP address 4 IBM.Application /<PREFIX>-serer IBM.AgFileSystem / RSCT-harested name IBM.SericeIP <PREFIX>-ip-1 NFS serer process, start/stopped/monitored ia script. Filesystem containing all NFS serer configuration data. Started, stopped, and monitored using StorageRM. Virtual IP address that defines an IP alias. Started, stopped, and monitored using IBM.GblResRM. Chapter 3. NFS high aailability policy 111

128 Table 24. NFS serer parts which are automated by the NFS serer high aailability policy (continued) Name Resource name Description NFS exported data group 5 NFS exported data container resource 6 NFS exported data export resource 7 Network equialency (not shown in Figure 19 on page 111) Network interfaces (not shown in Figure 19 on page 111) IBM.ResourceGroup/ <PREFIX>-data<NUMBER>filesys-rg IBM.AgFileSystem/ customer defined name IBM.Equialency / <PREFIX>-nieq-1 IBM.NetworkInterface / RSCT harested name Group containing the data to be exported to clients. Multiple instances possible. File system containing the data to be exported to clients. Started, stopped, and monitored using StorageRM. Multiple instances within a NFS exported data group possible One or more resources to control the export of the file systems. One instance per NFS exported data container resource. Defines which network adapters will be used to bind the irtual IP address to. Started, stopped, and monitored using IBM.GblResRM. Network adapters to bind the irtual IP address to. The NFS serer processes, the NFS serer configuration data, and the irtual IP address belong to one resource group (nfsserer-rg). Your configuration might contain sets of mount points that hae to be exported together. The policy will group each set of mount points in one single resource group. The NFS serer high aailability policy contains the following relationships: Table 25. NFS serer high aailability policy relationships Relationship name Source Target Type IBM.Application/ <PREFIX>-<FILESYSNAME>export-rs <PREFIX>data<NUMBER>- filesys-rg- DependsOnnfsserer- rg 8 <PREFIX>data<NUMBER>- <FILESYSNAME>- export- DependsOn- <FILESYSNAME> 9 <PREFIX>-serer- DependsOn-nfsctrlfs 10 <PREFIX>-ip-onnieq- 1-dyn (not shown in Figure 19 on page 111) NFS exported data group NFS exported data export resource NFS serer process NFS serer irtual IP address NFS serer group NFS exported data container resource NFS serer configuration data Network interfaces dependson relationship: Can occur multiple times depending on number of NFS exported data groups. dependson dependson dependson 112 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

129 Table 25. NFS serer high aailability policy relationships (continued) Relationship name Source Target Type <PREFIX>- <FILESYSNAME_SOURCE>- stopafter- <FILESYSNAME_TARGET> on AIX only 11 NFS exported data container resource NFS exported data container resource stopafter may occur multiple times depending on number of exported data container resources within one NFS exported data group on AIX <PREFIX>-serer- DependsOn-nfsip 12 NFS serer process NFS serer irtual IP address dependson Since nfsserer-serer cannot run without nfsserer-ip and nfsserer-data-arlibnfs being aailable, and the data exported data filesys-rg cannot be exported without the NFS serer running, dependson relationships between the affected components are defined. StartAfter or StopAfter relationships are created for file systems on AIX that belong to the same group. This ensures that mounting the file system is executed in an well defined order and consecutiely. All resources of the policy are defined as floating resources, so that they can be moe between the nodes of their domain. They are configured to always run on the same node within the domain due to the collocated behaior of the defined dependson relationships. The equialency nfsserer-nieq of network interfaces is necessary to determine the network interfaces which will potentially host the floating IP address (nfsserer-ip). A depends on relationship is required between the floating IP address and the equialency. Example In this sample scenario, the following setup is automated using the NFS Serer policy: NFS serer is automated using the NFS serer high aailability policy. Its configuration data is located on shared disk hdisk1. A set of filesystems (data1-fs1, data1-fs2 and data1-fs3) is located on shared disk hdisk2. A set of filesystems (data2-fs1) is located on shared disk hdisk3. On AIX, all inoled shared disks (hdisk1,hdisk2 and hdisk3) are contained in different olume groups (g1,g2 and g3). Below is a figure of resources created for this sample scenarios: Chapter 3. NFS high aailability policy 113

130 Figure 20. NFS serer high aailability policy sample scenario The output of lssam for this setup is shown below: Online IBM.ResourceGroup:nfsserer-data1-filesys-rg Nominal=Online -. - Online IBM.AgFileSystem:fsa1 MNT=/data1/fsa1 <. <. <. - Offline IBM.AgFileSystem:fsa1:node-1 - Online IBM.AgFileSystem:fsa1:node-2 SA - Online IBM.AgFileSystem:fsa2 MNT=/data1/fsa1/fsa2 <. - - Offline IBM.AgFileSystem:fsa2:node-1 - Online IBM.AgFileSystem:fsa2:node-2 SA - Online IBM.AgFileSystem:fsa3 MNT=/data1/fsa1/fsa3 - - Offline IBM.AgFileSystem:fsa3:node-1 <. - Online IBM.AgFileSystem:fsa3:node-2 DO - Online IBM.Application:nfsserer-data1-fsa1-export-rs - - Offline IBM.Application:nfsserer-data1-fsa1-export-rs:node-1 - Online IBM.Application:nfsserer-data1-fsa1-export-rs:node-2 DO - Online IBM.Application:nfsserer-data1-fsa2-export-rs - - Offline IBM.Application:nfsserer-data1-fsa2-export-rs:node-1 - Online IBM.Application:nfsserer-data1-fsa2-export-rs:node-2 DO - Online IBM.Application:nfsserer-data1-fsa3-export-rs - - Offline IBM.Application:nfsserer-data1-fsa3-export-rs:node-1 - Online IBM.Application:nfsserer-data1-fsa3-export-rs:node-2 Online IBM.ResourceGroup:nfsserer-data2-filesys-rg Nominal=Online -. - Online IBM.AgFileSystem:fsb1 MNT=/data2/fsb1 <. - Offline IBM.AgFileSystem:fsb1:node-1 - Online IBM.AgFileSystem:fsb1:node-2 DO - Online IBM.Application:nfsserer-data2-fsb1-export-rs - - Offline IBM.Application:nfsserer-data2-fsb1-export-rs:node-1 - Online IBM.Application:nfsserer-data2-fsb1-export-rs:node-2 DO DO Online IBM.ResourceGroup:nfsserer-rg Nominal=Online < < - Online IBM.AgFileSystem:arlibnfs MNT=/arlibnfs <. - Offline IBM.AgFileSystem:arlibnfs:node-1 - Online IBM.AgFileSystem:arlibnfs:node-2 DO - Online IBM.Application:nfsserer-serer Offline IBM.Application:nfsserer-serer:node-1 - Online IBM.Application:nfsserer-serer:node-2 DO 114 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

131 - Online IBM.SericeIP:nfsserer-ip-1 IP= < - Offline IBM.SericeIP:nfsserer-ip-1:node-1 - Online IBM.SericeIP:nfsserer-ip-1:node-2 NFS serer policy parameters The NFS serer high aailability policy requires a number of parameters to be specified in order to tailor the NFS serer high aailability policy for your specific enironment, like the file system to be exported. The following parameter listings consist of a parameter description, a alue type, and a default alue. The parameters ary by the operating system (AIX, Linux), where the NFS serer is installed. Policy parameters for AIX Table 26. NFS serer high aailability policy parameters (AIX) # Parameter description 1 Enter the name of your SA MP domain. Proide the name of an existing SA MP domain. The SA MP domain will host the NFS resources that will be configured with this template. 2 Enter your desired prefix for all NFS serer resources. This prefix will be used as a prefix for all SA MP resources that coer the NFS serer. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. 3 Enter the nodes where you want to automate the NFS serer. These nodes must be listed when you enter the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. NFS serer resources will be created for each of the specified nodes. 4 Do you want to monitor the NFS daemon nfsrgyd? The nfsrgyd daemon only exists for NFS 4 serer on AIX. The nfsrgyd daemon proides a name translation serice for NFS serers and clients. It only needs to run if the NFS serer is setup for NFS 4 on AIX operating systems. 5 Select the IP ersion used in your cluster. Depending on the IP ersion you must specify either NetMask for IP4, or NetPrefix for IP6. 6 This parameter will be ignored unless the following condition is fulfilled: Parameter # 5 has the alue IP4. Value Type Value Value type: String Value type: String nfsserer List of alues, alue type for each alue: Hostname or IP ersion 4 address Value type: {yes no} no One of these alues: IP4 IP6 IP4 Value type: IP ersion 4 address Specify a irtual IP4 address for the NFS serer instance. This IP4 address will be used as a irtual IP address for the floating NFS serer instance. 7 This parameter will be ignored unless the following condition is fulfilled: Parameter # 5 has the alue IP6. Value type: IP ersion 6 address Specify a irtual IP6 address for the NFS serer instance. This IP6 address will be used as a irtual IP address for the floating NFS serer instance. Chapter 3. NFS high aailability policy 115

132 Table 26. NFS serer high aailability policy parameters (AIX) (continued) # Parameter description 8 This parameter will be ignored unless the following condition is fulfilled: Parameter # 5 has the alue IP4. Enter the netmask for the subnet of the irtual NFS serer IP address. Enter the netmask for the subnet of the irtual NFS serer IP address. An example for a netmask is This parameter will be ignored unless the following condition is fulfilled: Parameter # 5 has the alue IP6. Enter the NetPrefix for the irtual NFS serer IP address. Enter the NetPrefix for the irtual NFS serer IP address. 10 Enter the aailable network interface for the NFS Serer. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system). The aailable network interface specifies to which network interface the irtual NFS serer IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the NFS serer will be automated. 11 Specify the name of the IBM.AgFileSystem resource that represents the mount point of the NFS serer configuration data directory. The following IBM.AgFileSystem is aailable in your domain ("Name" "SysMountPoint"): (remaining part of description is harested from running system) Value Type Value Value type: IP ersion 4 address Value type: numeric. Minimum alue: 0, maximum alue: 128 Value type: String Value type: String SA MP will automatically mount the directory with NFS serer configuration data prior to starting the NFS serer processes, and will automatically unmount the directory after stopping the NFS serer processes. You can determine the name of the IBM.AgFileSystem by issuing the command: lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint This command will return a list of IBM.AgFileSystem resources. Use the name of the resource that represents the mount point of the NFS serer configuration data directory. 116 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

133 Table 26. NFS serer high aailability policy parameters (AIX) (continued) # Parameter description 12 Specify the names of the IBM.AgFileSystem resources that represent the mount points of the directories to be exported. The IBM.AgFileSystem resources can be combined in multiple IBM.ResourceGroups. For each group, the IBM.AgFileSystem resource names must be specified separately. The followingibm.agfilesystem is aailable in your domain ("Name" "SysMountPoint"): the remaining part of the description is harested from the running system. The alues are specified in table form: Each table row (prompted as "alue") consists of ariable number of columns (each column prompted as "sub-alue"). The ariable number of columns is prompted for each row separately. Each table row will result in a separate IBM.ResourceGroup. Each column within a row represents a single IBM.AgFileSystem resource name, that will be added to one IBM.ResourceGroup. SA MP will automatically mount and export each directory if the corresponding resource group is started, and will automatically unmount and unexport the directory if the corresponding resource group is stopped. You can determine the name of the IBM.AgFileSystem by issuing the command: lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint This command will return a list of IBM.AgFileSystem resources. Use the name of the resources that represent the mount points of the exported file system. Example: IBM.ResourceGroup:data1-filesys-rg - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:data2-filesys-rg - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Number of columns for alue 1: 3 Value 1, sub-alue 1: "FS1" Value 1, sub-alue 2: "FS2" Value 1, sub-alue 3: "FS3" Number of columns for alue 2: 2 Value 2, sub-alue 1: "FS4" Value 2, sub-alue 2: "FS5" Number of columns for alue 3: Just press ENTER to complete the input. This parameter must hae the same number of alues as the following parameters: Parameter # 13 Value Type Value List of alues, each alue consisting of sub-alues, alue type for each sub-alue: String Chapter 3. NFS high aailability policy 117

134 Table 26. NFS serer high aailability policy parameters (AIX) (continued) # Parameter description 13 Specify the mountpoints of the directories to be exported. These mountpoints must be specified in the same structure as you hae specified the IBM.AgFileSystem names in the preious question. Specify the mountpoints of the directories to be exported. For each directory, only one export can be configured. The alues are specified in table form: Each table row (prompted as "alue") consists of ariable number of columns (each column prompted as "sub-alue"). The ariable number of columns is prompted for each row separately. Each table row belongs to an IBM.ResourceGroup specified in the preious question. Each column within a row represents a mount point name. Value Type Value List of alues, each alue consisting of sub-alues, alue type for each sub-alue: String Example: IBM.ResourceGroup:data1-filesys-rg - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:data2-filesys-rg - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Number of columns for alue 1: 3 Value 1, sub-alue 1: "/mnt/test_a" Value 1, sub-alue 2: "/mnt/test_a/one" Value 1, sub-alue 3: "/mnt/test_a/two" Number of columns for alue 2: 2 Value 2, sub-alue 1: "/mnt/test_b" Value 2, sub-alue 2: "/mnt/test_b/one" Number of columns for alue 3: Just press ENTER to complete the input. This parameter must hae the same number of alues as the following parameters: Parameter # Are there any nested mountpoints between mounted file systems within one file system set? Nested mountpoints are mountpoints where one mountpoint contains another mountpoint, i.e. /mnt/test/one is a nested mountpoint to /mnt/test. Value type: {yes no} no 118 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

135 Table 26. NFS serer high aailability policy parameters (AIX) (continued) # Parameter description 14.1 Optional; a alue for this parameter is only required if parameter # 14 has the alue "yes". Specify the nested mountpoints that are contained in one file system set. For each nesting leel, sub-alue number 1 is the nested mountpoint, sub-alue number 2 is the mountpoint one leel aboe. You need to specify the names of the IBM.AgFileSystem resources for each mountpoint. Value Type Value List of alues, each alue consisting of the same number of sub-alues, alue type for each sub-alue: String Specify the names of the IBM.AgFileSystem of the nested mountpoints that are contained in one file system set. The alues are specified in table form. Each table row (prompted as "alue") consists of two columns (each column prompted as "sub-alue"). The first column alue is the nested mountpoint and the second column alue is the mountpoint at the higher directory leel. Each row will be used to create a StartAfter relationship from first column alue (source) to second column alue (target). Example: IBM.ResourceGroup:Group1 - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:Group2 - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Value 1, sub-alue 1: "FS2" Value 1, sub-alue 2: "FS1" Value 2, sub-alue 1: "FS3" Value 2, sub-alue 2: "FS1" Value 3, sub-alue 1: "FS5" Value 3, sub-alue 2: "FS4" Value 4, sub-alue 1: just press Enter to complete input 15 Specify the desired state of your NFS serer resources. If you specify Online, the NFS serer resources will be started on policy actiation, if not already started. If you specify Offline, the NFS serer resources will not be started on policy actiation, but stopped if they are online. One of the following alues: Online Offline Offline Policy parameters for Linux Table 27. NFS serer high aailability policy parameters (Linux) # Parameter description 1 Enter the name of your SA MP domain. Proide the name of an existing SA MP domain. The SA MP domain will host the NFS resources that will be configured with this template. 2 Enter your desired prefix for all NFS serer resources. This prefix will be used as a prefix for all SA MP resources that coer the NFS serer. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. Value Type Value Value type: String Value type: String nfsserer Chapter 3. NFS high aailability policy 119

136 Table 27. NFS serer high aailability policy parameters (Linux) (continued) # Parameter description 3 Enter the nodes where you want to automate the NFS serer. These nodes must be listed when you enter the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. NFS serer resources will be created for each of the specified nodes Value Type Value List of alues, alue type for each alue: Hostname or IP ersion 4 address (plus additional alue checking) 4 Select the IP ersion used in your cluster. Depending on the IP ersion you must specify either NetMask for IP4, or NetPrefix for IP6. 5 This parameter will be ignored unless the following condition is fulfilled: Parameter # 4 has the alue IP4. One of these alues: IP4 IP6 IP4 Value type: IP ersion 4 address Specify a irtual IP4 address for the NFS serer instance. This IP4 address will be used as a irtual IP address for the floating NFS serer instance. 6 This parameter will be ignored unless the following condition is fulfilled: Parameter # 4 has the alue IP6. Value type: IP ersion 6 address Specify a irtual IP6 address for the NFS serer instance. This IP6 address will be used as a irtual IP address for the floating NFS serer instance. 7 This parameter will be ignored unless the following condition is fulfilled: Parameter # 4 has the alue IP4. Enter the netmask for the subnet of the irtual NFS serer IP address. Enter the netmask for the subnet of the irtual NFS serer IP address. An example for a netmask is This parameter will be ignored unless the following condition is fulfilled: Parameter # 4 has the alue IP6. Enter the NetPrefix for the irtual NFS serer IP address. Enter the NetPrefix for the irtual NFS serer IP address. 9 Enter the aailable network interface for the NFS Serer. The following network interfaces are aailable on your local system: (remaining part of description is harested from running system) Value type: IP ersion 4 address Value type: numeric. Minimum alue: 0, maximum alue: 128 Value type: String (plus additional alue checking) The aailable network interface specifies to which network interface the irtual NFS serer IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the NFS serer will be automated. 120 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

137 Table 27. NFS serer high aailability policy parameters (Linux) (continued) # Parameter description 10 Specify the name of the IBM.AgFileSystem resource that represents the mount point of the NFS serer configuration data directory. The following IBM.AgFileSystems are aailable in your domain ("Name" "SysMountPoint"): (remaining part of description is harested from running system) Value Type Value Value type: String (plus additional alue checking) SA MP will automatically mount the directory with NFS serer configuration data prior to starting the NFS serer processes, and will automatically unmount the directory after stopping the NFS serer processes. You can determine the name of the IBM.AgFileSystem by issuing the command 'lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint'. This command will return a list of IBM.AgFileSystem resources. Use the name of the resource that represents the mount point of the NFS serer configuration data directory. Chapter 3. NFS high aailability policy 121

138 Table 27. NFS serer high aailability policy parameters (Linux) (continued) # Parameter description 11 Specify the names of the IBM.AgFileSystem resources that represent the mount points of the directories to be exported. The IBM.AgFileSystem resources can be combined in multiple IBM.ResourceGroups. For each group, the IBM.AgFileSystem resource names hae to be specified separately. The following IBM.AgFileSystems are aailable in your domain ("Name" "SysMountPoint"): the remaining part of description is harested from the running system. Value Type Value List of alues, each alue consisting of a ariable number of sub-alues, alue type for each sub-alue: String (plus additional alue checking) The alues are specified in table form: Each table row (prompted as "alue") consists of ariable number of columns (each column prompted as "sub-alue"). The ariable number of columns is prompted for each row separately. Each table row will result in a separate IBM.ResourceGroups. Each column within a row represents a single IBM.AgFileSystem resource name, that will be added to one IBM.ResourceGroups. SA MP will automatically mount and export each directory if the corresponding resource group is started, and will automatically unmount and unexport the directory if the corresponding resource group is stopped. You can determine the name of the IBM.AgFileSystem by issuing the command: lsrsrc -s "ResourceType==1" IBM.AgFileSystem Name SysMountPoint. This command will return a list of IBM.AgFileSystem resources. Use the name of the resources that represent the mount points of the exported file systems. Example: IBM.ResourceGroup:data1-filesys-rg - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:data2-filesys-rg - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Number of columns for alue 1: 3 Value 1, sub-alue 1: "FS1" Value 1, sub-alue 2: "FS2" Value 1, sub-alue 3: "FS3" Number of columns for alue 2: 2 Value 2, sub-alue 1: "FS4" Value 2, sub-alue 2: "FS5" Number of columns for alue 3: Just press ENTER to complete the input. This parameter must hae the same number of alues as the following parameters: Parameter # Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

139 Table 27. NFS serer high aailability policy parameters (Linux) (continued) # Parameter description 12 Specify the mount points of the directories to be exported. These mount points must be specified in the same structure as you hae specified the IBM.AgFileSystem names in the preious question. Specify the mount points of the directories to be exported. For each directory, only one export can be configured. The alues are specified in table form. Each table row (prompted as "alue") consists of ariable number of columns (each column prompted as "sub-alue"). The ariable number of columns is prompted for each row separately. Each table row belongs to an IBM.ResourceGroup specified in the preious question. Each column within a row represents a mount point name. Value Type Value List of alues, each alue consisting of a ariable number of sub-alues, alue type for each sub-alue: String (plus additional alue checking) Example: IBM.ResourceGroup:data1-filesys-rg - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:data2-filesys-rg - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Number of columns for alue 1: 3 Value 1, sub-alue 1: "/mnt/test_a" Value 1, sub-alue 2: "/mnt/test_a/one" Value 1, sub-alue 3: "/mnt/test_a/two" Number of columns for alue 2: 2 Value 2, sub-alue 1: "/mnt/test_b" Value 2, sub-alue 2: "/mnt/test_b/one" Number of columns for alue 3: Just press ENTER to complete the input. This parameter must hae the same number of alues as the following parameters: Parameter # Are you running with NFS ersion 4? If the NFS serer is running with NFS4, a separate daemon process, called idmapd has to be started, stopped and monitored. Specify 'yes' if you are running with NFS4. 14 This parameter will be ignored unless all following conditions are fulfilled: Parameter # 13 has the alue "yes" Value type: {yes no} Value type: String /ar/lib/nfs/rpc_pipefs Specify the path of the RPC pipefs directory. The RPC pipefs is a required directory of the rpc.idmapd daemon for NFS4. The idmapd is the NFS4 ID to name mapping daemon. The default path for the pipefs is /ar/lib/nfs/rpc_pipefs. 15 Are there any nested mount points between mounted file systems within one file system set? Nested mount points are mount points where one mount point contains another mount point, that is, /mnt/test/ one is a nested mount point to /mnt/test. Value type: {yes no} no Chapter 3. NFS high aailability policy 123

140 Table 27. NFS serer high aailability policy parameters (Linux) (continued) # Parameter description 15.1 Optional; a alue for this parameter is only required if parameter # 15 has the alue "yes". Specify the nested mount points that are contained in one file system set. For each nesting leel, sub-alue number 1 is the nested mount point, sub-alue number 2 is the mount point one leel aboe. You need to specify the names of the IBM.AgFileSystem resources for each mount point. Value Type Value List of alues, each alue consisting of the same number of sub-alues, alue type for each sub-alue: String Specify the names of the IBM.AgFileSystems of the nested mount points that are contained in one file system set. The alues are specified in table form. Each table row (prompted as "alue") consists of two columns (each column prompted as "sub-alue"). The first column alue is the nested mount point and the second column alue is the mount point at the higher directory leel. Each row will be used to create a StartAfter relationship from first column alue (source) to second column alue (target). Example: IBM.ResourceGroup:Group1 - IBM.AgFileSystem:FS1 MNT=/mnt/test_a - IBM.AgFileSystem:FS2 MNT=/mnt/test_a/one - IBM.AgFileSystem:FS3 MNT=/mnt/test_a/two IBM.ResourceGroup:Group2 - IBM.AgFileSystem:FS4 MNT=/mnt/test_b - IBM.AgFileSystem:FS5 MNT=/mnt/test_b/one Specify the alues in the following form: Value 1, sub-alue 1: "FS2" Value 1, sub-alue 2: "FS1" Value 2, sub-alue 1: "FS3" Value 2, sub-alue 2: "FS1" Value 3, sub-alue 1: "FS5" Value 3, sub-alue 2: "FS4" Value 4, sub-alue 1: just press Enter to complete input 16 Specify the desired state of your NFS serer resources. If you specify Online, the NFS serer resources will be started on policy actiation, if not already started. If you specify Offline, the NFS serer resources will not be started on policy actiation, but stopped if they are online. One of the following alues: Online Offline Offline Using the wizard to configure and actiate the NFS serer high aailability policy The NFS serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. The policy template samnfs_templatenfsserer.tmpl.xml is located in the installation directory of the NFS serer high aailability policy /usr/sbin/rsct/sapolicies/nfsserer. To configure the template, run the following command: sampolicy w /usr/sbin/rsct/sapolicies/nfsserer/samnfs_templatenfsserer.tmpl.xml 124 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

141 You must configure a policy pool before running the wizard. The wizard will then store all modifications to the policy pool. If you set your policy pool to /etc/mypolicypool, a wizard run using sampolicy -w /usr/sbin/rsct/sapolicies/nfsserer/samnfs_templatenfsserer.tmpl.xml stores the results to /etc/mypolicypool/samnfs_templatenfsserer.tmpl.xml The next time you inoke the wizard, use the file stored in the policy pool. With the example aboe, inoking the wizard for the second time would look like this: sampolicy -w /etc/mypolicypool/samnfs_templatenfsserer.tmpl.xml Using the wizard to configure and actiate the SAP Central Serices high aailability policy on page 42 Each SAP Central Serices high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Using the wizard to configure and actiate the Oracle database high aailability policy on page 138 The Oracle database serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Chapter 5, Using the wizard to configure and actiate the policy, on page 141 Use the policy setup wizard to configure and actiate your IBM Tioli System Automation for Multiplatforms policies. Verifying the NFS serer high aailability policy After you installed and configured your NFS serer, erify that your setup is correct. To erify your installation and configuration to make the NFS serer highly aailable, proceed with the following steps, using the following example setup: 1. Check if the NFS serer is ready to use. An NFS serer has been made highly aailable using the IP address: The directory to be exported is /work. Before trying to mount an exported file system from an NFS client, you need to check if the NFS serer is ready for NFS client connections and if all file systems defined in /etc/exports are really exported to the specified hosts. Applying the example setup settings, enter showmount e exportfs The output of both commands should correspond to the content of /etc/exports: #cat /etc/exports /work node-3(rw,sync) #showmount e xport list for : /work node-3 #exportfs /work node-3 If any errors occur, sole them first before you continue with the next steps. 2. Access automated NFS serer from an NFS client. Using the example aboe, check if an NFS client is able to mount the NFS file system exported from The mount point on the NFS client is be /mnt/work. From a command prompt on the NFS client, run the following command as user root: Chapter 3. NFS high aailability policy 125

142 #mount :/work /mnt/work If no errors occur, check the result using the mount command. #mount For this example, this command reports a list of all mounted file system with the following entry: :/work on /mnt/work type nfs (rw,soft,addr= ) 3. Testing NFS serer failoer: After you hae erified that your automated NFS serer works on one node, you can try a failoer. In a two node cluster with node-1 and node-2, exclude the node from automation on which the NFS serer currently runs and see if it is started on the other node. Assuming the NFS serer runs on node-2, enter: samctrl -u a node-2 This adds node-2 to the list of nodes excluded from automation. Wait until the failoer starts. Then inspect the resources in nfsserer-rg using the lssam command: Online IBM.ResourceGroup:nfsserer-rg Nominal=Online - Online IBM.AgFileSystem: nfsserer-data-arlibnfs - Online IBM.AgFileSystem:nfsserer-data-arlibnfs:node-1 - Offline IBM.AgFileSystem:nfsserer-data-arlibnfs:node-2 Node=Excluded - Online IBM.Application:nfsserer-serer - Online IBM.Application:nfsserer-serer:node-1 - Offline IBM.Application:nfsserer-serer:node-2 Node=Excluded - Online IBM.SericeIP:nfsserer-ip-1 - Online IBM.SericeIP:nfsserer-ip-1:node-1 - Offline IBM.SericeIP:nfsserer-ip-1:node-2 Node=Excluded Note: The groups hosting the exported file system will also moe to node-1. You can always inspect which nodes are excluded using the lssamctrl command to display SAMControl information: SAMControl: TimeOut = 60 RetryCount = 3 Automation = Auto ExcludedNodes = {node-2} ResourceRestartTimeOut = 5 Ensure that the NFS serer mounted on your NFS clients are still working, for example by accessing the directory of the mount.you can now include node-2 into automation again, enter: samctrl -u d node-2 The parameter d is used to delete the node from the list of excluded nodes. After the NFS serer is online on node node-1, you should be able to access and modify the NFS data of a NFS client. After haing successfully completed this test scenario using samctrl, a more adanced scenario like a node failure can be run. Before you start, ensure that the following prerequisites are met: Make sure that no node is on the list of excluded nodes. You can use the command lssamctrl to erify. If you hae only a 2-node-cluster as in the preious example be sure you hae correctly setup a tiebreaker. For more information about the tiebreaker, see System Automation for Multiplatforms Administrator's and User's Guide. If these prerequisites are satisfied you can test a failoer by either rebooting the node currently running the NFS serer or pressing the power button. The NFS serer should be failed oer to the other node, and the NFS clients are still able to connect the mounted NFS data. 126 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

143 Chapter 4. Oracle high aailability policy You can define high aailability policies for your Oracle database. The topics in this section describe the process. The high aailability concept offered by System Automation for Multiplatforms keeps an Oracle database highly aailable. Besides DB2, the Oracle database is the most frequently used database systems for SAP. There are different high aailability concepts for an Oracle database, for example Actie Data Guard and the Real Application Cluster (RAC) feature. The solution offered by System Automation for Multiplatforms is an additional high aailability solution, using the concept of placing the database files on a shared disk that is mounted to the database serer exclusiely. The following figure depicts the high aailability architecture for an Oracle database that is required for the Oracle database high aailability policy: Figure 21. High aailability architecture for an Oracle database The database control software, for example the Oracle database serer and the database listener are installed on node-1 and node-2. Both nodes are connected to a shared disk where the database is installed, but the disk is always mounted to one single node. The database listener is accessible from database clients using the irtual IP address and is waiting for requests from a database client. The listener queries the database and returns results to the database client. Copyright IBM Corp. 2014,

144 Assume that the Oracle database serer and the database listener are running on node-1. The shared disk with the database files is mounted on node-1, the irtual IP address is bound to a network interface on node-1. If node-1 fails, the shared disk is mounted to node-2, the Oracle database serer and the listener on node-2 are started and the irtual IP address is bound to a network interface on node-2. The database clients remain connected to the same irtual IP all the time. Planning the Oracle database automation and high aailability Before you automate your Oracle database with System Automation for Multiplatforms, check that the ersion of Oracle installed in your enironment is supported, and that you hae the required hardware and network infrastructure. Supported Oracle ersions The following Oracle ersions are supported for the Oracle database high aailability policy: Oracle 10g Release 2 ( ) and higher patches Oracle 11g Prerequisites For each irtual IP address that is defined in the high aailability policy, an equialency of network interfaces is defined. Only network interfaces with the same network interface name can be part of the equialency. Ensure that the network interfaces you want to use hae the same name on each system. Infrastructure requirements For an Oracle database to failoer between different systems, the following requirements for the system infrastructure hae to be fulfilled. Ensure that your operating system meets all prerequisites of the Oracle database release which you install. Refer to the Oracle database documentation for further information. At least one shared disk is required for the Oracle database high aailability configuration. One or more disks contain the data that is exported by the Oracle database. They contain configuration files that the Oracle database requires to run properly and behae identically on all systems. On a Linux machine the Oracle database uses files located in /ar/lib/nfs to store information about any Oracle database which hae mounted a file system that is exported by this Oracle database and information about file locks. On AIX this information is contained in the files /etc/xtab, /etc/exports, /etc/rmtab and the directory /ar/statmon. This information must persist after a node failoer to the Oracle database, otherwise the Oracle databases lose their connections to the Oracle database. The Oracle database information is stored in a small file system on a shared disk to keep this information in sync on all nodes. These disk(s) must be accessible by all nodes that are allowed to host the Oracle database, for example if the nodes are connected to a storage deice. Each shared disk has a unique deice name and number. The unique deice name and number must be the same on all nodes. Depending on your operating system, these requirements are: Linux To transparently fail oer the Oracle database from one host to another on a Linux machine, the shared disk(s) must be connected to each serer with the same unique major and minor number. System Automation for Multiplatforms can only identify the shared disk if all nodes identify the 128 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

145 shared disk with the same unique number. The shared disk must hae the same deice name and number on all nodes, for example /de/sdc1. You can determine the major and minor number as follows: #cd /de #ls l sd* The last command will return an output like this: <systemname>:/de # ls -l sd* brw-rw root disk 8, :25 sda brw-rw root disk 8, :25 sda1 brw-rw root disk 8, :25 sda2 brw-rw root disk 8, :25 sda3 brw-rw root disk 8, :25 sda4 For sda, the major number is 8 and the minor number is 0. AIX On an AIX machine the olume group MAJOR NUMBER must be identical to the olume group containing the shared data on all of the nodes. For details about the MAJOR NUMBER, see the lsg command man pages. Make sure your setup fulfills the MAJOR NUMBER requirements and keep in mind that this is also important for later changes of the configuration of the serers. This applies for eery shared disk hosting data to be exported by the Oracle database. Keep in mind that it is not possible to hae more than one Oracle database running on a single node. If you want to run consolidation projects, consolidate the exports of seeral Oracle databases to one Oracle database instead of placing seeral Oracle databases on a single machine. If there is more than one Oracle database resource within a System Automation for Multiplatforms cluster, then these resources must hae an AntiCollocated relationship to ensure that these Oracle databases are neer started on the same node at a time. Restrictions The Oracle database listener must not be started directly using the command tnslsnr. System Automation for Multiplatforms will not be able to detect such a running listener, because it is not registered properly with the listeners name. Installing and setting up the Oracle database Install the Oracle database, create a database on a shared disk, and then configure the indiidual Oracle database components. If you want to configure and actiate the Oracle database high aailability policy, see Configuring and actiating the Oracle database high aailability policy on page 132. Installing the Oracle database software To install a database using the shared disk approach, you need to adhere to the following installation requirements. Oracle supplies detailed and comprehensie documentation for the database installation. Carefully read the Oracle documentation for your database ersion and the follow the steps described below. Prepare each system where you want to install the Oracle database, select one system to install the database software, create the database on a shared disk and finally replicate the database software to all other systems you hae prepared. Chapter 4. Oracle high aailability policy 129

146 For all nodes On each system where you want to install the Oracle database, perform the following steps: 1. Ensure that a shared disk is aailable on each of the systems, fulfilling the requirements that are described in Planning the Oracle database automation and high aailability on page 128. This disk contains the database files. 2. Ensure that all preinstallation requirements to install the database are met. These requirements include hardware and software, examples for such requirements are sufficient disk space and memory or certain patches for an operating system. Preinstallation requirements include mandatory preinstallation tasks. These tasks include the creation of users and groups, directories, and the configuration of shell limits. In the Oracle documentation, the requirements tasks are listed in the chapters Preinstallation tasks for Oracle 10.2 and Oracle Database Preinstallation Requirements for Oracle 11. You must create the directory that contains the database files on the shared disk you designated for this purpose. For a single node Select a node where you want to install the Oracle database software and follow these steps: 1. Mount the shared disk. 2. Install the database software by following the instructions in the Oracle documentation. Ensure that you install the database software only. The installer has an option like Install database software only. Select this option. 3. For Oracle 11g only, configure a database listener with the command netca as Oracle user. Oracle 10g contains the database listener configuration in the standard installer. 4. Create a database with the command dbca as Oracle user. As storage mechanism, select file system and use common location for all database files. As a location, select the directory you created on the shared disk. 5. Start the database and the listener. 6. Verify your installation, for example by connecting a database client to the database. 7. Stop the database and the listener. 8. Create an archie of the database software. For example, if you installed the database in the directory /opt/oracle, run the following command: tar cf MP1_oracle10g.tar /opt/oracle. 9. Copy the tar file to all systems you prepared to run the Oracle database software. Unpack the archie that you created. For example, run the following command: tar xf MP1_oracle10g.tar /opt/oracle. 10. Test whether the replication step was successful: Unmount the shared disk on the system where you installed the database. Mount the shared disk on the system where you unpacked the archie. Start the database. Start the database listener. 130 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

147 Ensure that the database works properly by connecting a database client to the database. If you completed all the steps successfully, you can proceed with the configuration. See Configuring and actiating the Oracle database high aailability policy on page 132. Configuring the indiidual Oracle database components To automate an Oracle database, configure the following subcomponents of a database installation. Oracle database serer To automate the database serer, System Automation must be able to start, stop, and monitor the specified database serer. For more information on how to automate the database serer using System Automation, refer to Oracle database high aailability policy on page 133. If Oracle is configured to be started automatically by the operating system, for example it is listed in /etc/rc.d/rc*.d (Linux) and /etc/inittab (AIX), you need to ensure that these listings are remoed. This is not a default configuration performed by the Oracle installation, but is required if your system administrator has configured the operating system to automatically start Oracle. Oracle database listener To automate the database listener, System Automation must be able to start, stop and monitor the specified database listener. For more information on how to automate the database listener using System Automation, refer to Oracle database high aailability policy on page 133. Oracle database files The Oracle database files need to be accessible from each node where the Oracle database serer runs. Therefore, data must be located on shared disks. For each file system that resides on such a shared disk, a mount point must be defined within the operating system, for example in /etc/fstab on Linux. For each mount point, an IBM.AgFileSystem resource must exist, either harested by the StorageRM resource manager or user-defined. On Linux it is recommended to specify a label for the file system, because the label is taken as resource name for harested IBM.AgFileSystem resources. For more information about StorageRM, see System Automation for Multiplatforms Administrator's and User's Guide. Note: If a shared disk configuration is changed, for example attaching a new deice to use as a shared disk or adding and changing mount points, the StorageRM may not immediately remap these changes into the harested storage resource information. You need to run the command refrsrc IBM.Disk or wait at least the configured harest interal of IBM.Disk. The default alue is 1800 seconds. If you create mount points, specify mount option noauto to preent that the file system is mounted during system start. Chapter 4. Oracle high aailability policy 131

148 Oracle irtual IP address Database clients connect to a database serer by contacting a listener of the database serer, which is determined by its host name or the IP address of the host. When the listener is restarted on a different node, then the irtual IP address will be bound to a network adapter on the same node, so that the client always connects to the same IP address. Example for Linux network adapters: node-1 network adapter eth netmask network adapter eth netmask node-2 network adapter eth netmask network adapter eth netmask Example for AIX network adapters: node-1 network adapter en netmask network adapter en netmask node-2 network adapter en netmask network adapter en netmask For example, you only want database clients to access the nodes through the IP addresses /3. Then you must specify eth0 on Linux or en0 on AIX of node-1 and node-2 as network interfaces in the Oracle policy. The irtual IP address can hae any free IP address in the subnet, for example Oracle database clients You need to configure your Oracle database clients to connect to the irtual IP address defined in the policy. Configure the host parameter of the file tnsnames.ora. The database client is installed in /opt/oracle/product/10.2.0/db_1, and the database alias to connect to a database is MPDBALIAS. The irtual IP address has the DNS name irtualip105. The port 1521 must be aailable and the same on all database serers. The database SID which the listener connects to is MPDB. /opt/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora MPDBALIAS = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = irtualip105)(port = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = MPDB) ) ) Configuring and actiating the Oracle database high aailability policy System Automation for Multiplatforms proides a predefined Oracle database high aailability policy to automate your Oracle database and to keep it highly aailable. The policy takes care of all Oracle database components as described in Configuring the indiidual Oracle database components on page 131. Use the sampolicy wizard to configure the policy to your specific Oracle database configuration and actiate this policy. 132 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

149 Oracle database high aailability policy The Oracle database high aailability policy consists of one group containing the Oracle database serer, the Oracle database listener, the irtual IP address and the file system containing the Oracle database. Figure 22. Oracle database high aailability policy The following table lists all resources contained in the policy: Table 28. Oracle database high aailability resources Name Resource name Description Oracle resource group IBM.ResourceGroup/<PREFIX>-rg Resource group containing all Oracle resources. Oracle database serer IBM.Application/<PREFIX>- db Oracle database processes, which are started, stopped, and monitored using scripts. Oracle database listener IBM.Application/<PREFIX>- lsn Oracle database listener process, which is started, stopped, and monitored using scripts. Virtual IP address IBM.SericeIP/<PREFIX>-ip Virtual IP address to connect Oracle database clients to Oracle database listener. Oracle database files IBM.AgFileSystem/ <ORACLE_FILESYSNAME> File system containing the Oracle database files, may occur multiple times. Network interfaces IBM.Equialency and IBM.NetworkInterface/ <PREFIX>-nieq-1-dyn Selects network adapters to bind irtual IP to. Started, stopped, and monitored using IBM.GblResRM. The Oracle database serer and the Oracle database listener are resources of class IBM.Application. For IBM.Application, a script is required to start, stop, and monitor. The samoraclectrl-db script that controls the Oracle database serer has the following arguments: Chapter 4. Oracle high aailability policy 133

150 Action <start stop status> OracleHome <path to the oracle installation> OracleSid <instance name of the database to start> OracleOwner <user ID of the database owner> start Starts the database processes. stop Stops the database processes. status Checks if a process for the specified instance runs The samoracle-lsn script which controls the Oracle database listener has the following arguments: Action <start stop status> OracleHome <path to the oracle installation> ListenerName <name of the listener instance> OracleOwner <user ID of the database owner> start Starts the listener processes. stop Stops the listener processes. status Checks if the listener processes for the specified listener instance runs. The following table shows all relationships that are defined: Table 29. Oracle database high aailability policy relationships Relationship name Source Target Type <PREFIX>-lsn-on-ip-1 Oracle database listener Virtual IP address <PREFIX>-ip-on-nieq-1 Virtual IP address Network equialency <PREFIX>-lsn- DependsOn- <ORACLE_FILESYSNAME> <PREFIX>-db-DependsOn- ORACLE_FILESYSNAME> Oracle database listener Oracle database serer Oracle database files Oracle database files DependsOn DependsOn DependsOn may occur multiple times depending on number of file systems. DependsOn may occur multiple times depending on number of file systems. The Oracle database listener and the Oracle database serer cannot be started without the file system being mounted that contains the Oracle database files. DependsOn relationships are defined between the listener and the database files and the listener and the database serer. The Oracle database clients connect to the Oracle database listener using a irtual IP address, therefore there is also a dependson relationship defined between the listener and the IP address. The irtual IP address needs to be bound to a network interface, which leads to a dependson relationship between the irtual IP and the network equialency. In this sample scenario an Oracle database installation was automated using the Oracle database policy: The Oracle database was automated using the policy described aboe. A mount point oracledata is defined on a shared disk. A irtual IP address is resered for the database listener and specified to be bound to the en0 network interfaces on both nodes. Output of lssam for this setup: 134 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

151 Offline IBM.ResourceGroup:oracle-rg Nominal=Offline - Offline IBM.AgFileSystem:oradata MNT=/oracledata <. <. - Offline IBM.AgFileSystem:oracledata:node-1 - Offline IBM.AgFileSystem:oracledata:node-2 DO - Offline IBM.Application:oracle-db - - Offline IBM.Application:oracle-db:node-1 - Offline IBM.Application:oracle-db:node-2 DO - Offline IBM.Application:oracle-lsn Offline IBM.Application:oracle-lsn:node-1 - Offline IBM.Application:oracle-lsn:node-2 DO - Offline IBM.SericeIP:oracle-ip-1 IP= < - Offline IBM.SericeIP:oracle-ip-1:node-1 - Offline IBM.SericeIP:oracle-ip-1:node-2 DO Online IBM.Equialency:oracle-nieq-1-dyn < - Online IBM.NetworkInterface:en0:node-1 - Online IBM.NetworkInterface:en0:node-2 Oracle policy high aailability and automation preparation Before you run the sampolicy wizard, to configure and actiate the Oracle database high aailability policy, complete all of the following required installation and configuration tasks: All Oracle installation and configuration steps must be completed successfully. See Installing the Oracle database software on page 129 and Configuring the indiidual Oracle database components on page 131. System Automation for Multiplatforms is installed and an automation domain is configured. For a description of this setup for the SAP high aailability policy, see Installing System Automation for Multiplatforms on all cluster nodes on page 24. Skip the SAP-specific steps in that section. Make sure that: System Automation for Multiplatforms ersion or higher is installed on all nodes where you want the Oracle database serer to run. Issue the samersion command to check that the correct ersion of System Automation for Multiplatforms is installed. Domain has quorum: lssrc -ls IBM.RecoeryRM SAP Central Serices high aailability policy feature license is installed as described in Installing the SAP high aailability policy feature license on page 26. Before you automate an Oracle database, ensure that the Oracle database works properly on all systems. For all necessary steps to test a manual failoer from one system to the other, see Installing the Oracle database software on page 129. Oracle database high aailability policy parameters The Oracle database high aailability policy requires a number of parameters to be specified in order to configure the Oracle database high aailability policy for your specific enironment, like the Oracle home directory or the file system on a shared disks that hosts the database instance. The following parameter listings consist of a parameter description, a alue type, and a default alue. Chapter 4. Oracle high aailability policy 135

152 Table 30. Oracle database high aailability policy parameters. # Parameter description Value Type Value 1 Value type: String Enter the name of your SA MP domain. 2 Proide the name of an existing SA MP domain. The SA MP domain will host the Oracle database resources that will be configured with this template. Enter your desired prefix for all Oracle policy resources. oracle Value type: String SA-oracle 3 This prefix will be used as a prefix for all SA MP resources that coer the Oracle database policy. For later operational tasks, the prefix can be used to start and stop resources with the same prefix with one single command. Enter the nodes where you want to automate the Oracle database. List of alues, alue type for each alue: Host name or IP ersion 4 address (plus additional alue checking) These nodes must be listed when you enter the SA MP command lsrpnode for the specified domain. You can use either the long or the short name for a node. Oracle database resources will be created for each of the specified nodes. Specify a irtual IP address for the Oracle database instance. This IP address will be used as a irtual IP address for the floating Oracle database instance. Enter the netmask for the subnet of the irtual Oracle database IP address. Enter the netmask for the subnet of the irtual Oracle database IP address. An example for a netmask is Enter the aailable network interface for the Oracle database. The following network interfaces are aailable on your local system: The aailable network interface specifies to which network interface the irtual Oracle database IP address can be bound, for AIX an example is "en0", for Linux, an example is "eth0". The same network interface name needs to be aailable on all nodes where the Oracle database will be automated. Value type: IP ersion 4 address Value type: IP ersion 4 address Value type: String (plus additional alue checking) 136 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

153 Table 30. Oracle database high aailability policy parameters (continued). # Parameter description Value Type Value 7 List of alues, alue type for each alue: Specify the names of the IBM.AgFileSystem resources that represent the mount points of the Oracle database instance directories. The following resource of class IBM.AgFileSystem are aailable in your domain ("Name" "SysMountPoint"): String (plus additional alue checking) SA MP will automatically mount the directories with Oracle database instance data prior to starting the Oracle database processes, and will automatically unmount the directories after stopping the Oracle database processes. You can determine the name of the IBM.AgFileSystem by issuing the following command lsrsrc -s "ResourceType==1 IBM.AgFileSystem Name SysMountPoint. This command will return a list of IBM.AgFileSystem resources. Use the name of the resources that represent the mount point of the Oracle database instance data directories. Specify the path to the Oracle home directory, that was set during the Oracle database installation. The Oracle home directory contains all Oracle software files. For an Oracle 11g installation, the home directory is called 'Software Location' in the Oracle installer, for an Oracle 10g installation, 'Oracle Home'. Specify the Oracle System Identifier (SID) for the database that will be kept highly aailable. The Oracle System Identifier (SID) uniquely identifies a database instance and is set during the Oracle database configuration or installation. Specify the name of the Oracle software owner user, for example "oracle". The Oracle software owner user was created before the Oracle installation is started. This user is required to start and stop the database. Value type: String Value type: String Value type: String Chapter 4. Oracle high aailability policy 137

154 Table 30. Oracle database high aailability policy parameters (continued). # Parameter description Value Type Value Specify the name of the Oracle Net listener. An Oracle Net listener is required for each Oracle installation in order to establish a remote connection to a database. Specify the desired state of your Oracle resources. If you specify Online, the Oracle resources will be started on policy actiation, if not already started. If you specify Offline, the Oracle resources will not be started on policy actiation, but stopped if they are online. Value type: String One of the following alues: Online Offline Offline Using the wizard to configure and actiate the Oracle database high aailability policy The Oracle database serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. The policy template samora_templateoracle.tmpl.xml, is located in the installation directory of the Oracle database high aailability policy, /usr/sbin/rsct/ sapolicies/oracle. To configure the template, run the following command: sampolicy w /usr/sbin/rsct/sapolicies/oracle/samora_templateoracle.tmpl.xml You must configure a policy pool before running the wizard. The wizard will then store all modifications to the policy pool. If you set your policy pool to /etc/mypolicypool, a wizard run using sampolicy -w /usr/sbin/rsct/sapolicies/oracle/samora_templateoracle.tmpl.xml stores the results to /etc/mypolicypool/samora_templateoracle.tmpl.xml The next time you inoke the wizard, use the file stored in the policy pool. With the example aboe, inoking the wizard for the second time would look like this: sampolicy -w /etc/mypolicypool/samora_templateoracle.tmpl.xml Using the wizard to configure and actiate the SAP Central Serices high aailability policy on page 42 Each SAP Central Serices high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Using the wizard to configure and actiate the NFS serer high aailability policy on page 124 The NFS serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. 138 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

155 Chapter 5, Using the wizard to configure and actiate the policy, on page 141 Use the policy setup wizard to configure and actiate your IBM Tioli System Automation for Multiplatforms policies. Verifying the Oracle database high aailability policy After you installed and configured your Oracle database, erify that your settings are correct. Verifying the settings To erify the installation and configuration of your Oracle highly aailability policy, proceed with the following steps: Start the database policy. Enter the command chrg o online <database_group_name> Connect a database client to the database. If the connection is successful, continue with testing Oracle database failoer. Testing Oracle database failoer After you erified that your automated Oracle database works on one node, initiate a failoer. In a two node cluster with node-1 and node-2, exclude the node from automation on which the Oracle database currently runs and check if it is started on the other node. Assuming the Oracle database runs on node-2, enter: samctrl -u a node-2 Node-2 is added to the list of nodes that are excluded from automation. Wait until the failoer starts. Then inspect the resources in SA-nfsserer-rg using the lssam command: Offline IBM.ResourceGroup:oracle-rg Nominal=Offline - Online IBM.AgFileSystem:oradata MNT=/oracledata - Online IBM.AgFileSystem:oracledata:node-1 - Offline IBM.AgFileSystem:oracledata:node-2 Node=Excluded - Offline IBM.Application:oracle-db - Online IBM.Application:oracle-db:node-1 - Offline IBM.Application:oracle-db:node-2 Node=Excluded - Offline IBM.Application:oracle-lsn - Online IBM.Application:oracle-lsn:node-1 - Offline IBM.Application:oracle-lsn:node-2 Node=Excluded - Offline IBM.SericeIP:oracle-ip-1 IP= Online IBM.SericeIP:oracle-ip-1:node-1 - Offline IBM.SericeIP:oracle-ip-1:node-2 Node=Excluded You can always inspect which nodes are excluded using the lssamctrl command: SAMControl information SAMControl: TimeOut = 60 RetryCount = 3 Automation = Auto ExcludedNodes = {node-2} ResourceRestartTimeOut = 5 Ensure that the NFS serer mount points on your NFS clients are still working, for example by accessing the directory of the mount points. You can now include node-2 to the automation again, enter: samctrl -u d node-2 Chapter 4. Oracle high aailability policy 139

156 The parameter d is used to delete the node from the list of excluded nodes. After the Oracle database is online on node-1 you should be able to access and modify the Oracle database from a database client. After haing successfully completed this test scenario using samctrl, run a node failure test scenario. Before you start, ensure that the following prerequisites are met: Make sure that the list of excluded nodes is empty. Use the command lssamctrl to erify. If you hae a two node cluster as in the preious example make sure you hae correctly setup a tiebreaker. For more information about the tiebreaker, see System Automation for Multiplatforms Administrator's and User's Guide. If these prerequisites are satisfied you can test a failoer by either rebooting the node currently running the Oracle database serer or pressing the power button. The Oracle database serer should be failed oer to the other node, and the Oracle clients are still able to connect to the database. 140 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

157 Chapter 5. Using the wizard to configure and actiate the policy Use the policy setup wizard to configure and actiate your IBM Tioli System Automation for Multiplatforms policies. You can perform the following tasks using the System Automation for Multiplatforms Policy Setup Wizard: Start the Policy Setup Wizard. Select the policy that you want to configure. You can find one policy XML file for each of the SAP high aailability setup options that are described in Starting the Policy Setup Wizard. Specify or modify the parameters to configure the policy and adapt it to your enironment. You can find a description of the parameters in SAP Central Serices high aailability policy parameters on page 43 for each SAP high aailability setup to help you configuring the policy and choosing the right alues. Sae the policy XML file. You may want to quit the wizard at any point in time, een if your input is still incomplete or incorrect. If you later resume the policy setup task, the Policy Setup Wizard will pick up the alues that you specified so far. Actiate the policy. Once you hae created a complete and correct ersion of the policy, you can actiate the policy using the Policy Setup Wizard or you enter the sampolicy command from the command line. Using the wizard to configure and actiate the SAP Central Serices high aailability policy on page 42 Each SAP Central Serices high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Using the wizard to configure and actiate the NFS serer high aailability policy on page 124 The NFS serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Using the wizard to configure and actiate the Oracle database high aailability policy on page 138 The Oracle database serer high aailability policy consists of a policy template that is tailored by using the sampolicy wizard. Starting the Policy Setup Wizard Use the sampolicy command to start the Policy Setup Wizard. The following describes a subset of the sampolicy syntax that is required to start the Policy Setup Wizard. Refer to Tioli System Automation for Multiplatforms Reference for a description of the complete set of options and parameters for this command. Synopsis sampolicy w Templatefilename Options -w Starts the Policy Setup Wizard. Parameters Templatefilename Copyright IBM Corp. 2014,

158 If you start the Policy Setup Wizard, an xml template is used as input file. Define alues for the ariables contained in the xml template before you can actiate the corresponding policy. The Policy Setup Wizard will fill all alues based on your input. Please obsere the following when specifying the xml template file as input parameter: After installing System Automation for Multiplatforms, all template files are located in one of the subdirectories of /usr/sbin/rsct/sapolicies. If you start the Policy Setup Wizard for a particular xml template for the first time, specify one of those template files, for example /usr/sbin/rsct/sapolicies/sap/ samsap_templateabap.tmpl.xml. The Policy Setup Wizard modifies the xml file and stores the modified ersion in the System Automation for Multiplatforms policy pool using the same file name. You must configure the policy pool before you can start the wizard. For more information, see System Automation for Multiplatforms Installation and Configuration Guide. If you want to change a policy again, specify the template file that is located in the policy pool when you inoke the Policy Setup Wizard. Your changes are again stored in the policy pool. Wheneer an xml template in the policy pool is modified, a new backup copy of the original template file is created in the policy pool before oerwriting the original file with the latest changes. The backup file has the same name as the original file with a time-stamp appended. This allows you to fall back to any preious ersion of the policy. If you want to restore one of the backup ersions from the policy pool, inoke the Policy Setup Wizard specifying the corresponding backup file. If you want to go back to the initial ersion that was deliered with System Automation for Multiplatforms, inoke the Policy Setup Wizard with the corresponding template file in /usr/sbin/rsct/sapolicies/<policy>. Regardless of whether a template file is located in a product install directory or in the policy pool, there are two ways you can specify the template file as an input parameter: 1. By proiding the fully qualified name. 2. By using the directory where the template is located as working directory and specifying just the file name. Migrating between an old and a new template If a new template file is shipped with a new System Automation for Multiplatforms ersion, the new template file can contain changes. If you enter the command sampolicy with the existing template file you receie the information if a migration is necessary. Values that are already specified in an existing template file can then be migrated to the new template file using the wizard migrate option: Synopsis sampolicy w -m <TemplatefilenameNew> <TemplateFileNameOld> Options -w -m: Starts the Policy Setup Wizard in migration mode. Parameters <TemplatefilenameNew>: The latest XML template file, installed in /usr/sbin/rsct/sapolicies/<policyname>, containing the phrase tmpl in its filename. <TemplatefilenameOld>: Any template file that already contains alues you wish to migrate to the new policy template. 142 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

159 Oeriew dialog Using this option, all alues of the old template file are copied to the new template file and the wizard proceeds based on the new file with the copied alues. If it is required to specify additional alues in the new template they are indicated in the parameter oeriew with the flag Missing besides a alue question. When the Policy Setup Wizard is started, the oeriew dialog is displayed. It lists all parameters and their current alue status. From the oeriew dialog you can switch directly to a parameter dialog for each of the parameters. The following is an example for an oeriew dialog: Figure 23. Oeriew dialog Chapter 5. Using the wizard to configure and actiate the policy 143

160 Dialog elements Dialog header The dialog header proides a short description of the policy that you currently configure. If you configure multiple policies, the dialog header description clearly identifies with which policy you are working. Below the description you see the accumulated oerall parameter status: OK or Incorrect. Parameter list The parameter list proides an entry for each parameter that you can configure for this policy. The list consists of three columns with the following alues: #:Contains a sequence number that uniquely identifies the parameter. Enter this number to switch to the corresponding parameter dialog. Parameter: Contains a descriptie text for the parameter. If the parameter represents a yes or no decision, the text may also be the corresponding question. Value:Shows the current alue status of the parameter. This can be one of the following: OK: A alid alue is defined for this parameter. Missing: Currently no alid alue is defined for this parameter. Although a alue might hae been preiously entered into the template file, this alue can become inalid if the system enironment changes, for example if a NetworkInterface is no longer aailable on a system. The wizard will not display inalid alues. Incorrect: A alue is specified for this parameter, but this alue is not alid due to unfulfilled dependencies to other parameters. The oerall parameter status that is shown in the dialog header is OK if the alue status for all parameters is OK. Options The options that you can select in the oeriew dialog are:?: Enables or disables to display parameter help information in all parameter dialogs. Refer to Parameter help information on page 154 for a description how you can control the display of help information in the oeriew dialog as well as in parameter dialogs. H: Enables or disables to automatically retriee the currently defined alue in all parameter dialogs that support the alue haresting option. A command to retriee the alue may be defined for one or multiple parameters in the XML template file that you hae specified when starting the wizard. If no haresting command is defined for any of the parameters in the template, this option is not aailable. You may consider to enable automatic alue haresting before you step through the parameter dialogs for the first time. Refer to Dialog elements on page 146 for a description of the alue haresting option in a parameter dialog. 0: Saes your changes and quits the Policy Setup Wizard. Changes that you hae applied to any of the parameter alues are saed. X: Cancels the Policy Setup Wizard. No changes are saed. Refer to Closing the wizard on page 155 for more details on how to finish the wizard using Finish or Cancel in the oeriew dialog as well as in parameter dialogs. 144 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

161 Interactions Type either one of the numbers that are listed in the # column of the parameter list or one of the options and press ENTER. Skipped parameters Gaps of missing numbers in the parameter list indicate that parameters are skipped. In the oeriew dialog shown in Figure 23 on page 143 you can see that parameters 15 and 18 are skipped. Which parameters are currently skipped depends on alues that are specified for related parameters. The set of skipped parameters changes depending on your input. An example for a parameter that determines which related parameters are to be skipped is the product ersion for which you configure a policy template. For different product ersions different sets of parameters are required. If you select "Version A" for the product ersion parameter, all parameters that are required for ersion B are skipped and ice ersa. Parameter dialog Note: The last parameter(s) in the sequence may be skipped. This is not as obious as actual gaps in the parameter number sequence. Inoke a parameter dialog by entering the assigned number in the # column on the oeriew dialog. The following are two examples for the parameter dialog # 3. The first one is an example for the case where no alue is specified yet. Figure 24. Parameter dialog #3 without alue definition In the second example, a alue is already defined. Chapter 5. Using the wizard to configure and actiate the policy 145

162 Figure 25. Parameter dialog #3 with alue definition Dialog elements Dialog header The dialog header proides a short description of the policy that you currently configure. If you configure multiple policies, the dialog header description clearly identifies with which policy you are working. Below the description you see the accumulated oerall parameter status: OK or Incorrect. Parameter information Below the dialog header you find some information that helps you to configure this particular parameter: Parameter n of m: The parameter sequence number is located on the right hand side. n is the number of this parameter that matches the corresponding number from the # column in the parameter list of the oeriew dialog. m is the total number of parameters that need to be configured for this policy. Parameter description: This is the text that matches the text from the Parameter column for this parameter in the parameter list of the oeriew dialog. Parameter alue: Reflects the configured alue for this parameter. Figure 24 on page 145 shows a parameter that has no entered alue. Figure 25 shows a parameter with a defined alue of 7.0. Options The options that you can select in a parameter dialog are: 1: Enter a alue for this parameter as shown in Figure 24 on page 145 or edit an existing alue as shown in Figure 25. Selecting this option starts the prompt mode for this parameter which is described in Entering alues on page Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

163 2: Return to the preious parameter dialog in the sequence as listed in the oeriew dialog in Figure 23 on page 143. This option is not aailable for the first parameter. Note: This option may also be not aailable although the number of the current parameter is larger than "1". In this case all proceeding parameters are skipped. Refer to Skipped parameters on page : Display the next parameter dialog in the sequence as listed in the oeriew dialog in Figure 23 on page 143. This option is not aailable for the last parameter. Note: This option may also be not aailable although the number of the current parameter is smaller than the total number of parameters. In this case all following parameters are skipped. Refer to Skipped parameters on page : Retriee the currently defined alue from the running system. The parameter alue in the parameter information section is filled with the harested alue. This option is only aailable if a command is defined to actually retriee the alue in the XML template file that you hae specified when starting the wizard. If a alue is already shown in the parameter information section, it will be oerwritten with the harested alue. You can oerwrite again a harested alue by using option 1. If you hae enabled automatic alue haresting in the oeriew dialog and no alue is specified yet, the haresting function is performed automatically as soon as you open the dialog.?: Display help information for this parameter. Refer to Parameter help information on page 154 for a description how you can control the display of help information in the oeriew dialog as well as in parameter dialogs. +: Return to the oeriew dialog. 0: Sae and exit the Policy Setup Wizard. Changes that you hae applied to any of the parameter alues are saed. X: Cancel the Policy Setup Wizard. No changes are saed. Entering alues Refer to Closing the wizard on page 155 for more details on how to quit the wizard using Finish or Cancel in the oeriew dialog as well as in parameter dialogs. Interactions Type one of the options and press ENTER. Each parameter dialog lets you select an option. If you select option 1, the dialog switches to the alue prompt mode where you can select or enter a alue. Depending on the kind of alue that you specify, different prompt modes are used. The following alue prompt modes apply: Single alue: Enter a alue. Multiple alues: Enter a set of different alues. For the multiple alue prompt mode, you can enter one of the following types: List of alues: Enter multiple alues, where each alue is one row in the list. Chapter 5. Using the wizard to configure and actiate the policy 147

164 Table of alues with a fixed number of table columns: Enter multiple alues, where each alue is one cell in the table. Table of alues with a ariable number of table columns: Enter multiple alues, where each alue is one cell in the table and for each table row enter the number of columns. Value section: Select one of a distinct set of alues Decision: Select yes or no In the alue prompt mode the Policy Setup Wizard executes syntactical erification of the input alues that you specify. Examples: Enter a numeric alue within a certain minimum or maximum range. Enter an IP address. Select a alue listed in the alue selection mode. Single alue This prompt mode is used for the most of the parameters to enter a single alue. The following is an example for this mode: Figure 26. Single alue prompt Type the requested alue and press ENTER. If you want to cancel the alue prompt and return to the option selection mode, press ENTER without typing any alue. Multiple alues Prompts for a set of different alues. The following is an example for this mode in which the dialog prompts for a list of alues: 148 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

165 Figure 27. Multiple alues prompt For each alue that you want to specify, enter the alue and press ENTER. After you hae specified the last alue, press ENTER without typing any alue. If the set of multiple alues that are prompted is a table of alues instead of simply a list, enter the alue for each table cell and press ENTER. In this case, each table row is referred to in the prompt text as "alue" and each table column is referred to as "sub-alue". If the set of input alues is a table with a ariable number of columns per row, the dialog prompts also for the number of alues in each row before prompting for the actual sub-alues for that row. If you want to cancel the alue prompt and return to the option selection mode, press ENTER when the dialog asks for the ery first alue. Value selection Select one alue from a set of predefined alues. The following is an example for this mode: Chapter 5. Using the wizard to configure and actiate the policy 149

166 Figure 28. Value selection mode Type the option for the alue that you want to choose and press ENTER. If you want to cancel the alue prompt and return to the option selection mode, just press ENTER without typing any alue. Note: This is also an example for how to modify an existing alue. Decision Prompts for a yes or no decision. The following is an example for this mode: 150 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

167 Option parameters Figure 29. Decision prompt Type the option that matches your decision and press ENTER. If you want to cancel the alue prompt and return to the option selection mode, press ENTER without typing any alue. Note: This is at the same time an example for how to modify an existing alue. Option parameters represent a yes or no option. Your decision has the following impact: yes: Configure one or more additional parameters. no: Additional parameters are obsolete and will be ignored. As long as no decision is made or no is selected, the additional parameters are not shown in the oeriew dialog. Parameter # 17 in the oeriew dialog in Figure 23 on page 143 is an example for an option parameter that has currently the alue no. If you select yes, the parameters are shown in the oeriew dialog as follows: Chapter 5. Using the wizard to configure and actiate the policy 151

168 Figure 30. Option parameter in oeriew dialog You can find fie additional parameters that are nested under the option parameter. The nested parameters need to be configured as well. Proceed as follows: 1. Switch to the option parameter dialog. 2. Naigate from one parameter to the next parameter using the Next option. The following is the parameter dialog for this option parameter: Figure 31. Option parameter dialog Select Next to configure the first nested parameter. If you hae multiple nested parameters to configure for the same option parameter, Next naigates you through the list of nested parameters. The number of nested parameters that you hae to define is added to the parameter information on the right hand side. 152 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

169 Wizard dialog flow Figure 32. Nested parameter dialog Figure 33 on page 154 shows the flow between the oeriew dialog and parameter dialogs, including option parameters and the corresponding nested parameter dialogs. Chapter 5. Using the wizard to configure and actiate the policy 153

170 Figure 33. Wizard dialog flow Parameter help information In addition to the descriptie text, there is also a more detailed help text aailable for each parameter. You can control the display of the help at two different locations: 1. Oeriew dialog 2. Parameter dialog Enable and disable help information for all parameter dialogs In the oeriew dialog you can enable or disable parameter help information in all parameter dialogs by using the? option. The text that is associated with the? option indicates whether help information is currently enabled or disabled. Using the? option toggles the status of help information display. Table 31. Help information text of the Setup Policy Wizard Help information text Description? Enable help for all parameters Indicates that help information is currently disabled. Selecting the? option will then enable help information in all parameter dialogs. 154 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides

171 Table 31. Help information text of the Setup Policy Wizard (continued) Help information text Description? Disable help for all parameters Indicates that help information is currently enabled. Selecting the? option will then disable help information in all parameter dialogs. Display help information in selected parameter dialogs In each parameter dialog you can use the? option to display help information for the respectie parameter. When you select the? option, the parameter information section of the dialog is extended by adding the help text. The? option is remoed from the option list of this dialog. You can remoe the help text only by switching to the oeriew dialog and disable help information for all parameter dialogs. The following is an example for a parameter dialog with help information being shown. Closing the wizard Figure 34. Help information in parameter dialogs You hae the following two options to close the wizard: 1. Use the 0 option to close the wizard. The following actions are performed: a. The content of the xml policy template file that you hae specified with the sampolicy command to start the wizard is modified. The modified ersion is stored in the System Automation for Multiplatforms policy pool. If you Chapter 5. Using the wizard to configure and actiate the policy 155

172 Actiating the policy want to change a modified policy again, refer to Starting the Policy Setup Wizard on page 141. This section describes the different options and considerations for modifying policies. b. A parameter and alue summary is created in HTML format. The generated HTML table is similar to the tables that are included in SAP Central Serices high aailability policy parameters on page 43. The file is also saed in the policy pool with the same name as the template and the extension.html. c. If all parameter alues are correctly specified which is indicated by the oerall parameter status OK, then you are prompted for policy actiation. Refer to Actiating the policy. 2. Use the X option to cancel the wizard. Confirm your cancel request to quit the wizard without any saed changes. No parameter summary is created and you do not hae the opportunity to actiate the policy. The Finish and Cancel options are aailable in the oeriew dialog as well as in each parameter dialog. The actions described are executed independently from the type of dialog in which the option is selected. If you used the 0 option to end the wizard and all parameter alues are correctly specified with oerall parameter status OK, you can actiate the policy. The following is an example for the dialog asking to actiate the policy: Figure 35. Policy actiation in the wizard Depending on the option that you select, one of the following actions is performed: 1. Yes, actiate as new policy: The policy is actiated as a new policy. This is equialent to inoking the command sampolicy a t templatefilename 2. Yes, actiate by updating currently actie policy: The policy is actiated by updating the currently actie policy. This is equialent to inoking the command sampolicy u t templatefilename 3. No, sae modifications and exit: No policy actiation is performed. Your modifications are saed and the wizard is closed. 4. No, return to parameter oeriew: No policy actiation is performed. Modifications are not saed and the wizard returns to the oeriew dialog. 156 Tioli System Automation for Multiplatforms V4.1: High Aailability Policies Guides