SS stopped responing to DM

[Remy Dessureault]

Hi

 

in our new CA14 environment, we have seven SS on our environment 

(SS-P1, SS-p2...) and a domain manager (DM-P1)

 

Every server have been up and running since May 2018.

 

Last week SS-P6 stopped responding, we tryed a few thing to no avail. We move the computer from P6 to P7,  uninstalled CA from the server and reinstall it.  Bingo it worked.

 

Today P7 did the same thing.  We've tryed a few thing to no avail, since it worked for P6, we switch back the copmuter from P7 to P6, uninstall CA on the P7 and reinstall it.  

 

There is no error in event viewer, Agent said it register to SS-P1, but SS doesn't work...

 

If we do 

 

Ping DM-P1 from SS-P7  there is no error

CAF Ping and camping work for all SS from SS-P7

but

CAF Ping or camping doesn't answer on DM-P1 from SS-p7

and

CAF Ping or Camping doesn'T answer on SS-P7 from DM-P1

 

 

any idea what we can do?  And why the SS stopped working?

 

 

 

Rémy Dessureault

[lecri01]

See if camping works from dm to dm and from ss to ss.  That will tell you if cam/caf is not responding on one of the machines.

 

If they both work then start looking to the network for problems such as firewalls or network being too busy.  If one of the machines cannot camping itself then do a camstat –a on that machine and look at the size of the cam queue

 

Richard Lechner

Principal Engineering Services Architect

 

CA Technologies

Mobile: [phone] | [e-mail]

 

<mailto:[e-mail]>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>

[Remy Dessureault]

Hi 

I'm able to camping SS to SS or DM to DM, caf Ping SS to SS and DM to DM

 

This morning I was able to reinstall, it worked just long enough for the SS to register then it stopped working again...

 

There's no entry in the event viewer

 

Remy

[lecri01]

It sounds like a local firewall or anti intrusion software on the SS.  I would check that.  If camping works locally then try camping from an agent to the ss does it work.

 

Also do a caf status on the ss are all services running.  Do a camstat on the ss is it running?

 

Richard Lechner

Principal Engineering Services Architect

 

CA Technologies

Mobile: [phone] | [e-mail]

 

<mailto:[e-mail]>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>

[Remy Dessureault]

HI 

 

I've try:

Camstat (it's running a bunch of stuff...)

camping from agent to SS (work fine)

caf status (Everything running)

 

cserver check -c   from SS (error DM is unavailable. (exit code 103))

cserver register -a   (error DM is unavailbble (exit code 104))

caf register (create an entry in event viewer (1000 , error while registering, Delay...))

 

Sopmeone from our network services will be looking into that side.  They claim they haven't modified anything on their part... 

 

I saw two thing that might have cause the problem.

   VmTool have been updated

   Windows Server 2012 have been update with eptember KB.

 

could it be that ?

 

Rémy

[lecri01]

If you have agents connecting to the ss then look in the folder ..\ca\dsm\serverdb\collect\00000001.  Are there any files.  If so then that means the agents are connecting and sending inventory.  On an agent point to the this ss force the agent to run the agent to see if it populates.  On the agent machine

Run caf start amagent

 

If the agent populates then the ss is working as well as cam and caf.  Then you know it has to be an issue between the ss and the dm  do you have other ss are they working ok?

Richard Lechner

Principal Engineering Services Architect

 

CA Technologies

Mobile: [phone] | [e-mail]

 

<mailto:[e-mail]>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>

[Remy Dessureault]

Hi

 

we found part of the answer:

 

The VM tool were updated by the virtualization team, those Tools modify Something in the network card.  ITCM didn't like it…

 

We had to do a rollback on the tool as all the SS where stopping one after the other. (...after a reboot…)

 

 

 

Remy