This chapter describes how you use the cfgadm (1M) command on the Sun Fire 15K domain to perform DR operations. It also describes attachment points and procedures for displaying the status of system boards.

Before you use the cfgadm (1M) command, make sure you understand the syntax for attachment points on the Sun Fire 15K platform. There are physical and logical attachment points. In addition, single attachment points are used for board slots, and dynamic attachment points are used for components. Attachment points created by the DR driver have a physical and logical path.

Physical attachment points for system boards take the following form:

/devices/pseudo/dr@0:SBx (for CPU/memory boards)

-OR-

/devices/pseudo/dr@0:IOx (for I/O boards)

where x represents the board number (0 through 17).

Logical attachment points for system boards take the following form:

SBx (for CPU/memory boards)

-OR-

IOx (for I/O boards)

where x represents the board number (0 through 17).

Dynamic attachment points refer to components (CPUs and memory) on system boards and I/O devices on I/O boards. The attachment points are created by the DR driver. Refer to the dr (7D) man page for more details.

The cfgadm (1M) command displays information about boards and slots. Refer to the cfgadm_sbd (1M) man page for options to this command.

Basic Status Display

Many operations require that you specify the system board names. To obtain these system names, type:

# cfgadm -a -s "select=class(sbd)"

The cfgadm command displays information only about those boards that are assigned to the domain; or those boards that appear in the available component list (ACL) for the domain and are not assigned to any other domain.

The following output is typical:

Ap_Id                Type       Receptacle       Occupant        Condition

SB0                  CPU        connected        configured      ok

SB0::cpu0            cpu        connected        configured      ok

SB0::memory          memory     connected        configured      ok

IO1                  HPCI       connected        configured      ok

IO1::pci0            io         disconnected     unconfigured    failed

Detailed Status Display

For a more detailed status report, use the cfgadm (1M) command with its -v option, which turns on expanded (verbose) descriptions. In addition to basic information such as the attachment point ID, receptacle and occupant states, and board status, the expanded status report also includes the date when the board was configured into the domain, the type of board, the activity state, and the physical attachment point.

This section describes how to remove a CPU/Memory and an I/O board.

To perform the following steps, you must have domain administrator privileges.

1. Log in to the domain.

2. Use the cfgadm (1M) command with its -l option to determine the attachment point for the board.

3. Stop all activity on the board.

You must halt all access by other CPU and memory boards, and prevent any further use until the board is replaced by using the appropriate Solaris commands.

4. Verify that the board does not have bound processes running.

If a process is bound to a CPU, the board cannot be removed until the process is unbound. Refer to the pbind (1M) man page for more information.

5. Unconfigure and disconnect the board using the following single command:

# cfgadm -v -c disconnect SBx

where x represents the board number (0 through 17).

Caution Caution - Do not remove a board until it is disconnected; otherwise the board will be damaged.

To remove an I/O board, you must first stop all usage of the board. To complete the steps in this procedure, you must have domain administrator privileges.

1. Log in to the domain.

2. Check the status of the board.

# cfgadm -a -s "select=class(sbd)"

3. If the system is using multipathing software:

a. Switch all board functions to the alternate board.

b. Remove any multipathing databases and/or private regions.

c. Wait until all of the alternate paths are functioning before proceeding.

4. Unmount file systems, including metadevices that have a board resident partition (for example: umount / partition ).

5. If the board contains Sun RSM Array 2000 controllers, take the controllers off-line, using the rm6 or rdacutil commands.

6. Remove disk partitions from the swap configuration.

7. If any process directly opens a device or raw partition, either kill the process or direct it to close the open device on the board.

8. If a detach-unsafe device is present on the board, close all instances of the device and use modunload (1M) to unload the driver.

Caution Caution - Unmounting file systems may affect NFS client systems.

9. Disconnect the board.

# cfgadm -v -c disconnect IOx

where x represents the board number (0 through 17).

When installing a board, consider the following points:

• Never use a board that is defective or even suspected to be unreliable; it can crash the system.

• The board type and option cards must be supported by DR.

To perform a board installation from the domain, the board must already be assigned to the domain, or must be in the available component list (ACL). Refer to the System Management Services (SMS) 1.2 Administrator Guide for information on how to assign boards or to update the ACL.

1. Verify that the selected board slot can accept a board.

# cfgadm -a -s "select=class(sbd)"

The states and conditions should be either:

• Receptacle state--Empty

• Occupant state--Unconfigured

• Condition--Unknown

-OR-

• Receptacle state--Disconnected

• Occupant state--Unconfigured

• Condition--Unknown

2. Connect and configure the board using a single command.

# cfgadm -v -c configure SBx (CPU/memory board)

-OR-

# cfgadm -v -c configure IOx (I/O board)

where x represents the board number (0 through 17).

After a short delay during which the system tests the board, a message appears in the domain console log indicating that the components have been configured. The states and conditions for a connected and configured attachment point should be:

• Receptacle state--Connected

• Occupant state--Configured

• Condition--OK

Now the system is aware of the usable devices on the board and the devices can be used.

Sun Fire 15K Dynamic Reconfiguration (DR) User Guide

816-4278-10

Copyright © 2002, Sun Microsystems, Inc. All rights reserved.