Verifying the BMC Server Automation installation

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

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

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

To verify the BMC 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.

   Installer	Click View Log to access the corresponding log file.
   Directory path	The installation log files reside under the Windows\Temp directory on Microsoft Windows or under the /tmp directory on Linux. The BMC Server Automation Console installation log file (the client installation log) is named serverAutomationConsole_install_log.txt. The BMC Server Automation Application Server log file (the server installation log) is named BladeLogic_Install.

   
   The following example shows a SEVERE client installation exception:

   SEVERE,com.bmc.install.product.clientinstaller.AppServerRunningDetectionValidationTask,
   LOG EVENT {Description=[APPSERVER_AGENT_MUST_BE_STOPPED],Detail=[Application Server and RSCD Agent is running. Please stop the Application Server and RSCD Agent before attempting to install.]}

   If no error messages were reported, the installation was successful and you can skip the rest of the verification procedures for BMC Server Automation Application Server and Console.

2. For all error, (including SEVERE) messages, perform the following procedures:
   • Verify the installation (perform the rest of the procedures in this section).
   • Verify the BMC Server Automation – File Server installation
   • Verify the BMC Server Automation – Advanced Repeater server installation
   • Verify the installation of the BMC Server Automation – Application Server (MAS)
   • Verify the installation of the PXE and TFTP servers
3. If a SEVERE error message was reported, additionally perform the steps documented in the Resolving product installation issues on target hosts topic.

To check services or processes

• (Windows) Open the Services (Local) window, and verify that the following services are running:
  • BladeLogic Application Server
  • BladeLogic Process Spawner
    
    If they are not running, start them from the Services (Local) window.
• (Linux) Run the ps -ef | grep -i bladmincommand 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 BMC Application Server is installed, invoke Network Shell (NSH) and run the blasadmincommand 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

   To find the name of the job deployment, log into the BMC 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. 

4. Verify that the following application services are enabled and that the following parameters have the assigned values:

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

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

To check the Application Server's components and connectivity

Access the BMC Application Server by logging on to the BMC Server Automation Console as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the BMC Application Server. In the BMC Server Automation Console, verify that specific packages, catalogs, and folders have been created and that the BMC 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. Expand BladeLogic > Component Templates and verify that the CSM_Application_Packages package folder is created:
   
   
2. Expand BladeLogic > Depot and verify that the following folders are created:
   
   
   • CSM_OS_Packages
   • CSM_Publish_Product_Catalog
   • CSM_Scripts
3. 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
4. Expand BladeLogic > Jobs and verify that the CSM_Applications folder is created:
   
5. Expand BladeLogic > Jobs > CSM_Publish_Product_Catalog and verify that the Publish_Product_Catalog_job job is created:
   
6. Expand Configuration > Infrastructure Management > Application Servers and verify that the following subfolders are created:
   
   
   • config_deployment_hostName
   • job_deployment_hostName
7. Expand Configuration > Infrastructure Management > Database Configuration Info and verify the parameters of the BMC Server Automation database:
   
8. Expand 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 BMC Application Server by logging on to the BMC Server Automation Console as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the BMC Application Server.
2. In the BMC Server Automation Console, select Configuration > Infrastructure Management > Application Servers.

3. Verify that the config and job deployment servers are created appropriately based on your deployment type:

   Deployment type	Config server	Job deployment server
   Proof of concept	1	1
   Small	1	2
   Medium	1	2
   Large	1	3

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 BMC Server Automation online technical documentation.

Verifying the BMC 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 BMC 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 BMC Server Automation – Advanced Repeater server installation

To verify the BMC Server Automation Advanced Repeater installation, perform the following tasks.

To check the installation log for errors

1. To determine whether any errors were recorded, check the Advanced Repeater installation log.
   You can check the bcac_install_log.txt installation log file through the installer afterthe product installation is complete. Alternatively, you can access the installation log file through the corresponding directory path.

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

2. If a SEVERE exception error exists, continue with the following checks. If no SEVERE exceptions are recorded, you are done with the verification.

To check services or processes

• (Windows) Open the Services (Local) window, and verify that the following service is running: BMC Advanced Repeater.
• (Linux) Run the ps -ef | grep AdvancedRepeater command to check the status of the AdvancedRepeater process. If it is not running, start the process by executing the following command:
  /etc/init.d/AdvancedRepeater start

For additional information about the BMC Server Automation Advanced Repeater, see Configuring advanced file servers and Advanced Repeater servers in the BMC Server Automation online technical documentation.

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

To verify the installation of the BMC 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 BMC 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 BMC Server Automation – Application Server and Console and BMC Server Automation – MAS products, launch the NSH prompt and run the following command:
   md5 checksum of keystore

For additional information about the BMC Server Automation Advanced Repeater, see Configuring a multiple Application Server environment in the BMC 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 afterthe 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 the Troubleshooting section for more information.

To check services or processes

• (Windows)Open the Services (Local) window, and verify that the following services are running:
  • BladeLogic PXE Server
  • BladeLogic 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 BMC Application Server by logging on to the BMC Server Automation Console as the BLAdmin user, with the BLAdmin password that you specified when installing and configuring the BMC Application Server.
2. In the BMC 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