2.2 Preparing the preinstallation NNMi management server environment

An NNMi management server is a server on which the NNMi software is installed. Each NNMi management server must be a dedicated 64-bit machine. To learn more about hardware prerequisites, see 2.1 Checking the hardware and software.

Before you install NNMi on the NNMi management server, complete the checklist in Table 2-1.

Important note

Configure the remote desktop as described below before installing and configuring NNMi. This configuration increases the resources that Windows uses, so we recommend that you return to the original configuration after you complete these tasks, if necessary.

Configuration path

Windows Server 2008

Administrative Tools > Terminal Services > Terminal Services Configuration

Windows Server 2008 R2

Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration

Windows Server 2012 and later

Local Group Policy Editor^# > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders

#: To open Local Group Policy Editor, enter gpedit.msc in the Start window.

Configuration settings

Windows Server 2008 and Windows Server 2008 R2

Clear the Use temporary folders per session and Delete temporary folders on exit check boxes. Log off, and then log back on to apply the new settings to the system.

Windows Server 2012 and later

Enable Do not use temporary folders per session and Do not delete temp folder upon exit. To apply these settings to the system, log off and then log on again.

Table 2‒1: NNMi management server preinstallation checklist
Completed? (y/n)	NNMi management server preparation
	Make sure that the host name of the server where you plan to install NNMi is RFC-compliant. Host names are allowed to use alphanumerics (`A` to `Z`, `a` to `z`, `0` to `9`), hyphens (`-`), and periods (`.`) (to demarcate domain names). Setup of host names that are not RFC-compliant (host names that use underscores (_), for example) might result in failure of the NNMi console connection or command execution.
	Make sure that the name of the local host can be resolved on the server on which NNMi is installed and that `localhost` is set up with the name resolved to `127.0.0.1`.
	Windows Make sure that the `C` drive is used as the OS's system drive. NNMi cannot be installed in an environment where the system drive is not drive `C`.
	Windows If you have restrictive security settings in place, you might need to adjust the permission on the drive or drives on which you want to place the NNMi install and data directories. For details, see A.1 Specifying disk drive security settings (Windows).
	Windows Short file names in the 8.3 format must be enabled. If they are disabled, execute the following command: `fsutil` `behavior` `set` `disable8dot3` `0` Short file names in the 8.3 format must also be set if the directory specified as the installation directory and the names of its parent directories are not in the 8.3 format. If short file name are not set, execute the following command: `fsutil` `file` `setshortname` `directory-being-configured` `short-file-name`
	Windows Check for the SNMP service; if installed, the SNMP trap service needs to be disabled on this server.
	Install and enable a supported Web browser. For details, see 2.1 Checking the hardware and software and A.3 Enabling the Web browser for the NNMi console.
	Dynamic Host Configuration Protocol (DHCP) users: Makes sure that the NNMi management server is consistently assigned the same IP address.
	Windows To improve installation performance, disable anti-virus software until NNMi installation is complete. When NNMi installation is complete, restart the anti-virus software.
	Linux Before you can install NNMi on a Linux server, the library files listed below that are needed by NNMi must be installed. Also, install the library files that have dependence relationships with these files: `/lib64/libaio.so.1` `/usr/lib/libstdc++.so.6` `/usr/lib64/libXtst.so.6` `/usr/lib64/libXi.so.6` For details, see A.4 Installing required libraries in Linux.
	Do not install NNMi until you have verified that all ports used by NNMi are available. For a list of the ports used by NNMi and the direction in which data passes through the firewall, see C. List of Ports Used by NNMi in the manual Job Management Partner 1/Consolidated Management 2/Network Node Manager i Setup Guide.
	Do not block communication with the IP address of the local host, such as by using a firewall.
	Configuration information from earlier versions of NNM remains, even if NNM is removed. See the Release Notes for the earlier version of NNM to identify the older information, and then delete that information prior to installing NNMi.
	Windows Before installing NNMi, make sure that the Windows Services window (the window started from Control Panel > Administrative Tools > Services) is not running. If it is, close it.
	Windows If the sum of the character string set in the system environment variable `Path` and the lengths of the directory paths below is 950 bytes or more, NNMi installation might fail even on OS versions that allow character strings of 1,024 bytes or more to be set in environment variables. `%NnmInstallDir%bin\;` `%NnmDataDir%shared\nnm\actions\;` Temporarily shorten the character string set in `Path`, and then install NNMi. After installation is complete, you can again add to the character string in system environment variable `Path`, within the bounds that the OS can handle.
	Windows If you are installing NNMi using a path other than the default, you can use alphanumerics (`A` to `Z`, `a` to `z`, `0` to `9`), hyphens (`-`), periods (`.`), underscores (`_`), and single-byte spaces for the names of the install and data directories. The maximum length of the absolute paths for these directories is 60 characters.
	Windows Do not specify paths that include junction points, such as `drive:\Documents` `and` `Settings`. Doing so might cause problems, such as temporary files not being deleted.
	Windows If you install NNMi in an environment in which environment variables `%TEMP%` and `%TMP%` have different values, installation might fail. Make sure that the values of `%TEMP%` and `%TMP%` are the same before installation. If they differ, set `%TEMP%` and `%TMP%` to the same values.
	Windows Do not set the following variables as environment variables: `LANG` Anything that begins with `LC` If another product sets these environment variables, it might not be compatible with NNMi. Installation might fail if NNMi is installed with these variables set.
	Windows In Windows Server 2008 R2 or Windows Server 2012 or later, if a Remote Desktop session host has been installed in Remote Desktop Services, the following setting is required before you install NNMi: Execute `change` `user` `/install` to change to install mode. For details about this setting, see Help for the Remote Desktop session host. In the case of Windows Server 2008, substitute terminal server for Remote Desktop session host in the text above.
	Windows If changes you have made to the system on which you plan to install NNMi require restarting the OS, do so prior to installing NNMi. For example, the OS must be restarted if the registry value below exists. If this value exists, NNMi might suspend the installation: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session` `Manager\PendingFileRenameOperations` This registry value normally disappears when the OS is restarted.
	Windows NNMi uses a `%TEMP%` directory of up to 500 MB when it is installed or removed. The install or removal might fail without sufficient disk space. UNIX NNMi uses a `/tmp` directory of up to 1 GB when it is installed or removed. The install or removal might fail without sufficient disk space.
	Windows During installation, under Administrative Tools > Terminal Services > Terminal Services Configuration (for Windows Server 2008 R2, Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration), clear the Use temporary folders per session and Delete temporary folders on exit check boxes. Log off, and then log back on to apply the new settings to the system. In Windows Server 2012 and later, under Local Group Policy Editor > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders, enable Do not use temporary folders per session and Do not delete temp folder upon exit. To apply these settings to the system, log off and then log on again.
	UNIX If you are re-installing NNMi, also re-install all applications that require NNMi and configure them accordingly.
	UNIX Install applications that require NNMi after the configuration of the environment that follows NNMi installation has been completed. Remember to execute the `ovstop` command before you install applications.
	UNIX During NNMi installation, do not change the size of the terminal window in which Hitachi PP Installer is running. Doing so might prevent NNMi from installing properly.
	HP-UX The kernel must be configured (check using `/usr/sbin/smh`). Configure kernel parameters in the `Kernel` `Configuration/Tunables` section. Add `50` to `nproc`. The minimum value is 300. If `max_thread_proc` is less than 2,048, set it to `2048`. If `nkthread` is less than 10,000, set it to `10000`. Adjust `filecache_max` as needed so that an `ovjboss` heap can be allocated. For details about the minimum size for the `ovjboss` heap, see Java heap size in 4. Memory and Disk Space Requirements in Release Notes.
	Linux NNMi requires a UDP reception buffer of 8 MB and a UDP transmission buffer of 2 MB. To change the settings for memory spaces allocated to buffers, edit the `/etc/sysctl.conf` file to add the following entries: `#` `NNM` `settings` `for` `UDP` `receive` `and` `send` `buffer` `sizes` `net.core.rmem_max` `=` `8388608` `net.core.wmem_max` `=` `2097152` After editing the `/etc/sysctl.conf` file, apply the changes by restarting the OS or executing the `/sbin/sysctl` `-p` command.
	Linux The value of `kernel.shmmax` might be too small. If it is, edit the `/etc/sysctl.conf` file to add the following entries. Hitachi recommends a value of 64 GB. `#` `NNM` `settings` `for` `embedded` `database` `kernel.shmmax` `=` `68719476736` If you set the value of `kernel.shmmax`, after editing the `/etc/sysctl.conf` file, apply the changes by restarting the OS or executing the `/sbin/sysctl` `-p` command.
	Solaris NNMi requires a UDP reception buffer of 8 MB and a UDP transmission buffer of 2 MB. To change the UDP memory allocations, execute the following command: `ndd` `-set` `/dev/udp` `udp_max_buf` `8388608` To apply the change made to the UDP memory allocation after a system restart, create a system start script. Example: Create the `/etc/init.d/ndd` file. Example of `ndd` file: `#!/bin/sh` `ndd` `-set` `/dev/udp` `udp_max_buf` `8388608` Set the file permissions. `chmod` `0744` `/etc/init.d/ndd` `chown` `root:sys` `/etc/init.d/ndd` To start the NNMi service at run level 3, create the `/etc/rc3.d/S70ndd` file. `cd` `/etc/init.d` `ln` `ndd` `/etc/rc3.d/S70ndd`
	Solaris NNMi uses shared memory. Set the amount of shared memory according to the amount of physical memory, as follows: If physical memory is less than 8 GB, allocate 1 GB of shared memory. If physical memory is at least 8 GB but less than 16 GB, allocate 2 GB of shared memory. If physical memory is at least 16 GB but less than 24 GB, allocate 3 GB of shared memory. If physical memory is 24 GB or greater, allocate 5 GB of shared memory. To set `project.max-shm-memory`, set its value in both the `user.root` project and the `system` project. The following example sets `project.max-shm-memory` to 5 GB: `prctl` `-n` `project.max-shm-memory` `-v` `5368709120` `-r` `-i` `project` `user.root` `projmod` `-a` `-K` `"project.max-shm-memory=(priv,5368709120,deny)"` `user.root` `prctl` `-n` `project.max-shm-memory` `-v` `5368709120` `-r` `-i` `project` `system` `projmod` `-a` `-K` `"project.max-shm-memory=(priv,5368709120,deny)"` `system` If the NNMi service is configured to start automatically at system startup, `/etc/init.d/netmgt` is executed at system startup. Make sure the system project settings have been updated before `/etc/init.d/netmgt` is executed.
	Solaris You must increase the number of semaphores to 256. To set `project.max-sem-ids`, set its value in both the `user.root` project and the `system` project. The following example sets `project.max-sem-ids`: `prctl` `-n` `project.max-sem-ids` `-v` `256` `-r` `-i` `project` `user.root` `projmod` `-a` `-K` `"project.max-sem-ids=(priv,256,deny)"` `user.root` `prctl` `-n` `project.max-sem-ids` `-v` `256` `-r` `-i` `project` `system` `projmod` `-a` `-K` `"project.max-sem-ids=(priv,256,deny)"` `system` If the NNMi service is configured to start automatically at system startup, `/etc/init.d/netmgt` is executed at system startup. Make sure the system project settings have been updated before `/etc/init.d/netmgt` is executed.
	Solaris When the `useradd` command is used to create users, by default the home directory will be `/home/user-name`. However, under the default settings in Solaris, directories cannot be created in `/home`. If your environment does not allow directories to be created in `/home`, change the `useradd` command's default home directory to a location that allows directories to be created. The following example changes the default home directory to `/export/home/user-name`: `#` `/usr/sbin/useradd` `-D` `-b` `/export/home`
	Solaris If you will be upgrading NNMi, check the home directory of the user `nmsdbmgr` before upgrading. The following shows an example of the command used to check the home directory: `#` `/usr/bin/finger` `nmsdbmgr` If the home directory of the user `nmsdbmgr` (for example, `/home/nmsdbmgr`) cannot be created, change the home directory to a directory that can be created. The following example changes the home directory of the user `nmsdbmgr` to `/export/home/nmsdbmgr`: `# /usr/sbin/usermod -d /export/home/nmsdbmgr nmsdbmgr`

To Page Top