Skip to Content

Configuration of AWS specific Constraints

The AWS Move IP agent will need to operate on the same node as the SAP HANA database. A constraint will force it to be on the same node. The constraint will be different compared to section 5.3.8 of the Setup Guide (SAP HANA SR Performance Optimized Scenario 12SP1) document from SUSE.

Creation of a Constraint in the Command Line Interface

Create a file aws-constraint.txt with the following content. Take care that you use the same resource identifier as before.

colocation col_IP_Primary 2000: res_AWS_IP:Started msl_SAPHana_SID_HDB00:Master
order ord_SAPHana 2000: cln_SAPHanaTopology_SID_HDB00 msl_SAPHana_SID_HDB00

The file above encoded the SAP SID as part of the ressource name. This will differ in your configuration!

Add this file to the configuration. The following command has to be issued as super user. It uses the file name aws-constraint.txt:

crm configure load update aws-constraint.txt

Remaining Configuration

Make sure that the SUSE instance will allow to reach the URL http://169.254.169.254/latest/meta-data . The stoneith agent will access it. Allow your firewall to access it. Disable proxy access to this URL. The hypervisor is providing this information. The system will not access the Internet for it.

The tasks described in section 5.3.9 are needed only when additional development and QA systems are being operated on the cluster.

All other installation steps are identical to an installation from the Setup Guide SAP HANA SR Performance Optimized Scenario (12SP1).

 



book | by Dr. Radut