Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Cloud-Native Router User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Storm Control

Release: JCNR 23.3
{}
Change Release
date_range 15-Oct-23

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.

content_copy zoom_out_map
 # rate limit profiles for bum traffic on fabric interfaces in bytes per second
  stormControlProfiles:
    rate_limit_pf1:
      bandwidth:
        level: 0

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

content_copy zoom_out_map
- eth1:
      ddp: on
      interface_mode: trunk
      vlan-id-list: [100, 200, 300, 700-705]
      storm-control-profile: rate_limit_pf1
      native-vlan-id: 100
      no-local-switching: true

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:

content_copy zoom_out_map
dropstats
L2 untag pkt drop             8832
L2 Src Mac lookup fail        880
Rate limit exceeded 29312474

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.

content_copy zoom_out_map
vif0/2         PCI: 0000: af: 01.1 (Speed 10000, Duplex 1)
               Type: Physical HWaddr: 76:5d: f5: f5: c1:7a
               Vrf:0 Flags: L2Vof QOS:-1 Ref: 8 BUM Rate Limit: 1000000
               RX port    packets:1 errors:0
               RX queue packets:1 errors:0
               RX queue errors to lore 000000000000
               Driver: net_iavf 
               Fabric Interface: 0000:af:01.1 Status: UP
               Vlan Mode: Trunk Vlan: 300 500 600
               RX packets:0  bytes:0 errors:1                      						        
               TX packets:0 bytes:0 errors:0
               Drops: 1
Note:
  • 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.

footer-navigation