Skip to content

Commit 908ce3a

Browse files
committed
Update the ILB creation instructions in HA articles to clarify that 2nd ILB is not needed
1 parent 3b718cb commit 908ce3a

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/virtual-machines/workloads/sap/high-availability-guide-suse-multi-sid.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,6 @@ The following list shows the configuration of the (A)SCS and ERS load balancer f
109109
* IP address for NW1: 10.3.1.14
110110
* IP address for NW2: 10.3.1.16
111111
* 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
114112
* Probe Ports
115113
* Port 620<strong>&lt;nr&gt;</strong>, therefore for NW1, NW2, and NW3 probe ports 620**00**, 620**10** and 620**20**
116114
* Load-balancing rules -
@@ -131,8 +129,6 @@ The following list shows the configuration of the (A)SCS and ERS load balancer f
131129
* IP address for NW1 10.3.1.15
132130
* IP address for NW2 10.3.1.17
133131
* 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
136132
* Probe Port
137133
* Port 621<strong>&lt;nr&gt;</strong>, therefore for NW1, NW2, and N# probe ports 621**02**, 621**12** and 621**22**
138134
* 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
144140
* 5<strong>&lt;nr&gt;</strong>14 TCP
145141
* 5<strong>&lt;nr&gt;</strong>16 TCP
146142

143+
* Backend configuration
144+
* Connected to primary network interfaces of all virtual machines that should be part of the (A)SCS/ERS cluster
145+
147146

148147
> [!Note]
149148
> 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

Comments
 (0)