- Management Server Functions
- Section 2.7: Solaris OE Installation Preparation on Each Cluster Node
- Section 2.8: Install the Solaris 8 Operating Environment on Each Cluster Node
- Section 2.9: Install Recommended Solaris OE Patches on Each Cluster Node
- Section 2.10: The Solaris OE Post Installation and Configuration
- Section 2.11: Configure Additional Cluster Management Services
- Appendix A: System Configuration Files
Management Server Functions
Management servers can be used to perform the following functions:
Distributing (that is, saving) valuable cluster node (site-specific) configuration files
Configuring the Solaris OE syslogd(1M) 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
These logs should be saved and reviewed, as necessary.
Running the Cluster Control panel (CCP) to access the Cluster Console window for 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.
These hands-on labs demonstrate remote cluster operations (for example, with CCP operations), including configuring and monitoring the 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.
Setting up time synchronization throughout the SunPlex platform
Setting up Solaris installation services using JumpStart software
Acting as an applications server for VERITAS Volume Manager software (VxVM), Solstice DiskSuite™ software, Sun Cluster software, and associated utilities
Acting as an online repository for applications (binaries), patches, and 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 Sun Cluster 3.0 U1 System Administration Guide.
Optionally, the management server can be configured to act as a Sun Cluster 3.0 software-installation server to 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(1M) and flarcreate(1M) commands) can help enable quick and consistent disaster recovery operations.
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 application processing to occur or to achieve automatic failover to a standby node.