Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1, Administration Manual

Page: 263 / 1026

•
Deleting entries from an ordered list in the device
• Deleting entries from an ordered list in the template
• Deleting template-provided entries in the device
•
Reordering entries in the device
•
Reordering entries in the template
TIP: Where possible, avoid mixing reordering operations with other operations
that affect the order of list entries. The results might not be what you intended.
When reordering is combined with adding and deleting entries, there is no
single obvious way to define the behavior so it always matches your intention.
Rules for Reordering Lists
When the template order changes, NSM uses best effort to apply the new sequence to
the device object using the following rules:
• NSM uses the device order before the operation as the starting point.
•
If, prior to applying the change, a contiguous subsequence of parameters in the template
matches a contiguous subsequence of parameters in the device, then NSM applies
the new template order for the subsequence to the device,
• Entries added in a template are placed in the same sequence in the device; that is, an
entry follows the entry in the device that precedes it in the template, even if that entry
has been moved in the device.
Examples of Reordered Lists
Examples of the rules for reordering lists follow.
Examples That Reorder a Common Sequence
Example 1: In the following example, the device has inherited the template entries and
maintained the same order as in the template. The user then changes the template order:
Before:
C B A Template Sequence
2 1 C B A Device Sequence
C B A Matching
Subsequence
Change:
Now reverse the first three items in the template sequence. Because the reordering takes
place within what was the matching subsequence, the new sequence is transferred to
the device:
213 Copyright © 2010, Juniper Networks, Inc.
Chapter 5: Configuring Devices