User Privileges On An Nsm Appliance - Juniper NETWORK AND SECURITY MANAGER 2010.4 - INSTALLATION GUIDE REV1 Installation Manual

User Privileges on an NSM Appliance

Copyright © 2010, Juniper Networks, Inc.
Copy the and
5. Guidb.tar
Extract the database:
6.
cd /var/netscreen ; tar xvpf Guidb.tar
cd /var/netscreen ; tar xvpf Devdb.tar
Log in as the nsm user by entering the following command and using the admin
7.
password:
sudo su - nsm
NOTE: If you are not using the same IP address in the NSM appliance as
you had for the Linux server, follow steps 6, 7, and 9 of the procedure for
migrating data from Solaris to an NSM appliance. See "On the NSM
appliance:" on page 166.
Also make sure that the
/var/netscreen/DevSvr/devSvr.cfg
NOTE: If you are migrating only the GUI Server data directory to the NSM
appliance, follow steps 6, 8, 9, and 10 of the procedure for migrating data
from Solaris to an NSM appliance. See "On the NSM appliance:" on page 166.
These steps are required:
Delete the existing RSA keys between devSvr and guiSvr from the
devSvr.cfg
Correct the one-time client password in
If the Linux server used a customized device server data directory, then you must open
8.
the /var/netscreen/pgsql/data/postgresql.conf
the config parameter from the customized path used on the Linux
?data directory?
server to the default
/var/netscreen/DevSvr/
Start the HaSvr, GuiSvr, and DevSvr processes:
9.
/usr/netscreen/HaSvr/bin/haSvr.sh start
The NSM appliance allows you to execute commands with root privileges or nsm privileges
and to switch back and forth.
Log in as admin and execute the sudo su - nsm command any time you want to run
an NSM-specific command, such as starting or stopping a service manually or running
a CLI command.
Log in as admin and execute the sudo su - command any time you want to reboot or
shut down.
Chapter 7: Upgrading NSM Appliances to NSM 2010.4
archive files to
Devdb.tar /var/netscreen
guiSvrX.addr details in the
file are correct.
file so they can be renegotiated and established again.
file on the NSM appliance and change
before starting the NSM server processes.
.
.
devSvr.cfg
169