HP-UX Operating System: Peripherals Configuration HP-UX version 11.00.
Notice The information contained in this document is subject to change without notice. UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE OF STRATUS TECHNOLOGIES, STRATUS MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PURPOSE.
Contents Preface Revision Information Audience Notation Conventions Product Documentation Online Documentation Notes Files Man Pages Related Documentation Ordering Documentation Commenting on This Guide Customer Assistance Center (CAC) ix ix ix xii xiii xiii xiii xiii xiv xv xv 1.
Contents 3. Configuring Serial Ports for Terminals and Modems Configuring Console Controller Serial Ports Configuring the Console Terminal Configuring Other Terminals 3-1 3-1 3-6 3-7 4.
Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7. Figure 1-8. Figure 2-1. Figure 2-2. Figure 5-1. Figure 6-1. Figure 7-1. Figure 7-2. Sample Listing of ioscan Sample ioscan -H Output Sample ioscan -f Output Class and Instance in ioscan Display Device Special Files Associated with a Peripheral ftsmaint Output ftsmaint Output for 1/0 ftsmaint Output for 0/2/7/2 Sample download.conf File Sample personality.
Tables Table 3-1. Table 5-1. Table 5-2. Console, RSN, and Auxiliary Port Configuration Tape-Drive Commands and Special Files Unsupported Commands HP-UX version 11.00.
Preface Preface This manual describes how to configure peripherals for Continuum systems. Revision Information This manual has been revised to reflect support for Continuum systems using suitcases with the PA-8600 CPU modules, additional PCI card and storage device models, company and platform1 name changes, and miscellaneous corrections to existing text. Audience This document is intended for system administrators who install and configure the HP-UX™ operating system.
Notation Conventions – Monospace bold represents user input in screen displays. For example, ls -a ■ Monospace italic represents variables in commands for which the user must supply an actual value. For example, cp filename1 filename2 It also represents variables in prompts and error messages for which the system supplies actual values.
Notation Conventions ■ A right-arrow (>) on a sample screen indicates the cursor position. For example, >install - Installs Package ■ A name followed by a section number in parentheses refers to a man page for a command, file, or type of software.
Product Documentation DANGER Danger notices alert you to conditions that are potentially lethal or extremely hazardous to people.
Product Documentation Online Documentation When you install the HP-UX operating system software, the following online documentation is installed: ■ notes files ■ manual (man) pages Notes Files The /usr/share/doc/RelNotes.fts file contains the final information about this product. The /usr/share/doc/known_problems.fts file documents the known problems and problem-avoidance strategies. The /usr/share/doc/fixed_list.fts file lists the bugs that were fixed in this release.
Product Documentation ■ The HP-UX Operating System: Continuum Series 400 Hardware Installation Guide (R002H) or the HP-UX Operating System: Continuum Series 400-CO Hardware Installation Guide (R021H) describes how to install a complete Continuum Series 400 or 400-CO system from unpacking the system components to booting the machine.
Customer Assistance Center (CAC) When ordering a documentation CD-ROM please specify the product and platform documentation you desire, as there are several documentation CD-ROMs available. When ordering a printed manual, please provide the title, the part number, and a purchase order number from your organization. If you have questions about the ordering process, contact the CAC. Commenting on This Guide Stratus welcomes any corrections or suggestions for improving this guide.
1 Getting Started 1- When you physically install a disk drive, tape drive, expansion cabinet, or other peripheral device, you sometimes must configure the HP-UX operating system to communicate with it. Many portions of a Continuum system are preconfigured and do not require additional administrator actions, but some peripherals require configuration in order for Continuum systems to recognize them.
Peripherals and Fault Tolerant Hardware Keep this manual, the online man pages, and any other manuals that were shipped with your Continuum system available for reference when installing and configuring peripheral devices. Commands such as mksf, insf, and ioscan, as well as the Stratus value-added ftsmaint command, make it unnecessary to manipulate the device special minor number literally.
Peripherals and Fault Tolerant Hardware Differences from Hewlett-Packard Systems Stratus and Hewlett-Packard systems do not support the same set of peripheral devices.
Peripheral Configuration in Its Simplest Terms Peripheral Configuration in Its Simplest Terms A peripheral device requires two or three configuration steps to communicate with the HP-UX operating system: configure, install, and (if needed) reboot. Most devices supported by Continuum systems do not need a system reboot to be recognized by the system. Standard device drivers are already present in the kernel. 1. Configure the device drivers into the kernel.
Peripheral Configuration in Its Simplest Terms Using SAM to Configure Peripherals The System Administration Manager (SAM) provides the easiest way to view your Continuum system configuration and configure the peripheral device drivers into the kernel. To invoke SAM, enter sam SAM’s user interface and online help system allow you to discover the configuration information as you proceed through its screens.
Understanding Device Special File Names Understanding Device Special File Names Device special files tell the HP-UX 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. For example, device special files for tape drives show rewind and density. Most device special file names contain the location of the device on the bus architecture.
Viewing System Configuration with ioscan Here are some sample device special files and their possible meanings: /dev/rdsk/c0t2d0 Entire disk accessed in character (raw) mode through SCSI card instance 0, target 2, LUN 0. /dev/rmt/c1t0d0BESTnb Tape drive accessed through card instance 1, target 0, LUN 0. Tape writes at best available density/format, no rewind, Berkeley-style close. /dev/rmt/0mnb Tape drive device special file with identical characteristics (linked) to /dev/rmt/c1t0d0BESTnb.
Viewing System Configuration with ioscan # ioscan -u H/W Path Class Description ==================================================== 0/0/0 phys_cpus CPU Adapter 0/0/1 phmem MEM Adapter 0/1/0 phys_cpus CPU Adapter 0/1/1 phmem MEM Adapter 0/2/0/0 pcmcia 0/2/0/0.0 flash PCMCIA Bridge FLASH Adapter 0/2/1/0 pseudo LAN Adapter 0/2/2/0 tty Asyn Card 0/3/0/0 pcmcia 0/3/0/0.
Viewing System Configuration with ioscan # ioscan -H 0/4/0/1 H/W Path Class Description ======================================= 0/4/0/1 ext_bus HSC SCSI Adapter Figure 1-2.
Viewing System Configuration with ioscan # ioscan -f Class I H/W Path Driver S/W State H/W Type Description ========================================================================== bc 0 root CLAIMED BUS_NEXUS ba 0 0 gbuscdio CLAIMED BUS_NEXUS ba 1 0/0 pmerc CLAIMED BUS_NEXUS PMERC Nexus phys_cpus 0 0/0/0 merc_cpus CLAIMED INTERFACE CPU Adapter phmem 0 0/0/1 phmem CLAIMED INTERFACE MEM Adapter ba 2 0/1 pmerc CLAIMED BUS_NEXUS PMERC Nexus phys_cpus 1 0/1/0 me
Viewing System Configuration with ioscan Understanding Class and Instance The sample ioscan output in Figure 1-4 shows the ext_bus class of a sample Continuum system. The card instance numbers are listed under I. For device file naming and hardware mapping, the only significant instance numbers are those associated with the INTERFACE hardware type.
Viewing System Configuration with ioscan Card Instances and Device Files Card instance number and hardware path elements map directly into the device special file as card instance, target number, and device number. For example, the disk device special file /dev/dsk/c1t3d0 refers to instance one of the logical SCSI manger (lsm), target disk with SCSI ID 3, and logical unit number (lun) of 0. Typically, the card instance maps as the digit after the letter c (or for terminals, the number after tty).
Viewing System Configuration with ioscan # ioscan -C disk -fun Class I H/W Path Driver S/W State H/W Type Description ====================================================================== disk 0 14/0/0.1.0 sdisk CLAIMED /dev/dsk/c0t1d0 disk 1 14/0/0.2.0 sdisk CLAIMED /dev/dsk/c0t2d0 disk 2 14/0/0.3.0 sdisk CLAIMED /dev/dsk/c0t3d0 disk 3 14/0/0.4.0 sdisk CLAIMED /dev/dsk/c0t4d0 disk 4 14/0/0.5.0 sdisk CLAIMED /dev/dsk/c0t5d0 disk 5 14/0/1.0.
Using ftsmaint to Administer System Hardware Using ftsmaint to Administer System Hardware The ftsmaint command is the primary utility for managing Continuum system hardware components.
Using ftsmaint to Administer System Hardware # ftsmaint ls Modelx H/W Path Description State Serial# PRev Status FCode Fct ================================================================================ - CLAIM - - Online - 0 GOLFBUS Nexus CLAIM - - Online - 0 g31100 0/0 PMERC Nexus CLAIM 10432 9.0 Online - 0 - 0/0/0 CPU Adapter CLAIM - - Online - 0 m70700 0/0/1 MEM Adapter CLAIM - - Online - 0 g31100 0/1 PMERC Nexus CLAIM 10414 9.
Using ftsmaint to Administer System Hardware p21400 12/0/8 AC Power Controller CLAIM - - Online - 0 p21400 12/0/10 AC Power Controller CLAIM - - Online - 0 p20600 12/0/12 Power Supply Unit 0 CLAIM - - Online - 0 p20600 12/0/13 Power Supply Unit 1 CLAIM - - Online - 0 - 13 LNM Nexus CLAIM - - Online - 0 - 13/0/0 LAN Adapter CLAIM - 0 Online - 0 - 13/0/1 LAN Adapter CLAIM - 0 Online - 0 - 14 LSM Nexus CLAIM - - Online - 0 - 14/0/0 LSM Adapter CLA
Using ftsmaint to Administer System Hardware # ftsmaint ls 1/0 H/W Path : 1/0 Device Name : reccs Description : RECC Adapter Class : phys_reccs Instance : 0 State : CLAIMED Status : Online Modelx : e593 Sub Modelx : 00 Board Type : 0 Board Rev : 59 Art Rev : 0 Min Partner Revision: 0 Firmware Rev : 18.0 Serial# : 10432 Fault Count : 0 Fault Code : - MTBF : Infinity MTBF Threshold : 600 Seconds Weight. Soft Errors : 1 Min. Number Samples : 6 Figure 1-7.
Using ftsmaint to Administer System Hardware # ftsmaint ls 0/2/7/2 H/W Path : 0/2/7/2 Partner H/W Path : 0/3/7/2 Device Name : dpt Description : SCSI Adapter W/SE Class : ext_bus Instance : 18 State : CLAIMED Status : Online Duplexed Modelx : u501 Sub Modelx : 00 Firmware Rev : 0ST5 Serial# : 42-000643 PCI Vendor ID : 0x1044 PCI Device ID : 0xA400 Fault Count : 0 Fault Code : - MTBF : Infinity MTBF Threshold : 600 Seconds Weight. Soft Errors : 1 Min.
2 Configuring Interface Cards 2- This chapter discusses removing and replacing components, and downloading firmware. It ends with a summary on configuring a peripheral. Removing and Replacing Components The HP-UX operating system adds components to the system structure at boot time by inventorying the existing Continuum hardware components and configuring the system accordingly.
Downloading Firmware Downloading Firmware On Continuum systems a user-level daemon is responsible for downloading firmware. This daemon is downloadd. See the downloadd(1M) man page for additional information. This daemon is used to download firmware for the Async, SDLC, and X.25 protocols. Each time the system boots, downdloadd is started and performs its designated actions, including: ■ renaming the logfile /var/adm/download.log to /var/adm/download.log.
Downloading Firmware /etc/stratus/download.conf --------------------------# This is a configuration file for Continuum Series 400 hardware # Key hw_path fw_path Modelx personality event command # Async Card F * - u45000 - INI "/usr/sbin/asyndload -i $INST" C - - - - ENA "/usr/sbin/asyndload -i $INST" C - - - - ACT "/usr/sbin/asyndload -i $INST" F * - k11800 INI "/usr/sbin/kdload -d /dev/diag/mux$INST -f \ /etc/stratus/prom_code/ioa18_async.
Downloading Firmware paths. The hardware paths are identified when entry in the Modelx field and the entry in the personality field from the download.conf file match the entry in the Modelx field and the entry in the personality field from the personality.conf file. A Fault Tolerant Service (FTS) event, such as initiating, enabling, disabling, activating, or deactivating the device. The event determines when the actions specified in the command field will be executed.
Downloading Firmware The fields in the /etc/stratus/personality.conf file have the same purpose and meaning as the fields in the /etc/stratus/download.conf file. New cards with a Modelx entry configured in the /etc/stratus/download.conf can be added any time. Whenever a new card is added, downloadd: ■ identifies the new device ■ determines if the model for the device is present in the download.
Configuring a Peripheral (A Summary) In this case, 11/10/12 is the desired slot for the K118 device, and /etc/stratus/prom_code/ioa18_async.pm is the firmware file name you want to burn on this device. Configuring a Peripheral (A Summary) First, prepare for configuring the peripheral by gathering information required for the successful configuration of the peripheral. The considerations vary depending on the peripheral type and are discussed in each peripheral-specific chapter.
3 Configuring Serial Ports for Terminals and Modems 3- This chapter contains the procedures for configuring serial ports and related terminals and modems on a Continuum system. For the HP-UX operating system to communicate with a terminal or modem, the following conditions must be met: ■ The serial device driver that is required to communicate with the device must be configured into the kernel. ■ The terminal or modem must be attached and configured to the port.
Configuring Console Controller Serial Ports The console controllers support three serial ports, a console port, a port reserved for the RSN modem, and an auxiliary port that you can use for various purposes (for example, an external UPS). The ports are located on the back of the system base or cabinet in a Continuum system.
Configuring Console Controller Serial Ports 3. Burn the port configuration information into the standby console controller. To burn the config partition, enter ftsmaint burnprom -F config hw_path hw_path is the hardware path of the standby console controller (as determined in step 2), which is either 1/0 or 1/1. For example, if the standby console controller is located at 1/0, enter ftsmaint burnprom -F config 1/0 4.
Configuring Console Controller Serial Ports 5. The system next displays the following three prompts: power up on boot [1]: allow host config [0]: shadow console setup [0]: To change a default value, enter the new value at the appropriate prompt. These prompts serve the following purposes: – The power up on boot prompt allows you to set whether the system automatically powers up when power is restored to the system after being shut down.
Configuring Console Controller Serial Ports 6. To activate the new settings, the standby console controller you just updated must become the online console controller. To switch the status of both controllers (online becomes standby and vice versa), enter ftsmaint switch hw_path hw_path is the hardware path of the standby console controller (as determined in step 2), which is either 1/0 or 1/1. For example, if the standby console controller is located at 1/0, enter ftsmaint switch 1/0 7.
Configuring the Console Terminal Configuring the Console Terminal The addhardware command detects any new terminals added to the system and automatically configures them into the system, without need for shutdown or reboot. Therefore, any qualified terminal with a valid entry in the system terminfo file can be configured into the system simply by running the addhardware command. For more information, see the addhardware(1) man page.
Configuring Other Terminals and Maintenance Guide (R024H) for more information on terminal setup and settings. If you lose communication with the system, also check the serial cable connections. Configuring Other Terminals As noted in the preceding section, “Configuring the Console Terminal,” you can configure a new terminal into the system simply by running the addhardware command.
Configuring Other Terminals 3. To create a new terminfo file, follow the directions in the terminfo(4) man page. To adapt an existing terminfo file, follow these steps: a. Log in as super-user. b. Make an ASCII copy of an existing terminfo file. For example, to copy the file /usr/share/lib/terminfo/w/wy100, enter untic wy100 > new_file c. Edit the new file to reflect the capabilities of the new terminal. Make sure you change the name(s) of the terminal in the first line. d.
4 Configuring Disk Drives 4- This chapter gives procedures and guidelines for configuring disk drives using the SCSI interface.
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. The correct device driver must be present in the kernel for the interface and disk device you are installing. Once you have planned your disk configuration, proceed to the “Managing Disk Devices” section. Performance Overall system performance depends partly on how your disks are arranged on your system.
Managing Disk Devices Managing Disk Devices The procedures in this section apply to all cases of adding, replacing, moving, and deleting disk drives. CAUTION Although SAM allows you to manage disk devices, do not use SAM for any of the following procedures (add, replace, move, or delete a disk). Using SAM might cause the procedure to fail and leave the LVM in an inconsistent state. NOTE This chapter includes procedures for adding, replacing, moving, or deleting a disk.
Managing Disk Devices 4. Verify that the new disk is configured into the system by entering the following commands: ioscan -fn -C disk ftsmaint ls hw_path hw_path is the hardware path to the disk. Confirm that the disk is present, CLAIMED, and Online, and that device special files have been created for it in the /dev/dsk and /dev/rdsk directories.
Managing Disk Devices b. To determine the mirror state of the logical volumes, enter lvdisplay lv_name lv_name is the path name (identified in step a). Check the field Mirror copies for mirror information. Repeat for each logical volume. 4. Deallocate the logical volumes by entering lvreduce [-m 0] lv_path pv_path lv_path is the block device path name of the logical volume and pv_path is the path name of the physical volume (the disk to be replaced).
Managing Disk Devices 9. Add the physical volume to the volume group by entering vgextend vg_name pv_path vg_name is the volume group name and pv_path is the block device file name, for example, /dev/dsk/c0t1d0. 10. Do one of the following: a. If you replaced a mirrored disk, reestablish the volume mirror by entering lvextend -m 1 vg_name pv_path Repeat for each logical volume. b. If you replaced a nonmirrored disk, restore the missing data from your backup archives (if available).
Managing Disk Devices b. To determine the mirror state of the logical volumes, enter lvdisplay lv_name lv_name is the path name (identified in step a). Look in the Mirror copies field for mirror information. Repeat for each logical volume. 4.
Managing Disk Devices 8. Create a physical volume on the new disk by entering pvcreate [-B] rpv_path rpv_path is the character (raw) device file name for the new disk, for example, /dev/rdsk/c0t1d0. Use the -B option if this is a boot disk. 9.
Managing Disk Devices 3. If you are moving a root LVM disk, determine the current root-disk configuration by entering lvlnboot -v This command displays the boot disk(s) device path name(s) and the logical volumes for boot, root, swap, and dump. Verify that the root disk is mirrored, and record the path name of the disk to be moved. CAUTION Do not move a root disk unless it is mirrored. Moving an unmirrored root disk will crash the system.
Managing Disk Devices 8. Remove the disk drive from its current slot and insert it into its new slot, following instructions provided in the hardware documentation. See the HP-UX Operating System: Continuum Series 400 Operation and Maintenance Guide (R001H), the HP-UX Operating System: Continuum Series 400-CO Operation and Maintenance Guide (R025H), or the HP-UX Operating System: Continuum Series 600 and 1200 Operation and Maintenance Guide (R024H) for instructions. 9.
Managing Disk Devices 13. If the newly located disk is not the root disk, you can mount it by entering mount -a If the newly located disk is the root disk, it has been mounted already by other means. 14. Update any software application configurations that use the relocated disk drive to make sure they use the new device files. See your software application documentation for specific instructions.
Managing Disk Devices 6. If you are removing a nonmirrored LVM disk and you want to save the data, move all the data contained on the disk to another disk by entering pvmove source_pv_path dest_pv_path source_pv_path is the path name of the physical volume (disk to be removed) and the dest_pv_path is the path name of the destination physical volume. 7. If you are removing a mirrored online LVM disk, remove the disk from its current configuration.
Managing Disk Devices Determining Disk Drive Characteristics To display information about a specific disk, enter diskinfo char_device char_device is the character special file for that disk, as in the following example: # diskinfo /dev/rdsk/c1t0d0 SCSI describe of /dev/rdsk/c1t0d0: vendor: SEAGATE product id: ST32550W type: direct access size: 2097029 Kbytes bytes per sector: 512 SCSI disks can be further identified by the product ID field.
After Configuring the Disk Drive After Configuring the Disk Drive After configuring the HP-UX operating system for a disk device, you can complete the following tasks required to put it to use: ■ setting up powerfail 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 ■ making the disk available for swapping ■ creating or moving file systems ont
5 Configuring Tape Drives 5- Several kinds of tape drives, having different recording methods and formats, can be configured to the HP-UX operating system.
Configuring a Tape Drive When configuring a tape drive, have available the following additional documentation: ■ Continuum 600 and 1200 Series: Tape-Drive Operation Guide (R442), HP-UX Operating System: Continuum Series 400 Hardware Installation Guide (R002H), HP-UX Operating System: Continuum Series 400-CO Hardware Installation Guide (R021H), or other appropriate installation guide ■ HP-UX Operating System: Fault Tolerant System Administration (R1004H) ■ the online man pages Tape drives can be confi
Configuring a Tape Drive 3. Install the tape drive, following instructions provided in the hardware documentation. See the HP-UX Operating System: Continuum Series 400 Hardware Installation Guide (R002H) or the HP-UX Operating System: Continuum Series 400-CO Hardware Installation Guide (R021H) for instructions. 4. Turn on power to the tape drive. 5. Configure the device into the system.
After Configuring a Tape Drive 7. Verify that you can read and write to and from the device. One way to do this is through the tar command. In the following example, the first tar command writes the /etc/passwd file to tape using a device special file shown in the ioscan output from step 6. The second tar command displays the contents of the tape.
After Configuring a Tape Drive Table 5-1.
After Configuring a Tape Drive Table 5-1.
6 Configuring CD-ROM Drives 6- NOTE Continuum Series 400 systems support CD-ROM drives in a slightly different manner than Hewlett-Packard systems, due to support on the external SCSI bus only. However, Continuum Series 600 and 1200 systems support CD-ROM drives in the same manner as Hewlett-Packard systems. If you are aware of the Hewlett-Packard system model for CD-ROM support, you should be aware of these differences before replacing or installing a new CD-ROM drive.
Configuring a CD-ROM Drive Because CD-ROM disks hold only read-only file systems, you cannot create new file systems on CD-ROM or use them for swap space. Continuum Series 400 systems boot off a flash card. This means they cannot use CD-ROM drives as boot devices. However, Continuum Series 600 and 1200 systems can use CD-ROM drives as boot devices. See the HP-UX Operating System: Installation and Update (R1002H).
Configuring a CD-ROM Drive b. For Continuum Series 600 and 1200 systems, check the location of the CD-ROM drive by entering ftsmaint ls Check for addresses that are already used. The new CD-ROM can use any other legal address. 3. Install the CD-ROM hardware, following instructions provided in the hardware documentation. 4. For Continuum Series 400 systems only, turn on power to the CD-ROM drive. 5.
7 Configuring Asynchronous Serial Interfaces 7- This chapter contains information on how to configure the asynchronous serial interface on Continuum systems. HP-UX operating system multiplexers provide asynchronous data communication through RS-232C protocols. These RS-232C serial ports can support additional terminals, modems, or related devices.
Loading the Asynchronous Card Firmware Notice that the instance number (column I) for the asynchronous serial interface card in the example is 1. The other instance numbers are for the three console controller ports. Instance numbers are assigned according to standard HP-UX operating system protocols. If no instance for the card is found on the flash card during booting, one will be assigned.
Creating Device Special Files briefly describes how to create device special files from the command line. Determine the instance number of the interface card you are configuring. To check instance numbers, enter ioscan -f Instance numbers are in the I column. Port numbers 0–7 are assigned to the individual interfaces on each async card. NOTE Port numbers are numbered 0—7, but the numbers printed on the arms of the octopus cable are 1—8. Subtract one from the cable number to obtain the port number.
Attaching Devices to the Asynchronous Serial Interface Attaching Devices to the Asynchronous Serial Interface The following sections describe issues and procedures related to attaching devices (modems or terminals) to an asynchronous serial interface. Cable Connection and Flow Control Cable connection and flow control require some understanding of the concepts behind them. DTE and DCE Controllers An asynchronous port behaves like data terminal equipment (DTE).
Attaching Devices to the Asynchronous Serial Interface Null modem cable pins must be correctly configured. If the pins are not correctly configured, getty operations will not work. The correct pin positions are shown in Figure 7-2. DCE 1 2 3 4 5 6 ] 8 20 DTE 1 3 2 5 4 20 6 [ 8 Figure 7-2. Null Modem Cable Pin-Outs Configuring in the Device You might need to add a getty entry to the /etc/inittab file for each new device if a login is needed.
Attaching Devices to the Asynchronous Serial Interface ■ 4800 baud ■ 9600 baud ■ 19200 baud ■ 38400 baud (not available for Continuum Series 600 and 1200 systems) The stop bits supported are 1.5 bits and 2 bits. Supported data bits are 5 bits, 6 bits, 7 bits, and 8 bits. Parity options of even, odd, and no parity are available. Hardware and software flow control is recommended for baud rates above 19200 baud.
Attaching Devices to the Asynchronous Serial Interface 2. Instruct the system to use the new (latest) /etc/inittab settings by entering init q 3. Add an (optional) entry to /etc/ttytype. Entries should conform to the format documented on the ttytype(4) man page. The following are two sample entries: 2392 console 2392 tty0p3 2392 is the terminal type, while console and tty0p3 are the device file names in the /dev directory. 4. The HP-UX operating system will now communicate with the new terminal.
Attaching Devices to the Asynchronous Serial Interface To set up the modem through the SAM interface, determine the following: ■ the hardware path (including the instance number and port number) of the asynchronous serial interface to be used by the modem (by entering the ioscan -C tty command) ■ the modem’s baud rate ■ whether the modem will be used for outgoing calls ■ whether the modem will receive incoming calls ■ whether the modem requires CCITT (required only by certain European government p
Additional References ■ If modems connect to each other, but no data appears, turn off all compression, reliability, MNP, PEP, LAP, and other advanced features. Set the modem as simply as possible. Once working, add the advanced features. ■ Do not use CCITT control signals on either modem or system. This does not affect the modem use of CCITT modulation or compression standards such as V.22, V.32, V.22bis, V.32bis, V34, V.42, or V.42bis.
Index A addhardware command, 1-11, 2-1, 3-6, 4-3, 5-3, 6-3 administrative tasks standard command paths, 1-1 asynchronous adapter card creating device file for, 7-2 loading firmware, 7-2 asynchronous serial interface attaching devices to, 7-4 hardware support, 7-1 C cable pins, null modem, 7-5 CAC, contacting, xv CCITT, modems requiring, 7-8 CD-ROM drives configuring into system, 6-2 mounting, 6-3 components see hardware components console configuring serial port for, 3-2 enabling secondary port, 3-4 setti
Index G getty entry, terminal, 7-6 groups see volume groups H hardware address displayed in ioscan, 1-8 format of, 1-9 hardware components configuration summary, 2-6 configuring through commands, 1-5 configuring through SAM, 1-5 installing peripherals, 1-4 removing or replacing, 2-1 hardware paths defining, 1-2 determining, 1-2, 1-8 I insf, compression default, 5-4 instance, device, 1-12 interface cards binding to driver, 1-11 ioconfig files binding interface cards, 1-11 updated by addhardware, 1-11 ioin
Index ports see serial ports R reboot, after installing devices, 1-4 root disk, determining configuration, 4-9 RSN, configuring serial port for, 3-2 S SAM configuring peripherals through, 1-5 managing disk devices, 4-3 serial ports, 7-1 configuring console controller, 3-1 default configurations, 3-2 shadow console setup prompt, 3-4 System Administration Manager see SAM system configuration managing data storage, 4-2 viewing with ftsmaint, 1-14 viewing with ioscan, 1-7 T tape drives commands for using, 5-
