Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
217 views

How to limit duplicates when using wmi and powershell and ntcmd

Jump to solution

ucmdb 10.01 cup8 content pack 12

 

The environment is such that we need to run WMI, Powershell, and NTCMD because we are not sure which will respond, but we know at least one will respond. 

 

Using all three protocols is leading to duplicates,

 

What is the best way to approach and address this issue.

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: How to limit duplicates when using wmi and powershell and ntcmd

Jump to solution

Kedem;

 

The 'best practice' is to discover with only one protocol (either WMI, NTCMD, PowerShell, SNMP)... The protocols will send back differing information even if discovering the same CI (due to the protocol and the tables it gets from the systems).

 

If that is not an option, you will, most likely, have to change the reconciliation rules for node (dangerous!!!) to expand the interfaces > 66% most likely...

 

Keith

Hope this helps,
Keith Paschal
UCMDB Worldwide Support Lead
Micro Focus 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'

View solution in original post

0 Likes
3 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: How to limit duplicates when using wmi and powershell and ntcmd

Jump to solution

Hello,

 

Based on the scenario described, it shouldn't be creating duplicates. Since there are, it might be due to some information not being collected properly. As a result we will need to look at these duplicates separetely.

Can you open a Support ticket and provide the properties export for each of the duplicates along with the communicationn log.

 

Thanks,

Ana Acosta-Diaz

 

"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'
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: How to limit duplicates when using wmi and powershell and ntcmd

Jump to solution

Kedem;

 

The 'best practice' is to discover with only one protocol (either WMI, NTCMD, PowerShell, SNMP)... The protocols will send back differing information even if discovering the same CI (due to the protocol and the tables it gets from the systems).

 

If that is not an option, you will, most likely, have to change the reconciliation rules for node (dangerous!!!) to expand the interfaces > 66% most likely...

 

Keith

Hope this helps,
Keith Paschal
UCMDB Worldwide Support Lead
Micro Focus 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'

View solution in original post

0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

Re: How to limit duplicates when using wmi and powershell and ntcmd

Jump to solution

The discovery should not be creating duplicates. Which CI types do you see being duplicated? If duplicates are created it should be treated as a bug.

 

The reason why several jobs are running and reporting data multiple times in this scenario is that Host Connection jobs create multiple protocols, such WMI, PowerShell and NTCMD, attach them to the Node and cause further discovery jobs to be triggered on these WMI, PowerShell and NTCMD CIs attached to the Node. There is some mutual exclusivity here, but not for everything. For example, you can take a look at the Trigger TQL for the Host Connection by WMI job. When it gets triggered on the Node with the attached IP address, it only selects those nodes to which there is no Shell CI attached (that includes NTCMD as it is a child of the Shell CI) - you can see the Cardinality condition of 0..0 between Node and Shell. This means that you should not be getting WMI and NTCMD based jobs running at the same time because the Host Connection by WMI should not be creating the WMI protocol CI as it would not be triggering on those nodes where NTCMD is already attached. But there is no such exclusivity/condition for PowerShell (and in the trigger TQL for Host Connection by PowerShell).

 

To summarise, if you do not rely on any PowerShell or WMI specific jobs (other than Host Resources and Application jobs) you can change the trigger TQL for

  • Host Connection by WMI job to avoid triggering on Nodes that have PowerShell CIs attached to them (NTCMD is already excluded out of the box)
  • Host Connection by PowerShell job to avoid triggering on Nodes that have NTCMD or WMI CIs are attached to them

Then you would need to clean up UCMDB so that only one type of protocol (NTCMD - preferred, PowerShell or WMI) is connected to existing Node CIs. The new exclusivity TQL conditions will ensure that it stays that way.

 

Thanks,

  Vitaly

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.