IBM Books

Installation and Migration Guide


Replacing a fixed disk

This procedure applies only to disks that are part of the rootvg volume group.

Step 1: Shut down the node

You can use Perspectives to power off the node.
If using: Do this:
Perspectives

SELECT
The Hardware Perspective icon by double clicking

SELECT
The Nodes Pane
  • The Nodes Pane receives focus.

SELECT
The node to power off

PRESS
Power Off icon

SELECT
The power off options

PRESS
Apply

cshutdown Issue:
cshutdown -G -N 48

Step 2: Replace the disk

Your IBM Customer Engineer (CE) performs this step. Make sure that the new disk has equivalent or greater disk space available.

Step 2a: Unconfigure DCE-related information for the node (required for DCE)

Note:
You must have cell administrator authority to perform this step.

If a node was previously configured for DCE, you must remove any DCE-related principles and objects from the DCE registry before issuing the nodecond command.

  1. On the control workstation, use the rm_spsec -t admin dce_hostname command.
    Note:
    To run this command off of the SP, you must set the SP_NAME environment variable on the remote workstation to point to the SDR of the SP system being configured. Refer to the rm_spsec command in PSSP: Command and Technical Reference for a description of the -r (remote) flag.
  2. Do a DCE Admin unconfigure for the node (smit rmdce).
    Note:
    To remove any additional principals related to the node using the SMIT panels, enter the host name of the adapter to be deleted. For example, on the "Admin unconfiguration for another machine" panel in the "Machine's name or TCP/IP address" field, enter the host name for the additional adapters.
  3. |For the nodes being removed, verify that all DCE principals have |been deleted from the DCE registry. Issue:
    |dcecp -c principal catalog -simplename

You must now create new DCE information for the node by performing the following steps:

  1. Run the setupdce command.

    Notes:

    1. You will be prompted for the cell administrator's password when you issue this command.

    2. To run this command off of the SP, you must set the SP_NAME environment variable on the remote workstation to point to the SDR of the SP system being configured. The value must be a resolvable address. For example:
      export SP_NAME=spcws.abc.com
      
  2. As an ID with cell administrator authority, run the config_spsec -v command.
    Note:
    To run this command off of the SP, you must set the SP_NAME environment variable on the remote workstation to point to the SDR of the SP system being configured. Refer to the config_spsec command in PSSP: Command and Technical Reference for a description of the -r (remote) flag.

Step 3: Install the system image on the disk

Use the spbootins command to:

  1. Set bootp_response to install using the spbootins command. For example:
    spbootins -s no -r install -l 33
    
  2. Ensure that the installation information is set up properly by running the splstdata command. For example:
    splstdata -b -l 33
    
  3. Run setup_server on the boot/install server.

Step 4: Network boot the node

Use Perspectives to network boot the node.
If using: Do this:
Perspectives

SELECT
The Hardware Perspective icon by double clicking

SELECT
The Nodes Pane
  • The Nodes Pane receives focus.

Select
Nodes to network boot

PRESS
Actions > Nodes > Netboot

PRESS
Apply

nodecond Issue:
nodecond frame_id slot_id &


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]