SuperCluster: OESHM reports "Unable To Contact Logical Domain"

Asset ID:	1-72-2293934.1
Update Date:	2017-11-27
Keywords:

Solution Type Problem Resolution Sure

Solution 2293934.1 : SuperCluster: OESHM reports "Unable To Contact Logical Domain"

Applies to:

Oracle SuperCluster M7 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster Specific Software - Version 2.x to 2.x [Release 2.0]
Information in this document applies to any platform.

Symptoms

OESHM dashboard reports ldom does not communicate with Oracle Enterprise System Hardware Manager(OESHM), even though the domain is up and hwmgmtd package is installed.

Message report follows.

Component Name:
Compute Server 2
LDOM Name: ssccnxxxx
Serial Number: AKxxxxxx
Problem Type: Communication
Severity: Warning
State: Open
Message: Unable to contact logical domain ssccnxxxxconsole (PDOM0). Some or all information may not be displayed. Please check that the domain is up and hwmgmtd package is installed.
Reported: 05/15/2017 at 18:00:50 CEST
UUID: d6073bbd-750f-4961-ab43-cb0be0b99203
FMA Message ID:
Rack Slot: 27

---

root@xxxxx:~# pkg info hwmgmtd
  Name: system/management/hwmgmtd
  Summary: Oracle Hardware Management Pack - Hardware Agent
  Description: Oracle Hardware Management Tools - hardware management agent
  daemon
  Category: System/Administration and Configuration
  State: Installed
  Publisher: solaris
  Version: 2.3.7.0
  Build Release: 5.11
  Branch: 0.175.3.11.0.4.0.11031106.10000110
  Packaging Date: Fri Feb 10 19:50:57 2017
  Size: 5.57 MB
  FMRI: pkg://solaris/system/management/hwmgmtd@2.3.7.0,5.11-0.175.3.11.0.4.0.11031106.10000110:20170210T195057Z

Cause

Error while OESHM communicates with logical domain on the system, this is likely to occur when a domain undergoes reconfiguration (freeze, name changes, domain removal/addition, LDOMS are taken DOWN due to panic/hang/stop or reconfiguration)

Solution

Gather OESHM Snapshot, this gathers data for the OESHM application itself.

This is gathered from the Setup -> Maintenance -> Snapshot page of the BUI.

Review OESHM snapshot if there are some ldom related state issues reported, where a problem is reported because the LDOM was off. If the LDOM is now on, and those problems remain, the suggestion is then to restart ESHM and see if the problem is still reported.

You can restart ESHM via the BUI at

Setup Up -> Maintenance -> Restart.

There is an underlying software bug in the HMP hwmgmtd agent in the control domain of each server. The symptoms can be addressed by executing the following in each control domain:

svcadm restart /system/sp/management

SuperCluster Custom Incorporation (SC CI) 11.3.11.6.0-1.10 and later (for SRU 11) and 11.3.14.6.0-1.8 or later (for SRU 14) contains a fix for

25144873 ESHM: Unable to contact logical domain

This fix address a majority of the causes of the 'unable to connect" message.

Attachments

This solution has no attachment