test

Sun Enterprise 10000 Dynamic Reconfiguration User Guide

Chapter 1 DR on the Sun Enterprise 10000 Server

This chapter first describes what DR is and what it can do for you. Then it describes the two models of dynamic reconfiguration (DR) that are available on the Sun Enterprise 10000 server. It also contains procedures for switching between the two models.

Overview of DR

DR software is part of the Solaris operating environment. With the DR software you can dynamically reconfigure system boards in order to safely remove them or install them into a system. You perform DR operations while the Solaris operating environment is running, and with minimum disruption to user processes that are running in the dynamic system domain (referred to simply as a domain in this document).

You can use DR to do the following:

DR Models

There are two models of DR available for the Sun Enterprise 10000 server. DR model 2.0 is sometimes referred to as "legacy DR," and DR model 3.0 is referred to as "next generation DR." DR model 3.0 is available starting with version 8, update 6 of the Solaris operating environment and version 3.5 of the SSP software. Either DR model 2.0 or 3.0 can be enabled on Solaris version 8 software, whereas only DR model 2.0 can be enabled on Solaris version 7 software.

Only one model of DR can run within a domain at a time. To check the version of DR that is running, use the following command: domain_status -m.

The Sun Enterprise 10000 server can switch from one model of DR to the other. See "Model Switching" for information about switching between DR models 2.0 and 3.0.

Make sure to use the domain_status(1M) command with its -m option to verify the DR model before you execute any DR commands. The following is an example of the domain_status(1M) output. The DR-MODEL column indicates which model is enabled.


# domain_status -m

DOMAIN     TYPE                     PLATFORM   DR-MODEL   OS   SYSBDS
A          Ultra-Enterprise-10000   all-A      2.0        5.8  2
B          Ultra-Enterprise-10000   all-A      3.0        5.8  3 4
C          Ultra-Enterprise-10000   all-A      2.0        5.7  5 6

According to this output, domain A is running Solaris version 8 software (OS 5.8) with DR model 2.0 enabled; domain B is running Solaris version 8 software with DR model 3.0 enabled; and domain C is running Solaris version 7 software (OS 5.7) with DR model 2.0 enabled.

Only certain commands are available in each model, and if you execute a command that is not supported, an error message appears on the console.

DR Model 2.0

Versions 2.0 and 3.0 of Dynamic Reconfiguration (DR) let you logically attach and detach system boards to and from the operating system without causing machine downtime. DR is used in conjunction with hot swap, which is the process of physically removing or inserting a system board. You can use DR to add a new system board, reinstall a repaired system board, or modify the domain configuration on the Sun Enterprise 10000 system.

If a system board is being used by a domain, you must detach it before you can power it off and remove it. After a new or upgraded system board is inserted and powered on, you may attach it to the domain.

You can execute DR operations from the system service processor (SSP) by using the Automated DR (ADR) commands: addboard(1M), moveboard(1M), deleteboard(1M), and showusage(1M).

For more information about DR 2.0, see "Introduction to the DR 2.0 Model". For more information about using DR 2,0, see "DR 2.0 Procedures".

DR Model 3.0

DR 3.0 model offers the following enhancements over DR 2.0:

DR 3.0 has a framework that offers better integration with applications, through the Reconfiguration Coordination Manager.

DR 3.0 supports multi-pathing using IPMP.

You can execute DR operations from the system service processor (SSP) by using the SSP commands--addboard(1M), moveboard(1M), deleteboard(1M), cfgadm(1M), and showdevices(1M).

Caution - Caution -

If you switch to DR 3.0 in a domain that is running the Solaris 8 SU6 operating environment, you must upgrade the SSP software to version 3.5. SSP versions 3.3 and 3.4 do not support DR 3.0 operations.

For more information about DR 3.0, see "Introduction to the DR 3.0 Model". For information about using DR 3.0, see "DR 3.0 Procedures".

Model Switching

By default, the DR 2.0 is enabled when you install the Solaris 8 operating environment Update 6. However, you can switch the model by using the first of the two procedures in "Switching DR Models". If you have DR 3.0 enabled, you can use the second procedure to switch back to DR 2.0.

Switching DR Models

The steps in both of the following procedures are executed on the domain.

Caution - Caution -

If you switch to DR 3.0 in a domain that is running the Solaris 8 operating environment Update 6, you must upgrade the SSP software to version 3.5. SSP versions 3.3 and 3.4 do not support DR 3.0 operations.

To Switch to DR 3.0

  1. Change directories to the following directory:

    /platform/SUNW,Ultra-Enterprise-10000/kernel/drv

  2. Modify the ngdr.conf file to set the legacy-dr-model variable to 0 (zero).

    The default value for legacy-dr-model is 1.


    legacy-dr-model=0;

  3. Reboot the domain.

    After the reboot, you can verify that DR 3.0 is enabled by viewing the /var/adm/messages file for the following message.


    NOTICE: Next Generation DR Model (DR 3.0) is enabled

    To ensure that the SSP recognized the model switch, execute the following command on the SSP: domain_status -m.

To Switch to the DR 2.0

  1. Change directories to the following directory:

    /platform/SUNW,Ultra-Enterprise-10000/kernel/drv

  2. Modify the ngdr.conf file to set the legacy-dr-model variable to 1.


    legacy-dr-model=1;

  3. Reboot the domain.

    After the reboot, you can verify that the legacy model is enabled by viewing the /var/adm/messages file for the following message.


    NOTICE: Legacy DR Model (DR 2.0) is enabled

    To ensure that the SSP recognized the model switch, execute the following command on the SSP: domain_status -m