Scenarios Test SAP Clustering Failover

** Team
Activity
Objective
Method
Expected Result
Actual Result
Pass or Not
SAP Clustering Test Scenarios
Stopping HA heartbeat
To simulate heartbeat failure on each node
·         Disable heartbeat on node 1 or node 2
·         Nothing happen. No cluster resource failover. SAP users can work as normal
·         No cluster resource failover. SAP users can work as normal

Starting HA heartbeat
To simulate heartbeat failback on each node
·         Enable heartbeat on node 1 or node 2
·         Nothing happen. No cluster resource failback. SAP users can work as normal
·         No cluster resource failback. SAP users can work as normal

Stopping public network on node 1
To test HA failover on node 2 if node 1's public network is disabled
·         Disable all public network on node 1
·         Node 2 should sense that node1's public is down and should takeover all resources of node 1
·         Cluster resource failover to node 2



Starting public network on node 1
To test HA failback process when node1's public network is enabled
·         Enable all public network on node 1
·         All resource are still activated on node 2 (check node owner)

·         The status of node 1 should be online

·         Failback have to be manually performed
·         Cluster resource still on node 2 ( no failback)

·         node 1’s status  is online

·         Failback done by manual move cluster resource group with MCSG Cluster Admin.

·         Stop SAP CI on Node2 by halt resource

·         Start SAP CI on Node1 by start resource

·         Start SAP DI on Node2

Stopping all public network on node 2
To test HA redundancy interface card on node 2 if node 2's one public network is disabled
·         Disable all public network on node 2
·         Nothing happen. No cluster resource failback. SAP users can work as normal
·         Cluster resource still on node 1

·         Node 2’s status is online

·         Node 2's public interface offline

Starting public network on node 2
To test HA normally  process when node2's public network is enabled
·         Enable all public network on node 2
·         All resource are still activated on node 1 (check node owner)

·         The status of node 2 should be online


·         Cluster resource still on node 1

·         Node 2’s status is online

Power failure on node 1
To test HA failover on node 2 if node 1 suddenly shutdown
·         Turn-off server by pressing the power button located on the server's front panel
·         Node 2 should sense that node 1 is down and should takeover all resources of node 1
·         Cluster resource failover to node 2

Power restore on node 1
To test HA failback process when power is restored and node 1 is properly booted
·         Turn-on server by pressing the power button located on the server's front panel
·         All resource are still activated on node 2 (check node owner)

·         The status of node 1 should be online

·         Failback have to be manually performed
·         No cluster failback to node 1

·         Node 1’s status is online

Power restore on node 2
To test HA failback process when power is restored and node 2 is properly booted
·         Turn-on server by pressing the power button located on the server's front panel
·         All resource are still activated on node 1 (check node owner)

·         The status of node 2 should be online

·         Failback have to be manually performed
·         No Cluster failback to node 2

·         Node 2’s status is online

0 comments:

Loading