Agilent E1498A Users Guide

Download

Models V743/64 and V743/100

Owner's Guide

HP 9000 Series 700

VXIbus Controllers

ABCDE

HP Part No. E1497-90016

Printed in USA November 1995

Edition 3

E1195

Legal Notices

The information contained in this document is sub ject 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.

Agreement and Limited Warranty

Please read the enclosed

Hewlett-Packard SoftwareProduct License

before operating this product. Righ

ts in the

software are oered only on the condition that the customer accepts all terms

and conditions of the License Agreement.

Operating the product indicates your acceptance of these terms and conditions.

If you do not agree to the License Agreemen

t, you may return the unused

product for a full refund.

A copy of the specic warranty terms applicable to your Hewlett-Packard

product and replacement parts can be obtained from your local Sales and

Service Oce.

Copyrightc

Hewlett-Packard Company 1994, 1995.

This document contains information which is protected by copyright. All rights

are reserved. Reproduction, adaptation, or translation without prior written

permission is prohibited, except as allowed under the copyrightlaws.

Copyrightc

1986, 1987, 1988 Sun Microsystems, Inc. Copyright

1984, 1986 UNIX System Laboratories, Inc. Cop

Massachusetts Institute of Technology. Copyright

Corp. Copyrightc

1983, 1985-1990. Copyrightc

Inc. Copyrightc

The Regents of the University of California 1979, 1980,

1987, 1988, 1989 Lynx Real-Time Systems,

1980, 1984, 1986 AT&T Technologies, Inc. Copyright

yright



1985-1986, 1988



1986 Digital Equipment



1980,



1984-1991 Wind River Systems, Inc.

X Window System is a trademark of the Massachusetts Institute of Technology.

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.

Government Department of Defense is subject to restrictions as set forth in

paragraph (b)(3)(ii) of the Rights in Technical Data and Software clause in

FAR 52.227-7013.

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 maybe

made at reprint without changing the printing date. The manual part number

will change when extensivechanges o ccur.

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 pro duct support service. See your

Hewlett-Packard Sales Representative for details.

Edition 1 - October 1994

Edition 2 - August 1995

Edition 3 - November 1995

Hewlett-Packard Company

MXD Learning Pro ducts

815 14th Street S.W.

Loveland, Colorado 80537

Safety Symbols and Conventions

The following conventions are used throughout this manual:

Note

Caution

Warning

Warnings

There is a danger of explosion if the cloc

Replace the battery only with the same or equivalenttyp e recommended by

the manufacturer. Discard used batteries according to the manufacturer's

instructions.

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 b eyond 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. Do not proceed

beyondaWARNING sign until the indicated conditions are fully

understood and met.

k battery is incorrectly replaced.

(France): Il y a danger d'explosion s'il y a remplacement incorrect de la

batterie. Remplacer uniquementavec une batterie du m^eme type ou d'un

type recommande par de constructeur. Mettre au rebut les batteries usagees

conformement aux instructions du fabricant.

Regulatory Information

FCC Statement(For U.S.A. Only)

The Federal Communications Commission (in Subpart J of Part 15, Docket

20780) has sp ecied that the following notice be brought to the attention of the

users of this product:

This equipment has b een tested and found to comply with the limits for a

Class A digital device, pursuanttoPart 15 of the FCC Rules. These limits

are designed to provide reasonable protection against harmful interference

when the equipment is operated in a commercial environment. This

equipment generates, uses, and can radiate radio frequency energy

not installed and used in accordance with the instruction man

harmful interference to radio communications. Operation of this equipment

in a residential area is likely to cause harmful in

user will b e required to correct the in

70 dB Declaration (Germany Only)

Laermangabe nach der Maschinenlaermverordnung | 3GSGV

terference at his own expense.

terference, in which case the

, and, if

ual, may cause

(Deutschland)

(Noise Declaration | German Law)

LpA<70 dB

