| United States-English |
|
|
|
![]() |
Communicator e3000 MPE/iX Express 1 Based on Release 7.0: HP e3000 MPE/iX Computer Systems > Chapter 4 PCI-SCSI Device Adapter CardsSCSI Device Configuration Examples for N-Class and A-Class HP e3000 Systems |
|
by Jim Hawkins 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 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.
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):
Proceed to the Information 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.
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.
* Dual Port Cards, presenting two independent SCSI Buses, will have a pair of paths, one for each SCSI Bus. Each such path pair will have the same leading three values, one member of the pair ending in zero (0) and the other in a one (1). (In PCI Bus Architecture terminology, these cards are "multi-function" devices.) As a final check, this pair must be on the same bus/slot number pair. From the information previously gathered from the Information Menu, IO Function, we can see that the system has the following cards connected: Using the information in Table #1 with the output from console display #3 command we can derive the following:
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.
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. 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:
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. 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_bcio> ap 0/0 id=pat_pci_bcio> ap 0/0/2 id=pci_deviceio> 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 deviceio> ad 1 path=0/0/2/0.6.0 id=hpc2490wd \ pair of entries per stand alone device 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/0PATH: 0/0/2/0 LDEV: ID: A5159A TYPE: DAPMGR: PCI_SCSI_DAM PMGRPRI: 6LMGR: MAXIOS: 0 If 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_deviceio> ap 0/0/1/0 id=A5149A << This is the Device Adapter Cardio> ap 0/0/1/0.2 id=pseudo __/ pair of entries per stand alone deviceio> ad 7 path=0/0/1/0.2.0 id=hpc1553B \ pair of entries per stand alone device 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:
As 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: 7CLASS: TAPE TAPE2 DDUMP TAPE1 This 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:
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: 6CLASS: 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: 2CLASS: 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_bcio> ap 1/10 id=pat_pci_bcio> ap 1/10/0 id=pci_deviceio> 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 deviceio> ad 100 path=1/10/0/0.4.0 id=hpc2490wd \ pair of entries per stand alone device |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||