Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Routing Policy and Firewall Filters

  • Class-Based Forwarding Class Usage (PTX10004, PTX10008, PTX10001-36MR)—Starting in Junos OS Evolved release 21.2R1 you can configure Source Class Usage (SCU) and Destination Class Usage (DCU). SCU enables you to monitor the amount of traffic originating from a specific prefix and DCU enables you to track how much traffic is sent to a specific prefix in the core of the network originating from a specific interface.

    [See Configuring the Filter Profile.]

  • Support for route’s next-hop weight in policy match condition (PTX10001, PTX10003, PTX10008)—Starting in Junos OS Evolved Release 21.2R1, a route with multiple next-hop paths can use weight associated with the paths to identify primary and backup paths. The path with the lowest weight is used as the primary path, and any paths with higher weights are treated as backup paths. You can use the next-hop weight as a match condition in export policies to redistribute IGP and BGP routes based on whether the primary or backup paths are active. You can also use this match condition in conjunction with the programmed match condition to avoid exporting routes programmed by APIs that don't have a primary path configured.

    Configure this match condition at the [edit policy-options policy-statement policy-name term term-name from] hierarchy level.

    [See Basic BGP Routing Policies.]