Dynamic Reconfiguration for High-End Servers: Part 1 --- Planning Phase
This article is Part 1of a two-part series about planning and implementing Sun FireTM; 15K/12K server Dynamic Reconfiguration (DR) in the Solaris Operating Environment (Solaris OE). Part 1 provides an introduction to Sun Fire 15K/12K server DR and details the planning phase.
This article is a primer for the second part titled "Dynamic Reconfiguration for High-End Servers: Part 2Implementation Phase," which describes the implementation of DR operations and presents DR best practices.
The audience for this two-part series includes IT professionals, system administrators, and anyone interested in learning how to maximize system availability with DR.
Part 1 of this article contains the following topics:
"Minimum Software Requirements"
"Preparing the System: Requirements"
"About the Authors"
"Ordering Sun Documents"
"Accessing Sun Documentation Online"
Minimum Software Requirements
For both the system controllers (SCs) and the domains, the minimum version for using slot 0 DR is Solaris 8 OE (02/02) or Solaris 9 OE (04/03) with patches. The minimum Systems Management Services (SMS) software version is SMS 1.2. In addition, for both the SMS software on the SC and the Solaris OE on the domains, patches are required.
The minimum Solaris OE version for the SC is Solaris 8 OE (02/02) for slot 1 DR. For domains, the minimum Solaris OE version is Solaris 8 OE (02/02) with patches or Solaris 9 OE (04/03). The minimum SMS software version is SMS 1.3. In addition, for both the SMS software on the SC and the Solaris OE on the domains, patches are required.
For Solaris versions 10 and newer, the software is referred to as the Solaris Operating System (Solaris OS). For this article, all versions referenced are Solaris 9 OE and earlier.