Table of Contents
Advertisement
Copyright © 2010, Juniper Networks, Inc.
Verify in the Device List tab that the new device is visible and has the connection
e.
status "Never connected."
Give the unique external ID and the one-time password to the device manager.
f.
On the device, configure the device to connect with NSM:
3.
Log on to the Junos device.
a.
At the command-line prompt, identify the management system by device name,
b.
device ID, and HMAC.
For devices running the 9.0 version of the operating system, use the following
command syntax:
set system services outbound-ssh application-id <name> secret <string>
services netconf device-id <external-id from nsm> <NSM device server ip>
port 7804
For example:
% set system services outbound-ssh application-id nsm-wei secret 123456789
services netconf device-id abcdef 10.150.42.16 port 7804
For devices running the 9.1 and later versions of the operating system, use the
following command syntax:
set system services outbound ssh client <name> secret <secret string>
services netconf device-id <external-id from nsm> <nsm device server ip>
port 7804
For example:
set system services outbound ssh client nsm wei secret 123456789
services netconf device-id abcdef 10.150.42.16 port 7804
Establish the SSH connection with the network management system.
c.
For a gateway or router with a single Routing Engine, or for a single EX Series
switch:
#
commit
For an EX Series virtual chassis, an SRX virtual chassis or for a gateway or
router with redundant Routing Engines:
#
commit synchronize
Synchronizing the commit operation ensures that NSM connects to the backup
Routing Engine following failover of the master Routing Engine.
The device software initiates the TCP connection to NSM and identifies itself
using the specified device ID and HMAC. The two sides then engage in SSH
transport layer interactions to set up an encrypted tunnel, and NSM authenticates
itself to the device based on user name and password.
In the Device List, verify the connection status of the newly added device. The
d.
status changes from "Never connected" to "Up."
Chapter 4: Adding Devices
137
Advertisement
Table of Contents
Related Manuals for Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1
Related Products for Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - CONFIGURING INTRUSION DETECTION AND PREVENTION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING INTRUSION DETECTION PREVENTION DEVICES GUIDE REV 01
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - API GUIDE REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - M-SERIES AND MX-SERIES DEVICES GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.2 - ADMINISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING J SERIES SERVICES ROUTERS AND SRX SERIES SERVICES GATEWAYS GUIDE REV
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - NSMXPRESS SERIES II REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.4 - M-SERIES AND MX-SERIES DEVICES GUIDE REV 1
- Juniper NETWORK AND SECURITY MANAGER 2010.2
- Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - CATEGORY OFFENSE INVESTIGATION GUIDE REV 1
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 R2 - LOG MANAGEMENT ADMINISTRATION GUIDE REV 1
- Juniper MEDIA FLOW CONTROLLER 2.0.5
- Juniper 200 Series