This article explains the behaviour of the storm-control feature on EX4100 switches when interfaces are configured with family inet or encapsulation vlan-bridge.

Storm-control is a Layer 2 feature designed to monitor and limit broadcast, multicast, and unknown unicast traffic received on Ethernet switching ports. As a result, the feature is available only on interfaces operating in Layer 2 mode using family ethernet-switching.

Unable to configure the storm-control statement under an interface configured with:

• family inet
• encapsulation vlan-bridge

The CLI does not present the storm-control option under the above interface families.

Storm-control can be successfully configured when the interface is configured with family ethernet-switching.

{master:0}[edit]
root@Switch# set interfaces ge-0/0/0 unit 0 family inet ?
Possible completions:
  <[Enter]>            Execute this command
> address              Interface address/destination prefix
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don't inherit configuration data from these groups
  arp-max-cache        Max interface ARP nexthop cache size (1..2000000)
  arp-new-hold-limit   Max no. of new unresolved nexthops (1..2000000)
> dhcp                 Dynamic Host Configuration Protocol client configuration
> filter               Packet filtering
  mtu                  Protocol family maximum transmission unit
  no-neighbor-learn    Disable neighbor address learning on interface
  no-redirects         Do not redirect traffic
  primary              Candidate for primary interface in system
> rpf-check            Enable reverse-path-forwarding checks on this interface
> sampling             Interface sampling
> service              Service operations
> simple-filter        Filter for doing multifield classification
> targeted-broadcast   Directed broadcast
  unconditional-src-learn  Glean from arp packets even when source cannot be validated
> unnumbered-address   Unnumbered interface address/destination prefix
  |                    Pipe through a command

This behaviour is expected. Storm control is fundamentally a Layer 2 feature that monitors and limits broadcast, multicast, and unknown unicast traffic received on Ethernet switching ports. Accordingly, interfaces configured with family ethernet-switching are treated as Layer 2 interfaces and support the storm-control feature.

As interfaces configured with family inet operate as Layer 3 routed interfaces, while encapsulation vlan-bridge does not expose the storm-control configuration under the current Junos implementation.

Based on the current implementation, the storm-control feature is supported only on interfaces configured with family ethernet-switching.

{master:0}[edit]
root@Switch# set interfaces ge-0/0/0 unit 0 family ethernet-switching ?          
Possible completions:
  <[Enter]>            Execute this command
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don't inherit configuration data from these groups
> filter               Packet filtering
> inner-vlan           Trunk mode vlan membership for this interface
+ inner-vlan-id-list   Trunk mode VLAN membership for this interface based on inner VLAN tag
  inter-switch-link    PVLAN inter switch link
  interface-mode       Type of interface mode
> recovery-timeout     Recovery timeout for this interface
> storm-control        Storm control profile name to bind
> vlan                 Virtual LAN parameters
  vlan-auto-sense      Enable VLAN auto sense on this interface
> vlan-rewrite         Specify VLAN translation
  |                    Pipe through a command

https://www.juniper.net/documentation/us/en/software/junos/security-services/topics/task/rate-limiting-storm-control-disabling-cli-els.html