Interface CIT: Challenge populating data to Interface class
We're experiencing the following challenge:
We discover Interfaces as part of our discovery process. We want to enrich the Interface attributes through population. We export the discovered interfaces, update it with the data we wish to populate and use an integration job to load it back to HP uCMDB. This we we always know that we're working with existing Interfaces. When trying to do the population, our integration job fails due to not having enough reconciliation data. The one way to overcome the problem is to include the root_container.
Does anybody have an example/solution which included the root_container as we're not too familiar with exactly how this works.
Any other suggestion/guidance will be appreciated.
P.S. This thread has been moevd from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. - Hp Forum Moderator
Re: Interface CIT: Challenge populating data to Interface class
Root_container is the CI which has "composition" link towards your interface, in your case the Node.
It makes sense that in order to identify an interface you need to provide the Node which that interface is connected to. You will need to report in your "discovery" job the Node (probably just its name will do the work, but you might need more attributes for the Node's identification), the Composition link as well as the Interface.