Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Storm Control

SUMMARY Read this topic to understand how the broadcast rate limiting feature is implemented by the cloud-native router when deployed in L2 mode.

The storm control or rate limiting feature controls the rate of egress broadcast, unknown unicast, and multicast (BUM) traffic on fabric interfaces.

Configuration Example

You specify the rate limit in bytes per second by adjusting stormControlProfiles in the values.yaml file before deployment.

Once a profile is created, it can be assigned to the interface via the storm-control-profile interface attribute. For example:

The system applies the configured profiles to all specified fabric interfaces in the cloud-native router. The maximum per-interface rate limit value you can set is 1,000,000 bytes per second.

If the unknown unicast, broadcast, or multicast traffic rate exceeds the set limit on a specified fabric interface, the vRouter drops the traffic. You can see the drop counter values by running the dropstats command in the vRouter CLI. You can see the per-interface rate limit drop counters by running the vRouter CLI command vif --get fabric_vif_id --get-drop-stats. For example:

When you configure a rate limit profile on a fabric interface, you can see the configured limit in bytes per second when you run either vif --list or vif --get fabric_vif_id.

  • The rate limit is only configurable on physical interfaces and only during deployment.

  • The existing global rate limit configuration fabricBMCastRateLimit is deprecated from release 22.4.