Skip to content

Commit 52fc564

Browse files
AnnaMHuffAnnaMHuff
authored
Merge pull request #267233 from code-sidd/gateway
new changes accommodated
2 parents b7ee276 + 02c7f59 commit 52fc564

File tree

2 files changed

+112
-108
lines changed

2 files changed

+112
-108
lines changed

‎articles/mariadb/concepts-connectivity-architecture.md

Lines changed: 56 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -36,59 +36,62 @@ As part of ongoing service maintenance, we'll periodically refresh compute hardw
3636
3737
The following table lists the gateway IP addresses of the Azure Database for MariaDB gateway for all data regions. The most up-to-date information of the gateway IP addresses for each region is maintained in the table below. In the table below, the columns represent following:
3838

39-
* **Region Name:** This column lists the name of Azure region where Azure Database for PostgreSQL - Single Server is offered.
4039
* **Gateway IP address subnets:** This column lists the IP address subnets of the gateway rings located in the particular region. As we retire older gateway hardware, we recommend that you open the client-side firewall to allow outbound traffic for the IP address subnets in the region you're operating.
41-
* **Gateway IP addresses (decommissioning):** This column lists the IP addresses of the gateways hosted on an older generation of hardware that is being decommissioned right now. If you're provisioning a new server, you can ignore these IP addresses. If you have an existing server, continue to retain the outbound rule for the firewall for these IP addresses as we haven't decommissioned it yet. If you drop the firewall rules for these IP addresses, you may get connectivity errors. Instead, you're expected to proactively add the new IP addresses listed in Gateway IP addresses column to the outbound firewall rule as soon as you receive the notification for decommissioning. This will ensure when your server is migrated to latest gateway hardware, there's no interruptions in connectivity to your server.
42-
* **Gateway IP addresses (decommissioned):** This column lists the IP addresses of the gateway rings, which are decommissioned and are no longer in operations. You can safely remove these IP addresses from your outbound firewall rule.
43-
44-
45-
| **Region name** | **Gateway IP address subnets** | **Gateway IP addresses (decommissioning)** | **Gateway IP addresses (decommissioned)** |
46-
|:-----------------------|:--------------------------------------------------------------|:------------------------------------------|:------------------------------------------|
47-
| Australia Central | 20.36.105.32/29 | | |
48-
| Australia Central 2 | 20.36.113.32/29 | | |
49-
| Australia East | 13.70.112.32/29, 40.79.160.32/29, 40.79.168.32/29 | 13.75.149.87 | |
50-
| Australia South East | 13.77.49.32/29 | 13.73.109.251 | |
51-
| Brazil South | 191.233.200.32/29, 191.234.144.32/29 | | 104.41.11.5 |
52-
| Canada Central | 13.71.168.32/29, 20.38.144.32/29, 52.246.152.32/29 | | |
53-
| Canada East | 40.69.105.32/29 | 40.86.226.166 | |
54-
| Central US | 104.208.21.192/29, 13.89.168.192/29, 52.182.136.192/29 | 13.67.215.62 | |
55-
| China East | 52.130.112.136/29 | | |
56-
| China East 2 | 52.130.120.88/29 | | |
57-
| China East 3 | 52.130.128.88/29 | | |
58-
| China North | 52.130.128.88/29 | | |
59-
| China North 2 | 52.130.40.64/29 | | |
60-
| China North 3 | 13.75.32.192/29, 13.75.33.192/29 | | |
61-
| East Asia | 13.75.32.192/29, 13.75.33.192/29 | | |
62-
| East US | 20.42.65.64/29, 20.42.73.0/29, 52.168.116.64/29 | 40.121.158.30 | 191.238.6.43 |
63-
| East US 2 | 104.208.150.192/29, 40.70.144.192/29, 52.167.104.192/29 | 52.177.185.181 | |
64-
| France Central | 40.79.136.32/29, 40.79.144.32/29 | | |
65-
| France South | 40.79.176.40/29, 40.79.177.32/29 | | |
66-
| Germany West Central | 51.116.152.32/29, 51.116.240.32/29, 51.116.248.32/29 | | |
67-
| India Central | 104.211.86.32/29, 20.192.96.32/29 | | |
68-
| India South | 40.78.192.32/29, 40.78.193.32/29 | | |
69-
| India West | 104.211.144.32/29, 104.211.145.32/29 | 104.211.160.80 | |
70-
| Japan East | 13.78.104.32/29, 40.79.184.32/29, 40.79.192.32/29 | 13.78.61.196 | |
71-
| Japan West | 40.74.96.32/29 | 104.214.148.156 | |
72-
| Korea Central | 20.194.64.32/29, 20.44.24.32/29, 52.231.16.32/29 | 52.231.32.42 | |
73-
| Korea South | 52.231.145.0/29 | 52.231.200.86 | |
74-
| North Central US | 52.162.105.192/29 | 23.96.178.199 | |
75-
| North Europe | 13.69.233.136/29, 13.74.105.192/29, 52.138.229.72/29 | 40.113.93.91 | 191.235.193.75 |
76-
| South Africa North | 102.133.120.32/29, 102.133.152.32/29, 102.133.248.32/29 | | |
77-
| South Africa West | 102.133.25.32/29 | | |
78-
| South Central US | 20.45.121.32/29, 20.49.88.32/29, 20.49.89.32/29, 40.124.64.136/29 | 13.66.62.124 | 23.98.162.75 |
79-
| South East Asia | 13.67.16.192/29, 23.98.80.192/29, 40.78.232.192/29 | 104.43.15.0 | |
80-
| Switzerland North | 51.107.56.32/29, 51.103.203.192/29, 20.208.19.192/29, 51.107.242.32/27 | | |
81-
| Switzerland West | 51.107.153.32/29 | | |
82-
| UAE Central | 20.37.72.96/29, 20.37.73.96/29 | | |
83-
| UAE North | 40.120.72.32/29, 65.52.248.32/29 | | |
84-
| UK South | 51.105.64.32/29, 51.105.72.32/29, 51.140.144.32/29 | | |
85-
| UK West | 51.140.208.96/29, 51.140.209.32/29 | | |
86-
| West Central US | 13.71.193.32/29 | 13.78.145.25 | |
87-
| West Europe | 104.40.169.32/29, 13.69.112.168/29, 52.236.184.32/29 | 40.68.37.158 | 191.237.232.75 |
88-
| West US | 13.86.217.224/29 | 104.42.238.205 | 23.99.34.75 |
89-
| West US 2 | 13.66.136.192/29, 40.78.240.192/29, 40.78.248.192/29 | | |
90-
| West US 3 | 20.150.168.32/29, 20.150.176.32/29, 20.150.184.32/29 | | |
91-
40+
* **Gateway IP addresses**: Periodically, individual **Gateway IP addresses** will be retired and traffic will be migrated to corresponding **Gateway IP address subnets**.
41+
42+
We strongly encourage customers to move away from relying on any individual Gateway IP address (since these will be retired in the future). Instead allow network traffic to reach both the individual Gateway IP addresses and Gateway IP address subnets in a region.
43+
44+
45+
| **Region name** | **Gateway IP address(es)** | **Gateway IP address Subnets** |
46+
|:-------------------------|:----------------------------------------------------------------|:--------------------------------------------|
47+
| Australia Central | 20.36.105.32 | 20.36.105.32/29, 20.53.48.96/27 |
48+
| Australia Central 2 | 20.36.113.32 | 20.36.113.32/29, 20.53.56.32/27 |
49+
| Australia East | 13.70.112.32, 40.79.160.32, 40.79.168.32 | 13.70.112.32/29, 40.79.160.32/29, 40.79.168.32/29, 20.53.46.128/27 |
50+
| Australia Southeast | 13.77.49.33 | 13.77.49.32/29, 104.46.179.160/27 |
51+
| Brazil South | 191.233.201.8, 191.233.200.16 | 191.234.153.32/27, 191.234.152.32/27, 191.234.157.136/29, 191.233.200.32/29, 191.234.144.32/29, 191.234.142.160/27 |
52+
| Canada Central | 13.71.168.32 | 13.71.168.32/29, 20.38.144.32/29, 52.246.152.32/29, 20.48.196.32/27 |
53+
| Canada East | 40.69.105.32 | 40.69.105.32/29, 52.139.106.192/27 |
54+
| Central US | 104.208.21.192, 13.89.168.192, 52.182.136.192 | 104.208.21.192/29, 13.89.168.192/29, 52.182.136.192/29, 20.40.228.128/27 |
55+
| China East | 52.130.112.139 | 52.130.112.136/29, 52.130.13.96/27 |
56+
| China East 2 | 40.73.82.1, 52.130.120.89 | 52.130.120.88/29, 52.130.7.0/27 |
57+
| China East 3 | 52.130.128.89 | 52.130.128.88/29, 40.72.77.128/27 |
58+
| China North | 52.130.128.89 | 52.130.128.88/29, 40.72.77.128/27 |
59+
| China North 2 | 40.73.50.0 | 52.130.40.64/29, 52.130.21.160/27 |
60+
| China North 3 | 13.75.32.192, 13.75.33.192 | 13.75.32.192/29, 13.75.33.192/29 |
61+
| East Asia | 13.75.33.20, 13.75.33.21 | 20.205.77.176/29, 20.205.83.224/29, 20.205.77.200/29, 13.75.32.192/29, 13.75.33.192/29, 20.195.72.32/27 |
62+
| East US | 20.42.65.64, 20.42.73.0, 52.168.116.64 | 20.42.65.64/29, 20.42.73.0/29, 52.168.116.64/29, 20.62.132.160/27 |
63+
| East US 2 | 104.208.150.192, 40.70.144.192, 52.167.104.192 | 104.208.150.192/29, 40.70.144.192/29, 52.167.104.192/29, 20.62.58.128/27 |
64+
| France Central | 40.79.129.1 | 40.79.128.32/29, 40.79.136.32/29, 40.79.144.32/29, 20.43.47.192/27 |
65+
| France South | 40.79.176.40 | 40.79.176.40/29, 40.79.177.32/29, 52.136.185.0/27 |
66+
| Germany West Central | 51.116.152.0 | 51.116.152.32/29, 51.116.240.32/29, 51.116.248.32/29, 51.116.149.32/27 |
67+
| India Central | 104.211.86.32, 20.192.96.33 | 40.80.48.32/29, 104.211.86.32/29, 20.192.96.32/29, 20.192.43.160/27 |
68+
| India South | 40.78.192.32 | 40.78.192.32/29, 40.78.193.32/29, 52.172.113.96/27 |
69+
| India West | 104.211.144.32 | 104.211.144.32/29, 104.211.145.32/29, 52.136.53.160/27 |
70+
| Japan East | 40.79.184.8, 40.79.192.23 | 13.78.104.32/29, 40.79.184.32/29, 40.79.192.32/29, 20.191.165.160/27 |
71+
| Japan West | 40.74.96.6 | 20.18.179.192/29, 40.74.96.32/29, 20.189.225.160/27 |
72+
| Korea Central | 52.231.17.13 | 20.194.64.32/29, 20.44.24.32/29, 52.231.16.32/29, 20.194.73.64/27 |
73+
| Korea South | 52.231.145.3 | 52.231.151.96/27, 52.231.151.88/29, 52.231.145.0/29, 52.147.112.160/27 |
74+
| North Central US | 52.162.104.35, 52.162.104.36 | 52.162.105.200/29, 20.125.171.192/29, 52.162.105.192/29, 20.49.119.32/27 |
75+
| North Europe | 52.138.224.6, 52.138.224.7 | 13.69.233.136/29, 13.74.105.192/29, 52.138.229.72/29, 52.146.133.128/27 |
76+
| Norway East | 51.120.96.0 | 51.120.208.32/29, 51.120.104.32/29, 51.120.96.32/29, 51.120.232.192/27 |
77+
| Norway West | 51.120.216.0 | 51.120.217.32/29, 51.13.136.224/27 |
78+
| South Africa North | 102.133.152.0 | 102.133.120.32/29, 102.133.152.32/29, 102.133.248.32/29, 102.133.221.224/27 |
79+
| South Africa West | 102.133.24.0 | 102.133.25.32/29, 102.37.80.96/27 |
80+
| South Central US | 20.45.120.0 | 20.45.121.32/29, 20.49.88.32/29, 20.49.89.32/29, 40.124.64.136/29, 20.65.132.160/27 |
81+
| Southeast Asia | 23.98.80.12, 40.78.233.2 | 13.67.16.192/29, 23.98.80.192/29, 40.78.232.192/29, 20.195.65.32/27 |
82+
| Sweden Central | 51.12.96.32 | 51.12.96.32/29, 51.12.232.32/29, 51.12.224.32/29, 51.12.46.32/27 |
83+
| Sweden South | 51.12.200.32 | 51.12.201.32/29, 51.12.200.32/29, 51.12.198.32/27 |
84+
| Switzerland North | 51.107.56.0 | 51.107.56.32/29, 51.103.203.192/29, 20.208.19.192/29, 51.107.242.32/27 |
85+
| Switzerland West | 51.107.152.0 | 51.107.153.32/29, 51.107.250.64/27 |
86+
| UAE Central | 20.37.72.64 | 20.37.72.96/29, 20.37.73.96/29, 20.37.71.64/27 |
87+
| UAE North | 65.52.248.0 | 20.38.152.24/29, 40.120.72.32/29, 65.52.248.32/29, 20.38.143.64/27 |
88+
| UK South | 51.105.64.0 | 51.105.64.32/29, 51.105.72.32/29, 51.140.144.32/29, 51.143.209.224/27 |
89+
| UK West | 51.140.208.98 | 51.140.208.96/29, 51.140.209.32/29, 20.58.66.128/27 |
90+
| West Central US | 13.71.193.34 | 13.71.193.32/29, 20.69.0.32/27 |
91+
| West Europe | 13.69.105.208, 104.40.169.187 | 104.40.169.32/29, 13.69.112.168/29, 52.236.184.32/29, 20.61.99.192/27 |
92+
| West US | 13.86.216.212, 13.86.217.212 | 20.168.163.192/29, 13.86.217.224/29, 20.66.3.64/27 |
93+
| West US 2 | 13.66.136.192 | 13.66.136.192/29, 40.78.240.192/29, 40.78.248.192/29, 20.51.9.128/27 |
94+
| West US 3 | 20.150.184.2 | 20.150.168.32/29, 20.150.176.32/29, 20.150.184.32/29, 20.150.241.128/27 |
9295

