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/expressroute/expressroute-howto-routing-arm.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,6 +117,13 @@ This section helps you create, get, update, and delete the Microsoft peering con
117
117
* Customer ASN: If you are advertising prefixes that are not registered to the peering AS number, you can specify the AS number to which they are registered.
118
118
* An MD5 hash if you choose to use one.
119
119
120
+
> [!IMPORTANT]
121
+
> Microsoft verifies if the specified 'Advertised public prefixes' and 'Peer ASN' (or 'Customer ASN') are assigned to you in the Internet Routing Registry. If you are getting the public prefixes from another entity and if the assignment is not recorded with the routing registry, the automatic validation will not complete and will require manual validation. If the automatic validation fails, you will see 'AdvertisedPublicPrefixesState' as 'Validation needed' on the output of "Get-AzExpressRouteCircuitPeeringConfig" (see "To get Microsoft peering details" below) command.
122
+
>
123
+
> If you see the message 'Validation needed', collect the document(s) that show the public prefixes are assigned to your organization by the entity that is listed as the owner of the prefixes in the routing registry and submit these documents for manual validation by opening a support ticket as shown below.
124
+
>
125
+
>
126
+
120
127
Use the following example to configure Microsoft peering for your circuit:
Copy file name to clipboardExpand all lines: articles/expressroute/expressroute-howto-routing-portal-resource-manager.md
+74-49Lines changed: 74 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,13 @@
1
1
---
2
2
title: 'Configure peering for a circuit - ExpressRoute: Azure | Microsoft Docs'
3
3
description: This article documents the steps for creating and provisioning ExpressRoute private and Microsoft peering. This article also demonstrates how to check the status, update, or delete peerings for a circuit.
4
+
4
5
services: expressroute
5
6
author: mialdrid
6
7
7
8
ms.service: expressroute
8
9
ms.topic: conceptual
9
-
ms.date: 06/28/2019
10
+
ms.date: 05/20/2019
10
11
ms.author: mialdrid
11
12
ms.custom: seodec18
12
13
@@ -51,17 +52,9 @@ This section helps you create, get, update, and delete the Microsoft peering con
51
52
52
53
### To create Microsoft peering
53
54
54
-
1. Configure the ExpressRoute circuit. Check the **Provider status** to ensure that the circuit is fully provisioned by the connectivity provider before continuing further.
55
-
56
-
If your connectivity provider offers managed Layer 3 services, you can ask your connectivity provider to enable Microsoft peering for you. In that case, you won't need to follow the instructions listed in the next sections. However, if your connectivity provider does not manage routing for you, after creating your circuit, proceed with these steps.
57
-
58
-
**Circuit - Provider status: Not provisioned**
59
-
60
-
[![](./media/expressroute-howto-routing-portal-resource-manager/not-provisioned-m.png"Provider status: Not provisioned")](./media/expressroute-howto-routing-portal-resource-manager/not-provisioned-m-lightbox.png#lightbox)
61
-
62
-
**Circuit - Provider status: Provisioned**
55
+
1. Configure the ExpressRoute circuit. Ensure that the circuit is fully provisioned by the connectivity provider before continuing further. If your connectivity provider offers managed Layer 3 services, you can ask your connectivity provider to enable Microsoft peering for you. In that case, you won't need to follow the instructions listed in the next sections. However, if your connectivity provider does not manage routing for you, after creating your circuit, proceed with the next steps.
63
56
64
-
[![](./media/expressroute-howto-routing-portal-resource-manager/provisioned-m.png"Provider status = Provisioned")](./media/expressroute-howto-routing-portal-resource-manager/provisioned-m-lightbox.png#lightbox)
57
+
65
58
2. Configure Microsoft peering for the circuit. Make sure that you have the following information before you proceed.
66
59
67
60
* A /30 subnet for the primary link. This must be a valid public IPv4 prefix owned by you and registered in an RIR / IRR. From this subnet you will assign the first useable IP address to your router as Microsoft uses the second useable IP for its router.
@@ -74,83 +67,87 @@ This section helps you create, get, update, and delete the Microsoft peering con
74
67
***Optional -** An MD5 hash if you choose to use one.
75
68
3. You can select the peering you wish to configure, as shown in the following example. Select the Microsoft peering row.
76
69
77
-
[![Select the Microsoft peering row](./media/expressroute-howto-routing-portal-resource-manager/select-peering-m.png"Select the Microsoft peering row")](./media/expressroute-howto-routing-portal-resource-manager/select-peering-m-lightbox.png#lightbox)
78
-
4. Configure Microsoft peering. **Save** the configuration once you have specified all parameters. The following image shows an example configuration:
4. Configure Microsoft peering. The following image shows a configuration example:
79
72
80
-
73
+
74
+
5. Save the configuration once you have specified all parameters.
81
75
82
-
If your circuit gets to a 'Validation needed' state, you must open a support ticket to show proof of ownership of the prefixes to our support team. You can open a support ticket directly from the portal, as shown in the following example:
76
+
> [!IMPORTANT]
77
+
> Microsoft verifies if the specified 'Advertised public prefixes' and 'Peer ASN' (or 'Customer ASN') are assigned to you in the Internet Routing Registry. If you are getting the public prefixes from another entity and if the assignment is not recorded with the routing registry, the automatic validation will not complete and will require manual validation. If the automatic validation fails, you will see the message 'Validation needed'.
78
+
>
79
+
> If you see the message 'Validation needed', collect the document(s) that show the public prefixes are assigned to your organization by the entity that is listed as the owner of the prefixes in the routing registry and submit these documents for manual validation by opening a support ticket as shown below.
80
+
>
81
+
>
83
82
84
-
83
+
If your circuit gets to a 'Validation needed' state (as shown in the image), you must open a support ticket to show proof of ownership of the prefixes to our support team.
85
84
86
-
5. After the configuration has been accepted successfully, you'll see something similar to the following image:
85
+
[![View Microsoft peering properties](./media/expressroute-howto-routing-portal-resource-manager/view-peering-m.png"View properties")](./media/expressroute-howto-routing-portal-resource-manager/view-peering-m-lightbox.png#lightbox)
95
102
### <aname="updatemsft"></a>To update Microsoft peering configuration
96
103
97
-
You can select the row for the peering that you want to modify, then modify the peering properties and save your modifications.
104
+
You can select the row for peering and modifythe peering properties.
This section helps you create, get, update, and delete the Azure private peering configuration for an ExpressRoute circuit.
110
117
111
118
### To create Azure private peering
112
119
113
-
1. Configure the ExpressRoute circuit. Ensure that the circuit is fully provisioned by the connectivity provider before continuing.
114
-
115
-
If your connectivity provider offers managed Layer 3 services, you can ask your connectivity provider to enable Azure private peering for you. In that case, you won't need to follow the instructions listed in the next sections. However, if your connectivity provider does not manage routing for you, after creating your circuit, proceed with the next steps.
116
-
117
-
**Circuit - Provider status: Not provisioned**
118
-
119
-
[![](./media/expressroute-howto-routing-portal-resource-manager/not-provisioned-p.png"Provider status = Not Provisioned")](./media/expressroute-howto-routing-portal-resource-manager/not-provisioned-p-lightbox.png#lightbox)
120
-
121
-
**Circuit - Provider status: Provisioned**
122
-
123
-
[![](./media/expressroute-howto-routing-portal-resource-manager/provisioned-p.png"Provider Status = Provisioned")](./media/expressroute-howto-routing-portal-resource-manager/provisioned-p-lightbox.png#lightbox)
120
+
1. Configure the ExpressRoute circuit. Ensure that the circuit is fully provisioned by the connectivity provider before continuing. If your connectivity provider offers managed Layer 3 services, you can ask your connectivity provider to enable Azure private peering for you. In that case, you won't need to follow the instructions listed in the next sections. However, if your connectivity provider does not manage routing for you, after creating your circuit, proceed with the next steps.
2. Configure Azure private peering for the circuit. Make sure that you have the following items before you proceed with the next steps:
126
124
127
125
* A /30 subnet for the primary link. The subnet must not be part of any address space reserved for virtual networks. From this subnet you will assign the first useable IP address to your router as Microsoft uses the second useable IP for its router.
128
126
* A /30 subnet for the secondary link. The subnet must not be part of any address space reserved for virtual networks. From this subnet you will assign the first useable IP address to your router as Microsoft uses the second useable IP for its router.
129
127
* A valid VLAN ID to establish this peering on. Ensure that no other peering in the circuit uses the same VLAN ID. For both Primary and Secondary links you must use the same VLAN ID.
130
128
* AS number for peering. You can use both 2-byte and 4-byte AS numbers. You can use a private AS number for this peering except for the number from 65515 to 65520, inclusively.
131
-
* You must advertise the routes from your on-premises Edge router to Azure via BGP when you set up the private peering.
132
129
***Optional -** An MD5 hash if you choose to use one.
133
-
3. Select the Azure private peering row, as shown in the following example:
130
+
3. Select the Azure Private peering row, as shown in the following example:
134
131
135
-
[![Select the private peering row](./media/expressroute-howto-routing-portal-resource-manager/select-peering-p.png"Select the private peering row")](./media/expressroute-howto-routing-portal-resource-manager/select-peering-p-lightbox.png#lightbox)
136
-
4. Configure private peering. **Save** the configuration once you have specified all parameters.
5.Save the configuration once you have specified all parameters. After the configuration has been accepted successfully, you see something similar to the following example:
@@ -171,17 +168,45 @@ This section helps you create, get, update, and delete the Azure public peering
171
168
> Azure public peering is deprecated for new circuits. For more information, see [ExpressRoute peering](expressroute-circuit-peerings.md).
172
169
>
173
170
171
+
### To create Azure public peering
172
+
173
+
1. Configure ExpressRoute circuit. Ensure that the circuit is fully provisioned by the connectivity provider before continuing further. If your connectivity provider offers managed Layer 3 services, you can ask your connectivity provider to enable Azure public peering for you. In that case, you won't need to follow instructions listed in the next sections. However, if your connectivity provider does not manage routing for you, after creating your circuit, continue your configuration using the next steps.
174
+
175
+
176
+
2. Configure Azure public peering for the circuit. Make sure that you have the following items before you proceed with the next steps:
177
+
178
+
* A /30 subnet for the primary link. This must be a valid public IPv4 prefix. From this subnet you will assign the first useable IP address to your router as Microsoft uses the second useable IP for its router.
179
+
* A /30 subnet for the secondary link. This must be a valid public IPv4 prefix. From this subnet you will assign the first useable IP address to your router as Microsoft uses the second useable IP for its router.
180
+
* A valid VLAN ID to establish this peering on. Ensure that no other peering in the circuit uses the same VLAN ID. For both Primary and Secondary links you must use the same VLAN ID.
181
+
* AS number for peering. You can use both 2-byte and 4-byte AS numbers.
182
+
***Optional -** An MD5 hash if you choose to use one.
183
+
3. Select the Azure public peering row, as shown in the following image:
184
+
185
+
186
+
4. Configure public peering. The following image shows a configuration example:
187
+
188
+
189
+
5. Save the configuration once you have specified all parameters. After the configuration has been accepted successfully, you see something similar to the following example:
190
+
191
+
192
+
174
193
### <aname="getpublic"></a>To view Azure public peering details
175
194
176
-
View the properties of Azure public peering by selecting the peering.
195
+
You can view the properties of Azure public peering by selecting the peering.
196
+
197
+
177
198
178
199
### <aname="updatepublic"></a>To update Azure public peering configuration
179
200
180
-
Select the row for peering, then modify the peering properties.
201
+
You can select the row for peering and modify the peering properties.
202
+
203
+
181
204
182
205
### <aname="deletepublic"></a>To delete Azure public peering
183
206
184
-
Remove your peering configuration by selecting the delete icon.
207
+
You can remove your peering configuration by selecting the delete icon, as shown in the following example:
208
+
209
+
Copy file name to clipboardExpand all lines: articles/expressroute/howto-routing-cli.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,6 +119,12 @@ You can get configuration details by using the following example:
119
119
```azurecli-interactive
120
120
az network express-route peering show -g ExpressRouteResourceGroup --circuit-name MyCircuit --name AzureMicrosoftPeering
121
121
```
122
+
> [!IMPORTANT]
123
+
> Microsoft verifies if the specified 'Advertised public prefixes' and 'Peer ASN' (or 'Customer ASN') are assigned to you in the Internet Routing Registry. If you are getting the public prefixes from another entity and if the assignment is not recorded with the routing registry, the automatic validation will not complete and will require manual validation. If the automatic validation fails, you will see 'AdvertisedPublicPrefixesState' as 'Validation needed' on the output of the above command.
124
+
>
125
+
> If you see the message 'Validation needed', collect the document(s) that show the public prefixes are assigned to your organization by the entity that is listed as the owner of the prefixes in the routing registry and submit these documents for manual validation by opening a support ticket as shown below.
0 commit comments