![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1332034.1 : Unable To Boot The Domain due to "No usable Cpu board or IO board in domain"
In this Document Created from <SR 3-3777866741>
Applies to:Sun Fire 6800 Server - Version: Not ApplicableSun Fire E6900 Server - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Sun Fire 4800 Server - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Sun Fire E4900 Server - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Information in this document applies to any platform. Symptoms=== Issue Clarification === For any Mid-Range Servers, you will not be able to boot a domain due to the fact that the minimum number of CPU or IO board in the domain is not present. === Issue Verification === To check for Hardware failure, the SA need to log into the Main system controller and on the Platform shell execute these commands to confirm that there are hardware failures preventing the domain from booting. sc> showboards -v sc> showcomponent -v sc> showlogs -v sc> showlogs -d <domain-id> sc> showplatform sc> showchs -b sc> showerrorbuffer The key message indicator in such a situation is "No usable Cpu board in domain" seen in the showlogs -v output. In this example, the domain-B has only one IB8 and one SB5, both of which have been marked as failed. This will prevent the domain from booting, even if either one of the boards is marked as failed. Thorough investigation is required from Oracle and an 'explorer -w scextended' needs to be sent to Oracle for further investigation. See Document 1019066.1 If an explorer cannot be gathered for some reason, see Document 1003529.1 that outlines the commands to collect data from the SC manually. XXX:SC> showboards -v Slot Pwr Component Type State Status Domain ---- --- -------------- ----- ------ ------ SSC1 On System Controller Main Passed - SSC0 On Present Spare - - ID0 On Sun Fire 6800 Centerplane - OK - PS0 On A152 Power Supply - OK - PS1 On A152 Power Supply - OK - PS2 On A152 Power Supply - OK - PS3 On A152 Power Supply - OK - PS4 On A152 Power Supply - OK - PS5 On A152 Power Supply - OK - FT0 On Fan Tray Low Speed OK - FT1 On Fan Tray Low Speed OK - FT2 On Fan Tray Low Speed OK - FT3 On Fan Tray Low Speed OK - RP0 On Repeater Board - OK - RP1 On Repeater Board - OK - RP2 On Repeater Board - OK - RP3 On Repeater Board - OK - /N0/SB0 - Empty Slot Assigned - A /N0/SB1 On CPU Board V2 Active Passed A /N0/SB2 - Empty Slot Assigned - A /N0/SB3 On CPU Board V2 Active Passed C /N0/SB4 - Empty Slot Assigned - A /N0/SB5 Off CPU Board V2 Assigned Not tested B << /N0/IB6 On PCI I/O Board Active Passed A /N0/IB7 On PCI I/O Board Active Passed C /N0/IB8 On PCI I/O Board Assigned Degraded B << /N0/IB9 - Empty Slot Assigned - A Component J-No. Size Reason --------- ----- ---- ------ /N0/SB5 - - No board power Component Segment Compatible In Date Time Build Version --------- ------- ---------- -- ---- ---- ----- ------- /N0/SB5/FP0 - - - - - - No board power /N0/SB5/FP1 - - - - - - No board power /N0/IB8/P1/B0 disabled - chs 66/33MHz. PCI Bus /N0/IB8/P1/B1 disabled - chs 33MHz. PCI Bus Domain: B Jun 02 12:47:49 xxxxxx Domain-B.SC: [ID 483975 local0.error] [AD] Event: SF6800.ASIC.CHEETAH.EMU_C2MS_WER.732411a1 CSN: 0425MM21B5 DomainID: B ADInfo: 1.SCAPP.21.1 Time: Thu Jun 02 12:47:48 GMT+10:00 2011 FRU-List-Count: 1; FRU-PN: 5016178; FRU-SN: A45076; FRU-LOC: /N0/SB5/P3 Recommended-Action: Service action required Jun 02 12:47:49 xxxxxx Domain-B.SC: [ID 610449 local0.warning] Excluded unusable, unlicensed, failed or disabled board: /N0/SB5 Jun 02 12:47:49 xxxxxx Domain-B.SC: [ID 834059 local0.error] No usable Cpu board in domain. CauseHardware Failure located on SB5 and IB8 in this exampleSolutionFor this example, FE must take these actions:1.- Replace the SB5 2.- Replace the IB8 3.- Run post with diag level set to max (or mem2 if memory is suspect) 4.- Boot the domain and confirm if the system is working fine. References<NOTE:1003529.1> - Procedure to manually collect System Controller (SC) level failure data on Sun Fire[TM] v1280, E2900, 3800, 4800, E4900, 6800, E6900, and Netra 1280, 1290 servers.<NOTE:1019066.1> - How to collect scextended or 1280extended Explorer on Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900 and Netra[TM] 1280, 2900 servers. Attachments This solution has no attachment |
||||||||||||
|