B.2 Initial startup problems

(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.

(a) Solution

The URL for accessing the NNMi console includes the port that JBoss Application Server uses for communicating with the NNMi console. To access the NNMi console, enter the following URL into a Web browser window:

http://fully-qualified-domain-name:port/nnm/

where fully-qualified-domain-name is the fully qualified domain name of the NNMi management server, and port is the port that JBoss Application Server uses for communicating with the NNMi console.

If your NNMi management server has more than one domain name, NNMi chooses one during the installation process. To determine which fully qualified domain name NNMi is using, run the nnmofficialfqdn.ovpl script. For details, see the nnmofficialfqdn.ovpl Reference Page.

To determine which port JBoss Application Server is using, use the following files:

Windows

%NnmDataDir%Conf\nnm\props\nms-local.properties

%NnmDataDir% is the data directory specified during installation.

UNIX

/var/opt/OV/conf/nnm/props/nms-local.properties

In this file, look for the following line:

nmsas.server.port.web.http=80

The port assigned to nmsas.server.port.web.http is the port to specify in the URL. For details, see the nnm.ports Reference Page.

(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:

1. As a user with administrator privileges (Windows) or root privileges (UNIX), open the following file in any text editor:

   • Windows

     %NnmDataDir%Conf\nnm\props\nms-local.properties

     %NnmDataDir% is the data directory specified during installation.

   • UNIX

     /var/opt/OV/conf/nnm/props/nms-local.properties

2. Modify the existing entries, replacing any conflicting port numbers with available port numbers.

3. Save the file, and then restart the NNMi services:

   ovstop -c
   ovstart -c

   Reference 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.

(a) Solution

1. From the Workspace navigation panel, select the Configuration workspace.

2. From Configuration, open the Seeds view.

3. 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.