An UP Message Not Received From One or More Servers

You can confirm an UP message problem on the control plane server by checking whether the following conditions exist:

• In the /var/adm/tspr.debug file, a message is listed similar to the following:

  "Still waiting for 1 device(s) in 2879974 ms"

• The farm activation shows ERROR 50, as shown in the following example:

  FARM_ID FARM_NAME CUSTOMER STATE ISTATE ERROR 123 Farm_Name Customer NEW DISPATCHED 50

The following figure shows the steps needed to diagnose and resolve this problem.

Figure 7–2 Resolving Monitoring Problems

The preceding illustration shows the following troubleshooting sequence:

1. Check for a network, DNS, or DHCP problem. See Network, DNS, or DHCP Problems for details on how to do this.

2. Check that the monitoring processes are running on the control plane server. See Monitoring Processes Are Not Running on the Control Plane for details. Follow the instructions in this section to restart the processes.

3. Check that the agent processes are running on the resource pool server. See Agent Processes Are Not Running on a Resource Pool Server for details. If the agent processes are not running, follow the instructions in this section to restart them.