Table of Contents
Advertisement
Specifying the Order of List Entries
Copyright © 2010, Juniper Networks, Inc.
zone name in the device configuration. You must first delete the template-derived zone,
and then create a new zone.
A list or table entry in the configuration can contain multiple list key fields. For example,
in the routing table for a ScreenOS device, multiple fields (including IP address/netmask,
interface, next-hop, vsys, and so on) uniquely identify a particular route entry.
When configuring a device through NSM, you can enter most list or table entries in any
order. However, in some cases the order of list or table entries is significant to device
behavior. For example, in a routing policy or firewall filter, you define terms that are
analyzed sequentially. Also, when you create a named path in dynamic MPLS, you define
an ordered list of the transit routers in the path, starting with the first transit router and
ending with the last one.
NOTE: The ordering of list entries is a detailed point and of low significance
to most users. Skip this section if ordering of list entries is not significant to
you.
To specify a sequence in which the list or table entry order matters, select the entry in
the template and then use the up and down arrows at the top of the dialog box. The up
and down arrows appear on any table where the order of parameters is important and
can be altered. Figure 55 on page 211 shows an example.
Figure 55: Up and Down Arrows for Changing the Sequence of a List
NSM allows you to add, insert, or delete entries in ordered lists. NSM uses some simple
rules to establish the order of configuration entries when they are changed on the device
and then imported into NSM, or changed in the NSM template, and then updated on the
device.
The default order of entries in a list depends on their order in the template, their order in
the device object, their order in a configuration group, and their order on the device itself.
Chapter 5: Configuring Devices
211
Advertisement
Table of Contents
