Remove warning that fenced VM can take 15 minutes to restart(obsolete warning)

Author: rdeltcheva

articles/virtual-machines/workloads/sap/sap-hana-high-availability-rhel.md

@@ -12,7 +12,7 @@ ms.service: virtual-machines-linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 03/31/2020
+ms.date: 05/21/2020
 ms.author: radeltch
 
 ---
@@ -706,9 +706,6 @@ See [Red Hat Knowledgebase article 79523](https://access.redhat.com/solutions/79
 The virtual machine should now restart or stop depending on your cluster configuration.
 If you set the `stonith-action` setting to off, the virtual machine is stopped and the resources are migrated to the running virtual machine.
 
-> [!NOTE]
-> It can take up to 15 minutes until the virtual machines is online again.
-
 After you start the virtual machine again, the SAP HANA resource fails to start as secondary if you set `AUTOMATED_REGISTER="false"`. In this case, configure the HANA instance as secondary by executing this command:
 
 <pre><code>su - <b>hn1</b>adm
@@ -779,6 +776,26 @@ Resource Group: g_ip_HN1_03
     vip_HN1_03 (ocf::heartbeat:IPaddr2):       Started hn1-db-1
 </code></pre>
 
+### Test a manual failover
+
+Resource state before starting the test:
+
+<pre><code>Clone Set: SAPHanaTopology_HN1_03-clone [SAPHanaTopology_HN1_03]
+    Started: [ hn1-db-0 hn1-db-1 ]
+Master/Slave Set: SAPHana_HN1_03-master [SAPHana_HN1_03]
+    Masters: [ hn1-db-0 ]
+    Slaves: [ hn1-db-1 ]
+Resource Group: g_ip_HN1_03
+    nc_HN1_03  (ocf::heartbeat:azure-lb):      Started hn1-db-0
+    vip_HN1_03 (ocf::heartbeat:IPaddr2):       Started hn1-db-0
+</code></pre>
+
+You can test a manual failover by stopping the cluster on the hn1-db-0 node:
+
+<pre><code>[root@hn1-db-0 ~]# pcs cluster stop
+</code></pre>
+
+
 ## Next steps
 
 * [Azure Virtual Machines planning and implementation for SAP][planning-guide]