Table of Contents
Advertisement
Modifying Values in Templates
Copyright © 2010, Juniper Networks, Inc.
The templates for each family are different because the configuration fields for each
family are different.
Some devices might not have all fields prescribed in the template for that device family.
You can apply a template to any device in its family. NSM will ignore any fields that do
not apply to the given device.
A template can refer to other templates, enabling you to combine multiple templates
into a single template. When you make changes to any of the referenced templates,
those changes propagate through the combined template. For instructions for creating
and applying templates, see the Network and Security Manager Online Help topics,
"Applying Templates."
JUNOS device templates can also contain configuration groups. A configuration group
is similar to a template in that it specifies configuration data for reuse, but only within
the same device, and not across devices. See "Using Configuration Groups" on page 221.
The EX Series device template has the following configuration enhancements:
Template categories: These are logical groupings of configuration nodes based on
product functionality, such as VLAN, STP, and PoE for EX Series devices. You can select
one or more of these template categories while creating an EX Series template. The
configuration tree displays only the nodes associated with the selected template
category, which enhances the usability of the template. If template categories are not
selected, the default display is a full tree view. You can also view the associated
template categories in the
Customized configuration tree views: Instead of numerous configuration nodes being
always displayed irrespective of whether the node is configured, the EX Series device
template allows you to select either a full or partial configuration tree view. Check the
box, at the upper left of the
Display all
The default setting is the partial configuration tree view, which shows the first level
configuration node and its children. You can switch between the two views, even after
the device template is migrated.
NOTE: Conflicting configuration created using different configuration nodes, for example,
VLAN created through the VLAN configuration template, as well as the Interface
Configuration, can result in wrong device configuration during template application
and device update.
Template data applied to a device object does not affect the device itself until you push
the device object configuration to the device using the Update Device directive as
described in "Updating Devices" on page 241.
You can modify a template that has already been applied to one or more device
configurations. When you change a field value in a template, the device object that
references the template also changes.
Device Template
table view.
window, to have a full tree view.
Configuration
Chapter 5: Configuring Devices
197
Advertisement
Table of Contents
