Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..
580 views

UCMDB sees *two* HP Operations Agents on each server

Hi,

My customer has an integrated environment with UCMDB, OMi/OBM etc, as well as a lot of OA's (Operations Agent) on all Linux-servers that are monitored by OBM. UCMDB is used as the master CMS in their environment. An issue in UCMDB, though, is that its inventory scanners consequently discover *two* InstalledSoftware CI instances called "HP Operations Agent" on each Server. On one of them the FileSystemPath attribute is "/opt/" and on the other the same attribute is "/opt/OV/bin/".

Furthermore, the scanners also seem to discover two RunningSoftware CI instances which are fairly similar for each of the servers, one called "HP Operations Agent" and one called "HP OpenView Agent". If I look at the related Process CI's for each of these two, the former is dependant of four processes called ovbbccb, ovconfg, opcmsga and ovcd. The latter is dependant on opcmsga & ovcd (i.e. the exact same instances as the former) as well as opcmsgi and opcacta. So they i.e. seem to have split the various processes of the normal OA in between them.

Do you know what is going on here? Is it the OA-bundled Performance Agent (PA) that somehow messes up things? I would expect UCMDB to be able to handle OA's very well, considering that they are developed by the same vendor 😉

BR,
Frank Mortensen
Managon AB

0 Likes
6 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB sees *two* HP Operations Agents on each server

Hi Frank, 

talking about the first issue. Can you check who is the CreatedBy on both the instances? It is possible that you have enabled the discovery of InstalledSoftware from two different places - from the Inventory by Scanner and from the Host Application by Shell. 

If this is not the case, check the processed scanner file, open it with winzip (by adding .gz at the end of the file) and read the XML to see what is sent.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

Likes are appreciated!
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB sees *two* HP Operations Agents on each server

On the second issue, the Running Software is discovered based on the ApplicationsSignature.xml. What I can see from the file, there are two separate requirements in order to discover Operations Agent vs OpenView Agent:

 

    <Application-Component app_id="HP Operations Agent" name="HP Operations Agent" vendor="hewlett_packard_co" supported_versions="11.x">
        <process name="ovbbccb" description="HTTP / HTTPS communication controller" />
        <process name="ovconfd" description="Config management" />
        <process name="opcmsga" description="Message Agent" />
        <process name="ovcd" description="HP OpenView Ctrl Service" />
        <process name="ovbbccb.exe" description="HTTPS communication controller" />
        <process name="ovconfd.exe" description="Config management" />
        <process name="opcmsga.exe" description="Message Agent" />
        <process name="ovcd.exe" description="HP OpenView Ctrl Service" />
    </Application-Component>

 

 

 

    <Application-Component app_id="HP OpenView Agent for Unix" name="HP OpenView Agent" vendor="hewlett_packard_co" supported_versions="7.x, 8.x, 9.x">
        <process name="opcctla" description="Control Agent" />
        <process name="opcmsga" description="Message Agent" />
        <process name="opcacta" description="Action Agent" />
        <process name="ovcd" description="HP OpenView Ctrl Service" />
        <process name="opcmsgi" description="Message Interceptor" />
    </Application-Component>

As you can see,  ovcd and opcmsga match, but the rest don't.  So if you have some old running processes left after upgrade of the agents, it is fully possible to be valid to have both the version discovered. Check the communication file from the Application By Shell discovery.

 

Petko

 

Likes are appreciated!
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: UCMDB sees *two* HP Operations Agents on each server

Hi, and thanks for your replies!

Regarding the first; They are both created at the exact same second by the exact same UCMDBDiscovery-scanner.

Regarding the second; Yes, we found that very old "HP OpenView Agent" definition after my initial posting 🙂 I'm surprised it is still there in the signature file. Our UCMDB guys have now disabled it. Thanks!

Cheers,
Frank

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB sees *two* HP Operations Agents on each server

Hi,

so on issue 1, you can check the processed scanner file for this computer and find out the InstalledSoftware detected. We have to know if the scanner is causing this behaviour or something with the enricher. 

on issue 2, you can always disable the signature, which will work until the next update of UCMDB, when you have again to disable it. More interesting is why do you have the old processes available in the discovered server, if you don't use openview agent any more.

Petko

Likes are appreciated!
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: UCMDB sees *two* HP Operations Agents on each server

On issue 1; thanks for the tip

On issue 2; There are two signatures in the file (HP OpenView Agent and HP Operations Agent) and these are by default tied to a few dedicated processes and two common processes. Those two common processes were included in the agent back in the old days, when it was in fact called an HP OpenView Agent and they are included in the agents today, not that it is called HP Operations Agent (which is not really the correct namy anymore either, considering that it is now MicroFocus...). So this is what causes the confusion. The HP OpenView definition should really have been removed completely from the signature file.

Cheers,
Frank

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: UCMDB sees *two* HP Operations Agents on each server

Yeah, it strange that the processes mentioned in openview are indeed part of operations agent which causes the discrepancy. Maybe you can raise a ticket to support to fix this in the next CP. 

Petko

Likes are appreciated!
0 Likes
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.