Problem: Cannot start NFM-P client, or error message during client startup

Prerequisites

Before you proceed, ensure that the following conditions are present:

Steps
 

If the NFM-P client is installed on RHEL and you receive a “Cannot execute” message when you try to run the client, the client executable file permission may have been reset by an event such as an auto-client update failure. You must ensure that the correct file permissions are assigned.

  1. Log in as root, or as the user that installed the client, on the client station.

  2. Open a console window.

  3. Enter the following:

    chmod +x path/nms/bin/nmsclient.bash

    where path is the NFM-P client installation location, typically /opt/nsp/client


Review the login messages that are displayed when a client GUI attempts to connect to a server. Messages that state things like the server is starting or the server is not running indicate the type of problem.


Ensure that the user name and password are correct.


To check that the NFM-P server is up and to view additional server configuration information, perform the following steps.

  1. Log on to the NFM-P server station as the nsp user.

  2. Open a console window.

  3. Navigate to the /opt/nsp/nfmp/server/nms/bin directory.

  4. Enter the following:

    ./nmsserver.bash appserver_status ↵

    Server status and configuration information are displayed.

  5. To check additional server status conditions, perform Problem: Cannot start an NFM-P server, or unsure of NFM-P server status.


Check the client GUI login error message.

When a firewall is running locally on the client station, a login error message may appear indicating that the server is not available. Ensure that a local firewall is not preventing a connection to the server, and that the NFM-P server IP address is in the client host-lookup file.

End of steps