C H A P T E R 4 |
DR Procedures - From the System Domain |
This chapter contains procedures that describe how to use the DR feature from the Sun Fire system domain on high-end and midrange systems. Procedures that apply to one platform but not the other are clearly marked. The terms system board and I/O board apply to both platforms.
Caution - Before you attempt to perform any DR operation on a board or component, determine its state and condition as described in Checking Device Type, State and Condition.
|
You must be superuser to run DR in a domain.
Note - Wherever you see SBx or IOx, the x represents the board id number. |
This chapter covers the following topics:
To add a system board to the domain, the board must already be assigned to the domain, or must be in the ACL, an abbreviation for available component list on a high-end system domain and access control list on midrange system domains.
For information about the high-end system ACL, see the System Management Services (SMS) Administrator Guide. For information about the midrange system ACL, see the Sun Fire Midrange Systems Platform Administration Manual.
To Add a System Board |
1. Verify that the selected board slot can accept a board.
The states and conditions should be:
2. Add the board to the slot, then connect and configure the board.
After a short delay during which the system tests the board, a message displays 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:
Now the system is aware of the usable devices on the board and the devices can be used.
To Connect a System Board But Not Configure it |
1. Verify that the selected board slot can accept a board.
The states and conditions should be:
To Configure a Connected System Board |
Configure the connected board.
where x represents the number of the board.
To Delete a System Board |
Unconfigure and disconnect the board.
To Unconfigure But Not Disconnect a System Board |
To Delete an Unconfigured System Board |
To Delete a System Board Temporarily |
Use this procedure to power off the board and leave it in place if, for example, a board fails and no replacement board or system board filler panel is available.
1. Identify the attachment point ID for the board.
2. Detach and power off the board.
where ap_id is the attachment point ID returned by the command in Step 1.
To Find the System Board that Contains a Domain's Permanent Memory |
Identify the board that contains permanent memory.
To Unconfigure a System Board with Permanent Memory |
1. Identify the board that contains permanent memory.
2. Unconfigure the board that contains permanent memory.
Note - Using the -y option here does not prevent the quiesce. |
To Move a System Board Between Domains |
1. Identify the slot number of the board to be removed.
2. Unconfigure the board but leave the power on to preserve the test status:
where ap_id is the attachment point ID returned by Step 1.
At this point, the slot is not assigned to any domain, and the slot is visible to all domains.
3. In the domain to which you are moving the board, check to see if the board is now visible as disconnected.
4. Configure the board in the new domain.
To Add an I/O Board |
1. Verify that the selected board slot can accept a board.
The states and conditions should be:
3. For a midrange system, test the I/O board; for a high-end system, proceed to the next step.
If you are adding a board to a midrange system, see To Test an I/O Board (Midrange Only).
4. Connect and configure the board.
After a short delay during which the system tests the board, a message displays 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:
Now the system is aware of the usable devices on the board and the devices can be used.
To Add and Connect an I/O Board But Not Configure it |
1. Verify that the selected board slot can accept a board.
The states and conditions should be:
3. For a midrange system, test the I/O board; for a high-end system, proceed to the next step.
If you are adding a board to a midrange system, see To Test an I/O Board (Midrange Only).
To Configure a Connected I/O Board |
Configure the connected I/O board.
To Delete an I/O Board |
Unconfigure and disconnect the I/O board.
To Unconfigure an I/O Board But Not Disconnect it |
Unconfigure the I/O board without disconnecting it.
To Disconnect an Unconfigured I/O Board |
Disconnect the unconfigured I/O board.
Note - The following procedures apply to both single-core and dual-core CPUs. |
To Configure CPU on a System Board |
where x represents the board number and y represents the CPU number, which is 0 through 3 for Sun Fire high-end and midrange systems.
To Configure Memory on a System Board |
where x represents the board number. For memory, the command applies to all the memory on the system board
To Configure All CPUs and Memory on a System Board |
Configure all CPUs and memory on the board.
To Unconfigure CPU on a System Board |
where x represents the board number and y represents the CPU number, which is 0 through 3 for Sun Fire high-end and midrange systems.
To Unconfigure Memory on a System Board |
where x represents the board number. For memory, the command applies to all the memory on the system board
To Unconfigure All CPUs and Memory on a System Board |
Unconfigure all CPUs and memory on the board.
To Track a Memory Unconfigure Operation |
You can use the cfgadm(1M) command to track the progress of a memory unconfigure operation. The following command displays a snapshot of the amount of memory deleted, and the amount of memory remaining to delete.
Track the memory-delete process.
Each hot-plug slot on an I/O board can be individually connected, configured, unconfigured, and disconnected. Each attachment point for a hot-plug slot, which identifies both the slot and the adapter card that is plugged into the slot, is created when the I/O board is configured into the domain.
Sun Fire high-end systems support PCI and hsPCI cards. Sun Fire midrange systems support PCI and CompactPCI cards. In the procedures that follow, PCI refers to any of these card types.
To Connect a PCI slot on an I/O Board |
where pci_ap_id represents the ID of the PCI slot.
For example, to connect, but not configure, an adapter at slot 1 of I/O board 1 into a domain, use a command such as the following:
To Configure a PCI slot on an I/O Board |
where pci_ap_id represents the ID of the PCI slot.
For example, to configure the adapter at slot 1 of I/O board 1 into the domain, use a command such as the following:
To Disconnect a PCI slot on an I/O Board |
where pci_ap_id represents the ID of the PCI slot.
For example, to disconnect an adapter at slot 1 of I/O board 1 before unplugging the adapter, use a command such as the following:
To Unconfigure a PCI Slot on an I/O Board |
where pci_ap_id represents the ID of the PCI slot.
For example, to unconfigure the adapter at slot 1 of I/O board 1 out of the domain, use a command such as the following:
For more information, see cfgadm_pci(1M).
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.