CA Client Automation

Hi all,

Our business is new to the CA product range and I've been tasked with the setup of the IT client manager  v12.9.0338.

Server (vm running windows 2008 R2 SP1) has been setup and (stand alone no other CA servers in this single domain setup) is installed.

I have successfully deployed several CA DSM Agents to a test laptop but I cannot see the test laptop in the "All Computers" container in the DSM explorer.

I have tried manually creating the test laptop in the "All Computers" container but when I do that the "AM Status, SD Status show up as "preregistered", I cant get any inventory info.... in short I'm stuck:(

After late nights and early mornings on this I'm beginning to go a little nuts ....... any advice, or documentation on how to get clients talking with the server would be greatly appreciated.

Hi,

please check the following:

1. caf status (on the client to see if all process are up, you should see a minimum of 8 - 10 processes) --> on the client

2. caf setserveraddress (as output you should see the IP or FQDN of your Scalability / Domain Manager) --> on the client

If the above mentioned statement looks good, then check if the connection from client to server could be established.

1. camping from the client to your Domain Manager. --> Check if the Firewall is oopen on port 4728

camping %DomainManager%

for example:

camping: Trying 10.11.15.219 ...

1:  reply from 10.11.15.219, rtt 161ms
2:  reply from 10.11.15.219, rtt 2ms
3:  reply from 10.11.15.219, rtt 2ms
4:  reply from 10.11.15.219, rtt 2ms

Kind regards

Gregor

Hi Gregor.wolf77, thanks for your reply.

I ran the first 2 cmd's and got the following results;

caf status:

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Querying caf for status information...

Showing running DSM services...

[1]  Asset Management software usage agent for workstation (amswmagtw)

[2]  Certificate exchange plugin (cfcertex)

[3]  Configuration agent (ccnfagent)

[4]  Configuration and State Management agent (ccsmagt)

[5]  DSM Service Locator plugin (cfsvclocator)

[6]  Event notification plugin (cfnotify)

[7]  External Process Manager (cfprocessmanager)

[8]  File transfer server (cfftplugin)

[9]  Notification Server (cfnotsrvd)

[10] Registration plugin (cfregister)

[11] Remote Control host agent (rchost)

[12] Session messaging server (smserver)

All looks good

However when running the caf setserveraddress I got the below; (server name taken out by me) - no FQDN was returned just the server name

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Caf currently registers with the scalability server at ***.

Connecting toXXX to ask if a server is present...

Failed to send a message to caf: . Possible reasons for this are:

the host may not be contactable, caf may not be running or caf

is too busy to reply.

The command failed.

HI,

this is exactly the problem, client is not connected to a scalability server (SS), just run the following command and then you should see the client within your DSM GUI.

caf setserveraddress %IP or FQDN of your SS, or your DM if no SS is available%

after the SS is set with above mentioned command, just run the re register of the client with following statement

caf register

You should consider building up a dedicated SS for connecting all clients and then the SS is transferring all assets to the DM.

Kind regards

Gregor

Caf appears to be configured correctly as caf setserveraddress returned the servername

now check if camping will work

Hi EUS

Welcome to the Community!

I agree with Gregors update. We need to verify communication between your agent and the server

If camping works in both directions then the underlying communication protocol is working. next check if the caf components can talk with

caf ping <target>

check this in both directions to see if caf can communicate

the ports required for communication are

4104 UDP

4105 TCP

7163 TCP

By default all coms will use the UDP protocol unles you have deliberatly configured cam to use TCP.

If camping fails then first confirm that a standard PING works then check to see if there is an fragment size restriction in your network by following TEC511460

regards

Rich

Hi EUS,

use the comment from Rich, I did not saw that server was taken out.

Kind regards

Gregor

hi guys, First thanks for all the prompt answers – I’ve moved now from bordering despair to hopeful…

I’ve done the following:

caf ping from client to server

982 ms: CA DSM r12 Common Application Framework 12.9.0.338

   62 ms: CA DSM r12 Common Application Framework 12.9.0.338

   15 ms: CA DSM r12 Common Application Framework 12.9.0.338

   46 ms: CA DSM r12 Common Application Framework 12.9.0.338

caf ping from server to client

2255 ms: CA DSM r12 Common Application Framework 12.9.0.338

   34 ms: CA DSM r12 Common Application Framework 12.9.0.338

   15 ms: CA DSM r12 Common Application Framework 12.9.0.338

   43 ms: CA DSM r12 Common Application Framework 12.9.0.338

