Table of Contents
Advertisement
Copyright © 2010, Juniper Networks, Inc.
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.
3.
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 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. NSM authenticates itself to the device
based on user name and password.
Confirm Connectivity and Import the Device Configuration into NSM
In NSM, validate connectivity with the device, and then import the device configuration:
In the Device List, verify the connection status of the newly added device. The status
1.
changes from "Never connected" to "Up."
If the configuration status is "device platform mismatch," you selected the wrong
device platform when adding the device into NSM. Delete the device from NSM and
add it again using the correct device platform.
If the configuration status shows "device firmware mismatch," you selected the
wrong managed OS version when adding the device into NSM. Delete the device
from NSM and add it again using the correct managed OS version.
Chapter 4: Adding Devices
127
Advertisement
Table of Contents
Related Manuals for Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1
Related Products for Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1
- Juniper NETWORK AND SECURITY MANAGER 2010.3 - CONFIGURING INTRUSION DETECTION AND PREVENTION GUIDE REV1
- 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.3 - 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 - 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.3
- Juniper NETWORK AND SECURITY MANAGER 2010.2
- Juniper MEDIA FLOW CONTROLLER 2.0.4 -
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - AQL EVENT AND FLOW QUERY CLI GUIDE
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - EVENT CATEGORY CORRELATION REV 1
- Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 - SNMP AGENT GUIDE REV 1
- Juniper STRM LOG MANAGEMENT 2008.2 - S 6-2008