- 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 Unicast Forwarding
- play_arrow Unicast Reverse Path Forwarding
- play_arrow Unknown Unicast Forwarding
-
- play_arrow Storm Control
- play_arrow Malware Protection
- play_arrow Juniper Malware Removal Tool
-
- play_arrow Configuration Statements and Operational Commands
Configuring Control Plane DDoS Protection
Control plane DDoS protection is enabled by
default for all supported protocol groups and packet types. Devices
have default values for bandwidth (packet rate in pps), bandwidth
scale, burst (number of packets in a burst), burst scale, priority,
and recover time. To see the default policer values for all supported
protocol groups and packet types, run the show ddos-protection protocols CLI
command before modifying any configurable DDoS protection values.
EX2300 and EX2300-C switches might have control plane DDoS protection but don’t support CLI options to show or change the default policer parameters.
Starting in Junos OS Release 24.2R1 the EX4100 and EX4400 devices and starting in Junos OS Release 24.4R1 the EX3400 and EX4300-MP devices support CLI options to show or change the default policer parameters.
You can change the control plane DDoS configuration parameters as follows:
For individual packet types supported within a protocol group, you can change bandwidth (pps), burst (packets), and priority policer values.
Note:On PTX10003 and PTX10008 routers, you can change default bandwidth (pps) and burst (packets) values for aggregate or packet type policers, but not priority values.
For the aggregate policer for a protocol group, you can change bandwidth (pps) and burst (packets) policer values.
When you set bandwidth (pps), burst (packets), and priority values for a protocol group or packet type policer, the same values apply at all policer levels. Change the scaling configuration options to tune those values at the Packet Forwarding Engine level.
Note:ACX Series routers with control plane DDoS protection support changing policer values at the Routing Engine level, which propagates down to the PFE chipset level. They don’t support the line card scaling configuration options at the
[edit system ddos-protection protocols protocol-group aggregate fpcstatement hierarchy.
You can disable control plane DDoS protection as follows:
On most routing devices that have policers at the Routing Engine level, you can disable control plane DDoS protection at the Routing Engine and for all line cards either globally or for individual packet types within a protocol group.
PTX10003, PTX10008 and PTX10016 routers include policers at the Routing Engine level, but like other PTX Series routers, you can only disable line-card policers.
On other PTX Series routers and QFX Series switches, policers are supported only at the line cards, so on these devices you can disable control plane DDoS protection for all line cards either globally or for individual packet types within a protocol group.
Control plane DDoS logging is enabled by default, but you can disable it globally for all control plane DDoS events or for individual packet types within a protocol group. You can also configure tracing operations for monitoring control plane DDoS events.
MX Series routers with MPCs and T4000 routers with FPC5s support control plane DDoS protection. The CLI accepts the configuration if other line cards are also installed on either of these types of routers, but the other line cards are not protected so the router is essentially not protected.
To change default-configured control plane DDoS protection parameters:
(Optional) Configure global control plane DDoS protection settings or disable control plane DDoS protection.
(Optional) Configure control plane DDoS protection settings for the aggregate policer or individual packet types for the desired protocol groups.
(Optional) Configure tracing for control plane DDoS protection operations.
Disabling Control Plane DDoS Protection Policers and Logging Globally
Control plane DDoS protection policers are enabled by default for all supported protocol groups and packet types.
On ACX Series routers, you can disable policers globally or for individual protocol groups at the Routing Engine level. Disabling policers globally essentially disables control plane DDoS protection on the device.
On MX Series routers, T4000 routers, and EX9200 switches, policers are established at the level of the individual line card and the Routing Engine. You can disable the line card policers globally for all MPCs or FPC5s. You can also disable the Routing Engine policer. When you disable either of these policers, the policers at that level for all protocol groups and packet types are disabled.
On PTX Series routers and QFX Series switches, policers are established at the level of individual line cards only. If you disable line-card policers globally, control plane DDoS protection is disabled on the switch.
PTX10003, PTX10008 and PTX10016 routers include policers at the Routing Engine level, but like other PTX Series routers, you can only disable line-card policers.
Control plane DDoS protection logging is also enabled by default. You can disable all control plane DDoS event logging (including flow detection event logging) for all protocol groups and packet types across the router or switch.
The global configuration for disabling policers and logging overrides any local configuration for packet types.
To configure global control plane DDoS protection settings:
Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers
Control plane DDoS policers are applied to control packet traffic and are enabled by default for all supported protocol groups and packet types. You can change default policer parameters to configure different values for the maximum allowed traffic rate, maximum burst size, traffic priority, and how much time must pass since the last violation before the traffic flow is considered to have recovered from the attack. You can also scale the bandwidth and burst values for individual line cards so that the policers at this level trigger at lower thresholds than the overall protocol or packet thresholds.
Protocol group and packet type support varies across platforms and Junos OS releases, as follows:
For most routing devices, see protocols (DDoS).
For ACX Series routers, PTX Series routers and QFX Series switches, see protocols (DDoS) (ACX Series, PTX Series, and QFX Series).
You can configure aggregate policer values for any protocol group. The aggregate policer applies to the combination of all types of control packet traffic for that group.
ACX Series routers only support the aggregate policer for any supported protocol groups.
For some protocol groups, you can also configure policer values for individual packet types. When you configure aggregate policer values for certain protocol groups, you can optionally bypass that policer for one or more particular packet types in that group.
Although all policers have default parameter
values, these values might not accurately reflect the control traffic
pattern of your network. We recommend that you model your network
to determine the best values for your situation. Before you configure
policers for your network, you can quickly view the default values
for all packet types from operational mode using the show ddos-protection protocols parameters brief command. You can also use the command to specify a single
protocol group of interest. For example, to see default values for
the dhcpv4 protocol group, use the show ddos-protection
protocols dhcpv4 parameters brief command.
You can disable a packet type policer at either the Routing Engine level (if supported) or at the Packet Forwarding Engine level (if supported) for a specified line card or for all line cards. You can also disable logging of all control plane DDoS protection events for individual packet types within a protocol group.
To configure the desired aggregate or packet-type DDoS protection policer settings:
See Also
Verifying and Managing Control Plane DDoS Protection
Purpose
View or clear information about control plane DDoS protection configurations, states, and statistics.
Action
To display the control plane DDoS protection policer configuration, violation state, and statistics for all packet types in all protocol groups:
content_copy zoom_out_mapuser@host> show ddos-protection protocols
Run this command before you make any configuration changes to see the default policer values.
To display the control plane DDoS protection policer configuration, violation state, and statistics for a particular packet type in a particular protocol group:
content_copy zoom_out_mapuser@host> show ddos-protection protocols protocol-group packet-type
To display only the number of control plane DDoS protection policer violations for all protocol groups:
content_copy zoom_out_mapuser@host> show ddos-protection protocols violations
To display a table of the control plane DDoS protection configuration for all packet types in all protocol groups:
content_copy zoom_out_mapuser@host> show ddos-protection protocols parameters brief
To display a complete list of packet statistics and control plane DDoS protection violation statistics for all packet types in all protocol groups:
content_copy zoom_out_mapuser@host> show ddos-protection protocols statistics detail
To display global control plane DDoS protection violation statistics:
content_copy zoom_out_mapuser@host> show ddos-protection statistics
To display the control plane DDoS protection version number:
content_copy zoom_out_mapuser@host> show ddos-protection version
To clear control plane DDoS protection statistics for all packet types in all protocol groups:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols statistics
To clear control plane DDoS protection statistics for all packet types in a particular protocol group:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols protocol-group statistics
To clear control plane DDoS protection statistics for a particular packet type in a particular protocol group:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols protocol-group packet-type statistics
To clear control plane DDoS protection violation states for all packet types in all protocol groups:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols states
To clear control plane DDoS protection violation states for all packet types in a particular protocol group:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols protocol-group states
To clear control plane DDoS protection violation states for a particular packet type in a particular protocol group:
content_copy zoom_out_mapuser@host> clear ddos-protection protocols protocol-group packet-type states
