Document Audience: | INTERNAL |
Document ID: | I0951-1 |
Title: | Sun Fire B100s Server FRU's may boot from network instead of local disk after installation due to two incorrectly set OBP parameters. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | 2005-03-07 |
---------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0951-1
Synopsis: Sun Fire B100s Server FRU's may boot from network instead of local disk after installation due to two incorrectly set OBP parameters.Create Date: Apr/11/03
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Sun Fire B100s Servers
Product Category: Server / Service
Product Affected:
Systems Affected:
-----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- A44 ALL Sun Fire B1600 -
X-Options Affected:
-------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
Part Number Description Model
----------- ----------- -----
540-5078-03 FRU BLADE 1X512MB 30GB STL0 -
540-5079-03 FRU BLADE 2X512MB 30GB STL0 -
540-5454-03 FRU BLADE 2X1GB 30GB STL0 -
References:
N/A
Issue Description:
A small number of Sun Fire B100s FRUs have shipped from the factory
with two incorrectly configured OBP parameters. This will cause the
system to attempt to boot from the network when it is powered on. A
boot from local disk is required for initial installation. In general,
these incorrect settings will not affect customers' operation of the
system.
This issue affects Sun Fire B100s FRUs installed in Sun Fire B1600 Blade
Servers which shipped during February 2003. There are approximately
200 affected FRUs.
The part number breakdown is as follows:
F540-5078 FRU,BLADE,1X512MB,30GB,STL0 x 69
F540-5079 FRU,BLADE,2X512MB,30GB,STL0 x 69
F540-5454 FRU,BLADE,2X1GB,30GB,STL0 x 64
The affected Sun Fire B100s Blades have OBP environment variables set
(incorrectly) as follows:
diag-device = net
diag-script = none
These OBP environment variables can be displayed either from the OBP "ok"
prompt or from Solaris.
From OBP:
ok printenv diag-device
ok printenv diag-script
From Solaris:
#eeprom diag-device
#eeprom diag-script
When this issue occurs, the system will not run OBdiag tests at poweron
and will attempt to boot from the network rather than disk. However,
the first action that a customer needs to perform is to network install
a blade by booting from the local disk. The disk image contains a
pre-install boot stub image which would initiate a network install.
This issue occurs due to the B100s FRUs being incorrectly configured at
the factory. Current shipments of these FRUs are now being correctly
configured.
Implementation:
---
| | MANDATORY (Fully Proactive)
---
---
| | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
The following recommendation is provided as a guideline for authorized
Sun Services Field Representatives who may encounter the above
mentioned problem.
If the issue described above is detected for any Sun Fire B100s FRU,
perform the following procedure:
1. Poweron the the Blade at the system controller sc> prompt.
sc> poweron Sn (where is the slot number of the blade)
2. Connect to the Blade console.
sc> console Sn
[Connected with input enabled on fru S0]
Escape Sequence is '#.'
3. When the Blade has completed OBP initialization, return to the SC
prompt (using #.) and send a break to the blade to stop it booting.
#.
sc> break Sn
Are you sure you want to send break to FRU s0 (y/n)? y
s0: Break sent.
4. Reconnect to Blade console. (you may need to press return to get
a prompt)
sc> console Sn
[Connected with input enabled on fru S0]
Escape Sequence is '#.'
ok
5. Correct the invalid OBP parameters.
ok setenv diag-script all
diag-script = all
ok setenv diag-device disk net
diag-device = disk net
6. Restart the boot by typing 'boot disk' from the 'ok' prompt.
ok boot disk
If Solaris is up and running, the settings can be corrected from a root
login shell using
eeprom diag-script=all
eeprom diag-device="disk net"
Comments:
NOTE: Ship Start Date: February 1, 2003 (date affected system started
shipping)
Ship End Date: February 28, 2003 (when fix was incorporated in Mfg)
RR Date: March 11, 2003
============================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Sun Services will attempt to contact
all affected customers to recommend implementation of the FIN.
ii) For CONTROLLED PROACTIVE FINs, Sun Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Sun Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.central/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.central/
* From there, select the appropriate link to browse the FIN or FCO index.
Internet Access:
----------------
* Access the top level URL of https://spe.sun.com
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------