[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring JUNOSe Secondary Input Policy Conditions

For JUNOSe policies, you can apply secondary input policies to the input (ingress) side of the router interface. Secondary input policies evaluate conditions after a route lookup.

Use the following configuration statements to configure match conditions for JUNOSe secondary input policies:

policies group name list name rule name traffic-condition name traffic-match-condition {
source-class source-class ;
destination-class destination-class ;
traffic-class traffic-class;
color color;
user-packet-class user-packet-class;
destination-local-interface destination-local-interface ;
}

To add conditions for JUNOSe secondary input policies to a classify-traffic condition:

  1. From configuration mode, create a classify-traffic condition inside a policy rule that has already been created and configured for a policy list whose type is junose-ipv4 or junose-ipv6 and applicability is secondary-input. For example, to create a traffic-condition called rtcl within policy rule clacl:
  2. (Optional) Configure the condition to match packets based on the source route class.
  3. (Optional) Configure the condition to match packets based on the destination route class.
  4. (Optional) Configure the condition to match packets based on the traffic class.
  5. (Optional) Configure the condition to match packets based on the packet color.
  6. (Optional) Configure the condition to match packets based on the user packet class action number.
  7. (Optional) Configure the condition to match packets based on packets destined for a local interface.
  8. (Optional) Verify the secondary input policy configuration.
    [edit policies group junose list ipv4 rule clacl traffic-condition rtcl traffic-match-condition]
    user@host# show 
    
    
    

Related Topics


[Contents] [Prev] [Next] [Index] [Report an Error]