Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1003441.1
Update Date:2009-09-23
Keywords:

Solution Type  Technical Instruction Sure

Solution  1003441.1 :   Sun Fire[TM] 3800R/4800(R)/4810(R)/6800: Server I/O Card Probe Order  


Related Items
  • Sun Fire E6900 Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Fire E4900 Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Fire 4810 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
204826


Description

This document describes the general OBP card probe/discovery order for a Sun Fire[TM] 3800R/48x0(R)/6800 system. This probe order is useful in pre-determining what Solaris[TM] Operating System instance a particular card might have upon installation or reconfigure reboot. Note that the OS probes in the opposite order that the OBP does.



Steps to Follow

The general probe order is:

 # highest IB to lowest IB
# Schizo 1 then Schizo 0, within the current IB
# Leaf A (66Mhz) of the current Schizo first
# Leaf B (33Mhz) of the current Schizo next, highest slot number first 

For an 8-slot PCI IB, the order is: 7, 6, 5, 4, 3, 2, 1, 0
For a 6-slot cPCI IB, the order is: 1, 5, 4, 0, 3, 2
For a 4-slot cPCI IB, the order is: 1, 0, 3, 2

Note that the actual instance numbers assigned depend upon factors other than just this probe order - such as previously existing hardware instances in /etc/path_to_inst, etc.

Related Documents:

Infodoc 45360 - Provides more information on /etc/path_to_inst and on boot -r



Product
Sun Fire 6800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire 3800 Server
Sun Fire E6900 Server
Sun Fire E4900 Server

3800, 4800, 4810, 6800, path_to_inst, pci, ib
Previously Published As
72350

Change History
Date: 2005-03-28
User Name: 97961
Action: Approved
Comment: Publishing.
Version: 8
Date: 2005-03-28
User Name: 97961
Action: Accept
Comment:
Version: 0
Date: 2005-03-28
User Name: 74729
Action: Approved
Comment: ready to be published
Version: 0
Date: 2005-03-15
User Name: 74729
Action: Accept
Comment:
Version: 0
Date: 2005-03-15
User Name: 38093
Action: Approved
Comment: See 2 previous comments on what was changed.
Version: 0
Date: 2005-03-15
User Name: 38093
Action: Add Comment
Comment: Also infodoc 15626 has been archived and incorporated in to 45360. Changed doc to indicate that.
Version: 0
Date: 2005-03-15
User Name: 38093
Action: Update Started
Comment: The probe order here is for the OBP. The OS probes in the opposite order. Adding comment to indicate this. I had a PS person build a large design spec based on this and it was incorrect.
Version: 0
Date: 2005-02-24
User Name: 7058
Action: Approved
Comment: Updates OK.
Republishing
Version: 5
Date: 2005-02-23
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2005-02-23
User Name: 137953
Action: Approved
Comment: Removed internal SWAN URL from free document.
Added keywords
Version: 0
Date: 2005-02-23
User Name: 137953
Action: Update Started
Comment: Fixing Related Document URL
Version: 0
Date: 2004-12-12
User Name: 97961
Action: Approved
Comment: Converted to STM formatting to improve readability of doc. Fixed some trademarking issues.

Review date will not be moved to 5 years time. It is SOP to review knowledge every year to ensure that we have a knowledge base is up to date and relevant.
Version: 3
Date: 2004-12-12
User Name: 97961
Action: Accept
Comment:
Version: 0
Date: 2004-12-12
User Name: 93923
Action: Approved
Comment: I agree with renewal- Is there any method to renew for greater than 1 year. Would be good to renew this doc for 5 years.
Product has not been EOL'd as yet. This doc will be valuable
information for a minimum of 5 years. Very likely longer, but no need
to create extra review work.
Version: 0
Date: 2004-12-12
User Name: 93923
Action: Accept
Comment:
Version: 0
Date: 2004-12-10
User Name: 81757
Action: Approved
Comment: document needs to be renewed, as it is expired.
Version: 0
Date: 2004-12-02
User Name: 81757
Action: Update Started
Comment: Document is technically accurate and should be renewed for one year.
Version: 0
Date: 2003-11-13
User Name: 91361
Action: Approved
Comment: KE'd, checked for duplicates, ... ready to publish.

- KE, Matt Steck
Version: 0
Date: 2003-11-08
User Name: 72607
Action: Approved
Comment: Great info, and that's right, there's no duplicated info into SunSolve. Please publish
Version: 0
Date: 2003-11-07
User Name: 76225
Action: Approved
Comment: This doesn't appear to be out there anywhere, yet....
Version: 0
Date: 2003-11-07
User Name: 76225
Action: Created
Comment:
Version: 0
Product_uuid
29da7938-0a18-11d6-8a41-9ed1ad6d6779|Sun Fire 6800 Server
29d6f808-0a18-11d6-8aa8-943929fbbdd8|Sun Fire 4810 Server
29d3a694-0a18-11d6-92da-df959df44cdd|Sun Fire 4800 Server
29d05214-0a18-11d6-92b2-a111614865b5|Sun Fire 3800 Server
4fe39727-0599-11d8-84cb-080020a9ed93|Sun Fire E6900 Server
bed24aa9-0598-11d8-84cb-080020a9ed93|Sun Fire E4900 Server

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback