Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1009033.1
Update Date:2018-03-06
Keywords:

Solution Type  Problem Resolution Sure

Solution  1009033.1 :   Sun Enterprise[TM] 10000 Server: HPOST exits quickly but doesn't indicate any FAILED components.  


Related Items
  • Sun Enterprise 10000 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>High-End Servers
  •  

PreviouslyPublishedAs
212453


Applies to:

Sun Enterprise 10000 Server - Version All Versions to Not Applicable [Release All Releases to N/A]
All Platforms

Symptoms

 Although HPOST doesn't FAIL any components, it exits almost immediately with a generic message such as the following:

Exitcode = 76: Unable to configure a bootable system
POST (level=16, verbose=20) execution time 0:03
Further investigation of the post log reveals the following, but still no
concrete indication as to what the problem might be:
phase cplane_isolate: CP domain cluster mask clear...
No minimum system left after CP domain cluster mask clear! Bailing out!

The entire POST log might look as follows:

00 # SMI E10000 POST log opened Mon Nov 10 22:03:27 2003
01 # hpost version 3.4 May 14 2001 11:49:18
02 # pid = 28781 level = 16 verbose_level = 20
03 # SSP name: dssp04m.
04 # HOSTNAME = bbp
05
06 Significant contents of /export/home/ssp/.postrc:
07 #
08 logfile
09
10 Using blacklist file /var/opt/SUNWssp/etc/sapto4/blacklist
11 #=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
12 proc 4.3 5.3 15.0 15.1 15.2 15.3 14.0 14.1 13.1 13.2 13.3 12.0 12.2
13 abus 0
14 Reading centerplane asics to obtain bus configuration...
15 Bus configuration determined to be 3F.
16 phase cplane_isolate: CP domain cluster mask clear...
17 No minimum system left after CP domain cluster mask clear! Bailing out!
18
19 Board Descriptor Array: Bus Config 3F
20 Proc M/Grp IOC/Slot CIC PC XDB LDPTH
21 Brd Gen 3210 3210 1/3210 0/3210 3210 210 3210 10
22 0: c cccc c/cccc c/cccc c/cccc cccb ccc cccc cc | G=Good
23 1: c cccc c/cccc c/cccc c/cccc cccb ccc cccc cc | f=Failed
24 2: c cccc c/cccc c/cccc c/cccc cccb ccc cccc cc | m=Missing
25 3: c cccc c/cccc c/cccc c/cccc cccb ccc cccc cc | b=Blacklist
26 4: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr | r=Redlisted
27 5: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr | c=Crunched
28 6: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr | _=Undefined
29 7: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr | x=NotInDoma
30 8: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr | u=G,unconfi
31 9: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
32 A: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
33 B: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
34 C: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
35 D: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
36 E: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
37 F: x rrrr r/rrrr r/rrrr r/rrrr rrrr rrr rrrr rr
38
39 Exitcode = 76: Unable to configure a bootable system
40 POST (level=16, verbose=20) execution time 0:03
41 # SMI E10000 POST log closed Mon Nov 10 22:03:30 2003

 

As you can see, there is no indication of a component that has FAILED and at first glance, it might be difficult to determine where the problem lies.
The key here can be found at line 13 of the above POST log. It appears that Address Bus 0 (abus 0) has been blacklisted, yet the bus configuration

(line 15,19) of the platform calls for the use of all 4 address buses and both data buses. Similarly, in cases where a data bus (dbus X) has been
incorrectly blacklisted, the end result was also that a problem such as this was encountered.

In this sample case, looking at the blacklist file for the platform (/var/opt/SUNWssp/etc/<platform name>/blacklist) revealed that someone had
recently editted the blacklist file using hostview. The indication was as follows:

#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+

#Blacklist file edited by Hostview - Wed Nov 5 16:21:58 MET 2003

#=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+

 

Changes

 

Cause

 The blacklist file has been updated to include abus or dbus.

Solution


To resolve this issue, remove the 'abus' or 'dbus' entry from the blacklist
file and execute the 'bringup' command again. If the intent was to actually
blacklist one of these buses, all domains MUST be down and a 'bringup -C'
must be issued to reconfigure the centerplane.

Internal Comments
This problem resulted in a Sev 1 Task for CaseID 36996496. Searching
SunSolve revealed that this problem had also been seen in at least 4 other
cases as well.

Sun Enterprise 10000, hpost
Previously Published As 72404


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback