Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual page 70

Junose software for broadband services routers policy management configuration guide

Table of Contents

JUNOSe 11.1.x Policy Management Configuration Guide

NOTE:

Use the input or output keyword to assign the policy list to the ingress or egress of

the interface. For ATM, IP, and IPv6 policy lists, use the secondary-input keyword to

assign the policy list, after route lookup, to data destined for local or remote

destinations. For IP and IPv6 policy lists, use the secondary-input keyword to assign

the policy list, after route lookup, to data destined to local or remote destinations.

The router supports secondary input policies whose principal applications are:

NOTE: The local-input keyword for the ip policy and ipv6 policy commands is

deprecated, and may be completely removed in a future release. We recommend

you remove the keyword from scripts. Re-create any local input policies using the

ip classifier-list local true command and attaching the policies using the ip policy

secondary-input command.

You can enable or disable the recording of routing statistics for bytes and packets

affected by the policy. If you enable statistics, you can enable or disable baselining

of the statistics. The router implements the baseline by reading and storing the

statistics at the time the baseline is set and then subtracting this baseline whenever

baseline-relative statistics are retrieved. You must also enable baselining on the

interface with the appropriate baseline command.

NOTE: The gre-tunnel policy command does not support the baseline keyword.

You can use the preserve keyword to save the existing statistics when you attach a

policy to an interface that already has a policy attached. This keyword saves the

statistics for any classifier-list that is the same for both the new and old policy

attachments. Without the preserve keyword, all statistics are deleted when you attach

the new policy.

For example, when you replace a policy attachment that references the original

policy-list plOne with a new attachment referencing policy-list plTwo, the existing

Applying Policy Lists to Interfaces and Profiles Overview

The mpls policy command is used to attach policies to MPLS Layer 2 circuits

only.

The SRP module Fast Ethernet port does not support policy attachments, nor

can the module be the destination for the forward next-hop, forward

next-interface, next-hop, and next-interface commands

To defeat denial-of-service attacks directed at a router's local IP or IPv6 stack

To protect a router from being overwhelmed by legitimate local traffic

To apply policies on packets associated with the route class

Table of Contents

E series