Overview of Dynamic Reconfiguration

C H A P T E R 1

This chapter provides an overview of Dynamic Reconfiguration, which is controlled by the eXtended System Control Facility (XSCF).

This chapter includes these sections:

Basic DR Functions

Security

Overview of DR User Interfaces

1.1 DR

Dynamic Reconfiguration (referred to as DR, in this document) enables hardware resources such as processors, memory, and I/O to be added and deleted even while the Oracle Solaris Operating System (referred to as Oracle Solaris OS in this document) is running.

DR has three basic functions; i.e., addition, deletion and move, which can be used for the following purposes.

Add system boards without stopping the Oracle Solaris OS of the domain, to improve business operations or handle higher system loads.

Temporarily remove a faulty system board for parts replacement without stopping the Oracle Solaris OS of the domain, in the event of an error that causes the system board to become degraded.

Move a resource from one domain to another while continuously operating the domains without physically removing or inserting a system board. Resources can be moved to balance the loads on multiple domains, or to share common I/O resources between domains.

SPARC Enterprise M4000/M5000/M8000/M9000 servers have a unique partitioning feature that can divide one physical system board (PSB) into one logical board (undivided status) or four logical boards. A PSB that is logically divided into one board (undivided status) is called a Uni-XSB, whereas a PSB that is logically divided into four boards is called a Quad-XSB. Each composition of physical unit of the divided PSB is called an eXtended System Board (XSB). These XSBs can be combined freely to create domains.

DR functions on these servers are performed on an XSB. This manual uses the term system board unless physical units of PSB and XSB are described. For an explanation of each term, see TABLE 1-2.

Note - This document explains DR functions on system boards. Use the Oracle Solaris command cfgadm(1M) to execute DR on I/O devices, including PCI cards. For more information, please see the Service Manual for your server, and the cfgadm(1M) and cfgadm_pci(1M) man pages.

FIGURE 1-1 Uni-XSB and Quad-XSB (Midrange Servers)

FIGURE 1-2 Uni-XSB and Quad-XSB (High-end Servers)

TABLE 1-1 and TABLE 1-2 list DR-related terms.

TABLE 1-1 Basic DR Terms
Term	Definition
Add	To connect a system board to a domain and configure it into the Oracle Solaris OS of the domain.
Delete	To unconfigure a system board from the Oracle Solaris OS of a domain and disconnect it from the domain.
Move	To disconnect a system board from a domain and then connect the system board to another domain.
Register	To register a system board in the domain component list (hereinafter called DCL).
Release	To delete a registered system board from the DCL.
Assign	To assign a system board to a domain.
Unassign	To release a system board from a domain.
Connect	To connect a system board to a domain.
Disconnect	To disconnect a system board from a domain.
Configure	To configure a system board in the Oracle Solaris OS.
Unconfigure	To unconfigure a system board in the Oracle Solaris OS.
Reserve	To reserve a system board such that it is assigned to or unassigned from a domain on the next reboot or power-cycle.
Install	To insert a system board into a system.
Remove	To remove a system board from a system.
Replace	To remove a system board and then mount it or a new system board, for system maintenance and inspection.

