Highlighted
Trusted Contributor.
Trusted Contributor.
156 views

Question for R & D

Hi.  I had previously created a Service Request for this but it was suggested I ask here.

I have an enrichment that builds 'consumer provider' relationships between servers and SAN logical volumes.

If a server is named eccdb1008, it will use SAN logical volumes (from storage devices topology by CIM) named eccdb1008_001, eccdb1008_002, etc.

In ci type manager, I can see one relationship between eccdb1008 and eccdb1008_009. (That server name and log volume name are unique.)

However, a query in the database shows 6 relationships.  How can this happen? Perhaps there is some characteristic of consumer provider that I am unaware of.

a_display_label a_root_class a_display_label a_root_class cmdb_id a_data_source

eccdb1008 unix eccdb1008_009 logical_volume 0x0329C3FA9CBDDDDD74865DE412AAC4A1 enrichment.ComputerToSANRelationships_Physical

eccdb1008 unix eccdb1008_009 logical_volume 0x1BB3AA6C04576A468ECD43EE6DBEAA30 enrichment.ComputerToSANRelationships_Physical

eccdb1008 unix eccdb1008_009 logical_volume 0x1E681DF7A40A7BFE80DD4C2603BB3AC9 enrichment.ComputerToSANRelationships_Physical

eccdb1008 unix eccdb1008_009 logical_volume 0xA0CFF2C3A5CDEFF4C506ACD1AE660679 enrichment.ComputerToSANRelationships_Physical

eccdb1008 unix eccdb1008_009 logical_volume 0xA62F4E8038621F42AAAB65A50F893FF1 enrichment.ComputerToSANRelationships_Physical

eccdb1008 unix eccdb1008_009 logical_volume 0xB66BC0CE5CDE15073E257DFBD4178265 enrichment.ComputerToSANRelationships_Physical



A side question. I tried getting the create timestamp of the relationship from cdm_root and was unable to do so. I tried joining consumer provider to cdm root and got nothing. Then, I hard-coded the cmdb IDs from consumer provider in a query against cdm_root and got nothing.

Here is the query to pull the relationships of computers to logical volumes (I used managed object at first because I was trying to narrow down where the high count of relationships came from.)

select end1.a_display_label,end1.a_root_class,
end2.a_display_label,end2.a_root_class,
cp.cmdb_id,
cp.a_data_source
from dbo.managed_object_1 end1,
dbo.managed_object_1 end2,
dbo.consumer_provider_1 cp
where end1.cmdb_id = cp.end1_id
and end2.cmdb_id = cp.end2_id
and cp.a_data_source like '%ford%'
and end1.a_display_label = 'eccdb1008'
and end2.a_display_label = 'eccdb1008_009'
order by end1.a_display_label

Here was my try to get data from cdm_root.

select * from dbo.cdm_root_1 where
cmdb_id in('0xB66BC0CE5CDE15073E257DFBD4178265',
'0x1BB3AA6C04576A468ECD43EE6DBEAA30',
'0x1E681DF7A40A7BFE80DD4C2603BB3AC9',
'0xA0CFF2C3A5CDEFF4C506ACD1AE660679',
'0xA62F4E8038621F42AAAB65A50F893FF1',
'0xB66BC0CE5CDE15073E257DFBD4178265')

Shouldn't this work?

 

 

0 Likes
3 Replies
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Question for R & D

Hello Everett,

We hope you are doing great !

We  involved more resources to help you on your request .

 

Best Regards.

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Question for R & D

Hi Everett,

To the secodn part of the question. The display label doesn't exist in persistency (not in the DB). It's calculated in runtime. The value you are looking for will be in name attribute.

 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Question for R & D

As to the last (query related) question: CMDB_ID is a varbin, so you can't use the quotes. Try:

select * from dbo.cdm_root_1 where cmdb_id in (0xB66BC0CE5CDE15073E257DFBD4178265, 0x1BB3AA6C04576A468ECD43EE6DBEAA30, 0x1E681DF7A40A7BFE80DD4C2603BB3AC9, 0xA0CFF2C3A5CDEFF4C506ACD1AE660679, 0xA62F4E8038621F42AAAB65A50F893FF1, 0xB66BC0CE5CDE15073E257DFBD4178265)

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.