HP Apollo 9000 Model 720/730 Owner's Guide for HP-UX Users HP 9000 Series 700 Computers ABCDE HP Part No.
1 January 1991 . . . Edition 1. January 1991 ... Edition 1.
About This Guide In this section you will nd information about the organization of this guide and the audience for which it is intended. You will also nd references to other documents and directions for you to to comment upon or ask questions about this guide. The HP Apollo 9000 Model 720/730 Owner's Guide describes your HP Apollo 9000 Model 720/730 workstation. It also refers to other documents that you have received with your computer and its system software.
How This Guide Is Organized Each chapter contains speci c information about your system. Read Chapter 2 to learn about your workstation's parts, connectors, switches, controls and indicators. Read Chapter 3 to learn how to turn on the power, log in, log out and turn o the power safely. Read Chapter 3 to learn about the human interfaces that come with your system. This chapter will help you decide if you wish to use the HP Visual User Environment or an HP-UX shell to control your workstation.
Audience This guide is intended for use by service personnel and by owners of HP Apollo 9000 Model 720/730 workstations. Read Me Documents Please refer to the release documents you received with your system. These documents have titles that begin with the phrase \Read Me ." In these documents you will nd information that may not have been included in this guide at the time of its publication. Problems, Questions, and Suggestions We appreciate comments from the people who use our computer systems.
Typeface Conventions Unless otherwise noted in the text, this guide uses the following typeface conventions. term Marks the rst appearance of a word and phrase that is used as terminology. Terms are explained immediately or de ned further in a glossary. Example: The practice of copying les onto other media for safe storage is called backup. Menu Item The label of a menu item. Example: Select Network Con guration Tasks to continue.
Your HP Apollo 9000 Model 720/730 2 Workstation This chapter provides an introduction to your HP Apollo 9000 Model 720 workstation and its components.
System Unit Placement The system unit is the at box that contains the computer itself. The system unit may be installed at on the desktop (see Figure 2-1), or it may be set on its side for deskside placement. A \foot" stabilizer has been included for this purpose. (See the HP Apollo 9000 Model 720 Installation Guide for information about placement.) If your system has been installed vertically on its \foot," it will resemble Figure 2-2.
Figure 2-2.
System Unit Switches Before turning on your system, you should become familiar with the system unit switches. The power switch is in the front of the unit on the right side. The other switches are behind a small bezel door just above the power switch (see Figure 2-3). These are the functions of the system unit switches: Power switch Turns system unit power on and o . Transfer-of-control switch Restarts the workstation by resetting the operating system. Service switch Used only during manufacturing.
Figure 2-3.
Understanding the LEDs On the front of the system unit is a bezel door. When the door is closed, ve LEDs can be viewed through small \windows". Beside each window is a symbol indicating the meaning associated with the activity of each LED. Table 2-1.
Figure 2-4.
The Rear of the System Unit On the rear of the system unit, you will nd the connectors you will use to attach peripherals to your workstation. The connectors are mounted on bulkheads: metal panels that cover portions of the rear of the workstation. You can get access to most of the internal parts of your workstation by removing these bulkheads. You will nd descriptions of these internal parts in Chapter 5. Figure 2-5.
The Disk Tray Bulkhead This panel covers the disk tray, which holds up to two 3.5 inch disk drives. The bulkhead is on the left side of the system unit as you view it from the rear. See Figure 2-5. The disk tray bulkhead has a pair of SCSI (Small Computer Systems Interface) connectors. (See Figure 2-6. You will nd more information about these connectors in Chapter 5. Figure 2-6.
The I/O Bulkhead The I/O (input/output) connectors are mounted on the I/O bulkhead. The I/O bulkhead is in the center of the rear panel, above the graphics interface slot. (See Figure 2-5.) The I/O connectors are illustrated in Figure 2-7. Figure 2-7.
The Power Supply Bulkhead This panel covers the power supply. It has a plug connector for the power cord. The power supply bulkhead is on the right side of the system unit as you view it from the rear. See Figure 2-5. Figure 2-8.
VSC (Graphic) Interface Bulkhead You will nd the bulkhead for the graphic interface for your workstation just below the I/O bulkhead. (See Figure 2-5.) The connector to an external graphic processor will be mounted on this bulkhead. The circuit card that is behind the bulkhead provides an interface that connects your workstation to an external graphic processor, which is in turn connected to a video display monitor. (See Figure 2-9.) Figure 2-9.
The Monitor and Its Controls The monitor is the video display device for your HP Apollo 9000 Model 720/730 workstation. It is attached to your workstation through an external graphic device. The monitor for your workstation is 98754A, a high-resolution 19-inch color monitor. Before using your monitor, you should become familiar with the controls and indicator. The power indicator is an LED just to the left of the power switch. It is lluminated when power is on.
Figure 2-10.
3 Starting Up Your Workstation This chapter tells you how to boot HP-UX and get started with the HP Visual User Environment.
Before Turning On the Power for the First Time If you are turning on your workstation for the rst time, you will be asked for some information about your system. You should know the following things: The system name of your workstation. This is sometimes called the host name. The system name should not exceed eight characters in length. Obtain a system name from your system administrator. The time zone where your computer is located.
process of user login is one of the ways that HP-UX prevents unauthorized persons from using your system. This is especially important if your system is attached to a network. Turning On the Power Turn on the power to the monitor and any external peripherals rst. If necessary, wait for any external disk drives to come up to speed. (The installation documents that are supplied with the external drives will explain this.
Logging In 1 After your computer has booted HP-UX, the login screen shown below appears. This means your hardware installation was successful and HP-UX has booted. Your HP VUE has also loaded and started. If this screen does not appear, see Chapter 6, or contact your designated service representative.
2 You must rst login as root. To login as root, type: root 4Return5 If you have given your workstation a hostname other than unknown, skip to step 4. Otherwise, go on to step 3.
3 If a window appears over your login screen cautioning you about your workstation's hostname being unknown, you may continue and start HP VUE. Move your mouse to put the pointer on the Start HP VUE screen button, then click the left mouse button once. NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Caution 3-6 You should not click on the No Windows screen button until you have learned how to read and edit les.
4 The copyright screen shown below appears. Your HP VUE workspace (the screen environment in which you interact with HP-UX) appears in about one minute. The windows displayed on your screen may not be exactly like those shown in this manual.
5 A screen similar to this one appears, with a console icon and the workspace manager. The workspace manager is also known as the control panel. Move the mouse pointer over the console icon and press and release the left mouse button twice.
6 The console icon disappears and is replaced by the console window. This is a It behaves just like any text terminal. You may type a command into it, and it will print the results of the command's execution. terminal window. For the moment, though, you will use another feature of the HP Visual User Environment: the Help System. Through interaction with the Help System, you may learn about HP VUE. Move the pointer to the Help screen button.
7 The Help Index window shown below appears. Move the mouse pointer into the window and onto the line A Tutorial for New Users and click the left mouse button once to bring the next index into the window. Then click the left mouse button on the Viewer screen button to see the help information. You need not read all the information now. See HP Visual Environment User's Guide for information on using the scroll bars.
8 To close the Help window, move the mouse pointer over the Window Menu button in the upper left-hand corner of the Help window. Then click the left mouse button twice quickly. To see all of a window that's behind another window, move your pointer onto the window you want to see, then click the left mouse button once.
Logging Out 1 3-12 To logout, move your pointer onto the control panel's lower right-hand bar. This bar is called the logout button. Click the left mouse button once.
2 This con rmation box will appear. To con rm your logout, click on the screen button marked \OK." About a minute later, the login screen will reappear.
Creating a New User Account 1 To create a new user account that you will normally use, you must rst login as root. Caution 3-14 root is a user account with special privileges and dangers. Only the system administrator should regularly login as root.
2 Activate the Help System by moving the pointer to the control panel's Help screen button (on the bottom, marked with a \?") and clicking the left mouse button once.
3 When the Help Index window appears, move your pointer onto System Administration Tasks You may need to use the scroll bar or arrows to see System Administration Tasks. Then click the left mouse button once.
4 When the System Administration Tasks Help Topic window appears, select and click on d Creating a New User Account a c b Starting Up Your Workstation 3-17
5 3-18 When you have nished reading the instructions, click on the control panel's application button. That button has a few sheets of paper pictured on it.
6 You will see a le manager window similar to this one. To open the system_apps folder, move the pointer onto the system_apps folder icon, then click your left mouse button twice quickly.
7 You will see a system applications window similar to this one. Open the sys_admin folder by putting the pointer on it and clicking your left mouse button twice.
8 This system administration window appears. Move your pointer onto the System Administration Manager (SAM) icon and click your left mouse key twice.
9 The System Administration Manager (SAM) is a application that is designed to run on text terminals. If you wish to move the highlight bar to another item, you must use the cursor keys. To press a softkey, you may either use the function keys on your keyboard or use the mouse to click on the softkeys in SAM's terminal window. With this item highlighted, Users -> NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN move the mouse pointer over the Select Item softkey and click your left mouse button once.
10 When this window appears, this line will be highlighted: Add a New User Account to the System NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN Move the mouse pointer over the Select Item softkey and click the left mouse button once.
11 Type the login name you want to use for normal work, for example: wizard NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN then click on the Perform Task softkey. Some items are set to their default values and normally will not be changed.
12 Type in the password for your new login account. For example: 123four NNNNNNNNNNNNN then press the 4Return5 key or click on the Done softkey. Caution Remember your password! If you forget your password for the system, you won't be able to log back in under the login name you have chosen.
13 NNNNNNNNNNNNN Reenter the password, then press 4Return5 or click on the Done softkey. The new user will be added to the system. You should also create a password for root. Refer to Appendix A ofthe HP Visual User Environment User's Guide .
14 After the new user has been added to the system, press the keyboard space bar to get a blank form.
15 3-28 NNNNNNNNNNNNNNNNNNNNNNNNNN Click on the Main Menu softkey.
16 NNNNNNNNNNNNNNNNNNNNNNNN Click on the Exit SAM softkey. To close the Permanent Terminal Window, move the mouse pointer over the Window Menu button in its upper left-hand corner and click the left mouse button twice quickly.
Shutting Down Your Workstation Warning Do not power off your computer without first doing these shutdown procedures. You may damage the programs and data on your disk. When you need to shut down your workstation so it can be powered o , you should follow these steps. Doing this will ensure that your le system remains intact and that you can power-up and login correctly. 1 3-30 You must be logged in as root. If you are not, logout, then login as root.
2 Open the terminal window by clicking on the console icon twice. Click on the control panel's application button. That's the one with the pages on it.
3 3-32 When this window appears, move your pointer onto the system_apps folder and click the left mouse button twice.
4 When this window appears, move your pointer onto the sys_admin folder, then click the left mouse button twice.
5 3-34 When this window appears, click on the HALTSYS icon twice.
6 When this Halt System window appears, you have three choices: If you press the 4N5 key and then press 4Return5, you can continue and your workstation will not shut down. If you press the 4Y5 key and then press 4Return5, the shutdown process starts. You will have no control of your computer until you boot HP-UX and login again. If you wait for one minute without pressing any keys, the system will halt itself.
7 The shutdown process takes about one minute. These lines appear at the lower left-hand corner of your screen: c Halting (in a tight loop) -OK to hit reset button You may now turn OFF your computer.
8 The nex time you turn on your workstation, its HP VUE login screen should appear in about three minutes. d a c b For More Information . . . To learn more about the HP-UX window environments, refer to HP Visual User Environment User's Guide , The HP Visual User Environment System Administration Manual and A Beginner's Guide to the X Window System .
3 Using Your Workstation This chapter will help you decide how to interact with your HP Apollo 9000 Model 720 workstation. It describes the following: The two types of environments you may use: HP Visual User Environment (HP VUE) HP-UX shells Sample interactions in each environment Further resources for learning more about the environments Note Your HP Apollo 9000 Model 720 workstation has HP VUE pre-loaded, and it will start up in HP VUE.
Working with HP VUE The following examples are typical of tasks to be accomplished with HP VUE. The details of the display appearance will di er from that of your workstation; these examples are only for the purpose of illustrating how you can interact with HP VUE and to help you to decide whether you prefer to work with the HP Visual User Environment or one of the shells. Like other graphical user interfaces, HP VUE provides windows for various applications that run on your computer.
About Directories and HP VUE File Managers Manage the information you store in your workstation with the le manager. Your workstation uses les to hold data. Directories are \folders" that hold les and other directory folders. 1. Move the mouse pointer over the le manager icon and press the left mouse button to open the le manager. Note Your workstation shows di erent les than those pictured. The le manager illustrated here displays the home directory of the user patti.
Example 1: Moving a File 1. If your two le manager views overlap, move the overlapping view below the underlying view by moving the mouse pointer onto the title bar (marked File Manager) of the overlapping window, pressing and holding down the left mouse button , dragging the window away from the underlying window so you can see the display areas of both, and releasing the mouse button. 2. Press and hold down the middle mouse button on the le to be moved from one of the le managers. 3.
Example 2: Copying a File 1. 2. 3. 4. Move the pointer over the le to be copied. Press and hold down 4CTRL5. Press and hold down the middle mouse button . Drag the le over an empty area in the display area of the le manager window into which it is to be copied. 5. While still holding down 4CTRL5, drop the le (release the mouse button). If you release 4CTRL5 before the mouse button, the le is moved instead of copied. 6. Release 4CTRL5.
Learning More about HP VUE To learn more about the HP Visual User Environment, read the HP Visual User Environment User's Guide . This book explains many of the features of the di erent HP VUE managers and provides examples of how they may be used.
About Shells In systems equipped only with text terminals, HP-UX usually communicates with the user through a shell. A shell is a program that captures text typed on the terminal's keyboard, interprets the text into commands and data, transmits the commands to the operating system, and prints the results of the commands' execution (and any resulting messages) on the terminal's screen. A shell is sometimes also called a command interpreter or command processor.
Table 3-1. HP-UX Shells Shell Features Bourne Shell The default shell for HP-UX. It is compatible with most of the shell programs provided with your system. Korn Shell An upwardly-compatible extension of the Bourne Shell, with many new features: A command history bu er Command aliases Pathname completion Job control Interactive command-line editing Key Shell An upwardly-compatible extension of the Korn Shell.
The command name is the name of an HP-UX command. The argument is the data that the command will act upon. There may be more than one argument . In the following examples, all of the arguments are le names. About Directories You will understand the following examples better if you know something about directories. In HP-UX, a le is a \container" for data. A directory is a \container," too, but it contains les. A directory may also contain other directories.
If /users/terry contains a le called myfile, this is how it is designated: /users/terry/myfile Because this describes the \path" one must follow from the root directory to locate myfile, /users/terry/myfile is a path name. Example 1: Moving Files Use the mv command to move les from one directory to another. For example, to move myfile into the projects directory, type: $ cd $ mv myfile projects Move to your home directory rst. Now verify that it worked: List your current working directory.
Example 2: Copying Files To copy a le into a di erent directory, use the cp command. For example, to make a copy of myfile named myfile2 in the projects directory, type: $ cp myfile projects/myfile2 $ lsf myfile projects/ The le myfile still exists. $ lsf projects myfile2 new/ old/ The copy (myfile2) is in the projects directory.
Changing Your Login Shell If your system was installed for you, the installer may have chosen a shell for you. If you prefer to use another shell, you may change your shell permanently by using the chsh (change shell) command: chsh username full shell name where username is your user name and full shell name is the full path name of the shell you want as your login shell. After you use the chsh command, you must log out and log in again for the change to take e ect.
4 Putting New Applications on Your Workstation This chapter describes how to install applications on your workstation using the /etc/update program. You will use the same procedure to install optional HP-UX products such as Network Services. Caution Do not use this chapter to install the HP-UX operating system. If you have an HP-UX Install tape, use the instructions that came with your installation tape. The following table tells you where to go for information. If You Plan to ... Where to Go Next ...
Interactive Versus Non-interactive Update The update program described in this book is interactive and uses menus, prompts, and help screens to guide you through the procedure. A non-interactive (command line) interface is also available, but is less friendly than the interactive update program.
Before Running Update Before All Updates This section lists things you need to do before you update a system. See the related documentation. See the Read Me Before Installing HP Apollo 9000 Model 720/730 document supplied with your workstation. See the Release Notes for HP-UX 8.01 .
ll /dev (if all your device les are in the /dev directory). ll /dev/rct (if your device les are grouped in sub-directories). Before you can update over the network, you must set up the netdist server. See the section \Setting Up a Network Server to Update HP-UX Applications" later in this chapter for instructions. If your server is already set up and you are ready to update, you need to nd out the hostname of the netdist server from which you will update, and the port number.
If you use a 700/92 terminal to add an application, your screen may go blank after a while if you don't enter anything from the keyboard. To turn the display back on, press the 4Shift5 key; this key is not interpreted as input. Do not use use any other key for this. Where to Go Next . . . If You Plan to ... Move on to Section ... Update from a DAT drive or netdist server. Work through the section \Running the Update Program." Then move to \Tasks to Perform after the Update.
Running the Update Program Procedure 1. If you have not already done so, see the preceding section \Before Running Update". 2. Become the superuser on the system you want to update. 3. Make sure you are in the root directory (cd /). 4. If you are loading optional lesets that do not require a system reboot, proceed to the next step. If you are not sure, proceed with the rest of this step. If you are loading lesets that cause the system to reboot you should bring the system to a single-user state.
Use this opportunity to run a simple check on the integrity of your le systems. The HP-UX program that performs this function is called fsck. Enter: fsck -p For additional information on this command, see fsck (1M) in the HP-UX Reference and Appendix A of Solving HP-UX Problems . 5. To invoke the interactive update program, type: /etc/update 6. When you invoke the interactive update program, you see the Main Menu.
Note Some tips on navigating in update: You navigate in update the same way you navigate in SAM (the HP-UX System Administration Manager). For details on navigating, use the arrow key to highlight the \How to Use Update" menu item in the Main Menu, and press Help (function key 4f15). See also \Using the System Administration Manager" in chapter 1 of the System Administration Tasks manual. NNNNNNNNNNNNNN During the update process, you will progress through a series of screens.
To change the source or destination for a DAT drive: Select \Change Source or Destination" from the Main Menu. Then select \From Tape Device to Local System". The following menu appears. d a From Tape Device to Local System Modify the desired field and press "Done". Tape Device File (source): /dev/update.
To update from a netdist server: Select \Change Source or Destination" from the main menu. Then select \From Netdist Server to Local System". The following menu appears. d a From Netdist Server to Local System Modify the desired fields and press "Done". Netdist Server (source): ____________________ Port Number: 2106 Specify the system type of the files to be loaded.
Note If you are running updist: During updist, the HP9000 Series (300 or 800) eld indicates the type of system les (300 or 800) you want to load. The default displayed is the architecture of the system where update is being run. The update and updist programs do not distinguish between Series 700 and 800 software, so if you are on a Series 700 system, you will see 800 displayed. A netdist server can be con gured to o er any combination of 300, 700, or 800 lesets.
9. When you are satis ed with your choice of software, select \Start Loading"; the system will calculate whether disk space is adequate to load the selected lesets. It accounts for the current sizes of les that will be updated. If adequate space is available, loading starts. Note If the system calculates that the amount of free disk space after loading will be below the recommended minimum or that there is insu cient space to load the selected lesets, you will receive a warning message.
If You Need to Free Up Disk Space The update program determines if you have su cient disk space before it begins loading lesets. To calculate the amount of free disk space, update searches all mounted volumes to nd where the les to be updated reside. It learns whether those volumes are writable (not NFS mounts or read-only disks) and it compares the sizes of existing les on the destination with the lesets on the update source.
How to Free Disk Space You can free disk space by de-selecting lesets or removing les, by mounting another le system, or by creating symbolic links. Deselect Filesets or Remove Files Interactively While in the update program, you can free disk space by deselecting lesets using the Partition Selection screen, the Fileset Selection screen, , or the Disk Space Analysis screen.
For example, to move /usr/man from /usr to /extra/man (where /extra/man is a le system in which more free space exists), follow the steps below. Because /usr/man is approximately 5 Mbytes, you will be freeing 5 Mbytes in the /usr le system and consuming that amount in /extra: 1. 2. 1. Copy the subdirectory cd /usr find man -print | cpio -pdumv /extra from /usr to /extra. mv /usr/man /usr/man.old 2. Temporarily rename the original man (this is your \backup"). 3. ln -s /extra/man /usr/man 3.
Tasks to Perform after the Update After the update program has completed, you need to perform various tasks to set up the system for users. These tasks include the following: 1. Log in and check the following les and directories: Check this ... /tmp/update.log le For this Information ... Contains a description of the events and any errors that occurred during the update process. For more information, see \Checking the update.log File" in this chapter.
Checking the update.log File After running the update or updist programs, check /tmp/update.log for a description of the events and any errors that occurred during the process. This log le has a date and time heading that corresponds to each update session. After you've reviewed this log, you might want to remove it: the update program will continue to append to this log le, and it could become large. The update.log le contains three broad kinds of messages: 1. Output from update or updist.
2. Output from leset customize scripts, which should be in the same format described above. 3. Output (standard output or standard error) from programs executed by update, updist, or a customize script. For example, the following output is from a program executed by update: Following is output from "/bin/make": ============================================================================== Compiling conf.c ... /bin/cc +O1 +M -Wc,-Nd3500,-Ns3500 -Dhp9000s200 -D_hp9000s300 -D_hp90 ...
Protecting Your Programs and Data Your programs and data are of great value, and you should have procedures in place to make periodic copies of them on other media, such as DAT tape. Such a copy of your le system is called a backup. There are two kinds of backups: Disk image A special tape containing an exact bit-for-bit copy of your disk(s).
a tape created with the procedure described in \Creating a Disk Image". Note You should back up your disks on a regular basis. You may use either fbackup or dd, or both in an appropriate combination. For information about backing up your system, see HP-UX System Administration Tasks . For instructions on restoring a seriously damaged le system with a disk image, see \Restoring Your Disk(s)" in Chapter 6.
is write-protected; if it is closed, data may be written on the tape. If necessary, slide the tab to close the recognition hole. 4. The command to copy a disk image onto tape looks like this: lename of=DAT device lename If you want to copy the disk located at /dev/rdsk/6s0, type: $ dd if=disk $ dd if=/usr/lib/uxbootlf.700 of=/dev/rmt/0mn bs=2k The DAT drive will run for about one minute while the le is being copied.
Setting Up a Network Server to Update HP-UX Applications Use this section to set up your workstation as a server to update HP-UX applications over the network. Overview of the netdist Program Setting up a network server to distribute update software is particularly useful if you have a large groups of networked systems that must be updated to a new application. You can set up a network distribution (netdist) server on your network to distribute applications over the network.
Before Setting Up a Network Distribution Server You need to meet the following requirements before you can set up a netdist server. Make sure the server has adequate disk space mounted at /netdist.700. The actual size will depend on the size of the lesets you wish to distribute. In fact, you might want to mount a separate disk on the netdist server to contain the directories from which the server distributes les.
Setting Up a Network Distribution Server 1. If you have not already done so, read the preceding section \Before Setting Up a Network Distribution Server". 2. On the server, create the directory /netdist.700 if it does not already exist. (The netdist program will build a hierarchy under this directory that includes a sub-directory labeled 800; however, you'll actually be loading 700 lesets. The updist program does not distinguish between Series 700 and 800.
the netdist server delivers to other systems on request: the lesets you select using updist are the only ones the netdist server can provide. To distribute software for Series 300, Series 700, and Series 800 systems, run the updist program with each series set of update tapes. After all sets of software are loaded, the Series 300 and 800 software is contained in separate directories beneath the /netdist directory. Series 700 software is contained in the 800 directory beneath /netdist.700. 5.
Series 800 To distribute software for a Series 800, type: cd /netdist/800/TOOL/product tar -cvf /tmp/TOOL.800 etc system 7. This step assumes that anonymous ftp has been set up on your system (see \Before Setting Up a Network Distribution Server" earlier in this chapter): Make the TOOL archive available to requesting systems by putting the archives in a place where other systems can get them.
Shutting Down the Network Distribution Server You'll need to shutdown an existing netdist server before updating it to distribute a new version of software. Failure to do so can cause the update or updist program to terminate and trigger a core dump. Procedure 1. The netdistd daemon spawns a child process to handle each incoming update request. Thus, if three update requests are being serviced, four copies of the netdistd daemon are running (one parent and three child processes).
Adding and Updating Filesets on the Network Distribution Server Prerequisite Read the previous section, \Shutting Down the Network Distribution Server". Adding New Filesets to an Existing Server 1. Run the updist program on the server, as described in Step 4 of \Setting Up a Network Distribution Server". Load the new lesets you want. 2. When the updist program has completed, kill and restart the parent netdistd daemon. To kill the parent daemon see \Shutting Down the Network Distribution Server".
3. When updist completes, restart the netdistd daemon, by entering the netdistd command appropriate to series architecture you are distributing. For example, to start the netdistd daemon to distribute Series 700 software, enter: /etc/netdistd -l -f /netdist.700/MAIN.pkg -P 2107 To start the netdistd daemon to distribute Series 300 or 800 software, enter: /etc/netdistd -l Checking the lowercase L netdist.log File The netdistd daemon records events in /usr/adm/netdist.
2.570 2.570 2.570 1.562 2.570 15:10:36...Begin service for hpclient on port 2106 (4) 15:10:36 update @(#) $Revision: 64.492 $ 15:10:36 HP-UX hpclient 6.5 B 9000/300 15:13:02...End service for hptest 15:27:17...End service for hpclient (1) The rst three lines in the preceding example print when you start the netdistd program. The rst line shows the version of the netdistd program; the second and third lines indicate that the database was initialized successfully.
Finding Out What Filesets Are Available to Network Update You can determine what lesets are available on the netdist server for network update by checking the MAIN.pkg le. Checking the MAIN.pkg File This MAIN.pkg le is automatically created or modi ed when you run the updist program; it describes the lesets available on the server for network distribution. The le's contents will look something like this: source "/netdist/800/ACCOUNTING/netdist.pkg"; source "/netdist/800/ALLBASE1/netdist.
The update program issues an error message if the netdist server from which the program is updating contains unsatis ed leset dependencies. To verify that the dependencies are correct, type the following command on the client system once the netdist server is running: update -s server hostname -c Modifying What Filesets are Available to Requesting Systems To change what lesets are available on the netdist server for distribution to requesting systems you can modify the MAIN.pkg le. To modify the MAIN.
Troubleshooting the Update Process The table in this section describes some of the possible situations and error messages that you might encounter during the interactive update process. Situation Updating from a local tape drive. Possible Message(s) . . . Cannot verify the specified source. Change the source specified, or ensure the media is loaded and ready to read. What to Do 1. Ensure either the tape drive is online and has queued up the tape. 2. Ensure your source is correct.
Situation Updating from a local source. Possible Message(s) Cannot open source name : What to Do Ensure your source is correct: Series 700: Default source is /dev/update.src. If your system does not have the default device le, if you are updating from a di erent source, you must specify the correct name of the source device's device le. See \Before Running Update" in this chapter. This table is continued on the following page. . . .
Situation Updating from a netdist server. Possible Message(s) What to Do 1. Netdist server host name For each of these messages, rst check that the host name and port number are correct. If you do not know the correct 2. Cannot connect to netdist name/number, see the network server running on host x or system administrator. is not in the hosts database. at port y : Server not running or connection refused. 3. Connection closed by netdist server on host name : Access to this server is restricted. 4.
Situation Possible Message(s) What to Do Network distribution requires CDF information that does not exist on pre-7.0 media. Obtain a 7.0 (or later) version of this software. Con guring a netdist server (running updist). The software on this update media cannot be distributed by a netdist server due to missing CDF information. Starting the 1. Network service name /tcp 1.
Situation Possible Message(s) You selected . . . non-essential process (other than those expected lesets that caused a system at the time of system reboot) . . . reboot, but unexpected processes are running. What to Do You have several options: Continue, and the processes will terminate when update reboots the system; users may lose work in progress. Do a shell escape, and run cat or more on /tmp/update.procs to get PIDs of nonessential processes. Kill those processes using /tmp/update.killall.
Situation A customize script has failed. Possible Message(s) Type "exit" to return to update. The process Utility requires more memory than is quits at configured. boot-up, either during or after an update. What to Do Check /tmp/update.log, and re-run the customize script as indicated. Reset the ISL fastsize parameter: 1. Cycle power on the processor (turn the processor o and then on again). 2.
5 Expanding Your Workstation and Replacing Its Parts Your HP Apollo 9000 Model 720/730 workstation can be expanded and modi ed in many ways: additional memory additional disk storage, both internal and external di erent graphic display systems This chapter contains descriptions and illustrations of how to add these options to the system unit. It also contains the procedures for removing and replacing your workstation's internal components, should that ever be necessary.
Procedure Terminology Pay special attention to the rst word in each procedure's title. This keyword informs you of the type of operation you are about to undertake: Terms De nition Replacing Implies removing a component and installing another component of the same type. Example: to replace a bad component to resolve a hardware problem. Changing Implies changing the functionality of the component. Example: to change 802.3 LAN types between thin or thick cables.
Electrostatic Discharge (ESD) Precautions Electrostatic discharge (ESD) can result from the buildup of static electricity on or around the components you handle. You can even carry a charge on you own body, and the discharge of this energy through a component or your workstation can cause damage to the system.
Replaceable Parts List System Unit Components Major components for the Base Package (PN A1094-62001): Processor card (PN A1094-66510) SIMM card (8 Megabyte) (PN A1094-66521) Core I/O card (PN A1094-60005) Power supply assembly (PN 0950-2081) Optional components include: Disk tray assembly (PN A1094-62021) 210 megabyte disk assembly (PN A1094-62025) Graphic interface card (PN 987x5-6658x) 5-4 Expanding Your Workstation and Replacing Its Parts
Getting Ready Perform the following steps to safely power down your workstation: 1. Make sure that any user processes have been stopped. In particular, warn any persons who may be using the system that you are about to take it out of service. 2. If the system is running a windowing environment, exit it by holding down the 4CTRL5 and 4Shift5 keys. While you are holding them down, press the 4Break5 key. The window display will vanish and be replaced by a text display.
Replacing the Core I/O Card Perform the following steps in the order given to replace the core I/O card: 1. Power down all the workstation components; disconnect the power cord from the system unit; disconnect all the cables connected to the core I/O card. 2. Remove the core I/O card from the middle slot of the system unit cabinet as shown in Figure 5-1. 3. Remove the two EEPROMs on the original core I/O card and install them on the other core I/O card.
Figure 5-1.
Replacing the Processor Card The core I/O card must be removed to gain access to the processor card. Perform the following steps in the order given to replace the processor card: 1. Power down all the workstation components; disconnect the power cord from the system unit. 2. Remove the core I/O card from the middle slot of the system unit cabinet as shown in Figure 5-1. 3. Remove the processor card from the top slot of the system unit cabinet as shown in Figure 5-2. 4.
Figure 5-2.
Replacing or Adding SIMM Cards The processor card must be removed to gain access to the SIMM cards. Perform the following steps in the order given to update, replace, or add SIMM cards plugged into the processor card: 1. Power down all the workstation components; disconnect the power cord from the system unit. 2. Remove the core I/O card from the middle slot of the system unit cabinet as shown in Figure 5-1. 3. Remove the processor card from the top slot of the system unit cabinet as shown in Figure 5-2.
Figure 5-3.
Replacing an Internal Disk Perform the following steps in the order given to replace the internal disks attached to the disk tray assembly: 1. Power down all the workstation components; disconnect the power cord from the system unit; disconnect the SCSI cables/terminator. 2. Remove the disk tray assembly from the rear of the system unit cabinet as shown in Figure 5-4. 3. Remove the at ribbon cable and the power cable from the drive to expose the holding screw. 4.
Figure 5-4.
Replacing the Lithium Battery The lithium battery provides power for the system clock and stable storage. It is located on the core I/O card. Caution There is danger of explosion if this battery is not replaced correctly. Replace this battery only with Panasonic BR-2325 or equivalent. Discard the used battery according to the battery manufacturer's instruction. Perform the following steps in the order given to replace the lithium battery: 1.
Figure LITHBAT here. Figure 5-5.
Changing 802.3 LAN Types Your workstation accepts two di erent types of LAN connectors. Only one of the connectors on the I/O bulkhead may be used. To change connector types, you must reset some jumpers on the core I/O card. Perform the following steps in the order given to change the 802.3 LAN type jumpers on the core I/O card: 1. Power down all the workstation components; disconnect the power cord from the system unit. 2.
Figure 5-6.
Replacing the VSC Interface Card The VSC interface card connects your workstation to an external graphics processor. Perform the following steps in the order given to replace the VSC interface card: 1. Power down all the workstation components; disconnect the power cord from the system unit; disconnect any cables connected to the graphics card. 2. Remove the VSC interface card from the bottom slot of the system unit cabinet as shown in Figure 5-7. 3.
Figure 5-7.
Replacing the Power Supply Assembly Perform the following steps in the order given to replace the power supply: 1. Power down all the workstation components; disconnect the power cord from the system unit. 2. Remove the power supply bulkhead from the system unit cabinet as shown in Figure 5-8. 3. Remove the power supply assembly from the system unit cabinet as shown in Figure 5-9. 4. Install another power supply assembly into the same slot in the system unit cabinet. 5.
Figure 5-9.
6 Troubleshooting This chapter contains information that will help you determine what's wrong with your system when you have problems. Your workstation comes with many tools to help you understand operating faults: Front panel LEDs Power-on selftests Boot Administration commands System Acceptance Test You will learn how and when to use these resources in this chapter. Troubleshooting Strategies This is an outline of what you should do in the event of trouble. 1.
error is an unrecoverable hardware error, and it may require the use of special diagnostic tools and replacement of a hardware component which you cannot access. 5. If your workstation cannot be turned o , call your designated service representative. This requires replacement of a hardware component which you cannot access. System Unresponsive Try the actions listed in Table 6-1 if your system does nothing in response to turning on the power. Table 6-1.
Operating System Will Not Load Try the actions listed in Table 6-2 if the operating system will not begin loading. Table 6-2. Problems with Loading the Operating System Problem The green-colored power LED is on, but the screen is blank or is ickering. Action If your system is equipped with an external graphics unit, make sure that its power switch is set in the ON position. Turn the Brightness control on the monitor clockwise . If the screen is still blank, turn o the power switches.
System Loses Network Communications If the program you have been running uses resources from a local area network, and it stops unexpectedly, see Table 6-3. Table 6-3. Problems with the 802.3 Network Problem 6-4 Action No systems respond to the /etc/ping command. Check the network connection at the back of your workstation. Make sure that the cable is securely fastened to the appropriate connector. Your system does not respond to /etc/ping from another system on the network.
System Works Intermittently If your system works intermittently, see Table 6-4. Table 6-4. Intermittent Failures Problem Action Parts of the system seem to work, but others do not. Run the SAX tests to verify that the system's hardware is functioning properly. (See the section \Running the SAX (System Acceptance Exerciser) Tests" in this chapter.) The hardware passes the SAX tests, but operation is still intermittent. Call your designated service representative.
Dealing with a Boot Failure If you have reached this section, your usual boot device (typically a disk) is not responding as it should. You must attempt to boot from the disk (or another boot device) by selecting it manually. To boot a device manually, follow these steps: 1. Turn o the power to the workstation, wait a few seconds, then turn the power back on. 2. Press the 4ESC5 key. In a few seconds, this message appears: Terminating selection process.
If no disk devices are listed, then your workstaton is failing to communicate with its disks. Recheck the SCSI connections and try again. 3. If the search locates a disk, attempt to boot from it. Enter the boot command (b) with your choice from among the listed devices. For example, if a SCSI disk is listed as item P0 (as in the example list above), type: Select from menu: b P0 It may be several seconds before the boot messages begin to appear on the screen.
Restoring Your Disk(s) If your system still will not boot, you must restore your disk(s) from the disk images stored on tape. The exact procedure you will use depends on the con guration of your system. If you ordered a development system, both the disks in your workstation contain programs an data supplied by the manufacturer, so both of these disks will have to be restored. If you purchased a runtime system, only one disk (the root disk) need be restored.
To copy these disk images, your computer must have at least a minimum operating system (called the recovery kernel. Follow the instructions in \Booting the Recovery Kernel". then select the disk image source you will use to restore your disk(s). Warning The following procedures will prompt you for the hardware paths of the boot device and the disks that are being restored. An error in specifying the target disks could lead to loss of data. Booting the Recovery Kernel To boot the recovery kernel: 1.
?) Help Select from menu: 3. Insert the Support Tape in the SCSI tape drive. 4. Scan the Device Selection list. Look for the SCSI tape drive and note its Pn number. For example, if the SCSI tape drive is listed as item P2, type: Select from menu: b P2 IPL This command calls on device P2 (in this case, the SCSI tape drive) to boot the Initial System Loader (also known as the Initial Program Loader or IPL). It may be several seconds before the boot messages begin to appear on the screen.
Your workstation contains two disks. They were originally installed at special locations, and if you have not made changes to your hardware con guration, they will still be in those locations. HP-UX uses device les to communicate with the disks in your workstation. A device le is used to transmit information to the disk and read information from it. In your system's original con guration, root disk uses the device le /dev/rdsk/6s0 . The other disk uses the device le /dev/rdsk/5s0. 1. Press 4X5 4Return5.
Type: $ menu The SUPPORT TAPE RESTORE DISK IMAGE MENU reappears. Backing Up Your Disks Before you restore your disk(s) from disk images on tape, back up the data that is on your disks now. Obtain a scratch tape. This is a DAT tape which may be written on without destroying needed data. Make sure that the tape is not write-protected. To do this, check the rear of the cassette. You will see a sliding tab in one corner. This tab is used to open and close the \recognition hole" in the cassette.
If the tape is write-protected, you will see this message: Unable to access tape at address for writing. Insert writable scratch tape into tape drive. Press "c" then to continue, or press "a" then to abort backup process. If you receive this message, remove the scratch tape, render it writable, put it back in the tape drive, and press 4C5 4Return5.
If you have not changed the con guration of your workstation, the user (/usr) disk is located at SCSI.5.0. If you have changed your con guration, check your records to determine the location of the user disk. 9. Type in the hardware path of the disk which contains the user (/usr) partition: Enter Path for User ( /usr ) Disk :SCSI.5.0 The backup of the user disk begins. It takes about half an hour.
SCSI.0.0, SCSI.1.0, SCSI.2.0, SCSI.3.0, SCSI.4.0, SCSI.5.0, SCSI.6.0, SCSI.7.0 Enter Tape Drive Path : 2. Type in the hardware path of the SCSI tape drive from which the system is currently booted (the hardware path of the SCSI tape drive that contains the Support Tape). Enter Tape Drive Path :SCSI.4.0 These lines appear: Press "r" then to restore Root ( / ) Disk, or press "u" then to restore User ( /usr ) Disk, or press "a" then to abort restoration process. 3.
If you have not changed the con guration of your workstation, the user (/usr) disk is located at SCSI.5.0. If you have changed your con guration, check your records to determine the location of the user disk. 6. Type in the hardware path of the disk which contains the user (/usr) partition: Enter Path for User ( /usr ) Disk :SCSI.5.0 The restoration of the user disk begins. It takes about half an hour.
Recovering a Disk from an Image Copy Made with Warning dd This procedure will completely destroy any data on the disk to which the using the dd copy is made. correct Be absolutely certain that you are designation for the destination disk. To recover your disk, boot the system from the dd copy: 1. Turn o the power to the workstation, wait a few seconds, then turn the power back on. 2. Press the 4ESC5 key. In a few seconds, this message appears: Terminating selection process.
3. Place the tape which contains the dd copy of the disk image in the DAT drive. 4. Scan the Device Selection list. Look for the SCSI tape drive and note its Pn number. For example, if the SCSI tape drive is listed as item P2, type: Select from menu: b P2 IPL This command calls on device P2 (in this case, the SCSI tape drive) to boot the Initial System Loader (also known as the Initial Program Loader or IPL). It may be several seconds before the boot messages begin to appear on the screen.
Dealing with Hardware Faults If your system still fails to boot, match the LED pattern that you had noted in the list of steps in Table 6-2 earlier in this chapter against those listed in Table 6-5 and take the recommended action. If the action has no e ect, contact your designated service representative for assistance. LED Error Codes This section contains information about the error codes displayed by the LEDs that are located behind the fold-away corner bezel (see Figure 6-1).
Figure 6-1. LED Array Table 6-5 lists some of the LED display patterns generated by the selftests that your workstation runs on its processor, memory, input/output, and graphic interface cards. Usually, these patterns will ash by quickly. However, if your workstation cannot complete its booting process, and one of these patterns is displayed on the LEDs, it may be necessary to take some corrective action.
Table 6-5.
Running the SAX (System Acceptance Exerciser) Tests SAX is an online system-level exerciser. You will use SAX in its CIT (Customer Installation Test) mode to verify that your system is correctly installed and con gured. You must have permission to access the /etc/diag directory. If you receive a message that you do not have access rights to this directory, change them. If you have superuser login priviledges on your workstation, log in as root and use the/bin/chmod command to allow access to the directory.
current time (by the system clock) the time at which the tests were started system loading information The last item, system loading, is measured in terms of the number of microseconds it takes to do a unit of work. The system load has a threshold value, and whenever this value is exceeded, a system overload occurs, and an overload indicator appears in the Tracker window.
Calling for Service If you have a problem that is not dealt with in this manual, contact your designated service representative for assistance. When calling for service, always have your system's model and serial number ready.
Troubleshooting 6-25
Index A A Beginner's Guide to the X Window System , 3-37 adding applications. See update address, station, 3-2 B battery, lithium replacement, 5-14{15 boot administration commands, 6-1 boot device, 6-6 boot failure, 6-6{7 booting the workstation, 3-1, 3-2 C color monitor, 2-13 commands cp, 3-10, 3-11 dd, 6-17 `fsck'', 6-8, 6-10 mv, 3-10, 3-11 netdistd, 4-25. See also netdist update, 4-7. See also update updist, 4-24.
graphic interfacebulkhead, 2-12 graphics card replacement, 5-18{19 LED display location, 2-6 used for troubleshooting, 6-1, 6-19, 6-21 used in troubleshooting, 6-3 LED, \heartbeat", 2-6 LED, power not illuminated when power is turned on, 6-2 LED. power, 2-6 LED, \receiving from LAN", 2-6 LED, \transmitting to LAN", 2-6 logging in, 3-2, 3-4 H M \heartbeat" LED, 2-6 host name, 3-2, 3-6 HP-UX updating, 4-1{32 HP-UX operating system, 3-2 HP-UX Support Tape, 6-8 HP Visual User Environment.
network connection, 3-1 network distribution server de ned, 4-22 networking host name, 3-2 station address, 3-2 system name, 3-2 O operating system, HP-UX, 3-2 P peripherals, external, 3-3 powering up the workstation, 3-1 power LED, 2-6 power suply bulkhead, 2-11 power supply replacement, 5-20{21 power switch, 2-4 processor card replacement, 5-8{9 R \receiving from LAN" LED, 2-6 recovery kernel, 6-8 replacement of components, 5-1 restoring a damaged le system, 6-8{16 using dd, 6-17 root user, 3-5 S SAX,
cartridge tape, updating from (errors), 4-33{34 changing source or destination, 4-11 cluster updates, 4-1, 4-14 command line, 4-1, 4-2 DAT drive, updating from, 4-5 deselecting lesets, 4-14 destination, changing, 4-11 device les, 4-3{4, 4-4 disk space.
