SuperCluster - LDOMs Are Missing

Asset ID:	1-72-1680732.1
Update Date:	2014-10-16
Keywords:

Solution Type Problem Resolution Sure

Solution 1680732.1 : SuperCluster - LDOMs Are Missing

Applies to:

Solaris SPARC Operating System - Version 11.1 to 11.1 [Release 11.0]
Oracle SuperCluster T5-8 Half Rack - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster T5-8 Full Rack - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster M6-32 Hardware - Version All Versions to All Versions [Release All Releases]
SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

The application LDOM's are not visible in a SuperCluster following a maintenance operation or unintentional power cycle

# ldm list

NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-c-- UART 256 1048064M 2.6% 2.6% 23m
#

# ldm list-spconfig
factory-default [current]
layout7
layout7_ML12112013184702
layout7_ML02242014193237
layout7_ML03032014142318

Changes

The system has some hardware issues, and we have faults listed in ilom snapshot.

faultmgmtsp> fmadm faulty
------------------- ------------------------------------ -------------- --------
Time UUID msgid Severity
------------------- ------------------------------------ -------------- --------
2014-06-08/23:22:21 95671b34-594c-6745-bd3f-ebe2dc15020c SPT-8000-HR Major

Fault class : fault.component.disabled

FRU : /SYS/PM1/CMP0/BOB0/CH0/D1
(Part Number: 07042210)
(Serial Number: 00AD011302493F85F9)

Description : A chassis component or device has been disabled.

Response : The Host will cease using the disabled component; reset may
be required.

Impact : The component cannot be used until enabled by an
administrator.

Action : The administrator should review the ILOM event log for
additional information pertaining to this diagnosis. Please
refer to the Details section of the Knowledge Article for
additional information.

Cause

There are still HW faults reported in the ilom. The POST indicates errors in HW, which indicates the system still has some HW issue.
During such situation, the system set the spconfig to factory default.

Once all the HW issue is fixed and faults are cleared, we need to set the spconfig to desired one and do a node reboot.

Solution

1. We need to fix the HW issue that has been listed in the HW alert. Please raise an SR and understand if anything need to be fixed.

2. Once the HW has been replaced, the fault need to be cleared

To clear these faults, for each fault UUID listed in the 'fmadm faulty' run

# fmadm repair <uuid>
example: #fmadm repair 6f6b149a-2206-c967-ebd4-a3c52be6bed0

# fmadm repaired <fmri | label>
example: #fmadm repaired /SYS/PM1/CMP0/BOB0/CH0/D1
# fmadm faulty (to make sure the output is clean after repair)

Exit and rest the SP.

reset /SP
start /SYS

3. Once the HW issue is fixed and the faults are cleared spconfig need to be restored. # ldm set-spconfig

# ldm list-spconfig
factory-default [current]
layout4_ML12112013184702
layout6_ML02242014193237
layout7 [next poweron]

4. Once the spconfig is restored it will be effective only on next power up. Please stop the /SYS and start it again.

-> stop /SYS
-> start /SYS

5. Now the system should list all the application LDOM

# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 96 327168M 9.3% 9.3% 4m
ssccn2-app1 active -n---- 5001 32 192G 7.9% 7.9% 4m
ssccn2-app2 active -n--v- 5002 32 192G 13% 13% 4m
ssccn2-app3 active -n--v- 5003 96 320G 0.4% 0.4% 4

Attachments

This solution has no attachment