Merged Policy Naming Conventions; Reference Counting For Merged Policies - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Merged Policy Naming Conventions

Reference Counting for Merged Policies

Copyright © 2010, Juniper Networks, Inc.
host1(config)#ip policy-list p1
host1(config-policy)#classifier-group C1 precedence 90
host1(config-classifier-group)#forward next-hop 1.1.1.1
host1(config-classifier-group)#exit
host1(config)#ip policy-list p2
host1(config-policy)#classifier-group C1 precedence 90
host1(config-classifier-group)#forward next-interface atm 5/0.1
host1(config-classifier-group)#exit
host1(config)#ip policy-list p2
host1(config-policy)#classifier-group C1 precedence 90
host1(config-classifier-group)#forward next-interface fastEthernet 4/0.1
next-hop 1.1.1.2
host1(config-classifier-group)#exit
Combining p1, p2, and p3, internally results in the following:
ip policy-list mpl_10
classifier-group C1 precedence 90
forward next-hop 1.1.1.1
forward next-interface atm 5/0.1
forward next-interface fastEthernet 4/0.1 next-hop 1.1.1.2
exit
Policy management enables multiple policy attachments at the same attachment point,
which results in a merged policy that is created and attached at the specified attachment
point. The logical OR of the statistics and baseline keywords of all attachments are used
as the statistics and baseline keyword for the merged policy attachment, as in the
following example:
host1(config)#interface atm 5/0.1
host1(config-subif)#ip policy input p1 statistics enable baseline enable merge
host1(config-subif)#ip policy input p2 merge
host1(config-subif)#ip policy input p3 statistics enable merge
host1(config-subif)#exit
Results in the following:
interface atm 5/0.1
ip policy input mpl_5 statistics enable baseline enable merge
exit
Merged policies are dynamically created. The naming convention is mpl_hex_of
internally_generated_policy ID, such as mpl_10. If the newly generated name already
exists, then a sequence number is appended to the new name to make it unique. The
sequence number starts at 1 and increments until the name is unique, such as mpl_10_2.
The reference counts in all containers referenced within a merged policy are incremented
by the number of times they are referenced within the merged policy. Also, the reference
counts of all component policies of a merged policy are incremented because of the
association of the component policies with the merged policy. This means you cannot
delete a component policy while a merged policy is still associated with it.
Chapter 6: Merging Policies
101