Table of Contents
Advertisement
M-series and MX-series Devices
Related
Documentation
Device Schemas
12
Figure 2: NSM Network Architecture
When you update a device configuration, the GUI Server translates the objects and
object attributes in the ADM domain into device configuration information in a DM. For
DMI based devices which include the M-series and MX-series, the Device Server converts
the DM into an XML configlet and sends the configlet through NetConf protocol to the
device.
When you import a device configuration, the device sends the configuration through
the NetConf protocol as an XML document to the Device Server, which translates the
XML document into a DM with device configuration information. The GUI Server then
translates the device configuration in the DM into objects and object attributes in the
ADM, and uses the ADM to display current information in the UI.
For more details on the ADM and DMs, see "Managing Devices" in the Network Security
Manager Administration Guide.
The management system also provides an application programming interface (API) for
integrating NSM into larger enterprise business systems. This NSM API provides an
alternative interface to that provided by the UI. For details, see the Network and Security
Manager API Guide.
NSM and Device Management Overview on page 5
Understanding the CLI and NSM on page 6
Comparing the CLI To the NSM UI on page 7
NSM Services Supported for M-series and MX-series Devices on page 10
Device Schemas on page 12
Communication Between a Device and NSM on page 13
The structure of the ADM and the DMs is defined by a DM schema, which lists all the
possible fields and attributes for a type of object or device. The DM schema reads from
a capability file, which lists the fields and attributes that a specific operating system
version supports, to determine the supported features for the operating system version
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
