Absent Member.. Absent Member..
Absent Member..

UCMDB Support Tip: How a probe is selected to run a trigger according to the adapter’s input CI type

-   Trigger CI type is ip address: simply take the probe from the ip_probename attribute.


-   Trigger CI type is running_sofware: probe is chosen according to the following running software attributes:

  • Application_ip
  • Application_ip_domain  (Simply check in the DomainScopeDocument which probe in the domain contains the application_ip in its range).

-   Trigger CI type is node: One of the IPs connected to the node will be chosen, and its ip_probename property will define the probe (exception: if the node has UD agent connected to it, the probe will be calculated from it like RSW – starting from version 10.0).


-   Other CI types: we recursively search a node using composition links, and then taking the ip from the related ip address.


-   If ‘override probe selection’ is defined for the adapter, these rules won’t be applied and the probe will be calculated from there.

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
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.