| United States-English |
|
|
|
![]() |
Configuring HP-UX for Peripherals: HP 9000 > Chapter 2 Configuring Interface Cards Selecting Device Drivers for Your Interface Cards |
|
The following sections describe each interface and their connectivity to peripherals. HP-UX multiplexers provide asynchronous data communication using protocols RS-232-C, RS-422, or RS-423 (depending on the card). All HP-UX computers are equipped with RS-232-C serial ports. Additional serial cards increase the number of connections possible between the SPU and terminals, modems, printers, and uninterruptable power system (UPS). Table 2-2 “Multiplexer Connectivity Configuration Requirements ” summarizes the scope of HP cards, architecture, and drivers available. It also identifies the distribution panels available for each serial card. Table 2-2 Multiplexer Connectivity Configuration Requirements
Distribution panels (DDPs, ADP/MDPs) can be used to expand the connectivity between serial interface card and peripheral device. Data communications and terminal controllers (DTCs) provide additional serial connectivity for local or remote devices directly to the LAN. These mechanisms are illustrated in Figure 2-2 “Serial Connectivity via Distribution Panels or DTC”. Table 2-3 “Distribution Panels ” summarizes the distribution panels and their capabilities. All distribution panels listed provide connectivity for terminals, printers, and plotters. Those with full duplex modem control provide connectivity for modems also. Table 2-3 Distribution Panels
Data communication and terminal controllers (DTCs) are stand-alone boxes that connect to the LAN to provide additional serial connections for local or remote devices. Unlike serial interface cards, which communicate directly with the core operating system, DTCs use Telnet-TCP/IP protocols to communicate with the peripheral devices. Therefore DTCs provide most, but not all, the same functionality. Two types of DTCs are available:
DTCs must be configured by one of two DTC software products, HP OpenView DTC Manager (HP part number D2355A) and HP DTC Manager/UX (HP part number J2120A), both of which can be used with HP-UX systems. Consult your HP Sales Representative for full information. For cabling purposes, serial devices may be thought of as Data Communications Equipment (DCE) or Data Terminal Equipment (DTE). Historically, DCEs were modems, and DTEs were whatever terminated the data path, typically a terminal at one end, and computer at the other. When transmitting remotely, the circuit may be shown diagramically as follows, with the active pins listed in Table 2-4 “DCE and DTE Pin Assignments ”.
Table 2-4 DCE and DTE Pin Assignments
Table 2-5 “RS-232-C Interconnections ” provides a quick reference to RS-232-C cabling between serial devices and an HP-UX system. Neither RS-422 nor direct CPU-to-CPU connections are tabulated. Table 2-5 RS-232-C Interconnections
The centronics (parallel) interface allows characters to transfer over multiple data lines, one bit per line. This results in faster speed than serial transmission and is preferred for configuring printers, plotters, and scanners. On Series 700 workstations, the centronics (parallel) interface is provided as a standard feature; Series 800 systems may have a parallel interface on the multi-functional I/O card (personality card) supplied standard with the computer or on an optional SCSI/Centronics interface card. Centronics is not supported on Series 800 CIO systems. Table 2-6 Centronics Configuration Requirements
When configuring an interface card to the EISA bus, the eisa device driver must be present in the kernel, that is, it must be listed in /stand/system. Because EISA is a set of services used by other interfaces, configuring EISA cards is done differently than for other HP-UX interfaces. Refer to Appendix A, "EISA Configuration," for detailed information on configuring EISA cards and using the /sbin/eisa_config utility. If you are adding a device to your system that you plan to use as a primary swap device, and the device will be connected to an EISA card, you must perform the task in the following order:
The following table shows the driver and device special files used by graphics cards and subsystems. Table 2-7 Graphics Card Configuration Requirements
During system bootup, ioinit creates the default device special files shown in this table when it encounters the framebuf driver. If for any reason these device files are insufficient for your purposes, you can create new ones using mknod. As shown in /usr/conf/master.d/core-hpux, the major number for framebuf (the driver that provides the additional graphics capability) is 174. A character (raw) device special file is required. Use the bit assignments shown for graph3 interface driver in Table C-5 in Appendix C of this manual. Graphics capabilities can be enhanced by installation of any of a growing family of cards and subsystems. Table 2-8 “Graphics Enhancement Capabilities” is intended only to give a rough idea of the possibilities available on HP workstations. Consult your HP Sales Representative for information targeted to your specific needs. Table 2-8 Graphics Enhancement Capabilities
Any time you modify your graphics configuration, be sure to update the configuration files used by your application programs. For example, if you are adding a CRX24 (or CRX48) and using it as a console, you must
The HP-FL interface, based on fiber-optic technology, is used where radio-frequency interference poses problems or for high security since communication between the SPU and disks transmit without radiated signals. HP-FL is suited to large-disk configurations, particularly when the SPU is distant from the source of data. HP-FL is not supported on Series 700 computers. Table 2-9 HP-FL Interface Cards and Configuration Requirements
Peripheral devices (such as disks) connect to the HP-FL interface port via fiber-optic link (up to 500 meters). The HP-FL peripheral devices themselves are daisy-chained to one another using electrical PBus cables. This is shown in Figure 2-3 “HP Fiber-Optic Connectivity”. Fiber-optic cable can be ordered from Hewlett-Packard to custom length; specify HFBR-AWSxxx, where xxx is the length in increments of one meter from 001 to 500 meters.
The Hewlett-Packard Interface Bus (IEEE Standard 488-1980) provides connectivity for up to four peripherals on the same card, including disks, cartridge tape subsystems, magnetic tape units, plotters, and printers. Table 2-10 HP-IB Configuration Requirements
Two Series 700 EISA HP-IB cards, E2070A and E2071B, are available for instruments. Both use drivers that are packaged as part of the Standard Instrument Control Library (SICL) and a graphical processing environment (VEE-TEST). See your HP Sales Representative for information on these products. For Series 800 HP-IB cards only, you can access the entire card and all activity on the HP-IB bus by including the instr0 driver in your kernel. For example, you can set medium or fast signal transmission on the HP-IB bus using the instr0 driver. (Disks and tape drives require high-speed signal transmission, while printers and plotters require medium speed.) For specification of the I/O controls, consult the hpib(7) manpage of the HP-UX Reference. An HP-IB device can be cabled directly to its port on the back of the computer, or to other HP-IB devices only in a daisy-chained arrangement. HP-IB cable is available in the following lengths:
Cabling of medium-speed devices is limited to two meters per device or 20 meters total, whichever is less. Cabling of high-speed devices is limited to one meter per device or 10 meters total, whichever is less. Transmission distance between an HP-IB interface and peripheral devices can be extended to a maximum of 1.25km using the HP 37204A Multipoint HP-IB extender with coaxial or fiber-optic cable. Consult your HP Sales Representative for information. HP Series 700 and 800 systems shipped with LAN ports on the personality (multi-functional) or core I/O boards provide network access through AUI LAN, ThinLAN, or EtherTwist. (Note, the two ports on the standard LAN personality card are mutually exclusive; you can use either, but not both ports simultaneously.) Additional networking options are available for HP-UX systems. Table 2-11 “Network Interfaces and initial Configuration Requirements” summarizes their initial configuration requirements. All network products require a layered set of software — links, transports, and services — whose details fall beyond the scope of this book. Consult networking documentation for further information. Table 2-11 Network Interfaces and initial Configuration Requirements
Small Computer System Interface (SCSI) is an ANSI standard for connecting computers and peripheral devices. HP Series 700 and 800 computers support three implementations of SCSI-2, as shown in Table 2-12 “Types of SCSI and Characteristics ”. Table 2-12 Types of SCSI and Characteristics
Table 2-13 “SCSI Configuration Requirements ” lists HP SCSI cards, the architecture on which they are supported, and the configuration requirements of the cards and attached SCSI devices. Table 2-13 SCSI Configuration Requirements
Up to seven single-ended SCSI or fifteen fast-wide SCSI devices can be configured to a single SCSI device adapter. Each device requires a unique bus address.
Although most peripheral devices require only one address, the Optical Disk Library System (HP C17xxA) uses three SCSI addresses (two for the magnet-optical drives and one for the autochanger picker). Multiple SCSI peripheral devices can be connected to a single SCSI interface using a daisy-chain configuration. The final SCSI device in the daisy chain requires the proper terminator, discussed later in "SCSI Signal Termination."
Table 2-14 SCSI Cables
Cabling options can be ordered for the HP fast/wide/differential host adapter (HP 28696A) to extend standard cabling and for SwitchOver configurations (V-cables, male-male-male to daisy-chain multiple hosts). Table 2-15 “Fast/Wide SCSI Cables” show additional cables available to connect a Fast/Wide SCSI adapter-to-peripheral or peripheral-to-peripheral. Table 2-15 Fast/Wide SCSI Cables
The HP 28643A SCSI Fiber-Optic Extender overcomes SCSI distance limitation to a maximum of 100 meters. Note, however, this device is single-ended SCSI and is recommended for printers, optical libraries, and magnetic tape drives only. It is not supported for SwitchOver configurations. SCSI cable impedance and construction have a significant impact on signal quality; use only HP cables. Table 2-16 “Example of SCSI Cable Length Calculation” demonstrates how to calculate SCSI bus cable lengths for a typical installation. Table 2-16 Example of SCSI Cable Length Calculation
All devices must be connected to a common (single point) system reference ground. The system ground must be isolated from other electrical devices such as copying machines, arc welders and air conditioners. Cables supplied by HP have correct grounding. Make sure there are no unterminated cables (that is, that all cables are attached to a device at both ends). Because a closed loop is required by the SCSI bus for successful signal transmission, the last SCSI device in the chain must have a terminator installed on its second connector. The terminator is (or acts as) a small resistor that provides matching impedance on the bus circuit. Without such termination, data traveling on the bus is likely to be corrupted and the protocol upset to the point that it hangs the bus. Some devices (particularly host adapters) contain internal SCSI bus terminators or require special terminators. If two devices supply termination power, locate them at each end of the SCSI bus. Refer to the specific hardware manuals of host adapters and the devices on the bus for instructions on how to prevent excessive or improper SCSI bus termination.
All HP SCSI products are shipped with appropriate terminators. Table 2-17 “SCSI Terminators ” might be helpful if you need to order additional termination. Table 2-17 SCSI Terminators
All devices on a SCSI bus must be consistent in parity-checking capability. If any device on the SCSI bus does not generate parity, all devices on the bus, including the adapter, must not check parity. (Although parity-checking is selectable, the adapter always generates parity.) If a SCSI device cannot match the parity-checking capability of other devices on the bus, it must be installed on a separate SCSI bus.
Use of non-Hewlett-Packard peripherals is not supported by Hewlett-Packard's standard support process. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||