result outputs appear good so spurred on with hope I moved on ☺

caf setserveraddress SERVERIP

C:\Users\125004623>caf setserveraddress SERVERIPADDRESS

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Caf currently registers with the scalability server at SERVERNAME.

Connecting to SERVERIPADDRESS to ask if a server is present...

You must be an administrator to perform this command.

Then I ran the following cmd’s

C:\Users\125004623>caf register

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Asking caf to re-register...

Command completed successfully.

C:\Users\125004623>caf register

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Asking caf to re-register...

Command completed successfully.

But I don’t see the client in the “All Computers” container… have I missed something

Hi EUS

Now you need to look at the Engine Collect job. Is it running?

regards

Rich

I set this up last night by taking the following steps….

Under;

Engines – Collect Tasks – (right click in screen) select New.

Task type = Collect clicked next

Task name = test laptop name – clicked next – selected the items below

Scheduling = Always run job. All other tabs in the Scheduling options dialog box left at default.

In Engines – Collect Tasks - test laptop name I see “SystemEngine” status Enabled. Double clicking on “SystemEngine” I see status Waiting 0 successful runs…..

Tasks screen shot did not show on above mail... listed below.

Asset registration

Audit

Backup

Content Distribution

Hardware Inventory

Software Discovery

Software Usage

Status

Hi EUS

OK so the reason you do not see the agent is that the collect job has not yet run

Can you check Engines - All Engines - SystemEngine

Is the engine busy running another task?

Rich

Hi Richard Little – yes there is another task running, the task that is running is returning all the results from the local server.

The only device visible in the all computers container is the ITAM server…..

Should I stop this engine from running – is this preventing the test machine from showing up in the computers container ?

Hi EUS

Yes the test machine will not show up until the collect job has run. You can either unlink the other tasks or create another engine instance and attach the collect task to this new engine.

regards

Rich

Hi EUS

Have you managed to register your test machine.

regards

Rich

Hi Richard_Little,

I have not.

I have recreated the engine task (collection job) it has now had 5264 successful runs but I still don’t see the test laptop in the all computers container.

In the DSM Explorer-Servername-Domain – Control Panel – Engines – All Engines – System Engine I see the below.

But still no laptop to be found in the computers container ….. any suggestions are welcome.

Thanks

Hi EUS

Have you had any luck on this?

regards

Rich

Hi

what you need to do is run on the agent machine these commands and then check the logs for the cause of the registration failing

caf setserveraddress <scalability server>

caf register all

check the file named TRC_CF_REGISTER_0.log located in the DSM\logs directory on the agent machine.

you can look to see if you see messages like this

100715-12:55:45.4796428L|001752|000016dc|cfRegister|cfRegister|000000|NOTIFY | ITRMAgent::registerUnitFullAgent: Unit . registered!

or you may see errors which you can search our website for.

Also look at the TRC_CSERVER_#.log and TRC_CF_REGISTER_#.log on the Domain Manager for errors related to the agent node (search by Ip address or hostname)

You should also verify if you have duplicate hostuuid's for these objects you can check by running this query in SQL Management Studio

use mdb

SELECT * FROM ca_discovered_hardware WHERE host_name IN (SELECT host_name FROM dbo.ca_discovered_hardware AS ca_discovered_hardware_1 GROUP BY domain_uuid  , host_name HAVING (COUNT(host_name) > 1))

if any returns are present this indicates a duplicate hostuuid is an issue and should be deleted via DSM Explorer. Then you should delete the agent registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\HostUUID 

clear the value for hostuuid and then run the above commands

caf setserveraddress <scalability server>

caf register all

check the dsm explorer

One other item I would check is if you are having some sort of certificate issue in 12.5 not sure if you upgraded from this version or not but we had a duplicate certificate issue that prevents communication.

see technical documents

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec557259.aspx

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec567733.aspx?intcmp=searchresult…

Check the %CAI_MSQ%\logs directory and look in the logs that contain DG in them and see if you are getting reverse proxy messages

like what is detailed in document

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec539203.aspx

If the above doesn't help I would advise you to open a CA Support issue and we can assist you further

Thanks and hope this is helpful

Joe

one other item regarding the reverse proxy messages is check both the scalability server and Domain Manager and if you have any entries under the ROUTING heading in the cam.cfg dont make the changes for disable_proxies = yes or it nullifies the entries.

Thanks

Joe

guys – thanks a bundle….. I ran the first 2 cmds (this time I used the server IP instead of the server name and it is visible in the computers container..

again guys thank you very much.