Reordering Lists; Using Configuration Groups With Templates; Sharing Configuration Group Definitions Across Multiple Devices - Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1 Administration Manual

Network and Security Manager Administration Guide

Reordering Lists

Using Configuration Groups with Templates

Sharing Configuration Group Definitions Across Multiple Devices

230
b # from configuration group J
r # from configuration group K
For unordered lists, this rule is unimportant. For ordered lists such as policies and
configuration group definitions, the rule is important.
Ordered lists that are inherited from a configuration group follow the same rules as
ordered lists inherited from a template:
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
configuration group matches a contiguous subsequence of parameters in the device,
then NSM applies the new configuration group order for the subsequence to the device.
Entries added in a configuration group are placed in the same sequence in the device;
that is, an entry follows the parameter in the device that precedes it in the configuration
group, even if that entry has been moved in the device.
For details and examples, see "Specifying the Order of List Entries" on page 211.
NSM uses the same mechanism for identifying ordered list entries that do not match the
configuration group order as is used for templates. Green highlights in the first data
column indicate entries in the regular configuration that are not in the order specified in
the configuration group. See "Identifying Ordered List Entries That Do Not Match the
Template or Configuration Group Order" on page 216 for details and examples.
If a field in a device object can inherit from both a template and a configuration group,
then the template value is used. NSM first expands the template, and then expands the
configuration group. Regular configuration data has precedence over template or
configuration group data.
For simplicity, we recommend that you use either templates or configuration groups for
each part of the configuration, but not both. Avoid applying a configuration group in a
device object to part of the configuration that also has values applied from a configuration
group that is part of a referenced template.
In some cases, however, it can be desirable to mix templates with configuration groups.
One practical use of mixing configuration groups with templates is so that you can use
a wildcard mechanism in a configuration group to assign a common value to like
parameters across multiple list entries such as interfaces.
Templates provide a natural mechanism for sharing configuration group definitions across
multiple devices. The use of configuration groups enhances the capabilities of templates,
for example, by allowing you to set the same field value on all interfaces across multiple
devices by using the configuration group wildcard feature.
Copyright © 2010, Juniper Networks, Inc.