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


Configuring JUNOSe Secondary Input Policies

The SRC software includes support for JUNOSe secondary input 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. user@host# edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition 
    
    
    
  3. (Optional) Configure the condition to match packets based on the source route class.
  4. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set source-class source-class 
    
    
    
  5. (Optional) Configure the condition to match packets based on the destination route class.
  6. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set destination-class destination-class 
    
    
    
  7. (Optional) Configure the condition to match packets based on the traffic class.
  8. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set traffic-class traffic-class 
    
    
    
  9. (Optional) Configure the condition to match packets based on the packet color.
  10. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set color color 
    
    
    
  11. (Optional) Configure the condition to match packets based on the user packet class action number.
  12. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set user-packet-class user-packet-class 
    
    
    
  13. (Optional) Configure the condition to match packets based on packets destined for a local interface.
  14. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# set destination-local-interface destination-local-interface 
    
    
    
  15. (Optional) Verify the secondary input policy configuration.
  16. [edit policies group junose list ipv4 rule clacl traffic-condition rtcl 
    traffic-match-condition]
    
    user@host# show 
    
    
    


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