Vice Admiral Vice Admiral
Vice Admiral
565 views

service navigator discovery

Jump to solution

we found new functionality in omw9 named service navigator discovery, agents discovers data and sends them to server for modelling service navigator tree, similar daemon with name "service discovery server" is a part of omu 9 linux.

question:

why is hp announcing this type of modelling by old-fashioned navigator, when go-forward strategy is omi and modelling inside bsm/rtsm/ucmdb ?

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Absent Member.
Absent Member.

You are correct, the go forward strategy is OMI and modeling inside bsm/rtsm/ucmdb.

 

However this doesn't mean that we are abandoning our "classic" OMW, OML servers etc.

 

There was a long standing request to open up the development of custom discovery policies. This finally made it into OMW9, where you can develop your custom script that does (agent-based) discovery and reference it within the new service discovery policy.

 

Synchronization between an OM and OMi server is also improved with OMi 9.0. OMi now also includes a discovery server component. In addition to basic toposync (available with OMi 8.10 already) OMi 9.0 now offers "dynamic" toposync, SPI discovery data is sent to OMi as soon as an Operations Agent discovers a change. This is much faster now, we call it "near real time".

View solution in original post

0 Likes
3 Replies
Absent Member.
Absent Member.

You are correct, the go forward strategy is OMI and modeling inside bsm/rtsm/ucmdb.

 

However this doesn't mean that we are abandoning our "classic" OMW, OML servers etc.

 

There was a long standing request to open up the development of custom discovery policies. This finally made it into OMW9, where you can develop your custom script that does (agent-based) discovery and reference it within the new service discovery policy.

 

Synchronization between an OM and OMi server is also improved with OMi 9.0. OMi now also includes a discovery server component. In addition to basic toposync (available with OMi 8.10 already) OMi 9.0 now offers "dynamic" toposync, SPI discovery data is sent to OMi as soon as an Operations Agent discovers a change. This is much faster now, we call it "near real time".

View solution in original post

0 Likes
Vice Admiral Vice Admiral
Vice Admiral

ok, thanks, but can you specify how exactly is this collected topology mapped into objects and relations in rtsm/ucmdb ?

what exactly is done by OMU component named "omu service discovery server " ? is this one responsible for sync of topology data between omu and omi ?

0 Likes
Absent Member.
Absent Member.

Regarding your question what the OMU service discovery server does...

(1) it updates the OM service model with new content discovered by the OM agents

(2) it synchronizes the OM model (nodes, node groups, services) with other OM and OMi servers.

 

Note, at this point in time only the OMW discovery server synchronizes the service model with OMi as well as to other OM servers. The same capabilities will become available with OMU 9.? patch ??? expected shortly.

 

Unfortunately we don't have a customer version of the "OM service navigator" to RTSM/UCMDB mapping.

 

Basically both OM services and nodes have become CIs in the RTSM, eg. for nodes:

Windows Nodes in OM are mapped to NT CIs in the RTSM

Unix Nodes in OM are mapped to Unix CIs in the  RTSM

SNMP Nodes in OM are mapped to netdevice CIs in the  RTSM

Unknown Nodes in OM are mapped to node CIs in the  RTSM.

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.