Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1004664.1 : Decoding Enterprise[TM] 3000, 3500, 4000, 4500, 5000, 5500, 6000, and 6500 Server device paths to identify a board slot number.
PreviouslyPublishedAs 206465 Description Decoding device paths to board slot locations.The document provides instructions, tables, and examples to assist a user in identifying which board slot number is referenced from a Sun Enterprise[TM] (also known as "Ultra Enterprise") 3000, 3500, 4000, 4500, 5000, 5500, 6000, and 6500 Server device path. Steps to Follow Decoding device paths to identify a board slot number.Example using a device path from an Ultra Enterprise[TM] 3000 Server:
The first portion ("sbus@3,0")of the device path indicates the I/O board slot location. In Table 1 below, sbus@3,0 correlates to the I/O board in slot 1 which is located on the rear of the machine (UE 3000's only use the rear, odd number slots because there are internal disks in the front). I/O Board Sbus@Front/Rear Slot Assignments Table 1(a): Front Slot Assignments:
Table 1(b): Rear Slot Assignments
The second portion ("SUNW,fas@3,0") of the device path indicates the type of onboard controller and the Sys I/O bus it uses (see Table 2 below). I/O boards are basically split in half, each half is controlled by a Psycho or Sys I/O chip (A or B). SUNW,fas@3,0 correlates to the onboard (built-in) fast/wide SCSI controller at Sys I/O B on this board. Onboard Controller Assignments Table 2: Onboard Controller Assignments
The next portion of the device path ("sd@0,0") correlates to the SCSI disk (sd) set to target id 0 (in this case an internal disk, since only internal disks should be controlled by the onboard SCSI controller of the I/O board in slot 1). Example 1: /sbus@6,0/SUNW,socal@d,0/sf@0,0/ssd@2200002136bcd49,0 (ssd27)
***NOTE: sf@0 is the GBIC port on the right and sf@1 is the GBIC port on the left when looking at an I/O with soc+ (socal) board.; On an Enterprise 3000 & 3500, sf@0 is the GBIC port on the bottom and sf@1 is the GBIC port on the top. Example 2: /sbus@5,0/scsi@2,0/st@5,0
Example 3: Without access to the tables above, one is forced to use a different method to determine slot location. /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020370df2a8,0 Divide the "sbus@#" by 2, the remainder is not important.
The device drivers used in this example are some of many device drivers that could appear in the device driver section. See examples below:
Note: From the Ultra™ Enterprise™ 3000 System Installation Guide (802-6050), section 2.7, and the Sun Enterprise 6500/5500/4500 Systems Installation Guide (805-2631) section 2.8: “External SCSI-2 devices connect to your system through the built-in single-ended Fast/Wide SCSI-2 port on I/O boards (except for the board in slot 1), or through FSBE/S, DSBE/S, SWIS/S, or DWIS/S SBus cards installed on I/O boards. Note – The onboard SCSI-2 bus on the I/O board in slot 1 controls internal SCSI tray devices. Therefore, the external SCSI connector on the I/O board in slot 1 must always have a terminator installed.” The HD68, Single Ended, Fast Wide terminator, part number 150-2267, should be used to terminate the SCSI port on I/O board #1. Product Sun Enterprise 6000 Server Sun Enterprise 5000 Server Sun Enterprise 4000 Server Sun Enterprise 3000 Server Sun Enterprise 6500 Server Sun Enterprise 5500 Server Sun Enterprise 4500 Server Sun Enterprise 3500 Server decode, device path, board, slot, location, classic, ultra enterprise, sun enterprise, IO, io device, decoder, path Previously Published As 22759 Change History Date: 2009-11-24 User Name: Josh Freeman Action: Refreshed Comment: Format modifications and removed Internal Section (it was duplicate of info in Steps to Follow. Ready to roll per ESG Content Team. Date: 2008-01-08 User Name: 95826 Action: Update Canceled Comment: *** Restored Published Content *** canceling update to allow migration to IBIS Version: 0 Date: 2008-01-08 User Name: 95826 Action: Reassign Comment: reassigning document to release it in order to allow migration to IBIS Version: 0 Attachments This solution has no attachment |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|