Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure Enhanced Hierarchical Policer (Junos OS Evolved)

This example shows how to configure enhanced-hierarchical-policer under the dynamic profile using four levels of traffic priority hierarchies– high, medium-high, medium-low, and low. To know more about enhanced hierarchical policer functionality, see Enhanced Hierarchical Policer Overview (Junos OS Evolved).

The following steps require you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.

  1. Configure prefix list to enable the dynamic profile to classify traffic based on IP prefixes. This allows the enhanced hierarchical policer to selectively apply rate-limiting policies to those matched prefixes.
  2. Create a dynamic profile.
  3. Configure variables within the dynamic profile. They act as placeholders or keys with dynamically assigned values sourced from a RADIUS server during subscriber authentication.
  4. Configure the default values for the predefined variables. These default values are used when RADIUS server does not supply a value.
  5. Create enhanced hierarchical policer under the dynamic profile hierarchy. Also, include logical-interface-policer statement to define traffic rate limiting of input traffic for both inet and inet6 families on the same logical interface without needing to create multiple instances of the policer.
  6. Define committed information rate (CIR), maximum committed information rate (MAX CIR), and committed burst size (CBS) for the four traffic priorities- high, medium-high, medium-low, and low.
  7. Configure firewall filter under dynamic profiles with enhanced hierarchical policer and other required filter actions.
    1. Specify the family address type (inet for IPv4 and/or inet6 for IPV6) for the firewall filter, specify the filter name using a defined variable, and include the interface-specific statement to apply the policer function specific to an interface.
    2. (Optional) To enable the Packet Forwarding Engine (PFE) to report policer statistics to the RADIUS server, include the service-accounting statement. The statistics include the timestamp when the data was collected, along with the total bytes and packets allowed by the policer at each level. The system provides statistics to the RADIUS server for all four policer levels.
    3. Specify firewall filter terms based on destination prefixes and enhanced hierarchical policer filter actions.
  8. Configure the logical interface to apply firewall filters.
  9. (Optional) Confirm the configuration by entering the show dynamic-profiles pppoe-client-enh-hpol-profile-scaling command. If the command output does not display the intended configuration, repeat the instructions in this procedure to correct the configuration.