am Arbeitsplatz (operator's position)

normaler Betreib (normal operation)

nach DIN 45635 T. 19 (per ISO 7779)

VCCI Statement (Japan Only)

vii

xxxxxxxxxxxxReplace this page with the Ventura Decl of Conformity

xxxxxxxx

viii

Printing Conventions

This bo ok uses the following typographical conventions:

If you see

...

computer text

italic text

Key

NNNNNNNNNNNNNNNNNNNNNNNNNN

Displayed

NNNNNNNNNNNNN

Item

It means

...

Represents text you will see on the screen or text you must

type/enter yourself. For example,

indicates a login prompt displayed by the system.

Variable text supplied byyou. For example,

le name

means that you type a le name of your choice.

Italic text is also used for text emphasis and for documen

t titles.

Type the corresponding key on the keyboard. For example,

5-4D5

CTRL

means you hold down the

CTRL

key, and press the

key.

Select an on-screen item or a corresponding softkey.For example,

NNNNNNNNNNNNNN

Help

Contents

1. Product Description

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 1-1

The HP 9000 Model V743 Embedded VXI Controller . . . . . 1-2

Features . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Memory Congurations . . . . . . . . . . . . . . . . . 1-3

Interfaces . . . . . . . . . . . . . . . . . . . . . . . 1-4

Graphics . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Operating System . . . . . . . . . . . . . . . . . . . . 1-6

2. Finding Information About Your System

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 2-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Manuals for System Information . . . . . . . . . . . . . 2-2

Online Sources of Information . . . . . . . . . . . . . . . 2-4

3. Getting Started with HP-UX

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 3-1

Before Logging In the First Time . . . . . . . . . . . . . . 3-2

System Requirements . . . . . . . . . . . . . . . . . . 3-3

Turning On the System . . . . . . . . . . . . . . . . . . 3-6

Conguring the Controller . . . . . . . . . . . . . . . . . 3-8

Conguring the RS-232 Ports . . . . . . . . . . . . . . . . 3-10

Logging In and Out . . . . . . . . . . . . . . . . . . . . 3-11

Logging In . . . . . . . . . . . . . . . . . . . . . . . 3-11

Logging Out . . . . . . . . . . . . . . . . . . . . . . 3-11

Creating a New User Account . . . . . . . . . . . . . . . 3-12

Setting or Changing a Password . . . . . . . . . . . . . . 3-14

Selecting a New Password . . . . . . . . . . . . . . . . 3-14

Powering Down the System . . . . . . . . . . . . . . . . 3-15

Using the Command Line . . . . . . . . . . . . . . . . . 3-16

Contents-1

4. Conguring for a VXI/MXI System

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 4-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Description of HP SICL . . . . . . . . . . . . . . . . . 4-2

Examining Your VXI/MXI Conguration . . . . . . . . . . 4-3

Default Values . . . . . . . . . . . . . . . . . . . . . 4-3

Changing Your VXI/MXI Conguration . . . . . . . . . . . 4-4

Changing the VXI Shared Memory . . . . . . . . . . . . 4-4

Conguring the VXI/MXI Trigger Lines . . . . . . . . . . . 4-5

Routing VXI TTL Trigger Lines in a VXI/MXI System . . . 4-7

Routing VXI TTL Trigger Lines in a Multiple Mainframe

System . . . . . . . . . . . . . . . . . . . . . . . 4-7

Inverting the Polarity of the V743 External Trigger Lines . . 4-9

Examining the VXI/MXI Bo ot Pro cess . . . . . . . . . . . 4-10

Viewing the VXIbus System Conguration . . . . . . . . . 4-11

VXI/MXI Conguration les . . . . . . . . . . . . . . . 4-11

The

iproc

Utility (Initialization and SYSRESET) . . . . . 4-13

Using HP SICL for VXIbus Backplane Communication . . . . 4-15

For More Information . . . . . . . . . . . . . . . . . . 4-16

5. Conguring Graphics

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 5-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Identifying Graphics Cards . . . . . . . . . . . . . . . . 5-3

Displaying Graphics on a Remote X Host . . . . . . . . . 5-3

For More Information . . . . . . . . . . . . . . . . . . 5-3

6. Conguring HP-UX for Printers

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 6-1

Preparing for Installation . . . . . . . . . . . . . . . . . 6-2

Conguring HP-UX for a Printer . . . . . . . . . . . . . . 6-3

Testing the Printer Installation . . . . . . . . . . . . . . 6-5

Dealing With Printer Problems . . . . . . . . . . . . . . 6-6

Contents-2

7. Conguring HP-UX for a DDS Tape Drive

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 7-1

Finding the Status of Existing SCSI Bus Addresses . . . . . . 7-2

Conguring for a Backup DDS Tape Drive . . . . . . . . . . 7-3

Conguring the Drive on HP-UX . . . . . . . . . . . . . 7-4

Testing Your Installation . . . . . . . . . . . . . . . . . 7-6

DDS Tape Drive LED Indicators . . . . . . . . . . . . . 7-7

Maximum Usage of DDS Cassettes . . . . . . . . . . . . 7-8

In Case of Diculty . . . . . . . . . . . . . . . . . . . 7-8

8. Backing Up and Restoring Software

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 8-1

Backing Up Your HP-UX System and Software . . . . . . . . 8-2

Creating a Recovery System . . . . . . . . . . . . . . . 8-2

Backing Up Your File Systems . . . . . . . . . . . . . . 8-4

Restoring Individual Files . . . . . . . . . . . . . . . . . 8-7

Restoring HP-UX Using the Recovery Tape . . . . . . . . . 8-10

For More Information . . . . . . . . . . . . . . . . . . 8-12

9. Dealing With Problems

Chapter Contents . . . . . . . . . . . . . . . . . . . . . 9-1

Interpreting the LED Indicators . . . . . . . . . . . . . . 9-2

Managing a Bo ot Failure . . . . . . . . . . . . . . . . . . 9-4

Boot Program Initializes Hardware . . . . . . . . . . . . 9-4

Selecting an Alternate Operating System . . . . . . . . . . 9-5

Recovering from a System Panic . . . . . . . . . . . . . . 9-7

Procedures for Recovering from a System Panic . . . . . . . 9-9

Dealing with Network Failures . . . . . . . . . . . . . . . 9-13

A. Installing Additional Memory

Appendix Contents . . . . . . . . . . . . . . . . . . . . A-1

RAM Upgrade Pro ducts . . . . . . . . . . . . . . . . . . A-2

Planning for Installation of RAM . . . . . . . . . . . . . . A-3

Determining Existing Memory . . . . . . . . . . . . . . A-3

Installing the RAM Boards . . . . . . . . . . . . . . . . . A-4

Contents-3

B. Using the Boot Console Handler

Appendix Contents . . . . . . . . . . . . . . . . . . . . B-1

The Bo ot Console Handler . . . . . . . . . . . . . . . . . B-2

Special Tasks . . . . . . . . . . . . . . . . . . . . . . B-2

Boot Console Information Display . . . . . . . . . . . . . B-2

Using the Bo ot Console Handler Interface . . . . . . . . . B-3

Conguring the Console Path and Display Format . . . . . B-4

Booting and Resetting the VXIbus Mainframe . . . . . . . B-9

Searching for Bootable Media . . . . . . . . . . . . . . . B-10

Displaying and Setting Paths . . . . . . . . . . . . . . . B-11

Displaying and Setting the Secure Boot Mo de . . . . . . . B-15

Displaying the LAN Station Address . . . . . . . . . . . B-18

Interactive Testing. . . . . . . . . . . . . . . . . . . . B-19

Displaying Firmware Information. . . . . . . . . . . . . . B-21

Glossary

Index

Contents-4

Product Description

Chapter Contents

Features.

Memory Congurations.

Interfaces.

Graphics.

Operating System.

Product Description 1-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

Instal lation Guide

for detailed hardware

information.

Features

The Mo del V743 VXI controller has the following general features:

Single-slot VXI C-size conguration.

64-MHz PA-RISC pro cessor (Model V743/64).

100-MHz PA-RISC pro cessor (Model V743/100).

HP-UX 9.05 (minimum) Operating System.

Congurable with 16 MB to 128 MB main memory (see \Memory

Congurations").

For the Mo del V743/64: factory-installable RAM is 16 MB to 64 MB.

For the Mo del V743/100: factory-installable RAM is 32 MB to 128 MB.

Error-Checking and Correcting (ECC) SIMM RAM.

External Cache: 256 KB merged (64-MHz or 100-MHz CPU):

Congurable for 1 MB of shared memory.

Total external disk capacity: 14 GB.

Input/Output:

On-Board Graphics.

RS-232C (2 p orts).

HP-IB.

Trigger Input-Output.

Clock Input-Output.

AUI (LAN).

Audio interface: 16-bit voice quality; composite mono; audio connector

(one output jack for speaker or headphone).

SCSI-II single ended.

PS/2 Keyboard and Mouse; Mini-DIN Connector.

1-2 Product Description

Memory Configurations

Figure 1-1. Four RAM Cards Installed

The standard Mo del V743 VXI controller comes with either 16 MB or 32 MB

factory-installed RAM, with other options possible. It can be upgraded b

user with internal RAM cards as follows (two cards p er upgrade):

HP A2578A; 16 MB total.

HP A2829A; 32 MB total.

HP A2827A; 64 MB total.

Upgrades or factory-integrated RAM provide the Mo del V743 VXI controller

with up to 128 MB maximum memory. See Appendix A for installation

instructions.

Product Description 1-3

y the

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).

LAN AUI (high-density, 15-pin D-subminiature; requires a custom cable and

MAU for connection to LAN).

Two asynchronous RS-232C Interfaces: high-density, 9-pin male DTE (PC

standard). Requires a custom cable.

SCSI-IIInterface: high-density, 50-pin; single-ended 8-bit, up to 5 MB/sec.

synchronous.

Custom Cables

(Not currently supported)

The high-density I/O connectors for this board computer require adaptation to

standard cabling, using one or more of the following items (these are provided

with your controller):

HP A4301A RS-232C: High-density 9-pin to standard 9-pin \M". (2)

HP A4303A LAN: High-density 15-pin to 15-pin AUI.

HP A4304A Video: High-density 15-pin to standard 15-pin \F".

HP K2996 SCSI: High-density 50-pin to standard bail lock.

HP 11130A HPIB: High-density 15-pin to standard 24-pin, IEEE-488.

In addition, standard cables are also available and may be required.

1-4 Product Description

Physical Dimensions and Power Requirements

The Mo del V743 VXI controller o ccupies 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 DC Current Dynamic Current

+5V 10 A 100 mA

+12 V 250 mA 3mA

-12V 80 mA 2mA

+24 V 40 mA 1mA

-24V 0mA 0mA

- 5.2 V 560 mA 4mA

-2V 480 mA 2mA

+5V

0mA 0mA

STDBY

Note that +24V is required only for a at-panel display (not currently

supported).

System power requirements depend to some degree on the RAM conguration as

well as on the softwarebeing run. Each additional RAM card adds .2 amps to

the +5 Vdc. requirement at 64 or 100 MHz. See the hardwarespecications in

your service manual for further information.

Graphics

The Model V743 VXI controller comes with on-board graphics.

For information on currently supported monitors, see Chapter 5 in this

manual, or the current Release Notes le in

HP-UX 9. For Release Notes on HP-UX 10, see the

/etc/newconfig/905RelNotes

/usr/share/doc

directory.

Product Description 1-5

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

Pascal

ANSI FORTRAN

SICL for C Programming, Revision 3.9

User Interface: HP-UX 9.05 includes the X Window System and can b e

congured with HP VUE 3.0.

Network Features: IEEE 802.3/Ethernet Local Area Network

ARPA/Berkeley networking services

VXI Backplane Networking (Optional)

TCP/IP

HP Diskless

1-6 Product Description

Finding Information About Your System

Chapter Contents

Manuals for System Information:

HP-UX

HP VUE

Online Sources of Information.

Finding Information About Your System 2-1

Overview

The Model V743 VXI controller uses the standard HP-UX operating

system, a highly versatile system for multitasking, running your application

programs, and p erforming a variety of development tasks. For information

on installing HP-UX 9, see the manual

(and the 9.05 Release Notes for updates). For HP-UX 10, see

HP-UX 10

(and the Release Notes in the

Instal ling and Updating HP-UX 9.03

Instal ling

/usr/share/doc

directory for

updates).

To get started with using HP-UX, rst read your

Installation Guide

, then

go to Chapter 3 in this manual for information on b ooting and running the

system.

Manuals for System Information

If you have not installed your hardware or started your controller, refer to the

Instal lation Guide

for the Mo del V743 VXI controller b efore going on.

HP-UX

After you have done the pro cedures in the

Installation Guide

for the Mo del

V743 VXI controller, you maywant to see the following sources for further

information:

For HP-UX administration information, see

System Administration Tasks

For a quick reference to commonly used HP-UX commands, see the

Appendix in

Using HP-UX

HP VUE is the default interface for HP-UX. At some point, you maywantto

interact with the Mo del V743 VXI controller using HP VUE via the LAN,

with an X Window System display. As a simpler window alternative, you

can also use the X Window System by itself. Both are included in HP-UX.

For further information, see the manual

HP-UX

,or

HP VUE User's Guide

Using the X Window System,Using

The following manuals will also b e useful:

If you have not yet installed your HP-UX system, see

Updating HP-UX 9.03

(and the 9.05 Release Notes in

Instal ling and

etc/newconfig

2-2 Finding Information About Your System

for

updates) for HP-UX 9, or see

in the

For troublesho oting HP-UX, see Chapter 9 in this manual, and the manual

Solving HP-UX Problems

VXI

usr/share/doc

directory) for HP-UX 10.

Instal ling HP-UX 10

