Verifying the TrueSight Server Automation installation

This topic provides information and instructions for verifying that TrueSight Server Automation  (formerly called BMC Server Automation) installed correctly. To verify the TrueSight Server Automation installation, you check the following components:

• • Verifying the installation of the TrueSight Server Automation Application Server and Console
  • Verifying the TrueSight Server Automation – File Server installation
  • Verifying the installation of the TrueSight Server Automation – Application Server (MAS)
  • Verifying the installation of the PXE and TFTP servers

When verifying the components, you check the corresponding installation logs, services and processes, and configuration settings.

Verifying the installation of the TrueSight Server Automation Application Server and Console

To verify the TrueSight Server Automation Application Server and Console installation, perform the following tasks:

To check the installation logs for errors

1. To determine whether any errors were recorded, check both the client and server installation logs.
    You can check the installation logs through the installer after the product installation is complete. Alternatively, you can access the installation logs through the corresponding directory path.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
   
   
   

2. If a SEVERE or WARNING error message was reported, consult the Known and corrected issues and Troubleshooting the installation, migration, or upgrade sections. You may also contact BMC Customer Support for additional help.

To check services or processes

• (Windows) Open the Services (Local) window, and verify that the following services are running:
  • TrueSight Server Automation Application Server
  • TrueSight Server Automation Process Spawner
    
    If they are not running, start them from the Services (Local) window.
• (Linux) Run the ps -ef | grep -i bladmin command to get a full list of processes and to check the status of the blappserv and the blprocserv processes. If they are not running, start the respective process by executing the corresponding command:
  • /etc/init.d/blappserv start
  • /etc/init.d/blprocserv start

To check parameter values and application services

1. On the system where the TrueSight Application Server is installed, invoke Network Shell (NSH) and run the blasadmin command to verify specified application services and parameters and their values.
   • (Windows) Open a command window and enter nsh to launch the script.
      A Command Prompt window is displayed, showing the host name followed by the hash sign:
     hostName%
   • (Linux) Run nsh from the command line: /bin/nsh.
      The host name followed by the hash sign is displayed.

2. Enter the blasadmin command with the -s switch and the name of the job deployment that you are checking. For example:
   hostName%blasadmin -s <jobServer>
   hostName%blasadmin -s job_deployment_vw-sj-dv004.labs.bmc.com 

   Success

   To find the name of the job deployment, log into the TrueSight Server Automation Console and select Configuration > Infrastructure Management > Application Servers. When you click Application Servers, you see a list of current configuration server and job server deployments.

3. Enter show appserver all to display the job server settings. 
   Verify that the following application services are enabled and that the following parameters have the assigned values:

   Application service/Parameter	Value
   DisableIpv6SupportForSysInfo	true
   EnableAtriumIntegration	true
   MaxJobs	75
   MaxWorkItemThreads	100
   MaxHeapSize	2048

   For additional information about Application Server parameter settings, see Sizing Application Servers in the TrueSight Server Automation online technical documentation.

To check the Application Server's components and connectivity

In the TrueSight Server Automation Console, verify that specific packages, catalogs, and folders have been created and that the TrueSight Application Server is connected with BMC Atrium CMDB. Expand the following folders and make sure that the required subfolder and/or packages are created:

1. To open the TrueSight Server Automation Console, select Start > All Programs > BMC Software > TrueSight Server Automation Suite > Server Automation Console. 
2. Log on as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the TrueSight Application Server, and then click Connect. 
3. If you see a security alert, click Yes to proceed. 
4. Expand BladeLogic > Component Templates and verify that the CSM_Application_Packages package folder is created:
   
5. Expand BladeLogic > Depot and verify that the following folders are created:
   
   • CSM_OS_Packages
   • CSM_Publish_Product_Catalog
   • CSM_Scripts
6. Expand BladeLogic > Depot > CSM_Scripts and verify that the following .nsh scripts are created:
   
   • configure_nic.nsh
   • create_user_linux.nsh
   • create_user_windows.nsh
   • CSM_Delayed_Reboot.nsh
   • open_port_linux.nsh
   • open_port_windows.nsh
   • set_user_password_linux.nsh
   • set_user_password_windows.nsh
7. Expand BladeLogic > Jobs and verify that the CSM_Applications folder is created:
8. Expand BladeLogic > Jobs > CSM_Publish_Product_Catalog and verify that the Publish_Product_Catalog_job job is created:
9. Select Configuration > Infrastructure Management > Application Servers and verify that the following subfolders are created:
   • config_deployment_hostName
   • job_deployment_hostName
     
10. Select Configuration > Infrastructure Management > Database Configuration Info and verify the parameters of the TrueSight Server Automation database:
11. Select Configuration > Atrium Integration > Configuration and verify that the values for the Host Name/IP Address, CMDB Port, and CMDB User parameters are correct. To verify that the servers are communicating, click Test Connection.
     

