Highlighted
Absent Member.. Absent Member..
Absent Member..
114 views

UD - Reoccuring Discovery Errors

Jump to solution

Hello experts.

We are running the "Range IPs by ICMP" discovery job, which, in turn, triggers three diffrent jobs: "Host Connection by Shell", "Host Connection by WMI" and "Host Connection by SNMP".
My question is in regard to a lot of errors on the "Host Connection by WMI" job.
I can see that a lot of the errors on the job "Host Connection by WMI", do not come from Windows servers, but from linuxs or other networking devices in our environment.

  1. I understand that when a trigger IP is created, it's just an IP address, and UD tries all the discovery jobs available on the trigger CI to get more information about it. But once uCMDB knows it's not a windows server (i.e. linux or cisco switch-router) - how does the discovery job "know" when to stop using this CI? Where is this defined?
  2. When I re-run the discovery job, all the trigger CIs are activated once more - am I correect about this?

Any document or KB references would be greatly appreciated!

Thank you very much in advance,
Binyamin Kisch,
Bezeq International.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Trusted Contributor.
Trusted Contributor.

Re: UD - Reoccuring Discovery Errors

Jump to solution

Hello,

Hope you are more than great. 

The Windows domain in which the credentials are defined. If this field is left empty or is not a valid domain, the WMI protocol assumes the user is defined locally on the host. This is the way that the Job can defined is a Windows Ci or not.

And about the second question, yes, you are rigth. 

You can fin more information on the guides. UCMDB DataFlow_Mgmt.

 

Kind Regards

 

 

View solution in original post

1 Reply
Highlighted
Trusted Contributor.
Trusted Contributor.

Re: UD - Reoccuring Discovery Errors

Jump to solution

Hello,

Hope you are more than great. 

The Windows domain in which the credentials are defined. If this field is left empty or is not a valid domain, the WMI protocol assumes the user is defined locally on the host. This is the way that the Job can defined is a Windows Ci or not.

And about the second question, yes, you are rigth. 

You can fin more information on the guides. UCMDB DataFlow_Mgmt.

 

Kind Regards

 

 

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.