How Nsm Works With The Cli And Distributed Data Collection - Juniper NETWORK AND SECURITY MANAGER 2010.4 - M-SERIES AND MX-SERIES DEVICES GUIDE REV 1 Manual

How NSM Works with the CLI and Distributed Data Collection

Copyright © 2010, Juniper Networks, Inc.
How NSM Works with the CLI and Distributed Data Collection on page 11
Device Schemas on page 12
Communication Between a Device and NSM on page 13
Before we can discuss how NSM works with the CLI, the following terms need to be
defined:
ADM (Abstract Data Model)—The Abstract Data Model is an XML file that contains all
the configuration information for a domain.
configlet—A configlet is a small, static configuration file that contains information on
how a device can connect to NSM.
Device Server—The Device Server is the component of the NSM management system
that handles communication between the GUI Server and the device, collects data
from the managed devices on your network, formats configuration information sent
to your managed device, and consolidates log and event data.
DM (Data Model)—A Data Model is an XML file that contains configuration data for
an individual device. The DM is stored in the Device Server; when you create, update,
or import a device, the GUI Server edits the Abstract Data Model (ADM) to reflect the
changes, then translates that information to the DM
GUI Server—The GUI Server manages the system resources and data that drives NSM
functionality. The GUI Server contains the NSM databases and centralizes information
for devices and their configurations, attack and server objects, and policies.
NSM and the CLI communicate through the GUI and Device Servers that translate objects
and object attributes in both directions. Device configuration information is translated
into Data Model (DM) objects or Abstract Data Model (ADM) object attributes, and
conversely DM objects and ADM object attributes are translated into XML configlets and
documents.
NSM uses a distributed data collection system. Each device is described by a unique DM.
The DM is stored in the Device Server which communicates with the GUI Server and the
device.
When you create, update, or import a device into NSM, the GUI Server edits the ADM to
reflect the changes, then translates that information to the DM. The ADM contains
configuration data for all objects in a specific domain. When you use the UI to interface
with your managed devices, the ADM and DMs work together.
Chapter 2: Understanding the JUNOS CLI and NSM
11