9396

9497
## Connection redirection
@@ -128,8 +131,7 @@ This indicates that your applications connect to server using static IP address
128131

129132
### Is there any impact for my application connections?
130133

131-
This maintenance is just a DNS change, so it's transparent to the client. Once the DNS cache is refreshed in the client (automatically done by operation system), all the new connections connect to the new IP address and all the existing connections will still work fine until the old IP address is fully decommissioned, which happens several weeks later. And the retry logic isn't required for this case, but it's good to see the application have retry logic configured. Either use FQDN to connect to the database server or enable list the new 'Gateway IP addresses' in your application connection string.
132-
This maintenance operation won't drop the existing connections. It only makes the new connection requests go to new gateway ring.
134+
This maintenance is just a DNS change, so it's transparent to the client. Once the DNS cache is refreshed in the client (automatically done by operation system), all the new connections connect to the new IP address and all the existing connections will still work fine until the old IP address is fully decommissioned, which happens several weeks later. And the retry logic isn't required for this case, but it's good to see the application have retry logic configured. Use FQDN to connect to the database server in your application connection string. This maintenance operation won't drop the existing connections. It only makes the new connection requests go to new gateway ring.
133135

134136
### Can I request for a specific time window for the maintenance?
135137

0 commit comments

Comments
 (0)