CA Client Automation

 View Only
  • 1.  CA ITCM Agent doesn't report to Server.

    Posted Sep 14, 2018 03:58 PM
      |   view attached

    Hello dear community, I'm having some issues, I install CA ITCM SP2 if I check the caf version command in that machine it has the update version, but in DSM Explorer and MDB it doesn't update the information.

    Somebody knows how to force the write in database?

    In picture some machines appears with Telnet error and that machines has the Updated Agent.


    Please help me!!!

  • 2.  Re: CA ITCM Agent doesn't report to Server.

    Broadcom Employee
    Posted Sep 14, 2018 04:29 PM

  • 3.  Re: CA ITCM Agent doesn't report to Server.
    Best Answer

    Posted Sep 18, 2018 01:56 PM

    If I understand your scenario properly, you are using the Deployment Wizard to upgrade your existing agents.


    Firstly, let me say that Software Delivery is the preferred method for upgrading agents.  Unless this is an Asset Management-only installation of ITCM, you should leverage Software Delivery to upgrade your existing agents.


    The Deployment Wizard is better suited for new agent installs.  Although it is capable of upgrading agents.  Just Software Delivery is much smoother and uses normal ITCM ports, than the requirements and moving parts associated with the Deployment Wizard.


    Secondly, once an agent is upgraded, it should register automatically (caf register).  The agent will register with its scalability server.  From there, the Engine running the Collect Task associated with that Scalability Server will pickup the registration message, and update the agent details in the database.


    The agent will register automatically, once per day.  It will also register anytime the CAF service starts up, a user logs in, the system reboots, or if any network address changes.  So registration is both scheduled and event based.  You can also manually trigger a registration with "caf register".


    Since upgrading the agents, what does a "caf setserveraddress" return?  Is it the scalability server you expect?  And if so, is the collect task for that SS linked to an engine in DSM Explorer?