You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications
@@ -599,7 +593,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
599
593
600
594
1. **[A]** Update the /usr/sap/sapservices file
601
595
602
-
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
596
+
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
603
597
604
598
```
605
599
sudo vi /usr/sap/sapservices
@@ -611,7 +605,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
If using enqueue server 1 architecture (ENSA1), define the resources as follows:
617
611
@@ -739,7 +733,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
739
733
# rsc_sap_QAS_ERS01 (ocf::heartbeat:SAPInstance): Started anftstsapcl1
740
734
```
741
735
742
-
1.**[A]** Add firewall rules for ASCS and ERS on both nodes
736
+
3.**[A]** Add firewall rules for ASCS and ERS on both nodes
743
737
Add the firewall rules for ASCS and ERS on both nodes.
744
738
```
745
739
# Probe Port of ASCS
@@ -1284,6 +1278,7 @@ Follow these steps to install an SAP application server.
1284
1278
1285
1279
## Next steps
1286
1280
1281
+
* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
1287
1282
*[HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
1288
1283
*[Azure Virtual Machines planning and implementation for SAP][planning-guide]
1289
1284
*[Azure Virtual Machines deployment for SAP][deployment-guide]
# High availability for SAP NetWeaver on Azure VMs on Red Hat Enterprise Linux with NFS on Azure Files
@@ -585,7 +581,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
585
581
586
582
1. **[A]** Update the /usr/sap/sapservices file
587
583
588
-
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
584
+
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
589
585
590
586
```bash
591
587
sudo vi /usr/sap/sapservices
@@ -868,6 +864,7 @@ Thoroughly test your Pacemaker cluster. [Execute the typical failover tests](./h
868
864
869
865
## Next steps
870
866
867
+
* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
871
868
* [HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
872
869
* [Azure Virtual Machines planning and implementation for SAP][planning-guide]
873
870
* [Azure Virtual Machines deployment for SAP][deployment-guide]
# Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux
@@ -481,7 +475,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
481
475
482
476
1.**[A]** Update the /usr/sap/sapservices file
483
477
484
-
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
478
+
To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
485
479
486
480
<pre><code>
487
481
sudo vi /usr/sap/sapservices
@@ -493,7 +487,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
If using enqueue server 1 architecture (ENSA1), define the resources as follows:
499
493
@@ -1036,6 +1030,7 @@ Follow these steps to install an SAP application server.
1036
1030
1037
1031
## Next steps
1038
1032
1033
+
* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
1039
1034
*[HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
1040
1035
*[Azure Virtual Machines planning and implementation for SAP][planning-guide]
1041
1036
*[Azure Virtual Machines deployment for SAP][deployment-guide]
0 commit comments