- Objectives
- Prerequisites
- Introduction
- Management Server Functions
- Section 2.1: Installing and Configuring the Management Server
- Section 2.2: Configuring the Terminal Concentrator
- Section 2.3: Configuring the Solaris JumpStart Server
- Section 2.4: Installing SUNWccon Package on the Administrative Workstation
- Section 2.5: Configuring the Management Server to Administer Cluster Nodes
- Section 2.6: Configuring the Cluster Control Panel
- Appendix A: System Configuration Files
- Appendix B: References
Management Server Functions
Management servers can be used to perform the following functions:
Management servers can be designated for distributing (saving) valuable cluster node (site-specific) configuration files.
Consider, also, configuring the Solaris OE syslog facility to copy messages from each cluster node to a remote administrative workstation (or another designated host) for the purpose of notifying administrators of potential cluster disruptions (logs, which should be saved/reviewed, as necessary).
A primary function demonstrated in these hands-on labs is the ability of the administrative workstation to run the cluster control panel (CCP), accessing the Cluster Console window of each cluster node in the SunPlex platform. As instructed throughout this guide, during the installation (and when monitoring cluster operation), commands will be entered simultaneously to each cluster node using a Cluster Console window (one window for each node), accessed from the CCP Hosts menu.
Cluster management services should provide all standard administrative workstation functions and can provide additional platform management functions.
NOTE
These hands-on labs demonstrate remote cluster operations (for example, with CCP operations) including configuring and monitoring cluster and status, managing changes within the cluster (for example, shutting down individual cluster nodes on the SunPlex platform prior to performing upgrades), rebooting a cluster node, and ensuring that auto-cluster formation occurs.
Time synchronization throughout the SunPlex platform.
Solaris installation services using JumpStart software.
Applications servers using VERITAS Volume Manager software (VxVM,) Solstice DiskSuite™ software, Sun Cluster software, and associated utilities).
Online repository for applications (binaries) and patches (/PATCH).
Online repository for site-specific data and configuration files.
For more information about cluster administration functions (for example, administering cluster interconnects and public networks, patching Sun Cluster software and firmware, and backing up and restoring a cluster), refer to the documentation referenced in Appendix B including the SC3.0 U1 System Administration Guide.
Optionally, the management server can be configured to act as a Sun Cluster 3.0 software-installation server, and can help simplify software installations for each cluster node on the SunPlex platform. For example, you can install the Sun Cluster 3.0 software packages on the management server and populate a custom JumpStart software directory.
Key Practice: Use the JumpStart technology to maintain consistency and fully automate the installation of the Solaris OE and additional software packages. The JumpStart software can minimize operator errors that occur during a manual installation process. Combining JumpStart software and Flash archives (for example, with the flar and flarcreate commands) can help enable quick and consistent disaster recovery operations.
NOTE
For information about implementing Flash archives, reference recent publications available from Sun BluePrints at http://www.sun.com/blueprints/, as well as the documentation referenced in Appendix B.
Not Required for Application Failover
Clusters do not require the use of the administrative workstation for normal applications processing to occur, or to achieve automatic failover to a standby node.