Hi,

We’re using ADDM 8.2, currently when LDOMs (running Solaris 10) are discovered they are grouped by host container.

When this information is passed to the CMDB a CI is created for the host container with a link to each of the LDOM CIs. The impact relationship shows that if any LDOM goes down the host container will be impacted (screen shot attached). This is not an accurate impact representation.

Not all LDOMs are created equal… one LDOM per Host container is the control domain, as its name implies, this controls the logical domain environment. It is used to configure machine resources and guest domains, and provides services necessary for domain operation. All other LDOMs below the host container are guest domains, running user applications.

If the control domain goes down this will take the guest domains down also. Whereas if a guest domain goes down it will only affect the applications/services using that particular guest domain.

Why is this not represented in the relationships produced by ADDM?

Many thanks

James

James,
ADDM does not take in to account the LDOM role when creating the containment relationship between the HostContainer and the contained Hosts.

Some of the impact relationships are backwards, as the HostContainer will not be impacted if any LDOM guest is down, but all LDOM guests will be impacted if the HostContainer is down. This is set by the CMDB.HostContainer_ComputerSystem syncmapping (in combination with the Sun.SolarisLDom pattern module that creates the containment relationships in the first place:

54 sync.rel.BMC_Component(
55 Source := container_cs,
56 Destination := computersystem,
57 Name := “SYSTEMPARTITION”
58 );

I would advice you to raise a proper support ticket for this issue as it does not only affect Solaris LDOMs, but other HostContainer types as well.

Thanks for your response Petrus – I’ll raise a support ticket in regard to the relationship direction.

Do you know whether ADDM could discover the LDOM role?

If I remember correctly, it does discover the LDOM role, but it is not visible in the UI. Someone might correct me here if I am mistaken :)