To verify that the config and job deployment servers are created correctly

1. Access the TrueSight Application Server by logging on to the TrueSight Server Automation Console as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the TrueSight Application Server.
2. In the TrueSight Server Automation Console, select Configuration > Infrastructure Management > Application Servers.

3. Verify that the config and job deployment servers are created appropriately based on the following deployment types supported in version 4.6: 

   Deployment type	Config server	Job deployment server
   Small	1	2
   Medium	1	2

   
   

   Warning

   Note

   The TrueSight Server Automation Java heap size check fails in the Install Planner if the TrueSight Application Server is not configured with the appropriate job and config servers. For details about tuning the TrueSight Server Automation components, see TrueSight Server Automation server tuning.

4. Select a job deployment and ensure that Maximum concurrent jobs is set to 75 and Available work item threads is set to 100.

For additional information about Application Server parameter settings, see Sizing Application Servers in the TrueSight Server Automation online technical documentation.

Verifying the TrueSight Server Automation – File Server installation

After the installer reports that the installation is successful, perform the following steps:

1. On the system on which you installed the file server, verify that a folder named storage has been created in the following path:
   
   • (Windows) C:\Program Files\BMC Software\BladeLogic\storage
   • (Linux) /opt/bmc/bladelogic/storage
     The storage folder is empty when you first install the File Server. Later, when you install TrueSight Application Server and Console, you are prompted for the location of the File Server. The installation routine populates the storage folder with subfolders and files. The standard subfolders are blassetclass, scripts, and tmp.
2. Log on to the target computer.
3. Go to the directory where the file server was created (for example, on Linux, /opt/bmc/bladelogic/storage).
4. Perform the following actions:
   1. Create a subdirectory under the storage folder.
   2. Create a file in that subdirectory.
       You should be able to create a subdirectory and a file without getting an exception.
5. Navigate to the scripts folder and verify that following scripts are created:
   • create_user_linux.nsh
   • create_user_windows.nsh
   • open_port_linux.nsh
   • open_port_windows.nsh
   • set_user_password_linux.nsh
   • set_user_password_windows.nsh
   • CSM_delayed_reboot.nsh
   • DB_and_FS_cleanup.nsh
   • configure_nic.nsh

Verifying the installation of the TrueSight Server Automation – Application Server (MAS)

To verify the installation of the TrueSight Server Automation - Application Server (Multiple Application Server, or MAS) implementation, perform the following steps:

1. Verify that the Application Server is running:
   • (Windows) Open the Services (Local) window, and verify that the BladeLogic Application Server service is running. If it is not running, start the service from the Services (Local) window.
   • (Linux) Run the ps -ef| grep blappserv command to to check the status of the blappserv process. If it is not running, start the process by executing the following command:
     /etc/init.d/blappserv start.
2. Access the host system where the TrueSight primary server resides.
3. Log on to the client Automation Console.
4. Select Configuration > Infrastructure Management to display the Infrastructure Management dialog box.
5. Verify that the secondary server that you installed has been added to the list by checking the Application Servers and Application Server Launcher folders.
6. To verify that the keystore values are same for the TrueSight Server Automation – Application Server and Console and TrueSight Server Automation – MAS products, launch the NSH prompt and run the following command:
   md5 checksum of keystore

For additional information about the TrueSight Server Automation Advanced Repeater, see Configuring a multiple Application Server environment in the TrueSight Server Automation online technical documentation.

Verifying the installation of the PXE and TFTP servers

To verify the installation of the Preboot Execution Environment (PXE) and Trivial File Transfer Protocol (TFTP) servers, perform the following tasks.

To check the installation log

1. To determine whether any SEVERE exception errors were recorded, check the PXE installation log.
    You can check the installation log file, BladeLogic_Install, through the Installer after the product installation is complete. Alternatively, you can access the installation log through the corresponding directory path.

   Installer	Click View Log to access the corresponding log file.
   Directory path	The BladeLogic_Install log file resides under the Windows\Temp directory on Windows or under the /tmp directory on Linux.

2. If a SEVERE error exists, see Troubleshooting for more information.

To check services or processes

• (Windows) Open the Services (Local) window, and verify that the following services are running:
  • TrueSight Server Automation PXE Server
  • TrueSight Server Automation TFTP Server
• (Linux) Run the ps -efcommand to get a full list of processes and to check the status of the blpxe and bltftp processes. If either process is not running, start the process by executing the corresponding command:
  • /etc/init.d/blpxe start
  • /etc/init.d/bltftp start

To check the services running on the Application Server

1. Access the TrueSight Application Server by logging on to the TrueSight Server Automation Console as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the TrueSight Application Server.
2. In the TrueSight Server Automation Console, select Configuration > Infrastructure Management, and verify that the PXE server or servers are listed and that each server has the following services:
   • AppServerService
   • BIProcessService
   • DatabaseService
   • FileManagerService
   • PortProviderService
   • SupportService