Error Conditions; Merging Policies Configuration Example - Juniper E320 Configuration Manual

!
!
!

Error Conditions

Most errors, such as mismatched interface types while merging attachments, are
caught during configuration. If merging fails, the attachment at the given interface
is not modified.
You can modify component policies manually. Although you might want to do this
for debugging purposes, we highly discourage you doing this because it can affect
synchronization with the Service Manager application. You cannot manually attach
a final merged policy to any interfaces. Instead, attach the set of component
policies that constitute this merged policy. If you want to modify the final merged
policy, use existing policy merging or component policy modification to achieve
this.

Merging Policies Configuration Example

In the following example IP policy p1 and IP policy p2 are attached at interface
atm5/0.1 as input attachments. Subsequently, policy p3 is attached at the same
point. Then policies p1 and p2 are attached as output at atm 5/0.2.
1. Create IP policy p1.
A detachment based on the policy name removes all attachments for that
policy at the specified attachment point in a single command regardless of
creation source. A detachment based on attachment type detaches all
attachments at that attachment point regardless of creation source. Service
Manager can delete only one attachment at a time through service
deactivation.
The statistics and baseline keywords for the merged policy attachment are
computed as a logical OR for all attachments at the specified attachment point.
If you delete an attachment:
! The merged policy is recomputed with the remaining attachments of the
same type that have the merge keyword set. The statistics for common
classifier groups are preserved when replacing the existing merged
attachment.
! The statistics and baseline keywords for the merged policy attachment are
recomputed to be a logical OR of all remaining attachments at the specified
attachment point.
host1(config)#ip classifier-list C1 tcp host 1.1.1.1 any eq 80
host1(config)#ip classifier-list C2 icmp any any 8 0
host1(config)#ip policy-list p1
host1(config-policy)#classifier-group C1 precedence 90
host1(config-policy-classifier-group)#forward next-hop 10.1.1.1
host1(config-policy-classifier-group)#exit
host1(config-policy)#classifier-group C2 precedence 10
host1(config-policy-classifier-group)#filter
host1(config-policy-classifier-group)#exit
Chapter 2: Creating Policies
! 51
Merging Policies