SuperCluster M7 HOST0 Not Booting To OS After PDom Reboot During OESCU

Asset ID:	1-72-2184431.1
Update Date:	2016-10-18
Keywords:

Solution Type Problem Resolution Sure

Solution 2184431.1 : SuperCluster M7 HOST0 Not Booting To OS After PDom Reboot During OESCU

Applies to:

Solaris Operating System - Version 11.3 and later
Oracle SuperCluster M7 Hardware - Version All Versions and later
Information in this document applies to any platform.

Symptoms

ODM Issue Clarification
====================

Summary: M7 HOST0 not booting to OS after PDom reboot

Description
---------------
This issue was encountered while performing a new SuperCluster M7 installation.

OES-CU step 25 failed with error related to an issue on /HOST0, and it was recommended to reboot both physical domains to clear the issue.

After reboot, both hosts (0,1) stopped at the ok prompt. On booting HOST1 boot into the OS, while HOST0 failed with the error below:

{0} ok boot
1000 Mbps full duplex Link up
Boot device: net File and args:
1000 Mbps full duplex Link up
iscsi: Could not connect to 192.168.1.15:3260 (Connection timed out)
ERROR: /packages/obp-tftp: Could not open /iscsi-hba/disk

Customer needed help to recover from the situation.

Cause

Root cause for this was that the SP config was somehow corrupted during the process of trying to recover. It seems many manual Solaris LDOM commands were executed in order to try and recover. It is not supported to use manual Solaris LDOM commands to reconfigure LDOMS outside of the oes-cu tools.

Solution

The system had to go through a factory reset with the aid of RPE. In the future any and all errors or failure encountered while running oes-cu should be debugged instead of trying to force a workaround, and never should manual commands be used in place of SSC tools *unless* directed by engineering / RPE.

References

<BUG:23614070> - SUPERCLUSTER INSTALL ISSUES SR 3-12883163371
<NOTE:1547088.2> - How to Upload Files to Oracle Support

Attachments

This solution has no attachment