Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Section 2.6: Configuring the Cluster Control Panel

During this section, you will start the cluster control panel (CCP) by entering the ccp command for the cluster named nhl. Please read this entire step before entering any commands. After starting the cluster control panel, you will double-click the Cluster Console icon.

Step 2.6.1—Enabling Remote Display

If you are accessing the administrative workstation (clustadm) from a remote system, first use the xhost + command on your local system to enable remote display from clustadm to your local system.

When accessing the administrative workstation remotely, you must also set the DISPLAY environment variable on the administrative workstation (clustadm) to point to your local system (for example, setenv DISPLAY yoursystem:0.0).


This step can be performed when accessing the administrative workstation from a remote workstation. It is often useful to access the CCP remotely, as appropriate, or when configuring (administering) the Sun Cluster software.

If accessing clustadm remotely, you must set the DISPLAY variable before invoking the CCP.

  1. First, on your local workstation type the following (example only).

    yoursystem# /usr/openwin/bin/xhost +clustadm
  2. Next, on clustadm type the following (example only).

    clustadm# setenv DISPLAY yoursystem:0.0

Step 2.6.2—Displaying the CCP

To display the CCP, first verify that your shell environment is setup and that shell variables are set according to the environment variables listed in Appendix A. Enter the following commands in the shell window on the management server (administrative workstation).

clustadm# which ccp

clustadm# ccp nhl &

When the ccp command is executed, it will display the Cluster Control Panel window; a menu bar and icon panel will display all available tools. See the following figure.

Figure 2-1Figure 2-1 Cluster Control Panel Window

Step 2.6.3—Customizing the CCP Display

Refer to the preceding figure. Double-click the Cluster Console (console mode) icon (circled), to display the Cluster Console window, as shown in the following figure.

In this example, three windows are displayed: one small Cluster Console window, and two larger cconsole: host [name] windows. Note that each of the larger windows is associated with a specific host, or cluster node.

Figure 2-2Figure: 2-2 Cluster Console (Console Mode) and cconsole Windows


The Cluster Console utility provides a method of entering commands into multiple cluster nodes either simultaneously or individually, as required. Always be aware of which window is active before entering commands.

If a Cluster Console window does not appear for a cluster node, follow these steps to display the missing window:

  1. From the Cluster Console window (console mode), select Hosts, and click Select Hosts.

  2. Verify or insert an entry for each cluster node (for example, there should be entries for clustnode1, clustnode2).

At this time, arrange each window to your personal viewing preferences. To ungroup the Cluster Console window from the cconsole: host [name] windows, select Options from the Cluster Console window and uncheck the Group Term Windows checkbox.

For example, arrange the cconsole windows to be able to see each window clearly (and at the same time) by moving the Cluster Console window away from the other cluster node windows. This is done to ensure commands are entered correctly into one, or both nodes, as required during these exercises (and to prevent entering commands into the wrong window).

It is not necessary to do so at this time, but when you wish to close the Cluster Console window, select Exit from the Host menu on the Cluster Console window.


If you need to issue a Stop-A command to the cluster nodes to place them into the Open Boot Prom mode, position the cursor over the Cluster Console window, left mouse click, then press the ^] (Ctrl +]) keys. This will access the telnet> prompt. At the telnet> prompt, enter the send brk command into each hosts cconsole window to return to the OpenBoot PROM ok prompt.

Step 2.6.4—Configuring Each Cluster Node

Verify the CCP utility is functioning and begin the software configuration of each cluster node.

At this time, ensure that each cluster node is at the OpenBoot PROM ok prompt.


For local (manual) installations, prior to installing Solaris Operating Environment (Solaris OE) on each cluster node, we will reconfigure the Open Boot PROM settings for each cluster node. This is achieved by executing commands at the OpenBoot PROM ok prompt (the ok prompt should be viewable through the Cluster Control Panel window). We are able to do this because we have previously configured (and connected) the serial (console) port from each cluster node to the terminal concentrator (refer to Figure 1-1 in the "Guide to Installation— Hardware Setup," for cabling/connections).

Key Practice: On each node in the SunPLEX, ensure the system EEPROM has the current (for example, latest or required) OpenBoot PROM version. This could prevent undesirable anomalies (bugs) from affecting your system reliability/performance. To obtain or verify that you have the most the most current version, refer to http://sunsolve.sun.com.

Step 2.6.5—Resetting EEPROM to Factory Defaults

Prior to configuring or customizing the system EEPROM, before installing any software, and to meet cluster requirements, reset the system EEPROM to its factory default. To do this:

  1. Position the cursor into the Cluster Console window and left-click to make the window active.

  2. Enter the set-defaults command. As you enter the command, you should see the word set-defaults echoed in the cconsole window, on each cluster node.

For local (manual) installations, at this time (at each cluster node, prior to any subsequent EEPROM settings), enter the following OpenBoot PROM command (ok prompt).

ok set-defaults

Using the set-defaults command at this step establishes a consistent, known (default) state of all OpenBoot PROM variables (prior to customizing the OpenBoot PROM environment).


Resetting the system EEPROM should only be performed at this time, during the initial preparation for the Solaris OE installation. This command resets all EEPROM (OpenBoot PROM) variables to their known, factory default values. All subsequent steps assume the EEPROM has been reset at this point in the exercise. During the next few steps, the EEPROM will be modified or customized.

Ensure a consistent state on each cluster node before proceeding to configure site-specific (custom) OpenBoot PROM settings. Prior to implementing any configuration changes, and as part of initial Solaris OE installation preparations, reset the EEPROM to the factory defaults. This is done only once, and at this point in the procedure and will easily (quickly) ensure that a known and consistent state is achieved before further customization occurs.

Step 2.6.6—Documenting System Information

Execute the banner command, as follows, and document the system information, such as the system model number, OpenBoot PROM version, Ethernet address, hostid, and serial number.

ok banner

Each node will respond with configuration information.

Summary of Key Practices

On each node in the SunPLEX, ensure the system EEPROM has the current/latest OpenBoot PROM version.

Prior to customization, reset the system EEPROM to a consistent, known state (factory default).

Execute the OBP banner command, and verify (document) important system information.

End of Section 2.6

This completes this section. The CCP has been configured and verified.

  • + Share This
  • 🔖 Save To Your Account