A company is deploying SAP Business Suite on SAP HANA by using two Amazon EC2 bare metal instances. The company has set up a Pacemaker cluster for SAP HANA. The cluster is set up between the two insta

Question

Options

• ATurn off the source/destination check on each bare metal instance.
• BModify the security groups to ensure that the minimal ports for connectivity between the application
• CAdd a route table entry to the route tables for the subnets of both bare metal instances for the
• DEnsure that both bare metal instances are in the same subnet.
• EPerform a failover and tailback by using the Pacemaker cluster. Check whether the overlay IP
• FMove the Pacemaker cluster to EC2 VM instances instead of bare metal instances.

• A
  81% (30)
• D
  11% (4)
• E
  3% (1)
• F
  5% (2)

Explanation

Three actions are needed to make the overlay (floating) IP reachable from application servers. First (A), source/destination checks must be disabled on both bare metal instances because AWS enforces this check by default - the overlay IP does not match the primary IP of either instance, so packets destined for the overlay IP would be dropped without this change. Second (B), security groups must permit the required ports between the application servers and the database cluster nodes, as security groups are stateful and must explicitly allow traffic on the overlay IP. Third (C), route table entries must be added to route traffic destined for the overlay IP to the active database node's network interface - without this, the VPC has no knowledge of how to reach the overlay IP from other subnets. Both instances do not need to be in the same subnet (D), failover does not fix routing (E), and bare metal instances support Pacemaker clusters (F is unnecessary).

No community discussion yet for this question.