Models V743/64 and V743/100 Owner's Guide HP 9000 Series 700 VXIbus Controllers ABCDE HP Part No.
Legal Notices The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
OSF/Motif is a trademark of the Open Software Foundation, Inc., in the U.S. and other countries. Certi cation for conformance with OSF/Motif user environment pending. This software and documentation is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. Restricted Rights Legend. Use, duplication or disclosure by the U.S.
Printing History This manual's printing date and part number show its 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 manual part number will change when extensive changes occur. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive these updates or new editions, you should subscribe to the appropriate product support service.
Safety Symbols and Conventions The following conventions are used throughout this manual: Note Caution Warning Notes contain important information set o from the text. Caution messages indicate procedures which, if not observed, could result in loss of data or damage to equipment. Do not proceed beyond a CAUTION sign until the indicated conditions are fully understood and met. Warning messages indicate procedures or practices which, if not observed, could result in personal injury.
Regulatory Information FCC Statement (For U.S.A. Only) The Federal Communications Commission (in Subpart J of Part 15, Docket 20780) has speci ed that the following notice be brought to the attention of the users of this product: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.
VCCI Statement (Japan Only) vii
x x x x x x x x x x x x Replace this page with the Ventura Decl of Conformity xxxxxxxx viii
Printing Conventions This book uses the following typographical conventions: If you see . . . It means . . . computer text Represents text you will see on the screen or text you must type/enter yourself. For example, login: indicates a login prompt displayed by the system. italic text Variable text supplied by you. For example, le name means that you type a le name of your choice. Italic text is also used for text emphasis and for document titles. 4Key5 Type the corresponding key on the keyboard.
Contents 1. Product Description Chapter Contents . . . . . . . . . . . . . . . . The HP 9000 Model V743 Embedded VXI Controller Features . . . . . . . . . . . . . . . . . . . Memory Con gurations . . . . . . . . . . . . Interfaces . . . . . . . . . . . . . . . . . . Graphics . . . . . . . . . . . . . . . . . . . Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-2 1-2 1-3 1-4 1-5 1-6 2.
4. Con guring for a VXI/MXI System Chapter Contents . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . Description of HP SICL . . . . . . . . . . . . . . . Examining Your VXI/MXI Con guration . . . . . . . . Default Values . . . . . . . . . . . . . . . . . . . Changing Your VXI/MXI Con guration . . . . . . . . . Changing the VXI Shared Memory . . . . . . . . . . Con guring the VXI/MXI Trigger Lines . . . . . . . . . Routing VXI TTL Trigger Lines in a VXI/MXI System .
7. Con guring HP-UX for a DDS Tape Drive Chapter Contents . . . . . . . . . . . . . . . Finding the Status of Existing SCSI Bus Addresses Con guring for a Backup DDS Tape Drive . . . . Con guring the Drive on HP-UX . . . . . . . Testing Your Installation . . . . . . . . . . . DDS Tape Drive LED Indicators . . . . . . . Maximum Usage of DDS Cassettes . . . . . . In Case of Di culty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B. Using the Boot Console Handler Appendix Contents . . . . . . . . . . . . . . . The Boot Console Handler . . . . . . . . . . . . Special Tasks . . . . . . . . . . . . . . . . . Boot Console Information Display . . . . . . . . Using the Boot Console Handler Interface . . . . Con guring the Console Path and Display Format Booting and Resetting the VXIbus Mainframe . . Searching for Bootable Media . . . . . . . . . . Displaying and Setting Paths . . . . . . . . . .
1 1 Product Description Chapter Contents Features. Memory Con gurations. Interfaces. Graphics. Operating System.
1 The HP 9000 Model V743 Embedded VXI Controller The HP 9000 Model V743 VXI controller is an exceptionally exible and responsive high-performance Precision Architecture VXI controller based on the Hewlett-Packard PA-RISC 7100LC technology. Some of the features are outlined in this chapter. See your Installation Guide for detailed hardware information. Features The Model V743 VXI controller has the following general features: Single-slot VXI C-size con guration. 64-MHz PA-RISC processor (Model V743/64).
1 Memory Configurations Figure 1-1. Four RAM Cards Installed The standard Model V743 VXI controller comes with either 16 MB or 32 MB factory-installed RAM, with other options possible. It can be upgraded by the user with internal RAM cards as follows (two cards per upgrade): HP A2578A; 16 MB total. HP A2829A; 32 MB total. HP A2827A; 64 MB total. Upgrades or factory-integrated RAM provide the Model V743 VXI controller with up to 128 MB maximum memory. See Appendix A for installation instructions.
1 Interfaces For graphics, printing, and LAN communications, the Model V743 VXI controller provides the following I/O interfaces: Graphics (on-board GSC; integrated color). 640 x 480 (15-in. monitor). 800 x 600 (15-in. monitor). 1024 x 768 (15- or 17-in. monitor). 1280 x 1024 (17- or 20-in. monitor). 1024 x 768 (11.8-in. at panel). (Not currently supported) LAN AUI (high-density, 15-pin D-subminiature; requires a custom cable and MAU for connection to LAN).
1 Physical Dimensions and Power Requirements The Model V743 VXI controller occupies one standard VXI slot. Height: 30.48 mm (1.2 in.) Width: 259.84 mm (10.23 in.) Depth: 368.30 mm (14.5 in.) Power Requirements: DC Voltage +5V + 12 V - 12 V + 24 V - 24 V - 5.2 V -2V +5V STDBY DC Current 10 A 250 mA 80 mA 40 mA 0 mA 560 mA 480 mA 0 mA Dynamic Current 100 mA 3 mA 2 mA 1 mA 0 mA 4 mA 2 mA 0 mA Note that +24V is required only for a at-panel display (not currently supported).
1 Operating System Table 1-1 lists the HP-UX operating system features and languages for the Model V743 VXI controller. Table 1-1. Operating System and Languages for the Model V743 VXI Controller Operating system: HP-UX 9.05 or later Languages: HP-PA Assembler 1.1 C and ANSI C C++ Pascal ANSI FORTRAN SICL for C Programming, Revision 3.9 User Interface: HP-UX 9.05 includes the X Window System and can be con gured with HP VUE 3.0. Network Features: IEEE 802.
2 Finding Information About Your System Chapter Contents Manuals for System Information: HP-UX HP VUE Online Sources of Information.
2 Overview The Model V743 VXI controller uses the standard HP-UX operating system, a highly versatile system for multitasking, running your application programs, and performing a variety of development tasks. For information on installing HP-UX 9, see the manual Installing and Updating HP-UX 9.03 (and the 9.05 Release Notes for updates). For HP-UX 10, see Installing HP-UX 10 (and the Release Notes in the /usr/share/doc directory for updates).
updates) for HP-UX 9, or see Installing HP-UX 10 (and the Release Notes in the usr/share/doc directory) for HP-UX 10. For troubleshooting HP-UX, see Chapter 9 in this manual, and the manual Solving HP-UX Problems . VXI For VXI con guration information, see the C-Size VXIbus Systems Con guration Guide . For VXI programming information, see the HP SICL User's Guide for HP-UX . HP VUE For information on using and con guring the HP VUE interface with HP-UX, see the HP VUE User's Guide .
2 Online Sources of Information HP-UX is designed so that you can access many sources of information without leaving your system. Most of these information sources are accessible via the shell command line on a character terminal. Man Pages: The information on HP-UX which is found in HP-UX Reference is also available online.
Newcon g: The directory /etc/newconfig for HP-UX 9, or usr/share/doc for HP-UX 10, contains information and new versions of HP-UX product con guration les, as well as shell scripts which may have been customized on your system. The contents of this directory will vary depending on which products you have loaded on your system. In most cases, old versions of these les, in their regular locations in the le system, are not overwritten by the update process.
3 Getting Started with HP-UX 3 Chapter Contents Before Logging In the First Time. Turning On the System. Con guring the Controller. Con guring the RS-232 Ports. Logging In and Out. Creating a New User Account. Setting or Changing a Password. Selecting a New Password. Powering Down the System. Using the Command Line.
Before Logging In the First Time 3 If your Model V743 VXI controller does not have a hard disk connected, or if it has a le system disk, and you want it to be a cluster client node (cnode), refer to the manual Managing Clusters of HP 9000 Computers for instructions on setting up HP-UX clusters and cnodes. This chapter reviews some initial procedures and provides information on using both HP VUE sessions and HP-UX. For more detailed information about using HP VUE after login, see the HP VUE User's Guide .
3 Figure 3-1. Model V743 VXI Controller in Mainframe System Requirements You should check to see that you have connected the following components before proceeding further with booting your system: Host System: HP Model E1401A or equivalent VXIbus mainframe. HP-UX, installed on a disk accessible to the Model V743 VXI controller. A direct connection to AC power for the mainframe. Avoid using extension power cables or power strips.
3 Custom cables (provided with the Model V743 VXI controller) with high-density connectors for LAN, monitor, and RS-232C. (See \Custom Cables" in Chapter 1 for a listing of custom cables.) Monitor connected to video output, or a terminal or terminal-emulator system connected to an RS-232C output. Keyboard connected to the Model V743 VXI controller. DDS-Format tape drive con gured to the SCSI bus of the Model V743 VXI controller (for backup of local disk, if installed).
3 Figure 3-2.
Turning On the System Before Booting the System 3 With all peripheral devices turned o , do the following: 1. Install the Model V743 VXI controller according to the instructions in the Installation Guide for the Model V743 VXI controller. 2. Connect a monitor to your system. See Figure 3-2 for some con guration alternatives. 3. Turn on the power to the monitor. The power indicator LED on the monitor will show that it is turned on, even if the screen remains dark.
Note If you want to change the con guration of the controller from graphics display to displaying on a console (via the serial port), you can do so by rst connecting the console to the RS-232C (Port A). (Note: The monitor and keyboard should not be connected during this procedure.) Then hold the Rst/Abt switch in the \Abt" (down) position while you cycle power (turn the power o and back on) on the VXIbus mainframe.
Configuring the Controller 3 A number of con gurations are possible, as diagrammed in Figure 3-2. One common con guration for the controller is as an HP-UX cluster node, or cnode. See the manual System Administration Tasks for procedures for other con gurations. Cluster Configuration After your hardware is in place, you can use SAM on the cluster server to do most of the con guration tasks.
6. On HP-UX 10, select Clusters NNNNNNNNNNNNNNNNNNNNNNNNNN 7. Select NFS Cluster Configuration --> NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 8. Choose Add Cluster Clients ... on HP-UX 9, or Define Clients on HP-UX 10. 9. Fill in the information in the selected elds on the SAM form. 10. Click on Add or Apply when the elds are lled in.
3 3. You should see a sequence of boot messages. As shipped, the Model V743 VXI controller will rst attempt to boot from an external SCSI device at SCSI address 6 if present, then at SCSI address 5 if present, then from any LAN-con gured system for which this system is a valid cluster client.
Configuring the RS-232 Ports The Model V743 VXI controller comes equipped with two RS-232C ports. The rst port, labeled \A", may be con gured using SAM (System Administration Manager). The second port, labeled \B", however, cannot be con gured using SAM; SAM will incorrectly con gure this port. To con gure this port you need super-user privilege. The command for con guring this port is: mknod /dev/rs232_b c 1 0x702004 You may choose a di erent name than \rs232 b" for the device le.
3. Otherwise, type your password when the system gives the following prompt: Password: 4. Press 4Enter5. The system prompt (\#" or \$") appears and you can use the system. 3 Logging Out If you are not using HP VUE, you can use the lock command to temporarily leave your system (while leaving processes running).
Creating a New User Account If you have access to a system administrator, that person may have already set up a user account for you. Otherwise, you will need to do the following to set up a user account so that you can interact with the system as non-root and not incur the risk of accidentally damaging data. You usually work in your home directory or \account", and most of your default les are kept there.
You can navigate around a SAM screen on a character terminal using the arrow keys and 4Tab5 to illuminate the selection you want to activate. When the selection is illuminated, press 4Enter5 to activate (or \choose") it. 1. Type the following: 3 On HP-UX 9: /usr/bin/sam 4ENTER5 On HP-UX 10: /usr/sbin/sam 4ENTER5 2. At the opening menu, choose Users and Groups-> by pressing 4Enter5 with Users and Groups-> illuminated.
NNNNNNNN 6. Choose OK when you are nished. 7. You will be asked to select a password. (See \Selecting a New Password" for password requirements. If you wish, you can select a temporary password and reset it later.) Type the password and choose OK (or press 4Enter5). Re-enter the password as requested and choose OK . The re-entered password must match the rst. 8. Choose OK . NNNNNNNN NNNNNNNN NNNNNNNN 9. When the \Task Completed" message appears, choose OK . NNNNNNNN 10. Select Exit then Exit SAM .
Setting or Changing a Password From a command line shell prompt, you can use the passwd command directly to set or change a password. (You do not have to be root.) Enter the following: 3 passwd 4Enter5 You will be prompted for your old password. Then you will be prompted to enter and re-enter your new password. The re-entered password must match the rst entry. See the \Selecting a New Password" section below if you need help with selecting passwords.
Powering Down the System Caution If you have a local disk connected to the Model V743 VXI controller, do not turn o power to the system without rst shutting down the controller's operating system software according to the following procedure. Turning o the power for your system without rst doing the shutdown procedure may result in damage to data on your disk. Always execute the shutdown process to completion rst. 1. Exit all processes currently running. 2.
Using the Command Line For guidance on entering HP-UX commands and using the HP-UX le system, tools, and networking commands, see the manual Using HP-UX . For more advanced work with shell programming, see the manual Shells: User's Guide .
4 Configuring for a VXI/MXI System Chapter Contents Overview. Examining Your VXI/MXI Con guration. Changing Your VXI/MXI Con guration. Con guring the VXI/MXI Trigger Lines. Examining the VXI/MXI Boot Process. Using HP SICL for VXIbus Backplane Communication.
Overview If your Model V743 VXI controller is to be a node in an HP-UX cluster, and it has not yet been installed and con gured according to the procedures in the Installation Guide for the Model V743 VXI controller, see \Con guring the Controller" in Chapter 3 before proceeding. 4 This chapter describes the VXIbus default values and how to change these values using the utilities provided with the HP Standard Instrument Control Library (SICL).
Examining Your VXI/MXI Configuration Default Values Your Model V743 VXI controller comes precon gured from the factory as follows: VXI Logical Address : 0. VXI Servant Area Size : 255. VXI Bus Error Timeout : 1ms. VXI Shared Memory : 0 (disabled). 4 The above values are programmed into the Model V743 VXI controller EEPROMs at the factory. There are times, however, when you want to change these values. See the next section \Changing Your VXI/MXI Con guration," for details on changing these values.
Changing Your VXI/MXI Configuration SICL includes some Model V743 VXI controller con guration utilities that are used to change the VXI Shared Memory in the VXIbus con guration. Changing the VXI Shared Memory 4 You can reserve 1 MByte of the Model V743 VXI controller system memory to be used as VXI shared memory in A24 address space. The Model V743 VXI controller is shipped with this feature disabled. When enabled, 1 MByte of the system memory becomes unavailable for use by HP-UX and your applications.
Configuring the VXI/MXI Trigger Lines 4 Figure 4-1. Front Panel Trigger I/O The table listed on the next page shows the relationship between SICL and the Model V743 VXI controller trigger lines and SMB connectors.
Trigger Lines 4 4-6 SICL V743 I TRIG TTL0 TTL0 I TRIG TTL1 TTL1 I TRIG TTL2 TTL2 I TRIG TTL3 TTL3 I TRIG TTL4 TTL4 I TRIG TTL5 TTL5 I TRIG TTL6 TTL6 I TRIG TTL7 TTL7 I TRIG ECL0 ECL0 I TRIG ECL1 ECL1 I TRIG ECL2 INVALID I TRIG ECL3 INVALID I TRIG EXT0 Trig in I TRIG EXT1 Trig out I TRIG EXT2 INVALID I TRIG EXT3 INVALID I TRIG CLK0 16 MHz Clock I TRIG CLK1 INVALID I TRIG CLK2 INVALID I TRIG CLK10 INVALID I TRIG CLK100 INVALID Configuring for a VXI/MXI System
Routing VXI TTL Trigger Lines in a VXI/MXI System Use the SICL ivxitrigroute function to route VXI trigger lines. For example, if you want to route TTL7 to Trig out, you can use the following SICL function call in your program: ivxitrigroute (id, I_TRIG_TTL7, I_TRIG_EXT1); See the HP SICL Reference Manual for more information on this and other SICL functions.
VXI-MXI TTL Trigger Routing: Name 0 1 2 3 4 5 6 7 ---- - - - - - - hpvximxi I I I I I I I I I - MXI->VXI O - VXI->MXI * - Not Routed Now the following illustrates TTL trigger line 1 being sourced by the device at logical address 24: 4 ttltrig.
Note You can use the /usr/pil/bin/e1489trg diagnostic test on HP-UX 9, or /opt/sicl/bin/e1489trg test on HP-UX 10, for the MXI/INTX trigger and interrupt circuitry. See Appendix F, \Con guring your VXI/MXI System," in the HP SICL User's Guide for HP-UX for information on this and other diagnostic tests for the E1489 MXIbus Controller Interface.
Examining the VXI/MXI Boot Process 4 When HP SICL is installed and con gured according to the procedures in the HP SICL User's Guide for HP-UX , certain SICL utilities are copied onto your system. These utilities automatically run when the system boots. The following is a summary of the VXIbus boot process utilities: iproc This utility runs at system boot and performs various system initialization functions. It uses the iproc.cf con guration le to determine when the other con guration utility runs.
Viewing the VXIbus System Configuration You can use the SICL ivxisc utility to read the current system con guration and print a human readable display: On HP-UX 9: ivxisc /usr/pil/etc/vxi16 On HP-UX 10: ivxisc /etc/opt/sicl/vxi16 See \The HP SICL Utilities" chapter of the HP SICL User's Guide for HP-UX for information on using this utility. Note The boot-up initialization line is commented out by default. You must un-comment the following line in the /usr/pil/etc/iproc.
VXI/MXI Configuration Files Con guration File Description vximanuf.cf Contains a database that cross references the VXI manufacturer id numbers and the name of the manufacturer. Edit this le if you add a new VXI vendor that is not currently in the le. vximodel.cf Contains a database that lists a cross reference of manufacturer id, model id, and VXI device names. Edit this le if you add a new VXI device to your system that is not currently in this database. 4 dynamic.
The iproc Utility (Initialization and SYSRESET) The iproc program is run from /etc/rc. This program becomes a daemon and monitors the VXI backplane for SYSRESET. The iproc.cf le tells iproc what to do if a SYSRESET occurs. Usually you want the resource manager to run and con gure your system (since the SYSRESET has destroyed the con guration). Note The SYSRESET line is commented out by default. You must un-comment the following line in the /usr/pil/etc/iproc.cf le on HP-UX 9, or the /etc/opt/sicl/iproc.
d The following is an example of the/usr/pil/etc/iproc.cf le: # # iproc configuration file # a # # Boot up functions # # Lines are of the form: # boot # boot echo "PIL: Instrument I/O Initialization" 4 # The next line must always exist. boot pilsetup # # V/382 or VXI/MXI Support # boot ivxirm -p -I vxi # When a SYSRESET occurs, rerun the resource manager (delay 5 sec). # The resource manager MUST be run in the background (i.e. last # character should be a '&').
Using HP SICL for VXIbus Backplane Communication Once your VXIbus system is con gured, you can start programming with SICL. SICL allows you to communicate directly over the VXIbus backplane to SCPI compatible message-based and register-based instruments.
d /* idn.c The following program uses SICL to query a VXI instrument for an identification string and prints the results. */ #include #include
5 Configuring Graphics Chapter Contents Monitor Selection. Displaying Graphics on a Remote X Host.
Overview Graphics operation will require a graphics display monitor connected to the Model V743 VXI controller selected from the following: Table 5-1. Supported Color Monitors Product Number 5 Resolution Size Refresh Frequency (Hz) HP D2806A 1024 x 768 15 in. 70 HP A4032A 1280 x 1024 17 in. (MultiSync) HP A4033A 1280 x 1024 20 in. 72 HP A4032B (Southern Hemisphere) 1280 x 1024 17 in. 60 HP A4033B (Southern Hemisphere) 1280 x 1024 19 in.
Identifying Graphics Cards NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Since only on-board graphics is supported on this computer, only GRAPHICS 1 will be indicated in the boot ROM console search display (see Appendix B). Displaying Graphics on a Remote X Host You can display graphics using a remote computer with X server capability connected to the Model V743 VXI controller via LAN. This is done by setting the DISPLAY environment variable on the controller.
6 Configuring HP-UX for Printers Chapter Contents Preparing for Installation. Testing the Printer Installation. Dealing With Printer Problems.
Preparing for Installation You may have to do some con guration for appropriate data interchange with a new printer. This chapter gives you general guidance for these tasks. You can use SAM (System Administration Manager) procedures to make your printer installation easier. SAM can determine the status of any of your connected devices and will perform the necessary software installation of the printer for you.
Configuring HP-UX for a Printer You will need to supply certain items of information needed to identify the printer you are installing. It will help you to write down this information now, so that you have it available to refer to during the software installation process: Printer Interface: Serial (RS-232C) (Port A): Serial (RS-232C) (Port B): Printer Name (a name the system uses to identify the printer. It can be any name.
To get help in SAM, press the 4f15 key. This key gives you context-sensitive information for the object at the location of the cursor in either graphical or character mode. Use the arrow keys and 4Tab5 to move the highlighted areas around the screen. Press 4Enter5 to \choose" an item when illuminated (such as OK ). NNNNNNNN 3. At the SAM opening screen, choose Printers and Plotters . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 4. Select Printers/Plotters on the next screen.
15. In the Add Local Printer/Plotter display which reappears, select and choose the box labeled Make this the system default printer . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 16. Choose OK . NNNNNNNN 17. If the print spooler was not previously running, a screen will appear with the question: Do you want to start the print spooler now? .
Dealing with Printer Problems If you experience problems in printing, check the following: The power cord for the printer is plugged in. The printer is turned on. The printer selection switches are set for online. Paper is loaded into the printer (and it isn't jammed). The correct interface has been set up. The printer cable is connected to the correct interface port on your printer. The cable is connected to the correct port on your system.
7 Configuring HP-UX for a DDS Tape Drive Chapter Contents Finding the Status of Existing SCSI Bus Addresses. Con guring for a Backup DDS Tape Drive. Con guring the Drive on HP-UX. Testing Your Installation. DDS Tape Drive LED Indicators. Maximum Usage of DDS Cassettes. In Case of Di culty.
Finding the Status of Existing SCSI Bus Addresses Before you attach a new SCSI drive, you can use the ioscan tool to help determine which device addresses are currently in use. To determine the connected SCSI bus IDs, enter ioscan -fb. The result will be a display of information, such as the following: Class H/W Path Driver H/W Status S/W Status Description ========================================================================= ... disk 2.0.1.2.0 scsi ok(0x5800101) ok tape_drive 2.0.1.3.
Configuring for a Backup DDS Tape Drive You will need to use a backup device if you have local disks connected to the Model V743 VXI controller. This section contains instructions for con guring an external DDS drive on HP-UX to use for backup. Tape Selection The DDS (\Digital Data Storage") tape drive is a sequential-access, read-write device using removable DDS cassettes. Although DDS drives are similar to DAT players in the audio industry, DDS and DAT cassettes are not interchangeable.
The general steps for adding a DDS tape drive to your system are as follows: 1. Make sure that the necessary device drivers are con gured into the kernel. On HP-UX, SAM will make this test. 2. Shut your system down and turn o the power. 3. Choose a SCSI bus address for the new tape drive that does not match the bus address for any other SCSI device. 4. Make all necessary hardware connections for the device. 5. Turn the new tape drive on . 6. Turn your system on and boot HP-UX. 7.
Before You Begin: Make a note of the tape drive product number and its hardware address (SCSI bus address) so that you will be able to identify it later. DDS Drive Product Number: Bus Address: 1. Log in as root. 2. Run SAM by typing the following: On HP-UX 9: $ /usr/bin/sam 4Enter5 On HP-UX 10: $ /usr/sbin/sam 4ENTER5 To get help in SAM, press the 4f15 key. This gives you context-sensitive information for the object at the location of the cursor. 3. Highlight and select Peripheral Devices -> .
choice has an asterisk placed by it, by pressing 4Enter5 while that line is highlighted.) Choose OK to con rm your choice of action. NNNNNNNN 9. You will next be given a choice of whether to install the new kernel now or later. If you move the kernel into place now, the system will also reboot. If you choose to do it later, you can then move the new kernel and reboot. You should also move: On HP-UX 9: /etc/conf/dfile.sam to /hp-ux /etc/conf/dfile.sam to /etc/conf/dfile On HP-UX 10: /stand/system.
Testing Your Installation Note that a write-protect tab on the cassette allows you to protect data from being overwritten. You will need to make sure that the tab is moved to the \writable" position in order for it to serve as a backup medium. A simple test to make certain that everything has been installed satisfactorily is to load a tape in the drive, wait for the \busy" light to stop blinking, and execute the ioscan command. The LED on the drive should icker brie y.
DDS Tape Drive LED Indicators Two LED indicators on the front panel of the drive indicate several operational and test states. The following table shows the LED combinations and explains what they indicate. Table 7-1.
7 Configuring HP-UX for a DDS Tape Drive 7-9
Caution Indicator The DDS drive continually monitors the number of errors it has to correct when reading or writing a tape. This information is presented to the user through the Caution Indicator (see chart above). A caution indication has two common meanings: The tape heads need cleaning. The tape itself is approaching the end of its useful life.
8 Backing Up and Restoring Software Chapter Contents Backing Up Your HP-UX System and Software. Restoring Individual Files. Restoring HP-UX Using the Recovery Tape.
Backing Up Your HP-UX System and Software The most important part of your system is the data you have accumulated. It is also especially important to protect your system from corruption. You can protect your data and system from loss, using the general procedures given in this chapter. (For detailed procedures, see the manual System Administration Tasks .) Make sure you create and maintain a backup HP-UX kernel (/SYSBCKUP on HP-UX 9, or /stand/system.
You should make a recovery tape by using the utility mkrs at the following times: Immediately after you set up the Model V743 VXI controller. Each time you update your operating system or make a change in your disk swap con guration. To do this, you will need a tape drive (cartridge or DDS) and one or more tapes. Using mkrs to Create a Recovery System on HP-UX 9 The mkrs utility on HP-UX 9 constructs a recovery system on removable media (or on a formatted hard disk drive).
Source Device Files By default, mkrs uses the following device les: /dev/update.src /dev/rct/c0 /dev/rct If none of the above defaults exist on the system, one of these device les must be created or the -f option must be used to specify the device le. The recovery device le can be either a block or a character device le.
Backing Up Your File Systems Preparation: The following procedure sets up a scheduled backup: 1. If your system is more than six months old, you have non-HP supported software, or you have never done a backup before, see System Administration Tasks before proceeding. Otherwise, SAM will provide interactive guidance. To use SAM, do the following: 2. Log in as root. 3. Type the following: On HP-UX 9: /usr/bin/sam 4ENTER5 On HP-UX 10: /usr/sbin/sam 4ENTER5 4. Choose Backup and Recovery .
2. Before initiating the backup, verify that your tape is not write-protected by checking that the write-protect device is in \writable" position. 3. Load a tape into the tape drive. Depending on what tape drive you are using, you may see activity lights ashing while the tape is loading. You can proceed when one light remains on, indicating that the drive is ready to accept data. 4.
Restoring Individual Files To restore speci ed les from a local device using SAM, rst you will need to have the following information and materials: A list of les you need. The media on which the data resides. The location on your system to restore the les (original location or relative to some other location). The device and device le for restoring the data.
3. Choose Backup and Recovery . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 4. Choose Backup Devices , Automated Backup , or Interactive Backup and Recovery . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 5. Highlight the device in the list from which the data is to be restored. 6.
8. To do any of the following during the restore process, activate Set Additional Parameters : NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Overwrite new les. Maintain original ownership. Recover les using full path name. OR Place les in a non-root directory. Turn on the appropriate checkbox(es). To restore les relative to a particular directory, ll in the directory. NNNNNNNN Choose OK to set the additional parameters. 9. Choose OK to start the restore process.
Restoring HP-UX Using the Recovery Tape If your operating system or the entire root disk becomes corrupted and not usable, you can restore your system using your recovery system tape and your archive backup tape(s). Also see \Booting and Resetting the VXIbus Mainframe" in Appendix B for information on using the boot ROM to nd and boot from a recovery tape. If your operating system is still usable but not functioning correctly, you can load the leset TOOL from an update tape to obtain diagnostic utilities.
You will see the message: NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Auto Boot discontinued 6. At the Main Menu, select Boot from a Device by typing 1 4Enter5. You will see a display like the following: NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN ==== BOOT FROM DEVICE ======================== Key Boot Device --- ----------------------------------------1 SCSI.6.0 HP C2233 2 LAN.080009-72333 15.99.255.25 3 LAN.080009-72345 INSTALL 15.88.123.456 4 SCSI.4.
b. The /hp-ux kernel le on HP-UX 9, or /stand/vmunix le on HP-UX 10, can be restored if it has been corrupted or removed, by doing the following: i. Mounting your system disk to an empty directory (make one if necessary) in your memory-based recovery system. ii. Using the cp command to copy the /hp-ux le on HP-UX 9 or the /stand/vmunix le on HP-UX 10 from your memory-based system (it is a copy of your real /hp-ux le) to the directory you used as a mount point for your system disk.
9 Dealing With Problems Chapter Contents Interpreting LED Indicators. Managing a Boot Failure. Selecting an Alternate Operating System. Recovering from a System Panic. Dealing with Network Failures.
Interpreting the LED Indicators There are four LEDs, which you can view on the panel of the Model V743 VXI controller, next to the clock and trigger I/O. LED Behavior Blinks occur in blinks/second groups. Each blink pattern is repeated at one-second intervals: Figure 9-1.
Table 9-1. Front Panel LED Indications LED Boot/Run (Green) Behavior continuously Meaning Power failure Remedy O Check DC power supply on VXI mainframe. Check AC power. On continuously Normal status No action needed. One blink/second CPU failure Replace system board. Four No console Check console path and blinks/second identi ed keyboard connections. If these are OK, replace system board. Sys Fail (Red) On when powered Normal operation No action needed. up and goes o after 5 seconds.
Managing a Boot Failure The boot program is located in the rmware of the Model V743 VXI controller. You can con gure the behavior of the boot process by interacting with the boot console handler. See Appendix B for procedures dealing with the boot console handler. If you have indications that the boot process has failed, check the following items. Boot Program Initializes Hardware Problems during the rst stage of the boot process are rare.
Selecting an Alternate Operating System If your hardware is functioning correctly, but your usual boot device (such as the root disk) is not responding as it should, you can select an alternate available boot device manually by following these steps: 1. Turn o the power to the VXIbus mainframe, and then turn it back on. 2. Press 4ESC5 at the prompt for stopping the boot selection process: System Search started Press [Esc] to discontinue the Auto Boot process 3.
You will see a list of bootable devices and LAN addresses, such as the following: ==== BOOT FROM DEVICE ======================== Key Boot Device --- ----------------------------------------1 SCSI.6.0 HP C2233 2 LAN.080009-72333 15.99.255.25 3 LAN.080009-72345 INSTALL 15.88.123.456 4 SCSI.4.
Recovering from a System Panic A system panic simply means that the operating system encountered a condition that it did not know how to respond to, so it halted your system. System panics are rare and not always the result of a catastrophe. They sometimes occur at boot if your system previously was not shut down properly. Sometimes they occur as the result of a hardware failure.
Should your system panic, it is important to record and categorize the circumstances associated with the panic. The following table will help you do so: Table 9-2. Summary of Possible Causes of Panics Problem Area Hardware Action If the failure appears to be associated with a peripheral device: Check the integrity of the cable connections. Ensure that the peripheral is online. If the above did not correct the problem, the failure may be associated with the System Processing Unit.
Procedures for Recovering from a System Panic Step 1: The Panic Message In a log book, record and categorize the panic message displayed on the system console. The panic message will tell you why the operating system panicked. Sometimes panic messages refer to internal structures of HP-UX (or its le systems) and the cause might not be obvious.
Proceed to Step 3, (Rebooting Your System). Step 2b: Recovering from a File System Problem If the panic message indicates a problem with one of your le systems, you will need to run the le system checker fsck to check and correct the problem(s). This is normally done automatically at boot time (from the /etc/rc le) so you should proceed to Step 3, \Rebooting Your System". Follow all directions that fsck gives you especially if the root le system ( \/" directory) has the problem .
switch on the panel. Otherwise, you can turn the system o and then back on to initiate the boot sequence. You will probably notice a few di erences in boot behavior as compared with your normal boot sequence. Your system might save a \core" le to disk. This core le is a \snapshot" of the previously running kernel at the time that it panicked. If necessary, this core le can be analyzed using special tools to determine more about what caused the panic.
Step 4: Monitoring the System If your system successfully boots, there is a good chance that you can resume normal operations. Many system panics are isolated events and are unlikely to reoccur. Check your applications to ensure that they are running properly and monitor the system closely. For a day or so, you might want to do backups more frequently until you are con dent that the system is functioning properly.
Dealing with Network Failures If the program you have been running uses resources from a local area network (LAN) and it stops unexpectedly, the following may help locate the source of the problem: Table 9-3. Problems with the Network Problem No systems respond to the /etc/ping hostname command. Action Check the network connection on the panel of your Model V743 VXI controller. Make sure that the cable is securely fastened to the connector.
A A Installing Additional Memory Appendix Contents RAM Upgrade Products. Planning for Installation of RAM. Installing the RAM Boards.
A RAM Upgrade Products The RAM upgrades for the Model V743 VXI controller are as follows (two cards per upgrade product): HP A2578A: 16 MB total. HP A2829A: 32 MB total. HP A2827A: 64 MB total. This Appendix is a general guide to RAM installation. For detailed information, also read the Installation Guide that comes with your upgrade before proceeding with any installation procedure.
A Planning for Installation of RAM Determining Existing Memory Follow these steps to determine how much memory your Model V743 VXI controller already has: 1. Turn the VXIbus mainframe on . If the mainframe is already on , cycle power (turn it o and back on .) 2. Stop the boot selection process by pressing 4ESC5 at the prompt. You will see the the boot console Main Menu. 3. Select HARDWARE INFORMATION . NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN 4.
A Installing the RAM Boards Caution A static charge of almost 40,000 volts can be generated on a carpeted oor. This exceeds the limits of these RAM cards and can cause unsuccessful operation or damage. Integrated circuits on printed circuit boards can be damaged by electrostatic discharge. Use the following precautions before working with the Model V743 VXI controller board or the RAM modules: Use the grounding wrist strap supplied with this upgrade. Follow the instructions printed on the strap's package.
A 3. Turn o the power for the VXIbus mainframe. 4. While facing the front panel of the board computer, use a at-tipped screwdriver to remove the two screws at the corners of the panel. Figure A-1. Extracting the Controller 5. Spread the two handles on the front panel. This will have the action of extracting the board computer out of its rear connector. 6. Pull the board out of the mainframe and place it labeled-side up on a rm, static-free surface. 7.
A Figure A-2. Removing RFI Cover 8. Using the Pozidriv screwdriver, remove the screw holding the RFI cover (with speci cations printed on it) from the top side of the board. 9. Place the tip of a at-tipped screwdriver through the slot in the RFI cover next to to the screw hole. Then pry the top cover back about 8mm (0.32 in.) to disengage the RFI cover front tabs from the system board and bottom cover.
A Note the L-shaped side tabs on the top cover that t through the system board and into the bottom cover on each side. Moving the RFI cover back also disengages these tabs. 10. Raise the back end of the RFI cover and remove the cover. 11. Remove a RAM card from the static-free packing material. Cards are installed in pairs, using either the front pair or the rear pair of RAM connectors on the board computer. Note that the RAM card is notched on one end to t the keyed connector. Figure A-3.
A 13. Snap the RAM card in place by moving it from vertical position to the angle of the old cards (or approximately 25 ). The ends of the card will snap into the spring clips at 25 . 14. Install the other member of the RAM pair the same way, in the adjacent slot toward the front panel. 15. Repeat the steps if you are installing another pair of RAM cards. 16. To test your installation, reinstall the Model V743 VXI controller in the VXI mainframe.
A 19. If the correct total memory is not listed, turn o the VXIbus mainframe and remove the board computer. a. Verify that the RAM cards are installed in adjacent pairs (front pair or rear pair). b. Verify that no RAM card connectors are dirty. 20. Turn o power and remove the board computer. 21. Reinstall the RFI cover. 22. Replace and tighten the RFI cover screw. 23. Reinstall the Model V743 VXI controller in the mainframe. 24. Replace the screws in the board computer front panel.
B Using the Boot Console Handler Appendix Contents The Boot Console Handler. Special Tasks. Boot Console Information Display. Using the Boot Console Handler Interface. Con guring the Console Path and Display Format. Booting and Resetting the VXIbus Mainframe. Searching for Bootable Media. Displaying and Setting Paths. Displaying and Setting the Fastboot Mode. Displaying and Setting the Secure Boot Mode. Displaying the LAN Station Address. Interactive Testing. Displaying Firmware Information.
B The Boot Console Handler There are times when you want to interact directly with the hardware of your VXIbus mainframe before it boots the operating system. The system provides an EEPROM con guration interface, called the boot console handler, which you can use before booting the operating system to display information, set paths, and set other system parameters even though the operating system isn't running.
Board serial number. SCSI device addresses and identi cations. Console path con guration. Note B As some of the rmware in the boot console handler is also used with the Model 743i , the I/O ASIC selections may list some device options such as HP Parallel not in the Model V743 VXI controller. Using the Boot Console Handler Interface To use the boot console handler menus, follow these steps: 1. Exit any applications you may have running. 2. Shut down your system. 3.
B Specifying a Boot Device To display devices that can boot HP-UX, type 1 4Enter5. A list of potential boot devices will be displayed. For example: ==== BOOT FROM DEVICE ======================== Key Boot Device --- ----------------------------------------1 SCSI.6.0 HP C2233 2 LAN.080009-72333 15.99.255.25 3 LAN.080009-72345 INSTALL 15.88.123.456 4 SCSI.4.
Setting the Console Path If you are using a graphics display or if you are changing from graphics to a RS-232C display mode, you will need to set the Console Path. 1. Press 4ESC5 at the prompt \System Search started . . . " 2. From the MAIN MENU , access the Path Con guration screen by typing 2 4Enter5. Type 3 4Enter5 at the Path Con guration menu to select the Console Path menu.
B 3. Turn on the VXIbus mainframe power. 4. Release the Rst/Abt switch. 5. You will begin seeing a set of messages on your screen, some of which will display clearly and some of which will not. The messages repeat the same content and each will remain on your display for about seven seconds.
You have selected this device as the CONSOLE CAUTION Before selecting 77 or 99: Set the CONSOLE PATH to this device, then Deselect INTERACTIVE CONSOLE SEARCH B This graphic device MONITOR TYPE is KEY 3 6. After the monitor or console type is con rmed, your console display shows the MAIN MENU . Type 2 4Enter5. The PATH CONFIGURATION menu appears.
B 8. For example, this menu indicates that your current console path is GRAPHICS 1 . To display a listing of supported monitors, type the number of this path. For this example, type 1. 9. For GRAPHICS 1 , a screen similar to the following example appears, indicating the supported monitor types, with an asterisk (*) beside your current selection. In this example, the current monitor format is indicated as Key 3 and is shown by the message at the top.
Booting and Resetting the VXIbus Mainframe B In case you do not want the usual automatic boot sequence to occur, you can start your system from an operating system that is stored on a device that is di erent from your usual boot device. If your normal operating system kernel or the disk on which it resides becomes damaged or unusable, you may wish to boot from a di erent disk or perhaps another type of device, such as a DDS-format tape drive. To boot from an alternate device: 1.
B Searching for Bootable Media Unless con gured otherwise in the boot console handler, the boot console process will automatically search exhaustively for bootable media. In automatic mode, the boot process searches all types of I/O devices in the default order for that operating mode (Test, OEM, or User), or in another order, if you have so speci ed in the BOOT FROM DEVICE menu. When it nds an ISL le, the ISL process initiates boot processes on its device.
Displaying and Setting Paths B A path is the hardware address of a device that is attached to the I/O system of your system. To display the current settings for the system paths, select Path Configuration from the boot console MAIN MENU by typing 2 4Enter5.
B Setting the Primary Path NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN To recon gure the primary boot device path, at the PATH CONFIGURATION menu, type 1 4Enter5. You will see the PRIMARY PATH menu. NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN ==== PRIMARY PATH ============================ PRIMARY PATH is now [ SCSI.6.0 ] Key Device Path --- ----------------------------------------1 SCSI.6.0 HP C2233 2 LAN.080009-72333 15.99.255.25 3 SCSI.4.0 CD-ROM HP C2943A ... ...............................
Selecting the Alternate Path Select the Alternate Path in a similar way by going to the PATH CONFIGURATION menu and typing 2 4Enter5 to see the ALTERNATE PATH menu. NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Resetting the Boot Device List Resetting the search list for primary or alternate boot devices is a similar process to setting paths in general.
B To reset the primary boot device, for example, type 1 4Enter5 to get the PRIMARY PATH menu: NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN ==== PRIMARY PATH ============================ PRIMARY PATH is now [ SCSI.6.0 ] Key Device Path --- ----------------------------------------1 SCSI.6.0 HP C2233 2 LAN.080009-72333 15.99.255.25 3 SCSI.4.0 CD-ROM HP C2943A ... .........................................
Displaying and Setting the Secure Boot Mode B There may be circumstances in which you would not wish to allow anyone to attempt to boot your system from a device other than the device you have speci ed, or to control the system from any console other than the one you have designated. This can be an important consideration in secure installations.
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN B Type 5 4Enter5 to get the CONTROL FLAGS menu, which will look something like the following: ==== CONTROL FLAGS ========================= Mode is now [ USER ] Key Enable Control Feature --- ----------------------------------------1 NO Fast Boot 2 NO Secure Mode 3 YES Auto Boot Select 4 NO Diagnostics to RS-232 (A) 5 NO Error Logging 6 NO Interactive ISL 7 NO Repeat Scan for Boot Devices 8 NO Interactive Console Search ... .........................................
Caution Once the secure boot mode is activated, the only way to deactivate it is to use the Rst/Abt switch, as in the previous section \Setting the Console Display Format" in this Appendix. This procedure is outlined below: 1. Make sure the VXIbus mainframe power is o and the console is connected and turned on . 2. Hold the Rst/Abt switch on the panel in its \Abt" (down) position. 3. Turn on the VXIbus mainframe power. 4. Release the Rst/Abt switch. 5.
B Displaying the LAN Station Address The LAN station address (\LANIC ID") of your system is the label that uniquely identi es the LAN connection for it at the link level (the hardware level). It is sometimes necessary for you to supply this address to other users. For example, if your system is to become a member of a cluster, the cluster administrator needs to know your LAN station address in order to add your system to the cluster.
==== Hardware Component Info ================= I/O ASIC Rev B 2.0 SCSI LAN 080009-010203 RS-232 (A) HP PARALLEL AUDIO PS/2 (0) PS/2 (1) Key Operation ... ......................................... 0 Previous Menu 77 Reset the System ---------------------------------------------Press Key, then press [Enter/Return] Note the third item in the list, which is the LAN address. (The item \HP PARALLEL" does not apply to the Model V743 VXI controller.
B The tests are as follows: CPU S.S. : tests the CPU super scalar operations. NNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN GRAPHICS 1 : initializes and tests the speci ed graphics interface. (Only GRAPHICS 1 is supported on the Model V743 VXI controller.) If the speci ed graphics interface is the console, the test will not be run but it will report \passed". HIL INIT does not apply to the Model V743 VXI controller.
Displaying Firmware Information. B This menu will give you information on the rmware module revision number. To get to this menu, at the MAIN MENU , type 5 4Enter5 ( FIRMWARE INFORMATION ). You will see a menu similar to the following: NNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN ==== FIRMWARE INFORMATION ==================== PDC Version 310.0 Release 0 Extension ROMs Name Revision Name Revision ----------- -------- ----------- -------CPU 1.00 MIOC 1.
Glossary Glossary absolute path name The name of a le which lists all the directories leading to it, starting with root (\/") and ending with the le base name itself. If the path name indicates a directory , leave the trailing slash. For example, /users/jth/. See Using HP-UX for more information on path names and directory structures in HP-UX.
Glossary boot device A device such as a disk drive, DDS tape drive, or network device that contains the appropriate program for booting the operating system. boot ROM An EEPROM memory which is incorporated into a system for the purpose starting the operating system, testing the terminal, and producing a standard display. Though loosely referred to as ROM, it includes a writable function to allow recon guration of path and boot con guration information.
Glossary cluster client A cluster node that does not have a local HP-UX le system. Its le system resides on the cluster server. A client can also refer to any process run by a server. cluster node Any workstation networked into an HP-UX cluster. (Also called \cnode".) cluster server The cluster node which acts as a le system server and operating system server for all the cluster nodes in an HP-UX cluster. Also called cluster root server. cnode Abbreviation for cluster node. CPU Central Processing Unit.
Glossary directory A table of identi ers and references (such as le names) that refer to corresponding les and items of data. Used in a typical HP-UX organizational structure to provide an organizational and logical identity for a given group of les and directories. environment The set of de ned shell variables (some of which are PATH, TERM, SHELL, HOME) that de ne the conditions under which your commands run.
Glossary HP-HIL Hewlett-Packard Human Interface Link. HP-IB Hewlett-Packard Interface Bus (IEEE 488 standard). HP-UX cluster A group of workstations connected via a LAN. One computer, the cluster server, performs as a le-system server for the cluster client. IPL Initial Program Loader (such as the ISL program). ISL Initial System Loader. This implements the operating system-independent portion of the boot process.
Glossary login Your login name, the name by which you are known to the workstation. This may be any group of characters, so long as it meets system rules. mainframe A VXIbus cardcage which allows instruments on a card to be plugged in and operate in a VXI environment. The HP E1401 is an example of an HP mainframe. mount To add an auxiliary (removable) le system to an active existing le system.
Glossary owner The owner of a le is usually the creator of that le. However, the ownership of a le can be changed by the superuser or the current owner with the chown (1) command or the chown (2) system call. password An encrypted sequence of characters used by HP-UX to identify an authorized user and to permit authorized login on a system. path name A sequence of directory names, separated by slashes, which specify the location of any le or directory. PDC Process Dependent Code.
Glossary relative path name The name of a le, listing all the directories leading to that le in relation to the current working directory. resource manager This runs at power on and identi es all plug-in modules installed in the mainframe. The resource manager also controls commander/servant hierarchies, allocates interrupt lines, performs address mapping, and starts the system operation. RFI Radio Frequency Interference. ROM Read-only memory.
Glossary SAM System Administration Manager. A subsystem of HP-UX that does a wide range of system administration tasks interactively. SCPI Standard Commands for Programmable Instruments. script A le that contains commands that a shell can interpret and run. SCSI Small Computer System Interface. servant area The area of a commander which de nes a range of logical addresses in which all instruments within the address range speci ed report to the commander. This cannot be changed.
Glossary SICL Standard Instrument Control Library. single-user state The state of a computer where there is little or no process activity and no users logged in. The system is only accessible to the current system administrator (root). This mode is brought about by execution of shutdown (1). Also called single-user mode. SPU System Processing Unit. The instruction- and graphics-processing module of the computer (in this case, the Model V743 VXI controller) containing the CPU and I/O processors.
Glossary user Any person who interacts directly with a computer system. user interface The medium through which users communicate with their workstations. The command-line prompt is one type of interface. The graphical objects of HP VUE are another type of interface. VME Versa Module Eurocard. A backplane connector protocol, used for networking customized arrays of processor boards in the same chassis. VMEbus The bus/protocol for VME cards. VME cards are networked together into a VMEbus chassis.
Index Index Special characters reboot\ {-}n, 9-8 #, 3-11{13 $, 3-11, 3-12 A Abt function, 3-7, B-5, B-17 account user, 3-13 alternate boot devices paths, B-11 anti-static grounding, A-4 archiving, 8-2 B backing up, 8-2{6 importance of, 9-7 backup DDS tape drive, 7-3 backups restoring data, 8-7 boot devices, B-13 path, B-13 bootable device, B-10 boot console bootable media search, B-10 booting, B-9 LAN addresses, B-18 resetting the system(hardware), B-9 setting secure boot, B-15 tasks, B-2 using, B-2{2
Index frecover, 8-7{9 fsck, 8-10{11, 9-8, 9-10, 9-11 ioscan, 7-7 lock, 3-12 man, 2-4 mkrs, 8-3{4 passwd, 3-16 reboot, 9-10, 9-11 reboot, -n option, 9-10, 9-11 shutdown, 3-17 con guration cluster, 3-8 examples, 3-5 VXI/MXI system, 4-10 con guration les, 4-11{12 con guration mode, B-2{21 con guring boot console, B-2{21 DDS drive, 7-3{7 IP address, 3-2 network id, 3-2 RS-232 ports, 3-11 system name, 3-2 time zone, 3-2 con guring printer, 6-3 connecting cables, 9-9 console path setting, B-4{5 C++ porting usin
Index H halting your system, 3-17 handler boot console, B-2{21 hard reset, 3-7 hardware failure at boot, 9-4, 9-9 failure of peripheral, 9-9 hardware paths setting, B-11 ? help icon, 2-4 help information, 2-4 home directory, 3-13 HP-UX command line, 3-11{12, 3-17 general features, 1-6 lock, 3-12 logging in, 3-11 logging out, 3-12 HP-UX recovery, 8-10 HP VUE, 3-2 NNNNN I iclear, 4-9 indicators LED, 7-8, 9-2{3 information help, 2-4 online, 2-4 product, 1-2{6 software, 2-2{5 system, 2-2{5 installation pre
Index upgrades, 1-3, A-2 mkrs, 8-3{4 device les, 8-4 errors, 8-4 Model V743 VXI controller general information, 1-2{6 operating system, 1-6 programming languages, 1-6 Model V743 VXI controller trigger lines, 4-5{9 monitors supported, 5-2 N network features, 1-6 network id, 3-2 network problems, 9-13 newcon g nding, 2-4 NFS le system recovery using SAM, 8-7 O on-board graphics, 1-5 operating system HP-UX, 1-6 P panic system, 9-7 panic message, 9-9 passwd, 3-16 password changing, 3-16 criteria, 3-16 ent
Index using, 8-10, 9-10, B-5, B-9, B-17 LAN, 9-10 recovering from, 9-7 Rst function, 3-7, B-9 S T SAM backing up with, 8-2, 8-5 creating user account, 3-13 entering and exiting, 3-13{15 setting password, 3-15 SCSI bus address nding existing, 7-2 SCSI bus IDs determining active, 7-2 secure boot mode, B-15 set_parms, 3-10 setting display, B-5 shared memory enabling/disabling, 4-4 shutdown, 3-17 shutting down, 3-17 SMB connectors, 4-5{6 starting a system, 3-2 starting the Model V743 VXI controller, 3-11 s
