Before creating resources to protect the virtual IP addresses associated to the ASCS and ERS instances, the following steps must be completed on node-a and node-b:

We will now follow the process described in Creating an AWS EC2 Resource (RouteTable Scenario) to create resource hierarchies for the virtual IP addresses associated to the ASCS and ERS instances.

Since the IP addresses used with the EC2 RouteTable resource type must be located outside of the VPC CIDR (which for LK-VPC is 10.20.0.0/16), we will use the following virtual host names and IP addresses:

Instance
Virtual Host Name
IP Address
ASCS10 sps-ascs 10.10.10.10
ERS20 sps-ers 10.10.10.20

Create the ASCS Virtual IP Resource Hierarchy

  1. Following the steps described in Creating an IP Resource, use the following parameters to create and extend a LifeKeeper IP resource (ip-sps-ascs) to protect the ASCS virtual IP address on node-a and node-b. Notice that the IP resource is being created on node-a and extended to node-b. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Field
Value
Create Resource Wizard
Switchback Type intelligent
Server node-a
IP Resource 10.10.10.10
Netmask 255.255.255.0
Network Interface eth0
IP Resource Tag ip-sps-ascs
Pre-Extend Wizard
Target Server node-b
Switchback Type intelligent
Template Priority 1
Target Priority 10
Extend comm/ip Resource Hierarchy Wizard
IP Resource 10.10.10.10
Netmask 255.255.255.0
Network Interface eth0
IP Resource Tag ip-sps-ascs
  1. Following the steps described in Creating an AWS EC2 Resource (RouteTable Scenario), use the following parameters to create and extend a LifeKeeper EC2 resource (ec2-sps-ascs) to manage the backend manipulation of the route table in AWS when the IP resource is switched over. Notice that the EC2 resource is being created on node-a and extended to node-b. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Field
Value
Create Resource Wizard
Switchback Type intelligent
Server node-a
EC2 Resource type RouteTable (Backend cluster)
IP Resource ip-sps-ascs
EC2 Resource Tag ec2-sps-ascs
Pre-Extend Wizard
Target Server node-b
Switchback Type intelligent
Template Priority 1
Target Priority 10
Extend comm/ec2 Resource Hierarchy Wizard
EC2 Resource Tag ec2-sps-ascs

Once the IP resource hierarchy has been successfully created, the LifeKeeper GUI should resemble the following image:

Create the ERS Virtual IP Resource Hierarchy

  1. Following the steps described in Creating an IP Resource, use the following parameters to create and extend a LifeKeeper IP resource (ip-sps-ers) to protect the ERS virtual IP address on node-a and node-b. Notice that the IP resource is being created on node-b and extended to node-a. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Field
Value
Create Resource Wizard
Switchback Type intelligent
Server node-b
IP Resource 10.10.10.20
Netmask 255.255.255.0
Network Interface eth0
IP Resource Tag ip-sps-ers
Pre-Extend Wizard
Target Server node-a
Switchback Type intelligent
Template Priority 1
Target Priority 10
Extend comm/ip Resource Hierarchy Wizard
IP Resource 10.10.10.20
Netmask 255.255.255.0
Network Interface eth0
IP Resource Tag ip-sps-ers
  1. Following the steps described in Creating an AWS EC2 Resource (RouteTable Scenario), use the following parameters to create and extend a LifeKeeper EC2 resource (ec2-sps-ers) to manage the backend manipulation of the route table in AWS when the IP resource is switched over. Notice that the EC2 resource is being created on node-b and extended to node-a. Also note that the resulting resource should not be extended to node-c, the witness node. The icon indicates that the default option is chosen.
Field
Value
Create Resource Wizard
Switchback Type intelligent
Server node-b
EC2 Resource type RouteTable (Backend cluster)
IP Resource ip-sps-ers
EC2 Resource Tag ec2-sps-ers
Pre-Extend Wizard
Target Server node-a
Switchback Type intelligent
Template Priority 1
Target Priority 10
Extend comm/ec2 Resource Hierarchy Wizard
EC2 Resource Tag ec2-sps-ers

Once the IP resource hierarchy has been successfully created, the LifeKeeper GUI should resemble the following image:

Add Entries to /etc/hosts

Add the following entries to /etc/hosts on node-a and node-b to allow resolution of the virtual host names to their corresponding IP addresses. The entry for sps-ascs must also be added on node-d and node-e (the PAS and AAS hosts), as this virtual host name will be used to access the /export/sapmnt/SPS and /export/usr/sap/trans shared file systems.

10.10.10.10    sps-ascs
10.10.10.20    sps-ers

フィードバック

フィードバックありがとうございました

このトピックへフィードバック

送信