OSIM: Boot server is not updating job status
Article ID: 106829
Updated On:
Products
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
Issue/Introduction
OSIM jobs are stuck in the pending/installing status, and are never being moved to "current", even after the OS image is successfully deployed, and the ITCM agent has been installed and registered with the domain manager.
Environment
Client Automation (ITCM) -- r14 SP2, only.
Resolution
Open a support case, requesting the following patches to be applied to the Domain Manager and remote Scalability/Boot Servers:
- T55L074 (CCNFAGENTAPI HANG)
- T55L084 (CAM RESPONDS AFTER PMUX KILLED)
- T533328 (ccsmagtd using high CPU)
After applying this series of patches, a number of scenarios where communication between Scalability Server and Domain Manager will be addressed, such that updating the OSIM job status should be resolved.
- T55L074 (CCNFAGENTAPI HANG)
- T55L084 (CAM RESPONDS AFTER PMUX KILLED)
- T533328 (ccsmagtd using high CPU)
After applying this series of patches, a number of scenarios where communication between Scalability Server and Domain Manager will be addressed, such that updating the OSIM job status should be resolved.
Feedback
Powered by
