Dynamic Reconfiguration for High-End Servers: Part 2--Implementation Phase
This article is Part 2 of a two-part series about planning and implementing Sun Fire™ 15K/12K server Dynamic Reconfiguration (DR) in the Solaris Operating Environment (Solaris OE). Part 2 describes the implementation of DR operations and presents best practices for successfully deploying DR operations.
This article is a follow-up article to the Sun BluePrints™ OnLine article titled "Dynamic Reconfiguration for High-End Servers: Part 1Planning Phase." Part 1 provides an introduction to Sun Fire 15K/12K server DR and details the planning phase.
The audience for this two-part series includes IT professionals, system administrators, and anyone interested in learning how to maximize system availability with DR.
The article includes the following topics:
"About the Authors"
"Ordering Sun Documents"
"Accessing Sun Documentation Online"
Dynamic Reconfiguration on Sun Fire 15K/12K servers is a powerful Sun technology for allocating hardware resources to a domain and unallocating hardware resources from a domain while the domain is running the Solaris Operating System (OS) and applications.
To successfully use DR on Sun Fire 15K/12K servers, it is strongly recommended to test all DR operations in a test domain before a domain is put into production. In addition, all DR operations should be documented in a runbook for quick reference. Only tested and well-documented DR procedures should be performed in a production domain.
Following the best practices for DR in the architect, implement, and manage phases allows you to unleash the full potential of DR.
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.