Run the farm -Lt farm_ID command to extract messages related to the specified farm from the log files.
If the farm has been assigned to an SP (as shown by the farm –l farm_ID command), look at the /var/adm/messages file and the /var/adm/tspr.debug file on the owning SP for any error messages for the farm.
Check the /var/adm/messages file and the /var/adm/tspr.debug on the SP running the Master Segment Manager for any critical error messages for the farm.
The following example shows how a message appears in the log:
Oct 30 00:16:47 sp4 java[506]: [ID 289794 user.info] TSPR [sev=okay] [apps=770034] TCPEventHandler:dispatch...
See Chapter 6, Error Messages in N1 Provisioning Server 3.1, Blades Edition, System Administration Guide.
Use the following tools to help pinpoint the problem:
Monitor the farm activation process through the Control Center Farm Requests dialog of the Administration screen. During the activation process, a message reports when a device is added successfully to the farm. See if you can identify a device that failed.
Use the terminal server, or the serial port of the device if the terminal server is not available, as a console to connect to a specific device and obtain diagnostic information. Until the farm device is activated, the only way to connect to the device is through the console connection.