(and the Release Notes

For VXI conguration information, see the

Conguration Guide

User's Guide for HP-UX

HP VUE

For information on using and conguring the HP VUE in

see the

HP VUE Instal lation Guide

HP VUE User's Guide

.For VXI programming information, see the

.For information on installing HP VUE, see the

C-Size VXIbus Systems

HP SICL

terface with HP-UX,

Finding Information About Your System 2-3

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

is also available online. You can access this information by clicking on the up

arrow(8)over the

the command line

NNNNN

help icon on the HP VUE FrontPanel, or byentering

man

command

, where

command

is the name of the HP-UX

HP-UX Reference

command or routine you want to get information on. If you're not sure of

the command name, you can enter

man -k

keyword

, where

keyword

is a

likely topic word to search on. This will result in a display listing commands

having the keyword in their description.

There are also a variety of les on your HP-UX system which contain

version-specic information. These will b e useful in administering and

conguring cards and devices for your version of HP-UX. Among these les are

the following:

Release Notes: This is the online version of the Release Notes which came

with your system. It contains all the latest information, undocumented

changes and bug xes for your release of HP-UX. It also contains information

on the currentversion of HP VUE. The Release Notes documen

in the

directory for HP-UX 10. Look for the le named b

example,

/etc/newconfig

905RelNotes

directory for HP-UX 9, or the

, for HP-UX 9.05.

/usr/share/doc

y its release number, for

t is found

HP-UX and HP VUE Help: For graphics displays, extensive help information

on the op erating system and the visual interface is included with HP VUE.

Access it via the

NNNNN

button on the control panel.

2-4 Finding Information About Your System

Newcong: The directory

for HP-UX 10, contains information and new versions of HP-UX pro duct

conguration les, as well as shell scripts whichmayhave 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 lo cations in the le system, are not overwritten by

the update process. See the README le in

/usr/share/doc

directory.

/etc/newconfig

on HP-UX 10, for information on the contents of this

for HP-UX 9, or

/etc/newconfig

usr/share/doc

on HP-UX 9,

Finding Information About Your System 2-5

Getting Started with HP-UX

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.

Getting Started with HP-UX 3-1

Before Logging In the First Time

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

on setting up HP-UX clusters and cno des.

This chapter reviews some initial procedures and provides information on using

both HP VUE sessions and HP-UX. For more detailed information ab out using

HP VUE after login, see the

Managing Clusters of HP 9000 Computers

HP VUE User's Guide

for instructions

You should rst read the

and follow the initial hardware setup and booting pro cedures applicable to y

conguration. When you rst turn on the VXIbus mainframe to complete the

installation process, your display will ask for information on the time zone,

system host name, and network IP address. If you do not have this information

readily available, simply press

information later.

Instal lation Guide

after the questions and you can supply the

Enter

for the Mo del V743 VXI controller,

our

3-2 Getting Started with HP-UX

Figure 3-1. Model V743 VXI Controller in Mainframe

System Requirements

You should check to see that you have connected the following components

before pro ceeding further with b ooting your system:

Host System: HP Model E1401A or equivalent VXIbus mainframe.

HP-UX, installed on a disk accessible to the Mo del V743 VXI con

A direct connection to ACpower for the mainframe. Avoid using extension

power cables or power strips.

LAN connection to the Model V743 VXI controller via an appropriate MAU

interface and custom cable for the AUI.

Getting Started with HP-UX 3-3

troller.

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).

Disk congured to the SCSI bus on the Model V743 VXI controller

(optional).

Some of the more common VXIbus congurations with the Model V743 VXI

controller are shown in Figure 3-2.

3-4 Getting Started with HP-UX

Figure 3-2. Configurations for the Model V743 VXI Controller

Getting Started with HP-UX 3-5

Turning On the System

Before Booting the System

With all p eripheral devices turned o, do the following:

1. Install the Mo del V743 VXI controller according to the instructions in the

Instal lation Guide

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.

Make sure of the following:

The appropriate LAN and/or RS-232C connection has been made to the

Model V743 VXI controller.

If you use a remote graphical display host connected via LAN, make sure

the remote system is congured to host the con

\Displaying Graphics on a Remote X Host" in Chapter 5 for the specics

of setting this up.

4. Check SCSI connections.

5. Turn on the power to any peripheral devices, but do not turn on the po

to the VXIbus mainframe until you have read the following note.

for the Mo del V743 VXI controller.

troller. See Figure 3-2 and

wer

3-6 Getting Started with HP-UX

Note

If you wanttochange the conguration of the controller from

graphics display to displaying on a console (via the serial p ort),

you can do so by rst connecting the console to the RS-232C

(Port A). (Note: The monitor and keyboard should

connected during this pro cedure.) Then hold the Rst/Abt

switch in the \

(turn the p ower o and back on) on the VXIbus mainframe.

This action starts the boot console routine whichinteractively

selects the display and congures the computer to recognize a

monitor's format correctly. Prompts for this are given during

the screen display process. See \Conguring the Console Path

and DisplayFormat" in Appendix B for the details of this

procedure.

Using the Rst/Abt Switch

Abt

" (down) position while you cycle power

not

Figure 3-3. Rst/Abt Switch

The Rst/Abt switch on the front panel is a momentary-contact, two-position

