- play_arrow Port Security
- play_arrow Port Security Overview
-
- play_arrow IPSec
- play_arrow Understanding IPsec and Security Associations
- play_arrow IPsec Configurations and Examples
- play_arrow Configuring IPsec Security Associations
- play_arrow Using Digital Certificates for IPsec
- play_arrow Additional IPsec Options
- play_arrow Configuring IPsec Dynamic Endpoints
- play_arrow Additional ES and AS PIC Configuration Examples
- Example: ES PIC Manual SA Configuration
- Example: AS PIC Manual SA Configuration
- Example: ES PIC IKE Dynamic SA Configuration
- Example: AS PIC IKE Dynamic SA Configuration
- Example: IKE Dynamic SA Between an AS PIC and an ES PIC Configuration
- Example: AS PIC IKE Dynamic SA with Digital Certificates Configuration
- Example: Dynamic Endpoint Tunneling Configuration
-
- play_arrow Digital Certificates
- play_arrow Configuring Digital Certificates
- Public Key Cryptography
- Configuring Digital Certificates
- Configuring Digital Certificates for an ES PIC
- IKE Policy for Digital Certificates on an ES PIC
- Configuring Digital Certificates for Adaptive Services Interfaces
- Configuring Auto-Reenrollment of a Router Certificate
- IPsec Tunnel Traffic Configuration
- Tracing Operations for Security Services
- play_arrow Configuring SSH and SSL Router Access
-
- play_arrow Trusted Platform Module
- play_arrow MACsec
- play_arrow Understanding MACsec
- play_arrow MACsec Examples
-
- play_arrow MAC Limiting and Move Limiting
- play_arrow MAC Limiting and Move Limiting Configurations and Examples
- Understanding MAC Limiting and MAC Move Limiting
- Understanding MAC Limiting on Layer 3 Routing Interfaces
- Understanding and Using Persistent MAC Learning
- Configuring MAC Limiting
- Example: Configuring MAC Limiting
- Verifying That MAC Limiting Is Working Correctly
- Override a MAC Limit Applied to All Interfaces
- Configuring MAC Move Limiting (ELS)
- Verifying That MAC Move Limiting Is Working Correctly
- Verifying That the Port Error Disable Setting Is Working Correctly
-
- play_arrow DHCP Protection
- play_arrow DHCPv4 and DHCPv6
- play_arrow DHCP Snooping
- Understanding DHCP Snooping (ELS)
- Understanding DHCP Snooping (non-ELS)
- Understanding DHCP Snooping Trust-All Configuration
- Enabling DHCP Snooping (non-ELS)
- Configuring Static DHCP IP Addresses
- Example: Protecting Against Address Spoofing and Layer 2 DoS Attacks
- Example: Protecting Against DHCP Snooping Database Attacks
- Example: Protecting Against ARP Spoofing Attacks
- Example: Prioritizing Snooped and Inspected Packet
- Configuring DHCP Security with Q-in-Q Tunneling in Service Provider Style
- play_arrow DHCP Option 82
- play_arrow Dynamic ARP Inspection (DAI)
-
- play_arrow IP Source Guard
- play_arrow Understanding IP Source Guard
- play_arrow IP Source Guard Examples
- Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN
- Example: Configuring IP Source Guard with Other EX Series Switch Features to Mitigate Address-Spoofing Attacks on Untrusted Access Interfaces
- Example: Configuring IP Source Guard and Dynamic ARP Inspection to Protect the Switch from IP Spoofing and ARP Spoofing
- Example: Configuring IPv6 Source Guard and Neighbor Discovery Inspection to Protect a Switch from IPv6 Address Spoofing
- Configuring IP Source Guard to Mitigate the Effects of Source IP Address Spoofing and Source MAC Address Spoofing
- Example: Configuring IP Source Guard and Dynamic ARP Inspection on a Specified Bridge Domain to Protect the Devices Against Attacks
- Example: Configuring IPv6 Source Guard and Neighbor Discovery Inspection to Protect a Switch from IPv6 Address Spoofing
-
- play_arrow IPv6 Access Security
- play_arrow Neighbor Discovery Protocol
- play_arrow SLAAC Snooping
- play_arrow Router Advertisement Guard
-
- play_arrow Control Plane Distributed Denial-of-Service (DDoS) Protection and Flow Detection
- play_arrow Control Plane DDoS Protection
- play_arrow Flow Detection and Culprit Flows
-
- play_arrow Unicast Forwarding
- play_arrow Unicast Reverse Path Forwarding
- play_arrow Unknown Unicast Forwarding
-
- play_arrow Malware Protection
- play_arrow Juniper Malware Removal Tool
-
- play_arrow Configuration Statements and Operational Commands
ON THIS PAGE
Enabling and Disabling Storm Control (ELS)
This task uses Junos OS with support for the Enhanced Layer 2 Software (ELS) configuration style. If your switching device is an EX Series switch and runs software that does not support ELS, see Understanding Storm Control. If your switching device is an EX Series switch and runs software that does support ELS, see Using the Enhanced Layer 2 Software CLI.
On EX4300 switches, the factory default configuration enables storm control on all Layer 2 switch interfaces. The default storm control level is set to 80 percent of the available bandwidth used by the combined broadcast, multicast, and unknown unicast traffic streams.
Storm control is not enabled by default on ACX7000 Series routers, EX9200 switches, and MX Series routers.
You can customize the storm control level for a specific interface. You specify the storm control level as the traffic rate in kilobits per second (Kbps) of the combined traffic streams or as the percentage of available bandwidth used by the combined traffic streams.
You can selectively disable storm control for broadcast, multicast, or unknown unicast traffic on all interfaces or on a specified interface. You can additionally disable storm control on registered or unregistered multicast traffic.
On ACX7000 Series of devices, storm control is supported only at the physical interface level and cannot be applied for known unicast traffic. To disable or unbind storm control profile on ACX7000 series, you need to remove the storm control profile-name from the physical interface.
In the tasks described in this topic, you use the [edit interfaces interface-name unit 0 family ethernet-switching]
hierarchy level to bind the storm control profile for EX Series switches and the [edit
interfaces interface-name unit 0 family bridge]
hierarchy level
to bind the storm control profile for MX Series routers. Starting in Junos OS release 17.4R1 for MX Series routers, you can also configure storm control
on logical systems.
Configuring Storm Control
You can configure storm control for a specific interface. The storm control level can be customized by explicitly configuring either the bandwidth level or the bandwidth percentage.
bandwidth-level
—Configures the storm control level as the bandwidth in kilobits per second of the combined traffic streams.bandwidth-percentage
—Configures the storm control level as a percentage of the available bandwidth used by the combined traffic streams.
You can also configure a limit for burst-size
. The burst size extends the function of the bandwidth limit to allow for bursts of
traffic that exceed the configured bandwidth.
To configure storm control:
Create a storm control profile and set the storm control level as the traffic rate in kilobits per second of the combined traffic streams:
content_copy zoom_out_map[edit forwarding-options] user@device# set storm-control-profiles profile-name all bandwidth-level kbps
Note:The name of the storm control profile can contain no more than 127 characters.
Bind the storm control profile to a logical interface:
For EX Series Switches (Enterprise Style Configuration Only):
content_copy zoom_out_map[edit] user@switch# set interfaces interface-name unit 0 family ethernet-switching storm-control profile-name
For MX Series routers:
Enterprise Style Configuration:
content_copy zoom_out_map[edit] user@device# set interfaces interface-name unit 0 family bridge storm-control profile-name
Service Provider Style Configuration: Starting in Junos OS release 18.3R1, you can configure storm control in the Service Provider Style configuration on MX Series devices.
content_copy zoom_out_map[edit]
content_copy zoom_out_mapuser@device# set interfaces interface-name flexible-vlan-tagging user@device# set interfaces interface-name encapsulation flexible-ethernet-services user@device# set interfaces interface-name unit logical-unit number encapsulation vlan-bridge user@device# set interfaces interface-name unit logical-interface family bridge storm control profile-name
user@host# set interfaces interface-name ether-options ethernet-switch-profile storm-control profile-name
Disabling Storm Control on Registered Multicast Traffic
To disable storm control on only registered multicast traffic:
Disabling Storm Control on Unregistered Multicast Traffic
To disable storm control on only unregistered multicast traffic:
Disabling Storm Control on Unknown Unicast Traffic
To disable storm control on only unknown unicast traffic:
Disabling Storm Control on Multiple Types of Traffic
To disable storm control on multiple types of traffic; for example, broadcast and multicast traffic:
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.