Absent Member.
Absent Member.

HP UCMDB Discovery doesn't work

I choose, IP Sweep detection, infraestructure, virtualization, software, etc. but the system never recognize nothing.

The probes are deactivated and doesn't says the reason,


How can I do for results?, credentials issues?

2 Replies
Absent Member.. Absent Member..
Absent Member..

Re: HP UCMDB Discovery doesn't work

Have the probes been configured with appropriate credentials? 

Have you considered posting your question in the product forums related to UCMDB?

Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: HP UCMDB Discovery doesn't work

If you haven't done so, check out the Discovery Modules, Data Flow Managament, Discovery Activities and Supported Content guides, they are good resources.

Content packs usually include a permissions PDF but didn't see one in CP 18. CP 17 used CP16's permissions PDF. This is a great resource to use when asking for discovery credentials.

Some jobs have pre-reqs to do before running them. Like the VMware job requires a VMware jar file from the VMware SDK. The VMware connection job also requires the VMware vCenter Running Software to be discovered first so you need to use a Host Applications or Host Resources job with the appropriate parameters on. For the VMware topology job, you need to run the VMware connection job first to discover the VMware Virtual Center CI that it VMware topology job uses as a trigger

You can also go to the Dependency Map on the Discovery Job to see what job(s) is required to run the job you want to run.

i.e To discover Windows servers with WMI:
1. Add a WMI Protocol with appropriate permissions (see the Content Pack's Permission PDF or the Discovery Modules guide)

2. Add the IPs to the appropriate probe with firewall access for the appropriate ports (see Discovery Modules and Supported Content guides) to those servers

3. Discover the IPs usually with a ping sweep

4. Since you are using WMI, run Host Connection with WMI

*Note: when you run a Discovery job, you also need to make sure a Job Execution Policy, Time Template or Discovery Scheduler does not block the job


Rey Lejano

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.