HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide (web version) (T1780-96078, March 2008)

Linux systems installation
99
Example of changing the value (when the new-setting-value is calculated to be 512 MB):
Before: java -Xmx256m -classpath ...
After: java -Xmx512m -classpath ...
3. Restart the Device Manager server as follows:
Execute the following command:
installation-directory-for-the-Device-Manager-server/suitesrvcntl -
stop_hdvm
After the Device Manager server has stopped, execute the following command:
installation-directory-for-the-Device-Manager-server/suitesrvcntl -
start_hdvm
The following shows an example of executing the commands:
# /opt/CVXPAE/suitesrvcntl -stop_hdvm
# /opt/CVXPAE/suitesrvcntl -start_hdvm
4-2 Installing the Device Manager server and
Common Component
This section explains the preparations for installing Device Manager, and describes how to perform
a new installation, an upgrade installation, and a re-installation of Device Manager.
NOTE: If you perform an upgrade installation, you cannot install Device Manager whose version
or revision is earlier than the one already installed. For example, in an environment in which
Device Manager 5.0 has been installed, you cannot install Device Manager 1.1 or an earlier
version. However, a build to which patches have been applied can be overwritten with the build
without the patches, as long as the version-revision numbers are the same. For example, after
installing a build of Device Manager 5.0 to which patches have been applied, you can install the
previous build that does not contain the patches.
The following is the default installation directory for the Device Manager server:
/opt/CVXPAE
The following is the default installation directory for the XP Provisioning Manager server:
/opt/CVXPAE/ProvisioningManager
4-2-1 Preparations for installation
Before you start installation, check the usage status of the port numbers, the installation status of
other programs, and other information as described below.
4-2-1-1 Checking port numbers
Check whether the port numbers required to use Device Manager are being used by another
product on the machine on which the Device Manager server is to be installed by using the
netstat command.
Example: Check whether another program is using the port 162/udp.
Execute the following command:
In Linux: netstat -uan