Training
Module
Introduction to Azure ExpressRoute - Training
This module explains what Azure ExpressRoute does, how it works, and when you should choose to use Azure ExpressRoute as a solution.
About rate limiting for ExpressRoute circuits over service provider ports
This article discusses how rate limiting works for ExpressRoute circuits created over service provider ports. You'll also learn how to monitor the throughput and traffic drop due to rate limiting.
An ExpressRoute circuit consists of two links that connects the Customer or Provider edge to the Microsoft Enterprise Edge (MSEE) routers. With a circuit bandwidth of 1 Gbps and traffic distributed evenly across both links, a maximum throughput of 2 Gbps (twice the 1 Gbps) can be achieved. However, rate limiting will restrict your throughput to the configured bandwidth if it is exceeded on either link. It is important to note that the excess 1 Gbps in this example serves as redundancy to prevent service disruptions during any link or device maintenance periods.
You can monitor the ingress and egress throughput of your ExpressRoute circuit for both links through the Azure portal using ExpressRoute circuit metrics. For ingress, select BitsInPerSecond and for egress, select BitsOutPerSecond. The following screenshot shows the ExpressRoute circuit metrics for ingress and egress throughput.
You can monitor the traffic that is being dropped due to rate limiting through the Azure portal using the ExpressRoute circuit QOS metrics. For ingress, select DroppedInBitsPerSecond and for egress, select DroppedOutBitsPerSecond. The following screenshot shows the ExpressRoute circuit QOS metrics for ingress and egress throughput.
You can seamlessly increase your circuit bandwidth through the Azure portal. For more information, see About upgrading ExpressRoute circuit bandwidth.
ExpressRoute circuit throughput is monitored at an aggregate level of every few minutes, while the rate limiting is enforced at a granular level in milliseconds. Therefore, occasional traffic bursts exceeding the configured bandwidth might not get detected by the throughput monitoring. However, the rate limiting is still being enforced and traffic gets dropped.
For more frequently asked questions, see ExpressRoute FAQ.