Procedure for ensuring latest version of lsm is deployed during OS provisioning.

Products

• CA Automation Suite for Clouds
• CA Automation Suite for Data Centers - Configuration Automation
• CA Client Automation - Asset Management
• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Remote Control
• CA Client Automation - Asset Intelligence
• CA Client Automation - Desktop Migration Manager
• CA Client Automation - Patch Manager
• CA Server Automation

Issue/Introduction

Description:

Problem:

A change in lsm behaviour was identified that causes breakage with some packages. When deploying operating systems from a CA ITCM Domain Manager or via CA Spectrum Automation Manager it is possible to auto-install the CA ITCM Agent + SD plugin package. Without following the instructions below the package deployed would contain an older version of lsm which could cause problems when attempting to subsequently deploy other packages.

Environment:

The problem affects target operating systems supported by CA ITCM for these major platforms.

Linux
Solaris
HP-UX
AIX

Solution:

Resolution:

The following fixes provide an updated version of lsm that should be used within the following procedure. The specific file that should be extracted and used is named "ca-sm-installer".

T2DF267 - Linux
T2DF268 - Sol Int
T2DF269 - Sol SPARC
T2DF270 - HP
T2DF271 - AIX

1. On the DSM Manager machine create a folder e.g. named "DSM_Patched_LSM".
   
   
2. Copy the dsmpush.dms script from the second CA ITCM DVD image (non-windows) in to the folder.
   
   
3. Copy the platformProductFiles_xxx folders from the DVD image to the same folder. Where platform is one of AIX, Linux, HPUX or Solaris
   
   
4. Within in each copied platform specific folder navigate to the "sd_agent" folder and overwrite the file ca-sm-installer with the new version from the CA supplied fixes. Note that there is a separate fix for each platform.
   
   
5. Open the file named "dmdeploy.dat" with a text editor and modify the following to properties "ItemVersion" and "VersionDisplay". In both cases increment the last number in the version string e.g. 12.5.0.2307 would become 12.5.0.2308. Save the file.
   
   
6. Now navigate down into the "reginfo" folder.
   
   
7. Open the file named "rsw.dat" and modify the following properties "ItemVersion", "ProductVerson", "DmVersion". In all cases increment the last number in the version string e.g. 12.5.0.2307 would become 12.5.0.2308. Save the file.
   
   
8. Open the file named "itemproc.dat" and modify all instances of the property "ItemVersion". In all cases increment the last number in the version string e.g. 12.5.0.2307 would become 12.5.0.2308. Save the file.
   
   
9. Start a command prompt and change directory to the previously created folder e.g. "DSM_Patched_LSM".
   
   
10. Execute the following command
    
    "dmscript dsmpush copy {-plat} -REGSD -REGDM -sd"
    
    Where -plat is any combination of "-hp -sun -ibm -linux"

This creates a new version of the SD agent package used by OSIM within the Software Package Library and updates the SD agent package used within in the DMDeploy package library. Both of these packages have a new version number and an updated version of lsm.

OSIM will automatically detect this package update and will create and deliver an updated version of the agent to the Scalability Server (Boot Server). This will ensure that the updated SD Agent package is used when automatically deploying the agent along with an OS deployment.

Cause:

A design change in PIF 4.5 affected the way in which environments for the PREPIF and PRESTART-phase callout scripts were being setup.

Environment

Release: UASIT.99000-12.5-Asset Intelligence
Component: