Highlighted
Visitor.
257 views

LDOM virtualization credentials

UCMDB 10.32

CP25

Hi Experts,

We have a problem with missing relationships between hypervisor and host.

Datas From Cmdb:

{unix@49e354db5cddccc991e66eba4facdcad}@[(string-bios_serial_number:[Empty CMDB property value]), (string-snmp_sys_name:[Empty CMDB property value]), (string-bios_asset_tag:[Empty CMDB property value]), (string-os_family:unix), (string-primary_dns_name:ABC), (string-ud_unique_id:[Empty CMDB property value]), (string-global_id:49e354db5cddccc991e66eba4facdcad), (string-serial_number:[Empty CMDB property value]), (string-net_bios_name:[Empty CMDB property value]), (string-cloud_instance_id:[Empty CMDB property value]), (string-host_nnm_uid:[Empty CMDB property value]), (string-name:afektglobal), (string-bios_uuid:[Empty CMDB property value])] with grade : 600

 

{unix@c527e9303516900591e4e28932c6e50a}@[(string-bios_serial_number:[Empty CMDB property value]), (string-snmp_sys_name:[Empty CMDB property value]), (string-bios_asset_tag:[Empty CMDB property value]), (string-os_family:unix), (string-primary_dns_name:XYZ), (string-ud_unique_id:[Empty CMDB property value]), (string-global_id:c527e9303516900591e4e28932c6e50a), (string-serial_number:2230886709), (string-net_bios_name:[Empty CMDB property value]), (string-cloud_instance_id:[Empty CMDB property value]), (string-host_nnm_uid:[Empty CMDB property value]), (string-name:afekt), (string-bios_uuid:F9687C99-9941-4628-DA0F-D321878437F3)] with grade : 1000

Reason: Contradiction encountered when trying to merge Cis

We think this [empty cmdb property value] can be privileges issue, but which privileges do we need to obtain data like string-bios_serial_number (necessary to make a relationship)?

0 Likes
3 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: LDOM virtualization credentials

The information which you have supplied is not very much. Who is trying to merge the CIs? Why they should be merged? From what I see, they have different 'name' (afektglobal vs afekt)  attribute and different primary_dns_name (ABC vs XYZ). I am really surprised that the UCMDB doesn't create two separate CIs... or does?

Empty attributes are not taken into account into reconciliation process. You can see that in the identification rules:

<attribute-condition attributeName="bios_serial_number" includeNullValue="false" conditionType="approveAndContradict" matchNameOnly="false"/>

permissions.pdf exists and what permissions each adapter needs in order to fill certain attribute

Likes are appreciated!
0 Likes
Highlighted
Visitor.

Re: LDOM virtualization credentials

Hi,

We had problem with missing relationship beetwen afektglobal and afekt (afekt is solaris zone on afektglobal). UCMDB was trying make a relationship between this two, but due not enough data it couldn't (hence the idea about permissions). Now we have other problem. Solaris zones by tty provided us relationships, but afekt now is connected to two virtualization layers (zones and ldom).

How it look like: ldom server->ldom hypervisor->afekt and afektglobal->zones hypervisor->afekt

How it should look like: ldom server->ldom hypervisor->afektglobal->zones hypervisor->afekt

The point is afektglobal have no relationship to ldom hypervisor. Relationship directly from afekt to ldom hypervisor shouldn't exist.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: LDOM virtualization credentials

well it looks like there is difference between your perception of what should be the model and the R&D one. Maybe is best to contact them through support ticket and eventually raise Enhancement Request. 

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.