- Objectives
- Prerequisites
- Introduction
- Enterprise Installation Services: Standard Installation Practices
- Hardware Configuration
- Solaris Configuration (clustadm)
- Install SUNWccon package on SC 3.0 Admin Workstation
- Patch Installation - Administration Workstation
- Configure Management Server for Administering Cluster Nodes
- Configure the Terminal Concentrator
- Configure Cluster Control Panel
- Configure Solaris OE (Each Cluster Node)
- Solaris OE —Post Installation and Configuration
- References
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Enterprise Installation Services: Standard Installation Practices
SunCluster installations must conform to the EIS Installation standards that are current at the time of the installation. For this module, we have previously gathered all configuration information and 'data-layout' criteria, as required to successfully complete the installation. Using the EIS process, this information is typically provided on the completed EIS "Install Specification" or equivalent documents.
For local (manual) installations, you must obtain and implement all current EIS standards when installing each node in the SunPlex platform. EIS installation checklists, shell scripts, Explorer and ACT software, as well as the EIS CD itself will all follow a separate revision cycle. The EIS CD revision used during any new installation will include a 'date check,' to ensure your EIS CD is current. For example, if you are using an out-dated EIS CD during the installation, you will be notified that the EIS CD you are using is ". . . > than xx days old . . . ". For local (manual) installations, you should always use the most recent EIS CD, before installing any system.
This guide, including all steps and procedures, represents a specific Sun Cluster implementation, which conforms to EIS standards at the time of this writing. Hence, during reconstruction of the lab cluster nodes, any warnings indicating that the EIS CD is 'out of date' must be accepted, since we have frozen the implementation, in order to guarantee successful configuration 'as tested'.
Installation and Planning Considerations
New installations that are well planned and well executed are critical to ensuring reliability and, ultimately, availability. Reducing system outages involves using proven methods (that is, well-documented techniques, applications, components, configurations, operating policies and procedures) when configuring highly available platforms. This includes minimizing all single points of failure (SPOFs), and documenting any SPOFs that could occur, along with documenting any associated best practices.
The following points can contribute to successful configurations, assist in sustaining daily operations, and help maximize platform availability and performance:
Ensure SC 3.0 administrators are highly trained and able to successfully test and conduct cluster failover operations for each highly available (HA) application and associated systems and subsystems, including fault isolation/troubleshooting, and disaster recovery procedures using all available utilities and interfaces.
Follow EIS recommendations for carefully documenting site-specific and application-specific configurations and procedures, as part of implementing best practices and simplifying data center operations and maintenance.
Follow EIS recommendations for Change Management: Register and record all standard and non-standard configurations, implementing change management procedures for all systems and subsystems for auditing and tracking key systems and components throughout the life cycle of the data center).
When designing SunPlex solutions, implement well-known and established configurations and techniques that minimize platform complexity and the number of active components, to simplify operations and maintenance.
Prior to installing the SunPlex platform, ensure all hardware components are fully operational and set to known state (that is, all settings to factory defaults and all disk media 'scrubbed'). This includes all system units and subsystems (disk arrays, controllers, firmware, and all shared disk media).
Provide diagnostics, utilities, and interfaces that are easy to use and interpret, with clearly documented error messages and procedures for resolving potential problems.
Refer to SunCluster 3.0 Configuration Guide for current restrictions on hardware, software, and applications running in SC 3.0 environment.
Customer Requirements
CAUTION
SC 3.0 applications are implemented across many layers, each layer has several aspects that must be considered when designing a solution. Only a comprehensive analysis of your applications requirements combined with thorough knowledge of Sun's products and services can ensure that the cluster solution will meet the service level agreement (SLA).
To obtain SC 3.0 licenses for bundled HA agents, contact your local Sun Service provider. For HA agents developed by Sun Microsystems or third party vendors requiring licenses, contact your local Sun Microsystems representative for professional services. Additionally, SC 3.0 does not include a VERITAS Volume Manager (VxVM) or CVM license, which must be purchased. In some cases, Sun StorEdge™ arrays may include a VxVM license. Ensure all licenses, information and keys are available during installation, and stored safely (that is, available for use, if needed, during disaster/recovery operations).