DR 2.0 Operations

You can execute DR operations from the SSP through the Hostview GUI or the dr(1M) shell application (refer to the hostview(1M) and dr(1M) man pages for more information). DR supports the following operations:

• DR attach - Logically attaches a system board to the operating system running in a domain. A system board is logically attached when its resources--processors, memory, and I/O adapters--are configured into a domain and are available to the Solaris operating environment. The system board must already be present in the system, powered on, and not be a member of a domain. Normally, you attach a system board after it is inserted and powered on by your service provider or after it is detached from another domain.

• DR detach - Logically detaches a system board from a domain. A system board is logically detached when its resources--processors, memory, and I/O adapters--are removed from the domain configuration and are no longer available to the domain. Normally, you detach a system board to either move it to another domain or prepare it for removal.

While DR operations are being performed within a domain, the dr_daemon(1M) (refer to the Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual) and the operating environment write messages regarding the status or exceptions of DR requests to the domain syslog message buffer (/var/adm/messages) and the SSP message files ($SSPOPT/adm/domainName/messages and $SSPOPT/adm/messages). In addition to the status and exception information displayed by Hostview and the dr(1M) shell application, the dr_daemon(1M) and operating environment messages are useful for determining the status of DR requests.

Only one DR operation per platform can be active at any time. A partially completed DR operation must be finished before a subsequent DR operation is permitted in the same domain. A DR operation that is partially completed and then dismissed within one domain does not prevent a subsequent DR operation from being started in a different domain.