Merging Policies; Merging Policies Overview; Interface - 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

CHAPTER 6

Merging Policies

Merging Policies Overview

Copyright © 2010, Juniper Networks, Inc.
This chapter provides information about merging policies on E Series routers. The chapter
discusses the following topics:
Merging Policies Overview on page 97
Resolving Policy Merge Conflicts on page 99
Merged Policy Naming Conventions on page 101
Reference Counting for Merged Policies on page 101
Persistent Configuration Differences for Merged Policies Through Service
Manager on page 102
Policy Attachment Sequence at Login Through Service Manager on page 102
Policy Attachment Rules for Merged Policies on page 102
Error Conditions for Merged Policies on page 103
Merging Policies Configuration on page 104
Parent Group Merge Algorithm on page 115
Overlapping Classification for IP Input Policy on page 117
Merging policies enables you to create multiple policy attachments at an attachment
point, resulting in a merged policy that is created and attached at this interface. Executing
more than one policy attachment command with the same attachment type at an
interface triggers a policy merge through the CLI.
In Profile Configuration mode, policy interface commands for IP and L2TP allow
attachments to be merged into any existing merge-capable attachment at an attachment
point. Service Manager can request that multiple interface profiles be applied or removed
at an interface as part of service activation or deactivation. Service Manager also specifies
whether or not the attachments created from these interface profiles are persistent on
subsequent reloads.
An interface and an attachment type identify an attachment point. The policies referenced
by the component attachments merge into a new policy, which then attaches at the
attachment point. The set of component policies are ordered alphabetically by name.
97

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents