UCMDB and UD Practitioners Forum (Previously CMS)
Showing results for 
Search instead for 
Do you mean 

host connection by shell problem with one CI

Frequent Advisor

host connection by shell problem with one CI

Hi

 

When host connection by shell  job ends for on server, it creates 4 CI-s: Windows and three Interfaces. It does not create a link between the IP and Windows CI. And it doesnt create ntcmd ci. Thus it does not run host application by shell.

uCMDB was 10.01 - upraded it to 10.10 and the result was the same

server is windows 2012

It says the job was completed.

 

On a similar machine (windows 2012), it creates ntcmd CI-s and host application by shell runs ok.

 

Has anyone idea where to look for the mistake. I think the Data Flow Probe doesnt get the neccesary info from the server.

Will this prevent the creation of ntcmd ci ?

 

Bests

Stream

4 REPLIES
HPE Expert

Re: host connection by shell problem with one CI

Could you please show us Communication log with enbled results in it?

Regards
-Dmitry Gomel, PMP
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Click the Like button at the bottom to say 'Thanks'.
Frequent Advisor

Re: host connection by shell problem with one CI

Selected the option to log the results, rerun the discovery and it reported CIs correctly. I previosly ran the job maybe 4 times. I dont know what was different now.

Trusted Contributor

Re: host connection by shell problem with one CI

stream0,

 

Do you also run Host Connection by WMI on the same nodes that are also discovered with Host Connection by Shell (NTCMD)

 

If you do, check the history on that node. I've seen Windows CIs that are discovered with both WMI and NTCMD, the other discovery job will delete the other protocol CI.

An example is that if you run Host Connection by WMI then it creates a related WMI agent to the node. Then run Host Connection by Shell, the job then removes the WMI agent and create the NTCMD agent. I've seen a few instances of this.


The CI History will have these changes.

Rey Lejano

effectualsystems.com
Frequent Advisor

Re: host connection by shell problem with one CI

Hi

 

Thanks for the idea, but I am running only jobs by ntcmd. So this was not behind the problem.

 Thus far it seems to working fine.

 

 

Bests

stream0 

//Add this to "OnDomLoad" event