========================== QD21 DISK CONTROLLER ============================= TECHNICAL MANUAL (MSCP COMPATIBLE) QD2151002-00 Rev G June, 1989 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � EMULEX PRODUCT/MANUAL REVISION HISTORY � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 PROM E65x(1), Location U44 旼컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴커 쿛ROM E65x� DESCRIPTION � MANUAL P/N � 쳐컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴캑 쿌,B,C,D � QD21 with � QD2151001-00, � � � optional diagnostics � � � � � � 쿐 and � QD21 with firmware- � QD2151002-00 � 쿪bove � resident diagnostics � � 읕컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴켸 This manual has been extensively revised to incorporate changes to support the Firmware-Resident Diagnostics (F.R.D.) that have been added to the Revision E controller firmware PROM. Due to the nature of these firmware changes, a QD21 with a Revision E and above firmware PROM will no longer operate with previously supplied diagnostic software. In addition, some of the ODT functions (NOVRAM loading commands and Format Drive command) previously available are no longer available. All of the functionality that was provided by software diagnostics and ODT commands has been incorporated in F.R.D. Be certain that your manual is appropriate for the revision level of your controller firmware, as noted in the table above. This firmware is easily identified by the label at U44. WARNING This equipment generates, uses and can radiate radio frequency energy, and if not installed and used in accordance with the technical manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of Federal Communications Commission (FCC) Rules, which are designed to provide reasonable protection against such interference when operating in a commercial environment. Operation of this equipment in a residential area is likely to cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. Copyright (c) 1988 Emulex Corporation The information in this manual is for information purposes and is subject to change without notice. Emulex Corporation assumes no responsibility for any errors which may appear in the manual. Printed in U.S.A. (1) The small x indicates the PROM's revision level letter: A, B, C, etc. 旼컴컴컴컴컴컴컴컴컴� � TABLE OF CONTENTS � 읕컴컴컴컴컴컴컴컴컴� ONE INTRODUCTION ---------------------------- 1.1 OVERVIEW 1.2 SUBSYSTEM OVERVIEW 1.2.1 Mass Storage Control Protocol (MSCP) 1.3 PHYSICAL ORGANIZATION OVERVIEW 1.4 SUBSYSTEM MODELS 1.5 FEATURES 1.5.1 Microprocessor Design 1.5.2 Firmware-Resident Diagnostics 1.5.3 Custom Configuration Capability 1.5.4 Self-Test 1.5.5 Error Control 1.5.6 Host-Initiated Bad Block Replacement 1.5.7 Seek Optimization 1.5.8 Command Buffer 1.5.9 Adaptive DMA 1.5.10 Block-Mode DMA 1.5.11 Twenty-Two-Bit Addressing 1.6 COMPATIBILITY 1.6.1 Operating Systems 1.6.2 Hardware TWO CONTROLLER SPECIFICATION ---------------------------------------- 2.1 OVERVIEW 2.2 GENERAL SPECIFICATION 2.3 ENVIRONMENTAL SPECIFICATION 2.4 PHYSICAL SPECIFICATION 2.5 ELECTRICAL SPECIFICATION THREE PLANNING THE INSTALLATION ----------------------------------------- 3.1 OVERVIEW 3.2 MSCP SUBSYSTEM CONFIGURATION 3.2.1 Architecture 3.2.2 Peripheral Numbering 3.2.3 Peripheral Capacities 3.3 A DEC MSCP SUBSYSTEM 3.4 THE QD21 MSCP SUBSYSTEM 3.4.1 Logical Unit Numbers 3.4.2 QD21 MSCP Subsystem Logical Configuration 3.4.2.1 Logical Devices 3.4.2.2 Device Numbers 3.5 OPERATING SYSTEMS, DEVICE AND VECTOR ADDRESSES 3.5.1 RSTS/E Operating Systems (V8.0 and above) 3.5.1.1 Adding MSCP Support 3.5.2 Operating Systems (V5.1 and above) 3.5.2.1 Installing a Single MSCP Controller 3.5.2.2 Installing Multiple MSCP Controllers 3.5.2.3 Disk Partitioning 3.5.3 RSX-11M Operating Systems (V4.0 and above) 3.5.3.1 Installing a Single MSCP Controller 3.5.3.2 Installing Multiple MSCP Controllers 3.5.4 RSX-11-MPlus Operating Systems (V2.1 and above) 3.5.4.1 Installing a Single MSCP Controller 3.5.4.2 Installing Multiple MSCP Controllers 3.5.5 MicroVMS Operating Systems 3.5.6 Ultrix-11 Operating Systems (V3.0 and above) 3.5.6.1 Sysgen 3.5.6.2 Special Files 3.5.6.3 Newfs 3.5.6.4 Volcopy 3.5.6.5 Copying a Bootstrap 3.5.7 Ultrix-32 Operating Systems 3.5.7.1 The Kernel 3.5.7.2 Special Files 3.5.7.3 Autoconfigure 3.5.7.4 Disk Partitions 3.5.7.5 Disk Partition Modifications 3.5.7.6 Default Partition Modifications 3.5.7.7 Newfs 3.5.7.8 Suggestions/Warnings FOUR INSTALLATION ---------------------------- 4.1 OVERVIEW 4.1.1 Subsystem Configurations 4.1.2 Dip Switch Type 4.1.3 Maintaining FCC Class A Compliance 4.2 INSPECTION 4.3 DISK CONTROLLER SETUP 4.3.1 Disk Controller Bus Address 4.3.2 Interrupt Vector Address 4.3.3 Options 4.3.3.1 Automatic Bootstrapping 4.3.3.2 MSCP Device Number 4.3.3.2.1 Logical Unit to Boot From 4.3.3.2.2 First Logical Unit Number for an Alternate Address 4.3.3.3 22-Bit Memory Addressing 4.3.3.4 DMA Burst Delay 4.3.3.5 DMA Adaptive Mode 4.4 PHYSICAL INSTALLATION 4.4.1 System Preparation 4.4.2 Slot Selection 4.4.3 Mounting 4.5 ESDI DISK DRIVE PREPARATION 4.5.1 Drive Placement 4.5.2 Sectoring 4.5.3 Drive Numbering 4.5.4 Spindle Motor Spin-up 4.5.5 Termination 4.6 CABLING 4.7 NOVRAM LOADING, DISK FORMATTING, AND TESTING 4.7.1 F.R.D. Conventions 4.7.2 Starting F.R.D. on a MicroVAX I 4.7.3 Starting F.R.D. on a MicroVAX II and a GPX Workstation 4.7.4 Starting F.R.D. on an LSI-11 System 4.7.5 Terminating F.R.D 4.8 F.R.D. OPTIONS 4.8.1 Option 1 - Self-test Loop 4.8.2 Option 2 - Format 4.8.3 Option 3 - Verify 4.8.4 Option 4 - Format and Verify 4.8.5 Option 5 - Data Reliability Test 4.8.6 Option 6 - Format, Verify, and Data Reliability Test 4.8.7 Option 7 - Read Only Test 4.8.8 Option 8 - List Known Units 4.8.9 Option 9 - Replace Block 4.8.10 Option 10 - Display NOVRAM 4.8.11 Option 11 - Edit/Load NOVRAM 4.9 DRIVE CONFIGURATION PARAMETERS 4.9.1 Type Code 4.9.2 Number of Units of this Type 4.9.3 Number of Sectors per Track 4.9.4 Number of Heads 4.9.5 Number of Cylinders 4.9.6 Number of Spare Sectors per Track 4.9.7 Number of Alternate Cylinders 4.9.8 Configuration Bits 4.9.9 Split Code 4.9.10 Cylinder Offset 4.9.11 Starting Head Offset 4.9.12 Removable Media 4.9.13 Gap 0, 1, and 2 Parameters 4.9.14 Spiral Offset 4.10 OPERATION 4.10.1 Indicators FIVE TROUBLESHOOTING ------------------------------- 5.1 OVERVIEW 5.2 SERVICE 5.3 FAULT ISOLATION PROCEDURE 5.4 POWER-UP SELF-DIAGNOSTIC 5.5 FATAL ERROR CODES SIX DEVICE REGISTERS AND PROGRAMMING ------------------------------------------------ 6.1 OVERVIEW 6.2 OVERVIEW OF MSCP SUBSYSTEM 6.3 PROGRAMMING 6.3.1 MSCP Command Support 6.3.1.1 Minimal Disk Subset 6.3.1.2 Diagnostic and Utility Protocol (DUP) 6.4 REGISTERS 6.5 BOOTSTRAP COMMAND SEVEN FUNCTIONAL DESCRIPTION -------------------------------------- 7.1 OVERVIEW 7.2 QD21 DISK CONTROLLER ARCHITECTURE EIGHT INTERFACES -------------------------- 8.1 OVERVIEW 8.2 LSI-11 BUS INTERFACE 8.2.1 Interrupt Priority Level 8.2.2 Register Address 8.2.3 DMA Operations 8.2.3 Scatter/Gather 8.3 QD21 ESDI DISK DRIVE INTERFACE 8.4 FRONT PANEL INTERFACE APPENDICES A AUTOCONFIGURE, CSR AND VECTOR ADDRESSES ------------------------------------------------------- A.1 Overview A.2 Determining the CSR Address for Use With Autoconfigure A.3 Determining the Vector Address for Use With Autoconfigure A.4 A System Configuration Example B PROM REMOVAL AND REPLACEMENT -------------------------------------------- B.1 Overview B.2 Exchanging Proms C DISK DRIVE CONFIGURATION PARAMETERS --------------------------------------------------- C.1 Overview C.2 Parameter Values C.3 Recommended Drive Options C.3.1 Setting the Switches on the CDC Wren III LIST OF FIGURES --------------- 1-1 QD21 Subsystem Configuration 1-2 QD21 Disk Controller 1-3 Sales Order Example 2-1 QD21 Disk Controller Dimensions 3-1 DEC MSCP Subsystem Logical and Physical Configuration 3-2 QD21 Subsystem Logical and Physical Configuration 3-3 Sample SHOW CONFIGURATION 3-4 CONFIGURE Command Listing 4-1 QD21 Configuration Reference Sheet 4-2 Switch Setting Example 4-3 QD21 Disk Controller Assembly 4-4 Drive Cabling 5-1 Fault Isolation Chart 7-1 QD21 Block Diagram 8-1 Control Pin/Signal Assignments at ESDI Disk Drive Interface (Connector J1) 8-2 Data Pin/Signal Assignments at ESDI Disk Drive Interface (Connector J2 or J5) 8-3 Status and Control Interface C-1 Setting the Switches on the Wren III LIST OF TABLES -------------- 1-1 Basic Contents 1-2 QD21 Options 2-1 QD21 General Specifications 2-2 QD21 Environmental Specifications 2-3 QD21 Physical Specifications 2-4 QD21 Electrical Specifications 3-1 Subsystem Configuration Example 3-2 Device Names 4-1 QD21 Switch Definitions and Factory Configuration 4-2 QD21 Jumper Definitions and Factory Configuration 4-3 Controller Address Switch Settings 4-4 Bootstrap MSCP Device Number 4-5 MSCP Device Number for the First Drive Supported by a QD21 at an Alternate Address 4-6 QD21 Internal Cabling Kit (P/N QD2113001) 4-7 Interface and Cable Components 4-8 MicroVAX Offsets 4-9 LSI-11 Offsets 4-10 Configuration Bit Values in Decimal 5-1 Flow Chart Symbol Definitions 5-2 LED Error Codes 5-3 MSCP Fatal Error Codes Used by the QD21 5-4 Fatal Error Codes 6-1 QD21 and SA Registers 8-1 LSI-11 Bus Interface Pin Assignments 8-2 Control and Status Interface Pin Function Description A-1 SYSGEN Device Table A-2 Priority Ranking for Floating Vector Addresses A-3 CSR and Vector Address Example A-4 Floating CSR Address Assignment Example C-1 Drive Configuration Parameter Values C-2 Drive Option Settings C-3 CDC Wren III Switch Settings 旼컴컴컴컴컴컴컴컴컴컴컴컴� � Section 1 INTRODUCTION � 읕컴컴컴컴컴컴컴컴컴컴컴컴� 1.1 Overview -------------- The QD21 Disk Controller, designed and manufactured by Emulex Corporation, is a Mass Storage Control Protocol (MSCP) compatible controller that interfaces with Enhanced Small Device Interface (ESDI) disk drives. This manual is designed to help you install and use your QD21 Disk Controller. It assumes that you have some knowledge of hardware configuration, LSI-11 architecture and terminology, and interpretations of error messages and device register contents. The contents of the eight sections and three appendices are described as follows: Section 1 General Description: This section contains an overview of the QD21 Disk Controller. Section 2 Controller Specification: This section contains the specification for the QD21 Disk Controller. Section 3 Planning the Installation: This section contains the information necessary to plan your installation, including MSCP subsystem and operating system considerations. Section 4 Installation: This section contains the information needed to set up and physically install the controller, including switch settings and cabling. It also describes the firmware-resident diagnostics and contains instructions for loading drive configuration parameters into the NOVRAM. Section 5 Troubleshooting: This section describes fault isolation procedures that can be used to pinpoint trouble spots. Section 6 Registers and Programming: This section describes the QD21's LSI-11 bus registers and presents an overview of the Mass Storage Control Protocol (MSCP). Section 7 Functional Description: This section describes the controller architecture. Section 8 Interfaces: This section describes the controller LSI-11 bus and ESDI interfaces. Appendix A Autoconfigure: This appendix describes the DEC algorithm for the assignment of CSR addresses and vector addresses. Appendix B PROM Removal and Replacement: This appendix contains instructions to remove and replace the firmware so that the user can upgrade the QD21 Disk Controller in the field. Appendix C Disk Drive Configuration Parameters: This appendix contains configuration parameters for supported ESDI disk drives. 1.2 Subsystem Overview ------------------------ The QD21 Disk Controller connects high-capacity mass storage peripherals to the LSI-11 bus on computers manufactured by Digital Equipment Corporation (DEC). The QD21 implements DEC's Mass Storage Control Protocol (MSCP) to provide a software-transparent interface for the host DEC computer. To provide traditional Emulex flexibility in peripheral selection, the QD21 uses the industry standard Enhanced Small Device Interface (ESDI) interface as its peripheral interface. The QD21 supports the magnetic disk drive and serial options of ESDI. For more information on the QD21's ESDI interface, see subsection 8.1.3. 1.2.1 Mass Storage Control Protocol (MSCP) -------------------------------------------- MSCP is a software interface designed to lower the host computer's mass storage overhead by offloading much of the work associated with file management into an intelligent mass storage subsystem. In concert with ESDI compatible peripherals, the QD21 provides just such a subsystem. The QD21 relieves the host CPU of many file maintenance tasks. The QD21 Disk Controller performs these MSCP functions: error checking and correction, bad block replacement, seek optimization, command prioritizing and ordering, and data mapping. This last feature is, perhaps, the most important. This feature allows the host computer's operating system software to store data in logical blocks that are identified by simple logical block numbers (LBNs). Thus, the host does not need to have detailed knowledge of the peripheral's geometry (cylinders, tracks, sectors, etc.). This feature also makes autoconfiguration a simple matter. During system start-up, the host operating system queries the subsystem to find its capacity (the number of logical blocks that the subsystem can store). Because the host operating system does not need to have detailed knowledge of its mass storage subsystem, the complexity of the operating system itself has been reduced. This reduction comes about because only one or two software modules are required to allow many different subsystems to be connected to a host. 1.3 Physical Organization Overview ------------------------------------ The QD21 Disk Controller is a modular, microprocessor-based disk controller that connects directly to the host computer's Q-bus backplane. The microprocessor architecture ensures excellent reliability and compactness. The QD21 is contained on a single dual-wide printed circuit board assembly (PCBA) that plugs directly into a Q-bus backplane slot. The QD21 supports up to two physical or four logical disk drives. Aggregate data storage capacities are limited only by the capacities of the peripherals. Figure 1-1 shows one possible ESDI configuration. 旼컴컴커 ESDI (DATA) 旼컴컴컴커 � �<컴컴컴컴컴컴컴�>� ESDI � � � ESDI (CONTROL) � DISK � 旼컴컴� LSI-11 BUS � �<컴컴컴컴컴쩡컴�>� DRIVE � � CPU �<袴袴袴袴袴>� QD21 � � 읕컴컴컴켸 읕컴컴� � � � 旼컴컴컴커 � � 읕컴�>� ESDI � � � � DISK � � �<컴컴컴컴컴컴컴�>� DRIVE � 읕컴컴켸 ESDI (DATA) 읕컴컴컴켸 Figure 1-1. QD21 Subsystem Configuration ========================================= 1.4 Subsystem Models ---------------------- The QD21 Disk Controller, with appropriate peripherals, provides a DEC MSCP-compatible mass storage subsystem. The QD21 is pictured in Figure 1-2. The QD21 is identified by a top level assembly tag that is glued to the 8031 microprocessor chip on the PWB. The QD21 top level assembly number is given in Table 1-1 along with the part numbers of the items that are delivered with the QD21. Table 1-1. Basic Contents 旼컴컴쩡컴컴쩡컴컴컴컴컴컴컴컴컴컴컴컴쩡컴컴컴컴컴컴커 � Itm � Qty � Description � Part Number � 쳐컴컴탠컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴탠컴컴컴컴컴컴캑 � 1 � 1 � QD21 Disk Controller � QD2110202-00 � � 2 � 1 � 22-Bit Addressing Kit � QD0113002-00 � � 3 � 1 � QD21 Technical Manual � QD2151002-00 � 읕컴컴좔컴컴좔컴컴컴컴컴컴컴컴컴컴컴컴좔컴컴컴컴컴컴켸 Options are specified as separate line items on a sales order. An example of an actual sales order is shown in Figure 1-3. Itm � Qty � Model Number � Comment/Description 컴컴탠컴컴탠컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1 � 1 � QD21 � Disk Controller implementing � � � DEC MSCP with ESDI drives Figure 1-3. Sales Order Example ================================ 1.5 Features -------------- The following features enhance the usefulness of the QD21 Disk Controller. 1.5.1 Microprocessor Design ----------------------------- The QD21 design incorporates an eight-bit, high-performance CMOS microprocessor to perform all controller functions. The microprocessor approach provides a reduced component count, high reliability, easy maintainability, and the microprogramming flexibility that allows MSCP to be implemented without expensive, dedicated hardware. 1.5.2 Firmware Resident Diagnostics ------------------------------------- The QD21 disk controller firmware incorporates a self-contained set of disk preparation and diagnostic utilities. These utilities are contained in QD21 Revision E and above firmware. Controllers with this firmware are easily identified by a silver tag labeled with the top assembly number QD2110201-00E. These utilities allow the user to communicate directly with the QD21 via a firmware resident terminal driver that is compatible with either CRT or hardcopy devices connected to an LSI-11 or MicroVAX console port. These firmware-resident diagnostics (F.R.D.) provide several important disk preparation functions, including the ability to: o Configure the controller NOVRAM o Format the drive o Test the disk surface and replace defective blocks, and o Perform reliability testing of the attached disk subsystem. 1.5.3 Custom Configuration Capability --------------------------------------- An on-board NOVRAM can be programmed for two independent physical drive configurations. Using the firmware-resident utilities, you can control drive parameters such as gap size, soft or hard sectoring, and the number of sectors per track. 1.5.4 Automatic Drive Configuration ------------------------------------- This feature allows you to take advantage of the drive configuration information available from the attached ESDI drive to set the drive parameters. You can configure the QD21 to use this information instead of entering the parameters manually. This feature supports both hard and soft sector formats. 1.5.5 Self-Test ----------------- The QD21 incorporates an internal self-test routine which exercises all parts of the microprocessor, the on-board memory, the buffer controller, the disk formatter chip, and the Host Adapter Controller (HAC). Although this test does not completely test all circuitry, successful execution indicates a very high probability that the disk controller is operational. If the QD21 detects an error during self-test, it leaves three light-emitting diodes (LEDs) ON and sets an error bit in the Status and Address (SA) register (base address plus 2) 1.5.6 Error Control --------------------- The disk controller presents error-free media to the operating system by correcting soft errors and retrying operations without intervention by the host 1.5.7 Host-Initiated Bad Block Replacement -------------------------------------------- The QD21 uses DEC-compatible host initiated bad block replacement to dynamically replace any defective blocks that occur during the life of the system. For maximum reliability, the QD21 reports even corrected single bit errors as candidates for replacement. 1.5.8 Media Defect List Management ------------------------------------ During format operations, the QD21 replaces all blocks on the disk that are labeled bad in the Manufacturer's Defect List. After formatting, the firmware- resident utilities can be used to test the entire disk surface with four worst- case data patterns and replace any pattern-sensitive blocks not found by the manufacturer. QD21 supports both 256- and 512-byte defect list formats. 1.5.9 Seek Optimization ------------------------- The QD21 is able to pool the various seeks that need to be performed and determine the most efficient order in which to do them. This is an especially important feature in heavily loaded systems. The disk controller's ability to arrange seeks in the optimum order saves a great deal of time and makes the entire system more efficient. 1.5.10 Command Buffer ----------------------- The QD21 contains a buffer that is able to store 13 MSCP commands. This large buffer allows the subsystem to achieve a higher throughput and to operate at a very efficient level. 1.5.11 Adaptive DMA --------------------- During each DMA data transfer burst, the QD21 monitors the LSI-11 bus for other pending DMA requests and suspends its own DMA activity to permit other DMA transfers to occur. The host processor programs the DMA burst length during the MSCP initialization sequence or the QD21 defaults to 16 words per burst. Because of these adaptive DMA techniques, the QD21 ensures that CPU functions, including interrupt servicing, are not locked out for excessive periods of time by high-speed disk transfers. The QD21 firmware design includes a DMA burst delay of either 4 or 8 microseconds to avoid data late conditions (SW2-7). In addition, the QD21 allows you to modify its DMA operations by disabling the adaptive DMA (SW2-8 ON) and defaulting to burst transfers of 8 words or less. 1.5.12 Block-Mode DMA ----------------------- The QD21 supports block-mode DMA for accessing memory. In this mode, the initial address of the data is transmitted, followed by a burst of up to 16 words of data. The memory address is automatically incremented to accommodate this burst. Block mode transfers considerably reduce the overhead associated with DMA operations. 1.5.13 Twenty-Two-Bit Addressing ---------------------------------- The QD21 supports the 22-bit addressing capability of the extended LSI-11 bus. 1.6 Compatibility ------------------- This subsection describes the compatibility of operating systems and hardware. 1.6.1 Operating Systems ------------------------- The QD21 implements MSCP. Emulex supports its implementation of MSCP beginning with the indicated version of the following DEC operating systems: Operating � System � Version 컴컴컴컴컴컴컵컴컴컴컴 Micro/VMS � 4.0 RSTS/E � 8.0 RSX-11M � 4.1 RSX-11M-PLUS � 2.1 RT-11 � 5.1 Ultrix-11 � 3.0 Ultrix-32m � 1.1 1.6.2 Hardware Compatibility ------------------------------ The QD21 Disk Controller complies with DEC LSI-11 bus protocol, and it directly supports 22-bit addressing and block-mode DMA. The QD21 also supports scatter- write and gather-read operations on the MicroVAX I. The QD21 supports the serial mode implementation of the ESDI interface on magnetic disk drives that have clocks up to 15 megaHertz. Emulex has qualified the following disk drives for QD21 support: o CDC Wren III (hard-sectored) o Fujitsu M2246E (soft-sectored) o Hitachi DK512-17 (soft-sectored) o Maxtor EXT-4175 (hard-sectored) o Maxtor EXT-4380 (soft-sectored) o Maxtor XT-4380E (hard-sectored, soft-sectored) o Micropolis 1350 (hard-sectored) o Micropolis 1558 (hard-sectored, soft-sectored) o Siemens 1300 (hard-sectored) The disk drives supported by the QD21 are not media compatible with comparable DEC MSCP products; this is not a problem, however, because of the fixed nature of most DEC drives. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � Section 2 CONTROLLER SPECIFICATION � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 2.1 Overview -------------- This section contains the general, environmental, physical, electrical, and port specifications for the QD21 Disk Controller. Subsection � Title 컴컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴컴 1.2 � General Specification 1.3 � Environmental Specification 1.4 � Physical Specification 1.5 � Electrical Specification 2.2 General Specification --------------------------- Table 2-1 contains a general specification for the QD21 Disk Controller. Table 2-1. QD21 General Specifications 旼컴컴컴컴컴컴컴컴컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � Parameter � Description � 쳐컴컴컴컴컴컴컴컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿑UNCTION 쿛roviding mass data storage to Digital Equipment � � 쿎orporation (DEC) computers that use the LSI-11 � � � � � Logical CPU Interface 쿐mulates DEC's Mass Storage Control Protocol � � � � � Diagnostics 쿐mbedded diagnostic � � � � � Operating System 쿘icro/VMS V4.0 and above � � Compatibility 쿝STE/S V8.0 and above � � 쿝SX-11M V4.1 and above � � 쿝SX-11M-PLUS V2.1 and above � � 쿝T-11 V5.1 and above � � 쿢ltrix-11 V3.0 and above � � 쿢ltrix-32m V1.1 and above � � � � � CPU I/O Technique 쿏irect Memory Access (DMA), including adaptive � � 퀃echniques and block mode; supports scatter-write� � 쿪nd gather-read operations on the MicroVAX I � � � � 쿔NTERFACE � � � � � � CPU Interface 쿐xtended LSI-11 bus interface � � � � � Device Base Address � � � Standard �17772150 � � Alternates �17772154 � � �17760334 � � �17760340 � � �17760344 � � �17760350 � � �17760354 � � �17760360 � � � � � Vector Address 쿛rogrammable � � � � � Priority Level 쿍R4 � � � � � Bus Loading �1 DC Load, 2.5 AC Loads � � � � � Peripheral Interface 쿐SDI � � � � � Number of Physical �2 � � Disk Drives Supported� � � � � � Drive Sectoring 쿓ard or Soft Sectored � � � � � Interface Cables �34-line control cable (daisy-chain), � � 쿺aximum 10 ft (3 m) � � �20-line data cables (radial), � � 쿺aximum 10 ft (3 m) � � � � � Disk Drive Mode 쿞erial � � � � � Firmware Diagnostic � � � Host Console � � � � � � LSI-11 쿏LV11J or Processor-resident console interface � � � � � MicroVAX 쿛rocessor-resident console port � 읕컴컴컴컴컴컴컴컴컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 2.3 Environmental Specification --------------------------------- Table 2-2 contains the environmental specifications for the QD21 Disk Controller. Table 2-2. QD21 Environmental Specifications 旼컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � Parameter � Description � 쳐컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿚PERATING � 10�C (50�F) to 40�C (104�F), where maximum � 쿟EMPERATURE � temperature is reduced 1.8�C per 1000 � � � meters (1�F per 1000 feet) altitude � � � � 쿝ELATIVE HUMIDITY � 10% to 90% with a maximum wet bulb of 28�C � � � (82�F) and a minimum dewpoint of 2�C (3.6�F) � � � � 쿎OOLING � 6 cubic feet per minute � � � � 쿓EAT DISSIPATION � 45 BTU per hour � 읕컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 2.4 Physical Specification ---------------------------- Table 2-3 contains the physical specifications for the QD21 Disk Controller. Table 2-3. QD21 Physical Specifications 旼컴컴컴컴컴컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � Parameter � Description � 쳐컴컴컴컴컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � PACKAGING � Single, dual-wide, four-layer PCBA � � � � � Dimensions � 5.186 by 8.70 inches � � � 13.172 by 22.09 centimeters � � � (see Figure 2-1) � � � � � Shipping Weight � 3 pounds � 읕컴컴컴컴컴컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 2.5 Electrical Specification ------------------------------ Table 2-4 lists and describes the electrical specification for the QD21 Disk Controller. Table 2-4. QD21 Electrical Specification 旼컴컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � Parameter � Description � 쳐컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � POWER � 5 Vdc + 5%, 2.6 amperes (A) � 읕컴컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쳐컴컴컴� 5.186 inches 컴컴컴� (13.172 cm) 旼컴컴컴컴컴컴컴컴컴컴컴컴컴커 � � � � � � � � � � � � � � � � � � � � � 8.700 inches � � (22.098 cm) � � � � � � � � � � � � � � � � � � � � � � � � 읏 悶 粕 � 읕컴컴컴컴컴켸읕컴컴컴컴컴켸 � Figure 2-1. QD21 Disk Controller Dimensions ============================================ 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � Section 3 PLANNING THE INSTALLATION � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 3.1 Overview -------------- This section is designed to help you plan the installation of your QD21 Disk Controller. Taking a few minutes and planning the configuration of your subsystem before beginning its installation should result in a smoother installation with less system down time. This section contains QD21 application examples and configuration procedures. The subsections are listed in the following table: Subsection � Title 컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 3.2 � MSCP Subsystem Configuration 3.3 � A DEC MSCP Subsystem 3.4 � The QD21 MSCP Subsystem 3.5 � Operating Systems, Device and Vector Addresses 3.2 MSCP Subsystem Configuration ---------------------------------- The following paragraphs describe MSCP Subsystem concepts, including architecture, unit numbering, capacities, and related concepts. 3.2.1 Architecture -------------------- MSCP is a protocol designed by DEC for mass storage subsystems using Digital Storage Architecture (DSA). In a MSCP mass storage subsystem, DSA comprises three functional and physical layers: o Host Layer. An MSCP class-driver in the host system receives requests from the operating system and then relays data and commands to the controller in MSCP message packets. o Controller Layer. The MSCP controller communicates with both the host layer and the mass storage layer. The controller transmits MSCP message packets to and from the host MSCP class-driver and performs data-handling functions for the mass storage devices. The QD21 functions as the controller layer. o Mass Storage Layer. The mass storage peripheral devices communicate with the MSCP controller and send or receive data as specified by the MSCP controller. MSCP defines the form of the message packets that are exchanged by the host and the MSCP controller. The QD21 implements MSCP in mass storage subsystems using ESDI as the peripheral interface. 3.2.2 Peripheral Numbering ---------------------------- Each MSCP peripheral on the system is identified to the operating system by an MSCP device name. An MSCP device name consists of a device class identifier and a unit number. The device class is indicated by a two-letter prefix; MSCP disk devices are indicated by the prefix DU. With the exception of MicroVMS systems, DEC operating systems require that all MSCP peripherals on a system have different MSCP device numbers, even if they are managed by separate MSCP controllers at separate LSI-11 bus device addresses. For example, under RSX-11M-PLUS, if there are three peripherals on the first MSCP controller (at 772150), then the first peripheral on the second MSCP controller (in floating CSR address space) is numbered DU3. 3.2.3 Peripheral Capacities ----------------------------- The capacity of peripherals in an MSCP subsystem is measured in logical blocks. Each logical block contains 512 bytes of data. The MSCP controller can report the capacity of a peripheral to the operating system. For example, a disk drive supported by the QD21 is able to store 280731 logical blocks. 3.3 A DEC MSCP Subsystem -------------------------- Figure 3-1 shows the organization of a typical DEC MSCP subsystem for the LSI-11 bus. The MSCP host and controller functions are combined in a single piece of hardware, in this example the DEC RQDX3. The RQDX3 supports RD51, RD52, or RD53 hard disk drives and the RX50 5.25-inch floppy drive. The RQDX3 plugs directly into the LSI-11 bus and is attached to disk drives via a disk- drive-native interface. 旼컴컴컴� 旼컴컴� LSI-11 BUS 旼컴컴컴� NATIVE � DRIVE � � CPU �<袴袴袴袴袴>� RQDX3 �<컴컴컴컴쩡컴>� DU0 � 읕컴컴� 읕컴컴컴� � 읕컴컴컴� � 旼컴컴컴� � � DRIVE � 쳐컴>� DU1 � � 읕컴컴컴� � 旼컴컴컴� � � DRIVE � 읕컴>� DU2 � 읕컴컴컴� Figure 3-1. DEC MSCP Subsystem Logical and Physical Configuration ================================================================== 3.4 The QD21 Subsystem -------------------------- Figure 3-2 illustrates a typical QD21 MSCP subsystem. As with the DEC implementation, the QD21 is connected directly to the LSI-11 bus. The QD21, however, uses the ESDI peripheral interface to communicate with one or two disk drives. 旼컴컴커 ESDI (DATA) 旼컴컴컴커 � �<컴컴컴컴컴컴컴�>� ESDI � � � ESDI (CONTROL) � DISK � 旼컴컴� LSI-11 BUS � �<컴컴컴컴컴쩡컴�>� DRIVE � � � � � � � DU0 � � CPU �<袴袴袴袴袴>� QD21 � � 읕컴컴컴켸 � � � � � 旼컴컴컴커 읕컴컴� � � � � ESDI � � � 읕컴�>� DISK � � � ESDI (DATA) � DRIVE � � �<컴컴컴컴컴컴컴�>� DU1 � 읕컴컴켸 읕컴컴컴켸 Figure 3-2. QD21 Subsystem Logical and Physical Configuration ================================================================ The MSCP subsystem provided by the QD21 is essentially analogous to the DEC MSCP subsystem. As in the DEC subsystem, the QD21 MSCP controller connects directly to the LSI-11 bus. As an MSCP controller, the QD21 receives requests from the host, optimizes the requests, generates ESDI commands to perform the operations, transfers data to and from the host, transfers data to and from the device, and buffers data as necessary. When the command is complete, the controller sends a response to the host. The QD21 also performs all of the functions of the peripheral controller, including serialization and deserialization of data. The QD21 connects to the peripherals it supports via the ESDI interface. 3.4.1 Logical Unit Numbers ---------------------------- As noted in section 3.2.2, most DEC operating systems do not allow any MSCP disk devices on one system to have the same unit number, even though they may be controlled by separate MSCP controllers at different base addresses. DEC MSCP-type drives can accept unit identification plugs that define addresses from 0 to 255. Disk drives controlled by the QD21 do not have this flexibility; the QD21 can detect only two unique drive addresses at its ESDI interface: 1 and 2. To prevent a unit-number conflict between the QD21's drives and another MSCP controller's drives, the QD21 employs switches to change the drive logical unit number that is reported to the operating system. Example 3-1: An MSCP controller at a standard base address supports four disk drives; a QD21 at an alternate base address supports two disk drives. An offset of 4 is specified for the QD21. This causes the QD21 disk with address 1 to be reported to the operating system as logical unit number (LUN) 4. The QD21 disk 2 is reported as LUN 5. The offset for the logical unit number is specified by using switches SW1-2 through SW1-4 on the QD21. See subsection 4.3.3.2.2 for switch setting information. 3.4.2 QD21 Subsystem Logical Configuration ---------------------------------------------- This subsection explains the algorithm used by the QD21 to map logical MSCP peripherals onto the physical disk drives provided by the QD21 subsystem. 3.4.2.1 Logical Devices ------------------------- The phrase "logical MSCP disk drive" refers to the disk drive as it appears to the operating system. That is, the operating system associates a disk drive of known type (in this case, an MSCP disk drive) with a unit number and a capacity. The QD21 MSCP controller presents that information to the operating system after initialization on command. Because the MSCP controller is responsible for establishing the relationship between unit number and capacity, it is possible for the controller to divide its physical disk drives into more than one logical unit. For example, if a physical disk drive has a capacity of 584,000 blocks, the MSCP controller can divide that capacity into two parts of 292,000 blocks each. (Each part may have a different capacity.) Each part is then assigned a separate unit number, and the unit number and capacity of each part is presented to the operating system. The operating system then sees the two parts as separate disk drives, even though the data is actually stored on the same physical drive. The two parts are called logical disk drives, and the numbers that identify them are called MSCP unit numbers. A drive configuration that supports multiple logical units is specified by the data that is stored in the configuration Nonvolatile Random Access Memory (NOVRAM). Information for programming the configuration NOVRAM is given in subsections (4.7, 4.8, and 4.9). The field that causes a drive to be divided into multiple logical units is called the Split Code. There are four types of split codes: no split, cylinder split, head split, and reverse head split: o When no split is specified, the entire physical drive is one logical drive o Cylinder split codes divide a physical drive by cylinders. A Starting Cylinder Offset field in the NOVRAM specifies the first cylinder of the second logical drive. Alternate cylinders are divided evenly between drives. For example, a Maxtor 4380, which has 1224 cylinders might be divided so that the first logical unit is assigned cylinders 0 through 611 and the second logical unit assigned 612 through 1224. In this example, the Starting Cylinder Offset has a value of 612. o Head split codes divide the drive by data heads. A Starting Head Offset field in the NOVRAM specifies the first head of the second logical drive. When the drive is split by data heads, each logical drive has its own platter(s); consequently, the lower blocks of one logical drive are in the same physical cylinder as the lower blocks of the other logical drive. For example, a Maxtor 4380 with 15 heads might be divided so that the first logical unit is assigned heads 0 through 7, and the second logical unit is assigned heads 8 through 14. The Starting Head Offset has a value of 8. o Reverse head split codes also divide the drive by data heads, but assign the lower numbered heads to drive 1 and the higher numbered heads to drive 0. If you entered a reverse split code for the previous Maxtor 4380 example, the first logical unit is assigned heads 8 through 14 and the second logical unit is assigned heads 0 through 7. The Starting Head Offset has a value of 8. The head splitting technique has a performance advantage over the cylinder method. Typically, most disk accesses are made in the lower cylinders of a disk because many system-oriented files are located there, including the drive's directory. Because the low (and high) cylinders are vertically aligned between the two logical drives when the head splitting technique is used, switching between head-split logical drives requires less head movement than switching between cylinder-split drives. 3.4.2.2 Device Numbers ------------------------ The drives supported by the QD21 are assigned MSCP device names by the operating system. As described in subsection 3.2.2, an MSCP device name consists of a device class prefix and a device unit number. Drives are assigned MSCP device numbers beginning with zero (0). The conventions for numbering multiple MSCP drives vary by operating system. Under RSX-11M, RSX-11M-PLUS and RT-11, DU0 is assigned to the first drive on the first MSCP controller, where "first" means the controller located at the standard base address. Unit number 1 would be the second drive on the first controller, etc. If there are two MSCP controllers on the system, the units installed on the second begin numbering at n+1, where n equals the highest unit number of the first MSCP controller. RSTS/E requires that drives supported by a standard MSCP controller be numbered starting at 0 and drives supported by an alternate MSCP controller be numbered starting at 4. Because MSCP device names under MicroVMS designate the supporting MSCP controller, the unit numbering is less restricted. For example, two drives which are supported by a standard MSCP controller might be DUA0 and DUA1 and a third drive supported by an alternate MSCP controller might be DUB0. Table 3-1 is an MSCP unit numbering example under the RSX-11M operating system which shows the MSCP number versus the actual physical addresses assigned to all the components. The physical disk drive (unit number 1) of the second controller is split into two logical units. Note that two device names are associated with that drive. Table 3-1. Subsystem Configuration Example 旼컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴쩡컴컴컴쩡컴컴커 � � � Drive � � � QD21 � � Unit 쿏evice� � Address � Device Description � Number쿙ame � 쳐컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴탠컴컴컴탠컴컴캑 � 772150 � Micropolis 1350 � 1 � DU0 � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컵컴컴컴� � � Micropolis 1350 � 2 � DU1 � 쳐컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴탠컴컴컴탠컴컴캑 � 760334 � Maxtor 4380 � 1 � DU2 � � (Floating) � (head split) � � DU3 � � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컵컴컴컴� � � Maxtor 4380 � 2 � DU4 � 읕컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴좔컴컴컴좔컴컴켸 NOTE All MSCP peripherals supported by the QD21 use the same device identifier - RA81. Section 3 (continued) 컴컴컴컴컴컴컴컴컴컴� 3.5 Operating Systems, Device and Vector Addresses ---------------------------------------------------- Before the installation of any peripheral device can be considered complete, the computer's operating system must be made aware of the new resource. The information provided in this section is intended to supplement your DEC operating system resources and to be used as an aid in planning the installation of your QD21. An operating system can be made aware of a new resource in three ways: o The operating system can poll the computer's I/O device address space. o The device can be manually connected using CONNECT or CONFIGURE statements o The user can tell the operating system about a device during an interactive SYSGEN procedure. The first technique is referred to as autoconfigure, and it is essentially automatic. The second technique requires that CONNECT statements be placed in a special command file that is executed each time the computer is bootstrapped. The third technique, interactive SYSGEN, creates a configuration file that the operating system references when the system is bootstrapped. All techniques accomplish the same result: they associate a specific device type with a bus address and interrupt vector. Most recent versions of DEC operating systems use autoconfigure to some extent, and try to follow the same rules. The RT11 operating system does not use autoconfigure, but can locate devices that reside at a standard address. There are some differences among operating systems, however, especially with regard to MSCP controllers at alternate LSI-11 bus addresses. The following paragraphs address these differences for each supported operating system. This discussion includes information on choosing appropriate LSI-11 bus device addresses and interrupt vectors for the subsystem. The following operating system discussions give procedures for choosing LSI-11 bus addresses for the first MSCP controller and any subsequent controllers in the host configuration. No instructions are provided for programming the chosen address into the QD21. See subsection 4.3.1 for detailed switch setting information. MSCP-type controllers contain two registers that are visible to the LSI-11 bus I/O page. They are the Initialization and Polling (IP) register (base address) and the Status and Address (SA) register (base address plus 2). The IP register, the CSR address, LSI-11 bus address and the base address all refer to the same register. All of the operating systems described in the following subsections use the standard LSI-11 bus address of 1772150(8) for the first controller on the host system. Vector addresses for MSCP controllers are not selected by using switches on the controller, but are programmed into the controller during the Initialization process. Many operating systems select the vector address automatically. If an operating system requires manual input of the vector, the procedure notes that fact. Again, although DEC has attempted to standardize treatment of peripherals by operating systems, some differences do exist. Table 3-2 lists and describes the device names assigned to MSCP devices under five operating systems. Two controller names and two drive names are given to indicate the numbering scheme Table 3-2. Device Names 旼컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴커 � Operating System � Controller � Drives Supported � � � First, Second � by First Controller � 쳐컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴캑 � RSTS/E � RU0, RU1 � DU0, DU1 � � RSX-11M � --- --- � DU0, DU1 � � RSX-11MPLUS � DUA, DUB � DU0, DU1 � � RT-11 � Port0, Port1 � DU0, DU1 � � MicroVMS � PUA, PUB � DUA0, DUA1 � � Ultrix-11 � uda0, uda1 � ra0, ra1 � � Ultrix-32m � uda0, uda1 � ra0, ra1 � 읕컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴켸 The information regarding operating systems in these subsections is subject to change. The following discussions are based on three assumptions: o This is the first pass that is being made through SYSGEN; therefore, no saved answer file exists. Answer N (no) to questions such as "Use as input saved answer file?" o Your host system configuration conforms to the standard LSI-11 device configuration algorithm (otherwise autoconfigure results are not reliable) o You are generating a mapped version of the operating system on the appropriate hardware (unless you are using RT11). 3.5.1 RSTS/E Operating Systems (V8.0 and above) ------------------------------------------------- RSTS/E scans the hardware to determine configuration each time the system is bootstrapped. The scanning program is called INIT.SYS and it relies on the same hardware configuration conventions as do the other DEC operating systems. The RSTS/E operating system can support two MSCP controllers. The first MSCP controller must be located at the standard LSI-11 bus address, 7721508. According to DEC documentation, the second unit should be located in floating address space. For an alternate QD21, Emulex suggests specifying a LSI-11 bus address of 760334(8) using the HARDWARE option of the INIT.SYS program. The INIT.SYS program uses a user-specified table, located in the currently installed monitor, to make exceptions to the autoconfigure algorithm. This table is modified by the HARDWARE option of the INIT.SYS program. Use of this table allows an MSCP controller to be placed at virtually any address on the I/O page. Note that this table must be reset any time a new monitor is installed. Emulex suggests using an LSI-11 bus address of 760334(8) for an alternate QD21. An MSCP controller must be located at the standard address to be a bootstrap device. Interrupt vector addresses are assigned to the MSCP controllers by INIT.SYS and programmed into the devices during initialization. 3.5.1.1 Adding MSCP Support ----------------------------- Support for an MSCP controller must be included in a monitor at SYSGEN time. To include support for an MSCP controller in a RSTS/E monitor, respond to the SYSGEN question "number of MSCP controllers" with the number of MSCP controllers on the system. Units connected to MSCP controllers will be accessible to an online RSTS/E system only after the monitor is successfully SYSGENed and installed with the INSTALL suboption of the INIT.SYS program, and the units have been successfully initialized with the DSKINT suboption of INIT.SYS. 3.5.2 Operating Systems (V5.1 and above) ------------------------------------------ The RT-11 Operating System supports up to four MSCP controllers with up to 256 devices (total) on the four controllers. The following paragraphs discuss the LSI-11 bus and vector addresses for MSCP controllers under RT-11 in host systems with only one MSCP controller and in those with more than one controller. Disk partitioning, a unique feature of RT-11 that is applicable regardless of the number of controllers, is also discussed. 3.5.2.1 Installing a Single MSCP Controller --------------------------------------------- If your host system includes only one MSCP controller, install it with a LSI-11 bus address of 772150(8). RT-11 will find and install the handler (driver) for that controller. In single MSCP controller configurations, it is not necessary to run SYSGEN. You may use one of the pregenerated monitors that are provided with the RT-11 Distribution. Emulex recommends that you modify the system startup command file, STARTx.COM, to properly partition the disk drives. See subsection 3.5.2.3. 3.5.2.2 Installing Multiple MSCP Controllers ---------------------------------------------- If your host system includes more than one MSCP controller, you may either modify the MSCP handler as described in the RT-11 Software Support Manual or perform a SYSGEN. The following procedure describes the SYSGEN technique (user input is in boldface print): 1. Initiate SYSGEN: IND SYSGEN Answer the next group of questions appropriately. 2. Indicate that you want the system to use the startup command file when booting: Do you want the startup indirect file (Y)? Y The startup command file is required to allow additional MSCP controller LSI-11 bus addresses to be specified and to partition the disks consistently when the system is bootstrapped. Answer the next set of questions appropriately. 3. Indicate that you want MSCP support when the Disk Options question appears: Enter the device name you want support for [dd]: DU 4. Indicate the number of MSCP controllers on your system in response to this question: How many ports are to be supported (1)? 2 RT-11 refers to individual MSCP controllers or controllers as ports. Each port has its own LSI-11 bus and vector addresses. 5. Specify support for all other devices in your host system configuration as well. Indicate that there are no more devices by entering a period: Enter the device name you want support for [dd]: . 6. You must specify the addresses of all MSCP controllers (ports) using the SET CSR keyboard command. To ensure that this is done consistently and automatically on power-up, you must add the commands to the system start-up command file, STARTx.COM. The x stands for the monitor that is being used, where x is S, F, or X for single-job, foreground/ background, or extended memory, respectively. Edit the command file to include the following statements: SET DU CSR=772150 (Default) SET DU CSR2=760334 (Floating) SET DU VECTOR=154 (Default) SET DU VEC2=300 The LSI-11 bus for the second device can be any unused address in the I/O page which is supported by QD21 address switch settings; the vector address can be any unused address in the vector page. Default statements are not required. 7. Complete SYSGEN according to the DEC documentation. 3.5.2.3 Disk Partitioning --------------------------- RT-11 is unable to handle drives with a capacity of more than 65,535 blocks (33.5M bytes). To allow drives with larger capacities to be used, RT-11 allows individual physical drives to be partitioned into multiple logical drives. This is done by assigning as many logical drive names (DU0, DU1, etc.) to a physical drive as that drive can support. The statements that make that assignment should be placed in the system start-up command file. This ensures that the drives are automatically partitioned every time the system is bootstrapped and that the partitions are always the same. Use the following procedure to determine the total number of logical drives to be assigned to each physical drive. 1. Determine the drive configuration(s) that you intend to use. You need to know the LUN of each logical drive and the data storage capacity (in logical blocks) of each logical unit. If the QD21 is at an alternate LSI-11 bus address (not 772150), then you must specify an MSCP device number by using switches SW1-2 through SW1-4 (see subsection 4.3.3.2.2). 2. Divide the capacity for each MSCP Unit by 65,535. If the result is a number greater than 1, then that MSCP Unit should be partitioned into multiple logical units. (The last partition on a disk may be smaller than 65,535 blocks.) Round the result up to the nearest whole number. That whole number (up to eight) equals the number of logical disks into which that MSCP unit should be partitioned. 3. You must then include a series of statements in the system startup command file, STARTx.COM, that assigns logical names to each partition. Each statement has the following format: SET DUn UNIT=y PART=x PORT=z where n is the logical device name, y is the physical MSCP unit number, x is the partition number, and z is the controller number (specify the controller number when two or more controllers are present; do not specify the port when only one controller is present). If you partition any drives, you must do this for each partition on each drive, including drives that can hold only one partition. Example: You have selected a Maxtor 4380 that has a capacity of 584,000 blocks. 584,000 컴컴컴� = 8.91 (9 logical units) 65,535 Dividing the unit capacities by 65,535 and rounding the result up to the nearest whole number gives the number of logical units into which each should be partitioned (remember that eight is the maximum). You assign logical names to the partitions, beginning with DU0. For the previous example, the assignments are made as follows: SET DU0 UNIT=0 PART=0 SET DU1 UNIT=0 PART=1 SET DU2 UNIT=0 PART=2 SET DU3 UNIT=0 PART=3 SET DU4 UNIT=0 PART=4 SET DU5 UNIT=0 PART=5 SET DU6 UNIT=0 PART=6 SET DU7 UNIT=0 PART=7 Because this configuration has only one controller, the port is not defined. If you had another controller in this configuration, the controllers would be defined as Port 0 and Port 1. Modify the system startup command file to include the disk partitioning statements. 3.5.3 RSX-11M Operating Systems (V4.0 and above) -------------------------------------------------- RSX-11M SYSGEN is an interrogative program that allows a complete, running RSX-11M system to be configured for a particular hardware environment. SYSGEN is well documented in the RSX-11M System Generation and Installation Guide, and you are expected to rely primarily on that manual. This explanation is provided only to remove some ambiguities that the installation of the QD21 may present SYSGEN supports autoconfigure, and MSCP controllers are detected by autoconfigure. However, autoconfigure detects only the MSCP controller that is located at the standard LSI-11 bus address. Additional MSCP controllers at alternate addresses must be attached to the operating system manually. NOTE If the QD21 controls the system disk, you must select 22-bit addressing (SW2-6 ON) even if your system has only 256K bytes of memory. 3.5.3.1 Installing a Single MSCP Controller --------------------------------------------- If you have only one QD21, install it at the standard address (772150) and use autoconfigure to connect your peripherals. The procedure given in the RSX-11M System Generation and Configuration Guide is adequate for this purpose. 3.5.3.2 Installing Multiple MSCP Controllers ---------------------------------------------- If you have two MSCP controllers, say a DEC MSCP controller and a QD21, you must perform a complete manual initialization. We recommend that the DEC MSCP controller be installed at the standard LSI-11 bus address. Locating the QD21 at the alternate LSI-11 bus address does not prevent its being used as the system device. Both MSCP controllers are connected to the operating system by using the following procedure. 1. Invoke SYSGEN. > SET /UIC=[200,200] > @SYSGEN 2. To indicate that you want to use autoconfigure, answer Y (yes) to the following question: * Autoconfigure the host system hardware? [Y/N]: Y 3. To indicate that you do not want to override autoconfigure results, answer N (no) to this question: * Do you want to override Autoconfigure results? [Y/N]: N Answer the rest of the questions in the SETUP section appropriately, and continue to the next section, TARGET CONFIGURATION. In TARGET CONFIGURATION, the defaults presented for the first group of questions should be accurate for your system because autoconfigure was requested. 4. In response to the question regarding devices, indicate that you have two MSCP-TYPE controllers: * Devices: DU=2 Devices: . This entry supersedes the value of 1 that autoconfigure has determined. Typing a period (.) terminates device input. Continue through the next four sections, HOST CONFIGURATION, EXECUTIVE OPTIONS, TERMINAL DRIVER OPTIONS, and SYSTEM OPTIONS, answering questions appropriately. 5. When you reach the PERIPHERAL OPTIONS section, SYSGEN asks you questions that pertain only to the MSCP devices on your system. (Unless you indicated that you wished to override other autoconfigure results when you responded to the Devices question, SYSGEN asks questions on those devices.) The first question requests information about the controller's interrupt vector address, LSI-11 bus address, the number of DU-TYPE disk drives (there is no default value for this parameter), the number of command rings, and the number of response rings. The question is asked twice, once for controller 0 and once for controller 1, because we have specified two DU-TYPE controllers. The dialog uses the abbreviation contr to indicate controller. * DU contr 0 [D:154,172150,,4,4] 154,172150,3,4,4 The standard vector address for MSCP controllers is 154. The vector for a second unit should be allocated from floating vector address space. Any unused vector between 300 and 774 can be allocated. See Appendix A for a description of DEC's algorithm for assigning floating vectors. The standard LSI-11 bus address for MSCP controllers is 772150. Emulex recommends that the second unit be located in floating LSI-11 bus address space. See Appendix A for a description of the DEC algorithm for assigning floating addresses. The number of DU-TYPE disk drives depends on the configuration that you have selected for the QD21, or on the number of drives that are attached to a DEC MSCP controller. When you select a configuration for the QD21, you are taking into account the number of physical disk drives that you are attaching to the QD21's ESDI interface. When you select a configuration, you are also specifying a logical arrangement for the QD21 MSCP subsystem. Some configurations split one physical drive into two logical drives to make file management easier. You determine the configuration of each ESDI disk drive when you program the QD21's NOVRAM; see subsections 4.7, 4.8, and 4.9. The following types of disk drives can be attached to DEC MSCP controllers: o RX50 o RD51 o RD52 o RD53 o RC25 o RA60 o RA80 o RA81 The RX50 drive contains two 5.25-inch floppy diskettes; count an RX50 as two drives. The RC25 has both fixed and removable hard media; count an RC25 as two drives. RSX-11M supports up to eight command and eight response rings; the number of command and response rings that you specify depends on your application. Four command and four response rings are reasonable and adequate for most applications. 6. SYSGEN then asks you to specify the type of disk drive(s) on each controller: * DU contr 0 unit 0. is an RA60/80/81/RC25/RD51/RX50 [D:RA81]RD51 For the DEC MSCP controller, indicate the appropriate peripherals. For the QD21, indicate that you have one RA81 for each logical disk drive RSX-11M does not tolerate gaps in sequence; the unit numbers must be contiguous. In addition, the unit numbers specified for each controller must be the same as those reported by the controller during initialization. 7. Complete the SYSGEN procedure according to DEC documentation. 3.5.4 RSX-11M-PLUS Operating Systems (V2.1 and above) ------------------------------------------------------- RSX-11M-PLUS SYSGEN is an interrogative program that allows a complete, running RSX-11M-PLUS system to be configured for a particular hardware environment. Sysgen is well documented in the RSX-11M-PLUS System Generation and Installation Guide, and you are expected to rely primarily on that manual. This explanation is provided only to remove some ambiguities that the installation of the QD21 may involve. SYSGEN supports autoconfigure, and MSCP controllers are detected by autoconfigure. However, autoconfigure detects only the MSCP controller that is located at the standard LSI-11 bus address. Additional MSCP controllers at alternate addresses must be attached to the operating system manually. 3.5.4.1 Installing a Single MSCP Controller --------------------------------------------- If you have only one QD21, install it at the standard address (772150) and use autoconfigure to connect your peripherals. The procedure given in the RSX-11M-PLUS System Generation and Configuration Guide is adequate for this purpose. 3.5.4.2 Installing Multiple MSCP Controllers ---------------------------------------------- If your initial system configuration includes two MSCP controllers, connect the alternate MSCP controller to the operating system during the initial SYSGEN. We recommend that you use autoconfigure to connect the first controller at the standard address (772150). We recommend that the DEC MSCP controller be installed at the standard LSI-11 bus address; locating the QD21 at the alternate LSI-11 bus address does not prevent its being used as the system device. If you are adding the second MSCP controller to the system configuration, use the Add a Device option of SYSGEN or a complete SYSGEN. The following procedure describes the Add a Device process (user input is in boldface print): 1. Invoke SYSGEN. > SET /UIC=[200,200] > @SYSGEN 2. To indicate that you want to do a subset of the SYSGEN procedure, answer N (no) to the following questions: * Do you want to do a complete SYSGEN? [Y/N D:Y]: N * Do you want to continue a previous SYSGEN from some point? [Y/N D:Y]: N 3. To indicate that you want to execute a specific module of the SYSGEN procedure, answer Y (yes) to this question: * Do you want to do any individual sections of SYSGEN? [Y/N D:Y]: Y 4. Select the Add a Device section of SYSGEN: * Which sections would you like to do? [S R:0.15.]: H Type the letter H to select the Add a Device section. SYSGEN now asks you all of the questions in the Choosing Peripheral Configuration section. The questions that SYSGEN asks pertain to the type and number of controllers that are installed on your system. There is one question for each type of controller that RSX-11M-PLUS can support. Answer 0 (zero) for all types of controllers until you are prompted for the number of UDA-TYPE devices. 5. When you are asked to specify the number of MSCP-type devices, answer appropriately: * How many MSCP disk controllers do you have?[D R:0.63. D:0.] 2 6. Give the total number of MSCP disk drives (on all controllers) installed on the system. * How many MSCP disk drives do you have? [D R:0.n. D:1.] 5 The answer to this question depends on the configuration that you have selected for the QD21 and on the number of drives that are attached to any DEC MSCP controllers. When you select a configuration for the QD21, you are taking into account the number of physical disk drives that you are attaching to the QD21's ESDI interface. When you select a configuration, you are also specifying a logical arrangement for the QD21 MSCP subsystem. Some configurations split one physical drive into two logical drives to make file management easier. You determine the configuration of each ESDI disk drive when you program the QD21's NOVRAM (see subsections 4.7, 4.8, and 4.9). The following types of disk drives can be attached to DEC MSCP controllers: o RX50 o RD51 o RD52 o RD53 o RC25 o RA60 o RA80 o RA81 The RX50 drive contains two 5.25-inch floppy diskettes; count an RX50 as two drives. The RC25 drive has both fixed and removable hard media; count an RC25 as two drives. 7. SYSGEN then asks you to specify controllers per disk drives. * To which DU controller is DU0: connected? [S R:11]: A This question is asked as many times as the number of MSCP drives that you have indicated are on the system. RSX-11M-PLUS does not tolerate gaps in sequence; the MSCP unit numbers must be contiguous. In addition, the unit numbers specified for each controller must be the same as those reported by the controller during initialization. Use A for the primary controller and B for the alternate controller. 8. Enter the vector address for each MSCP controller: * Enter the vector address of DUA [O R:60774 D:154] The standard vector address for MSCP controllers is 154. The vector for a second unit should be allocated from floating vector address space. Any unused vector between 300 and 774 can be allocated. See Appendix A for a description of DEC's algorithm for assigning floating vectors. 9. Enter the CSR address for each MSCP controller: * What is its CSR address? [O R:160000177700 D:172150] The standard CSR address for MSCP controllers is 772150. Emulex recommends that the second unit be located in floating CSR address space. See Appendix A for a description of the DEC algorithm for assigning floating addresses. 10. Specify the number of command rings for each MSCP controller: * Enter the number of command rings for DUA [D R:1.8. D:4.] 4 RSX-11M-PLUS supports up to eight command rings. The value you specify depends on your application. Four command rings are reasonable and adequate for most applications. 11. Specify the number of response rings for each MSCP controller: * Enter the number of response rings for DUA [D R:1.8. D:4.] 4 RSX-11M-PLUS supports up to eight response rings. The value you specify depends on your application. Four response rings are reasonable and adequate for most applications. 3.5.5 MicroVMS Operating Systems ---------------------------------- MicroVAX/MicroVMS supports MSCP controllers at the standard address, 772150, and in floating address space. MicroVMS has a software utility called SYSGEN which can be used to determine the LSI-11 bus address and interrupt vector address for any I/O devices to be installed on the computer's LSI-11 bus. A running MicroVAX/MicroVMS computer system is required in order to use this utility. If you do not have access to a running system, you must determine the LSI-11 bus addresses and vector addresses manually (although autoconfigure can still be used to connect the devices to the computer automatically on powerup). See Appendix A for a description of the algorithm used by SYSGEN to determine LSI-11 bus addresses. The following procedure tells how to use MicroVMS SYSGEN to determine LSI-11 bus addresses and interrupt vectors. 1. Log in to the system manager's account. Run the SYSGEN utility: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> The SYSGEN> prompt indicates that the utility is ready to accept commands. 2. Obtain a list of devices already installed on the MicroVAX LSI-11 bus by typing: SYSGEN> SHOW/CONFIGURATION Name: PUA Units: 1 Nexus: 0 CSR: 772150 Vector1: 154 Vector2: 000 Name: TTA Units: 1 Nexus: 0 CSR: 760100* Vector1: 300* Vector2: 304* Name: TXA Units: 1 Nexus: 0 CSR: 760500* Vector1: 310* Vector2: 000 *Floating address or vector Note: All addresses and vectors are expressed in octal notation. Figure 3-3. Sample SHOW CONFIGURATION ====================================== SYSGEN lists by logical name the devices already installed on the LSI-11 bus. Make a note of these other devices with floating addresses (greater than 760000) or floating vectors (greater than 300) that you plan to reinstall with your QD21. 3. To determine the LSI-11 bus addresses and vectors that autoconfigure expects for a particular device type, execute the CONFIGURE command: SYSGEN> CONFIGURE DEVICE> Specify the LSI-11 bus devices to be installed by typing their LSI-11 bus names at the DEVICE prompt (the device name for MSCP controllers under MicroVMS is UDA). DEVICE> UDA,2 DEVICE> DHV11 DEVICE> DZ11 A comma separates the device name from the number of devices of that type to be installed. The number of devices is specified in decimal. In addition to the QD21, you need only specify devices that have floating addresses or vectors. Devices with fixed addresses or vectors do not affect the address or vector assignments of devices with floating addresses and vectors. 4. Indicate that all devices have been entered by pressing the and Z keys simultaneously: DEVICE> ^Z SYSGEN lists the addresses and vectors of the devices entered in the format shown in Figure 3-4. SYSGEN> CONFIGURE DEVICE> DZ11 DEVICE> DHV11 DEVICE> UDA,2 DEVICE> ^Z Device: UDA Name: PUA CSR: 772150 Vector: 154 Support: yes Device: DZ11 Name: TTA CSR: 760100* Vector: 300* Support: yes Device: UDA Name: PUB CSR: 760354* Vector: 310 Support: yes Device: DHV11 Name: TXA CSR: 760500* Vector: 320 Support: yes *Floating address or vector Note: All addresses and vectors are expressed in octal notation. Figure 3-4. CONFIGURE Command Listing ====================================== 5. Note the CSR addresses listed for the LSI-11 bus devices in floating address space. Program the listed addresses into non-Emulex devices as instructed by the manufacturer's documentation. For the QD21, program the address given for the QD21 (lowest numerical address) into the board as described in subsection 4.3.1. 6. Complete SYSGEN according to the DEC documentation. If you want to select a nonstandard address for the QD21, that is one that differs from the address selected by the CONFIGURE command, you must enter CONNECT statements in the SYCONFIG.COM file that is in the system manager's account, SYS$MANAGER. Use the syntax of the CONNECT statements as described in the DEC documentation on MicroVMS SYSGEN. NOTE Do not alter the STARTUP.COM or UVSTARTUP.COM command files in the main system account, SYS$SYSTEM. 3.5.6 Ultrix-11 Operating Systems (V3.0 and above) ---------------------------------------------------- The Ultrix-11 Version 3.0 system supports up to a total of four MSCP disk controllers, but only one of each type of controller. Therefore, to add support for two MSCP controllers, the system generation procedure must be told that there is, for example, one UDA50 controller and one RQDX1 controller. The choices are: Controller name device name disk name UDA50 ra ra?? KLESI rc rc?? RQDX1, RQDX2, or RQDX3 rq rd?? RUX1 rx rx?? NOTE A bug exists in version 3.0 that prevents actually using more than three controllers. When an RQDX1, RQDX2, or RQDX3 is specified, the sysgen program will not allow specifying an RUX1 controller, and vice versa. 3.5.6.1 Sysgen ---------------- To add a device to an Ultrix-11 kernel, the sysgen program must be run to create and make a new kernel. Creating a kernel involves the creation of a configuration file and then "making" the kernel from this configuration file. A dialogue mode is used to enter various system parameters. The question: Disk controller type: ? asks for the specification of a disk controller. You must choose a different controller type for each MSCP controller on your system, even if they are all QD21s. NOTE The order in which you enter each controller is very important. The order becomes the controller number. The same order must also be used when creating the special files (see below). For each MSCP controller specified, one of the following statements will be typed: First MSCP controller type: Second MSCP controller type: Third MSCP controller type: and, depending on the controller name specified previously, the next question will differ. See the appropriate correlation below: Disk Controller Type Next Sysgen Question uda50 or kda50 Drive 0 type ? klesi Drive 0 type ? rqdx1/2/3 or rux1 Drive 0 type ? Note that it doesn't matter which drive type you choose. Just enter one of the supplied names for each drive you have connected to each controller. The next two questions refer to the controller's CSR and vector addresses: CSR address <172150> ? Vector address <154> ? The defaults for the CSR and Vector address will always be 172150 and 154, respectively. Be sure to enter the correct CSR value. Since the MSCP controller accepts a software-defined vector, an unused vector from the floating address space should be used for all nonstandard address controllers. Emulex suggests that you use a decrementing (by 4) vector address starting at 700 (octal). This will prevent you from using a vector address that is already in use. 3.5.6.2 Special Files ----------------------- The Ultrix operating system communicates with devices on the system by the use of special files. These files contain pointers into a system table that lists the entry points for a corresponding driver for that device. There must be a special file for each device (and each partition for disks) on the system in order for Ultrix to communicate with that device. Some devices will have two special files associated with a device: one for use with character mode, and the other for block mode. These special files exist in the account "/dev". The special files for Ultrix-11 are created with the 'msf' program (make special file). If no options are supplied, this program enters a dialogue mode: # /etc/msf The "msf" program will issue the prompt: Command : Use the "c" command to create the special files. Device name (? for help) : The "msf" program does not understand the notations for different controller types. Instead, it uses the device name and controller number in order to create the special files. For example, the special files for ra60, ra80, and ra81 would be "ra", the special file for an rc25 would be "rc", and the special files for an rd51/2/3 would be "rd". Therefore, you must enter a unique device name for each controller. It is suggested that you use the same device names used previously with the sysgen program. The next two questions are: MSCP controller number <0 1 2 3>: Unit number <0 -> 7 or all>: The MSCP controller number assigned to each controller is determined by the order in which you entered the devices to the sysgen program; that is, the number for the first controller is 0. The unit number for each drive (as it is identified by SW1-2 through SW1-4) must match the drive's specification in the configuration file. In addition, the drive to be booted from must be 0, regardless of whether the controller is at the standard or an alternate address. For ra, rc, and rd type devices, the next question will be asked: Assume standard disk partitions (? for help) ? If you answer "no", the next question will be asked: Create partitions <0 -> 7 or all>? You should always answer "all". 3.5.6.3 Newfs --------------- The "newfs" program is used to create file systems on specified partitions. The newfs program requires no arguments and immediately enters a dialogue mode. See the Ultrix-11 System Manager's Guide for more information on newfs. 3.5.6.4 Volcopy ----------------- Once a device is configured into your current kernel, you can copy an existing file system onto a new partition with the 'volcopy' program. The new partition will be created with the identical size parameters of the original file system. See the Ultrix-11 System Manager's Guide for more information on volcopy. 3.5.6.5 Copying a Bootstrap ----------------------------- A new bootstrap can be copied onto a new system disk with the "dd" program. The command: # dd if=/mdec/rauboot of=/dev/ra00 will copy the bootstrap file onto block zero of ra0. NOTE V7M-11 V1.0 and Ultrix-11 V2.0 did not support self-sizing disks and are, therefore, unusable with the Emulex MSCP controllers. 3.5.7 Ultrix-32 Operating Systems ----------------------------------- The Emulex MSCP class disk disk subsystems emulate the DEC DSA UDA-50/KDA-50/ RA81 (MSCP) disk subsystem. They report that they are of controller type "DU" and of device type "RA81". However, when asked for the number of logical blocks they do not return a size value that matches that of a "real" DEC RA81. 3.5.7.1 The Kernel -------------------- Support for MSCP controllers must be included in a monitor when rebuilding the kernel. The configuration file is edited to reflect the number of controllers and the number of drives connected to each controller. The Ultrix-32 system supports two MSCP disk controllers. Ultrix-32 does not require that the units be in sequential order. However, the MSCP device number for the drive to be booted from MUST be 0 regardless of the controller's LSI-11 bus address. Further, be certain that the MSCP device number of each drive (as it is identified by SW1-2 through SW1-4) matches the drive's specification in the configuration file. The following example shows two controllers, the first with two drives, the second with one: controller uda0 at uba0 csr 0172150 vector udintr disk ra0 at uda0 drive 0 disk ra1 at uda0 drive 1 controller uda1 at uba0 csr 0160334 vector udintr disk ra2 at uda1 drive 2 In this example, the first unit on the second controller must be MSCP device number two regardless of the units on the first controller. 3.5.7.2 Special Files ----------------------- The Ultrix operating system communicates with devices on the system by the use of special files. These files contain pointers into a system table that lists the entry points for a corresponding driver for that device. There must be a special file for each device (and each partition for disks) on the system in order for Ultrix to communicate with that device. Some devices will have two special files associated with a device: one for use with character mode, and the other for block mode. These special files exist in the account "/dev". There is a shell script, called "MAKEDEV" (uppercase important), on the Ultrix- 32 system to help build these special files. The format of this command is: % /dev/MAKEDEV device ... This script passes your input to the program "mknod" to create the special files. You should use this command file to create the special files for each disk you wish to connect to the system. An example for two disks is: % /dev/MAKEDEV ra4 ra5 This example assumes that you have already added the device into the configuration file, and you chose the logical names ra4 and ra5 for your disks. 3.5.7.3 Autoconfigure ----------------------- At boot time, Ultrix-32 attempts to auto-configure the devices included in the booted monitors configuration file. If the device was not included in the configuration files, it will not be configured into the running system. If the device is not present, Ultrix will skip it. When Ultrix finds a device at autoconfigure time it prints a message as follows rqd0 at csr 172150 vec 774, ipl 17 ra0 at rqd0 slave 0 ra1 at rqd0 slave 0 rqd1 at csr 160334 vec 770, ipl 17 ra2 at rqd1 slave 0 The CSR address were set in the configuration file. The vectors are assigned sequentially in reverse order by the operating system. If the CSR or unit numbers don't match the configuration file, the device will be skipped (and no message will be printed). 3.5.7.4 Disk Partitions ------------------------- Ultrix allows a user to logically subdivide a disk into sections called "partitions". Disk partitions were created because the first Unix operating systems could access only a limited amount of space on large disks. Disk partitioning lets several Unix file systems reside on the same disk, one file system per partition. This allows the operating system to utilize the entire disk. Each disk has a partition table that defines the starting location and size (both in blocks) of each partition on that disk. When a disk is opened by the operating system (for the very first time), it writes the partition size table into the super block of partition "a" (the first partition) on the disk. 3.5.7.5 Disk Partition Modifications -------------------------------------- Modifications to a disk's partition table is done with the "chpt" command each time a disk is initialized or reinitialized. The "chpt" command allows a system manager to alter a particular partition's location and size characteristic. The operating system initializes the disk's partition table with that of a real DEC RA81's size table (found in the disk driver) on its first opening. The system manager should then edit these sizes (with "chpt" command) to match the system needs. 3.5.7.6 Default Partition Modifications ----------------------------------------- It is also possible to modify the default RA81 partition size table, which is stored in the device driver; this would eliminate the need for editing the partition table each time the disk is initialized. When DEC reorganized the Berkeley 4.2 Unix system to create Ultrix-32, they set it up to allow the distribution of the operating system in a binary format. This allowed them to distribute a minimum amount of source code to binary license holders. They separated each of the drivers and system kernel modules into two sections: a code portion and a data portion. The code portion does not require recompilation depending on the selected options at SYSGEN time; this is supplied in object format (xx.o). The data portion requires selection parameters based on sysgen answers; this is supplied in source code format (xx_data.c). Making changes to this table will alter the default partition size characteristics for new disks. An example of the changes to the uda driver is included here. Example: /usr/sys/data/uda_data.c: }, ra81_sizes[8] ={ 15884, 0, /* A=blk 0 thru 15883 */ 66880, 15884, /* B=blk 15884 thru 82763 */ -1, 0, /* C=blk 0 thru end */ 0, 0, /* D= not used */ 0, 0, /* E= not used */ 0, 0, /* F= not used */ -1, 82764, /* G=blk 82764 thru end */ 0, 0, /* H= not used */ }; The -1 above indicates the end of the disk. 3.5.7.7 Newfs --------------- The newfs program speeds up the creating of a file system on a partition. It looks up information, in the file /etc/disktab, on the disk specified by the system manager and creates the file system according to those default values. An example of the changes to the /etc/disktab file have been included here. Example: /etc/disktab: qd21|QD21|Emulex QD21 Fujitsu Eagle M2351A Winchester:\ :ty=winchester:ns#47:nt#20:nc#840:\ :pa#15884:ba#4096:fa#512:\ :pb#66880:bb#4096:fb#512:\ :pc#789600:bc#4096:fc#1024:\ :pg#706836:bg#4096:fg#1024: 3.5.7.8 Suggestions/Warnings ------------------------------ There is a maximum of eight partitions per disk. The partitions form logical boundaries on the disk, separating each file system from all others. These logical divisions are useful for disk management because you can put similar types of users, files, directories or projects all on the same file system. Because a file system can never exceed its partition in size, you can use partitions to regulate disk use. There are certain areas of the disk which, by default, are reserved for the operating system. By mounting the swap space, for example, on its own partition important data can not be overwritten when data from memory is swapped to the disk. The Ultrix-32 systems use partition "b" for the swap file. If you plan to use your own partition values, be sure to allocate an area on your system disk for a swap file. For more information on disk partitioning and modifications to the partition sizes, see Appendix C, "Disk Partitioning", in the Ultrix-32 System Manager's Guide. The program "diskpart" is used to create entries for the disk driver or for the "disktab" file. It creates a template based on the default rules used at Berkeley. The following is a table defining the Berkeley defaults: Partition 20-60 MB 61-205MB 206-355 MB 356+ MB a 15884 15884 15884 15884 b 10032 33440 33440 66880 c * all all all all d 15884 15884 15884 15884 e unused 55936 55936 307200 f * unused end end end g * end end end end * The 'c' partition is, by convention, used to access the entire disk. In normal operation, either the 'g' partition is used, or the 'd', 'e', and 'f' partitions are used. The 'f' and 'g' partitions are variable sized, occupying whatever space remains after allocation of the fixed sized partitions. NOTE Ultrix-32 V1.0 did not support self-sizing disks and is, therefore, unusable with the Emulex MSCP controllers. The "diskpart" program was not included on the Ultrix-32 V1.1 distribution kit. 旼컴컴컴컴컴컴컴컴컴컴컴컴� � Section 4 INSTALLATION � 읕컴컴컴컴컴컴컴컴컴컴컴컴� 4.1 Overview -------------- The procedure for installing the QD21 Disk Controller is described in this section. The subsection titles are listed below to serve as an outline of the procedure. Subsection� Title 컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 4.2 � Inspection 4.3 � Disk Controller Setup 4.4 � Physical Installation 4.5 � ESDI Drive Preparation 4.6 � Cabling 4.7 � NOVRAM Loading, Disk Formatting, and Testing 4.8 � F.R.D. Options 4.9 � Drive Configuration Parameters 4.10 � Operation If you are unfamiliar with the subsystem installation procedure, Emulex recommends reading this Installation Section before beginning. 4.1.1 Subsystem Configurations -------------------------------- This section is limited to switch setting data and physical installation instructions. No attempt is made to describe the many subsystem configurations that are possible. If you are not familiar with the possible configurations, we strongly recommend reading Section 3, PREPARING THE INSTALLATION, before attempting to install this subsystem. When you are installing the subsystem, you should make a record of the subsystem configuration and environment. Figure 4-1 is a Configuration Record Sheet that lists the information required and shows where the data can be found This information will be of help to an Emulex service representative should your subsystem require service. 4.1.2 DIP Switch Type ----------------------- Switch-setting tables in this manual use the numeral one (1) to indicate the ON (closed) position and the numeral zero (0) to indicate the OFF (open) position. The two DIP switch types used in this product are shown in Figure 4-2. Each is set to the code shown in the switch setting example. 4.1.3 Maintaining FCC Class A Compliance ------------------------------------------ Emulex has tested the QD21 Intelligent Disk Controller with DEC computers that comply with FCC Class A limits for radiated and conducted interference. When properly installed, the QD21 does not cause compliant computers to exceed Class A limits. There are two possible configurations in which the QD21 and its associated ESDI peripherals can be installed: o With both the QD21 Disk Controller and the ESDI disk drives both mounted in the same cabinet, and o With the QD21 mounted in the CPU cabinet and the ESDI drives mounted in a separate cabinet. To limit radiated interference, DEC completely encloses the components of its computers that generate or could conduct radio-frequency interference (RFI) with a grounded metal shield (earth ground). During installation of the QD21, nothing must be done that would reduce this shield's effectiveness. That is, when the QD21 installation is complete, no gap in the shield that would allow RFI to escape can be allowed. Conducted interference is generally prevented by installing a filter in the ac line between the computer and the ac outlet. Most power distribution panels that are of current manufacture contain suitable filters. The steps that must be taken to maintain the integrity of the shield and to limit conducted interference are explained fully in subsection 4.6. 4.2 Inspection ---------------- Emulex products are shipped in special containers designed to provide full protection under normal transit conditions. Immediately upon receipt, the shipping container should be inspected for evidence of possible damage incurred in transit. Any obvious damage to the container, or indications of actual or probable equipment damage, should be reported to the carrier company in accordance with instructions on the form included in the container. Unpack the QD21 subsystem and, using the shipping invoice, verify that all equipment is present. Verify also that model or part numbers (P/N), revision levels, and serial numbers agree with those on the shipping invoice. Subsection 1.4 explains model numbers and details kit contents. These verifications are important to confirm warranty. If evidence of physical damage or identity mismatch is found, notify an Emulex representative immediately. If the equipment must be returned to Emulex, it should be shipped in the original container. Visually inspect the QD21 Disk Controller after unpacking. Check for such items as bent or broken connector pins, damaged components, or any other evidence of physical damage. Examine all socketed components carefully to ensure that they are properly seated. 4.3 Disk Controller Setup --------------------------- Several configuration setups must be made on the QD21 Disk Controller before inserting it into the chassis. These setups are made by option switches SW1 and SW2. Figure 4-3 shows the locations of the configuration switches referenced in the following paragraphs. LED1 :LED2 ::LED3 旼쩡컴컴컴쩡컴컴컫컫쩟쩡컴컫커 � 읕컴컴컴좔컴컴켸 읕컴켸 � � J1 J2 SW1 � 넬컴컴컴컴커 旼컴커� 냅컴컴컴컴켸 읕컴켸� � J3 J5 � 넬컴컴컴풢FG 悶U29 � NOVRAM (U29) BUFFER 납 쿓JK 旼� 잎 � CONTROLLER 납 U30 � 쿞� PQR � 냉컴컴컴� 쿥� � HOST ADAPTER 납 U38 � �2� S � CONTROLLER 납 � 읕� T旼� � (HAC) 냅컴컴컴� 쿢� � FIRMWARE PROM (U44) � 旼� �4� � � 쿢� U�4� � � �4� V읕� � � �9� � 22-BIT IC (U49) 읏 읕� 悶 粕 읕컴컴컴컴컴켸읕컴컴컴컴컴켸 Figure 4-3. QD21 Disk Controller Assembly ============================================ NOTE If you change a switch position on the QD21, or change the configuration values in the NOVRAM, you must also reset the QD21 so that the host operating system's initialization sequence reads the codes established by the switch settings and/or NOVRAM. To reset the QD21, either toggle switch SW1-1 (ON then OFF), or power-down and power-up the the system. If you toggle SW1-1, be sure the system is offline. Resetting the coupler with the system running is likely to crash the system. Table 4-1 defines the function and factory configuration of all switches on the QD21 controller. The factory configuration switch settings are representative of most QD21 Disk Controller applications. Table 4-1. QD21 Switch Definitions and Factory Configuration 旼컴컴컴쩡컴컴컴컴쩡컴컴컴컴컴컫컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴커 � SW � OFF(0) � ON(1) � FACT � Function � Section � 쳐컴컴컴탠컴컴컴컴탠컴컴컴컴컴컵컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴캑 � SW1-1 � Run � Reset/Halt � OFF(0) � Runvs.Reset/Halt � � � SW1-2 � - � - � OFF(0) � MSCP Device Number (LSB) � 4.3.3.2 � � SW1-3 � - � - � OFF(0) � MSCP Device Number � 4.3.3.2 � � SW1-4 � - � - � OFF(0) � MSCP Device Number (MSB) � 4.3.3.2 � � � � � � � � � SW2-1 � Disable � Enable � OFF(0) � Loop on Self-Test Error � � � SW2-2 � Disable � Enable � OFF(0) � Automatic Bootstrap � 4.3.3.1 � � SW2-3 � - � - � OFF(0) � LSI-11 Bus Address � 4.3.1 � � SW2-4 � - � - � OFF(0) � LSI-11 Bus Address � 4.3.1 � � SW2-5 � - � - � OFF(0) � LSI-11 Bus Address � 4.3.1 � � SW2-6 � 18-bit � 22-bit � OFF(0) � 22-Bit Addressing � 4.3.3.3 � � SW2-7 � 4 usec � 8 usec � OFF(0) � DMA Burst Delay � 4.3.3.4 � � SW2-8 � Enable � Disable � OFF(0) � Adaptive DMA Mode � 4.3.3.5 � 쳐컴컴컴좔컴컴컴컴좔컴컴컴컴컴컨컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴캑 � ON(1) = Closed � � OFF(0) = Open � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 Table 4-2 lists the function and factory configuration of all jumpers on the controller. Table 4-2. QD21 Jumper Definitions and Factory Configuration 旼컴컴컴쩡컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴쩡컴컴쩡컴컴컴컴컴컴컴컴� 쿕umper � OUT � IN 쿑ACT � Comment � 쳐컴컴컴탠컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴탠컴컴탠컴컴컴컴컴컴컴컴� 쿌-B-C-D� Reserved � Reserved � � � � E-F-G � Not Used � Not Used � OUT � Must be OUT � � H-J-K � Not Used � Not Used � OUT � Must be OUT � � L-M-N � Reserved � Reserved � � � � P-Q � Disable Clock � Enable Clock � IN � Must be IN � � R � Normal Operation � Ground (Test)� OUT � Must be OUT � � S-T � 16K PROM � 32K PROM � IN � Rev E and above � � � � � OUT � Rev D and below � � U-V � Normal Operation � Factory Test � OUT � Must be OUT � 쳐컴컴컴좔컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴좔컴컴좔컴컴컴컴컴컴컴컴� � FACT = Factory Setting � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 4.3.1 Disk Controller Bus Address ----------------------------------- Every LSI-11 bus I/O device has a block of several registers through which the system can command and monitor that device. The registers are addressed sequentially from a starting address assigned to that controller, in this case an MSCP-class Disk Controller. The address for the first of the QD21's two LSI-11 bus registers is selected by DIP switches SW2-3 through SW2-5. See Table 4-3 for register address switch settings. For more information on determining the LSI-11 bus address, see Section 3 and Appendix A. Table 4-3. Controller Address Switch Settings 旼컴컴컴컴컴쩡컴컴컴컴컴쩡컴컴컴� � �--- SW2 ---� � 쿍us Address� 3 4 5 쿑actory� �(in octal) � � � 쳐컴컴컴컴컴탠컴컴컴컴컴탠컴컴컴� � 772150 � 0 0 0 � * � � 772154 � 1 0 0 � � � 760334 � 0 1 0 � � � 760340 � 1 1 0 � � � 760344 � 0 0 1 � � � 760350 � 1 0 1 � � � 760354 � 0 1 1 � � � 760360 � 1 1 1 � � 읕컴컴컴컴컴좔컴컴컴컴컴좔컴컴컴� 4.3.2 Interrupt Vector Address -------------------------------- The interrupt vector address for the QD21 is programmed into the device by the operating system during the MSCP initialization sequence. See subsection 3.5 for a discussion of vector addresses. 4.3.3 Options --------------- There are other QD21 options that can be implemented by the user. These features are selected by physically installing the option on the PCBA or by enabling the option using a switch. 4.3.3.1 Automatic Bootstrapping --------------------------------- The automatic bootstrapping option causes the system to boot automatically from logical unit 0 through 3 on power-up when the QD21 is at the standard base address. To enable this option, set SW2-2 ON and set switches SW1-2 through SW1-4 as described in Table 4-4. This option should not be enabled with a MicroVAX or in a system that uses an 11/73B CPU module. Switch � OFF � ON 쿑actory 컴컴컴컵컴컴컴컴탠컴컴컴컵컴컴컴� SW2-2 쿏isable � Enable � OFF The automatic bootstrapping process requires that the LSI-11 CPU module be configured for power-up mode 0. The following table lists the configuration settings for several popular LSI-11 CPUs. CPU � Configuration Setting 컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴컴컴 11/73A� Install W3 and W7 11/23+� Remove J18-J19 and J18-J17 11/23 � Remove W5 and W6 11/02 � Remove W5 and W6 If the bootstrap device is not powered-up or safe (e.g., it failed its self- test), the autoboot routine in the QD21 halts the CPU after 1 minute. This causes the CPU to enter Console ODT. You can then examine the Status and Address (SA) register (base address plus 2) for an MSCP error code (Table 5-3) and bootstrap the system from another device. You can bootstrap from a drive supported by a QD21 installed at an alternate LSI-11 bus address, using any boot process other than autoboot. In this case, be certain that the automatic bootstrap option is disabled (SW2-2 OFF). 4.3.3.2 MSCP Device Number ---------------------------- QD21 switches SW1-2 through SW1-4 specify MSCP device numbers. The functions of these switches are dependent on the options you select for your QD21: o If the QD21 is installed at the standard LSI-11 bus address, these switches identify the MSCP device number of the drive from which to bootstrap. The QD21 automatic bootstrap option supports only MSCP units 0 through 3 at the standard address. o If the QD21 is installed at an alternate LSI-11 bus address, these switches identify the MSCP device number of the first drive supported by that alternate QD21. The first drive supported by the QD21 at an alternate address may be drive 0 through 7. 4.3.3.2.1 Logical Unit to Boot From ------------------------------------- If the QD21 automatic bootstrapping option is enabled (SW2-2 ON) and the QD21 is at the standard LSI-11 bus address (772150), switches SW1-2 through SW1-4 define the MSCP device number of the drive from which the QD21 bootstraps. By using these switches, you may select one of four logical units to bootstrap from. Table 4-4 defines the MSCP device numbers selected by switches SW1-2 through SW1-4 if the QD21 is at a standard address. Table 4-4. Bootstrap MSCP Device Number 旼컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴커 � Bootstrap MSCP � ------- SW1 ------- � Factory � � Device Number � 2 3 4 � � � � (LSB) (MSB) � � 쳐컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴캑 � 0 � 0 0 0 � * � � 1 � 1 0 0 � � � 2 � 0 1 0 � � � 3 � 1 1 0 � � 읕컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴켸 4.3.3.2.2 First Logical Unit Number for an Alternate Address -------------------------------------------------------------- If your QD21 is installed at an alternate address, switches SW1-2 through SW1-4 select the MSCP device number of the first drive supported by the QD21. MSCP device numbering schemes may vary by DEC operating system (see subsection 3.4.2.2). Table 4-5 defines the MSCP device numbers selected by switches SW1-2 through SW1-4 if the QD21 is at an alternate address. Example 4-1: Your system operates under RSX-11M-PLUS and has two QD21 Disk Controllers. The first QD21 is at the standard base address for MSCP controllers (772150) and supports three logical drives: Unit 0, Unit 1, and Unit 2. The second QD21 is at an alternate base address and supports two logical drives. RSX-11M-PLUS requires that the first drive on the alternate QD21 have an MSCP device number of 3 and that the second drive have an MSCP device number of 4. On the alternate QD21, set switches SW1-2 in the ON position, SW1-3 in the ON position, and SW1-4 in the OFF position to specify a MSCP device number of 3 for the first drive. This example would also apply if the first MSCP controller were a DEC MSCP controller with three logical drives. Table 4-5. MSCP Device Number for the First Drive Supported by a QD21 at an Alternate Address 旼컴컴컴컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴컴� � Starting MSCP � ------- SW1 ------- � � Device Number � 2 3 4 � � � (LSB) (MSB) � 쳐컴컴컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴컴� � 0* � 1 0 0 � � 1 � 0 1 0 � � 2 � 1 1 0 � � 3 � 0 0 1 � � 4 � 1 0 1 � � 5 � 0 1 1 � � 6 � 1 1 1 � � 7 � 0 0 0 � 읕컴컴컴컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴컴� *Used to bootstrap a drive from the QD21 at an alternate LSI-11 bus address. 4.3.3.3 22-Bit Memory Addressing ---------------------------------- The 22-bit addressing capability is a standard option for the QD21 and is supplied with the QD21 as a kit, part number QD0111302. To enable 22-bit addressing, install the single 7438 IC in socket U49 on the QD21 PCBA and set SW2-6 ON (1). 22-bit addressing must be enabled with MicroVAX systems. CAUTION Some manufacturers of LSI-11 bus backplanes use the backplane lines now devoted to extended addressing for power distribution. Installing a QD21 with the extended addressing option in such a system will damage the option IC. Before installing the option, confirm that there is neither positive nor negative potential between lines BC1, BD1, BE1, BF1, and logic ground. A QD21 without the extended addressing option will not be damaged if power is present on those lines. 4.3.3.4 DMA Burst Delay ------------------------- The QD21 firmware design includes a switch-selectable DMA burst delay to avoid data-late conditions. Switch SW2-7 selects either a 4- or 8-microsecond delay between DMA bursts. Even with the QD21 adaptive DMA, some applications may require a longer burst delay to allow other devices adequate time on the bus. Switch� OFF � ON 쿑actory 컴컴컴탠컴컴컴컵컴컴컴컴탠컴컴컴 SW2-7 � 4 usec � 8 usec � OFF 4.3.3.5 DMA Adaptive Mode --------------------------- Depending on the other devices on the bus and their priority, the QD21 may use more or less bus time than optimal for your application. The QD21 allows you to modify its DMA operations by disabling adaptive DMA. If adaptive DMA is disabled, the host processor programs the DMA burst length to a maximum of 8 words per burst. When adaptive DMA is enabled (SW2-8 OFF), the QD21 monitors the LSI-11 bus for other pending DMA requests and suspends its own DMA activity to permit other DMA transfers to occur. If the QD21 is not getting the bus time your application requires, you may want to disable the adaptive DMA. When adaptive DMA is disabled, the QD21 performs a burst transfer of 8 words of less, relinquishes the bus, then performs another DMA burst transfer. Switch� OFF � ON 쿑actory 컴컴컴탠컴컴컴컴컴컴컵컴컴컴컴컴컴컴탠컴컴컴 SW2-8 � Enable � Disable � OFF � Adaptive DMA � Adaptive DMA � NOTE If you are using the QD21 with adaptive DMA enabled in a MicroVAX II subsystem, be aware that the CPU module uses DMA requests to gain use of the bus to service device interrupts and may interfere with the QD21's bus access. You may consider disabling adaptive DMA for improved throughput. 4.4 Physical Installation --------------------------- This section provides instruction for system preparation, slot selection, and mounting the QD21. 4.4.1 System Preparation -------------------------- To prepare your CPU to accept the QD21, use the following procedures: o MICRO/PDP-11 and MicroVAX I and II Preparation: 1. Power down the system by switching OFF the main ac breaker. 2. Remove the rear cover from the chassis so that the patch panel is exposed. The rear cover is held on by snap pads. Grasp the cover at the top and bottom, and pull straight back. 3. Loosen the captive screws from the patch panel using a standard screwdriver. 4. Remove the patch panel. 5. Find the flat-ribbon cable that connects the CPU module to the patch panel. For easier board installation, you may disconnect the CPU flat-ribbon cable from the patch panel. o LSI-11 Series Preparation: 1. Power down the system by switching OFF the main ac breaker. 2. Remove the cover from the chassis so that the backplane is exposed. Do not replace the covers or patch panels until the installation is verified (subsection 4.8). 4.4.2 Slot Selection ---------------------- The QD21 may be assigned to any desired slot because it uses the LSI four- level interrupt scheme to perform distributed interrupt arbitration. Be sure to find out whether your backplane is straight or serpentine and choose a slot accordingly. On straight backplanes, the QD21 must be plugged into connectors A and B, since connectors C and D carry no signals. On a serpentine backplane, the QD21 can be plugged into either connectors A and B or connectors C and D. There must be no unused slots, however, between the CPU and the QD21. If you have a DEC RQDX1 in your backplane, be sure to install the QD21 in front of the RQDX1; not all RQDX1 controllers pass grant signals. 4.4.3 Mounting ---------------- The QD21 Disk Controller PWB should be plugged into the LSI-11 backplane with components oriented in the same direction as the CPU and other modules. Always insert and remove the boards with the computer power OFF to avoid possible damage to the circuitry. Be sure that the board is properly positioned in the throat of the board guides before attempting to seat the board by means of the extractor handle. 4.5 ESDI Disk Drive Preparation ----------------------------------- The disk drive(s) must have an ID plug or address selection switches properly configured and the drive set for either hard or soft sectoring. If you are using hard sectored drives, remember that in the autoconfigure mode the drive sector setting is overridden by the set bytes per sector command from the controller. If you are using the NOVRAM values, the drive sectoring must be set to match the NOVRAM values. 4.5.1 Drive Placement ----------------------- Unpack and install the disk drives according to the manufacturer's instructions Install the disk drives in their final positions before beginning the installation of the QD21. This positioning allows the I/O cable routing and length to be accurately judged. 4.5.2 Sectoring ----------------- The QD21 supports both hard and soft sectored drives. The drive parameter tables in Appendix C recommend either soft or hard sectoring; set jumpers or switches as indicated in the drive manufacturer's manual. In general, if a drive is capable of both hard and soft sector format, hard-sectoring is preferred as long as the number of hard sectors does not reduce the possible drive capacity. 4.5.3 Drive Numbering ----------------------- A unique address must be selected for each drive. The logical unit number is determined by the address given to the drive. See subsection 3.2.2. Drive manufacturers use jumpers, switches, or ID plugs to select addresses. Consult the appropriate drive manual for the exact procedure. 4.5.4 Spindle Motor Spin-up ----------------------------- Most ESDI drives have a spindle motor control option which allows the the drive controller to control the timing of the drive spindle motor spin-up. Emulex recommends that you allow the QD21 controller to start the spin-up of the drive(s). If there is more than one drive, the QD21 issues the spin-up commands to each drive sequentially. This will minimize any power surge on multiple drive systems. 4.5.5 Termination ------------------- Terminator power is supplied by the drive. The terminated drive must therefore have power applied in order for termination to be effective. Otherwise, indeterminate results will occur. Only the last drive in the string is terminated. 4.6 Cabling ------------- The QD21 Disk Controller interfaces with each ESDI disk drive that it controls via one 34-line control cable and a 20-line data cable. The control cable originates from connector J3 on the QD21 and is daisy-chained to all of the supported drives, terminating on the last drive. Maximum cumulative cable length for the control cable is 10 feet (3 meters). The data cables originate from connectors J1 and J2 on the QD21; each data cable is connected directly from the QD21 to each supported disk drive. Maximum cable length for each data cable is 10 feet (3 meters). Emulex offers the QD21 Internal Cabling Kit (P/N QD2113001) which allows you to install the QD21 and the ESDI disk drive(s) in the CPU cabinet. Table 4-6 lists the components of this cabling kit; Figure 4-4 shows basic cable installation. In addition, Emulex offers the QD21 External Cabling Kit (P/N QD0113003) which allows you to install the QD21 in the CPU cabinet and the ESDI disk drives in a separate cabinet; instructions for installing this kit are described in the QD01/QD21 Cabling Kit Instruction Sheet (P/N QD0152401). Table 4-6. QD21 Internal Cabling Kit (P/N QD2113001) 旼컴쩡컴컴컴컴컴컫컴컴컴컴컴컴쩡컴컴컴컴컴컴컴컴컴컴커 쿜ty� Part Number쿎able Length� Cable Description � 쳐컴탠컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴컴컴컴컴컴캑 � 2 쿜U0111202-01� 3 ft �20-conductor, flat � � � � 쿐SDI data interface � � � � � � � 1 쿜U0111201-01� 1 ft �34-conductor, flat � � � � 쿐SDI control interface� � � � 쿭aisy-chain � � � � � � � 1 쿜U0111203-01� 1 ft �34-conductor, flat � � � � 쿐SDI control interface� 읕컴좔컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴컴컴컴컴컴켸 Table 4-7 lists the components that are required to construct both control and data cables. Table 4-7. Interface and Cable Components 旼컴컴컴쩡컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � � � Cable Components � 쿎nctr � Controller � Header Control Cable Type Drive � 쿙umber � Function � Type Cnctr Unshield Shielded Cnctr � 쳐컴컴컴탠컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿕3 � Control � 3594 3414 3801/34 3517/34 3463 � 쿕1/J2 � Data � 3592 3421 3801/20 3517/20 3461 � 쳐컴컴컴좔컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿎nctr = Connector � 쿌ll component numbers are 3M. Equivalents may be used. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 UNIT 0 CONTROL CABLE 旼컴컴컴컴컴� �袴袴袴袴袴袴袴袴袴袴袴袴袴藁袴袴袴袴袴袴냄 ESDI � QD21 � DATA CABLE � 넨 DISK � 旼컴컴컴컴컴컴崙풧1 旼컴컴컴컴컴컴캤컴컴컴컴컴컴�] DRIVE � � J3謎[탠컴컴컴컴켸 � 읕컴컴컴컴컴� 팠 읊[탠컴컴컴컴커 �(DAISY CHAINED)..TERMINATOR � 쿕2 � � 旼�:컴컴컴컴� 읕컴컴컴컴컴컴컴