Skip to content

Commit 0a70583

Browse files
authored
Update expressroute-faqs.md
add q&A for prefix limits
1 parent c0aedab commit 0a70583

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/expressroute/expressroute-faqs.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,18 @@ If you're using a dual-stack circuit, there's a maximum of 100 IPv6 prefixes on
6868

6969
The connection between the ExpressRoute circuit and the gateway disconnects including peered virtual network using gateway transit. Connectivity re-establishes when the prefix limit is no longer exceeded.
7070

71+
## How can I adjust the number of prefixes advertised to the gateway to ensure it is within the maximum limitation?
72+
73+
ExpressRoute supports up to 11,000 routes, covering virtual network address spaces, on-premises networks, and virtual network peering connections. If the ExpressRoute gateway exceeds this limit, please update the prefixes to be within the allowed range.
74+
75+
To make this change in the Azure Portal:
76+
1. Go to the Advisor resource and select the "Performance" pillar.
77+
2. Click on the recommendation for "Max prefix reached for ExpressRoute Gateway."
78+
3. Select the Gateway with this recommendation.
79+
4. In the Gateway resource, select the "Virtual network" that the Gateway is attached to
80+
5. In the Virtual Network resource, select "Address Space" blade under settings on the left menu
81+
6. Reduce the advertised address space to within the limit
82+
7183
### Can routes from the on-premises network get filtered?
7284

7385
The only way to filter or include routes is on the on-premises edge router. User-defined routes can be added in the VNet to affect specific routing, but is only static and not part of the BGP advertisement.

0 commit comments

Comments
 (0)