SCSI Device Configuration Examples for N-Class and A-Class HP e3000 Systems
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
Commercial Systems Division Device configuration for N-Class and A-Class systems is accomplished using the same tools (SYSGEN, IOCONFIG) as existing HP e3000 Systems. Your MPE/iX 7.0 Release software will include four new default configuration groups: CONFNCL1 - N-Class booting from internal disk drive
CONFNCL2 - N-Class booting from external disk drive
CONFACL1 - A-Class booting from internal disk drive
CONFACL2 - A-Class booting from external disk drive These configuration files provide the minimum set of devices necessary to boot the system and start the installation process. You will need to modify your configuration file to connect additional SCSI devices to your system. This article will provide a step by step description of configuring both SCSI Device Adapter cards and attached SCSI peripherals on an N-Class System. This article will not provide a complete listing of other possible hardware types. The A-Class's interface will be similar enough to allow a System Manager experienced in configuring hardware to apply this N-Class example to an A-Class system. This article will not cover configuration of the system Console nor the configuration of Data Communications/Networking Devices.
 |
NOTE: The installation of Device Adapter Cards is a complex operation requiring partial disassembly of your system and is best left to your HP Hardware Support Technician. |
Determining the type of cards that are in your system
The following operations are accomplished while the system is "down," e.g. not running MPE/iX. Start by entering a Control-B at the system console. You may be prompted for a logon id and password, each of which currently defaults to a single Carriage Return. At the GSP> prompt enter an RS or TC command, confirm it and acknowledge any prompts that are presented. You should soon find yourself at the main Boot Command Handler (BCH) menu (If you have problems please refer to the MPE/iX System Software Maintenance Manual for this Release which should include a more complete description of rebooting your system):
Console Display #1
Main Menu: Enter command or menu > di
---- Main Menu -----------------------------------------------------------
Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices
COnfiguration menu Displays or sets boot values
INformation menu Displays hardware information
SERvice menu Displays service commands
DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
----
Proceed to the Information menu:
Console Display #2
Main Menu: Enter command or menu > in
---- Information Menu ----------------------------------------------------
Command Description
------- -----------
ALL Display all system information
BootINfo Display boot-related information
CAche Display cache information
ChipRevisions Display revisions of major VLSI
COprocessor Display coprocessor information
FRU Display FRU information
FwrVersion Display firmware version
IO Display I/O interface information
LanAddress Display Core LAN station address
MEmory Display memory information
PRocessor Display processor information
WArnings Display selftest warning messages
BOot [PRI|ALT|<path>] Boot from specified path
DIsplay Redisplay the current menu
HElp [<command>] Display help for specified command
RESET Restart the system
MAin Return to Main Menu
----
For the purposes of this article we are only interested in
the I/O information for this system. The "IO" function
will provide two sets of information in two sections. The first section
is the listing of the System and Local Bus Adapters; the Local Bus
Adapters with slot numbers 1-12 are potential Device Adapter locations.
The second section is the listing of PCI Device Adapters that are
actually present on the system. These controllers are either Device
Adapter Cards or the embedded functions of the Core I/O Card.
Console Display #3
Information Menu: Enter command > io
I/O MODULE INFORMATION
Path Slot IODC
Type (dec) Number HVERSION SVERSION Vers
---- ----- ------ -------- -------- ----
System bus adapter 0 0x8030 0xc10 0x0
Local bus adapter 0/0 Built_In 0x7820 0xa00 0x0
Local bus adapter 0/1 Built_In 0x7820 0xa00 0x0
Local bus adapter 0/2 6 0x7820 0xa00 0x0
Local bus adapter 0/4 2 0x7820 0xa00 0x0
Local bus adapter 0/5 1 0x7820 0xa00 0x0
Local bus adapter 0/8 4 0x7820 0xa00 0x0
Local bus adapter 0/10 5 0x7820 0xa00 0x0
Local bus adapter 0/12 3 0x7820 0xa00 0x0
System bus adapter 1 0x8030 0xc10 0x0
Local bus adapter 1/0 12 0x7820 0xa00 0x0
Local bus adapter 1/2 10 0x7820 0xa00 0x0
Local bus adapter 1/4 9 0x7820 0xa00 0x0
Local bus adapter 1/8 11 0x7820 0xa00 0x0
Local bus adapter 1/10 8 0x7820 0xa00 0x0
Local bus adapter 1/12 7 0x7820 0xa00 0x0
PCI DEVICE INFORMATION
Path Vendor Device Bus Slot
Description (dec) Id Id # #
----------- ----- ---- ---- --- ---
Ethernet cntlr 0/0/0/0 0x1011 0x19 0 Built_In
SCSI bus cntlr 0/0/1/0 0x1000 0xc 0 Built_In
SCSI bus cntlr 0/0/2/0 0x1000 0xf 0 Built_In
SCSI bus cntlr 0/0/2/1 0x1000 0xf 0 Built_In
Comp. ser cntlr 0/0/4/0 0x103c 0x1048 0 Built_In
Comp. ser cntlr 0/0/5/0 0x103c 0x1048 0 Built_In
Fibre channel 0/1/0/0 0x103c 0x1028 8 Built_In
SCSI bus cntlr 0/5/0/0 0x1000 0xc 40 1
Ethernet cntlr 0/10/0/0 0x1011 0x19 80 5
SCSI bus cntlr 0/12/0/0 0x1000 0xf 96 3
SCSI bus cntlr 0/12/0/1 0x1000 0xf 96 3
SCSI bus cntlr 1/0/0/0 0x1000 0xb 128 12
SCSI bus cntlr 1/0/0/1 0x1000 0xb 128 12
SCSI bus cntlr 1/10/0/0 0x1000 0xf 208 8
SCSI bus cntlr 1/12/0/0 0x1000 0xc 224 7
Information Menu: Enter command >
The hardware path can loosely be interpreted as:
System Bus Location / Local Bus Number / PCI Device / PCI Device Function
One potential point of confusion is that, unlike existing
HP e3000 systems, there is no formula to correlate Slot #, physical
location in the system, with Bus # and Path. Notice from the above
that the System has enough information to identify "SCSI
bus cntlr" or "Ethernet cntlr." Each
path marked "SCSI bus cntlr" represents a separate
SCSI Bus. The Vendor Id, Device Id, Path and Bus/Slot information
may be used to uniquely identify each PCI-SCSI Device Adapter Card type.
Table 4-3 Card Type with Vendor Id. and Device Id.
| Card Type | Vendor Id | Device Id |
|---|---|---|
| A4800A (SP HVD) | 0x1000 | 0xf (same as A5159A) |
| A5159A (DP HVD)* | 0x1000 | 0xf (same as A4800A) |
| A5149A (SP LVD/SE) | 0x1000 | 0xc |
| A5150A (DP LVD/SE)* | 0x1000 | 0xb |
Example #1: Correlating Path and Card Type.
Using the information in Table #1 with the output from console display #3 command we can derive the following:| Path | Device Id. | Card Type |
|---|---|---|
| 0/0/1/0 | 0xc | Core I/O Embedded A5149A (SP LVD/SE) |
| 0/0/2/0, 0/0/2/1 (pair on same bus) | 0xf,0xf | Core I/O Embedded A5159A (DP HVD) |
| 0/12/0/0, 0/12/0/1 ( " " " " ) | 0xf,0xf | A5159A (DP HVD) |
| 1/0/0/0, 1/0/0/1 ( " " " " ) | 0xb,0xb | A5150A (DP LVD/SE) |
| 1/10/0/0 | 0xf | A4800A (SP HVD) |
| 1/12/0/0 | 0xc | A5149A (SP LVD/SE) |
Determining the Devices connected to the system
The N-Class system has a built in function that will search for devices attached to the system. This function is available on the Main Menu as the Search command.
Console Display #4
Main Menu: Enter command or menu > sea
Searching for potential boot device(s)
This may take several minutes.
To discontinue search, press any key (termination may not be immediate).
Path# Device Path (dec) Device Path (mnem) Device Type
----- ----------------- ------------------ -----------
P0 0/0/1/0.2 extscsi.2 Sequential access media
P1 0/0/2/0.6 intscsia.6 Random access media
P2 0/0/2/1.6 intscsib.6 Random access media
P3 0/1/0/0.8 Random access media
P4 0/12/0/0.3 Random access media
P5 1/10/0/0.4 Random access media
P6 1/12/0/0.0 Random access media
This provides us with an idea of types of devices (Sequential
~ Tape, Random ~ Disk) connected to our system. This information,
combined with the card types, gives us the basic information needed
to configure the system. Note that these devices are not SCSI Multi-LUN
devices; therefore, this output does not show the implied LUN value
of ZERO for each of these devices. The MPE/iX configuration addresses
of these devices would have ".0" appended to them.
One piece of configuration data that is missing is the actual
hardware device Ids. At this time the only source for this information
is the ISL utility, ODE MAPPER2. MAPPER2 is the 64-bit version of
the MAPPER program used for previous HP e3000 platforms. For more
complete information on ODE MAPPER2, please see the MPE/iX System
Software Maintenance Manual for this Release. It is highly recommended
that your configured device Ids match the actual device Ids returned
by ODE MAPPER2. For the purposes of this article we'll
assume some arbitrary but legal device Ids.
The next part of your configuration must be done while the
system is "up" and running MPE/iX.
New Boot Messages for N-Class (and A-Class):
Early in the system boot code, MPE/iX will scan possible hardware locations to determine what I/O adapter cards are present in the system. The code will indicate the presence of I/O adapter cards using "+" or "*". The "+" indicates the presence of a PCI Device with a single PCI function; the "*" indicates the presence of a PCI Device with multiple functions:
ISL> start norecovery MPE/iX launch facility Scanning PCI BUS 0 ++*..++.......................... Scanning PCI BUS 8 ................................ Scanning PCI BUS 10 ................................. Scanning PCI BUS 20 ................................. Scanning PCI BUS 28 +............................... Scanning PCI BUS 40 ................................ Scanning PCI BUS 50 +............................... Scanning PCI BUS 60 *................................ Scanning PCI BUS 80 *............................... Scanning PCI BUS 90 ................................ Scanning PCI BUS A0 ................................ Scanning PCI BUS C0 ................................ Scanning PCI BUS D0 +............................... Scanning PCI BUS E0 +............................... Initialize_genesis - Ver bld1: <<pci 2.1601>> WED, OCT 25, 2000, 2:59:03 PM (y/n)?The messages seen when booting an A-Class system will be an abbreviated form of the above as the A-Class systems have fewer PCI Buses. The remainder of the system boot messages will be the same as seen on existing platforms on current MPE/iX Releases.
Configuring SCSI Devices using SYSGEN on N-Class Systems
The process followed to configure SCSI Devices on these new Device Adapter Cards is the same as the process configuring of SCSI Devices on existing HP e3000 9XX Systems. The main difference is that various path elements represent different hardware components than on existing HP e3000 9XX systems; these new hardware devices require different software drivers. For the following examples we will assume that we are using the same system information presented in the preceding examples. These examples will show the configuration of an internal disk drive (as LDEV 1), an external tape drive (as LDEV 7) and cover the special cases of the System Spooled Printer (LDEV 6) and System Streams Devices (LDEV 10). The configuration of LDEV 20, the System Console, and other Data Communications/Networking hardware devices, will be covered in separate articles in this Communicator. We'll start by configuring LDEV 1 on the internal system disk at path address 0/0/2/0.6.0. Recall from our previous explorations that this path represents a "random access media," e.g. a disk, and that it in on the Core I/O Embedded A5159A (DP HVD). We'll choose the disk Id of HPC2490WD as this is a supported "Fast/Wide SCSI" (HVD) disk (you may use this Id too, though it is recommended that you use the Id obtained from ODE MAPPER2). As with existing HP e3000 systems, you must build up a set of paths by configuring each path element separately starting with the left-most element. To review the hardware path "0/0/2/0.6.0" can be interpreted as:
System Bus Location / Local Bus Number / PCI Device /
PCI Device Function . SCSI Target . SCSI LUN
We start by configuring System Bus Location equal to zero
("0"). We then configure Local Bus Number equal
to zero ("0"), PCI Device equal to two ("2"),
and PCI Function equal to zero ("0"). The System
Bus entry, Local Bus entry and PCI Device entry all have new and unique
configuration identifiers. The configuration of SCSI devices is
accomplished with the same exact steps as are followed in MPE/iX
6.5 on existing HP e3000 systems.
If you were to build a new configuration file for an N-Class
system and wanted the device 0/0/2/0.6.0 to be our LDEV #1 (system/boot
disk), you would issue the following commands in SYSGEN.
io> ap 0 id=pat_ioa_bc
io> ap 0/0 id=pat_pci_bc
io> ap 0/0/2 id=pci_device
io> ap 0/0/2/0 id=A5159A << This is the Device
Adapter Card (ID from Example #1)
io> ap 0/0/2/0.6 id=pseudo __/ pair of entries per stand alone device
\ pair of entries per stand alone device
io> ad 1 path=0/0/2/0.6.0 id=hpc2490wd
or (if LDEV #1 previously existed)
io> md 1 path=0/0/2/0.6.0 id=hpc2490wd
Checking that the Device Adapter Card is properly configured:
io> lp 0/0/2/0 PATH: 0/0/2/0 LDEV: ID: A5159A TYPE: DA PMGR: PCI_SCSI_DAM PMGRPRI: 6 LMGR: MAXIOS: 0If you were to build a new configuration file for an N-Class system, the next step would be to configure LDEV 7. In our previous examples we found a "sequential access media," e.g. "tape" at path address 0/0/1/0.2.0. Recall from our previous explorations that this device is on the Core I/O external SCSI Bus, A5149A (SP LVD/SE). We've chosen to use HPC1553A as this is a supported SE-SCSI DDS-3 Tape drive; you should use the value that matches your Boot Tape device.
(Paths "0" and "0/0" were added in previous example for LDEV #1)
io> ap 0/0/1 id=pci_device
io> ap 0/0/1/0 id=A5149A << This is the Device Adapter Card
io> ap 0/0/1/0.2 id=pseudo __/ pair of entries per stand alone device
\ pair of entries per stand alone device
io> ad 7 path=0/0/1/0.2.0 id=hpc1553B
or (if LDEV #7 previously existed)
io> mp 7 path=0/0/1/0.2.0 id=hpc1553B
Checking that the Device Adapter Card is properly configured:
io> lp 0/0/1/0 PATH: 0/0/1/0 LDEV: ID: A5149A TYPE: DA PMGR: PCI_SCSI_DAM PMGRPRI: 6 LMGR: MAXIOS: 0As in the previous example, PMGR is set to "PCI_SCSI_DAM," which is the correct value. This is how LDEV 7 is configured in CONFNCL1:
LDEV: 7 DEVNAME: OUTDEV: 0 MODE: ID: HPC1553A RSIZE: 128 DEVTYPE: TAPE PATH: 0/0/1/0.6.0 MPETYPE: 24 MPESUBTYPE: 7 CLASS: TAPE TAPE2 DDUMP TAPE1This covers the basics of configuring a single Disk and single Tape; now, on to the special cases. The MPE/iX Operating System requires several logical devices to be present in order to function properly. LDEV 1, LDEV 7 and LDEV 20 are the basic hardware devices that must be present. In addition MPE/iX requires that LDEV 10 be configured as the "Streams" device and that a spooled printer be configured, usually LDEV 6 with Class LP or PP, in order for Jobs to Logon. Neither of these devices has to be physically present but they must be configured. If your system has been factory preloaded, these devices should already be present in configuration files found in the group CONFIG.SYS. Alternately, they should be found in the groups CONFNCL1, CONFNCL2 (N-Class), CONFACL1, and CONFACL2 (A-Class). In order to configure these "virtual" LDEVs you must use a real hardware path up to the Device Adapter, but you do NOT have to have actual LDEV6 and LDEV10 devices physically present. We recommend that these devices be configured with the special Target Ids 16 (sixteen) and 17 (seventeen) so as to not artificially limit the number of devices allowed on a SCSI Bus (the PCI_SCSI_DAM software will allow these normally illegal values for "virtual" LDEVs). New Device IDs have been added to IODFAULT.PUB.SYS to ensure proper configuration of these special devices: LP_PP_ID: use for the System Printer JOBTAPE_ID: use for the Streams device Assuming that LDEV 7 was previously configured at path 0/0/1/0.2.0 as in the previous examples the actual SYSGEN commands to add LDEV 6 and LDEV 10 would be:
io> ap 0/0/1/0.16 id=pseudo
io> ad 6 path=0/0/1/0.16.0 id=lp_pp_id
or (if ldev 6 already defined but not valid or being used)
io> md 6 path=0/0/1/0.16.0 id=lp_pp_id
The streams device (LDEV10) must have OUTDEV parameter set to
an existing spooled device class. In this case LP-PP-ID has a default
class of PP, so that is the value we use for OUTDEV.
io> ap 0/0/1/0.17 id=pseudo
io> ad 10 path=0/0/1/0.17.0 id=jobtape_id outdev=pp
or (if ldev 10 already defined but not valid or being used)
io> md 10 path=0/0/1/0.17.0 id=jobtape_id outdev=pp
From the CONFNCL1 file:
LDEV: 6 DEVNAME: OUTDEV: 0 MODE:
ID: LP_PP_ID RSIZE: 66 DEVTYPE: PP
PATH: 0/0/1/0.16.0 MPETYPE: 32 MPESUBTYPE: 6
CLASS: LP PP
LDEV: 10 DEVNAME: OUTDEV: LP MODE: JA
ID: JOBTAPE_ID RSIZE: 128 DEVTYPE: TAPE
PATH: 0/0/1/0.17.0 MPETYPE: 24 MPESUBTYPE: 2
CLASS: JOB JOBTAPE
From the screen output shown in "Console Display
#4" it can be seen that we have another disk drive at path "1/10/0/0.4".
The MPE/iX SCSI configuration address of this device must include
a SCSI LUN which is implied to be zero since it is not shown. So
our configuration path will be "1/10/0/0.4.0".
In Sysgen you would enter the following commands:
io> ap 1 id=pat_ioa_bc
io> ap 1/10 id=pat_pci_bc
io> ap 1/10/0 id=pci_device
io> ap 1/10/0/0 id=A4800A << This is the Device
Adapter Card (ID from Example #1)
io> ap 1/10/0/0.4 id=pseudo __/ pair of entries per stand alone device
\ pair of entries per stand alone device
io> ad 100 path=1/10/0/0.4.0 id=hpc2490wd
|
PCI-SCSI Device Adapter Cards on HP e3000 N-Class and A-Class Systems |
SCSI Interface and Device Support for N-Class and A-Class HP e3000 |