Reverting A Configuration To Default Values Of A Template; Templates And Validation; Applying Multiple Templates - Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1 Administration Manual

Network and Security Manager Administration Guide

Reverting a Configuration to Default Values of a Template

Templates and Validation

Applying Multiple Templates

204
NSM allows you to revert the device configuration values to that of the template default
values for SA, IC and Junos devices. The default value is inherited from the template
based on the order of priority in which the templates are applied to the device.
To revert a device configuration to the default values in a template:
Select
1. Configure > Device Manager > Devices
configuration settings you want to revert. The Device dialog box appears
Select the
Configuration
2.
From the Device configuration tree, right-click the configuration node that you want
3.
to revert and select
Revert to template/default value
Click OK. The configuration reverts to the template default values.
4.
You can apply a single template to different device types that run different OS versions
within the same device family. In some cases, the field values you specify in the template
might not be appropriate for all OS versions and device types:
If the template specifies a field that a device does not support, then the field does not
appear in the device editor and is not updated to the device. No validation message
appears.
If the template specifies a field that the device supports, but the value is outside the
permitted range for the device, a validation message appears in the Device dialog box.
A template value might be valid for one device but invalid for other devices.
As you create and edit template values and fields, NSM validates the values, and might
display validation messages. For example, you can configure an IP address in one template
and the netmask for that IP address in another template. However, a validation message
might appear when you enter the IP address because the netmask is not specified within
that same template.
You can safely ignore a validation message if the missing value is derived from another
template that is applied to the device, or if you manually entered the value in the specific
device configuration.
When applying multiple templates to a single device, you determine the order in which
the templates are applied. The highest-priority template is at the end of the template
list, and can override values set in any of the lower-priority templates. If more than one
template specifies a value for the same field, the value in the highest-priority template
takes precedence. The lower the template appears in the template list, the higher priority
it has when applying values to a device configuration.
and double-click the device whose
tab. The Device configuration tree appears.
.
Copyright © 2010, Juniper Networks, Inc.