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:
- user@host# edit policies group junose list
ipv4 rule clacl traffic-condition rtcl traffic-match-condition
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set source-class source-class
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set destination-class destination-class
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set traffic-class traffic-class
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set color color
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set user-packet-class user-packet-class
- [edit policies group junose list ipv4 rule clacl traffic-condition
rtcl traffic-match-condition]
- user@host# set destination-local-interface destination-local-interface
[edit policies group junose list ipv4 rule clacl traffic-condition rtcl traffic-match-condition] user@host# show