CA Client Automation - 14.0

English

Known Issues and Troubleshooting in 14.0.1

The
CA Client Automation
 14.0.1 release contains the following issues and their work arounds:
cla140
The
CA Client Automation
 14.0.1 release contains the following issues and their work arounds:
Known Issues
Triggering of SD Agent from 14.0.1 SHA-2 Only Configured Manager
The SD Agent is getting triggered on Agent, which is not an expected behavior.
  1. 14.0.1 Manager exists and an Agent (older than 14.0.1 version) is connected to a 14.0.1 Manager.
  2. The
    Certificate preference order
     configuration policy is set to the
    SHA256_2048
    option.
  3. The caf is restarted after setting the policy.
  4. Right-clicking on the 14.0 Agent and selecting
    Software Jobs
     and
    Activate Job Check
    ,
    the SD agent is getting triggered on 14.0 Agent.
For the 14.0.1 prior Agent versions, jobs fail to complete because Agents cannot communicate with the Scalability Server.
Interactive Service Jobs Not Working on Windows 2016 & Windows 10 Agents
The Interactive service jobs are not working on Windows 2016 and Windows 10 Agents.
Troubleshooting
Automatic Agent Software Upgrade Not Initiated on HP-UX Systems with
CA Client Automation
 r12.8 Version
Symptom
The automatic upgrade of Agent software is not initiated because of the mismatch in the Agent package names as mentioned.
Package names in 12.8
 : CA DSM Agent + Basic Inventory plugin HP-UX(800) (ENU)
Package names from r12.9 onwards
 : CA DSM Agent + Asset Management plugin HP-UX (ENU)
Solution
Based on the agent plug-ins that are installed on your systems, execute the following commands as appropriate.
 
ccnfcmda -cmd setParameterValue -ps itrm/installed_packages/basichwinv -pn name -v "CA DSM Agent + Basic Inventory plugin HP-UX (ENU)"
 
ccnfcmda -cmd setParameterValue -ps itrm/installed_packages/agent_am -pn name -v "CA DSM Agent + Asset Management plugin HP-UX (ENU)"
 
ccnfcmda -cmd setParameterValue -ps itrm/installed_packages/agent_sd -pn name -v "CA DSM Agent + Software Delivery plugin HP-UX (ENU)"
 
ccnfcmda -cmd setParameterValue -ps itrm/installed_packages/addon_rvi -pn name -v "CA DSM Agent AM RVI plugin HP-UX (ENU)"
Operating System Shown as Unclassified
Symptom
The Operating System is shown as unclassified for recently certified platforms when inventory is collected using NRI. This error occurs only when Manager is upgraded from prior 12.9 versions.
Solution
Navigate to the <DSM Install Directory\Web Console\webapps\wac\jsp\ei\wl\scripts\<launguage> folder. Edit the 1basic.wlscr, 2adv.wlscr, 3register.wlscr files.
Increase the file count by 1 and add the entry for OSConfig.xml. For example: change from Files=16 to Files=17 and add entry File17=OSConfig.xml
CA Client Automation
 Upgrade Using Software Delivery Fails on Agents Configured with Internal-NOS Download Method
Symptom
If the Agent is configured with the Internal-NOS method in the following scenarios, Agent upgrade fails with Software Delivery:
  • Windows Scalability Server and Windows Agent
  • Linux Scalability Server and Linux agent
Solution
  • For Windows Scalability Server and Windows Agent
    Change the configuration policy not to use the mapped drive on Windows. For Windows, set the value of
    Software Library access: Use mapped drive
     configuration policy to True and apply on the Agent. For more information about Software Library access: Use mapped drive, see Software Delivery Agent Policy Group.
  • For Linux Scalability Server and Linux Agent
    Provide executable permission for the installdsm files in the Software Library of the Scalability Server. For example, 
    find $SDROOT/asm/library/ -name installdsm | xargs chmod u+x
CA Client Automation
 Agent Installation Using Infrastructure Deployment Fails
Symptom
The
CA Client Automation
 installation fails on Unix/Linux/Mac systems with the latest ssh server (openSSH 7.2 or later) running throwing an error as
Error: “Unable to establish SSH connection”
.
Solution
Add 3des-cbc to the supported list of Ciphers in the sshd daemon configuration file.
For example, add the following line in the /etc/ssh/sshd_config file.
 
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour
Packages Fail to Stage on Linux Scalability Server
Symptom
An error message as
ERRORCIpcCommon::GetIPCKey: failed to create new semaphore: sem_mtx_SD_ScheduleNewTrig: (28) No space left on device
is logged in the TRC_USD_SDSERVER_0.log.
Solution
Increase the number of semaphore sets(SEMMNI) to 1024 in the Linux Scalability Server. The default value of SEMMNI is set to 128 on few Linux platforms.
For example, following values are set in the semaphore section in the Red Hat ES: 
 
#cat /proc/sys/kernel/sem
 
250 32000 32 128
Execute the following command to change the values and restart the CAF service:
sysctl -w kernel.sem="250 256000 256 1024"
Add or update the following line in the
/etc/sysctl.conf
 file to change the value permanently, and reboot the server.
# echo "kernel.sem = 250 256000 256 1024" >> /etc/sysctl.conf