test

Sun Cluster 2.2 System Administration Guide

Chapter 7 Administering Server Components

This chapter describes the software procedure for adding or removing Sun Cluster node components. The topics in this chapter are listed below.

Replacing System Boards

The Solstice DiskSuite component of Sun Cluster is sensitive to device numbering and can become confused if system boards are moved around. Refer to Chapter 1, Preparing for Sun Cluster Administration, for more information on instance names and numbering.

When the node is booted initially, the multihost disk expansion unit entries in the /dev directory are tied to the connection slot.

For example, when the node is booted, system board 0 and SBus slot 1 will be part of the identity of the multihost disk expansion unit. If the board or SBus card is shuffled to a new location, Solstice DiskSuite will be confused because Solaris will assign new controller numbers to the SBus controllers when they are in a new location.

Note -

The SBus cards can be moved as long as the type of SBus card in a slot remains the same.

Shuffling the fiber cables that lead to the multihost disk expansion units also can create problems. When SBus cards are switched, you must also reconnect the multihost disk expansion units back to the same SBus slot they were connected to before the changes.

Adding Board-Level Modules

Adding or replacing board-level modules such as SIMMs and CPUs involves both software and hardware procedures.

How to Add Board-Level Modules

  1. Stop Sun Cluster on the node that is to receive the board-level module.

    In this example, phys-hahost2 will be the first to receive the board-level module.


    phys-hahost2# scadmin stopnode

  2. Halt the node.


    phys-hahost2# halt

  3. Power off the node.

  4. Install the board-level module using the instructions in the appropriate hardware manual.

  5. Power on the node.

  6. Perform a reconfiguration reboot.


    ok boot -r

  7. Start the cluster software on the node.


    # scadmin startnode

  8. Repeat Step 1 through Step 7 on the other Sun Cluster nodes that need a similar hardware upgrade.

  9. Switch each logical host back to its default master, if necessary.

    If manual mode is not set, an automatic switchback will occur.


    phys-hahost2# haswitch phys-hahost1 hahost1

Replacing SBus Cards

Replacement of SBus cards in Sun Cluster nodes can be done by switching over the data services to the node that is functioning and performing the hardware procedure to replace the board. The logical hosts can be switched back to the default masters following the procedure.

How to Replace SBus Cards

  1. Switch ownership of the logical hosts from the Sun Cluster node that needs an SBus card replaced.

    For instance, if the board is being replaced on the physical host phys-hahost2, enter the following:


    phys-hahost1# haswitch phys-hahost1 hahost1 hahost2

  2. Stop Sun Cluster on the affected node.

    Run the scadmin(1M) command with the stopnode option on the host that has the failed SBus card


    phys-hahost2# scadmin stopnode
    .

  3. Halt and power off the affected node.

  4. Perform the hardware replacement procedure.

    Refer to the instructions in the appropriate hardware service manual to replace the SBus card.

  5. Power on the node and start the cluster software on the node.


    # scadmin startnode

    The node automatically will rejoin the Sun Cluster configuration.

  6. Switch the logical hosts back to the default masters, if necessary.

    If manual mode is not set, an automatic switchback will occur.


    phys-hahost1# haswitch phys-hahost2 hahost2