N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide

ProcedureHow To Activate a Farm By Using the Farm Activation Command

Steps
  1. Type the command farm -a farm_ID to activate a farm on the SP.


    Note –

    To add a high priority code to this request or to issue a request to a farm in ERROR state, use the -f option to create a high priority request. Refer to Chapter 6, Troubleshooting for more information on the ERROR state.


  2. For software that runs on the Solaris Operating System, check the file /var/adm/messages for error messages. If you have turned on the debugging option in the /etc/opt/terraspring/tspr.properties file, check for any error messages in the file /var/adm/tspr.debug. You can view messages by using the command tail -f /var/adm/tspr.debug and by monitoring the error column in the output from the farm -l command. Also monitor the request queue for the farm using the command request -lf farm_ID to check the status of the queue.


    Note –

    The tspr.debug will have messages interleaved if actions on multiple farms are issued the same time.


  3. When the farm status changes to ACTIVE, display the farm resources using the command lr -lv farm_ID.

    The farm configuration includes the server IP address and the subnet configuration for the farm. This information is available as soon as the allocation process is completed. You do not have to wait until the farm reaches the ACTIVE state.


    Note –

    The Farm Manager keeps a log file of the farm activation process and any updates that are associated with the farm. The messages are logged in the file /var/adm/messages. Type the command tail -f /var/adm/tspr.debug on the farm's owner SP to view the debug log file if you would like to follow farm activities in real time.