Diagnosing Common Monitoring Symptoms (N1 Provisioning Server 3.1, Blades Edition, System Administration Guide)

N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Diagnosing Common Monitoring Symptoms

A number of symptoms are common to a number of problems. This section describes how to diagnose the following symptoms.

Network, DNS, or DHCP Problems

Perform the checks in the following table for network, DNS, or DHCP problems:

Table 7–4 Checking for Errors


Error Check	Error Confirmation
Verify that all the resource pool servers can receive `ping`signals by running the following command on the control plane server: `/opt/terraspring/sbin/mls -lf farm-ID`. Note – This command lists all the servers in the farm that can receive `ping` signals.	Any of the servers are listed as `ADDED`
Verify that all the resource pool servers are reachable by performing a `telnet` to each of the servers.	Any of the servers are not reachable with `telnet`

Note –

Sometimes a server can receive ping signals but is not reachable with telnet when in a single-user mode. To resolve this problem, connect to the console port and boot into multiuser mode.

Monitoring Processes Are Not Running on the Control Plane

After you determine a diagnosis for a monitoring process run the command:

/usr/ucb/ps -auxww | grep MM

If the monitoring process is running, you will see an output similar to this example:

USER	 PID %CPU %MEM SZ  RSS TT   S START  TIME  COMMAND
root 14540 0.2	1.14 485 620 608? S Mar 05	 18:32 /bin/../java/bin/..
/bin/sparc/native_threads/java -Dsun.net.inetaddr.ttl=0 com.
terraspring.mon.MM 
root 9529  0.1	0.1	  976 672 pts/2 S 11:49:40 0:00 grep MM

If the monitoring process is not running, you will see an output similar to this example:

USER PID %CPU %MEM  SZ  RSS TT     S  START TIME     COMMAND
root 9565 0.1  0.1  976 672 pts/2  S  11:50:28  0:00 grep MM

See Restart the Monitoring Processes on the Control Plane Server for details on how to restart the process.

Agent Processes Are Not Running on a Resource Pool Server

Agent processes might not be running on a resource pool server. You can verify this condition by one of two methods:

On the control plane server run the following command:
/opt/terraspring/sbin/mls -a IP address of host
To be able to use this command, you must know the IP address of the server.

On the server on which the agent you want to verify is running, run the following command:

/usr/ucb/ps -auxww | grep tspragt

If the agent processes are running, you will see output similar to the following example:

root 7652  0.1  0.1  976  656 pts/1 S 11:37:30  0:00 grep tspragt

root 321  0.1  0.73167213816 ? S 16:26:37  0:10 /usr/bin/../java/bin/..
/bin/sparc/native_threads/java -Dsun.net.inetaddr.ttl=0 
com.terraspring.mon.client.tspragt start 10.42.14.2

If the agent processes are not running, you will see output similar to the following example:

root      7709  0.1  0.1  976  656 pts/1    S 11:39:54  0:00 grep tspragt

See Restart the Agent Processes on a Resource Pool Server for details on how to restart the process.

Control Plane Server-to-Control Center Messages Not Working

For a number of reasons messages between the control plane server and Control Center might not work. The most common reasons include:

The mapping between the gw-mon-vip to the IP address of the Control Center server software is not set in the /etc/hosts file on the control plane server. Verify that a suitable entry is present to check this condition.

For example:
10.5.131.19 gw-mon-vip
The listener on the Control Center server software is not running. You can verify this condition by running finger test@gw-mon-vip on the control plane server. The expected sample output is similar to the following examples:
[gw-mon-vip]
or
[hostname]