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-1004664.1
Update Date:2011-01-13
Keywords:

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.  


Related Items
  • Sun Enterprise 3000 Server
  •  
  • Sun Enterprise 4500 Server
  •  
  • Sun Enterprise 5500 Server
  •  
  • Sun Enterprise 4000 Server
  •  
  • Sun Enterprise 5000 Server
  •  
  • Sun Enterprise 6000 Server
  •  
  • Sun Enterprise 3500 Server
  •  
  • Sun Enterprise 6500 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Midrange Servers
  •  

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:

/sbus@3,0/SUNW,fas@3,0/sd@0,0

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:

Front Slot

Sbus@

Sbus@

0

0

1

2

4

5

4

8

9

6

c

d

8

10

11

10

14

15

12

18

19

14

1c

1d

Table 1(b): Rear Slot Assignments

Sbus@

Sbus@

Rear  Slot

2

3

1

6

7

3

a

b

5

e

f

7

12

13

9

16

17

11

1a

1b

13

1e

1f

15

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

Front

Sysio A

Sysio B

soc@d

fas@3

sbus@1

hme@3

sbus@2

sbus@0

Rear

soc@d

fas@3

sbus@1

hme@3

sbus@2

sbus@0

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)

  • Device path correlates to an I/O board in slot 3 of a UE server (sbus@6)
  • The onboard socal controller (socal@d), and the GBIC port (sf@0) *** See note below.
  • ssd@2200002136bcd49,0 (ssd27) is a disk inside of an A5x00 array
    • The long number after `ssd@' is the world wide (unique) number of this particular disk.

***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

  • Device path correlates to an I/O board in slot 2 in the front of a Ultra Enterprise server (sbus@5)
  • SCSI controller card in slot 2 on the I/O board (scsi@2)
  • st@5 is a SCSI tape (st) drive at target id 5 attached to this controller.

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.

sbus@2 = Divide the 2 by 2 to reveal the I/O board slot number "2/2 = 1"
I/O board slot number = 1

NOTE:  Always divide the "sbus@#" by 2, the remainder is not important (i.e /sbus@7, 7/2 = 3 r1).

The device drivers used in this example are some of many device drivers that could appear in the device driver section. See examples below:

E3x00

only have board slots in the back (internal disks in front)

E4x00, E5x00, & E6x00

have board slots in the front and back

fas

driver for fast/wide SCSI controllers (on-board)

hme

driver for Fast Ethernet

isp

driver for differential SCSI controllers and the SunSwift Card

glm

driver for UltraSCSI controllers

scsi

driver for Small Computer Serial Interface (SCSI) devices

sf

driver for soc+ or socal Fiber Channel Arbitrated Loop (FCAL)

socal

driver for SPARC Storage Array (SSA) controllers

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
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback