Table of Contents
Advertisement
Copyright © 2010, Juniper Networks, Inc.
NOTE: All passwords handled by NSM are case-sensitive.
c. Click Show Device Commands to display the list of CLI commands that must be
executed on the device to connect to NSM. The commands enable management
and set the management IP address to the Device Server IP address, enable the
Management Agent, set the Unique External ID, and set the device OTP.
d. Copy and paste these commands into a text file,
e. Click Finish to complete the Add Device wizard and include the new device in the
Device Manager list.
Log into the device as root and run the commands.
7.
Check the device configuration status (mouse over the device in Device Manager or
8.
check in Device Monitor):
The status message "Waiting for 1st connect" might display briefly.
After the device connects, the status displays "Import Needed", indicating that the
device has connected but the management system has not imported the device
configuration yet.
Import the device configuration by right-clicking the device and selecting Import
9.
Device. The Job Information box displays the job type and status for the import; when
the job status displays successful completion, click Close.
After the import finishes, double-click the device to view the imported configuration.
To check the device configuration status, mouse over the device in Device Manager (you
can also check configuration status in Device Monitor). The device status displays as
"Managed", indicating that the device has connected and the management system has
successfully imported the device configuration.
The next step is to verify the imported configuration using the Device Monitor or the
Device Manager. See "Verifying Imported Device Configurations" on page 128 for details.
Adding and Importing an Infranet Controller or Secure Access Device
The procedure for importing a device with an unknown IP address is the same for Secure
Access and Infranet Controller devices. This procedure requires specific actions to be
taken on the a Secure Access or Infranet Controller device in addition to those taken in
the NSM UI.
Because Secure Access and Infranet Controller configurations can be large, some large
binary data files are not imported with the rest of the configuration. A stub is placed in
the device configuration tree instead. If you need to manage these files in NSM, you must
import them later as shared objects, and then create links to those shared objects from
the device configuration tree. See "Managing Large Binary Data Files (Secure Access and
Infranet Controller Devices Only)" on page 275 for details.
Chapter 4: Adding Devices
121
Advertisement
Table of Contents
