Highlighted
Micro Focus Expert
Micro Focus Expert
148 views

map all CIs respective types in CMDB

Summary:

Existing Operations Connector for Icinga is monitoring all CIs from Icinga and mapping them as Windows or Linux based on flavor of the node and if the CI type doesn't belongs to any OS it will be fall back to host_node type. Instead of generalizing the nodes to "host_node", we can enhance the mapping of CIs by discovering all the nodes to specific CI type in OBM. Which can be done by enhancing the topology collection to map all CIs to specific CI type.

*****************************************************************************************************************************

Customer is using the Icinga Integration (version: 2019.05) and are trying to send topology and events to an OBM 2019-05 (classical installation).

By default the Icinga Integration sends the Node-CIs as CI_Type Computer/host_node. With the Atrium Integration they import Server CIs as host_node and Netdevices (like Firewalls) as netdevice.

Most of the monitored devices in Icinga are network devices (Load Balancers, Firewals). But in RTSM the host_node from Icinga-Integration does not reconcile with netdevice from Atrium Integration.


"Computer" and "NetDevice" are sibling CITs (they have the same parent: Node). in that case, CMDB doesnt allow reconciliation to sibling CIT.

it looks like this connector reads topology by running Java program. it then connects to Icinga via REST API and parse the response JSON. If the OS Type is not Windows or Unix (as returned from Icinga) then it is assigning "Computer" CIT


Below the forum discussion with Asaf Shechter. as per his opnion

it looks like this connector reads topology by running Java program. it then connects to Icinga via REST API and parse the response JSON. If the OS Type is not Windows or Unix (as returned from Icinga) then it is assigning "Computer" CIT hard-coded. this is the code snippet doing so:


if (!(this.OsName.isEmpty())) {
s_logger.debug("Assigning the os name ci type");
hostinstance.setKey(this.OsName + ":" + this.DisplayName);
hostinstance.setCiType(this.OsName);
this.parentCIName = this.OsName;
}
else {
s_logger.debug("Assigning host node as ci type");
hostinstance.setKey("host_node:" + this.DisplayName);
hostinstance.setCiType("host_node");
this.parentCIName = "host_node";
}

see OCTIM19G521468 for more info.

 

Kind regards,

Patrick Westdorp

Labels (1)
0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: map all CIs respective types in CMDB

hi Mamta,

Would you have any comments on this please ?

thank you.

 

Kind regards,

Patrick Westdorp
(patrick.westdorp@microfocus.com)

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: map all CIs respective types in CMDB

Not sure what is this case about. But in order to reconcile to  NetDevice subtypes, you have to put the generic devices in a parent class - Node in this case. If this is done in the code, produced by MicroFocus, open a topic in https://community.microfocus.com/t5/CMS-Idea-Exchange/idb-p/CMS_Idea.

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.