Are You Booted to the Wrong System?
If you did not interrupt the client~s boot process as described earlier in this chapter ~ and you did not remove or turn off any disk drive that was attached to the client and contained a boatable systeul~ then you are probably booted to the system on the disk.
Diagnose and correct this as follows:
1. Log in.
2. Enter the command:
/bin/getcontext
• If the system's response contains the word remoteroot~ you are probably booted to the right system.
(If this client is a member of more than one cluster, you could still be booted to the wrong server. You can check the names of the members of the current cluster by entering the command cnodes. For siulplicity's sake we recommend that a client be a member of only one cluster.)
• If the response is not found
or contains the word standalone or localroot ~ then you are booted to the wrong system. Follo\v directions under '"Tracking Down the Problem"
on the next page.
5
Tracking Down the Problem
Take the following steps if the client is either booted to the wrong systen1~ or not booted at all.
1. • If the client is booted to the wrong systenL do the following:
a. Make sure that no one else is logged into the cluster client systen1.
b. Enter the command:
fete/shutdown -h 0
c. When you receive the "halted" message, turn the cluster client's power off and on and interrupt the boot (as described under "Preparing To Add a Series 300/400 Client" earlier in this chapter) .
• If the client has not yet booted at all, try to boot it again now.
Turn the client's power off and on and interrupt the boot (as described under "Preparing To Add a Series 300/400 Clienf' earlier in this chapter).
If you do not see the cluster server's name on the line beginning LAN ... , turn power off and on once more to restart the boot ROl\1. See if the cluster server entry appears this tin1e.
:2. If you still do not see the cluster server entry. log in to the duster server and check that rbootd is rUllning all the server. for example:
ps -ef I grep rbootd
Also check the log file /usr/adm/rbootd.log.
5-18 Adding Cluster Clients
;3. If rbootd is running, you may have entered an incorrect station (link level) address into SAlvI. This address is now stored in the file / etc/ clusterconf.
You can check the format of entries in / etc/ clusterconf with the ccck (1M) con1n1and (usually restricted to the superuser).
4. If ccck returns an error, you need to fix the iten1 in error, and this may mean deleting the client and adding it back correctly. See Chapter 7,
"Rell10ving and Renall1ing Cluster Clients". If only the station address is wrong, however, you can silnply change it in / etc/ clusterconf (using the
bad connection. unusually heavy LAN traffic) or a software incompatibility
5
What To Do Next
Adding a Local Disk
If you need to add a local disk to a nevl cluster client, and you're already fanliliar with the task, the following outline should serve to remind you of the major steps.
Note
Caution
This is for quick reference only: if you have not connected a disk drive to a cluster client before, read the full explanation and example in Chapter 12, "Adding Peripherals to a Cluster".
If you are connecting a disk drive that is to be used for local swap and that disk drive is connected to an ElISA card, you must configure the card before the client attempts to swap to the disk. Otherwise the client will panic.
There's a more detailed note about this in Chapter 12, "Adding Peripherals to a Cluster", under "Example: Adding a Local Disk". For complete instructions on configuring ElISA cards, consult Installing Peripherals, HP part number B1864-90011.
1. Connect the disk drive to the cluster client.
Directions for each type of disk are in the Installirtg Peripherals Inanual.
2. Log in to the cluster client as superuser.
(Remember that the superuser login is valid for every Inachine in the cluster. which means that the superuser password you have established on the server \vill \vork on every cluster node.)
5
6. If you have configured swap on the disk, and you want other clients to swap to this swap area, too (that iSl if you want this client to be an auxiliary swap server), do the following:
a. Log in to the cluste'T' root server.
b. Run SA11 and select:
Cluster Configuration.
Caution This is for quick reference only. You can get into trouble if you reboot clients in the wrong order while changing swap servers. If you have not already read the section on "Setting Up Swap to an Auxiliary Swap Server" in Chapter 12, "Adding Peripherals to a Cluster", do so now.
c. Highlight the name of the swap client (the client that is to swap to this swap server) and choose
Modify Swap Server ...
fr0111 the Actions menu.
d. Highlight the nanle of the swap server (the client to which you have just added the disk) and press (OK ).
For example, if you have attached a swap disk to a client named client1 and you want client2 to swap to this disk. then change client2's Swap Server to client 1.
e. Turn power off and on for each client whose swap server has changed.
and let the client reboot.
The change will not take effect until you do this.
5·22 Adding Cluster Clients