switch which enables either a hard reset (in the \

termination (in the \

Abt

" position). The switch is used at boot, as indicated

Rst

" position) or process

earlier, to set the computer to display in the correct format for the console

monitor.

To rebo ot the computer, push the Rst/Abt switc

h to the \

Rst

" (up)

position.

To exit all currently running processes, push the Rst/Abt switch to the

Abt

" (down) position. This position is also used when cycling p ower to

reset the monitor conguration and console path.

Getting Started with HP-UX 3-7

Configuring the Controller

Anumber 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

congurations.

System Administration Tasks

for procedures for other

Cluster Configuration

After your hardware is in place, you can use SAM on the cluster server to do

most of the conguration tasks. The manual

Computers

gives you detailed guidance for congurations relating to clusters.

Managing Clusters of HP 9000

The following procedure gives you general guidance for setting up the controller

as a cno de:

1. Ensure that HP-UX has been installed on the serv

er and that it is

appropriately congured as a ro ot server (a cluster that has any Series

700 clients must have a Series 700 root server). Check that a client name

(ARPA host name) has b een assigned for the new Model V743 VXI

controller. See Chapter 4 in

Managing Clusters of HP 9000 Computers

more information on this.

2. Log onto the root server as

3. Print out a copyof

/tmp/cluster.log

root

which contains a list of the

context-dependent les (CSFs) which SAM creates on your system.

4. Get the LAN station address for the new Model V743 VXI con

the label on its packing box, or cycle power on its host system and get the

LAN station address from the boot console interface display

menu. You can also use

/etc/lanscan

to get this address from a running

troller from

NNNNNNNNNNNNNNNNNNNNNNNNNN

I/O ASIC

system if it already has access to an OS. Write down the LAN station

address.

5. On the cluster server, type the following:

On HP-UX 9:

/usr/bin/sam

ENTER

On HP-UX 10:

for

/usr/sbin/sam

ENTER

3-8 Getting Started with HP-UX

On HP-UX 10, select

Select

Choose

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

NFS Cluster Configuration -->

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add Cluster Clients ...

NNNNNNNNNNNNNNNNNNNNNNNNNN

Clusters

on HP-UX 9, or

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Define Clients

HP-UX 10.

9. Fill in the information in the selected elds on the SAM form.

10. Clickon

NNNNNNNNNNN

Add

NNNNNNNNNNNNNNNNN

Apply

when the elds are lled in.

11. Enter information for the next cno de to be added, if any.

NNNNNNNN

12. Clickon

to end the pro cess if you have no more cno des to add, and

wait for conrmation that the action has b een completed successfully

13. Check

/tmp/cluster.log

for errors.

14. Boot each new client.

15. Use SAM to add local DDS drives, for backup, if needed.

Install your SICL software onto the server disk for each cno de including

rebuilding the kernel after each SICL installation. Use the conguration steps

for SICL in Chapter 4 in this man

HP SICL User's Guide for HP-UX

ual. You will nd further information in the

Booting the System

1. If your Mo del V743 VXI controller is to be a diskless cluster node (cnode),

go to \Conguring the Controller" earlier in this chapter for instructions on

conguring the server.

2. If you have not already done so, turn on the p ower to the Model V743 VXI

controller bypowering up the VXIbus mainframe. The controller turns on

with the host system that it is plugged in

The topmost green LED (\

Boot

...

to.

Run

") on the panel will blink slowly

until HP-UX is booted, then it is continuously on. The other green LED

Act

") will blink when there is VXI backplane access activity. The two red

LEDs (second and fourth) will only light if there is a system problem in this

VXI system. Details of the indications are given in Table 9-1 .

Getting Started with HP-UX 3-9

3. You should see a sequence of b oot 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.

If there are multiple cluster servers that could recognize this client, or

if you are installing HP-UX from CD-ROM, you should interrupt the

automatic bo ot selection by pressing the

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Boot From a Device

to select the correct boot device. See Appendix B for

key, then select key 1

ESC

more information ab out conguring the automatic bo ot selection.

4. During the bo ot process, a new system will giveyou messages prompting

you for the host name, IP n

umber, and time zone. If y

information, enter it as requested. Otherwise, press

enter or update this information later b

ytyping

ou have this

Enter

set_parms

.You can also

after

Enter

a. The time zone where your system is located.

b. The host name for your system - any alphanumeric, single-word name

with eight or fewer characters.

c. The network address number, also called an IP number, for your system.

This consists of four address elds separated by p eriods: for example,

255.32.3.10

.You may need to consult with your system administrator

for this information. Or, if your host name and IP number have already

been assigned, you can nd out the host name after b oot b

uname -a

byentering

.Ifyou knowyour host name, you can nd out your IP number

nslookup

host name

at the system prompt.

yentering

5. You will also be asked if you want to set a root password at this time. If so,

see \Selecting a New Password" in this chapter for password requirements.

Finally,you will see the \

Console login:

" prompt.

3-10 Getting Started with HP-UX

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, lab eled \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 maychoose a dierent name than \rs232 b" for the device le.

If you plan to use this port with the HP-UX \

you will also need to mo dify the

/usr/lib/uucp/Devices

" command or similar utilities,

le to add an entry

for this device le name. A typical entry is:

Direct rs232_b - 9600 direct

Logging In and Out

Once HP-UX is running on your system, you must log in. The pro cess of

logging in is one of the ways that HP-UX prevents unauthorized persons from

using your system. This is especially important if y

our system is attached to a

network.

Logging In

If you are not using HP VUE, then a command line login prompt appears after

boot:

1. Type your login name (or

root

). (See \Setting or Changing a Password" for

setting a password).

2. Press

If you

Enter

haven't

yet set a password, you will get a a system prompt (\#" for

root, or$for user), and you can b egin using the system.

Getting Started with HP-UX 3-11

3. Otherwise, type your password when the system gives the following prompt:

Password:

4. Press

. The system prompt (\#"or \$") appears and you can use the

Enter

system.

Logging Out

If you are not using HP VUE, you can use the

leaveyour system (while leaving processes running). If you want to log out of

your currentwork session entirely, use the following command:

exit

lock

command to temporarily

3-12 Getting Started with HP-UX

Creating a New User Account

If you have access to a system administrator, that p erson mayhave 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. As \owner" of this directory and its subdirectories,

you also have control over access to the les in the account.

Using SAM

To create a user account, you will need to use SAM, the System

Administration Manager.

Caution

In order to use SAM, you must be logged in as

by the command prompt \#"). The

root

(indicated

account is a separate

This means that you need to take actions more carefully when

you are

root

. The

root

account is only used to do system

administration tasks, and, for security reasons, it should use a

password which is dierent from your everyday user password.

Using HP-UX

and

System Administration Tasks

giveyou more

details on using SAM.

Getting Started with HP-UX 3-13

You can navigate around a SAM screen on a character terminal using the

arrow keys and

selection is illuminated, press

to illuminate the selection you want to activate. When the

Tab

to activate (or \choose") it.

Enter

1. Type the following:

On HP-UX 9:

/usr/bin/sam

ENTER

On HP-UX 10:

/usr/sbin/sam

At the opening menu, choose

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Users and Groups->

At the next screen, choose

ENTER

illuminated.

NNNNNNNNNNNNNNNNN

Users

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Users and Groups->

by pressing

.You will see a screen displaying a list of

Enter

with

logins and real names.

Go to the

menu bar). Select

form

NNNNNNNNNNNNNNNNNNNNNNN

Actions

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

menu (use the appropriate function key to get to the

NNNNNNNNNNN

Add

from the

Add a User Account

NNNNNNNNNNNNNNNNNNNNNNN

Actions

pull-down menu. You will see a

5. Fill in your login name, choice of start-up program and environment (if

dierent from the defaults given), and the optional information.

Note

At this pointyou can select X Windows as your login default

environment, if you so desire.

3-14 Getting Started with HP-UX

6. Choose

when you are nished.

7. You will b e asked to select a password. (See \Selecting a New Password"

NNNNNNNN

for password requirements. If you wish, you can select a temporary

password and reset it later.) Type the password and choose

). Re-enter the password as requested and choose

Enter

NNNNNNNN

(or press

. The re-entered

password must match the rst.

Choose

When the \Task Completed" message app ears, choose

10.

Select

NNNNNNNN

NNNNNNNNNNNNNN

Exit

then

NNNNNNNNNNNNNNNNNNNNNNNNNN

Exit SAM

NNNNNNNN

Getting Started with HP-UX 3-15

Setting or Changing a Password

From a command line shell prompt, you can use the

directly to set or change a password. (You do not haveto be

passwd

command

root

.) Enter the

following:

passwd

Enter

You will be prompted for your old password. Then you will b e prompted to

enter and re-enter your new password. The re-entered password must match

the rst entry.

See the \Selecting a New P

selecting passwords. Use the same pro cedure to c

assword" section belowif you need help with

hange an old password

as to add a new password. If you already have one, you will be prompted

appropriately for the old password.

Selecting a New Password

If you have already booted and used your system, you should already have set

dierent passwords for your user account and for

root

However, you will also wanttochange your password from time to time as a

matter of go od security practice. The following gives the general requirements

of setting passwords.

A password must meet four criteria to be valid:

Contain at least six characters.

At least twocharacters must be alphabetic.

At least one character must be a number (0-9) or a special character (/, ?, !,

or other punctuation mark).

Dier from your previous password by at least three characters.

Your password is case sensitive, so the password

password

?secret

.Your password can also b e as long as y

?Secret

is dierent from the

ou want, but only

the rst eightcharacters are checked.

If you are adding many users to your system, see

System Administration Tasks

for the details of controlling access to your system.

If you have not yet set your password, you can do so using SAM or a shell

command line.

3-16 Getting Started with HP-UX

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 pro cedure. Turning o the power

for your system without rst doing the shutdown pro cedure

may result in damage to data on your disk. Always execute the

shutdown pro cess to completion rst.

1. Exit all processes currently running.

2. Execute the

shutdown

command as describ ed in the next section to bring

the system to a halted state.

You can do this either from the command line, with SAM, or b

y using the

HP VUE Toolbox. The following pro cedure uses the conventional HP-UX

command.

Using the Shutdown Command to Stop Your System

1. As

root

, exit your applications and, at a shell prompt, type the following

command:

cd /

Enter

shutdown -h 0

Enter

This gives a zero-length \grace p eriod" before the system goes down to the

halted state.

2. You will see a message:

Halted, you may now cycle power.

3. At this time the system no longer responds to k

eyboard input and you may

turn o the power. Turning the system back on again will initiate the boot

sequence (see App endix B).

If you wanttoshut down and reb oot automatically instead of using the above

procedure, simply enter the

See

shutdown

(1M) for various other options.

shutdown

command withnooptions.

Getting Started with HP-UX 3-17

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

advanced work with shell programming, see the manual

Using HP-UX

Shells: User's Guide

.For more

3-18 Getting Started with HP-UX

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.

Configuring for a VXI/MXI System 4-1

Overview

If your Model V743 VXI controller is to be a no de in an HP-UX cluster, and

it has not yet been installed and congured according to the procedures in the

Instal lation Guide

for the Mo del V743 VXI controller, see \Conguring the

Controller" in Chapter 3 before proceeding.

This chapter describes the VXIbus default values and howtochange these

values using the utilities provided with the HP Standard Instrument Control

Library (SICL). SICL is an I/O library that comes with your Mo del V743

VXI controller. You can use SICL for communication with your VXI

SCPI-compatible instruments. Install SICL according to the instructions in the

HP SICL User's Guide for HP-UX

.Ifyou have an application other than HP

SICL, see your application's documentation for information on changing the

VXIbus conguration.

Description of HP SICL

SICL is a modular instrument communications library that works with a

variety of computer architectures, I/O interfaces, and operating systems.

Applications written in C or C++ using this library can be p orted at the

source code level from one system to another without, or with v

ery few,

changes.

SICL uses standard, commonly used functions to communicate over a wide

variety of interfaces. For example, a program written to communicate with

a particular instrument on a given interface can also communicate with an

equivalent instrument on a dierenttype of interface. This is possible because

the commands are independent of the sp ecic communications interface.

SICL also provides commands to take advantage of the unique features of

eachtyp e of interface, thus giving the programmer complete control over I/O

communications.

4-2 Configuring for a VXI/MXI System

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).

The abovevalues are programmed into the Model V743 VXI controller

EEPROMs at the factory. There are times, however, when you wanttochange

these values. See the next section \Changing Your VXI/MXI Conguration,"

for details on changing these values.

Configuring for a VXI/MXI System 4-3

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

You can reserve 1 MByte of the Mo del V743 VXI controller system memory to

be used as VXI shared memory in A24 address space. The Mo del 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.

Instead, this memory is mapp ed onto the VXI backplane for use as VXI shared

memory.You can use the SICL \

feature by executing the following:

On HP-UX 9:

/usr/pil/bin/e1497cnf -i vxi

On HP-UX 10:

/opt/sicl/bin/e1497cnf -i vxi

e1497cnf

" utility to enable or disable this

See the \Customizing your VXI/MXI System" chapter in the

Guide for HP-UX

Note

4-4 Configuring for a VXI/MXI System

for more information on using the

You must be super user in order to run this utility

also requires you to reboot the system.

e1497cnf

HP SICL User's

utility.

. This utility

Configuring the VXI/MXI Trigger Lines

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.

Configuring for a VXI/MXI System 4-5

Trigger Lines

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

4-6 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.

Routing VXI TTL Trigger Lines in a Multiple Mainframe System

When you havemultiple mainframes connected via the MXIbus, the TTL

trigger lines are not routed from one mainframe to another. The INTXbus do es

not allowmultiple INTXbus devices to drive the same TTL trigger line. If

you need TTL trigger lines in the extended VXI mainframes, y

the

/usr/pil/etc/vxi16/ttltrig.cf

/etc/opt/sicl/vxi16/ttltrig.cf

conguration le on HP-UX 9, or the

conguration le on HP-UX 10, to map

ou need to edit

the TTL trigger line to the source logical address.

The following example illustrates an entry in the

ttltrig.cf

le, where the

rst column is the TTL trigger line and the second column is the logical

address of the TTL trigger source:

(Multiple trigger sources are still allowed on the same line within the same

mainframe.)

In the example above, all TTL trigger lines are sourced by the device at logical

address 0.

The following is an example of what you would see when the resource manager

runs:

Configuring for a VXI/MXI System 4-7

VXI-MXI TTL Trigger Routing:

Name 01234567

---- --------

hpvximxi IIIIIIII

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:

ttltrig.cf

124

resource manager output:

le:

VXI-MXI TTL Trigger Routing:

Name 01234567

---- --------

hpvximxi I0IIIIII

I - MXI->VXI

O - VXI->MXI

* - Not Routed

4-8 Configuring for a VXI/MXI System

Note

You can use the

HP-UX 9, or

/usr/pil/bin/e1489trg

/opt/sicl/bin/e1489trg

diagnostic test on

test on HP-UX 10, for

the MXI/INTX trigger and interrupt circuitry. See App endix

F, \Conguring your VXI/MXI System," in the

User's Guide for HP-UX

for information on this and other

HP SICL

diagnostic tests for the E1489 MXIbus Controller Interface.

Inverting the Polarity of the Model V743 VXI Controller External

Trigger Lines

At times you may wish to change the p olarity of the

Trig In

and

Trig Out

lines on the Model V743 VXI controller. This would allow you to connect to

an external device independent of the device's polarity. There is a SICL utility,

itrginvrt

, that can be used to do just this. The follo

inverts the p olarity of the

Trig In

line:

wing is an example that

itrginvrt -a vxi -i ON -o OFF

Where:

-a vxi

-i ON

-o OFF

See the \Customizing your VXI/MXI System" chapter in the

Guide for HP-UX

Note

species the interface name,

vxi

species that the Trig In line is to be inverted

species that the Trig Out line is not to be in

for a complete description of the

itrginvrt

The external trigger lines remain inverted until power is cycled

or the resource manager runs (with

iclearorivxirm

verted

HP SICL User's

utility.

, for

example). The external trigger lines then return to the same

state as the trigger line routed to them.

Configuring for a VXI/MXI System 4-9

Examining the VXI/MXI Boot Process

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 b oots. The

following is a summary of the VXIbus b oot process utilities:

iproc

This utility runs at system b oot and p erforms various system

initialization functions. It uses the

iproc.cf

conguration le to

determine when the other conguration utility runs.

ivxirm

This utility runs the resource manager which initializes and

congures the VXI/MXI mainframe resources. The resource

manager reads the VXI/MXI conguration les and p olls the

VXI devices to determine their resources and capabilities.

This utility runs at mainframe initialization if specied in the

iproc.cf

conguration le (the default is to not run at mainframe

initialization).

Note

These utilities and conguration les are only provided with

the SICL

VXI

leset. In order to use VXI/MXI, you must

have loaded this leset during the SICL installation. See the

HP SICL User's Guide for HP-UX

for SICL installation and

conguration information.

4-10 Configuring for a VXI/MXI System

Viewing the VXIbus System Configuration

You can use the SICL

ivxisc

utility to read the current system conguration

and printahuman 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 bo ot-up initialization line is commented out by

default. You

the

/usr/pil/etc/iproc.cf

/etc/opt/sicl/iproc.cf

must

un-comment the following line in

le on HP-UX 9, or the

le on HP-UX 10, in order for the

resource manager to run on bo ot-up.

boot ivxirm -p I vxi

VXI/MXI Configuration Files

The VXI/MXI conguration les are used to specify some site-dep enden

conguration rules and anychanges from the default. These les are not

usually edited except under sp ecial circumstances. See the

Guide for HP-UX

for more details on these les and when you want to make

HP SICL User's

changes to them.

Configuring for a VXI/MXI System 4-11

VXI/MXI Configuration Files

Conguration

Description

File

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.

dynamic.cf

Contains a list of VXI devices to be dynamically congured. You only

need to add entries to this le if you wanttooverride the default

dynamic conguration assignmentby the resource manager.

vmedev.cf

Contains a list of VME devices that use resources in the VXI

mainframe. Edit this le if you add a VME device to your VXI system.

irq.cf

Contains a database that maps specic interrupt lines to VXI interrupt

handlers. If you have non-programmable interrupters and you want

the interrupters to be recognized by a VXI interrupt handler, you must

makeanentry in this le. Keep in mind that not all VXI devices need

to use interrupt lines and not all interrupt lines need to b e assigned.

cmdrsrvt.cf

Contains a commander/servant hierarchy other than the default for

the VXI system. Edit this le only if y

ou wanttooverride the default

according to the commander's switch settings.

names.cf

Contains a database of a list of symbolic names to assign VXI devices

that have been congured. Edit this le if you add a new VXI device

to your system that is not currently in the database.

oride.cf

Contains values to be written to logical address space for

of register-based instruments every time the resource manager runs.

ttltrig.cf

Contains the mapping of VXI devices to TTL trigger lines for

extended VXI/MXI systems. Edit this le only if y

ou havean

extended VXI/MXI system and you wantyour TTL trigger lines to be

recognized.

4-12 Configuring for a VXI/MXI System

The

iproc

The

iproc

and monitors the VXI backplane for SYSRESET. The

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).

Utility (Initialization and SYSRESET)

program is run from

/etc/rc

. This program becomes a daemon

iproc.cf

le tells

iproc

Note

The SYSRESET line is commented out by default. You

un-comment the following line in the

le on HP-UX 9, or the

HP-UX 10, in order for the resource manager to run on

SYSRESET.

sysreset vxi ivxirm -t 5&

/etc/opt/sicl/iproc.cf

/usr/pil/etc/iproc.cf

le on

must

Configuring for a VXI/MXI System 4-13

The following is an example of the

/usr/pil/etc/iproc.cf

le:

d a

# iproc configuration file

# Boot up functions

# Lines are of the form:

# boot <command_to_execute>

boot echo "PIL: Instrument I/O Initialization"

# 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 '&').

sysreset vxi ivxirm -t &

# Sample lines for a second VXI/MXI interface:

#boot ivxirm -p -I vxi2

#sysreset vxi2 ivxirm -t &

# The following line must be present for ALL VXI/MXI systems

monitor

c b

4-14 Configuring for a VXI/MXI System

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.

With the SICL C library,you simply open a communications session with the

desired instrumentorinterface (

and send your instrument SCPI (Standard Commands for Programmable

Instruments) commands directly over the VXIbus backplane. The following is a

C language example that queries a VXI instrument for its identication string

and prints the results:

vxi

,or

iscpi

for register-based instruments)

Configuring for a VXI/MXI System 4-15

d a

/* idn.c

The following program uses SICL to query a VXI

instrument for an identification string and prints the results. */

#include <stdio.h>

#include <sicl.h> /* SICL header file */

/* Modify this line to reflect the address of your device */

#define DEVICE_ADDRESS "vxi,24"

void main()

{

/* declare a device session id */

INST id;

char buf[256];

/* error handler to exit if an error is detected */

ionerror(I_ERROR_EXIT);

/* open a device session with device at DEVICE_ADDRESS */

id = iopen (DEVICE_ADDRESS);

/* set timeout value to 1 sec */

itimeout (id, 1000);

/* send a SCPI *RST command and prompt for identification string */

iprintf (id, "*RST\n");

ipromptf (id, "*IDN?\n", "%t", buf);

/* print contents of buf */

printf ("%s\n", buf);

/* close device session */

iclose (id);

}

c b

For More Information

See the

HP SICL User's Guide for HP-UX

and the

HP SICL Reference Manual

for information on using HP SICL.

4-16 Configuring for a VXI/MXI System

Configuring Graphics

Chapter Contents

Monitor Selection.

Displaying Graphics on a Remote X Host.

Configuring Graphics 5-1

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

Resolution Size Refresh

Frequency

(Hz)

HP D2806A 1024 x 768 15 in. 70

HP A4032A 1280 x 1024 17 in. (Multi-

Sync)

HP A4033A 1280 x 1024 20 in. 72

HP A4032B

1280 x 1024 17 in. 60

(Southern

Hemisphere)

HP A4033B

1280 x 1024 19 in. 72

(Southern

Hemisphere)

From time to time, this information may change. F

or the most recent

information on supported monitors, please see the Release Notes for your

HP-UX system (online in

/etc/newconfig

on HP-UX 9, or

usr/share/doc

HP-UX 10) or the Support Matrix available from your HP support engineer.

Configuring for a New Monitor

Note that conguration of the Model V743 VXI con

troller to recognize new

monitors is accomplished interactively by the bo ot console handler by following

the procedure in \Conguring the Console Path and Display Format" in

Appendix B in this manual.

5-2 Configuring Graphics

Identifying Graphics Cards

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Since only on-board graphics is supported on this computer, only

GRAPHICS 1

will be indicated in the bo ot 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

environmentvariable on the controller.

DISPLAY

sets the host,

displaynumber, and screen number to which a system sends bitmapp ed output

for clients.

For example, if the Mo del V743 VXI controller is called

remote system is

VXI controller is called

your remote X host system to get it to displa

xhost +

xhost system

xwijit

, and the program running on the Model V743

,enter the following on the command line of

y for the

server system This enables the Model V743 VXI controller to

server

system

,your

recognize the remote X host.

rlogin

DISPLAY=

server system Log in on the Model V743 VXI controller.

xhost system

:0.0

On the controller, set the

DISPLAY

variable so

that it will display on your remote X system.

export DISPLAY

xwijit

Export the variable.

Run the program on the Model V743 VXI

controller.

For More Information

For detailed information on running HP VUE in a networked environment, see

the

HP VUE User's Guide

For additional information on conguration for graphics formats, see

\Conguring the Console Path and DisplayFormat" in Appendix B in this

manual.

Configuring Graphics 5-3

Configuring HP-UX for Printers

Chapter Contents

Preparing for Installation.

Testing the Printer Installation.

Dealing With Printer Problems.

Configuring HP-UX for Printers 6-1

Preparing for Installation

You mayhave 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 anyofyour

connected devices and will perform the necessary software installation of the

printer for you.

If you don't want to use SAM to install the printer, or if SAM is not on your

system, you can also use HP-UX commands directly to accomplish the same

tasks. For information on using manual system administration pro cedures for

this, see the manual

System Administration Tasks

6-2 Configuring HP-UX for Printers

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 haveitavailable 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 iden

tify the printer. It can b e any

name.):

Printer Model Number (located on a label on the bac

k of the printer):

Printer Cables

For serial data exchange, you will need the following:

HP A4301A (Serial): 9-pin high density to standard 9-pin \M". (Twoof

these cables are provided with the Model V743 VXI controller.)

Other standard cables may be required.

Procedure:

To install your printer:

1. Log in as

root

2. Run SAM bytyping:

On HP-UX 9:

/usr/bin/sam

Enter

On HP-UX 10:

/usr/sbin/sam

ENTER

Configuring HP-UX for Printers 6-3

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 arrowkeys and

screen. Press

At the SAM op ening screen, choose

Select

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Printers/Plotters

Enter

If your system do esn't haveany printers connected, you will see a message.

Make sure you have a printer connected. Choose

From the

choose

NNNNNNNNNNNNNNNNNNNNNNN

Actions

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add Local Printer/Plotter

6. Choose an appropriate selection on the sub-men

to move the highlighted areas around the

Tab

to \choose" an item when illuminated (suchas

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Printers and Plotters

on the next screen.

NNNNNNNN

or press

Enter

menu (on the menu bar at the top of the screen),

u giving options for Serial,

NNNNNNNN

HP-IB, etc.

7. A screen will giveyou information on available serial or parallel interfaces.

On HP-UX 9, if you choose

more than one serial interface could be listed. The serial in

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add Serial (RS-232C) Printer/Plotter

terfaces are

listed in ascending order. The lowest-numbered serial interface corresponds

to the lowest-numbered serial connector on your system. Choose the one to

whichyou have connected your printer.

Choose

NNNNNNNN

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

A display opens for

10.

Choose the box lab eled

Add Local Printer/Plotter

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Printer Name

and enter your

printername

for the

new printer (entered in the blank earlier).

11.

Select

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Printer Interface

and choose

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Printer/Model Interface

12. Scroll down the next screen, using the arrow keys, to nd the Model Name

of your printer.

13. Choose the Mo del Name (press

14.

Choose

NNNNNNNN

Enter

when illuminated).

6-4 Configuring HP-UX for Printers

15.

In the

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add Local Printer/Plotter

choose the box labeled

16.

Choose

NNNNNNNN

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

display which reapp ears, select and

Make this the system default printer

17. If the print sp ooler was not previously running, a screen will app ear with

the question:

NNNNNNNNNNN

Yes

or press

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Do you want to start the print spooler now?

Enter

. Choose

18. You will see a conrmation screen asking if your printer is turned on,

connected to your system, and online. Checkyour printer to ensure that it

is ready, and press

19.

You will see the message

20.

Exit the task and press the

21. Type

exit

Enter

Refer to

System Administration Tasks

to exit

Enter

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Task completed

NNNNNNNNNNNNNNNNNNNNNNNNNN

Exit SAM

root

. Press

Enter

function key.

and return to

user

status.

for additional SAM information.

Testing the Printer Installation

If you made your printer the default system printer, type the following

commands to test it:

Enter

lp .profile

Enter

(If your printer (called

printername

following command to test it:)

lp -d

printername

The le named

.profile

should print out on the new printer.

) isn't the default system printer, enter the

Enter

Configuring HP-UX for Printers 6-5

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 b een set up.

The printer cable is connected to the correct in

The cable is connected to the correct port on y

terface port on y

our system.

our printer.

6-6 Configuring HP-UX for Printers

Configuring HP-UX for a DDS Tape Drive

Chapter Contents

Finding the Status of Existing SCSI Bus Addresses.

Conguring for a Backup DDS Tap e 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.

Configuring HP-UX for a DDS Tape Drive 7-1

Finding the Status of Existing SCSI Bus Addresses

Before you attach a new SCSI drive, you can use the

determine which device addresses are currently in use. To determine the

connected SCSI bus IDs, enter

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 TOSHIBA CD-ROM

tape_drive 2.0.1.3.0 scsitape ok(0x1800202) ok HP HP35450A

disk 2.0.1.6.0 scsi ok(0x101) ok MICROP 1528

...

For example, the SCSI bus address for the HP 35450A tap e device is in the

fourth column of its hardware address as \3"(

procedure outlines how to use SAM for installing a tap e driv

ioscan -fb

2.0.1.3.0

ioscan

tool to help

). The following

7-2 Configuring HP-UX for a DDS Tape Drive

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

interchangeable. There are two ma jor dierences:

1. Audio cassette tapes transfer data in streaming mode, that is, they are

left in motion for p eriods of min

starting, stopping and repositioning, which is stressful to the tape. DDS

tapes are made rugged enough to withstand this kind of treatmen

tapes are not expected to perform this w

quickly in a data environment.

2. DDS cassettes haveamuch tighter case-dimension sp ecication than DAT

cassettes. As a result, DAT cassettes can get stuck in a DDS drive, requiring

the drive to b e disassembled. For this reason, only Hewlett-Packard

supported or properly certied DDS tape cartridges should b e used. Use of

DAT tapes intended for audio use could void your warranty.

utes. Tap es used for data are continually

ell, and as a result they fail very

not

t. Audio

Caution

Do not attempt to extricate a DAT cassette which is stuck

in a DDS drive. You may damage the drive. Have the drive

disassembled by someone qualied to do so.

Configuring HP-UX for a DDS Tape Drive 7-3

The general steps for adding a DDS tape drivetoyour 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 tap e drive that do es not match the

bus address for any other SCSI device.

4. Make all necessary hardware connections for the device.

5. Turn the new tape driveon.

6. Turn your system

7. Run SAM to create the device le for the new tape driv

and bo ot HP-UX.

Factory-Set SCSI Address

The factory-set SCSI address for the DDS drive is as follows:

SCSI bus address:

As it is possible that the SCSI bus address jumpers for a driv

emay be shipped

with dierent settings, please check the settings before installing the device.

See the

Instal lation Guide

for the device for information on resetting the bus

address, should this be necessary.

Configuring the Drive on HP-UX

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

The SAM

Kernel Configuration

procedure will conrm which drivers are

active for your tap e devices and will congure them as needed for connected

devices. Reconguring the kernel will involve reb ooting your system.

7-4 Configuring HP-UX for a DDS Tape Drive

Before You Begin:

Make a note of the tap e 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 bytyping the following:

On HP-UX 9:

$ /usr/bin/sam

Enter

On HP-UX 10:

$ /usr/sbin/sam

To get help in SAM, press the

ENTER

key. This gives you context-sensitive

information for the object at the lo cation of the cursor.

Highlight and select

At the next screen highlight and select

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

The

Tape Drive Manager

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Peripheral Devices ->

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Tape Drives ->

screen lists what tape devices are connected,

including your new device. Highlight that device.

From the

NNNNNNNNNNNNNNNNNNNNNNN

Actions

menu, choose

hardware steps for adding the tap e drive. Choose

7. A conrmation screen indicates whether any related device drivers needed

to be added to the kernel. Cho ose

NNNNNNNNNNNNNNNNNNNN

Add...

NNNNNNNNNNN

Yes

or press

. A message screen gives you the

Enter

NNNNNNNN

or press

Enter

8. If you needed to add a device driver, you will also need to create a new

kernel and (eventually) reboot the system. Select from the menuon

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

the

Create a New Kernel

screen whether you want to create the new

kernel now, later, or cancel the proposed modications. (Make sure your

Configuring HP-UX for a DDS Tape Drive 7-5

choice has an asterisk placed by it, by pressing

highlighted.) Cho ose

NNNNNNNN

to conrm your choice of action.

Enter

while that line is

9. You will next be given a choice of whether to install the new kernel nowor

later. If you move the kernel into place now, the system will also rebo ot.

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.samto/hp-ux

/etc/conf/dfile.samto/etc/conf/dfile

On HP-UX 10:

/stand/system.samto/stand/vmunix

/stand/system.samto/stand/system

If you reboot, the old kernel will be backed up as

/stand/system.prev

on HP-UX 10.

/SYSBCKUP

on HP-UX 9,

10. Exit SAM, if you have not already done so.

Note

If you are mo difying a cluster client's kernel, its kernel is not

backed up, since

/SYSBCKUP

is used exclusively for the cluster

server's kernel.

Your system is now running the added driver for SCSI DDS tape drive. You

are ready to use the drive to load a tape into your system.

7-6 Configuring HP-UX for a DDS Tape Drive

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 b een installed satisfactorily

is to load a tap e in the drive, wait for the \busy" light to stop blinking, and

execute the

The LED on the drive should icker briey. If the command completes

successfully, a listing of your devices, including the tape hardware address,

name and status will be displayed, indicating that it is installed correctly. Note

that the command may fail with a busy error if the command is executed

before the tape has completed loading.

ioscan

command.

Configuring HP-UX for a DDS Tape Drive 7-7

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. DDS Tape Drive LED State Codes

7-8 Configuring HP-UX for a DDS Tape Drive

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 tap e. This information is presented to the user

through the Caution Indicator (see chart ab ove).

A caution indication has two common meanings:

The tape heads need cleaning.

The tape itself is approaching the end of its useful life.

Maximum Usage of DDS Cassettes

Under optimal environmental conditions (50% relativehumidity,72



F),

Hewlett-Packard DDS cassettes are currently specied to 2000 passes over

any part of the tape. In operational terms, this can be translated in

approximately 200 to 300 backup operations. This takes into account that

during a backup, an area of tape mayhave several passes because streaming

cannot be maintained, or b ecause the backup software requires that certain

areas of the tape are accessed frequen

tly.

Under certain conditions the recommended number of backup operations needs

to be reduced. These conditions are as follo

ws:

Sustained use at lowhumidity.

Backup software requiring certain areas of the tape b eing accessed frequen

tly.

As a guideline, HP recommends that the number of backup operations should

be limited to 100 per cassette in extreme cases of the ab ove conditions.

In Case of Difficulty

If you experience any problems with the operation of the new driv

e, contact

your Hewlett-Packard Service Representative for assistance.

7-10 Configuring HP-UX for a DDS Tape Drive

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 and Restoring Software 8-1

Backing Up Your HP-UX System and Software

The most imp ortant part of your system is the data you have accumulated. It

is also esp ecially 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

Tasks

System Administration

Make sure you create and maintain a backup HP-UX kernel (

HP-UX 9, or

/stand/system.prev

on HP-UX 10) on your disk from which

/SYSBCKUP

you can boot in an emergency. The backup kernel is automatically created

by SAM whenever you recongure and reb oot a new kernel from your system

console.

To build your recovery system, you can use the follo wing devices:

Cartridge tape drives

DDS (\DAT") drives

Magneto-optical disk drives

Other hard disk drives

Backupyour le system.

Restore your le system, if needed.

Creating a Recovery System

A \recovery system" is a special tape containing a subset of the HP-UX

operating system. In the event of an operating system failure that prev

from bo oting or logging into HP-UX, you can b oot from the reco

very system

ents you

tape and use the tools on the tap e to repair the le system on your disk. A

recovery system is created by using commands rather than by using SAM.

You can also restore your system from a system CD-ROM that you can

purchase from your HP Sales Representative.

8-2 Backing Up and Restoring Software

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 makeachange in your disk

swap conguration.

To do this, you will need a tape drive (cartridge or DDS) and one or more

tapes.

Using

The

mkrs

to Create a Recovery System on HP-UX 9

mkrs

utility on HP-UX 9 constructs a recovery system on removable media

(or on a formatted hard disk drive). If a system later becomes unbo otable due

to a corrupt root disk, then you can b oot your system from the recovery tap e.

Once bo oted on the recovery system, you can then use the to ols it pro

vides to

repair the corrupt root disk.

Some Options for

Note

mkrs

The-soption is necessary for building Series 700 DDS tap e

recovery systems.

If enough free disk space is available in

option can b e used to make

mkrs

/usr/tmp

(typically 10-20 MB), the

-q

create an image of the recovery system in this

directory before copying it to the recovery media. This option generally saves a

great deal of time due to reduced seeking on non-random-access recovery media

(cartridge tape and DDS). Note: for DDS tape recovery systems, the-qoption

is assumed.

When creating a DDS recovery system for a small memory system (8 MB), the

-s

option should be used to sp ecify that a smaller set of les b e placed on the

recovery system.

See

mkrs

(1M) for more options with

mkrs

Backing Up and Restoring Software 8-3

Source Device Files

By default,

mkrs

uses the follo wing device les:

/dev/update.src

/dev/rct/c0

/dev/rct

If none of the ab ove defaults exist on the system,

must becreated

or the-foption must be used to specify the device le. The

one of these device les

recovery device le can be either a blo ckoracharacter device le.

Root Device Files

mkrs

,by default, uses the following device les for the root device:

/dev/dsk/0s0

/dev/root

/dev/hd

If none of the ab ove defaults exist on the system, one of these device les m

ust

be created or the-roption must be used to specify the device le to be used.

The ro ot device le must be a block device le.

If You Have a Problem

An error message results if:

None of the default device les for the recovery device exist and the

-f

option is not used to specify a recovery device le.

None of the default device les for the ro ot device exist and the-roption is

not used to specify a ro ot device le.

-m

The machine type cannot b e determined and the

specify the machine type.

option is not used to

8-4 Backing Up and Restoring Software

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 b efore, see

Tasks

before proceeding. Otherwise, SAM will provide interactive guidance.

System Administration

To use SAM, do the following:

2. Log in as

root

3. Type the following:

On HP-UX 9:

/usr/bin/sam

ENTER

On HP-UX 10:

/usr/sbin/sam

Choose

connected),

If you open

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Backup and Recovery

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Backup Devices

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Automated Backups

ENTER

(to determine what backup devices are

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Backup Devices

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

,or

Interactive Backup and Recovery

and no devices are shown or you see a

warning, make sure the device is connected and the tape is inserted.

Note

b. Choose the entry for the desired device.

Choose

If you go directly to

your local or remote backup device from

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add an Automated Backup (Local or Remote)

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Specify Backup Device

If you have to connect a device during this process, c

NNNNNNNNNNNNNNNNNNNNNNN

Refresh

from the

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add an Automated Backup

NNNNNNNNNNNNNNNNNNNNNNN

Options

menu.

from the

NNNNNNNNNNNNNNNNNNNNNNN

Actions

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Automated Backups

,you can select

NNNNNNNNNNNNNNNNNNNNNNN

Actions

. A form will displayany existing

backup devices.

hoose

menu.

Backing Up and Restoring Software 8-5

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 tap e drive. Dep ending on what tap e driveyou 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.

From the

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Add an Automated Backup

screen, you can select the options

which will bring up additional forms for specifying the following required

items:

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Select Backup Device

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Select Backup Scope

is to backup the entire system.

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Select Backup Time

: (if you have not already specied it).

: what lesets to include or exclude. The default

: time, day, date. You can also set whether you

want a full or incremental backup, for each time specication.

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Additional Parameters

(optional) allows you to sp ecify the following:

a. If you wantyour backups to cross NFS mount points.

b. If you want the tap e (cartridge or auto changer) rewound.

c. If you want an index log to be created for eac

h backup. (Results can be

mailed to a specied user.)

6. After the minimum required forms are lled out, SAM will then use

your specied tap e device to complete the bac

kup according to your

specications.

8-6 Backing Up and Restoring Software

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 lo cation on your system to restore the les (original lo cation or relative

to some other lo cation).

The device and device le for restoring the data.

Note

To restore data to disks physically connected to another

system, enter the

of SAM, or the

When restoring les that are NFS mounted to your system,

frecover

write permission. The

operates in

root

-mode. To ensure that

exported from the NFS server, login as

server and use the

command to exp ort the correct p ermissions. Refer to

exportfs

Administering NFS Services

To restore individual les:

1. Ensure that you have

2. Type the following:

On HP-UX 9:

/usr/bin/sam

ENTER

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Remote Administration

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Run SAM on Remote System

functional area

area.

can only restore those les having \other user"

user

-mode when crossing NFS mount p oints; not

(1M) in the

frecover

root=

option to the

HP-UX Reference

command normally

frecover

can restore the les

root

/usr/etc/exportfs

and the

on the NFS le

Instal ling and

manual.

root

capabilities.

On HP-UX 10:

/usr/sbin/sam

ENTER

Backing Up and Restoring Software 8-7

Choose

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Interactive Backup and Recovery

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Backup and Recovery

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Backup Devices

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Automated Backup

,or

5. Highlight the device in the list from which the data is to b e restored.

Choose

highlight

Choose the

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Recover Files or Directories

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Select Recovery Scope

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Selected Files

Do either of the follo

from the

. Clickon

checkbox (it should have an asterisk (*) in it.

wing:

NNNNNNNN

NNNNNNNNNNNNNNNNNNNNNNN

Actions

or press

menu and

Enter

Fill in the lename containing a list of les to restore. The lenames

should be full pathnames. This le is

not

a graph le. This le is used

to create a graph le. You can use the on-line index le created b

a previous backup, but it must be edited to containing only the full

pathnames of the les to be restored.

Enter each le name in the \Included" and \Excluded" bo

NNNNNNNNNNN

Add

.Ifyou make a mistake, highlight the entry with the error and use

NNNNNNNNNNNNNNNNNNNN

Modify

NNNNNNNNNNNNNNNNNNNN

Remove

to correct the mistake. Only the \Included" bo

xes and clickon

xis

required, if you choose this method.

You can use both the le and the included/excluded metho d

simultaneously to specify les to be restored.

When you have completed determining the selected les to be recovered,

clickon

NNNNNNNN

8-8 Backing Up and Restoring Software

8. Todoany of the following during the restore process, activate

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Set Additional Parameters

Overwrite new les.

Maintain original ownership.

Recover les using full path name.

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

to set the additional parameters.

NNNNNNNN

to start the restore pro cess.

NNNNNNNN

If conrmation messages appear, read the message(s) and c

hoose

proceed in each case. SAM displays a screen containing the output of the

executed

frecover

command.

Backing Up and Restoring Software 8-9

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 tap e and

your archive backup tap e(s). Also see \Bo oting and Resetting the VXIbus

Mainframe" in App endix 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 can b oot a memory-based version of

/stand/vmunix

on HP-UX 10 (known as a

/hp-ux

on HP-UX 9 or

recovery system

) from the tap e

cartridge or DDS recovery tape whichyou have made. From the recovery

system, you can mount and unmount le systems, run

fsck

to check and repair

le systems, copy les backonto your system disk, and various other tasks.

Caution

Do not run

This could introduce data corruption. Run

fsck

on a le system that is mounted and active.

fsck

in single-user

mode when checking the ro ot le system. For le systems other

than the ro ot le system, unmount the le system, run

fsck

and then remount the le system.

If your system disk (including

/stand/system.prev

on HP-UX 10) is unbootable, do the following:

1. Verify that the recovery tap e is

/SYSBCKUP

not

write-protected. HP-UX needs to have

on HP-UX 9, or

write access to your recovery tape when you bo ot it.

2. Load the recovery tape in your tap e drive and be sure that the driveis

turned on.

3. Wait for the drive to become ready (the \busy" light remains o ).

4. Reset your computer and start the b oot process b

switch to the \

Rst

" (up) p osition.

y pressing the Rst/Abt

5. Stop the automatic b oot process by pressing

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

System Search started

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

ESC

Press [Esc] to discontinue the Auto Boot process

8-10 Backing Up and Restoring Software

after the bo ot message:

NNNNNNNNNNNNNNNNNN

You will see the message:

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Auto Boot discontinued

At the Main Menu, select

NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN

Boot from a Device

will see a display like 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.0 CD-ROM HP

nnnn

--- -----------------------------------------

0 Previous Menu

33 Effective ISL Mode [ AUTOMATIC ]

66 Rescan for Boot devices

77 Reset the System

----------------------------------------------

To boot from a device, Press Key, then press [Enter/Return]

bytyping 1

Enter

.You

7. Select the DDS drive (product number HP 35450A, in the example) b

typing the number of the line for the device (\

Enter

", in the example) followed

8. Your recovery system should begin loading from the tap e. Once y

our

recovery system is running, you will have a minimum set of commands

to use. These will help you repair and restore your primary (disk-based)

operating system.

9. From this p oint, the specic things you need to do to recover your primary

system depend on the nature of the b oot problem. Some possibilities are

outlined in the following list:

Note

If your inability to b oot your system is caused by faulty

hardware, it will b e necessary to have that hardware repaired

before you can pro ceed with the items in this list.

a. Run the

fsck

program to repair your root le system. If you do this

make sure you rst shutdown to the single-user mode.

Backing Up and Restoring Software 8-11

b. The

/hp-ux

kernel le on HP-UX 9, or

/stand/vmunix

le on HP-UX

10, can be restored if it has b een 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 thecpcommand to copy the

/stand/vmunix

(it is a copyofyour

le on HP-UX 10 from your memory-based system

real

/hp-ux

le on HP-UX 9 or the

le) to the directory you used as a

mount point for your system disk. The destination le should be

called

c. You might need to restore important system les suchas

/etc/rc

procedure for doing this is almost iden

/hp-ux

on HP-UX 9 or

/stand/vmunix

on HP-UX 10.

/etc/inittab

, etc. from your memory-based system to your system disk. The

tical to the procedure for restoring

on HP-UX 9 or

/stand/vmunix

on HP-UX 10. Only the le

names and directories will b e dierent.

d. You might also need to move, remove, copy, or search for other les.

Note that the memory-based system has limited capabilities. Y

our primary

ob jective is to restore your disk-based system to a bo otable condition and

then rebo ot your computer from your system disk. From that point, you can

recover lost les from backup tap es, or whatever else is necessary to restore

your system to its normal operational condition.

For More Information

For more information on backup and recovery, see

and the reference for

HP-UX Problems

mkrs

(1m), in the online

System Administration Tasks

man

pages. Also see

Solving

8-12 Backing Up and Restoring Software

Dealing With Problems

Chapter Contents

Interpreting LED Indicators.

Managing a Bo ot Failure.

Selecting an Alternate Operating System.

Recovering from a System Panic.

Dealing with Network Failures.

Dealing With Problems 9-1

Interpreting the LED Indicators

There are four LEDs, whichyou can view on the panel of the Mo del V743 VXI

controller, next to the clock and trigger I/O.

LED Behavior

Blinks occur in blinks/second groups. Each blink pattern is rep eated at

one-second intervals:

Figure 9-1. Front Panel LEDs

9-2 Dealing With Problems

Table 9-1. Front Panel LED Indications

LED Behavior Meaning Remedy

Boot/Run

(Green)

O

continuously Power failure CheckDCpower supply on

VXI mainframe. CheckAC

power.

continuously Normal status No action needed.

One blink/second CPU failure Replace system board.

Four

blinks/second

No console

identied

Check console path and

keyboard connections. If

these are OK, replace

system board.

Sys Fail (Red)

when p owered

up and go es

Normal op eration No action needed.

o

after 5 seconds.

Stays

VXI failure.

EEPROM failed

to set up b oot

Try to reboot. Call your

Hewlett-Packard Service

Representative.

ROM

Goesonagain

after boot

Hardware failure Check

blink code. Identify chassis

code in self-test diagnostic

display (RS-232C-PortA).

Check service manual codes.

Act (Green)

\Activity", ashes

intermittently

System accessing

the VXIbus

Normal operation.

while running

Fail (Red)

when

Normal op eration No action needed.

powered-up and

goesoafter 5

seconds

Stays

VXI failure.

EEPROM failed

to set up b oot

Try to reboot. Call your

Hewlett-Packard Service

Representative.

ROM

Goesonagain

after boot

Hardware failure Identify chassis code in

self-test diagnostic display

(RS-232C-PortA). Check

code with service manual.

Boot/Run

(green)

Dealing With Problems 9-3

Managing a Boot Failure

The bo ot program is lo cated in the rmware of the Mo del V743 VXI controller.

You can congure the behavior of the b oot pro cess byinteracting with the

boot console handler. See App endix B for procedures dealing with the bo ot

console handler. If you have indications that the bo ot process has failed, check

the following items.

Boot Program Initializes Hardware

Problems during the rst stage of the boot process are rare. At this stage

problems can b e caused by:

No power to the host system (check the lo cal circuit breakers and the power

connections to your VXIbus mainframe).

Processor hardware failure.

Interface card hardware failure.

The Mo del V743 VXI controller isn't fully plugged into its VXI slot.

The LAN MAU connector is loose.

Incorrectly connected SCSI cable.

Turn o the power to the VXIbus host system. Wait ve or ten seconds and

turn the power to the system back on.

If the problem recurs, record the symptoms, the status of an

(especially any LED displays) on your processor, and any messages that appear

on your system console.

At this stage in the b oot process, most of the problems that occur require your

hardware to be serviced by a person trained and qualied to do so.

9-4 Dealing With Problems

y indicators

Selecting an Alternate Operating System

If your hardware is functioning correctly, but your usual boot device (such

as the ro ot disk) is not responding as it should, you can select an alternate

available bo ot device manually by following these steps:

1. Turn o the power to the VXIbus mainframe, and then turn it back on.

2. Press

at the prompt for stopping the boot selection process:

ESC

System Search started

Press [Esc] to discontinue the Auto Boot process

3. You will see the follo

==== MAIN MENU ===============================

Key Operation

--- -----------------------------------------

1 Boot From a Device

2 Path Configuration

3 Mode Configuration

4 Interactive Testing

5 Firmware Information

6 Hardware Information

7 System Configuration

... .........................................

77 Reset the system

88 Change Mode

99 Restart Auto Boot

----------------------------------------------

Press Key(s), then press [Enter/Return]

wing menu:

Select the rst action, \

Enter

Boot From a Device

"by pressing1, followed by

Dealing With Problems 9-5

You will see a list of b ootable 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.0 CD-ROM HP

C2943A

--- -----------------------------------------

0 Previous Menu

33 Effective ISL Mode [ AUTOMATIC ]

66 Rescan for Boot devices

77 Reset the system

----------------------------------------------

To boot from a device, Press Key, then press [Enter/Return]

4. If you are running a disked system and no disk devices are found, then y

mayhave a hardware installation problem. In this case, you should recheck

the connection to the SCSI devices and try the boot again. If this still

results in no devices b eing listed, con

tact your HP Service Representative for

assistance.

If the search lo cates a disk, enter the device selection number (\1", in

the example ab ove) to boot from that device. (Make sure that it is not

indicated as an \Install" operating system.)

Boot messages should begin to appear on the screen after sev

For detailed help in troubleshooting the boot pro cess, see the manual

HP-UX Problems

.For additional detail ab out b oot ROM conguration, see

eral seconds.

Solving

\Booting and Resetting the VXIbus Mainframe" in Appendix B in this manual.

9-6 Dealing With Problems

Recovering from a System Panic

A system panic simply means that the op erating system encountered a

condition that it did not knowhow to respond to, so it halted your system.

System panics are rare and not always the result of a catastrophe. They

sometimes occur at b oot if your system previously was not shut down prop erly.

Sometimes they o ccur as the result of a hardware failure. In a clustered

HP-UX environment, a diskless client node will panic if to o much time has

elapsed since its last communication with its server. This could b e the result of

nothing more than a LAN cable that has b een disconnected for to o long.

Recovering from a system panic can b e as simple as rebooting y

If you have an up-to-date set of le system bac

the

worst case

restoring any les that were lost or corrupted. If this situation was caused bya

rare hardware failure such as a disk head crash, you will of course havetohave

the hardware xed before you can perform the reinstallation.

Note

scenario would involve reinstalling the op erating system and

It is imp ortant to maintain an up-to-date backup of the les

on your system so that, in the event of a disk head crash or

similar situation, you can recover your data. How frequently

you update these backups dep ends on howmuch data you can

aord to lose. For information on how to back up data, refer to

System Administration Tasks

kup or system recovery tapes,

our system.

Dealing With Problems 9-7

Should your system panic, it is important to record and categorize the

circumstances asso ciated with the panic. The following table will help you do

so:

Table 9-2. Summary of Possible Causes of Panics

Problem

Action

Area

Hardware If the failure appears to be asso ciated 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 ma

ybe

associated with the System Processing Unit. In this case, call

your designated service representative.

File System

Run the le system checker,

the instructions that

fsck

HP-UX, for any subsequent reboots required by

Chapter 6 \File System Problems," in

fsck

, to correct the problem. Follow

may give, and use

reboot -n

fsck

Solving HP-UX Problems

, for

. See

for detailed information.

LAN Ensure the integrity of all LAN connections, including taps in any

AUI cable. Check for prop er 50 ohm terminations at both ends of

the LAN.

Other Reboot the system.

9-8 Dealing With Problems

Agilent E1498A Users Guide

Specifications and Main Features

Frequently Asked Questions

User Manual