Create a QoS profile for your tier-1 gateways to define limits on the traffic rates. You can specify the permitted information rate and the burst size to set the limitations. Any traffic that does not conform to the QoS policy, is dropped. QoS profiles can be set for both ingress and egress traffic, for all traffic types (unicast, BUM, IPv4/IPv6). You can choose to create a different profile for each tier-1 gateway.
- From your browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
- Select .
- Click the Gateway QoS Profiles tab.
- Click Add Gateway QoS Profiles.
- Enter a name for the profile.
- Enter the commited bandwidth limit that you want to set for the traffic.
- Enter the burst size. Use the following guidelines for burst size.
The constraints for burst size are:
- B is the burst size in bytes.
- R is the committed rate (or bandwidth) in Mbps.
- I is the time interval in milliseconds, to refill or withdraw tokens(in bytes) from the token bucket. Use the
get dataplanecommand from the NSX Edge CLI to retrieve the time interval, Qos_wakeup_interval_ms. The default value for Qos_wakeup_interval_ms is 50ms. However, this value is automatically adjusted by the dataplane based on the QoS configuration.
B >= R * 1000,000 * I / 1000 / 8because burst size is the maximum amount of tokens that can be refilled in each interval.
B >= R * 1000,000 * 1 / 1000 / 8because the minimum value for I is 1 ms, taking into account dataplane CPU usage among other constraints.
B >= MTU of SR portbecause at least the MTU-size amount of tokens need to be present in the token bucket for an MTU-size packet to pass rate-limiting check.
Max (R * 1000,000 * I / 1000 / 8, R * 1000,000 * 1 / 1000 / 8, MTU)For example, if R = 100 Mbps, I = 50 ms, and MTU = 1500, then
B >= max (100 * 1000,000 * 50 / 1000/ 8, 100 * 1000,000 * 50 / 1000/ 8, 1500) = 625000 in bytes
- Click Save.