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
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/sap/high-availability-guide-suse-multi-sid.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,8 +109,6 @@ The following list shows the configuration of the (A)SCS and ERS load balancer f
109
109
* IP address for NW1: 10.3.1.14
110
110
* IP address for NW2: 10.3.1.16
111
111
* IP address for NW3: 10.3.1.13
112
-
* Backend configuration
113
-
* Connected to primary network interfaces of all virtual machines that should be part of the (A)SCS/ERS cluster
114
112
* Probe Ports
115
113
* Port 620<strong><nr></strong>, therefore for NW1, NW2, and NW3 probe ports 620**00**, 620**10** and 620**20**
116
114
* Load-balancing rules -
@@ -131,8 +129,6 @@ The following list shows the configuration of the (A)SCS and ERS load balancer f
131
129
* IP address for NW1 10.3.1.15
132
130
* IP address for NW2 10.3.1.17
133
131
* IP address for NW3 10.3.1.19
134
-
* Backend configuration
135
-
* Connected to primary network interfaces of all virtual machines that should be part of the (A)SCS/ERS cluster
136
132
* Probe Port
137
133
* Port 621<strong><nr></strong>, therefore for NW1, NW2, and N# probe ports 621**02**, 621**12** and 621**22**
138
134
* Load-balancing rules - create one for each instance, that is, NW1/ERS, NW2/ERS and NW3/ERS.
@@ -144,6 +140,9 @@ The following list shows the configuration of the (A)SCS and ERS load balancer f
144
140
* 5<strong><nr></strong>14 TCP
145
141
* 5<strong><nr></strong>16 TCP
146
142
143
+
* Backend configuration
144
+
* Connected to primary network interfaces of all virtual machines that should be part of the (A)SCS/ERS cluster
145
+
147
146
148
147
> [!Note]
149
148
> When VMs without public IP addresses are placed in the backend pool of internal (no public IP address) Standard Azure load balancer, there will be no outbound internet connectivity, unless additional configuration is performed to allow routing to public end points. For details on how to achieve outbound connectivity see [Public endpoint connectivity for Virtual Machines using Azure Standard Load Balancer in SAP high-availability scenarios](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-standard-load-balancer-outbound-connections).
0 commit comments