TABLE 1-2 Terms Related to Hardware Configurations
Term	Definition
CPU/Memory board unit (CMU)	Unit equipped with a CPU module, and memory. High-end servers only.
Motherboard Unit (MBU)	Unit for midrange servers. A CMU is mounted on this board. Midrange servers only.
I/O unit (IOU)	Unit equipped with a PCI card and a disk drive unit.
Physical System Board (PSB)	The PSB is made up of physical parts, and can include 1 CMU and 1 IOU or just 1 CMU. In midrange servers, the CMU is mounted on a MBU. A PSB also can be used to describe a physical unit for addition/deletion/exchange of hardware. The PSB can be used in one of two methods, one complete unit (undivided status) or divided into four subunits.
eXtended System Board (XSB)	The XSB is made of physical parts. In the XSB, the PSB can be either one complete unit (undivided status) or divided into four subunits. The XSB is a unit used for domain construction and identification, and also can be used as a logical unit.
Logical System Board (LSB)	A logical unit name assigned to an XSB. Each domain has its own set of LSB assignments. LSB numbers are used to control how resources such as kernel memory get allocated within domains.
System board	The hardware resources of a PSB or an XSB. A system board is used to describe the hardware resources for operations such as domain construction and identification. In this manual, this refers to the XSB.
Uni-XSB	One of the division types of a PSB. Uni-XSB is a name for when a PSB is logically only one unit (undivided status). It is a default value setting for the division type for a PSB. The division type can be changed by using the XSCF command `setupfru`(8). Uni-XSB may be used to describe a PSB division type or status.
Quad-XSB	One of the division types of a PSB. Quad-XSB is a name for when a PSB is logically divided into four parts. The division type can be changed by using the XSCF command `setupfru`(8). Quad-XSB may be used to describe a PSB division type or status.

1.2 Basic DR Functions

This section describes the basic DR functions.

FIGURE 1-3 shows DR processing.

FIGURE 1-3 DR Processing Flow

In the example shown in FIGURE 1-3, system board #2 is deleted from domain A and added to domain B. In this way, the physical configuration of the hardware (mounting locations) is not changed but the logical configuration is changed for management of the system boards.

1.2.1 Adding a System Board

You can use DR to add a system board to a domain provided that board is installed in the system and not assigned to another domain. You can do so without stopping the Oracle Solaris OS running in the domain.

A system board is added in such stages as connect, and configure.

In the add operation, the selected system board is connected to the target domain. Then, the system board is configured to the Oracle Solaris OS of the domain. At this point, addition of the system board is completed.

1.2.2 Deleting a System Board

You can use DR to delete a system board from a domain without stopping the Oracle Solaris OS running in that domain.

A system board is deleted in such stages as unconfigure and disconnect. If the board must be assigned to another domain, the delete operation must also include an unassign step.

In the delete operation, the selected system board is unconfigured from its domain by the Oracle Solaris OS. Then, the board is disconnected from the domain. At this point, deletion of the system board is completed.

1.2.3 Moving a System Board

You can use DR to reassign a system board from one domain to another without stopping the Oracle Solaris OS running in either domain.

This move function can change the configurations of both domains without physical removal and remounting of the system board.

The move operation for a system board is a serial combination of the “delete” and “add” operations. In other words, the selected system board is deleted from its domain and then added to the target domain.

1.2.4 Replacing a System Board

You can use DR to remove a system board from a domain and either add it back later, or replace it with another system board, provided both boards satisfy DR requirements as described in this document. You can do so without stopping the Oracle Solaris OS running in either domain.

You can replace system board in the case of exchanging hardware resources such as CPUs, memory, I/O devices.

A system board is replaced successively in stages.

In the replace operation, the selected system board is deleted from the OS of the domain. Then, the system board is removed when it is ready to be released from its domain. After field parts replacement or other such task, the system board is re-installed and added.

Note - You cannot use DR to replace a system board in a midrange server because doing so would replace an MBU. To replace a system board in a midrange server, you must turn off the power of all domains, then replace the board without using DR commands.

1.3 Security

DR operations are executed based on privileges. For information about privileges and user accounts, see the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Administration Guide.

1.4 Overview of DR User Interfaces

DR operations are performed through the command line interface (CLI) within the XSCF shell or through the browser-based user interface (BUI) in the XSCF Web provided by the eXtended System Control Facility (XSCF). These operations are collectively managed by the XSCF. Furthermore, XSCF security management restricts DR operations to administrators who have the proper access privileges.

For details of XSCF shell commands provided for DR, see How To Use the DR User Interface. XSCF Web is beyond the scope of this document. See the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for further information.