Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Network and Security Manager Configuring Secure Access Devices Guide
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The Junos OS has no known time-related limitations through
the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited (if the Customer’sprincipal office is locatedoutside the Americas) (such applicable entity being referred
to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limits to Customer’s use of the Software. Such limits may restrict use to a maximum number of seats,registeredendpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized
copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software,in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold in the secondhand market; (f) use any ‘locked’or key-restricted feature,function, service, application, operation,or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statementthat accompanies the Software(the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligationto support
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
OR COSTSOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES,OR FOR ANY SPECIAL, INDIRECT,OR CONSEQUENTIALDAMAGES
ARISING OUT OF THIS AGREEMENT, THE SOFTWARE,OR ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.IN NO EVENT SHALL JUNIPER
BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES
JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT
ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’
or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by
Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between
the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination
of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer’s possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to
be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with
all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any
liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under
this Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three
years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL
at http://www.gnu.org/licenses/lgpl.html .
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).
Network and Security Manager (NSM) is a software application that centralizes control
and management of your Juniper Networks devices. With NSM, Juniper Networks delivers
integrated, policy-based security and network management for all security devices.
Secure Access (SA) device is the next generation Secure Access SSL VPN appliances in
its leading market. It enables a solution tailoring to meet the remote and extranet access
requirements.
This guide provides the various steps to configure and manage Secure Access using NSM.
This guide also helps in understanding of how to configure basic and advanced NSM
functionality, including adding new devices, deploying new device configurations, updating
device firmware, viewing log information, and monitoring the status of Secure Access.
Audience
This guide is intended for the system administrators who are responsible for configuring
Secure Access and Secure Access Federal Information Processing Standards (FIPS).
Document Conventions
Table 1 on page xiv defines notice icons used in this guide.
terminal lengthRepresent keywordsWords in plain text
mask, accessListNameRepresent variablesWords in italics
Words separated by the pipe ( | )
symbol
Words enclosed in brackets followed
by and asterisk ( [ ]*)
variable to the left or right of this symbol. The
keywordor variable can be optional or required.
can be entered more than once.
Represent required keywords or variables.Words enclosed in braces ( { } )
diagnostic | lineRepresent a choice to select one keyword or
[ internal | external ]Represent optional keywords or variables.Words enclosed in brackets ( [ ] )
[ level1 | level2 | 11 ]*Represent optional keywords or variables that
{ permit | deny } { in | out } { clusterId
| ipAddress }
List of Technical Publications
This section provides the list of the documentations required for any additional
information.
Table 4: Network and Security Manager and Secure Access Device Publications
Network and Security Manager
Installation Guide
Network and Security Manager
Administration Guide
Details the steps to install the NSM management system on a single server or on separate
servers. It also includes information on how to install and run the NSM user interface.
This guide is intended for IT administrators responsible for the installation and/orupgrade
to NSM.
Describes how to use and configure key management features in the NSM. It provides
conceptual information, suggested workflows, and examples where applicable. This
guide is best used in conjunction with the NSM Online Help, which provides step-by-step
instructions for performing management tasks in the NSM UI.
Network and Security Manager
Configuring Firewall/VPN Devices
Guide
Network and Security Manager
Online Help
This guide is intended for application administrators or those individuals responsible for
owning the server and security infrastructure and configuring the product for multi-user
systems. It is also intended for device configuration administrators, firewall and VPN
administrators, and network security operation center administrators.
Describes NSM features that relate to device configuration and management. It also
explains how to configure basic and advanced NSM functionality, including deploying
new device configurations, managing Security Policies and VPNs, and general device
administration.
Provides task-oriented procedures describing how to perform basic tasks in the NSM
user interface. It also includes a brief overview of the NSM system and a description of
the GUI elements.
Provides comprehensive information about configuring the Secure Access appliances.SecureAccessAdministrationGuide
Table 4: Network and Security Manager and Secure Access Device Publications (continued)
Secure Access Quick Start Guide
Provides procedures to install Secure Access appliances on your network and begin
configuration.
Requesting Technical Support
Technicalproduct support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number,use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•
Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .
NSM and Secure Access Device Management Overview on page 3
•
Communication Between a Secure Access Device and NSM Overview on page 3
•
Secure Access Device Services and Device Configurations Supported in NSM on page 5
NSM and Secure Access Device Management Overview
NSM is the Juniper Networks network management tool that allows distributed
administration of network appliances. You can use the NSM application to centralize
status monitoring, logging, and reporting, and to administer Secure Access device
configurations.
With NSM, you can manage most of the parameters that you can configure through the
Secure Access admin console. The configuration screens rendered through NSM are
similar to the screens in the Secure Access device admin console. NSM incorporates a
broad configuration management framework that allows co-management using other
methods.
Related
Documentation
Communication Between a Secure Access Device and NSM Overview on page 3•
• Secure Access Device Services and Device ConfigurationsSupported in NSM on page 5
• Importing a Secure Access Device on page 11
Communication Between a Secure Access Device and NSM Overview
The Secure Access device and the NSM application communicate through the Device
Management Interface (DMI). DMI is a collection of schema-driven protocols that run
on a common transport (that is, TCP). DMI is designed to work with Juniper Networks
platforms to make device management consistent across all administrative realms.
Supported DMI protocols include:
NetConf (for inventory management, XML-based configuration, text-based
configuration, alarm monitoring, and device specific commands).
•
Structured syslog.
•
Threat flow for network profiling.
DMI supports third-party network management systems that incorporate the DMI
standard; however, only one DMI-based agent per device is supported.
The Secure Access device configuration is represented as a hierarchical tree of
configuration items. This structure is expressed in XML and can be manipulated with
NetConf. NetConf is a network management protocol that uses XML. DMI uses NetConf’s
generic configuration management capability to allow remote configuration of the device.
To allow NSM to manage the Secure Access device using the DMI protocol, NSM must
import the schema and metadata files from the Juniper Networks Schema Repository,
a publicly accessible resource that is updated with each device release. In addition to
downloading the Secure Access device current schema, NSM may also download
upgraded software.
The Schema Repository enables access to XSD and XML files defined for each device,
model, and software version.
Before attempting to communicate with NSM, you must first complete the initial
configurationof the Secure Accessdevice. Initial configuration includes network interface
settings, DNS settings, licensing, and password administration.
If you have several Secure Access devices that will be configured in a clustering
environment, the cluster abstraction must first be created in the NSM Cluster Manager.
Then you can add individual nodes.
After you have completed the initial network configuration, you can configure the Secure
Access device to communicate with NSM using the appropriate network information.
Once the Secure Access device has been configured to communicate with NSM, the
Secure Access device contacts NSM and establishes a DMI session through an initial TCP
handshake.
All communications between the Secure Access device and NSM occur over SSH to
ensure data integrity.
After the Secure Access device initially contacts NSM and a TCP session is established,
interactionbetween the Secure Access device and NSM is driven from NSM, which issues
commands to get hardware, software, and license details of the Secure Access device.
NSM connects to the Schema Repository to download the configuration schema that is
specific to the Secure Access device.
NSM then issues a command to retrieveconfigurationinformation from the Secure Access
device. If NSM is contacted by more than one Secure Access device as a member of a
cluster, information from only one of the cluster devices is gathered. NSM attempts to
validate the configuration received from the Secure Access device against the schema
from Juniper Networks.
Once the Secure Access device and NSM are communicating, the Secure Access device
delivers syslog and event information to NSM.
After NSM and the Secure Access device are connected, you can make any configuration
changes directly on the Secure Accessdevice, bypassing NSM. NSM automatically detects
these changes and imports the new configurationdata. Changes to Secure Accesscluster
members will similarly be detected by NSM.
When you make changes to the Secure Access device configuration through NSM you
must push the changes to the device by performing an Update Device operation.
When you double-click the Secure Access device icon in the Device Manager and select
the Configurationtab, the configurationtree appears in the main display area in the same
orientation as items appear on the Secure Access device admin console.
Related
Documentation
Secure Access Device Services and Device Configurations Supported in NSM on page 5•
• Importing a Secure Access Device on page 11
• NSM and Secure Access Device Management Overview on page 3
Secure Access Device Services and Device Configurations Supported in NSM
The Secure Access device supports the following services in NSM:
•
Inventorymanagement service — Enables management of the Secure Access software,
hardware,and licensing details. Adding or deleting licenses or upgrading or downgrading
software are not supported.
•
Status monitoring service — Allows the Secure Access device’s status to be obtained,
including name, domain, OS version, synchronization status, connection details, and
current alarms.
•
Logging service — Allows the Secure Access device’s logs to be obtained in a
time-generated order. Logging configuration details that are set on the Secure Access
device will apply to NSM.
•
XML-based configuration management service — Enables NSM to manage the
configuration of the Secure Access device. NSM uses the same XML schema as the
Secure Access device, so you can troubleshoot NSM using XML files downloaded from
the Secure Access device.
The following device configurations are not supported:
•
Editing licensing information, although licenses can be viewed
•
Creating clusters, joining nodes to clusters, or enabling or disabling cluster nodes
•
Packaging log files or debug files for remote analysis
•
Rebooting the Secure Access device
Related
• Communication Between a Secure Access Device and NSM Overview on page 3
Secure Access Device and NSM
Installation Overview
•
Secure Access Device Installation Overview on page 7
•
NSM Installation Overview on page 7
Secure Access Device Installation Overview
Before beginning, see the Juniper Networks Security Products Safety Guide for important
safety information.
You can install the Secure Access device and start configuring your system using the
following steps:
1. Rack mount the Secure Access device.
2. Install the hardware.
3. Perform basic setup.
4. License and configure your Secure Access device.
See the Quick Start Guide for Secure Access 2500, 4500 and 6500 Guide to install and
configure a Secure Access device.
Related
Documentation
NSM Installation Overview on page 7•
• Communication Between a Secure Access Device and NSM Overview on page 3
NSM Installation Overview
NSM is a software application that enables you to integrate and centralize management
of your Juniper Networks environment. Youneed to install two main software components
to run NSM: the NSM management system and the NSM user interface (UI).
See the Network Security Manager Installation Guide for the steps to install the NSM
management system on a single server or on separateservers. It also includes information
on how to install and run the NSM user interface. The Network Security Manager InstallationGuide is intended for IT administrators responsible for installing or upgrading to the NSM.
This chapter provides information on how to add a Secure Access device through the
import workflowand also how to verify the imported configuration. This chapter contains
the following procedures:
•
Importing a Secure Access Device on page 11
•
Requirements for Importing a Secure Access Device into NSM Through a Reachable
Workflow on page 14
•
Adding a Secure Access Device Through a Reachable Workflow on page 15
•
Importing Multiple Secure Access Devices on page 16
•
Verifying Imported Device Configurations on page 19
Importing a Secure Access Device
You can add a Secure Accessdevice to your existing network by using NSM and importing
its configurations. Using the Add Device Wizard, you can configure a connection between
the management system and the physical device, and then import all device parameters,
policies, objects, VPNs, and so on.
Import a Secure Access device by following these procedures:
1.
Installing and Configuring a Secure Access Device on page 11
2.
Adding a Secure Access Device Through NSM on page 12
3.
Configuring and Activating the NSM agent on the Secure Access Device on page 13
4.
Confirming Connectivity and Importing the Secure Access Device
Configuration on page 14
Installing and Configuring a Secure Access Device
Before you add the Secure Access device to NSM, you must install and configure the
Secure Access device to have logon credentials for an NSM administrator.
1. Select System > Network > Overview in the device’s admin console and ensure that
basic connection information such as the following are configured on the Secure
Access device:
•
Network interface settings
•
DNS settings
•
Password
2. Select Authentication > Auth Servers and enter the username and password of the
NSM administrator in the applicable authentication server.
3. Select Administrators > Admin Roles and create an NSM agent role.
NOTE: Only password-based authentication serverscan be used. One-time
password authentication is not supported.
4. Select Administrators> Admin Realms and create an NSM agent administratorrealm
for the DMI agent on the Secure Access device and use role mapping to associate the
NSM agent role and realm. Do not apply any role or realm restrictions for the NSM
agent role or realm.
For complete details on installing and configuring Secure Access devices, see the Juniper
Networks Secure Access Administration Guide.
Adding a Secure Access Device Through NSM
To add the Secure Access device through the NSM UI:
1. From the left pane of the NSM UI, click Configure.
2. Expand Device Manager and Select Devices. The Devices workspace appears on the
right side of the screen.
3. Click the Device Tree tab, click the New button, and select Device. The New-Device
dialog box appears.
4. Select Device is Not Reachable and click Next.
5. Enter the device name, and select the required color, OS name (SA), and platform
and managed OS version from the drop-down lists.
6. From the Choose Device Server Connection Parameter area, select:
•
Use Default Device Server IP Address and Port — Connects the device to the NSM
Device Server IP address and port.
•
Use Device Server Through MIP — Connects the NSM device server through a
mapped IP address and port.
7. Click Next, and a unique external ID gets generated automatically. This ID represents