Network and Security Manager
NSMXpress Quick Start
November 17, 2010
Revision 1
NSMXpress isanappliance version of Network and Security Manager (NSM). NSMXpress
simplifies the complexity of network administration by providing a single, integrated
management interface that controls device parameters.
This robust hardware management system installs in minutes with full high availability
(HA) support, making it easy to scale and deploy. Enterprise customers with limited
resources can benefit significantly from NSMXpress because it eliminates the need to
have dedicated resources for maintaining a network and security management solution.
NSMXpress makes it easy for administrators to control device configuration, network
settings, and security policy settings for multiple families of Juniper devices including:
•
IDP Series Intrusion Detection and Prevention Appliances and Firewall and VPN devices
running ScreenOS
•
Devices running Junos OS, such as J Series Services Routers, SRX Series Services
Gateways, EX Series Ethernet Switches, M Series Multiservice Edge Routers, and MX
Series Ethernet Services routers
•
SA Series SSL VPN Appliances
•
IC Series Unified Access Control Appliances
For a complete list of supported device families and platforms, see the Network andSecurity Manager Administration Guide.
Up to 10 administrators can log into NSMXpress concurrently.
This quick start explains the following steps for installing and configuring NSMXpress
and for configuring NSM.
1. Install the NSMXpress appliance hardware.
2. Set up the NSMXpress appliance using the serial port.
We recommend that you install NSMXpress on your LAN to ensure that it can
communicate with your applicable resources,such as authentication servers, DNS servers,
internal Web servers through HTTP/HTTPS, external Web sites through HTTP/HTTPS
(optional), the Juniper update server via HTTP, Network File System (NFS) file servers
(optional), and client/server applications (optional).
NSMXpress Ports
Table 1 on page 4 provides required port information on the NSMXpress.
Table 1: Required Ports on NSMXpress
NOTE: If you decide to install NSMXpress in your DMZ, ensure that it can
connect to your internal resources.
443
8443
7800
7801
7802
7803
7804
Depends on
ConfigurationInternetLANDescriptionPortDirection
NoNoYesSSH command-line management22In
NoNoYesWeb interface for administrator
login
YesYesLANWebinterfacefor listening for NSM
API messages.
NoYesYesConnections from managed
devices to NSMXpress
NoNoYesConnections from the NSM GUI
Client to NSM
YesNoYesHeartbeat between peers in an HA
cluster
YesYesYesConnections from managed IDP
devices to NSM
YesYesYesConnections from devices running
Junos , Secure Access devices, or
Infranet Controller devices
For more information on ports, refer to the Network and Security Manager Installation
Guide.
Installing the Hardware
Follow these steps to unpack the NSMXpress appliance and connect it to your network.
To install NSMXpress:
22Out
23
80
123
NoYesYesSSH connection to new managed
device
YesNoYesTelnet connection to new
managed device
NoNoYesDNS lookups53
YesYesNoSystem Security Updates from
Juniper Networks
YesNoYesShared Disk portmap lookup111
YesYesYesNetworkTime Protocol (NTP) time
synchronization
YesNoYesShared Disk NFS connection2049
1. Place the shipping container on a flat surface and remove the hardware components
with care.
2. Remove the NSMXpress device from the shipping container and place it on a flat
surface.
3. Mount NSMXpress in your server rack using the attached mounting brackets.
4. Plug the power cord into the AC receptacle on the rear panel.
If your NSMXpress contains two power supplies, plug a power cord into each AC
receptacle.
5. Plug the other end of the power cord into a wall socket.
If your NSMXpress contains two power supplies, plug each power cord into a separate
power circuit to ensure that the NSMXpress continues to receive power if one of the
power circuits fails.
6. Plug the Ethernet cable into the port marked ETH0 on the front panel. See Figure 1 on
7. Plug the null modem serial cable into the console port. See Figure 1 on page 6.
This cable was shipped with your NSMXpress. If you do not have this cable, use any
other null modem serial cable.
8. Push the power button in the upper left corner of the front panel.
The green LED below the power button turns on. The NSMXpress hard disk LED turns
on whenever the appliance reads data from or writes data to an NSMXpress hard disk.
The internal port uses two LEDs to indicate the LAN connection status, which is
described in Table 2 on page 6.
Hardware installation is now complete. The next step is to set up the software, as
described in “Initial Setup Configuration” on page 6.
Table 2 on page 6 provides LED information for the ETH0 and ETH1 ports.
Table 2: Ethernet Port LEDs
Initial Setup Configuration
When you first turn on an unconfigured NSMXpress appliance, you need to enter basic
network and machine information through the serial console to make your appliance
accessible to the network. After entering these settings, you can continue configuring
the appliance using the CLI or the Web interface. You are not prompted for the initial
setup information again.
LED2LED 1LAN Status
OffOff10 Mbps connection
OffGreen100 Mbps connection
OffOrange1000 Mbps connection
BlinkingOrange, Green, or OffData is being transferred
This section describes the required serial console setup and the tasks you need to perform
when connecting to your NSMXpress for the first time:
•
Boot NSMXpress on page 7
•
Set Up Your Appliance on page 7
To configure NSMXpress for the first time, you must attach your NSMXpress appliance
to a console terminal running an emulation utility such as HyperTerminal.
1. Configure a console terminal or terminal emulation utility to use the following serial
connection parameters:
•
9600 bits per second
•
8-bit no parity (8N1)
•
1 stop bit
•
No flow control
Set Up Your Appliance
2. Connect the terminal or laptop to the null modem serial cable plugged into the
NSMXpress console port.
3. Turn on the NSMXpress appliance.
When NSMXpress is powered on, the serial console displays diagnostic information
beforeproceeding to the boot countdown. When complete,the serial console displays
the login prompt terminal emulator.
NSMXpress.juniper.net login:
4. Enter admin as your default login name.
5. Enter abc123 as your default password.
6. Change your default password when prompted. Enter the default password first,
followed by your new password. All passwords are case-sensitive.
This section provides the minimum information necessary to make your appliance active
on the network.
To set up your appliance either as a regional server or a central manager, follow these
steps:
1. Enter the IP address for interface eth0 and press Enter.
2. Enter the subnet mask for interface eth0 and press Enter.
3. Enter the default route or default gateway address for interface eth0 and press Enter.
Applying changes...
Re-loading database
ip_tables: (C) 2000–2002 Netfilter core team
ip_tables: (C) 2000–2002 Netfilter core team
ip_tables: (C) 2000–2002 Netfileter core team
Done!
Your NSMXpress is now active on the network.
To configure your system via a web browser, connect to:
https://10.150.43.205/admin
To configure your system via command line, type:
nsm_setup
For operation of NSM server, switch to user “nsm”.
Please consult NSM product documentation for details.
[admin@NSMXpress ~]$
To configure the NSM software using the CLI, see the NSMXpress User Guide. To configure
the NSM software using the Web interface, go to “Web Interface Configuration” on
page 8.
Web Interface Configuration
To configure NSM on your system from a Web interface, use the following steps.
1. Copy the URL (starting with https://) from the terminal emulator after installing
NSMXpress:
Your NSMXpress is now active on the network.
To configure your system via a web browser, connect to:
https//10.150.43.205/administration
2. Open a Web browser and paste the URL into the address text box.
3. Press Enter to open the NSMXpress login page.
4. Enter the admin user name and password and then click Login.
5. See “Configuring the NSM Software” on page 8 for details about how to install and
configure NSM on your NSMXpress appliance from the Web interface.
Configuring the NSM Software
After logging in as an ‘admin’ user, an initial setup script walks you through additional
configurationsystemsettings before finalizing the NSM installation. This chapter describes
that setup process.
Your NSMXpress appliance comes preconfigured as a regional server or a central manager.
Most installation and configuration steps in this section are identical for both types of
server. All exceptions are noted.
After logging into the NSMXpress Web interface, NSMXpress provides you with the
following installation options:
•
Configuring Basic Settings on page 9
•
Configuring High Availability on page 11
•
Advanced Options on page 14
•
Installing NSM Software on page 17
Configuring Basic Settings
To install the regional server or central manager software using the minimum
requirements:
1. Install your NSMXpress hardware as described in “Hardware Installation” on page 4.
2. Boot and setup your NSMXpress appliance as described in “Initial Setup Configuration”
on page 6.
3. Enter the https://<ip>/administration URL for your appliance in a Web browser. See
“Web Interface Configuration” on page 8 for details.
Configuring the NSM Software
4. Log into the Web interface. The System Info page opens.
5. Click the link Install NSM Regional Server (see Figure 2 on page 10) to go to the Install
Regional Server window or click the Install NSM Central Manager link to view the Install
NSM Central Manager window (see Figure 3 on page 10), as the case may be.
NOTE: The “admin” user default username is admin and the password is
the one you created in Step 6 of “Boot NSMXpress” on page 7.
6. Enter the primary IP address of your management server for eth0 (the default).
You can use the default IP address next to the first radio button or select the second
radio button and then enter a different IP address. Each IP address you add (in addition
to the default IP address) will be available in the drop-down list after you click the
second radio button.
7. Enter the NSM superuser password in the top text box, and then reenter it in the text
box below it.
This password must be at least eight characters long and is case-sensitive. This
password is used by the NSM superuser (also referred to as the NSM administrator).
This user has the highest level of privileges in NSM.
8. Enter the GUI Server one-time password in the top text box, and then reenter it in the
text box below it. This password is used to authenticate this NSM server with other
NSM servers with which it communicates. Regional servers use this password to
authenticate peer servers in an HA configuration and to authenticate the central
manager. The central manager uses this password to authenticate its peer server in
an HA configuration and any regional servers it manages. NSM servers must have the
same GUI Server one-time password, or the authentication will fail.
9. Select the license option. (This option is available only for regional servers.)
a. Select Base Install to use the built-in limited device license for as many as 25
devices.
b. Click Upload license file to upload the license file you generated using the Juniper
License Management System (LMS), which permits you to manage more than 25
devices. This license file must be located on your local hard drive.
See the Network and Security Manager installationGuide for more information about
NSM licensing.
10. Click Submit to save any changes, and then click Install to install the software.
Figure 5: Shared Disk Options for Regional Servers
Figure 6: Shared Disk Options for Central Managers
Configuring the NSM Software
NSMXpress supports shared disk via NFS only. Due to the data-intensive nature of
NSM, we recommend gigabit speed links (1000 Mbps) for shared disk use. For more
information about custom settings, refer to the Network and Security ManagerInstallation Guide.
9. Click Menu next to HA Links (see Figure 4 on page 12) to configure the second link in
the HA cluster (see Figure 7 on page 13). This step is optional.
Figure 7: HA Links Options
Use the options in this menu to set up a redundant link for the HA cluster. If you are
going to use a second link, you need to set the IP address for eth1 before configuring
this setting (see “Configuring the Network” on page 23 for details). Setting a redundant
link is optional. For more information about custom settings, refer to the Network andSecurity Manager Installation Guide.
If you configure HA with just one heartbeat link, then device management traffic and
data replication traffic both use that link. If you configure two links, device management
traffic uses the first link and data replication uses the second.
If you set the HA link count to 2, an expanded menu appears to configure the second
link:
Figure 8: Redundant Links
10. Click Menu next to HA Advanced Settings (see Figure 4 on page 12) to configure HA
advanced settings (see Figure 9 on page 14). This step is optional.
For more information about custom settings, referto the Network and Security ManagerInstallation Guide.
Advanced Options
Figure 9: HA Advanced Settings
11. Click Submit to save the HA options and return to the NSM Configuration Main Menu.
To display the Advanced Options menu, on the NSM Configuration Main Menu, select
Menu next to Advanced Options. The Advanced Options menu appears as shown in
Figure 10 on page 14.
https port for NBI service—Allows you to configure a port to listen for messages for the
NSM API. By default, this value is 8443. You can configure it to any port number from
1025 to 65535.
•
Remote Replication of Database—Mirrors the daily backup to an external server. You
can toggle it on or off. After you turn it on, use the menu options to configure this option.
•
SRS Enabled Options (regional server only)—Opens a menu to enable and configure
the Statistical Report Server (SRS). These options enable NSMXpress to interface
with SRS. You can toggle it on or off. When it is on, a menu with additional options is
available.
NOTE: SRS must be installed on a separate server from NSM.
The following sections provide details about the remote replication and SRS options:
•
Enabling and Configuring Remote Replication of the Database on page 15
•
Enabling and Configuring SRS (Regional Server Only) on page 16
Enabling and Configuring Remote Replication of the Database
To configure remote replication of database settings:
1. On the Advanced Options menu, click Menu next to Remote Replication of Database
(see Figure 4 on page 12) to configure daily backups (see Figure 11 on page 15).
Figure 11: Remote Replication of Database Options
2. Use the Remote Replication of Database option to turn remote replication on (y) or
off (n). The default is off.
3. Use the Hour of day to Replicate Database option to start the backup. The valid range
(in hours) is 00 through 23. The default is 2 AM.
4. Use the Remote Backup IP option to enter the IP address of the remote backup server.
Backup information is copied to the /var/netscreen/dbbackup directory on the remote
server. The “nsm” user must exist on both servers and you must establish an SSH trust
relationship. See the Network and Security Manager Installation Guide, for details.
7. Use the SRS Database Owner Password option to enter the SRS database password.
The password requires a minimum of eight characters and is case-sensitive. Reenter
it in the second text box.
8. Click Submit to save the options and return to the NSM Configuration Main Menu.
Installing NSM Software
After you submit all your configuration options, click Install to install the NSM software
on your NSMXpress appliance. Installation takes a few minutes. A status indicator shows
the progress of the installation. Wait until installation is finished before continuing to use
the Web interface.
Managing NSM Administration
Expand NSM Administration in the left navigation tree to access the options described
in this section. These options are available only after installing NSM.
The following sections explain how to use each of the NSM Administration options:
Managing NSM Administration
•
Changing the Superuser Password on page 17
•
Downloading NSM MIBS (Regional Server Only) on page 18
•
Exporting Audit Logs on page 18
•
Exporting Device Logs (Regional Server Only) on page 18
•
Generating Reports (Regional Server Only) on page 19
•
Modifying NSM Configuration Files on page 19
•
Backing Up the NSM Database on page 20
•
Changing the NSM Management IP on page 21
•
Scheduling Security Updates on page 21
Changing the Superuser Password
To change the superuser password, select NSM Administration > NSM Super User
Password. See Figure 13 on page 17.
To download any available MIBs, select NSM Administration > Download NSM MIBS,
and then click Download MIB. See Figure 14 on page 18. This option is not available on
the central manager.
Figure 14: Download NSM MIBs
Exporting Audit Logs
To export audit logs, select NSM Administration > Export Audit Logs. See Figure 15 on
page 18.
Figure 15: Export Audit Logs
To export an audit log to a csv file, select csv in the drop-down list box, and then enter
the csv file name in the text box.
To export an audit log to a system log server, select syslog in the drop-down list box,
and then enter the server IP address, if it is not the local host.
Exporting Device Logs (Regional Server Only)
To export device logs, select NSM Administration > Export Device Logs. See Figure 16
on page 18. This option is not available on the central manager.
To generate reports, select NSM Administration > Generate Reports. See Figure 17 on
page 19. This option is not available on the central manager.
Figure 17: Generate Reports
Managing NSM Administration
NOTE: The user is an NSM administrator and not an NSMXpress user. Enter
a user name as domain/user, such as global/super.
Modifying NSM Configuration Files
To manually edit the GuiSrv.cfg, DevSvr.dfg and HaSvr.cfgfiles, select NSM Administration
> Modify NSM ConfigurationFiles. The example in Figure 18 on page 20, shows the option
To change the IP address of the NSM management server, select NSM Administration
> NSM Management IP link under NSM Administration. See Figure 20 on page 21.
Figure 20: Change Management IP
Scheduling Security Updates
To schedule security updates, select NSM Administration > Schedule Security Updates.
See Figure 21 on page 22.
Use the options in the System Administration section to perform the tasks described in
the following sections:
•
Rebooting or Shutting Down NSMXpress on page 22
•
Changing the User Password on page 23
•
Configuring the Network on page 23
•
Managing RADIUS Servers on page 25
•
Monitoring with SNMP on page 28
•
Forwarding Syslog Messages on page 31
•
Changing the System Time on page 34
•
Installing Updates on page 34
•
Managing Users on page 35
•
Configuring the Web Interface on page 39
Rebooting or Shutting Down NSMXpress
To reboot or shut down NSMXpress, select System Administration > Bootup and
Shutdown, and then click either Reboot System or Shutdown System. See Figure 22
To change the user password, select System Administration > Change User Password,
fill out the form shown in Figure 23 on page 23, and then click Change.
Figure 23: Change User Password
Configuring the Network
To access options that allow you to configure the network, select System Administration
> Network Configuration.The Network Configurationwindow appears as shown in Figure
24 on page 23.
Managing System Administration
Figure 24: Network Interfaces Options
The following sections describe each of the options available in the Network Configuration
window:
•
Network Interfaces on page 23
•
Routing and Gateways on page 24
•
Hostname and DNS Clients on page 24
•
Host Addresses on page 25
Network Interfaces
Use this option to manage the network interfaces. See Figure 25 on page 24.
Use this option to manage host addresses, See Figure 28 on page 25.
Figure 28: Host Address
Managing RADIUS Servers
The NSMXPress WebUI supports authentication of users defined in the RADIUS servers,
in addition to authentication of locally defined admin users.
When a user logs into NSMXpress using the WebUI, the software first checks the UNIX
user database and then the WebUI user database to authenticate the user. If the user is
not a locally defined admin user, the software contacts the RADIUS servers added to the
RADIUS server list in the Web UI to authenticate the user. The RADIUS servers are
contactedin the order of priority set in the RADIUS server list. If any of the RADIUS servers
authenticates the user, the user is logged in with the privileges that are associated with
the user profile. If none of the servers authenticates the user, the user login fails.
NOTE: The NSMXpress appliance must be configured as a RADIUS client on
a RADIUS server so that the RADIUS server responds to authentication
requests from NSMXpress. Select any Juniper Make or Model in the
Make/Model field while adding an NSMXpress appliance as a RADIUS client.
You will need to update the juniper dictionary file (juniper.dct) in the RADIUS
server with the Juniper defined Vendor-Specific Attribute (VSA) for
NSMXpress:ATTRIBUTE Juniper-Nsmxpress-Profile Juniper-VSA(6, string)r . You will also need to add NSMXpress users with their associated user
profiles (SysAdmin, NSMAdmin, Operator, Guest), to the RADIUS database.
For more details see Steel-Belted Radius Documentation.
d. Auth Port: The RADIUS authentication software port. (We recommend UDP port
1812.)
e. Acct Port: The RADIUS accounting software port. (We recommend UDP port 1813.)
f. Disconnect/CoA port: The change of authorization or disconnect port.
g. Timeout (sec): Automatic time out in second(s) of the RADIUS access-request
after which the request will be retransmitted, if applicable. Enter a value between
1 and 10 seconds.
h. Retries: The number of times the RADIUS access-request must be retransmitted
for RADIUS authentication. Enter a value between 1 and 5.
4. Click Add. The RADIUS Servers dialog box appears with the RADIUS Server you added
listed.
Changing the Priority of RADIUS Servers
To change the priority of RADIUS servers:
1. Select System Administration > Radius Management. The RADIUS Servers dialog box
appears listing the RADIUS Servers that have been added.
2. To increase the priority of a RADIUS server, select the check box next to the name of
the server whose priority you want to increase, and click Move Up.
To decrease the priority of a RADIUS server, select the check box next to the name of
the server whose priority you want to decrease, and click Move Down.
Deleting a RADIUS Server
To delete a RADIUS server:
1. Select System Administration > Radius Management. The RADIUS Servers dialog box
appears listing the RADIUS Servers that have been added.
2. Select the check box next to the name of the server you want to delete, and click
Delete Selected.
NOTE: You need System Administration permissions to delete RADIUS
servers.
Editing RADIUS Server Parameters
To edit the parameters of a RADIUS server:
1. Select System Administration > Radius Management. The RADIUS Servers dialog box
appears listing the RADIUS Servers that have been added.
2. Click the name of the server whose properties you want to edit. The Edit RADIUS
Server dialog box appears. See Figure 31 on page 28.
3. Edit the parameters you want to change and click Save.
You can configure your NSMXpress appliance for SNMP monitoring from a network
operations server. The server can then issue periodic SNMP Get instructions to return the
status of the NSMXpress appliance.
You configure SNMP on the NSMXpress appliances with access credentials for either
SNMP v2c or SNMP v3. NSMXpress supports read-only access to the System Descriptor
(sysDescr) and Host Resource MIB.
This section provides instructions for configuring NSMXpress for SNMP monitoring. You
must provide access credentials for the SNMP server, a list of IP addresses from which
logon requests will be accepted, and the trap conditions to be reported to the SNMP
server.
To configure SNMP monitoring of your NSMXpress appliance, select SystemAdministration > SNMP Monitoring. The SNMP window appears. This window contains
the tabs described in the following sections:
•
SNMP Configuration on page 28
•
SNMP System Information on page 29
•
SNMP Trap Configuration on page 30
SNMP Configuration
To configure SNMP:
1. Select System Administration > SNMP Monitoring.
2. Select the SNMP Config tab, which is shown in Figure 32 on page 29.
3. Select the version of SNMP to be used, either v2c or v3.
4. Provide authentication information:
•
If you selected SNMP v2c, enter a username.
•
If you selected SNMP v3, enter a username and password.
Managing System Administration
The password must be at least 8 characters long.
NSMXpress implements a single username and password, which is effective only
for SNMP communication and is not related to any other username and password
used on the NSMXpress appliance.
5. To limit SNMP Get requests to specific servers, select Only, and then enter the IP
addresses of the permitted servers.
6. Click Save.
SNMP System Information
To configure SNMP system information:
1. Select System Administration > SNMP Monitoring.
2. Select the System Info tab, which is shown in Figure 33 on page 29.
Figure 33: Configuring SNMP System Information
3. Enter the following information, which is required for any SNMP-managed device:
NSMXpress provides a simple mechanism for configuring syslog messaging between the
NSMXpress appliance and a syslog receiver running rsyslog, syslog-NG, or basic syslog.
This mechanism simplifies choosing syslog receivers, data sources of the messages you
want to log, and the message transport used.
For the type of message transport, you can choose among TCP,SSL, and UDP. For rsyslog
or syslog-NG implementations use TCP or SSL. SSL adds security to TCP; if you select
SSL, NSMXpress createsa secure tunnel to the syslogreceiver. UDP messaging is available
for basic syslog implementations.
The following sections provide procedures for managing syslog message forwarding:
•
Viewing Syslog Receivers on page 31
•
Adding and Configuring Syslog Receivers on page 32
•
Editing Syslog Receiver Configurations on page 34
•
Deleting Syslog Receivers on page 34
Managing System Administration
Viewing Syslog Receivers
To view the syslog receivers configured on your NSMXpress appliance, followthese steps:
1. Select System Administration > Syslog Forwarding. The Syslog Forwarding window
Select SSL to create a secure tunnel to a syslog receiver in rsyslog or syslog-NG
implementations.
•
In the System Logs section of the Data Sources table, select the sources of data
from which system messageswill be forwardedto the syslog receiver. These sources
can include NSMXpress system messages, package updates, and mail logs.
•
In the NSM section of the Data sources table, select each GUI Server log, Device
Server log, and HA Server log to be forwarded to the syslog receiver.
8. Click Save to save and apply the configuration.
Editing Syslog Receiver Configurations
To edit a syslog receiver configuration, follow these steps:
1. Select System Administration > Syslog Forwarding.
2. In the Syslog Receivers window, click the name of the syslog receiver you want to edit.
The syslog receiver configuration window appears for the selected receiver.
3. Make the desired changes to the configuration.
4. Click Save to save and apply your edits to the configuration of this syslog receiver.
Deleting Syslog Receivers
To delete a syslog receiver configuration, follow these steps:
1. Select System Administration > Syslog Forwarding.
2. In the Syslog Receivers window, check the box next to each syslog receiver you want
to delete.
3. Click Delete selected receivers.
NSMXpress deletes the selected syslog receivers and any secure tunnels configured
for their use.
Changing the System Time
To set the system time, select System Administration > System Time. From the System
Time window, you can perform the following functions:
•
Set or change the system time.
•
Set the time zone.
•
Configure an NTP server to synchronize the system time with an external clock.
Installing Updates
Select System Administration > System Update to perform the following tasks:
The NSMXpress WebUIallows you to create multiple users with role-based access control
to the WebUI. You can create a user in the WebUI and associate the user to a predefined
user profile. You can also map a user created in the NSMXpress OS to a predefined user
profile in the WebUI. However, this user profile is only applicable to the local OS user in
the WebUI.
NOTE: You need System Administration permission to create users.
This topic contains the following sections:
•
Creating New NSMXpress Users on page 35
•
Deleting a User on page 37
•
Editing User Attributes on page 37
•
Understanding User Profiles on page 37
Creating New NSMXpress Users
To create a local OS user:
1. Select System Administration > User Management. The NSMXpress Users dialog box
appears listing all NSMXpress users. See Figure 36 on page 35.
Figure 36: NSMXpress Users Dialog Box
2. Click Create a new NSMXpress User. The Create NSMXpress user dialog box appears.
6. Select the user profile you want to associate with this user from the User Profile
drop-down list box.
7. Click Submit. The NSMXpress Users dialog box appears with the new NSMXpress user
listed.
Deleting a User
To delete a user:
1. Select System Administration > User Management. The NSMXpress Users dialog box
appears listing all NSMXpress users.
2. Select the check box next to the name of the user you want to delete and click Delete
Selected. Click Delete User in the Delete Users confirmation dialog box that appears.
NOTE: You cannot delete admin users or change their user profiles.
Editing User Attributes
To edit user attributes:
1. Select System Administration > User Management. The NSMXpress Users dialog box
appears, with all NSMXpress users listed.
2. Click on the name of the user whose attributes you want to edit. The Edit NSMXpress
Users dialog box appears.
3. Edit the parameters you want to change and click Submit. You can change the
password and the user profile.
Understanding User Profiles
NSMXpress provides four predefined user profiles that allow you to implement role-based
accesscontrol over the NSMXpress WebUI.A user created via the WebUIor in the RADIUS
server can be associated with any one of the following profiles:
•
System Administrator—System Administrators are superusers for the NSMXpress
WebUI and have full access to all the modules in the NSMXpress WebUI.
•
NSM Administrator—NSM Administrators have access to NSM Administration, Radius
Management, Maintenance and Troubleshooting modules.
•
Network Operator—Network Operators have access to Network Utilities and Report
Generation Modules.
•
Guest User—Guest Users haveread access to System Information and System Statistics
modules.
When a user logs in, NSMXpress modules are displayed or hidden based on the user
profile and the permissions associated with the profile. For more details about user
profiles and permissions, see Table 4 on page 38.
Table 4: NSMXpress WebUI User Profiles and Permissions (continued)
Maintaining NSMXpress
Configuring the Web Interface
To specify which NSM client computerscan accessNSMXpress through the Webinterface,
selectSystemAdministration> WebUI Configuration. The AllowedIP Addresseswindow
appears as shown in Figure 39 on page 39.
Figure 39: Web Interface Access
System
AdministratorNSMXpress Modules
NSM
Administrator
Network
Operator
Guest User
NoYesYesYesError Logs
NoYesYesYesNetwork Utilities
NoYesYesYesTech Support
YesYesYesYesSystem Information
Maintaining NSMXpress
The Maintaining section of the NSMXpress navigation tree allows you to perform the
tasks described in the following sections:
•
Viewing System Statistics on page 39
•
Upgrading the Recovery Partition on page 41
Viewing System Statistics
To view system statistics, select System Administration > Maintenance > System
Statistics. The system Statistics window appears as shown in Figure 40 on page 40.
The recovery partition contains all files necessary to perform a clean installation of the
NSMXpress OS and its applications with default settings. It provides a last-resort recovery
mechanism. When the NSMXpress appliance is shipped from the factory, the recovery
partition files match the version of the NSMXpress OS with factory default settings.
Using the Recovery Upgrade option, you can make the current version of NSMXpress
available for recovery, displacing the existing files in the recovery partition. The factory
default recovery files are retained as an alternative recovery choice. Other versions are
deleted.
Recovery upgrade uses two sets of packages to create a set of files from which you can
perform a clean installation. One set makes up the NSMXpress OS, the other a set of
upgrade script packages. Both sets are usually retained in the local file system. The
NSMXpress OS set can also be downloaded form the Juniper Networks software
repository.
NSMXpress splits the recovery upgrade process into a preparation phase and an upgrade
phase. In the preparation phase, NSMXpress assembles a copy of the current version of
the image files in temporary workspace. In the upgrade phase, NSMXpress replaces the
old recovery image files, and installs the current version of the image files from the
temporaryworkspaceinto the recovery partition. By splitting the process into two phases,
NSMXpress minimizes the period of vulnerability while the upgrade itself takes place.
Maintaining NSMXpress
To upgrade the recovery partition, follow these steps:
1. Select System Administration > Maintenance > Update Recovery Partition.
If the new recovery partition files have already been prepared,then the Upgrade screen
appears. Proceed with the upgrade phase as described in step 5.
If the upgrade files have not yet been prepared, the Upgrade Preparation window
appears. Proceed with the preparation phase in step 2.
2. Enter the location of the NSMXpress Regional server or Central Manager upgrade zip
file, downloaded from the Juniper Customer Support Center when upgrading NSM,
on the local file system.
3. If the NSMXpress Offline server upgrade file is available on the local file system, enter
the location and name of the NSMXpress offline server upgrade file in the System
upgrade source field. If the NSMXpress offline server upgrade file is not available on
the local file system and the appliance has access to the Juniper Update site, select
Online.
4. Click Prepare System.
The Preparation Progress screen shows the progress of the operation.
Errors are reported if the required files are unavailable, disk space is not sufficient, or
the previous version files are invalid.
When preparation is completed, the Upgrade window appears.
5. In the Upgrade window, enter the admin WebUI passwordand then click Start Update.
Use the options in the Troubleshooting section to access the following information and
utilities:
•
Auditing User Operations on page 42
•
Error Logs on page 43
•
Network Utilities on page 44
•
Tech Support on page 47
Auditing User Operations
The upgrade process usually takes less than one minute.
CAUTION: Do not interrupt the upgrade process. If you do, your NSMXpress
appliance might not boot normally.
You can audit all user operations performed in NSMXpress. Users with System
Administrator and NSM administrator permissions can view all Actions Logs in NSMXpress.
Actions by NSMXpress Users: Select the By any user check box to select actions by
all users. Select the By user check box and choose a username from the drop-down
list to specify actions by a particular user. Select By any user except and choose a
username from the drop-down list to exclude actions by a specific user.
•
Actions by User Profile: Select the By any profile check box to select actions by all
user profiles. Selectthe By profile check box and choose a profile from the drop-down
list to specify actions by a specific user profile. Select By any profile except and
choose a profile from the drop-down list to exclude actions by a user profile.
•
Actions by authentication mechanism: Select the By any authentication check box
to select actions by all authentication mechanisms. Select the By authentication
check box and choose an authentication mechanism from the drop-down list to
specify actions by a specific authentication mechanism. Select By any authentication
except and choose a profile from the drop-down list to exclude actions by an
authentication mechanism.
•
Actionsin module: Select the In any module check box to select actions in all modules.
Select the In module check box and choose a module from the drop-down list to
specify actions in a particular module.
•
Actions on dates: Select the At any time check box to select actions at any time.
Selectthe For today only check box to select today’s actions. Select the For yesterday
only check box to select yesterday’s actions. Select the During the last week check
box to select last week’s actions. Select the Between check box and enter the start
date and end date in the drop-down list to view actions within the specified time
period.
3. Click Search. The Search Results dialog box appears with the result of your query. See
Figure 42 on page 43.
Figure 42: Search Results Dialog Box
Error Logs
To review error logs, select Troubleshooting > Error Logs. Figure 43 on page 44 shows
an example,
To view details of an individual error log, select the file you want to view and click View.
Figure 44 on page 44 shows sample error log details.
Figure 44: Error Log Detail
Network Utilities
To access basic network utilities (ping, traceroute, and nslookup) for TCP/IP Networking,
select Troubleshooting > Network Utilities. These tools also provide an IP subnet
calculator. SeeFigure 45 on page 44.
Figure 45: Network Utilities Options
Ping
Ping is a tool for checking network connectivity. NSMXpress prompts with questions so
you can focus your search.
Enter the number of packets this ping command will send. The default is 5. The values
range from 1 through 99.
Packet Size
Enter the packet size (in bytes) this ping command will send. The default is 56. The values
range from 1 through 9999.
How Many Sec Between Sending Each Packet
Enter how much time (in seconds) ping should wait between sending each packet.
Patterns to Send (Hex)
The data sent by ping contains a hexadecimal pattern. If you leave this option blank, ping
will fill it with random data. This option is useful if you do not have problems with
connectivity itself but with data loss.
Verbosity Output
NSMXpress lists the ICMP packets (other than ECHO_Response) that have been received.
Numeric Output Only
Check this option if you do not want any attemptsto be made to look up symbolic names
for host addresses.
Bypass Routing Tables
If the host is not a directly attached network, an error is returned. This option can be used
to ping a local host through an interface that has no route through it.
Traceroute
Traceroute is a tool to print the route a packet takes to a network host. See Figure 47 on
page 46.
NOTE: The only required field is Hostname. The value can be either a
hostname or an IP address.
Lookup
Use the lookup tool to obtain the IP address from a hostname and the hostname from
an IP address (see Figure 48 on page 46). The query type drop-down list contains several
types of records found in the DNS database. Enter a nameserver or select the default. If
you choose the default, nslookup will use the server on which NSMXpress is installed.
Figure 48: Lookup Utility
IP Subnet Calculator
Use the IP subnet calculator to calculate the netmask for a TCP/IP-network. You can
calculate a netmask by class and subnet bits or by the number of hosts (See Figure 49
on page 47) When you calculate a netmask by the number of hosts, NSMXpress returns
the smallest network available.
To get contact information for Juniper Networks technical support, select Troubleshooting
> Tech Support. To help analyze problems, select a detail type in the drop-down list box,
and then click Run Tech-Support Script. NSMXpress creates a file you can download
and send to Juniper Networks technical support. See Figure 50 on page 47.
Figure 50: Juniper Tech Support
Viewing System Information
Use the SystemInformation menu item to display information about the server, including
CPU load and memory use, as shown in Figure 51 on page 48.
Table 5 on page 48 describes the documentation for NSMXpress and NSM.
Table 5: Network and Security Manager Publications
DescriptionBook
Network and Security
Manager Installation Guide
Network and Security
Manager Administration
Guide
Network and Security
Manager Configuring
ScreenOS and IDP Devices
Guide
Describes 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 or upgrade of
NSM.
Describes how to use and configure key management features in
the NSM. It provides conceptual information, suggested workflows,
and examples. 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 user interface (UI).
This guide is intended for application administrators or those
individuals responsible for owning the server and security
infrastructure and configuring the product for multiuser systems. It
is also intended for device configuration administrators, firewall
and VPN administrators, and network security operation center
administrators.
Describes NSM features related 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.
Network and Security
Manager Online Help
Provides procedures for basic tasks in the NSM user interface. It
also includes a brief overview of the NSM system and a description
of the GUI elements.
Table 5: Network and Security Manager Publications (continued)
DescriptionBook
Network and Security
Manager API Guide
Network and Security
Manager Release Notes
NSMXpress and NSM3000
User Guide
Requesting Technical Support
Technical product 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
Provides complete syntax and a description of the Simple Object
Access Protocol (SOAP) messaging interface to NSM.
Provides the latest information about features, changes, known
problems, resolved problems, and system maximum values. If the
information in the Release Notes differs from the information found
in the documentation set, follow the Release Notes.
Release Notes are included on the corresponding software CD and
are available on the Juniper Networks Website.
Describes how to set up and manage the NSM appliances as a
central manager or regional server.
•
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:
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/ .
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
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.