Your Value Description
Parameter
The command to mount the shared data partition.
The default command is:
/bin/mount /var/netscreen/DevSvr Command to mount
the shared disk partition
The command to unmount the shared data partition.
Before configuring this command, you must first verify that your mounts are defined properly.
The default command is:
/bin/umount /var/netscreen/DevSvr Command to unmount
the shared disk partition
The command to check the integrity on the shared data partition.
Directory path of the shared disk mount point.
Directory path for the shared disk
Prerequisite Steps
You can upgrade the management system from any previous running version of NSM.
Before you install the management system, you need to perform the following prerequisite steps:
1. Using your current version of NSM, upgrade any devices running ScreenOS 4.0.x or earlier version or remove them from your managed network. ScreenOS devices must run ScreenOS 5.0 or later version to be managed by NSM 2008.1 or later release. The NSM installer stops with errors if ScreenOS 4.0.x devices are present in the NSM database.
2. Ensure that the NSM appliance is accessible through a Serial Console 3. Log in to the appliance as root.
If you are already logged in as a user other than root, then run the following command to become root:
su
At the password prompt, enter the root password for the appliance.
NOTE:Although the management system runs with nsm user permissions, you must have root permissions to run the NSM installer.
4. Partition drives for sufficient disk space to accommodate your planned data requirements. Ensure that you have allocated a maximum amount of disk space for the data partition (/ partition).
See“Hardware Recommendations” on page 265for more information about the disk space requirements appropriate for your specific network.
5. Perform a backup of all files on the Device Server and GUI server. See“Archiving and Restoring Logs and Configuration Data” on page 238for more information archiving your data files.
6. Run the system update utility for your appropriate platform to ensure that you have all the up to date utilities and packages required to run the NSM installer properly.
See“Running the System Update Utility” on page 159for more information on running the system update utility.
7. Configure shared memory size on your appropriate platform. See“Configuring Shared Memory Size” on page 159for more information.
8. Increase the rsync backup timeout and rsync replication timeout values to 3600. See
“Setting the rsysnc Timeout Values” on page 160.
9. If you are upgrading NSM on a Solaris server, ensure that all required locales have been installed and that the necessary edits to the /etc/default/init files have been made. See“Preparing a Solaris Server for NSM” on page 161for details.
Running the System Update Utility
Use the system update utility to upgrade your system with the latest patches and packages required to run the NSM management system installer properly.
NOTE: The NSM 2012.2 system update utility is compatible with Red Hat Enterprise Linux 4.0 Update 5 or version 5.0.
To run the system update utility:
1. Copy the system update utility appropriate for your platform from the NSM Installation directory to a suitable directory on the server.
We recommend that you save the utility in the /usr subdirectory.
2. Uncompress the system update utility file using the gzip command. For example:
gzip -d nsm2012.2-systemupdate-linuxES_5.tar.gz
3. Uncompress the appropriate system update utility .tar file. For example:
tar xfv nsm2012.2-systemupdate-linuxES_5.tar
A subdirectory for the platform ("es4", “es5”, or "sol10") is created and all of the files required to update your system packages and utilities are extracted into that directory.
4. Navigate to the subdirectory.
5. Run the update shell archive script. For example, you can execute the shell archive script by running the following command:
<platform>.sh
For example, on Linux es4, the update script is named rhes4_upd3.sh and located in the es4 directory.
For Solaris, the systemupdate-solarisplatform.tar file expands to <platform> and the update script is put in that directory. The script for Solaris is located in the same directory as the tar file. The name of the update script for Solaris is update_solaris10.sh.
The script proceeds to check your system for required updates. It next prompts you to press Enter to continue or Ctrl-C to stop.
6. Press Enter to continue. The script proceeds to cleanup the RPM database. Let the script run to completion. This process can take up to 10 minutes depending upon the number of packages that need to be installed.
Configuring Shared Memory Size
Both the GUI and Device Server require that you modify the operating system shared memory in order to start and run.
On Solaris systems, you can do this by adding/updating the following in /etc/system:
set shmsys:shminfo_shmmax= 402653184 set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256 set shmsys:shminfo_shmseg=256 set semsys:seminfo_semmap=256 set semsys:seminfo_semmni=512 set semsys:seminfo_semmns=512 set semsys:seminfo_semmsl=32
On Linux systems, you can do this by adding/updating the following line in /etc/sysctl.conf:
kernel.shmmax= 402653184
After updating the shared memory requirements on your Linux or Solaris system, you must restart the server for your new settings to take effect.