Skip to content

Commit 2d32956

Browse files
authored
Merge pull request #206810 from callachun/patch-2
added FAQ per request by russp
2 parents 501fecf + 2da0655 commit 2d32956

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

articles/internet-peering/walkthrough-communications-services-partner.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,9 @@ For optimized routing for your Communication services infrastructure prefixes, y
8181
Please ensure that the prefixes registered are being announced over the direct interconnects established in that location.
8282
If the same prefix is announced in multiple peering locations, it is sufficient to register them with just one of the peerings in order to retrieve the unique prefix keys after validation.
8383

84+
> [!NOTE]
85+
> The Connection State of your peering connections must be Active before registering any prefixes.
86+
8487
**Prefix Registration**
8588

8689
1. If you are an Operator Connect Partner, you would be able to see the “Register Prefix” tab on the left panel of your peering resource page.
@@ -122,6 +125,14 @@ Below are the steps to activate the prefix.
122125

123126
## FAQs:
124127

128+
**Q.** When will my BGP peer come up?
129+
130+
**A.** After the LAG comes up our automated process configures BGP. Note, BFD must be configured on the non-MSFT peer to start route exchange.
131+
132+
**Q.** When will peering IP addresses be allocated and displayed in the Azure portal?
133+
134+
**A.** Our automated process allocates addresses and sends the information via email after the port is configured on our side.
135+
125136
**Q.** I have smaller subnets (</24) for my Communications services. Can I get the smaller subnets also routed?
126137

127138
**A.** Yes, Microsoft Azure Peering service supports smaller prefix routing also. Please ensure that you are registering the smaller prefixes for routing and the same are announced over the interconnects.
@@ -130,6 +141,10 @@ Below are the steps to activate the prefix.
130141

131142
**A.** Microsoft announces all of Microsoft's public service prefixes over these interconnects. This will ensure not only Communications but other cloud services are accessible from the same interconnect.
132143

144+
**Q.** Are there any AS path constraints?
145+
146+
**A.** Yes, for registered prefixes smaller than /24, advertised AS path must be less than four. Path of four or longer will cause the advertisement to be rejected by policy.
147+
133148
**Q.** I need to set the prefix limit, how many routes Microsoft would be announcing?
134149

135150
**A.** Microsoft announces roughly 280 prefixes on internet, and it may increase by 10-15% in future. So, a safe limit of 400-500 can be good to set as “Max prefix count”
@@ -158,6 +173,10 @@ Below are the steps to activate the prefix.
158173

159174
**A.** Time will be variable depending on number and location of sites, and if Peer is migrating existing private peerings or establishing new cabling. Carrier should plan for 3+ weeks.
160175

176+
**Q.** How is progress communicated outside of the portal status?
177+
178+
**A.** Automated emails are sent at varying milestones
179+
161180
**Q.** Can we use APIs for onboarding?
162181

163182
**A.** Currently there is no API support, and configuration must be performed via web portal.

0 commit comments

Comments
 (0)