Figure 56: Identifying Ordered List Entries That Do Not Match The Template; Using The Template Operations Directive - Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1 Administration Manual

Table of Contents

Advertisement

Using the Template Operations Directive

Copyright © 2010, Juniper Networks, Inc.

Figure 56: Identifying Ordered List Entries that Do Not Match the Template

Order
In the device configuration in Figure 56 on page 215:
The subsequence d, e, f is not highlighted because it is the longest common
subsequence between the device configuration and the template.
g is not highlighted because it does not come from the template.
a and b have a continuous green highlight because they represent a common
subsequence, though not the longest.
c has a single-entry out-of-order mark because it is adjacent to neither of its neighbors
in the template.
NOTE: If multiple subsequences tie for the longest common subsequence, then NSM
picks either one but not both.
NSM recomputes the longest common subsequence each time the list is reordered and
makes changes to out-of-sequence highlighting accordingly.
The Template Operations directive allows you to add templates or remove templates
for multiple devices at one time, and to validate configurations after changes.
NOTE: The Template Operations directive only updates the configuration database.
To apply changes to devices, you must use the Update Device directive.
Chapter 5: Configuring Devices
215

Advertisement

Table of Contents
loading

This manual is also suitable for:

Network and security manager 2010.3

Table of Contents