Table 15: Input Action And Secondary Input Actions - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Software for e series broadband services routers policy management configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04:
Table of Contents

Advertisement

Table 15: Input Action and Secondary Input Actions

Input
Action
Secondary Input Action
None
None
None
Copyright © 2010, Juniper Networks, Inc.
Traffic class action—If both the input and auxiliary-input attachments need this action,
the value configured in the auxiliary policy overwrites that of the primary policy.
User packet class action—Can be set twice per stage, with the second value overriding
the first.
The filter, next-hop, forward interface, and forward next-hop actions are mutually
exclusive within a classifier group. However, two policies in series can result in conflicting
actions, which are resolved using the following precedence rules:
The filter action has highest priority. A filter action in input or auxiliary-input policy
always prevails.
The exception action takes precedence over forward actions.
If multiple exception actions are required by the policy attachments, the last one
takes precedence.
If forward operations are required by both input and auxiliary-input policy
attachments, the auxiliary-input forward action takes precedence.
Input policy attachments depend on the local keyword in classifier list entries. Using the
local false keyword or using no local keyword (default) treats both local and non-local
traffic equally and ignores the local true classifier list entries.
Secondary input policies affect both local and non-local traffic and are processed by
policies attached with the secondary-input keyword. Secondary input policies are
controlled by the local keyword in the classifier list entries as follows:
local true keyword only affects local traffic
local false keyword only affects non-local traffic
no local keyword (default) affects both local and non-local traffic
In Table 15 on page 121, the filter action for the input policy takes precedence over the
others so that if a filter action is configured for either policy, the packet is filtered. If neither
policy has a filter action, but both policies specify a forward action, the action specified
by the auxiliary policy takes precedence. If only one policy specifies a forwarding action,
that action is executed. The next-hop rule is inoperative for auxiliary-input policies, just
as it is for secondary input policies. This policy rule has been superseded (but not replaced)
by the forward next-hop rule, which is operative for auxiliary-input policies.
Exception
Filter
Exception
Filter
Auxiliary
Next-hop
Forward
Interface
None
Forward
Interface
Auxiliary
Chapter 6: Merging Policies
Forward
Next-hop
Forward
Next-hop
Auxiliary
121

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents