More flexible ways to create unique node hints for OMi events

[jack_oneil]

OMi does not use RTSM topology to relate the CI hint to the node hint for incoming events. Therefore, globally unique identifiers are required for both hints. This can be challenging in a large multi-tenant environment and the options for node hints are limited.

We need a more flexible node hint solution. Specifically, we would like to be able to tell OMi to include an additional, optional, user designated attribute in addition to PrimaryIPAddress and PrimaryDnsName . The user designated attribute might be the Node NNMI UID, the Node NNM internal key, the global ID, the CMDB ID, etc.; whichever is easiest to populating in an incoming event.

[Andreas TSI]

I think this idea was still requested as ER, but never implemented.

Hope this will be don ein future and you have my vote.

Kind regards

Andreas

[SH]

Thanks for providing this idea. Could you please describe the scenario in more detail in which the related CI hint is not sufficient to set the hosting node correctly. An example would be helpful.

Thanks & regards,

Stefan Haug

[Chris_597]

HI Stefan,

Please see this lab case where workarounds were proposed and enhancement was discussed with customer and our lab.  

QCIM8D113213 SD02556352

Please let us know if you need more details why the Node Hint if blank or shortname will not work    RCH work fine and we use the NNMID@@Host there for the interface events but Node hints use different resolution attributes like Primary DNS  which is not always consistent for Routers and Switches.  

Thanks,

Chris Matye

[Chris_597]

Basically the idea was to make it configurable as to which attributes are used to identify nodes for CI resolution.  Write now it is hard coded : primary_dns_name, ip_address, and name.

They would like to be able to configure additional attributes to be used to identify nodes as well.

Regards,

Mike