2.5.2 Initial startup problems
- Organization of this subsection
(1) Problem: The user cannot run the NNMi command line tools on Linux NNMi management servers
(a) Solution
Check whether system environment variable PATH includes /opt/OV/bin. If it does not, add /opt/OV/bin to system environment variable PATH.
(2) Problem: JBoss port contention
(a) Solution
By default, JBoss Application Server uses several ports for communication with NNMi. These ports are commonly used by other applications as well.
To resolve any port contention, follow these steps:
As a user with administrator privileges (Windows) or root privileges (Linux), open the following file in any text editor:
Windows
%NnmDataDir%Conf\nnm\props\nms-local.properties
%NnmDataDir% is the data directory specified during installation.
Linux
/var/opt/OV/conf/nnm/props/nms-local.properties
Modify the existing entries, replacing any conflicting port numbers with available port numbers.
Save the changes.
Execute the following commands to restart the NNMi services:
ovstop -c ovstart -c
- Note
For Windows, the ovstop and ovstart commands can be executed from the Start menu. For details about the ports used by NNMi, see the nnm.ports Reference Page.
(3) Problem: NNMi is not discovering nodes
(a) Solution
From the Workspace navigation panel, select the Configuration workspace.
From Configuration, open the Seeds view.
Check the values in the Discovery Seed Results column.
If the status of many of the discovered nodes is something other than Node created, then the NNMi discovery process was not successful.
If the status is No SNMP response, verify that you can ping the node, and that you can run the nnmsnmpwalk.ovpl command to obtain information from the node. For details, see the nnmsnmpwalk.ovpl Reference Page. If you cannot run these tools, check the following items:
a. Ping the node to make sure it is responding.
b. Make sure that the node has SNMP enabled.
c. Make sure that the node has your local management server on its access list of SNMP agents.
d. Be sure to configure the correct community strings for the nodes so that NNMi discovers them correctly. This information is listed on the Communication Configuration form on the Default SNMPv1/v2 Community Strings tab.
e. Make sure that there are no Access Control Lists configured on your routers, switches, or firewalls that might be limiting discovery.
For details, see Configure Discovery in NNMi Help.
(4) Problem: You cannot start the NNMi console when accessing a Windows NNMi management server
If you cannot start an NNMi console when pointing your browser to a Windows NNMi management server, a firewall might be blocking the HTTP port. To troubleshoot this problem, run the browser on the NNMi management server. If you can access the NNMi console from this browser, but remote browsers fail, you need to check your ports.
To remedy this problem, add the nmsas.server.port.web.http value shown in the %NnmDataDir%conf\nnm\props\nms-local.properties file to the list of allowed ports. For details, see the nnm.ports Reference Page.
%NnmDataDir% is the data directory specified during installation.
(5) Problem: The NNMi console does not open after a successful installation or upgrade of NNMi
Also, the following error message appears in latest copy of the incidentActions.*.*.log file (available in the /var/opt/OV/log/nnm/public directory on the NNMi management server):
SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer:
Failed to get port number from /var/opt/OV/tmp/actionServer.port due to java.io.FileNotFoundException.
/var/opt/OV/tmp/actionServer.port.lock (Permission denied) : java.io.FileNotFoundException:
/var/opt/OV/tmp/actionServer.port.lock (Permission denied)
(a) Solution
-
Run the following commands on the NNMi management server:
a. /opt/OV/bin/ovstop
b. chown root:root /var/opt/OV/tmp
c. chmod 777 /var/opt/OV/tmp
d. chmod g+s /var/opt/OV/tmp
-
Look for the actionServer.port and actionServer.port.lock files in the /var/opt/OV/tmp directory.
Delete those files if they exist.
Run the following command on the NNMi management server:
/opt/OV/bin/ovstart