Configuring HP-UX For Peripherals HP 9000 Computers Manufacturing Part Number: B2355-90698 November 2000 © Copyright 2000 Hewlett-Packard Company 1
Notices Use of this document and flexible disc(s) or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs can be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited. This document contains information which is protected by copyright. All rights are reserved.
This software and documentation is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. Copyright ) The Regents of the University of Colorado, a body corporate 1979 This document has been reproduced and modified with the permission of the Regents of the University of Colorado, a body corporate. Copyright ) 1980, 1984, 1986 Novell, Inc. Copyright ) 1986-1992 Sun Microsystems, Inc.
Contents 1. Getting Started Peripheral Configuration in its Simplest Terms . . . . . . . . . . . . . . . . . . .17 Using SAM to Configure Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . .18 Using HP-UX Commands to Configure Peripherals. . . . . . . . . . . . . . .18 Understanding I/O Convergence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Understanding Loadable Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . .21 DLKM Module Types . . . . . . . . . . . . . .
Contents Analyzing Critical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLAR Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamically Loadable Kernel Modules (DLKM) . . . . . . . . . . . . . . . . How to On-Line Replace (OLR) a PCI card using rad . . . . . . . . . . . . How to On-Line Add (OLA) a PCI Card using rad . . . . . . . . . . . . . . . 48 49 53 54 60 3.
Contents Running Screen-Oriented Applications on a Terminal . . . . . . . . . . .113 Configuring a Non-HP Terminal as a Console . . . . . . . . . . . . . . . . . .113 Additionally Configuring HP-UX for a Modem . . . . . . . . . . . . . . . . . . .123 Requirements for Modems to Work on HP-UX . . . . . . . . . . . . . . . . . .126 Removing or Moving a Terminal or Modem . . . . . . . . . . . . . . . . . . . . . .128 Troubleshooting Terminal Problems . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Removing a Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Finding Out the Disk Model Number and Other Information . . . . . . 169 After Configuring HP-UX for the Disk Device . . . . . . . . . . . . . . . . . . . 170 6. Configuring Magneto-Optical Devices Planning to Configure a Magneto-Optical Device . . . . . . . . . . . . . . . . 172 Characteristics of Magneto-Optical Devices . . . . . . . . . . . . . . . . . . .
Contents Selecting Device Drivers for Your Printer or Plotter . . . . . . . . . . . . . . .199 Guidelines for Configuring a Printer or Plotter to a Serial . . . . . . . .199 Guidelines for Configuring a Printer or Plotter to a Parallel . . . . . .203 Guidelines for Configuring a Printer to a SCSI Interface . . . . . . . . .205 Configuring a Printer Using HP-UX Commands. . . . . . . . . . . . . . . . . .206 Creating a Device Special File for a Printer or Plotter . . . . . . . . . . .
Contents Moving an E/ISA Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Removing an E/ISA Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Creating Identical E/ISA Configurations on Other Workstations . . 245 Troubleshooting E/ISA Board Configuration . . . . . . . . . . . . . . . . . . . . Verifying the Syntax of a CFG File . . . . . . . . . . . . . . . . . . . . . . . . . . Board Stops Working or No Non-Volatile Memory (NVM) Driver . .
Contents Associating a Custom Driver with a Peripheral . . . . . . . . . . . . . . . . . .284 Creating Device Special Files using mknod . . . . . . . . . . . . . . . . . . . . . .288 D. Worksheets Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290 Terminals and Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Disk Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 12
Printing History The document printing date and part number indicate the document’s current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number will change when extensive changes are made. Document updates may be issued between editions to correct errors or document product changes.
Getting Started 1 Getting Started Before physically installing a disk drive, tape drive, printer, or other peripheral device, you must configure the HP-UX operating system to communicate with it. Configuring HP-UX for Peripherals provides the software information needed for system administrators to configure the many peripheral devices supported on HP-UX.
Getting Started interface cards are not supported by HP-UX Release 11.0. All such devices should be removed from your system before installing or updating to HP-UX Release 11.0.
Getting Started Peripheral Configuration in its Simplest Terms Peripheral Configuration in its Simplest Terms You must perform the following three steps before a peripheral device can communicate with an HP-UX system: Step 1. Configure the device driver(s) into the kernel. Device drivers are like translators that speak both the language of the peripheral device and the language of the computer. Step 2. Install the hardware.
Getting Started Peripheral Configuration in its Simplest Terms NOTE Often, if you anticipate having to add a new external peripheral device, you can configure the device drivers into the kernel at a time when no one else is on the system. Then, when the peripheral arrives, you can physically install it with minimal user disruption.
Getting Started Peripheral Configuration in its Simplest Terms and terminals are configurable automatically. Each peripheral-specific chapter of this document gives procedures for using HP-UX commands for configuration. Exceptions: Drivers insf Cannot Recognize Third-party drivers and certain drivers used for instrumentation or black-box applications are not recognized by insf, so insf cannot automatically create device files during the reboot process.
Getting Started Understanding I/O Convergence Understanding I/O Convergence As of HP-UX Release 10.0, the HP-UX I/O system is largely converged, allowing for an environment that supports a greater flexibility of bus architectural combinations. The convergence is seen most dramatically on Model K (8x9) systems, which have capabilities previously found only on Series 700 workstations.
Getting Started Understanding Loadable Device Drivers Understanding Loadable Device Drivers As of HP-UX Release 11.0, a new feature known as Dynamically Loadable Kernel Module (DLKM) provides the means to add a device driver to a running UNIX system without rebooting the system or rebuilding the kernel. This feature also makes it possible to dynamically remove a device driver from the UNIX system when the driver is no longer needed, thereby freeing system resources for other use.
Getting Started Understanding Loadable Device Drivers files, and the config (1M) manpage for a description of the HP-UX system file.
Getting Started Understanding Device Special File Names Understanding Device Special File Names Device special files tell the operating system which device driver to use, how to find the peripheral device, and what characteristics the peripheral device should employ. Characteristics vary by device. Thus, device special files for magneto-optical devices show the surface being addressed, while those for tape drives show rewind and density.
Getting Started Understanding Device Special File Names represents the entire disk, while section 2 represents a small disk section (previously section 0). If the s# is not shown, the device special file refers to the entire disk. Sample Device Special File Names Every peripheral-specific chapter in this document has tables of configuration requirements that show the default device special file names for that class of device.
Getting Started Understanding Device Special File Names is connected. These are discussed in the next sections. Decoding Device Special Files with lssf Use the /usr/sbin/lssf command to decode device special files. The following figure compares ll and lssf output. NOTE Throughout this document, examples of commands usage are shown as command text.
Getting Started Viewing the System Configuration with ioscan Viewing the System Configuration with ioscan The /usr/sbin/ioscan command is the single most versatile tool in HP-UX for displaying your system configuration. For example, you can use ioscan to identify available hardware addresses. Terse Listing of ioscan In its simplest form, /usr/sbin/ioscan displays hardware path, device class, and description.
Getting Started Viewing the System Configuration with ioscan The length of these numerical sequences differ by system model and architecture, but every hardware path leads you through the bus structure, starting from the bus closest to the system processor and ending at the output device. ioscan -H hardware_path shows you the sequence of connection to or from the specified location.
Getting Started Viewing the System Configuration with ioscan engineer. Full Listing of ioscan ioscan -f displays full information about the system configuration, including instance number, device/interface driver, software state, and hardware type. The -fn option also displays the device special files. /usr/sbin/ioscan -f Class I H/W Path Driver S/W State H/W Type Description ======================================================================== ...
Getting Started Viewing the System Configuration with ioscan The card instance number is assigned by the operating system to the interface card and reflects the order ioconfig binds that class of interface card to its driver when it boots. Instance is stored in two files — /etc/ioconfig and /stand/ioconfig. Information in these files retain their information across reboots, unless one is corrupted or missing, in which case, ioinit will rebuild the entire /dev structure.
Getting Started Viewing the System Configuration with ioscan Identifying Device Special Files Associated with a Peripheral Device You can use ioscan -fn (or -fkn or -fun) to show device special file names associated with a peripheral. You can also add other ioscan options (such as -H, -C, -d, or -I) to limit your output to specific elements in your configuration. The following example, using -C tape, shows the device files available for tape class, as well as the location and type of tape device.
Getting Started Configuring HP-UX for any Peripheral (A Summary) Configuring HP-UX for any Peripheral (A Summary) Prepare by gathering information required for the successful configuration of the peripheral. Considerations vary and are discussed in each peripheral-specific chapter.
Getting Started Configuring HP-UX for any Peripheral (A Summary) (1M) and kmtune (1M) in the HP-UX Reference. c. Build the new kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing. /usr/sbin/mk_kernel -s /stand/build/system d. Save the old system file by moving it. Then move the new system file into place. mv /stand/system /stand/system.prev mv /stand/build/system /stand/system e. Prepare for rebooting by invoking the kmupdate command.
2 Managing PCI Cards with OLAR This chapter contains the procedures for adding and replacing PCI cards using OLAR using SAM and rad along with concepts common to both.
Managing PCI Cards with OLAR How is the information in this chapter structured? How is the information in this chapter structured? This chapter has been split into three sections. This divides the material in a way that is suitable for testing: 1. SAM and rad (general information for either category) This contains PCI Card OLAR Overview and Concepts. 2. SAM Procedures • How to On-Line Replace (OLR) a PCI Card using SAM • How to On-Line Add (OLA) a PCI Card using SAM 3.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts PCI Card OLAR Overview and Concepts Introduction The letters O, L, A and R stand for On Line Addition [and] Replacement. This, of course, refers to the ability of a PCI I/O card to be replaced (removed and/or added) to an HP-UX computer system designed to support this feature without the need for completely shutting down, then re-booting the system or unnecessarily affecting other system components.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts Table 2-1 IMPORTANT Terms used in this section Term Meaning target card / target card slot The interface card which will be added or replaced using OLAR, and the card slot it resides in. affected card / affected card slot Interface cards and the card slots they reside in which are in the same power domain as the target slot. Currently multi-slot power domains are not implemented.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts Card Compatibility On-Line Addition (OLA) When on-line adding an interface card, the first issue that must be resolved is whether the new card is compatible with the system. Each OLAR-capable PCI slot provides a set amount of power. The replacement card cannot require more power than is available. Current systems have only one slot per bus with sufficient power. The card must also operate at the slot’s bus frequency.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts potentially conflict with the current driver. If a new card is not acceptable, SAM or rad will report that the card cannot be resumed. • During the replacement process, the driver instance for each port on the target card runs in a suspended state. I/O to the ports are either queued or failed while the drivers are suspended. When the replacement card is brought on-line, the driver instances resume normal operation.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts automatically, and presents options to you based on it’s findings. If critical resources will be affected by the procedure, you can replace the card off-line, or you can use either rad or SAM to perform an on-line addition of a backup card that can then be configured as a backup, and then replace the target card.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts OLAR Scripts At various stages throughout most OLAR procedures, SAM may initiate certain actions that notify the system of the addition or replacement of an interface card. • These actions are contained in OLAR scripts, which are developed by software driver engineers and based on the application or system requirements for the target interface card.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts encounters errors are encountered, it will attempt to resume operations at the point where it started. Post OLAR (Post Operations) Scripts Post-OLAR scripts are run by SAM just after a PCI card is added or replaced, and initialized. These scripts contain the necessary instructions to bring the replaced card into service before activity to and from the device is actually started or re-started.
Managing PCI Cards with OLAR PCI Card OLAR Overview and Concepts Virtual Ports Some driver designs create “virtual” ports that do not directly correspond to any physical hardware. Virtual ports can normally be identified by the driver that controls them. For example, HP Fibrechannel Mass Storage card drivers create virtual ports with drivers named “fcp”, “fcpdev”, “fcparray”, and “fcpmux” to control different aspects of the fibrechannel mass storage network to which they are attached.
Managing PCI Cards with OLAR How to On-line Replace (OLR) a PCI Card using SAM How to On-line Replace (OLR) a PCI Card using SAM Step 1. Start SAM. Step 2. From the SAM Areas screen, select Peripheral Devices. Step 3. From the Peripheral Devices screen, select Cards. Step 4. From the I/O Cards screen, view the list of available I/O cards. Click once on the card you wish to replace to select it, which will highlight the entire line that contains the card. Step 5. From the Menu bar, select Actions. Step 6.
Managing PCI Cards with OLAR How to On-line Replace (OLR) a PCI Card using SAM Table 2-2 Three Possible Critical Resource Analysis (CRA) Outcomes Outcome Notes Screen Displays Buttons Activated User Actions Critical resource(s) identified. SAM will not allow the operation to proceed. Detailed message describing the affected critical resource. Cancel Click “Cancel” to halt the operation with no change to the system Other resources identified.
Managing PCI Cards with OLAR How to On-line Replace (OLR) a PCI Card using SAM On-Line” menu item. Step 13. Replace the target card. The exact procedure for doing this will depend on what system class you have. Please refer to the hardware manual for your system for detailed information. Step 14. At this point, the amber LED should still be activated, and the green power LED should still be off. Return to the console, and click the “OK” button on the Replace Card dialog. Step 15.
Managing PCI Cards with OLAR How to On-line Add (OLA) a PCI Card using SAM How to On-line Add (OLA) a PCI Card using SAM Step 1. Read the information (below) in this step. An understanding of this section is important in order for you to make the correct decision(s) later in the procedure. You have two choices when performing an on-line add. Method 1: 1. Enter the I/O Cards area of SAM. 2. Insert the card into an empty, powered-off slot, then enter SAM. • Select “Actions->Add”.
Managing PCI Cards with OLAR How to On-line Add (OLA) a PCI Card using SAM finds. NOTE At this point, the OLA is complete. Note that in some cases additional configuration in another area of SAM may also be required. A network interface card, for example, might require network parameter setup in the Network Interface Card portion of the Networking and Communications area. After adding a card, SCSI host bus adapters are configured with default values for parameters, such as SCSI ID.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line Performing OLAR procedures from the command line This Critical Resource Analysis feature is not available from the command line (rad), so it is the responsibility of the engineer or system administrator to ensure that other system services are not interrupted during OLAR command line procedures. • Extreme care should be taken when using rad, since the command will, in most cases, attempt to complete the operation.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line which checks all ports on the target card for critical resources that would be temporarily unavailable while the card is shut down. This feature is not available from rad, so it is the responsibility of the engineer or system administrator to ensure the safety of the OLAR process.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line strongly recommends using SAM to perform OLAR operations. OLAR Script Location and Identification OLAR scripts reside in the following directory: /usr/sbin/olrad.d and are identified by the driver name. OLAR Scripts are identified by the driver name. Therefore, if the ioscan(1M) command indicates the driver associated with a device is named driver1, then the script associated with the device will be named driver1.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line Pref-OLAR scripts return “0” (for “YES”) or “1” (for “NO”). • If “0” is returned, you may continue with the remaining steps. • IF “1” is returned, the script will also display a message on stderr. Depending on the implications of the message, the user may abort, or continue with the remaining steps.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line Post-OLAR scripts accept the following parameters: • Execute action • Hardware path of I/O node For example: # sh/usr/sbin/olrad.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line Dynamically Loadable Kernel Modules (DLKM) DLKM provides the ability to auto load software drivers. When a DLKM-based driver is installed on a system, that driver is registered with, and configured into the system (kernel). The driver can be force loaded, demand loaded, or auto loaded. • In the first case, the behavior is similar to static drivers in that the driver is always loaded into the kernel upon system boot.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line How to On-Line Replace (OLR) a PCI card using rad Step 1. Before replacing an interface card in a system, consider the following impacts that doing so will have on a system, and review the applicable topics within the section “Planning and Preparation” for detailed information: • Ensure that you understand if the target card is a multi port card. Step 2. Obtain the ID of the slot which hosts the card you are replacing.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line or otherwise save or print the output of the rad -q command. Step 3. Verify that the target card slot reported by rad is consistent with the physical slot label on the server for the target card: a. Set the target card slot to it’s ATTENTION state, which will cause the amber LED located next to the card slot to flash: # rad -f attention slot_ID where slot_ID is the slot field returned by the rad -q command b.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line This command will report all I/O nodes on the target card. Step 6. Check for an OLAR prep_replace script in /usr/sbin/olrad.d/ If the driver requires no preparatory action, then no script will be present. Refer to the section “OLARD Scripts” for detailed information regarding the name, location and purpose of the use of OLARD scripts. If the script is present, perform the following steps: a.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line the amber attention LED is still flashing so that the suspended card can be more easily located on the system chassis. Step 9. Replace the target card: a. Prepare the PCI I/O card cage for card removal: 1. Remove the front bezel 2. Extend the SPU out the back of the cabinet 3. There are two PCI I/O card cages in the SPU, a left-hand side and a right-hand side.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line 3. Insert the SPU back into the cabinet. 4. For PCI I/O cards on the left-hand side of the SPU, you may need to re-install the rear door Step 10. Turn on power to the target slot(s): # rad -i slot_ID If the target slot is successfully powered on, the command prompt is returned and the slot’s green power LED turns on. Step 11.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line If the script is present, run it as follows: # sh /usr/sbin/olrad.d/drivername post_replace hw_path CAUTION In many cases, post-replacement scripts will contain commands to automatically download firmware patches and/or upgrades for an interface card.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line How to On-Line Add (OLA) a PCI Card using rad Step 1.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line physical slot label on the server for the target card: a. Set the target card slot to it’s attention state, which will cause the amber LED located next to the card slot to flash: # rad -f attention slot_ID where and slot_id is the number returned by the rad -q command b.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line confirm suspension. Enter Y to continue. For example: The following interface driver I/O node(s) will be suspended: 0/12/0/0 c720 Do you wish to continue(Y/N)? Y # rad returns the command prompt upon successful suspension of the driver. If for some reason the driver instance cannot be suspended, rad outputs an error message to console. Step 7.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line 1. Replace the PCI cover plate 2. Connect the appropriate I/O cable to the installed PCI card 3. Insert the SPU back into the cabinet 4. For PCI I/O cards on the left-hand side of the SPU, you may need to re-install the rear door Step 9. Turn on power to the target slot(s): # rad -i slot_ID If the target slot is successfully powered on, the command prompt is returned and the slot’s green power LED turns on. Step 10.
Managing PCI Cards with OLAR Performing OLAR procedures from the command line # sh /usr/sbin/olrad.d/drivername post_add hw_path b. If you determined that the target slot is in a power domain with any other slots, run the post_add script for them also (not implemented in this release). Step 13. Set the target card slot’s attention LED to its OFF state # rad -f attention slot_ID where slot_id is the slot field returned by the rad -q command Step 14. Notify users and applications of resource availability.
Configuring Interface Cards 3 Configuring Interface Cards Configuring an interface card or device adapter may provide new connectivity to external devices or instruments. For this connectivity to occur, the interface driver for the card must be present in the kernel. When the system is booted, HP-UX associates the driver (software module) with the card (hardware path) to provide communication for the external device or instrument.
Configuring Interface Cards Planning to Configure an Interface Card Planning to Configure an Interface Card • Read the instructions to be sure you understand them before proceeding. Have available the documentation supplied with the interface card. • Observe anti-static precautions when handling interface cards. Interface cards and device adapters are susceptible to damage by electrostatic discharge, which can result in degraded performance or loss of operation.
Configuring Interface Cards Planning to Configure an Interface Card — Keep a current copy of output from /usr/sbin/ioscan -f, for a total picture of your system's configuration, including use of hardware slots and configured device drivers. NOTE The HP Precision Bus (HP-PB) backplane is a slot-priority based system. The higher the slot number in which a card is installed, the higher the card's priority for gaining access to and communicating over the backplane.
Configuring Interface Cards Planning to Configure an Interface Card device- and platform-dependent, the following information represents basic guidelines only. For detailed information, contact an HP Customer Engineer or field office, which should have access to recent information published in the HP 9000 configuration and price guides.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Selecting Device Drivers for Your Interface Cards The following sections describe each interface and their connectivity to peripherals. Asynchronous Data Communication Configuration Guidelines 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.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-2 Multiplexer Connectivity Configuration Requirements Card Ports, Protocol Architecture Device Drivers Available Port Modules J2092A 16-port RS-232-C f HP-PB mux2e DDP 5062-3066 DDP 5181-2085 RJ45 0950-2431 J2093A 32-port MUX RS423 or RS422 g HP-PB mux2e DDP 5062-3066 DDP 5181-2085 RJ45 0950-2431 J2094A 16-port MUX RS-232-C h HP-PB mux2e MDP 5062-3054 J2096A 32-port MUX RS-232-Cf HP-PB mux2e DDP 5
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-2 Multiplexer Connectivity Configuration Requirements Card J2593A Ports, Protocol 64-port MUX PCI Architecture A-class, L-class N-class, V-class, Models B/C/J Device Drivers Available Port Modules pci_mux0 RJ45 J2484A DB25 J2485A RJ45 J2501A a. Specifying mux0 causes cio_ca0, sio, pfail, and pa to be included in the kernel. b.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Figure 3-2 Serial Connectivity via Distribution Panels or DTC Table 3-1, “Maximum Recommended Device Connections by Interface,” 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.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-3 Distribution Panels Model Type of Distribution Panel Compatible Protocols Complexity No. of Ports & Connectors Form Factor Duplex Modem Control 5062-3085 Active (ADP) RS-422b added logic 8 DB25 female 10.25 x 4.25in. yes 5181-2085 Direct (DDP) RS-232-Ca RS-423b pass-thr ough 8 DB25 female 19in. rackmount no 28659-60005 Modem d RS-232-Ca added logic 6 DB25 female 8.5 x 4in. yes a. b. c. d.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards 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. RS-232-C Cabling Guidelines For cabling purposes, serial devices may be thought of as Data Communications Equipment (DCE) or Data Terminal Equipment (DTE).
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-5 RS-232-C Interconnections Host Computer Connection a Device Connection Cable Suggested DTE-4F DTE-25M 92219T + 92224F adapter DTE-9F DCE-25F 92221M, or 98561-61604 + 40242M DTE-9F DTE-25F 92221P, or 98561-61604 + 40242G DTE-9F DTE-25M 98561-61604 + 40242C DTE-9M DCE-25F 24542M, or 98574-61606 + 92221M, or 98574-61606 + 98561-61604 + 40242M DTE-9M DTE-25F 24542G, or 98574-61606 + 92221P, or 98574-6160
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards a. F denotes female receptacle; M, male plug. 4 denotes USOC RJ-11C connector (as on contemporary consumer telephones), 9 denotes 9-pin DB-0 subminiature D-style connector, 25 denotes 25-pin DB-25 subminiature D-style connector, 50 denotes 50-pin amp "blue ribbon" D-style connector.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards you must perform the task in the following order: Step 1. Shut down the system without changing the kernel (still swapping to the original swap device). Step 2. Add the EISA card and connect the new device. Step 3. Boot the system, which is still swapping to the original swap device. Step 4. Configure the kernel to swap to the new EISA device. Step 5. Reboot the system. Step 6.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards character (raw) device special file is required. Use the bit assignments shown for graph3 interface driver in Table C-5, “Bit Assignments for Disk and Magneto-Optical Devices,” in Appendix C , “Major and Minor Numbers,” of this document. Graphics capabilities can be enhanced by installation of any of a growing family of cards and subsystems.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-8 Graphics Enhancement Capabilities Product Compatibility Provision A2673A CRX-24 subsystem Model 715 or 725 EISA Upgrades to CRX-24 configuration. A2674A 24-bit Z Buffer and Graphics Accelerator Model 715 or 725 Upgrades a color workstation to a CRX-24Z configuration. A2675A CRX-48Z subsystem Model 715/50 or 725 EISA Upgrades to CRX-48Z configuration.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Graphics Cable Extensions The following extensions are available for placing the CRT a distance away from the SPU: 46082A/B RGB extension 46080/81A HIL extension 1250-1287 Use three of these connectors to extend RGB cable for a Model 712. There is no PS/2 keyboard or mouse extension available for the Model 712.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards either, but not both ports simultaneously.) Additional networking options are available for HP-UX systems. Table 3-9, “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 document. Consult networking documentation for further information.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Bus Architecture Card Supported Models J2794A X.25 Streams B-class, C-class, J-class, D-class and Series 700 EISA lapb x25plp x25sentry x25idmap plp2llc2 trcl2 trcl3 synchal sxb sxbclone wan eisaxb J2815A X.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Bus Architecture Card Supported Models J3526A X.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Card Supported Models Bus Architecture Drivers A3722A FDDI K-class, T600-class HSC fddi3 A3723A FDDI D-class, B-class, C-class, J-class HSC fddi3 A3739A FDDI V-class, N-class, B-class, C-class, J-class PCI fddi4 J2165A HP TokenRing 9000 Series 700 EISA token1 J2166A HP TokenRing 9000 Series 800 HP-PB token2 A5783A PCI TokenRing A-class,
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Bus Architecture Card Supported Models J2792A SNAplus2 Link E/F/G/H/I-class, K-class, and T890 HP-PB psi0 sna_router sna_trace sna_access sna_NODE sna_SDLC sna_QLLC sna_LAN J2794A SNAplus2 Link B/C/J-class, Series 700, and D-class EISA psi0 sna_router sna_trace sna_access sna_NODE sna_SDLC sna_QLLC sna_LAN A5783A SNAplus2 Link N-class and V-class PCI
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Card Supported Models Bus Architecture A3526A SNAplus2 Link (SDLC only starting R6.1100.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Card Supported Models Bus Architecture Drivers J3573A ATM D-class, R380, R390 HSC atm2gsc J3557A ATM V-class PCI atmpci A4919A Hyperfabric V-class PCI clic A4920A Hyperfabric K-class HSC clic A4921A Hyperfabric D-class HSC clic A5506A 4-Port 100Base-TX A-class, R-class, N-class PCI btlan B5509A A5230A 1-Port 100Base-TX A-class, B/C/J
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Bus Architecture Drivers D-class, B/C/JR-class HSC btlan4 J3515A 1-Port Fast Ethernet D-class, B/C/J/R-class HSC btlan4 A3495A 1-Port 100Base-TX E/G/H/I/K-class, T500/T520/T600 HP-PB btlan1 A3658A 1-Port 100Base-TX D-class, B/C/J-class EISA btlan0 A4308B 1-Port 100Base-TX Series 700 EISA btlan0 A4926A Gigabit Ethernet V-class, B-class, C-cla
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-9 Network Interfaces and Initial Configuration Requirements Card Supported Models Bus Architecture Drivers A3740A Fibre Channel V-class, N-class PCI SCI-FI a. Obsolete models are shown for reference only. SCSI Configuration Guidelines Small Computer System Interface (SCSI) is an ANSI standard for connecting computers and peripheral devices.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-11 SCSI Configuration Requirements Architecture Interface Card (SCSI Type) Interface Driver Series 700 EISA 25525A/B (Differential) sctla Series 800 CIO 27147A (Single-Ended) scsi2b Series 800 HP-PB 28655A (Single-Ended) scsi1c Series 800 HP-PB 28696A (Fast/Wide) scsi3c a. Specifying sctl causes c700, c720, wsio, core, eisa, and eeprom to be included in the kernel. b.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards single-ended SCSI must not exceed six meters. Total cable length for fast/wide SCSI must not exceed 25 meters. These limitations include both internal and external cables, Refer to the documentation that came with your device for internal cable lengths. Table 3-12 SCSI Cables Product Number Length Connectivity Description Adapter-to-Peripheral SCSI Cables K2296 a 1.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards 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 3-13, “Fast/Wide SCSI Cables,” shows additional cables available to connect a Fast/Wide SCSI adapter-to-peripheral or peripheral-to-peripheral.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Table 3-14 Example of SCSI Cable Length Calculation Starting Point Device HP device #4 Cable to Next Device none Total Internal Cable Cumulative Cable Length 0.4m 3.9m 3.9m 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.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards additional termination. Table 3-15 SCSI Terminators Part Number Kind of Terminator No.
Configuring Interface Cards Selecting Device Drivers for Your Interface Cards Hewlett-Packard's standard support process.
Configuring Interface Cards Configuring an Interface Card Configuring an Interface Card Step 1. Determine the interface driver needed for your interface card by consulting the tables in “Selecting Device Drivers for Your Interface Cards”. Look at your /stand/system file to see if the required driver is present. (If you are also adding an external device such as a printer, consult the tables in the appropriate chapter and look for the presence of those drivers in /stand/system also.
Configuring Interface Cards Configuring an Interface Card /usr/sbin/mk_kernel -s /stand/build/system d. Save the old system file by moving it. Then move the new system file into place. mv /stand/system /stand/system.prev mv /stand/build/system /stand/system e. Prepare for rebooting by invoking the kmupdate command. This action sets a flag that tells the system to use the new kernel when it restarts. /usr/sbin/kmupdate Step 2.
Configuring Interface Cards Configuring an Interface Card that the interface card (and any peripheral devices you configured) are present and device special files have been created. In the following sample ioscan output, the LAN card installed in slot 14 of a Model 887 is displayed as hardware path 56 (slot number times 4).
Configuring Interface Cards For Further Information on Interface Cards For Further Information on Interface Cards For information on any device drivers, consult the Section 7 manpages in the HP-UX Reference, most of which deals with interfaces.
Configuring Interface Cards For Further Information on Interface Cards 100 Chapter 3
Configuring Terminals and Modems 4 Configuring Terminals and Modems This chapter contains the procedures for configuring terminals and modems to serial (RS-232-C) ports. For HP-UX to communicate with a terminal or modem, the following conditions must be met: • The serial device driver required to communicate with the device must be part of the kernel. • The terminal or modem must be physically attached and configured to the port. • A device special file must be created to communicate through the port.
Configuring Terminals and Modems Planning to Configure a Terminal or Modem Planning to Configure a Terminal or Modem Plan ahead before configuring a terminal or modem. Read the hardware documentation shipped with the peripheral device and understand what you need to do before getting started.
Configuring Terminals and Modems Planning to Configure a Terminal or Modem Non-HP Terminal as a Console”, later in this chapter. The following non-standard terminal emulations are provided for HP-UX: • DEC VT100, VT320 • VT420 terminals in VT100 or VT320 modes • Wyse 60 • HP terminal 700/60 in VT100, VT320, and Wyse 60 modes. Note, the less expensive DEC and Wyse terminals lack certain capabilities standard to full-featured HP terminal firmware.
Configuring Terminals and Modems Planning to Configure a Terminal or Modem You will need to create device special files with /usr/sbin/mksf specifically for modem use. mksf provides options for CCITT for special European protocol requirements (most US customers should not use the CCITT option), -i option for a UUCP dialer (used with access mode 0), and hardware flow control (an alternative to XON/XOFF pacing). The mksf options for the asio0 device driver allows for incoming and outgoing hardware buffering.
Configuring Terminals and Modems Selecting Device Drivers for Terminals and Modems Selecting Device Drivers for Terminals and Modems Use Table 4-1, “Serial Configurations for Terminals and Modems,” on the next page to identify the interface and device drivers required to configure a terminal or modem to a serial port. For information on increasing the number of available serial ports, see Table 4-1, “Serial Configurations for Terminals and Modems.
Configuring Terminals and Modems Selecting Device Drivers for Terminals and Modems d. mux# and tty#p# derive from ioscan output: The numeral after mux and tty is the card instance for the tty class of interface card to which the terminal is connected; the numeral after p is the port number of the serial interface. e. Specifying mux0 causes cio_ca0, sio, pfail, and pa to be included in the kernel. f. The A1703-60022 and 28639-60001 personality cards are used for console connection. g.
Configuring Terminals and Modems Configuring HP-UX for an HP Terminal or for a Modem Configuring HP-UX for an HP Terminal or for a Modem Step 1. Determine which driver is required for the terminal or modem by consulting Table 4-1, “Serial Configurations for Terminals and Modems.” Step 2. Determine whether the driver is present in the kernel by invoking the command, /usr/sbin/ioscan -fn -C tty, from the system console or any login to the system using an active terminal.
Configuring Terminals and Modems Configuring HP-UX for an HP Terminal or for a Modem to the port number of 1. (See Appendix C for explanation of bit assignments.) /usr/sbin/lssf /dev/tty0p1 mux4 card instance 0 port 1 hardwired at address 56/0 /dev/tty0p1 ll /dev/tty0p1 crw-rw-rw1 bin bin 178 0x000100 Mar 16 18:29 /dev/tty0p1 — If you are configuring a terminal without having to install an interface card, you can physically connect the terminal, as described in its owner's manual.
Configuring Terminals and Modems Configuring HP-UX for an HP Terminal or for a Modem NOTE To avoid introducing format errors, do not edit the HP-UX system description files directly. Instead, use the commands kmsystem and kmtune. These commands are new for Release 11.0; consult kmsystem (1M) and kmtune (1M) in the HP-UX Reference. d. Build the new kernel by invoking the mk_kernel command. This action creates /stand/build/vmunix_test, a kernel ready for testing.
Configuring Terminals and Modems Configuring HP-UX for an HP Terminal or for a Modem “Additionally Configuring HP-UX for a Modem” (later in this chapter), depending on which device you are configuring.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal Additionally Configuring HP-UX for a Terminal The previous procedure ensured the system side was set up properly; now you are setting up the terminal side. • If the terminal will be used as a console, the default configuration is likely to be correct. • If the terminal will not be used as a console (but rather as an additional serial terminal), you might have to set configuration modes. Step 1.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal • The /usr/sbin/getty is the process used to set up serial terminal and modem ports and provide the initial login prompt. • The -h option ensures that the getty will not hang up the line before setting the port speed. • The -t 60 is a security option to require that the user login name and password is typed within 60 seconds. • tty0p3 identifies the port in /dev to which the getty attaches.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal in Table 4-2, “Key Terminal Configuration Parameters,” might require configuration in /etc/gettydefs. Table 4-2 Key Terminal Configuration Parameters Parameter Console (as shipped) Serial Terminal (hard-wired) a Serial Terminal (via modem) Data bits 8 8 7 Parity no no even Default speed 9600 b 9600 300b a.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal system consoles on other HP 9000 Series 800 computers. Two HP MUX interface modules support configuration of a non-HP terminal console, provided you have the correct firmware version: • Access port MUX16 (part number A1703-60022 for Series 800 HP-PB) with firmware version Rev 2.30 datecode 3341. (If you installed the card, you should have recorded the firmware revision on a worksheet in Appendix D , “Worksheets.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal correct values for a Model VT420 terminal set up to emulate a VT100.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal Table 4-3 Configuration Values for vt100 Compatibility Communications Set-Up Comm1 Transmit=9600 Receive=Transmit XOFF at 64 8 Bits, No Parity (console) 1 Stop Bit (console) No Local Echo Data Leads Only Limited Transmit No Auto Answerback Answerback= Not Concealed Keyboard Set-Up Caps Lock Auto Repeat Keyclick High Margin Bell Off Warning Bell High Character Mode
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal VT100 default configuration.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal the key to erase, execute an stty command as follows: stty erase "^?" Input the ^ and ? characters as separate keystrokes and be sure to enclose them in quotation marks. HP 700/60 terminals in VT320 mode uses control-H for backspace. You can set this up in your .profile or .login file. Configuring the Wyse 60 Terminal Configure the Wyse 60 terminal for use as an HP console by executing the following set of instructions: Step 1.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal Table 4-5 Wyse 60 Default Configuration Values General F2 Personality Comm mode Data/Printer Rcvd CR Enhance End-of-Line-Wrap Auto Scroll Monitor Font Load Send Ack Init Tabs Width Change Clear Wy60 Full Duplex Modem/Aux CR On On On Off On On Off Off Keyboard F3 Keyclick Return XMT Limit Wyse Word Keylock Enter Fkey Xmit Limit Language Key Repeat Corner Key Break Margin Bell On CR None Off Caps CR No US On Funct 250 ms Off
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal Table 4-5 Wyse 60 Default Configuration Values Misc F5 Block End Auto Page TVI 955 Attribute VPG0 Blk End Labels Save Labels Page Edit WPRT Intensity WPRT Reverse WPRT Underline Test us/cr Off No Space None Off Off Off Normal Off Off Off Tabs F6 Tabs (undefined) Answerback Answerback (blank) FKeys F8 All FKeys definition (undefined) FKey Labels All FKey labels (undefined) F7 F9 Limitations to Non-HP Terminal Emu
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal located in the bottom row of the number pad. • Unlike HP terminals, which provide two lines, Wyse 60 terminals provide a single line to display softkey labels. Sometimes, this may result in truncated softkey labels. For example, the "Help on Context" label for F1 might appear as "Help on C.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Terminal Table 4-6 Function Key Mappings HP or Wyse60 DEC/ANSI keyboard in VT100 or HP700/60 in VT100 mode DEC/ANSI keyboard in VT320 or HP700/60 in VT320 mode F7 none F18 first unlabeled key to right of Pause/Break F8 none F19 second unlabeled key to right of Pause/Break DEC PC-AT keyboard • Many applications use Tab for forward navigation and ShiftTab for backward navigation when moving from one field to another.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Modem Additionally Configuring HP-UX for a Modem Step 1. If you are configuring a modem to the single modem port on a Series 800 multi-function card, you need to ensure that the modem port is not locked. Step 1. Execute a control-B on the console to get into command mode. This will give you a CM> prompt. Step 2. Execute a ur command to unlock the remote access port. Step 3. Execute a dr command to disable the remote access port. Step 4.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Modem appropriate for terminals. To create a device file with modem syntax (that is, /dev/cua#p#), you need to execute mksf with the -i option. The -i is used for only direct connect; it is not necessary for dial-out or dial-in modem files. Here is an example of creating device special files with mksf for a Series 700 whose modem is connected to hardware path 2/0/4.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Modem documented on the inittab (4) manpage of the HP-UX Reference. For example: p5:234:respawn:/usr/sbin/getty -h -t 240 ttyd2p5 9600 • The p5 is a label used to uniquely identify the entry. • This getty is executed when the system is in both run states 1 and 2. • The respawn tells init to restart the process if it dies for any reason. • The /usr/sbin/getty is the process used to open the port and provide the initial login prompt.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Modem users' manual for procedure on how to change strapping. At this point the modem is ready for call-in use. Step 13. To set up the modem for call-out use, you must add entries to the /etc/uucp/Devices file. (This file does not have an associated manpage; follow the examples given in the file itself.) Edit /etc/uucp/Devices to include an entry for the /dev/culnpp file created earlier.
Configuring Terminals and Modems Additionally Configuring HP-UX for a Modem for the interrupt signal as well as for baud-rate switching. • Modem speed between modem and terminal should be known; however, speed can be negotiated in modem-to-modem connections (using the modems' autobauding speed detection). Initially, features such as hardware flow control (CTS/RTS) and error correct should be turned off. Once you have established that the modem communicates properly, add these features one at a time.
Configuring Terminals and Modems Removing or Moving a Terminal or Modem Removing or Moving a Terminal or Modem NOTE Removing the system console is not supported. Terminals and modems are most easily removed using SAM, because SAM also removes the getty entries in /etc/inittab and ensures that inittab is reread. However, it is also a simple matter to remove a terminal or modem using HP-UX commands. Step 1. If users will be affected, notify them in advance about the change.
Configuring Terminals and Modems Troubleshooting Terminal Problems Troubleshooting Terminal Problems This section addresses problems with alphanumeric display terminals; however, the techniques can be applied to problems with terminal emulators such as AdvanceLink or X-Windows terminal processes (such as hpterm and xterm). Unresponsive Terminals Several conditions can cause a terminal not to display any characters except for those it echoes when you type.
Configuring Terminals and Modems Troubleshooting Terminal Problems work-in-progress to a temporary file so that both the original and edited versions of the file are accessible. If all else fails, kill the editor process from the console, as described in step 8.) Step 3. Enter Ctrl-Q at the terminal keyboard. If output to the unresponsive terminal was stopped because an XOFF signal (Ctrl-S) was sent from the terminal to the computer, you can restart it by sending an XON signal (Ctrl-Q).
Configuring Terminals and Modems Troubleshooting Terminal Problems Step 7. Send a short ASCII file to the unresponsive terminal's device file. Execute this in the background to retain the current terminal's responsiveness. For example, for an unresponsive terminal associated with the device file ttyd1p4, cat /etc/motd > /dev/ttyd1p4 & If you have solved the problem, you will see the contents of the file /etc/motd displayed on the terminal associated with /dev/ttyd1p4. Step 8.
Configuring Terminals and Modems Troubleshooting Terminal Problems /dev/tty is a pseudo-device used in many places to refer to the login terminal. Step 12. Check the functionality of your hardware. a. If the unresponsive terminal has a self-test feature, activate it. If not, power the terminal off, wait several seconds, and power the terminal back on. b. Swap the unresponsive terminal with one known to be functioning. Swap only the terminal and keyboard.
Configuring Terminals and Modems Troubleshooting Terminal Problems — wires are partially shorted or broken within the cable. — telephone connection is noisy • Parity is incorrectly set. (See “Differences between Console and Terminal Configuration”.
Configuring Terminals and Modems Troubleshooting Terminal Problems Refer to the terminfo (4) manpage for further explanation.
Configuring Terminals and Modems For Further Information on Terminals and Modems For Further Information on Terminals and Modems The following manpages specify terminal- and modem-related functionality: mesg (1) Permit or deny messages to a terminal pg (1) File paginator for video terminals stty (1) Set options for a terminal port tabs (1) Set tabs on a terminal telnet (1) User interface to the telnet protocol tput (1) Generate terminal-specific functions tset (1) Terminal-dependent initializa
Configuring Terminals and Modems For Further Information on Terminals and Modems environ (5) User environment variables modem (7) Asynchronous serial modem line control pty (7) Pseudo-terminal driver termio (7) General terminal interface tty (7) Controlling terminal interface The following manuals provide additional information: • Terminal Control User's Guide • Using Serial Connections Technical Guide • Terminal Session Manager User's Guide • DTC Device File Access Utilities and Telnet Port Ident
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives 5 Configuring Disk Drives, Disk Arrays, and CD-ROM Drives This chapter gives procedures and guidelines for configuring hard and floppy disk drives and disk arrays to SCSI interfaces. Procedures and guidelines are also provided for configuring CD-ROM drives to SCSI interfaces.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure a Disk Drive Planning to Configure a Disk Drive Review the material discussed in this chapter for each kind of disk drive. Identify the device driver(s) that must be present in the kernel for the interface and disk device you are installing. You will find the device drivers listed in “Selecting Device Drivers for a Disk Device and Interface”.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure a Disk Drive configuration tools. Consult the hardware documentation to find out what degree of data protection is provided by the RAID level in which the disk array is shipped. If you need to modify the RAID level, use the disk array utilities provided. If you are configuring a disk array with more than one controller, you will be using more than one target address.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure a Disk Drive • If using SAM, choose the action, Add -> Not Using LVM. LVM functionality is not supported on floppy disks. • Unlike HP hard disks, which are typically initialized before shipping, you must initialize floppy-disk media, using the mediainit command. See mediainit (1M) in the HP-UX Reference for information. • Do not use low-density floppy disks.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Selecting Device Drivers for a Disk Device and Interface Selecting Device Drivers for a Disk Device and Interface The following sections (covering SCSI interfaces and floppy disk drives) identify the device drivers that must be present in the kernel for HP-UX to communicate with your disk device. Choose the device drivers based on the interface to which you are configuring the disk device.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Selecting Device Drivers for a Disk Device and Interface the disk (7) manpage.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Selecting Device Drivers for a Disk Device and Interface c. The following disk devices can be configured to a Series 700 Fast/Narrow/Differential EISA/SCSI-II: (C2425JK), (C2427JK), C2435A, (C2436HA), C2436HZ, C2438A, (C2439HA), C2439HZ/JA/JZ, (C2440HA), C2440HZ/JA/JZ, C2474J, (C2481A), (C2482A), (C2491A), (C2492A). (Models shown in parenthesis are obsolete and are listed for reference only.) d.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Selecting Device Drivers for a Disk Device and Interface floppy disk drives are installed on some Series 700 and E-class (Series 800) computers. (See also “Considerations for Configuring a Floppy Disk Drive” for information about using a floppy disk drive with HP-UX.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring HP-UX for a New Disk Device Configuring HP-UX for a New Disk Device The simplest way to configure a disk device (hard disk, floppy disk, disk array, or CD-ROM) is to use SAM (/usr/sbin/sam). If SAM is not loaded on your system or if you prefer to use the command-line interface, the following procedure will guide you through the task. Familiarize yourself with the instructions before getting started. Step 1.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring HP-UX for a New Disk Device kmtune. These commands are new for Release 11.0; consult kmsystem (1M) and kmtune (1M) in the HP-UX Reference. Step 5. Build the new kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing. /usr/sbin/mk_kernel -s /stand/build/system Step 6. Save the old system file by moving it. Then move the new system file into place. mv /stand/system /stand/system.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring HP-UX for a New Disk Device Step 13. Verify the configuration by executing ioscan. If you are configuring a hard disk, you have finished the initial configuration. If you are configuring a floppy disk drive, initialize the floppy disk by invoking the mediainit command on the character device special file.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure into your System a Disk Already Containing Data Planning to Configure into your System a Disk Already Containing Data When configuring a new disk onto either Series 700 or 800 system, both SAM and insf now treat the disk in its entirety and create a single block device special file in /dev/dsk and a single character device special file in /dev/rdsk. As of HP-UX 10.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure into your System a Disk Already Containing Data mount system directories and structural files. System directories include /usr, /dev, /etc, /system, /bin, and /lib. Structural files include files such as /etc/checklist and dfile. Never attempt to use 9.x device special files on a 10.x system. They will fail. Delete or rename any system files and directories you find. Step 2. Examine user scripts for occurrences of 9.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Planning to Configure into your System a Disk Already Containing Data Step 1. Examine all files for the presence of system and structural files (as documented in the previous section) and remove any invalid references. Step 2. Configure the disk as documented in “Configuring into your System an Unpartitioned Disk Already Containing Data”, shortly. insf creates the required device special files to access the whole disks.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into your System an Unpartitioned Disk Already Containing Data Configuring into your System an Unpartitioned Disk Already Containing Data NOTE This procedure is provided for configuring a Series 700 legacy disk into HP-UX 10.0. Before proceeding, make sure you have read “Planning to Configure into your System a Disk Already Containing Data” and have performed the examination documented in “Ensuring Against Clashes with HP-UX 10.0”.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into your System an Unpartitioned Disk Already Containing Data description files directly. Instead, use the commands kmsystem and kmtune. These commands are new for Release 11.0; consult kmsystem (1M) and kmtune (1M) in the HP-UX Reference. c. Build the new kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing. /usr/sbin/mk_kernel -s /stand/build/system d.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into Your System a Partitioned Disk Already Containing Data Configuring into Your System a Partitioned Disk Already Containing Data NOTE This procedure is provided for configuring a Series 800 legacy hard-partitioned disk into HP-UX 10.0.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into Your System a Partitioned Disk Already Containing Data rebuild the kernel to include it. Here is how you rebuild the kernel: a. Change directory to the build environment (/stand/build). There, execute a system preparation script, system_prep. system_prep writes a system file based on your current kernel in the current directory. (That is, it creates /stand/build/system.) The -v provides verbose explanation as the script executes.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into Your System a Partitioned Disk Already Containing Data Step 7. Execute /usr/sbin/ioscan -fun -C disk again, to verify that the disk device configured successfully and to identify its whole-disk device special files (/dev/[r]dsk/c#t#d#). Step 8. Use the mksf command to create device special files for each individual section being used on the disk. (Refer to the printout of /etc/checklist to identify the sections.) Note, as of HP-UX 10.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into your System an LVM Disk Already Containing Data Configuring into your System an LVM Disk Already Containing Data NOTE This procedure is provided for configuring a Series 800 legacy LVM disk into HP-UX 10.0. Before proceeding, make sure you have read “Planning to Configure into your System a Disk Already Containing Data” and have performed the examination documented in “Ensuring Against Clashes with HP-UX 10.0”. Step 1.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into your System an LVM Disk Already Containing Data system file from the current kernel and writes a system file in your current directory. (That is, it creates /stand/build/system.) The -v gives verbose explanation as the script executes. cd /stand/build /usr/lbin/sysadm/system_prep -v -s system b. Modify the /stand/build/system file to add the absent driver(s) by invoking the kmsystem command.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Configuring into your System an LVM Disk Already Containing Data device by location. Step 11. Scan your current system to identify all disks by their volume groups. /usr/sbin/vgscan -v Step 12. Create a directory for the volume group to which the new LVM disk will belong. For example, a new volume group might be called vg06. mkdir /dev/vg06 Step 13. Check to make sure that you are creating a unique minor number for the new group file.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address Moving a Disk Drive to a Different Address Occasionally, you might find yourself having to move a disk from one interface card to another. This procedure explains how to do so. NOTE Moving the root disk and moving an LVM root disk are special cases. You will find additional instructions at several points in this procedure to cover these requirements. To move a disk drive using HP-UX commands: Step 1.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address the file systems from the client, the client will receive NFS error messages when accessing the files on the disk. There are several methods to unmount the NFS client file systems: • Enter the Remote Administration area of SAM on the NFS server and unmount the file systems remotely. • Log in directly to each NFS client and unmount the file systems using either SAM or HP-UX commands.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address Step 7. If you are moving a disk drive containing the root file system (and you want to continue to use it as root), you will need to make sure the AUTO file on the root disk boot area does not specify a hard-coded hardware path. To check this, a. Locate the root disk by executing mount or bdf and looking for the / entry. b.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address a. Change directory to the build environment (/stand/build). There, execute a system preparation script, system_prep, which extracts the system file from the current kernel, as follows: cd /stand/build /usr/lbin/sysadm/system_prep -v -s system The system_prep script writes a system file in your current directory (that is, it creates /stand/build/system).
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address Step 13. If you are moving a disk containing the root file system, you must change the hardware path that is read from stable storage: a. Start up your system, but override the autoboot. Do not boot from the primary or alternate boot path. Instead, enter Boot Administration mode. (Note, boot ROM administration is system-dependent, and thus differs for Series 700 and 800 systems.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address a. Execute a vgchange command to reactivate the root volume group. b. Execute an lvlnboot command to view the logical volumes in the volume group. c. Execute an lvrmboot command to remove the current definitions of root, swap, and dump from the disk's Boot Data Reserved Area. d. Execute lvlnboot commands to redefine root, swap, and dump. Use the -v option for verbose output. e.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Moving a Disk Drive to a Different Address disk drive to make sure they use the new device files. Refer to your software application documentation for specific instructions.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Removing a Disk Drive Removing a Disk Drive Step 1. Back up the data on the disk drive; see the backup chapter of Managing Systems and Workgroups. Step 2. If your system is an NFS server and file systems on the disk you are moving are exported, a. Find the NFS clients by logging in to the NFS server and looking at the /etc/exports file. Refer to exports (4) in the HP-UX Reference. b.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Removing a Disk Drive belongs.) b. Execute lvdisplay -v for every logical volume in the volume group of the disk being removed to locate any logical volumes currently straddling the disk being moved and another disk. If you find any, • Back up the data and remove the logical volume, by executing an lvremove command. Or, if the logical volume is mirrored, • Remove the mirroring, by executing an lvreduce -m 0 command. c.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Removing a Disk Drive instructions.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives Finding Out the Disk Model Number and Other Information Finding Out the Disk Model Number and Other Information The diskinfo command displays useful information about a disk. Execute it specifying the disk's character device special file.
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives After Configuring HP-UX for the Disk Device After Configuring HP-UX for the Disk Device After configuring HP-UX for a disk device, you may complete the tasks required to put it to use. These include: • Setting up power fail capabilities for the disk or disk array. • Setting up or modifying RAID levels for a disk array, if necessary. • Adding a disk to an LVM volume group. • Mirroring the disk. • Defining logical volumes in LVM.
Configuring Magneto-Optical Devices 6 Configuring Magneto-Optical Devices Magneto-optical disks and magneto-optical disk library systems are SCSI devices used for high-capacity read-write applications. The ability of magneto-optical devices to randomly access vast amounts of data makes them best suited for fast retrieval of infrequently accessed archival data, unattended backup, and storage of large data files such as electronic images.
Configuring Magneto-Optical Devices Planning to Configure a Magneto-Optical Device Planning to Configure a Magneto-Optical Device Magneto-optical disk devices are configured into the operating system much like a SCSI hard disk drive.
Configuring Magneto-Optical Devices Planning to Configure a Magneto-Optical Device the drives are used. Other commands (such as raw access with cpio or dd) will wait (sleep) until a drive is available. Understanding Magneto-Optical Media Capacity Magneto-optical disk mechanisms support several different capacities: • C17xxA and C17xxC products support 1X capacity disks. • C17xxT and C11xxA products support 1X and 2X capacity disks. • C11xxF, C11xxG, and C11xxH products support 4X capacity disks.
Configuring Magneto-Optical Devices Magneto-Optical Disk Configuration Guidelines Magneto-Optical Disk Configuration Guidelines This section identifies the device drivers that must be configured into HP-UX for it to communicate with single magneto-optical disks. If you are configuring a magneto-optical disk library or adding an optical disk to an existing magneto-optical disk library, refer to the section, "Magneto-Optical Disk Library Configuration Guidelines.
Configuring Magneto-Optical Devices Magneto-Optical Disk Configuration Guidelines c. c#t#d#[s#] derives from ioscan output: c# is the card instance for the class of interface card to which the device is attached, t# is the address of the device on the interface, d# is the device unit number. s# specifies section number and is shown for backward compatibility; the entire disk (s0) is assumed when s# is unspecified. d. Specifying scsi2 causes cio_ca0 to be included in the kernel. e.
Configuring Magneto-Optical Devices Magneto-Optical Disk Library Configuration Guidelines Magneto-Optical Disk Library Configuration Guidelines This section gives information pertinent to configuring a magneto-optical disk library. If you are configuring a single magneto-optical disk, refer to the previous section, “Magneto-Optical Disk Configuration Guidelines”.
Configuring Magneto-Optical Devices Magneto-Optical Disk Library Configuration Guidelines c. Specifying schgr or sdisk causes sctl, c700, and wsio to be included in the kernel. d. c#t#d# derives from ioscan output: c# is the card instance for the class of interface card to which the device is attached, t# is the address of the device on the interface, d# is the device unit number. #[a|b] specifies disk platter number and surface. e. Specifying scsi2 causes cio_ca0 to be included automatically in the kernel.
Configuring Magneto-Optical Devices Magneto-Optical Disk Library Configuration Guidelines mechanism and record the information. • Run the recommended tests. Step 3. Consult Table 6-3, “Magneto-Optical Disk Library Configuration Requirements,” to determine the device drivers needed for your magneto-optical disk library and interface. If any necessary static device driver is absent from the kernel, you will need to rebuild the kernel to include it. Here is how to do so: a.
Configuring Magneto-Optical Devices Magneto-Optical Disk Library Configuration Guidelines Step 4. Notify users that the system will be shut down to configure the optical disk library. You can use the wall command and/or the interactive capabilities of the shutdown command to broadcast a message to users before the system goes down. (See wall (1M) or shutdown (1M) in the HP-UX Reference.) Step 5. Bring the system down to a halt using the shutdown command. Step 6.
Configuring Magneto-Optical Devices Magneto-Optical Disk Library Configuration Guidelines target autoch 2 0 2/0/1.0 2/0/1.0.0 target CLAIMED schgr CLAIMED /dev/ac/c0t0d0_10a /dev/ac/c0t0d0_10b /dev/ac/c0t0d0_11a /dev/ac/c0t0d0_11b /dev/ac/c0t0d0_12a ...
Configuring Magneto-Optical Devices After Configuring a Magneto-Optical Device After Configuring a Magneto-Optical Device Once you have configured a magneto-optical disk, it can be used like any other disk. You will find its performance somewhat slower than a hard disk but faster than a floppy disk. Consult the Optical Disk Library System Administrator's Guide that accompanied the hardware for procedures on the following: • initializing the disk surfaces.
Configuring Magneto-Optical Devices After Configuring a Magneto-Optical Device 182 Chapter 6
Configuring Tape Drives 7 Configuring Tape Drives Several kinds of tape drives, having different recording methods and formats, can be configured to HP-UX: • nine-track reel-to-reel tape drive • cartridge tape drive (configured like a disk device) • QIC tape drive • DDS (DAT) tape drive • 8mm Exabyte tape drive • 3480-style cartridge tape drive Despite their differences, any of these tape drives can be configured into HP-UX by the same basic procedure: 1.
Configuring Tape Drives Selecting Device Drivers for a Tape Device and Interface Selecting Device Drivers for a Tape Device and Interface The following sections will help you identify the device drivers needed to configure a tape drive. Choose the drivers based on the interface to which the tape drive is being connected.
Configuring Tape Drives Selecting Device Drivers for a Tape Device and Interface configuration requirements for the single-ended SCSI tape drives.
Configuring Tape Drives Selecting Device Drivers for a Tape Device and Interface c. Naming convention for systems installed with long file names. c#t#d# derives from ioscan output: c# is the card instance number for the ext_bus class of interface card to which the tape drive is attached, t# is the SCSI address, d# is the device number. BEST represents the operational capabilities likely to be required, including the highest density/format and data compression, if supported by the device.
Configuring Tape Drives Configuring HP-UX for a Tape Drive Configuring HP-UX for a Tape Drive The simplest way to configure a tape drive is to use SAM (/usr/sbin/sam). If SAM is not loaded on your system or if you prefer to use the command-line interface, the following procedure will guide you through the task. Understand the instructions before getting started. Step 1.
Configuring Tape Drives Configuring HP-UX for a Tape Drive d. Save the old system file by moving it. Then move the new system file into place. mv /stand/system /stand/system.prev mv /stand/build/system /stand/system e. Prepare for rebooting by invoking the kmupdate command. This sets a flag that tells the system to use the new kernel when it restarts. /usr/sbin/kmupdate Step 3. Notify users that the system will be shut down to configure the tape drive.
Configuring Tape Drives Configuring HP-UX for a Tape Drive /usr/sbin/ioscan -C tape -fun Class I H/W Path Driver S/W State H/W Type Description ========================================================================== tape 0 2/0/1.3.0 stape CLAIMED DEVICE HP35480A /dev/rmt/0m /dev/rmt/c0t3d0BESTn /dev/rmt/0mb /dev/rmt/c0t3d0BEST /dev/rmt/0mn /dev/rmt/c0t3d0BESTb /dev/rmt/0mnb /dev/rmt/c0t3d0BESTnb Step 9. You can also use the tar command to verify that you can read and write to and from the device.
Configuring Tape Drives Creating Customized Device Special Files for Tape Devices Creating Customized Device Special Files for Tape Devices The default device special files created by insf handle most routine tape-drive requirements. For special circumstances, however, you can use SAM or the tape driver options of the mksf command to create device special files. For complete syntax information, consult the SAM online help or mksf (1M) manpage in the HP-UX Reference.
Configuring Tape Drives Creating Customized Device Special Files for Tape Devices The following shows the command line and resulting device special files: /usr/sbin/mksf -C tape -I 1 -e /dev/rmt/c#t#d#eBEST /dev/rmt/c#t#d#i# on a system allowing long file names, or on a system requiring short file names Avoiding Data Compression Sometimes an operation requires use of a device special file that writes data without compression.
Configuring Tape Drives After Configuring a Tape Drive After Configuring a Tape Drive The following manpages, found in the HP-UX Reference give specifications related to typical tape drive tasks and capabilities: cpio (1) Copy file archives in and out (cpio is not recommended for use with 3480 products.
Configuring Tape Drives After Configuring a Tape Drive savecrash (1M) Save a core dump of the operating system scsictl (1M) Control a SCSI device swinstall (1M) Install HP-UX software tar (4) Format of tar tape archive ct (7) Command set/80 (CS/80) cartridge tape access mt (7) Magnetic tape interface and controls scsi (7) Small Computer System Interface device drivers scsi_ctl (7) SCSI device control device driver scsi_tape (7) SCSI sequential access (stape) device driver Other sources you
Configuring Tape Drives After Configuring a Tape Drive 194 Chapter 7
Configuring Printers and Plotters 8 Configuring Printers and Plotters Because they are output-only devices, printers and plotters are configured somewhat differently than other peripheral devices. There are three basic steps to printer and plotter configuration: • physically installing the printer or plotter (documented in the hardware manual shipped with the device). • configuring the HP-UX kernel for the device drivers to communicate with the printer or plotter.
Configuring Printers and Plotters Preparing to Configure HP-UX for a Printer or Plotter Preparing to Configure HP-UX for a Printer or Plotter Choosing Means of Access Printers and plotters can be connected to the system to be accessed locally, remotely, or through the network. In the following example, the printer print1 is physically connected to a system named sys1.
Configuring Printers and Plotters Preparing to Configure HP-UX for a Printer or Plotter configuring access to a local printer; HP recommends using the HP JetDirect Network Interface, an optional product. SAM requires JetDirect configuration and hides any additional complexities. When a user generates a request to a configured network printer, the LP spooler on the system from which the request is generated sends the print request over the LAN to the printer.
Configuring Printers and Plotters Preparing to Configure HP-UX for a Printer or Plotter documentation regarding setting device address. Software Concerns • Consult the tables in “Selecting Device Drivers for Your Printer or Plotter” to identify the drivers compatible with the printer or plotter and interface to which it is being connected.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter Selecting Device Drivers for Your Printer or Plotter Use this section to identify the device drivers required for your printer configuration, based on the model of printer or plotter and the interface to which it is attached.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter Configured to a Serial Port”.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter e. Specifying mux2 causes sio, pfail, and pa to be included in the kernel. f. These cards are typically used for console and remote console. If the second port is not being used for remote console, a printer may be attached. g. Specifying mux4 causes lanmux0, lantty0, lan3, sio, pfail, and pa to be included in the kernel.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter c. The following plotter models can be configured to the Series 800 RS-232-C serial interface: 7440A, 7475A, 7550A/B, 7558, 7586B, 7595A, 7595B, 7596A, 7596B, 7599A, C1620A, C1625A, C1627A. HP plotter models 7595A and 7596A can also be configured to an RS-422 interface. d. Specifying mux0 causes cio_ca0, sio, pfail, and pa to be included in the kernel. e.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter Guidelines for Configuring a Printer or Plotter to a Parallel (Centronics) Interface Table 8-3 Parallel Printer Configuration Requirements Interface Card Interface and Device Drivers Default Device File Series 700 Core I/O (internal) a CentIfb /dev/c#t#d0_lpc Series 800 HP-PB 28655A d lpr2e (same as above) Architecture a.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter Table 8-4 Parallel Plotter Configuration Requirements Interface Card Interface and Device Drivers Default Device File Series 700 Core I/O (internal) a CentIfb /dev/c#t#d0_lpc Series 800 HP-PB 28655A d lpr2e (same as above) Architecture a.
Configuring Printers and Plotters Selecting Device Drivers for Your Printer or Plotter Guidelines for Configuring a Printer to a SCSI Interface Table 8-5 SCSI Printer Configuration Requirements Interface and Device Drivers Architecture Interface Card Default Device Files Series 800 CIO 27147-60002 a scsi2b lpr3c /dev/c#t#d#_lpd Series 800 HP-PB 28655Aa scsi1e lpr3c (same as above) a.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands Configuring a Printer Using HP-UX Commands First configure the software for the operating system. Then, if necessary, bring down the system to install hardware. When you reboot, HP-UX will automatically bind the drivers to the peripherals it finds. Step 1.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands Similarly, the ioscan output for a Series 800 might resemble this: /usr/sbin/ioscan -fn -d lpr2 Class I H/W Path Driver S/W State H/W Type Description =========================================================== ext_bus 2 56/53 lpr2 CLAIMED INTERFACE HP28655A-Parallel Interface /dev/c2t0d0_lp Both cases show that the drivers and device special files are present, allowing HP-UX to communicate with the printer.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands /usr/lbin/sysadm/system_prep -v -s system b. Modify the /stand/build/system file to add the absent driver(s) by invoking the kmsystem command. The -c Y specifies that driver-name is to be configured into the system. (If you are adding an interface card also, make sure to add the interface driver, as documented in Chapter 3, “Configuring Interface Cards.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands See shutdown (1M) or reboot (1M) in the HP-UX Reference. a. Power off and unplug all peripherals, then the SPU. b. Install the hardware, as described in the manual accompanying the (card and) printer. c. Connect the printer to the card. d. Plug in and power up the printer. e. Set the hardware switches for the printer address. f. Plug in and power on any other peripherals and then the SPU.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands line printer name. Step 1. Execute ioscan -fn -C tty to identify the device file currently associated with the port. Note in the following excerpted output, the sample device special file representing port 3 has a name consistent with the device-file format used by terminals and modems.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands /usr/sbin/lssf /dev/c0p3_lp mux2 card instance 0 port 3 hardwired at address 56/56 /dev/c0p3_lp ll /dev/c0p3_lp crw-rw-rw1 bin bin 193 0x000300 Mar 16 18:29 /dev/c0p3_lp In the minor number (0x000300, shown in the long listing), you can see that the 3 corresponds to the port number for the mux2 card at card instance 0.
Configuring Printers and Plotters Configuring a Printer Using HP-UX Commands an error if an ASCII file is sent to it.) Table C-3, “Minor Number for a SCSI Disk Device,”shows the bit assignments for the CentIf driver. Bits 28-31 encode the handshake mode, as follows: 1 Handshake using nACK and BUSY lines. 2 Handshake using BUSY line only. 3 Bidirectional read/write for ScanJet support. 4 Streaming mode. Setup = 1 usec, hold = 1 usec.
Configuring Printers and Plotters Configuring a Plotter or other Non-Automatically Configurable Output Devices Using HP-UX Commands Configuring a Plotter or other Non-Automatically Configurable Output Devices Using HP-UX Commands NOTE Although this procedure refers explicitly to plotters, it can be used to configure other devices that need the instr0 device driver on a Series 800 computer. Unlike printers, plotters cannot be automatically configured by the kernel.
Configuring Printers and Plotters Configuring a Plotter or other Non-Automatically Configurable Output Devices Using HP-UX Commands system file from the current kernel and writes a system file in your current directory. (That is, it creates /stand/build/system.) The -v provides verbose explanation as the script executes. cd /stand/build /usr/lbin/sysadm/system_prep -v -s system b. Modify the /stand/build/system file to add the absent driver(s) by invoking the kmsystem command.
Configuring Printers and Plotters Configuring a Plotter or other Non-Automatically Configurable Output Devices Using HP-UX Commands /usr/sbin/ioscan -M instr0 -H 56/48.5 /usr/sbin/ioscan -kf Class I H/W Path Driver S/W State H/W Type Description ================================================================= bc 0 root CLAIMED BUS_NEXUS bc 1 56 bc CLAIMED BUS_NEXUS Bus Converter lanmux 0 56/44 lanmux0 CLAIMED INTERFACE HP J2146A - 802.3 LAN lan 1 56/44.1 lan3 CLAIMED INTERFACE Step 6.
Configuring Printers and Plotters Moving a Printer or Plotter Moving a Printer or Plotter To move a printer or plotter, first remove it and then add it to your configuration. This sample procedure demonstrates attaching a printer to a different interface card. Step 1. Notify users that you are moving the printer or plotter. Step 2. If you have customized it, copy the /etc/lp/interface/printer_name to a temporary location. cp /etc/lp/interface/laserjet /etc/lp/interface/laserjet_old Step 3.
Configuring Printers and Plotters For Further Information on Printer-Related Tasks For Further Information on Printer-Related Tasks • Managing Systems and Workgroups, "Managing Printers and Printer Output," to set up the LP spooler. • SharedPrint/UX User and Administrator's Guide • HP MPower 1.
Configuring Printers and Plotters For Further Information on Printer-Related Tasks shutdown (1M) Terminate all processing tsm.
Configuring Printers and Plotters For Further Information on Plotter-Related Tasks For Further Information on Plotter-Related Tasks • Starbase Graphics Techniques • SharedPrint/UX User and Administrator's Guide • Managing SwitchOver/UX • In addition to the manpages listed in the previous section, the following manpages may be helpful: lpfilter (1M) Chapter 8 (plotdvr) HP-GL plotter filter 219
Configuring Printers and Plotters For Further Information on Plotter-Related Tasks 220 Chapter 8
Configuring Uninterruptable Power Systems 9 Configuring Uninterruptable Power Systems Installing a PowerTrust Uninterruptable Power System (UPS) to an HP-UX computer ensures that power is maintained to your computer system for up to fifteen minutes after an AC power failure, preventing problems such as networking time-outs and tape rewinds.
Configuring Uninterruptable Power Systems Planning to Configure a UPS Planning to Configure a UPS Hardware Considerations Choose your UPS based on its rated load capabilities. Determine which pieces of hardware besides the server require coverage by a UPS. For example, • If users in another building rely on the server, or several servers in a building require LAN traffic to shut down cleanly, you might need to ensure that the LAN interface is protected by the UPS.
Configuring Uninterruptable Power Systems Planning to Configure a UPS (UPS) Cabling Guidelines To communicate with the host, each PowerTrust UPS comes with an RS-232-C serial connector, HP part number 5061-2569 (pinouts shown in Table 9-1, “UPS Cable Pin-Outs.”) The cable has a male DB-9 connector on the UPS end and a male DB-25 connector on the MUX end, and is 2 meters (6.5 feet) long.
Configuring Uninterruptable Power Systems Planning to Configure a UPS NOTE Do not use a standard terminal cable to connect a UPS to the serial port. The pinouts are different. Table 9-1 UPS Cable Pin-Outs UPS MUX 9 pins(M) 25 pins(M) Receive 1 3 Transmit 2 2 Gnd 9 7 The computer should have one dedicated MUX port for UPS communication for each UPS configured. Additional UPS units must be connected to additional dedicated MUX ports.
Configuring Uninterruptable Power Systems Selecting Drivers for a UPS Selecting Drivers for a UPS Uninterruptable power systems use a serial interface and multiplexer drivers. Table 9-2, “UPS Configuration Requirements,” shows the interfaces, device drivers, and device special files used for each supported architecture.
Configuring Uninterruptable Power Systems Configuring a PowerTrust UPS Configuring a PowerTrust UPS The simplest way to configure a uninterruptable power system is to use SAM (/usr/sbin/sam). If SAM is not loaded on your system or if you prefer to use the command-line interface, the following procedure will guide you through the task. Familiarize yourself with the instructions before getting started. Step 1.
Configuring Uninterruptable Power Systems Configuring a PowerTrust UPS b. Add a comment sign (#) in front of the getty entry corresponding to the port used by the UPS. For example, #ttp1:2:respawn:/usr/sbin/getty -h tty0p1 9600 Step 4. Edit the /etc/ups_conf file to customize the UPS configuration for your system. The etc/ups_conf file informs the monitoring daemon (/usr/lbin/ups_mond) which ports to monitor and how to react to UPS status.
Configuring Uninterruptable Power Systems Configuring a PowerTrust UPS • Decrease shutdown_timeout_mins if shutdown takes less than five minutes. Small systems can take advantage of this. CAUTION You must wait the full duration of shutdown_timeout_mins before cycling power to the SPU, regardless of whether AC power has been restored. Once activated, the UPS will turn off after that period of time.
Configuring Uninterruptable Power Systems Configuring UPS to Cycle Power During Non-Work Hours Configuring UPS to Cycle Power During Non-Work Hours In work environments where energy savings is crucial, you can use your UPS to cycle power on and off according to a specified schedule. You can set this up with two commands: Instruct cron to implement the power_onoff command, unattended, as part of a routine schedule. Consult the cron (1M) and >power_onoff (1M) manpages for information on using this feature.
Configuring Uninterruptable Power Systems Configuring UPS to Cycle Power During Non-Work Hours Once these lines are added to /etc/syslog.conf, syslogd must be set to accept the changes. Execute kill -HUP `cat /etc/syslog.pid` and restart ups_mond. Step 3. Verify that HP-UX has been properly configured for the PowerTrust UPS as follows: • Check to make sure the UPS monitor daemon, ups_mond is running, by executing ps -ef | grep ups.
Configuring Uninterruptable Power Systems After Configuring the PowerTrust UPS After Configuring the PowerTrust UPS If adding any card or peripheral to a unit monitored by a UPS, you need to recalculate the voltage/amperage (VA) draw. Regardless of how many PowerTrust UPS devices are installed, only one instance of the ups_mond daemon should be running at any time.
Configuring Uninterruptable Power Systems After Configuring the PowerTrust UPS 232 Chapter 9
EISA Board Configuration A EISA Board Configuration Before you can make use of EISA and ISA I/O boards on Hewlett-Packard workstations, you must configure them using the /sbin/eisa_config program. eisa_config allocates resources (such as interrupt lines, memory, and DMA channels) to all the boards on the E/ISA backplane, by reading the boards' corresponding CFG files.
EISA Board Configuration E/ISA Boards and CFG Files E/ISA Boards and CFG Files ISA boards have physical switches or jumpers for setting the board's characteristics. Set the switches and jumpers using documentation provided by the board manufacturer, and alter the settings if eisa_config reports conflict. EISA boards lack physical switches or jumpers but instead use a configuration (CFG) file provided by the manufacturer to specify board resources.
EISA Board Configuration E/ISA Boards and CFG Files BOARD ID = "HWP0C80" NAME = "HP EISA SCSI host adapter 25525A" MFR = "Hewlett-Packard Co." ... IOCHECK = INVALID DISABLE = SUPPORTED COMMENTS = " This init file performs the following - Sets the ABRT to 1 in 0zC85. - Sets the RIEN to 0 in 0zC85. ... FUNCTION = "BOOT ROM ENABLE/RELOCATION" CHOICE = "ENABLED" LINK MEMORY = 32K ADDRESS = 0D8000h | 0C8000h | 0D0000h MEMTYPE = OTH WRITABLE = NO ...
EISA Board Configuration Configuring the Software Required by the E/ISA Board Configuring the Software Required by the E/ISA Board You install an E/ISA interface board much like installing any other board, by following the procedures detailed in Chapter 3, “Configuring Interface Cards.” However, several additional software elements need to be present for proper configuration: • A CFG file must reside in the /sbin/lib/eisa directory for every EISA board.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode Configuring E/ISA Boards Using Interactive Mode You might need to run eisa_config interactively for the following reasons: • You need to add, remove, or move an ISA board, which do not have readable ID registers and thus are not automatically recognized by eisa_config. • eisa_config exited from automatic mode with an error message requiring you to change the choice for a function. See “Changing Choices for Board Functions” shortly.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode Slot CFG File Contents 0 1 2 3 4 !HWPC010 !XYZ1401 HP Series 700 EISA System Board XYZ SCSI Controller ** EMPTY ** XYZ Centronics Interface ** EMPTY ** !XYZ1702 On-Line Help Note that eisa_config has self-explanatory on-line help. Type ? or help at an EISA prompt and read the entries to acquaint yourself with the program.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode area networking board for use with twisted-pair cabling. Slot CFG File Contents 0 1 2 3 4 !HWPC010 !XYZ1401 !XYZ1802 !XYZ1702 HP Series 700 EISA System Board XYZ SCSI Controller XYZ Networking Board XYZ Centronics Interface ** EMPTY ** You can use the comment command to display help or comments provided by the manufacturer about the board and its switches, the interface functions and choices.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode Skirt ........................ No Length .......................
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode EISA: quit A description of the configuration was saved in /var/adm/eisa/config.log. If eisa_config was run per the instructions of a specific product installation manual, refer to that manual for specifics on device file creation and I/O drivers. Step 4 may apply if other cards were affected. Otherwise, the following is a list of generally required steps: (1) Make any necessary device files.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode 1 0 0 1 Required setting 1 0 0 1 +-x-+-+-+-x-+on | | | | | +-+-x-+-x-+-+off 1 2 3 4 Slot 2 XYZ Networking Board Switch Name: Loopback Mode Default Required 0 0 0 0 0 0 0 0 on +-+ | +-+ | +-+ | +-+ | +-+ off x 4 x 3 x 2 x 1 Exiting eisa_config. $ Saving the Configuration and Exiting eisa_config You can save the current configuration without exiting eisa_config by using the save system.sci command.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode Setting Switches and Jumpers on an E/ISA Interface Board When you exit eisa_config or use the show switch changed command, you see a graphical representation of the switch and jumper settings that have changed during the eisa_config session. The /etc/eisa/config.log file also contains all required switch and jumper settings for each board in your working configuration. To set the switch and jumper settings, 1.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode requirements. Refer to “Setting Switches and Jumpers on an E/ISA Interface Board”. Step 6. Physically move the boards. Step 7. Turn the power on and reboot the system. As the system boots, the new configuration is written to NVM and /etc/eisa/system.sci. If the devices attached to the board use drivers known to insf (for example, SCSI devices), insf creates device special files for them at their new location.
EISA Board Configuration Configuring E/ISA Boards Using Interactive Mode Creating Identical E/ISA Configurations on Other Workstations If you have several workstations with identical E/ISA boards, you can streamline the configuration task as follows: Step 1. Invoke /sbin/eisa_config on the first system and configure the E/ISA boards to your satisfaction. Step 2. Save the configuration in a system.sci file instead of to NVM. EISA: save system.sci Step 3.
EISA Board Configuration Troubleshooting E/ISA Board Configuration Troubleshooting E/ISA Board Configuration Begin by reading the system messages displayed by the dmesg command. Then consult this section and “E/ISA Board Power-Up Messages” shortly for possible causes and recommended actions. Verifying the Syntax of a CFG File If an E/ISA board is not configuring properly, check the CFG file syntax, using the -c option.
EISA Board Configuration Troubleshooting E/ISA Board Configuration Step 3. If you added the board interactively, did you save the new configuration before exiting eisa_config? If not, run eisa_config again, add the board again, and then save the configuration. See "Saving the Configuration and Exiting eisa_config." Did you change any switch and jumper settings to match the settings specified in /etc/eisa/config.log? If so, verify that you did so accurately. Step 4.
EISA Board Configuration Troubleshooting E/ISA Board Configuration mv oldname newname Step 3. Move the renamed CFG file to the /sbin/lib/eisa directory. Type the following command: mv -i newname /sbin/lib/eisa Boards that have duplicate CFG file names must be added using eisa_config interactively (see “Configuring E/ISA Boards Using Interactive Mode”) earlier.
EISA Board Configuration E/ISA Board Power-Up Messages E/ISA Board Power-Up Messages This section contains a listing of E/ISA board power up messages, their potential cause, and action you can take to correct the problem. Several messages displayed are informational only. They indicate that configuration completed successfully. Message: No EEPROM Data -> EISA Card ID: eisa_id Cause: An EISA card identified itself, but non-volatile memory (NVM) has no configuration data for the slot.
EISA Board Configuration E/ISA Board Power-Up Messages Action: Check CFG file for inaccuracies. Suspect a hardware problem. Message: EISA Board ID:eisa_id ignored Board not present or driver not configured into kernel Cause: The ID displayed was obtained from NVM, not the card. Either an ISA card is present, but not its driver or the driver is present, but not the card. (Since ISA cards do not identify themselves, only the card's driver can verify its existence.
EISA Board Configuration E/ISA Board Power-Up Messages If either of these messages appear while booting from EISA SCSI, the system will fail to boot. If booting from other than EISA SCSI, the EISA cards will not be recognized. Action: Call your HP representative. Message: slot_num Slot EISA Expander Initialized: eisa_id Cause: This informational message indicates that the bus adapter located between the EISA bus and the host system bus initialized properly.
EISA Board Configuration E/ISA Board Power-Up Messages Message: Skipping Cause: Either the slot is empty, or NVM reports the slot is empty, or the slot has an ISA card but no EEPROM data, or the slot was skipped because of an already cited circumstance. Action: None. Message: EISA card id eisa_id in slot slot_num had fatal error Cause: An EISA card asserted the IOCHK line indicating a fatal error. An expansion card might do this if there was a parity error on a memory card.
EISA Board Configuration E/ISA Board Power-Up Messages /etc/bcheckrc will automatically generate data for and reconfigure the EISA cards that are present. You will need to reconfigure ISA cards, by running eisa_config interactively. Action: Appendix A Follow instructions in “Configuring E/ISA Boards Using Interactive Mode”.
EISA Board Configuration E/ISA Board Power-Up Messages 254 Appendix A
Bus Architectures B Bus Architectures This Appendix contains a sampling of HP bus architecture diagrams. In some cases, ioscan output is provided to help you associate the hardware configuration and the software display. Addressing on a typical multi-function (personality) card is also explained.
Bus Architectures Series 700 Bus Architecture Series 700 Bus Architecture Since its initial introduction, the Series 700 has grown enormously in breadth and ability to be configured. The figures shown illustrate the Series 700 configured as a workstation, although Model 735 can be configured to support additional 735 or 755 workstations as a cluster server. The Model 770 features multiple GSC+ buses, for versatility and I/O efficiency.
Bus Architectures Series 700 Bus Architecture Figure B-1 Model 712 Bus Relationships Model 725/100 Figure B-2, “Model 725/100 Bus Relationships,” shows a sample layout for a Model 725/100, and the example that follows it shows its ioscan -fn output. The 725 has capability for up to 4 graphics monitors. Core I/O descends from slot 2 off the system bus, and optionally at slot 5.
Bus Architectures Series 700 Bus Architecture Figure B-2 Model 725/100 Bus Relationships Class I H/W Path Driver S/W State H/W Type Description ============================================================== ========= bc 0 root CLAIMED BUS_NEXUS graphics 0 0 graph3 CLAIMED INTERFACE Graphics ba 0 2 bus_adapter CLAIMED BUS_NEXUS Core I/O Adapter ext_bus 0 2/0.1 c700 CLAIMED INTERFACE Built-in SCSI target 0 2/0.1.3 target CLAIMED DEVICE tape 0 2/0.1.3.
Bus Architectures Series 700 Bus Architecture target disk ST3600N target disk ST3600N 2 2/0.1.5 target 1 2/0.1.5.0 sdisk CLAIMED DEVICE CLAIMED DEVICE SEAGATE /dev/dsk/c0t5d0 /dev/rdsk/c0t5d0 3 2/0.1.6 target CLAIMED DEVICE 2 2/0.1.6.0 sdisk CLAIMED DEVICE SEAGATE lan LAN 0 2/0.2 /dev/dsk/c0t6d0 lan2 CLAIMED hil HIL 0 2/0.3 /dev/ether0 /dev/lan0 hil CLAIMED INTERFACE /dev/hil1 /dev/hil2 /dev/hil3 ... tty 0 2/0.4 Built-in RS-232C asio0 /dev/hil7 /dev/hil_0.1 /dev/hil_0.
Bus Architectures Series 800 Bus Architecture Series 800 Bus Architecture Model E Systems Model E computers report 806 when queried with uname -a. Slots 9 through 12 (addresses 56/36.x to 56/48.x) support HP-PB cards, as shown in Figure B-3, “HP 9000 Model E Bus Relationships.” Figure B-3 HP 9000 Model E Bus Relationships Addressing on Multi-Function Cards (Model E Example) Slots 13 and 14 (addresses 56/52.x to 56/56.x) of Model E systems are reserved for one of two multi-function (personality) cards.
Bus Architectures Series 800 Bus Architecture • MUX-based multi-function I/O card, containing single-ended SCSI, parallel port, and 8 or 16 RS-232-C ports for console, access port for remote console, and other serial devices. • LAN-based multi-function I/O card containing 802.3 LAN, serial connection for PowerTrust UPS, and remote modem access port with security option to defeat inadvertent system resets (control-B MUX defeat switch).
Bus Architectures Series 800 Bus Architecture Figure B-4 Typical I/O Addressing for a MUX/SCSI Multi-Function Card The following excerpted terse ioscan output shows only the entries for the interfaces represented by a sample multifunction card. H/W Path Class Description ======================================== ... 56/52 ext_bus HP 28655A - SCSI Interface ... 56/53 ext_bus HP 28655A - Parallel Interface 56/56 tty MUX ...
Bus Architectures Series 800 Bus Architecture • LAN-based multi-function I/O card (standard) containing an 802.3 Thin LAN interface, two serial interfaces (RS-232-C console port via circular DIN connector and access port for remote console), and a single-ended SCSI interface. • MUX-based multi-function I/O card (optional) containing 8 modem (or 8 modem and 8 direct-connect) RS-232-C ports, a single-ended SCSI interface, and a parallel port.
Bus Architectures Series 800 Bus Architecture Models 890 and T500 Systems Figure B-6, “HP 9000 T500 Configuration and Bus Relationships,” shows the configuration of a T500 system, a large system with enormous expandability; also included is excerpted ioscan output Sample Addresses The console is likely to have an address of 0/44.0. A disk array containing four disks might show several addresses (for example, 2/52.2.0, 2/52.3.0, 2/52.4.0, and 2/52.5.
Bus Architectures Series 800 Bus Architecture Figure B-6 HP 9000 T500 Configuration and Bus Relationships Class I H/W Path Driver S/W State H/W Type Description ============================================================== Appendix B 265
Bus Architectures Series 800 Bus Architecture ========= bc 1 0 bc CLAIMED BUS_NEXUS Bus Converter tty 0 0/16 mux2 CLAIMED INTERFACE HP J2092A - 16 RS-232 MUX ext_bus 2 0/28 scsi3 CLAIMED INTERFACE HP Fast/Wide SCSI Interface disk 12 0/28.0.0 disc3 CLAIMED DEVICE HP C2430D - SCSI Disk disk 13 0/28.1.0 disc3 CLAIMED DEVICE HP C2430D - SCSI Disk lanmux 0 0/44 lanmux0 CLAIMED INTERFACE LAN/Console tty 2 0/44.0 mux4 CLAIMED INTERFACE lan 0 0/44.1 lan3 CLAIMED INTERFACE lantty 0 0/44.
Bus Architectures Series 800 Bus Architecture memory memory memory processor Processor processor Processor processor Processor processor Processor processor Processor processor Processor 1 2 3 0 24 32 36 48 memory memory memory processor CLAIMED CLAIMED CLAIMED CLAIMED MEMORY Memory MEMORY Memory MEMORY Memory PROCESSOR 1 49 processor CLAIMED PROCESSOR 2 52 processor CLAIMED PROCESSOR 3 53 processor CLAIMED PROCESSOR 4 56 processor CLAIMED PROCESSOR 5 57 processor CLAIMED PROCE
Bus Architectures Series 800 Bus Architecture H/W Path Class Description ============================================= ... 8 bc I/O Adapter 10 bc I/O Adapter 10/0 ext_bus GSC built-in Fast/Wide SCSI Interface 10/0.6 target 10/0.6.
Major and Minor Numbers C Major and Minor Numbers This appendix addresses special situations in which HP-UX does not configure a driver automatically or create the required device special files. For example, you might need to configure a custom driver for black-box or instrumentation applications.
Major and Minor Numbers Understanding how the Kernel Associates Drivers to Device Understanding how the Kernel Associates Drivers to Device The kernel communicates with the hardware by associating the driver name with a hardware address. The kernel identifies the drivers it needs from the /stand/system file and finds them using the files in the /usr/conf/master.d directory. All standard HP-UX interface and device drivers shipped are located in the library /usr/conf/lib/libhp-ux.a.
Major and Minor Numbers Understanding how the Kernel Associates Drivers to Device tables — bdevsw, the block device switch table and cdevsw, the character device switch table. Drivers that support both block and character I/O (such as SCSI disk driver and optical auto changer) have both a block major number and a character major number. Devices that support only character-mode access have only a character major number. The core-hpux file in /usr/conf/master.
Major and Minor Numbers Understanding the Construction of Device Special Files Understanding the Construction of Device Special Files A long listing (ls -l) of a typical device special file might look like this: crw- 2 bin bin 193 0x010200 Jul 12 02:19 tty1p2 The two shaded fields are the major (193, decimal) and minor (0x010200, hexadecimal) numbers. Both major and minor number are encoded into a numerical designation of the device driver, called the dev_t format.
Major and Minor Numbers Understanding the Construction of Device Special Files class of the interface card when binding it into the system. This number is displayed (in decimal notation) in the I column of ioscan output.
Major and Minor Numbers Understanding the Construction of Device Special Files Examples of Minor Number Creation A Minor Number for a MUX Driver The minor number 0x010200 shown earlier for the mux2 driver can be represented as follows: Table C-2 Minor Number for the MUX2 Driver bits 8-11 12-15 16-19 20-23 24-27 28-31 binary 0000 0001 0000 0010 0000 0000 hex (0x) 0 1 0 2 0 0 0000 0001 The eight bits of the card instance number is 1 (tty1 in the device special file name).
Major and Minor Numbers Understanding the Construction of Device Special Files Adjusting Bits to Read a Floppy Disk Media used by tape drives and floppy disk drives have different densities. There might be times when you need to read a floppy disk that was written on older technology. For example, a Series 800 Model E computer has a built-in SCSI floppy disk drive whose typical minor number is 0x005000. However, when attempting to read a floppy disk originally created on a 2.
Major and Minor Numbers Minor Number Bit Assignments Minor Number Bit Assignments The tables on the following pages show the bit assignments for bits 16 through 31 for the principal HP device drivers. In all cases, bits 8 through 15 (that is NN in hexadecimal 0xNN0000) encode the card instance of the interface card through which the device communicates.
Major and Minor Numbers Minor Number Bit Assignments Table C-5 Bit Assignments for Disk and Magneto-Optical Devices bits 16-19 20-23 24-27 28-31 disc3 SCSI target SCSI LUN Reserved Section number disc4 SCSI target SCSI LUN Reserved Section number Reserved Disk partition number (always 0) sdisk Appendix C SCSI target SCSI LUN 277
Major and Minor Numbers Minor Number Bit Assignments Table C-5 Bit Assignments for Disk and Magneto-Optical Devices sflop bits 16-19 20-23 24-27 28-31 SCSI target SCSI LUN Reserved 0=3.5in 1.44MB drive, geom determined (default) 1=3.5in 1.44MB drive, no geom determined (SoftPC) 2=3.5in 720KB drive, geom determined 3=3.5in 720KB drive, no geom determined 4=3.5in 2.88MB drive, geom determined 5=3.5in 2.
Major and Minor Numbers Minor Number Bit Assignments Table C-5 Bit Assignments for Disk and Magneto-Optical Devices bits 16-19 20-23 24-27 28-31 6=not supported 7=not supported 8=5.25in 1.2MB drive, geom determined 8=5.25in 360KB drive, geom determined 9=5.25in 1.2MB drive, no geom determined 9=5.
Major and Minor Numbers Minor Number Bit Assignments Table C-6 Bit Assignments for Serial, Network, and Line Printer Devices asio0 mux0 mux2 mux4 bits 16-19 20-23 24-27 28-31 16-17 Receive fifo trigger level 18-19 Transmit fifo limit Reserved 24 - Card diagnostic bit 25 - Reserved 28 - Reserved 16-23 - Port number 26 - Reserved 27 - Hardware flow control enable 24 - Card diagnostic bit 25 - Port diagnostic bit 26 - Reserved 27 - Hardware flow control enable lan0 lan1 lan2 lan3 16-23 - Reser
Major and Minor Numbers Minor Number Bit Assignments Table C-6 Bit Assignments for Serial, Network, and Line Printer Devices bits 16-19 CentIf 16-27 - Reserved lpr0 lpr1 lpr2 lpr3 SCSI target 20-23 24-27 Handshake mode: 1=Automatic, using ACK, BUSY 2=Automatic, using BUSY only 3=Bidirectional read/write (for ScanJet) 4=Stream mode 5=Pulsed mode, using ACK, BUSY 6=Pulsed mode, using BUSY only SCSI LUN 24 - Diagnostic access 25 - Reserved 26 - Auto form feed 27 - Case fold Appendix C 28-31 28 - Raw
Major and Minor Numbers Minor Number Bit Assignments Table C-7 Bit Assignments for Miscellaneous Devices sctl bits 16-19 20-23 24-27 28-31 SCSI target SCSI LUN Reserved 0=Select with ATN enabled (default) 1=Select with ATN controlled by scsi_cmd_par ms a 2=Inhibit inquiry at open >2 - Not supported instr0 16-20 - Instrument address 21-23 Reserved pty0 pty1 Bits 8-31 - Unique hex value for pty pdn0 Bits 16-23=2 (type) 24 - Diagnostic access 25-31 - Reserved 24 - Diagnostic bit 25-31 - unus
Major and Minor Numbers Minor Number Bit Assignments Table C-7 Bit Assignments for Miscellaneous Devices audio bits 16-19 20-23 24-27 28-31 Instance Number 0=Read/writ e device 1=control only device Output destination (Ignored if Output format (Ignored if bits 28-31=0.) 0=Headphone, internal speaker, line out for Audio II 1=Headphone only 2=Int. speaker only 3=No output 4=Line output only (Audio II) bits 20-23=1) 0=No change 1=Mu-law 2=A-law 3=16-bit linear a. See /usr/include/sys/scsi.h. b.
Major and Minor Numbers Associating a Custom Driver with a Peripheral Associating a Custom Driver with a Peripheral If you are configuring HP peripherals and standard HP drivers, HP-UX configures the elements automatically, provided the drivers have been included in the kernel input file. Consider, however, the scenario of having a peripheral device for which you need to use a custom driver. Perhaps you have received the driver on a tape, which you have loaded onto your system.
Major and Minor Numbers Associating a Custom Driver with a Peripheral directly. 1. List the driver in the upper portion of the system file, with other similar drivers. For example, the following figure shows the upper portion of a system file with a custom SCSI driver, disco added.
Major and Minor Numbers Associating a Custom Driver with a Peripheral format (which resembles that of the DRIVER_INSTALL portion of /usr/conf/master.d/core-hpux): $DRIVER_INSTALL -1 -1 $$$ For example, here is a file for the disco driver. $DRIVER_INSTALL disco -1 -1 $$$ d. Verify that the driver you are installing has been built into a library that can be found by the mk_kernel utility.
Major and Minor Numbers Associating a Custom Driver with a Peripheral disco_install | 524264|extern|entry |$CODE$ g. Save the old system file by moving it. Then move the new system file into place. mv /stand/system /stand/system.prev mv /stand/build/system /stand/system h. Prepare for rebooting by invoking the kmupdate command. This action sets a flag that tells the system to use the new kernel when it restarts. /usr/sbin/kmupdate Step 2. Notify users that the system must be rebooted. Step 3.
Major and Minor Numbers Creating Device Special Files using mknod Creating Device Special Files using mknod To create device special files for any driver other than those listed on the insf and mksf manpages, use mknod. Step 1. Change directory to /dev. Step 2. Determine the major number by invoking the lsdev command. Step 3. Construct a minor number for the device by using the bit assignments for the device driver. For HP devices, the bit assignments are found in tables earlier in this Appendix.
Worksheets D Worksheets Copy these worksheets as many times as you need for the devices on your system. Keep a current copy of /usr/sbin/ioscan -fk output as an aid in configuring and troubleshooting your system.
Worksheets Interface Cards Interface Cards Table D-1 Part name and number: Version and date: Serial number: Firmware revision: Station address (LANIC ID) a : Hardware address: Dip switch settings: a. Use /usr/sbin/lanscan or /usr/sbin/lanadmin to identify the station address.
Worksheets Terminals and Modems Terminals and Modems Table D-3 Part name and number: Serial number: Cabling: Interface card, port number a : Hardware address: Dip switch settings b : Driver, device file, minor number: Modem use, baud rate, protocol: a. Note if configured via DTC or distribution panel. b. Note if configured as console or serial terminal.
Worksheets Disk Drives Disk Drives Table D-5 Part name and number: Serial number: Firmware Revision: Number of disks, capacity: Interface card, port number: Hardware address: Dip switch settings: Drivers, device special files, minor numbers: LVM physical volume, volume group: RAID level, use a : a. For example, file system, boot, dump, swap, raw data.
Worksheets Disk Drives Table D-6 LVM physical volume, volume group: RAID level, use: Table D-7 Part name and number: Serial number: Firmware Revision: Number of disks, capacity: Interface card, port number: Hardware address: Dip switch settings: Drivers, device special files, minor numbers: LVM physical volume, volume group: RAID level, use a : a. For example, file system, boot, dump, swap, raw data.
Worksheets Disk Drives Table D-8 Drivers, device special files, minor numbers: LVM physical volume, volume group: RAID level, use: 294 Appendix D
Worksheets Tape Drives Tape Drives Table D-9 Part name, number, type of tape drive: Serial number: Firmware Revision: Capacity: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, minor numbers: Use Table D-10 Part name, number, type of tape drive: Serial number: Firmware Revision: Capacity: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, minor numbers: Appendix D 295
Worksheets Tape Drives Table D-10 Use 296 Appendix D
Worksheets Printers and Plotters Printers and Plotters Table D-11 Part name, number: Serial number: Firmware Revision: Capacity: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, minor numbers: Means of access: Table D-12 Part name, number: Serial number: Firmware Revision: Capacity: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, minor numbers: Appendix D 297
Worksheets Printers and Plotters Table D-12 Means of access: 298 Appendix D
Worksheets Uninterruptible Power Systems (UPS) Uninterruptible Power Systems (UPS) Table D-13 Part name, number: Serial number: Firmware Revision: Rated load capability: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, minor numbers: Hardware coverage: Table D-14 Part name, number: Serial number: Firmware Revision: Rated load capability: Interface card, port number: Hardware address: Cabling: Dip switch settings: Drivers, device special files, mino
Worksheets Uninterruptible Power Systems (UPS) Table D-14 Hardware coverage: 300 Appendix D
Symbols /dev/cua#p# 123 /dev/cul#p# 123 /dev/mux# 105 /dev/tty#p# 105, 107 /dev/ttyd#p# 123 /etc/checklist 153 /etc/eisa/config.log file 242 /etc/exports 159 /etc/fstab 153, 164 /etc/gettydefs 133 /etc/inittab 131, 199 /etc/ioconfig 28 /etc/lp/interface 216 /etc/lvmtab 156, 158 /etc/syslog.
MSG_ONLY noncritical operation 228 Numerics 28643A 92 28643A SCSI Fiber-Optical Extender 90 5061-2569 (serial connector) 223 5961-8383 222 700/60 105 700/96 105 700/98 105 7596A Draftmaster II plotter 213 A A1439A CRX-24 graphics display interface card 78 A2269A Dual CRX graphics display interface card 78 A2941A 225 A2994A 225 A2996A 225 A2997A 225 A2998A 225 accelerator card HP A1454A 78 access mode bits 277 Access port MUX16 114 access to printers and plotters 196 adding drivers 187 adding peripherals sum
ar(1M) 270 asio0 69, 105, 107, 200, 209, 277 associating driver and peripheral manually 287 asynchronous data communication 69 ATT V.
disk drivers 276 line printer devices 277 magneto-optical devices 276 miscellaneous devices 282 network devices 277 serial devices 277 tape drivers 276 block I/O 270 block major number 271 boot administration boot ROM menus 163 LVM maintenance mode 163 mode 163 booting in LVM maintenance mode 163 BREAK signal used for INTR and baud switching 126 BSD behavior bit 276 build environment 31, 96, 108, 145, 151, 154, 156, 162, 178, 187, 207, 213, 284 bus architecture multi-processing system 264 bus relationships
C1085W 105 C2400-UTIL fileset for disk array tools 138 c700 89, 142, 174 c720 89, 142 cable length, SCSI 92 cables 92222A/B/C/D 90 C2900A 90 C2901A 90 C2902A 90 C2903A 90 C2906A 90 C2907A 90 C2908A 90 C2911A 90 for SwitchOver configurations 92 K2296 90 K2297 90 cabling guidelines RS-232-C devices 74 SCSI 90, 91 capacities, magneto-optical disk 173 capacity magneto-optical disk libraries 172 card instance 273 and class 23 and interface card 23 correlating device files 29 defined 23 cartridge tape bit 276 cas
CD-ROM configuration planning 139 cent(7) 211 CentIf 76, 203, 211, 277 handshake modes 211 centronics configuration requirements for plotters 203 for printers 203 centronics interface 76 CFG files 234 checking for correctness 246 format 234 changing choices for E/ISA board functions 240 character I/O 270 character major number 271 CharDrv 203 ChrDrv 76 CIO SCSI tape drives 184 Series 800 magneto-optical disk drives 174 Series 800 RS-232-C plotters 200 Series 800 RS-232-C printers 200 Series 800 SCSI disk dr
remove, eisa_config 244 save, eisa_config 242 set (shell command) 134 stty 133 who 129 comment command, eisa_config 239 compatibility pseudo-driver (cpd) 148 compression, data 184, 191 config(1M) 287 configuration initializing 239 configuration guidelines graphics devices 78 SCSI 89 console compared to terminal configuration 112 configuring a non-HP terminal 113 connectivity for 69 HP 700/60 configured in non-HP modes 113 planning to configure 102 VT100-compatible 113 VT320 113 Wyse 60 113 console, remote 6
CTS/RTS (hardware flow control) for modems 126 cue(1) 120 cuegetty(1M) 120 custom device drivers 284 custom drivers 65 customized graphics configurations, maintaining accuracy of 80 D daemons syslogd 229 system logging 226 UPS monitoring 226 ups_mond 229 data bits, terminal vs console 112 data communication and terminal controllers (DTC) 73 16TN/MX 73 72MX 73 J2060A/J2063A 73 J2070A 73 data compression avoiding its use on tape drives 191 dealing with 184, 191 DEC terminals 103 DEC VT terminals 114, 117 emul
and magneto-optical devices 172 and major numbers 270 associating custom driver with a peripheral 284 bit assignments 276 dev_t format 272 for parallel (centronics) plotters 203 for parallel (centronics) printers 203 for printers and plotters 199 for SCSI disk 142 for SCSI printers 205 for SCSI tape drives 184 for serial (RS-232-C) plotters 200 for serial (RS-232-C) printers 200 for terminals and modems 105 kernel association 270 location 270 major number 271 device installation requirements 17 device numbe
major and minor numbers 270 plotters 200, 203 printers 200, 203, 205 tape drives 184 diagnostic bit 276, 277 disc1 276 disc2 276 disc3 142, 143, 174, 276 disc4 276 disk class in sample ioscan output 179 disk array configuration planning 138 RAID levels 138 disk drives 7957B 142 7958B 142 7959B 142 A1999A 142 A2655A 142 A2657A 142 A3058A 142 A3182A 142 A3231A 138, 142 A3232A 138, 142 and device drivers 141 C2212A 142 C2213A 142 C2214B 142 C2216T 142 C2217T 142 C2281A 142 C2282A 142 C2290A 142 C2291A 142 C229
C2295B 142 C2425JK 142 C2427JK 142 C2460F/R 142 C2461F/R 142 C2462F/R 142 C2470S 142 C2471S 142 C2472F/R/S 142 C2473F/R/S 142 C2473T 142 C2474F/R/S 142 C2474J 142 C2476F/R 142 C2481A 142 C2482A 142 C2491A 142 C2492A 142 C3020T 142 C3021T 142 C3022R/T 142 C3023R/RZ/T 142 C3023T 142 C3024R/RZ/T 142 C3024T 142 C3027U 142 C3028U 142 C3032T 142 C3033T 142 C3034T 142 C3035T 142 C3036T 142 C3037U 142 C3038U 142 C3040R/T 142 C3041R/T 142 311
C3044U 142 C3560U 142 device special files created 142 moving using HP-UX commands 159 planning to configure 138 disk model number finding out 169 diskinfo(1M) 146, 169, 173 disks drives further tasks 170 disktab(4) 139, 155 distribution panels 0950-2431 72 28659-60005 72 5062-3054 72 5062-3070 72 5062-3085 72 5181-2085 72 ADP 5062-3070 69 ADP422 5062-3085 69 characterized 72 DDP 5062-3066 69 DDP 5181-2085 69 MDP 5062-3054 69 purpose of 71 RJ45 0950-2431 69 serial connectivity 71 DLKM (Dynamically Loadable
DTC Manager software 73 DTCs purpose of 71 serial connectivity 71 dump managing when moving a root LVM disk 159 managing when removing a disk 167 dynamically assigned major numbers 271 E E/ISA boards changing choices for board functions 240 choices 235 moving 243 removing 244 resources 234 setting switches and jumpers 243 troubleshooting configuration 246 eeprom 89 EISA boards 234 defined 76 SCSI disk drives 142 SCSI tape drives 184 eisa 89, 142 EISA device swapping to 76 eisa_config changing choices for bo
saving configuration 242 troubleshooting 246 eisa_config(1M) 206 Ethernet bit 277 EtherTwist 80 examples /etc/syslog.conf entry for redirecting UPS log messages 229 /usr/conf/master.
ioscan output of tape driver 188 lssf output for serial printer 211 lssf output for serial printer with hardware flow control (RTS/CTS) enabled 211 lvlnboot output 159 minor number for printer 210 mksf command for reading non-default tape format 190 mksf command for tape driver exhaustive mode 191 mksf command to prevent tape data compression 191 moving a disk 159 moving a printer or plotter 216 output from lssf for modem files 124 output of ps -ef 131 portion of /stand/system file 285 sample CFG file used
file-system layout 148 floppy disk drives adjusting minor number bits 275 configuration guidelines 143 configuration planning 139 device special files created 143 floppy disks and HP-UX capability for mounted file system 139 differences from PC floppies 139 intended use and limitations 139 floppy(7) 139 force configuration 284 force configuration of device drivers 284 formats handling differences on tape media 190 framebuf 77 fstab(4) 153, 164 full ioscan listing 29 further tasks disk drives 170 magneto-opt
graphics cable extensions 80 graphics card configuration guidelines 77 graphics cards and subsystems 98768A 78 A1439 78 A2269A 78 A2270A 78 A2271A 78 A2272A 78 A2666A 78 A2667A 78 A2673A 78 A2674A 78 A2675A 78 A4070A 78 A4071A 78 A4072A 78 A4073A 78 Z1100A 78 graphics configurations, maintaining accuracy of 80 graphics devices configuration information 78 installing 78 group volume group file 158 guidelines centronics (parallel) interface 76 configuring a disk with existing data 148 configuring a non-HP pri
parallel printer and plotter configuration 203 SCSI disk configuration 141 SCSI printer and plotter configuration 205 SCSI tape-drive configuration 184 serial printer and plotter configuration 199 H H/W Path defined 26 handshake bits 277 handshake modes for parallel interface 211 hardware terminals 132 hardware addresses 270 decoding 26 defined 26 determining 31 field separators 26 general 31 Models F/G/I/I, 8x7 263 on multi-function cards 261 hardware considerations for UPS 222 hardware flow control (CTS/R
HP terminals in non-HP modes 103 HP-IB interface limitations 138 HP-PB backplane slot priority 67 F/W SCSI disk drives 142 SCSI tape drives 184 Series 800 magneto-optical disk drives 174 Series 800 parallel plotters 203 Series 800 parallel printers 203 Series 800 RS-232-C plotters 200 Series 800 RS-232-C printers 200 Series 800 SCSI disk drives 142 Series 800 SCSI printers 205 Series 800 SCSI tape drivers 184 HP-UX runstate 129 HP-UX system file defined 22 I I/O hierarchy 27 identifying device special files
defined 23 location of 28 significance of 28 instr0 282 configuring devices 213 instrument address 282 interface card installing 65 interface card instance number significance of 28 interface cards 25525A/B 89 25567B 80 27147-60002 205 27147A 89 28639-50001 69 28639-60001 105, 225 28655A 76, 89, 203, 205 28696A 89 36960A 80 36967A 80 40299B 69, 105, 200, 225 98190A 69, 105, 200 98196A 105, 200 A1703-60003 69, 105, 225 A1703-60022 69, 105, 114, 225 A2544A 80 Apollo TokenRing 80 FDDI/9000 81 HIPPI Link 80 HP
J2093A 69, 225 J2094A 69, 225 J2096A 69, 225 J209x 200 J209xA 105 J2104A 80 J2109A 80 J2146A 81 J2156A 81 J2157A 81 J2159A 81 J2165A 81 J2166A 81 J2220A 81 J2226A 81 LAN/9000 80 LANLink 80, 81 maximum configurations 67 networking 80 planning to configure 66 selecting drivers 69 SNAplus Link 81 TokenRing 9000 81 X.25/9000 81 X.
using to determine available addresses 26 ISA boards 234 configuration guidelines 76 configuring 237 moving 243 removing 244 setting switches and jumpers 243 switches and jumpers 234 isdn 80 isdnnetd 80 isdnsn 80 isdnx25 80 K kernel (/stand/vmunix) 32, 162, 287 associating drivers 270 configuration file (/stand/system) 287 rebuilding to add drivers 31, 187, 207, 213 kernel (stand/vmunix) rebuilding to add drivers 107 kernel structures and ioscan(1M) 26 keyboard bits 282 kill(1) 131 killing processes 131 L L
limitations to non-HP terminal emulation 120 limited support STK 3480 tape drive 184, 191 location of device drivers 270 location of libraries 286 Logical Volume Manager (LVM) 139 need to import LVM information 148 to apportion disk space 148 lpr0 76, 277 lpr1 277 lpr2 203, 277 lpr3 205, 277 lpsched(1M) 211 lsdev(1M) 271 lssf(1M) 107, 210 LU number replaced 29 LU number, compared to instance number 29 lvlnboot(1M) 159, 164 LVM commands lvdisplay(1M) 160 lvlnboot(1M) 159, 164 lvreduce(1M) 160 lvremove(1M) 16
device special files created 174 further tasks 181 product ID strings 174 magneto-optical disk libraries C1708C 179 capacity 172 device drivers 176 further tasks 181 I/O limitations 173 installation planning 172 SCSI addresses 90 SCSI addressing guidelines 177 surfaces bits 276 magneto-optical disks access 172 device drivers 172, 174 powerfail support 173 surfaces 172 use as mountable file system 172 magneto-optical media capacity 173 ratings 173 major and minor numbers in device special files 270 major num
minor numbers bit assignments 276 creating 272 defined 271 examples 274 miscellaneous modules, DLKM 21 mk_kernel(1M) 31, 96, 108, 145, 151, 154, 156, 162, 178, 187, 207, 213, 284, 287 mkboot(1M) example 161 mknod(1M) 288 mksf(1M) 155, 190, 209 and data compression 184, 191 for modem configuration 104 used for creating device files for modems 123 Model 712 256 Model 712 floppy disk configuration 143 Model 725 257 Model 770 (J Series) 259 Model E 260 Models 890 and T500 264 Models 8x7 262 Models 8x9 (K Series
device file for dial-out port 123 device file for direct connect 123 DTR 126 duplex control 72 editing /etc/uucp/Devices 126 hardware flow control (CTS/RTS) 126 Hayes modem protocol 126 moving using HP-UX commands 128 planning to configure 103 removing using HP-UX commands 128 removing using SAM 128 requirements specific to HP-UX 126 system-side configuration 107 testing call-out ability 126 troubleshooting approach 126 using mksf(1M) 123 UUCP 103 modifying the printer address 216 module packaging 11.
A1703-60003 105 A1703-60022 105 and networking configuration 80 hardware addresses on 261 SCSI/Parallel/MUX 262 multi-function cards 260 multiplexers reset using /sbin/dasetup 132 multi-processing system bus architecture 264 multi-user mode 129 MUX connectivity 69 MUX interface for non-HP console 114 mux0 69, 105, 200, 209, 277 mux2 69, 105, 200, 209, 225, 277 mux4 69, 105, 200, 209, 225, 277 MUX-based multi-function cards 260 N naming device special files for printers and plotters 209 network interfaces 80
osi0 277 P pa 69, 89, 105, 142, 174, 200, 203, 205, 225 parallel configuration requirements for plotters 203 for printers 203 parallel interface 76 parity, terminal vs console 112 path, hardware 27 PC floppy disk configuration guidelines 143 pcfdc 143 pcfloppy 143 pdn0 80, 81, 282 performance disk drives 138 distribution of data 138 magneto-optical disk devices 172 peripheral, adding overview 31 peripherals removing using HP-UX commands 168 third party 95 personality (multi-functional) card 262 personality
magneto-optical disk libraries configuration 172 modem configuration 103 printer and plotter configuration 196 tape-drive configuration 184 terminal configuration 102 plotters 7440A 200, 203 7475A 200 7550A 200 7550B 203 7558 200 7570A 200 7576A 200 7586B 200 7595A/B 200 7596A 213 7596A/B 200 7596C 200 7599A 200 C1600A 203 C1601A 203 C1620A 200, 203 C1625A 200, 203 C1627A 200, 203 C1629A 200, 203 C1631A 203 C1633A 203 C2847A 200, 203 C2848A 200, 203 C2858A 200, 203 C2859A 200, 203 C3170A 200, 203 C3171A 200
serial (RS-232-C) configuration requirements 200 port number bits 277 ports, terminal 108 PostScript 211 power order for turning on/off 146, 179, 188 power_onoff(1M) 229 PowerTrust System Guide 222 PowerTrust Uninterruptible Power System (UPS) 231 PowerTrust UPS configuring 226 primary boot path setting 163 printer and plotter configuration planning 196 printers 2562C 200, 203 2563C 200, 203 2566B/C 200 2566C 203 2567B/C 200 2567C 203 2684A 200 2684A/P 203 2686A/D 200, 203 2932A 200, 203 2934A 200, 203 3343
C1202A 203 C1602A 200, 203 C1645A 200, 203 C1656A 203 C1676A 200 C1686A 203 C2001A 200, 205 C2010A 200, 203 C2011A 203 C2021A 203 C2040A 203 C2106A 200, 203, 205 C2113A 200, 203 C2114A 203, 205 C2121A 203 C2225C/P 203 C2225D 200 C2227A 200, 203 C2228A 200, 203 C2235A 203 C2235A/B/C/D 200 C2276A 200, 203 C2277A 200, 203 C2354A 200 C2356A 200, 203 C2562A/C 200 C2562C 203 C2563A/B/C 200, 203 C2564B/C 200, 203 C2565A 200, 203 C2566A/B/C 200 C2566B/C 203 C2567B/C 203 C2753A 205 C2754A 205 C2755A 205 331
C2756A 205 C2772A 205 C2773A 205 C2776A 205 C2777A 205 F100 206 LaserJet 4si 206 minor number example 210 parallel (centronics) configuration requirements 203 SCSI configuration requirements 205 serial (RS-232-C) configuration requirements 200 printers and plotters choosing means of access 196 configuring 219 hardware concerns 197 local and remote access 196 moving 216 network access 196 selecting device drivers 199 software concerns 198 TSM access 197 via DTCs 199 priority of backplane slots 67 problems wi
configuring LVM disk 156 configuring UPS to cycle power during non-work hours 229 force configuration of device drivers 284 manually associating driver and peripheral 287 moving disk drive to a different address 159 removing a disk drive 166 processes associated w/terminals 129 terminating 131 ps(1) 129 ps2 282 autosearch bits 282 psi0 81 psi1 81 pty0 282 pty1 282 Q QIC tape drives 190 R RAID independent mode 264 RAID levels 138 raw mode bit 277 real-time priority and UPS 226 reboot(1M) 109 rebuilding the k
root disk special considerations 159, 160 RS-232-C 105, 107 cabling 74 configuration requirements for plotters 200 configuration requirements for printers 200 interface cards 69 total cable length for UPS 223 RS-422 availability for plotter configuration 200 RS-422,423 69 rtprio 226 run-level 129 S s0 155 s2 155 sample addresses 256, 257, 263, 264 schgr 276 in sample ioscan output 179 sci files creating new 242 screen-oriented applications, running on a non-console terminal 113 SCSI addressing 90 addressing
disk array powerfail 141 disk configuration guidelines 141 disk device drivers 141 fast/wide 89 fast/wide/differential limitations 141 fiber-optic extender cable 92 floppy disk device drivers 143 grounding 93 inquiry response 169 limitations 90 line out 89 LUN bits 277 parity checking 94 power status 67 priorities of addresses 90 signal termination 93 single-ended 89 single-ended limitations 141 tape device drivers 184 target bits 276, 277 termination 93, 188 third party peripherals 95 types and characteris
scsi3 89 sctl 89, 174, 277 sdisk 142, 174, 276 in sample ioscan output 179 section number bits 276 selecting device drivers for disk drives 141 selecting device drivers for magneto-optical devices 172 selecting device drivers for tape drives 184 selecting driver for interface card 69 serial connectivity (RS-232-C) 69 serial ports cabling 74 configuring for a modem 107 configuring for a printer 206 configuring for a terminal 107 creating device files for printers and plotters 209 Series 700 bus architecture
configuring a modem 123 configuring disks with hard partitions 150 configuring LVM disks 150 ensuring the modem port is not locked 123 floppy disk configuration 143 hard partitions/sections 148 HP-PB parallel plotters 203 HP-PB parallel printers 203 HP-PB RS-232-C plotters 200 HP-PB RS-232-C printers 200 HP-PB SCSI disk drives 142 HP-PB SCSI printers 205 HP-PB SCSI tape drives 184 Model E 26, 260, 261 multi-function card 123 setting primary boot path 163 setting switches and jumpers, E/ISA boards 243 sflop
sna_trace 81 Soft PC bits 276 software applications 164 speed, default for terminals and console 112 stand/build/system 145 stape 276 Starbase Graphics Techniques 219 station address, obtaining 66 STK 3480 tape drive limited support 184, 191 stty(1) 118, 130 SupportWatch 231 surfaces in magneto-optical disk libraries 276 swap managing when moving a root LVM disk 159 managing when removing a disk 167 swapinfo(1M) 153 swapping to EISA devices 76 swinstall 224 swinstall(1M) 113 SwitchOver and cabling 92 syslog
avoiding data compression 191 C1502A 184 C1503A/B/C 184 C1504A/B/C 184 C1512A 184 C1520A/B 184 C1521A/B 184 C1530B 184 C1533A 184 C1534A 184 C1535A 184 C1553A 184 C2292A 184 C2297T/U 184 C2298A 184 C2463F/R 184 C2464F/R 184 C2465F/R 184 C2466F/R 184 C2467F/R 184 C2477F/R/S/U 184 C2478U 184 configuration bits 276 creating customized device special files 190 device special files created 184, 188 incompatibility of QIC and older cartridge media 190 index/density bits 276 planning to configure 184 STK 3480 184
target 142, 174, 205 target address defined 23 tasks configuring a DEC420 to emulate VT100 mode 114, 117 configuring a non-HP terminal as a console 113 configuring a port for a modem connection 107 configuring a port for a terminal connection 107 configuring a Wyse 60 terminal as HP console 118 configuring PowerTrust UPS 226 configuring printers 206 configuring UPS to cycle power during non-work hours 229 force configuration of device drivers 284 instr0 devices 213 maintaining accuracy of customized graphic
limitations to non-HP terminal emulation 120 moving using HP-UX commands 128 parity 112 planning to configure 102 ports 108 removing using HP-UX commands 128 removing using SAM 128 running screen-oriented applications on 113 setting default modes 111 system-side configuration 107 terminal-side configuration 111 unique definitions of VT100 keys 117 using HP 700/60 in DEC mode 117 terminals and modems configuring 136 device drivers 105 terminating processes 131 termination SCSI 93 SCSI devices 188 termio(7) 1
U unresponsive terminals 129 Upgrade.UPG-ANALYSIS fileset 149 Upgrade.
shutdown_delay_mins example 227 shutdown_timeout_mins example 227 software considerations 224 troubleshooting 231 tty class 226 UPS-TOOLS 224 upstty example 227 using crontab file 229 verifying configuration 230 voltage/amperage (VA) load considerations 222 UPS serial connector 5061-2569 223 ups_conf(4) 227 ups_mond(1M) 229 documentation of UPS error messages 231 UPS-TOOLS fileset 224 upstty example 227 usable devices, displayed with ioscan 26 UUCP for modem 103 uucp(1) 102 V verifying tape-drive configurat
HP-UX 10.
