This Appendix describes how to determine the names and addresses of internal and external peripheral devices. Internal peripheral devices can be disk drives and interface cards. External peripheral devices can be disk drives, printers, modems, and plotters that are cabled to connectors on the rear panel of a Sun system.
Before you can use these peripheral devices, your system must have information that these devices are present, a process that is often referred to as configuring a peripheral device.
Before you configure a peripheral device, you must determine:
Look in the hardware installation guide that accompanies the peripheral device and determine the interface of the device. Peripheral devices typically use one of the following interfaces:
In many cases, an external device is cabled to a connector that is part of a SCSI card. However, in some cases an external peripheral device is cabled to an onboard (built-in) SCSI connector. An onboard SCSI connector is usually part of the system board or main logic board.
You must determine the type of peripheral bus that your Sun system supports. As shown in Table F-1, there are two types of peripheral buses:
Your Sun system may have one or both types of peripheral buses. For information on the type of peripheral bus that your system has, refer to the hardware installation or service guide that accompanies your Sun system.
-------------------------------------------------
Peripheral Bus SCSI IPI -------------------------------------------------
SBus Built-in and cards Not supported
VMEbus Cards Cards
-------------------------------------------------
Typically, your sales representative provides you with the right interface card to fit the peripheral bus of your system and the type of interface that the peripheral device supports. Many systems have built-in SCSI support. Therefore, you would not need to install any additional cards.
You must determine the type of interface that your peripheral device requires before you can continue. If you have a peripheral device, such as a disk drive, that requires a SCSI interface, then your Sun system must also have a SCSI interface.
Sun systems support the following interfaces:
Note - Your Sun system may not support all of these interfaces unless you install additional SCSI cards or IPI cards. The hardware installation or service guide that accompanies your Sun system provides information on the types of interfaces that your system can support.
Sun systems often use the SCSI interface to communicate with their connected disks, tapes, and CD-ROM drives. Sun systems also use the IPI to communicate with their connected disks.
If the particular interface that your peripheral device needs requires you to install a card in your Sun system, make sure that you use a SCSI, IPI, serial, or parallel interface card that is designed for the peripheral bus of your Sun system.
To configure disk drives, tape drives, CD-ROM drives, printers, and modems, you need to understand the address selection scheme that your system uses for the specific peripheral device that you want to configure. Address selection schemes for disk drives differ from address selection schemes for tape drives. This section discusses the address selection schemes for different types of peripheral devices.
Make sure that your Sun system supports the interface that your drive requires. As most external drives require a SCSI interface, you may be able to connect them to the built-in SCSI connector of your Sun system. If your Sun system does not have built-in SCSI support, you will then have to install an additional SCSI card in your SBus or VMEbus. If you plan to connect a drive that requires IPI support, you must install an IPI card in the VMEbus.
Refer to your Sun system hardware installation or service guide for information on which type of interface support is built in. If the interface support for the drive that you plan to configure is not built in, you will have to install an interface card that supports the drive and fits the peripheral bus of your Sun system.
Your Sun system uses logical controller ID numbers, logical bus target ID numbers, logical disk ID numbers, and logical slice (often referred to as "partition") numbers to access specific areas on a given disk drive. A combination of all these ID numbers make up a device address for the drive.
A typical device address for a disk drive assigned by the Solaris 2.x operating system would be:
----------
c0t1d0s0 ----------
A typical device address for a CD-ROM drive assigned by the Solaris 2.x operating system would be:
----------
c0t6d0s0 ----------
The address selection scheme for disk drives that the Solaris 2.x operating system uses is shown in Figure F-1.
Figure F-1 Address Selection Scheme for Disk Drives
The Solaris 2.x operating system automatically assigns a device address to each internal and external disk drive connected to your Sun system.
Caution -
Logical controller ID numbers, such as c0, c1, c2, etc., are automatically assigned in sequential order to each interface card to which disk drives are connected. The interface cards can be located in either an SBus or a VMEbus.
The operating system detects or polls the interface cards one by one. If your Sun system has built-in SCSI support, the operating system automatically assigns 0 to that "card." Therefore, any disk drives that are connected to the built-in SCSI "card" have a device address that starts with c0. To change the polling order, refer to the OpenBoot PROM Toolkit User's Guide.
Logical target ID numbers, such as t0, t1, t3, correspond to the address switch setting that you select for each disk drive. All external disk drives have an address switch that is located on the rear panel. The default switch setting for Sun CD-ROM drives is 6. Internal disk drives usually have jumper settings that have been preset by the factory to 3, as shown in Table F-2. If your system has a second internal disk drive, it is usually set to 1 by the factory.
Note - Jumper settings serve the same purpose as address switch settings. They provide a unique address for a disk drive.
If you want to find out the current switch or jumper settings, you can use the
probe-scsi or the probe-ipi commands at the ok prompt. The
probe-scsi command returns the drive's logical target number and device
type (name). The probe-ipi command returns similar information about disk
drives that have an IPI interface.
You must set the address switch on all external disk drives. Since you can have up to seven devices daisy-chained to each SCSI or IPI interface card, you must assign and set a unique address (number) for each disk drive.
Table F-2 provides an example of how the Solaris 2.x operating system assigns device names to internal and external disk drives in a Sun system that has both an SBus and a VMEbus. In this example the Sun system has built-in SCSI support for three attached hard disk drives and one CD-ROM player; it also has two additional SCSI interface cards that are located in the SBus. Each of the SCSI cards has three external disk drives attached. In addition, this system has two IPI cards that are located in the VMEbus. Each of the IPI cards has three external disk drives attached.
Caution -
Table F-2 provides the information on how the Solaris 2.x operating system assigns device names of controller cards in a system based on the address switch settings selected for each disk drive.
Note - If you have an SBus-based Sun system, only the SCSI information applies. This table does not apply to the SPARCcenter 2000 and the SPARCserver 1000.
.
---------------------------------------------------------------------------------------------------------------
Disk Drives Built-In SCSI First SCSI Second SCSI First IPI Second IPI Support Interface Card Interface Card Interface Card Interface Card ---------------------------------------------------------------------------------------------------------------
First internal disk drive c0t3
Second internal disk drive; if c0t1
you do not have a second
internal disk drive, you can use
this address for your first
external disk drive.
First external disk drive that is c0t2
connected to the built-in SCSI
connector
Second external disk drive c0t0
CD-ROM player c0t6
First external disk drive c1t1
Second external disk drive c1t2
Third external disk drive c1t3
First external disk drive c2t1
Second external disk drive c2t2
Third external disk drive c2t3
First external disk drive c3t1
Second external disk drive c3t2
Third external disk drive c3t3
First external disk drive c4t1
Second external disk drive c4t2
Third external disk drive c4t3
---------------------------------------------------------------------------------------------------------------
Note - (1) If you have an SBus-based Sun system, only the SCSI information applies. (2) This table is not applicable to the SPARCcenter 2000 and the SPARCserver 1000.
Logical device ID numbers, such a d0, d1, and d2, are assigned by the Solaris 2.x operating system as follows:
Note -
The device ID number is always 0 for Sun products that are currently
being shipped. Third-parties may choose to use other numbering schemes.
Older, non-embedded Sun SCSI subsystems, such as the external storage
module, use the logical device ID.
Logical slice, or partition, numbers range from 0 to 7. To specify an entire disk, use slice 2. If you have a disk drive that has a logical bus target number of 1 and is supported by the built-in SCSI interface, the Solaris 2.x operating system assigns logical slice or partition numbers as follows:
----------
c0t1d0s0 c0t1d0s1 c0t1d0s2 c0t1d0s3 c0t1d0s4 c0t1d0s5 c0t1d0s6 c0t1d0s7 ----------
Use the format utility to display addresses of peripheral devices of disk drives. This section provides two examples:
To display addresses of connected and powered-on disk drives in an SBus system:
----------------------------
# format Searching for disks...done ----------------------------
The following example is based on an SBus-based system with built-in SCSI support. No additional SCSI cards have been installed. The system has one internal and one external hard disk drive.
Note - Device addresses for CD-ROM drives are not displayed by the format utility because the CD-ROM disk drive is a read-only device.
In this example, the Solaris 2.x operating system has assigned c0 as the logical controller ID number to all SCSI disks because they are supported by the built- in SCSI interface. The jumpers on the first internal hard disk have been set to 3 by the factory, resulting in a logical bus target ID number of 3 (t3).
The address switch on the first external hard disk has been set to 0, resulting in a logical bus target ID number of 0 (t0). The address switch on the CD-ROM drive has been set to 6 by the factory and was not changed resulting in a logical bus target ID number of 6 (t6).
The following information is then displayed (example for Sun-4C platforms):
The next display provides an example of format command for the SPARCcenter 2000 and the SPARCserver 1000:
Table F-3 shows the device name and path for each disk drive and the
CD-ROM drive in this example.
-------------------------------------------------------------------
Type of Device Device Name Device Path -------------------------------------------------------------------
First internal disk c0t3d0s0...7 /devices/sbus@1,f8000000/
(built-in SCSI support) esp@0,8000000/sd@3,0:..
First external disk c0t0td0s0...7 /devices/sbus@1,f8000000/
esp@0,8000000/sd@0,0:..
(built-in SCSI support)
CD-ROM player c0t6d0s0...7 ./devices/sbus@1,f8000000/
esp@0,8000000/sd@6,0:..
(built-in SCSI support)
-------------------------------------------------------------------
An example of a device path for the SPARCcenter 2000 and SPARCserver 1000 follows:
/devices/io-unit@f,e1200000/sbi@0,0/dma@1,81000/esp@1,80000/sd@0,0:..
To display the current setup of connected and powered-on disk drives in a Sun system with an SBus and a VMEbus:
----------------------------
# format Searching for disks...done ----------------------------
The following display provides an example of a system with an SBus and a VMEbus:
---------------------------------------------------------------------------
AVAILABLE DISK SELECTIONS: 0. c0t1d0 <SUN0669 cyl 1614 alt 2 hd 15 sec 54'> /iommu@f,e0000000/sbus@f,e0001000/dma@f,81000/esp@f,800000/sd@1,0 1. c0t2d0 <SUN0669 cyl 1614 alt 2 hd 15 sec 54'> /iommu@f,e0000000/sbus@f,e0001000/dma@f,81000/esp@f,800000/sd@2,0 2. c1t0d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@0,0/id@0,0 3. c1t1d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@0,0/id@1,0 4. c2t0d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@1,0/id@0,0 5. c2t1d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@1,0/id@1,0 6. c2t2d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@1,0/id@2,0 7. c2t3d0 <Seagate IPI ZBR Elite cyl 1893 alt 1 hd 17 sec 78'> /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4,d,1080000/ipi3sc@1,0/id@3,0 Specify disk (enter its number): ---------------------------------------------------------------------------
This example shows a server with built-in SCSI support (c0) to which two internal hard disk drives (sd@1,0, and sd@2,0) are connected. This system has two additional IPI cards (c1 and c2). The SCSI jumper switches on the disk drives have been set to 1 and 2 (t1 and t2).
There are two external disk drives (id@0,0, and id@1,0) connected to the first IPI card (c1). The IPI address switches on the disk drives have been set to 0 and 1 (t0 and t1).
There are four external disk drives (id@0,0, id1@1,0, id@2,0, and id@3,0) connected to the second IPI card (c2). The IPI address switches on the disk drives have been set to 0, 1, 2, and 3 (t0, t1, t2, and t3).
Table F-4 shows the device name and path for each disk drive.
--------------------------------------------------------------------------------------------------
Type of Device Device Name Device Path --------------------------------------------------------------------------------------------------
First internal disk (built-in c0t1d0s0...7 /iommu@f,e0000000/sbus@f,e0001000/dma@f,81000/esp@f
SCSI support) ,800000/sd@1,0
Second internal disk c0t2td0s0...7 /iommu@f,e0000000/sbus@f,e0001000/dma@f,81000/esp@f
,800000/sd@2,0
(built-in SCSI support)
First internal disk attached c1t0d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
to first IPI card in VMEbus /ipi3sc@0,0/id@0,0
Second internal disk c1t1d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
attached to first IPI card in /ipi3sc@0,0/id@1,0
VMEbus
First internal disk attached c2t0d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
to second IPI card in /ipi3sc@1,0/id@0,0
VMEbus
Second internal disk c2t1d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
attached to second IPI card /ipi3sc@1,0/id@1,0
in VMEbus
Third internal disk c2t2d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
attached to second IPI card /ipi3sc@1,0/id@2,0
in VMEbus
Fourth internal disk c2t3d0s0...7 /iommu@f,e0000000/vme@f,df010000/SUNW,pn@4d,1080000
attached to second IPI card /ipi3sc@1,0/id@3,0
in VMEbus
--------------------------------------------------------------------------------------------------
