Document Audience:INTERNAL
Document ID:I0707-1
Title:Booting from Network problem with Solaris 2.5.1 & 2.6 with 464MHz or faster CPU
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2001-08-16

---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)
FIN #: I0707-1
Synopsis: Booting from Network problem with Solaris 2.5.1 & 2.6 with 464MHz or faster CPU
Create Date: Aug/16/01
Keywords: 

Booting from Network problem with Solaris 2.5.1 & 2.6 with 464MHz or faster CPU

SunAlert: No
Top FIN/FCO Report: No
Products Reference: Solaris 2.5.1 and Solaris 2.6
Product Category: Server / Service
Product Affected: 
Mkt_ID   Platform   Model   Description            Serial Number
------   --------   -----   -----------            -------------
  -      E3000       ALL    Ultra Enterprise 3000        -
  -      E3500       ALL    Ultra Enterprise 3500        -
  -      E4000       ALL    Ultra Enterprise 4000        -
  -      E4500       ALL    Ultra Enterprise 4500        -
  -      E5000       ALL    Ultra Enterprise 5000        -
  -      E5500       ALL    Ultra Enterprise 5500        -
  -      E6000       ALL    Ultra Enterprise 6000        -
  -      E6500       ALL    Ultra Enterprise 6500        -   
  -      E10000      ALL    Ultra Enterprise 10000       -
  
Systems Affected
----------------

X-Options Affected
------------------
X2590A     -          -     E10000 SERVICE PROCESSOR    -
Parts Affected: 
Part Number   Description   Model
-----------   -----------   -----
     -             -          -
References: 
BugId: 4399377 - hme: boot net fails with greater than 400 Mhz cpu
                 modules on 2.5.1 and 2.6.
Issue Description: 
E10000 and EXX00 availability may be impacted negatively when
attempting to boot from the network due to a timing problem with the
network interface and processors of 464MHz or faster with Solaris OS
versions 2.5.1 and 2.6.  This problem could impact any customer who
installs the 464MHz processors for E10000s and EXX00s or for new
E10000s and EXX00s shipped with 464MHz processors.

With the impending release of UltraSparc-II 464MHz processors for the
E10000 Server, a problem has been discovered which could prevent a
customer from booting a domain with these processors. Getting this
information to the field will allow customers to use the workaround to
avoid the problem.

When trying to boot a domain from a qfe or hme network interface using
Solaris 2.5.1 or Solaris 2.6 and using these faster processors, the 
boot can fail and providing the following message repeatedly:

       SUNW,hme0: Link Down - cable problem?

The problem is caused by the hme/qfe driver's auto-negotiation algorithm
failing with the faster processors due to timing issues.

Solaris 2.5.1 and 2.6 will not be patched. Instead follow the workaround
provided.
Implementation: 
---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        |   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---
Corrective Action: 
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above 
mentioned problem:
        
To prevent this problem from occurring, implement ONE of the following
workarounds:

  From OBP, change the transfer speed of the interface to 10Mbps.

        apply transfer-speed=10 

      For example:

        apply transfer-speed=10 /sbus@50,0/SUNW,qfe@0,8c30000

        The path can be obtained from the "show-nets" command in OBP. 
         
  Then boot from the network device.
         
	 NOTE: This is an interim solution to complete the
               netinstall process and setup the system for local disk 
               booting.  The interface will switch back to 100Mbps for
               subsequent reboots and should work just fine.
Comments: 
None
    
------------------------------------------------------------------------------
Implementation Footnote: 
i)   In case of MANDATORY FINs, Enterprise Services will attempt to    
     contact all affected customers to recommend implementation of 
     the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Enterprise 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, Enterprise 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.ebay/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.Corp/

* From there, select the appropriate link to browse the FIN or FCO
index.

Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
  accessed internally at the following URL: http://edist.corp/.
  
* From there, follow the hyperlink path of "Enterprise Services
Documenta- 
  tion" and click on "FIN & FCO attachments", then choose the
appropriate   
  folder, FIN or FCO.  This will display supporting directories/files
for 
  FINs or FCOs.
   
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
---------------------------------------------------------------------------
Statusactive