Merging Policies; Merging Policies Overview; Resolving Policy Merge Conflicts; Merged Policy Naming Conventions - Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual

Junose software for broadband services routers policy management configuration guide
Table of Contents

Advertisement

Chapter 6

Merging Policies

Merging Policies Overview

This chapter provides information about merging policies on E Series routers. The
chapter discusses the following topics:
Merging Policies Overview on page 101
Resolving Policy Merge Conflicts on page 103
Merged Policy Naming Conventions on page 105
Reference Counting for Merged Policies on page 106

Persistent Configuration Differences for Merged Policies Through Service

Manager on page 106
Policy Attachment Sequence at Login Through Service Manager on page 106
Policy Attachment Rules for Merged Policies on page 106
Error Conditions for Merged Policies on page 108
Merging Policies Configuration on page 108
Parent Group Merge Algorithm on page 120
Overlapping Classification for IP Input Policy on page 122
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. This order determines how any merge conflicts are resolved,
with the most recently executed command taking precedence.
Merging Policies Overview
101

Advertisement

Table of Contents
loading

This manual is also suitable for:

E series

Table of Contents