Starting the Oracle Solaris Cluster Manager Software

The Oracle Solaris Cluster Manager graphical user interface (GUI) provides an easy way to administer some aspects of the Oracle Solaris Cluster software. See the Oracle Solaris Cluster Manager online help for more information.

Both Sun Java Web Console and the common agent container are started automatically when you boot the cluster. If you need to verify that Sun Java Web Console and the common agent container are running, see the Troubleshooting section immediately following this procedure.

How to Start Oracle Solaris Cluster Manager

This procedure shows how to start Oracle Solaris Cluster Manager on your cluster.

Determine if you intend to access Oracle Solaris Cluster Manager by using the cluster node root user name and password or set up a different user name and password?
- If you will access Oracle Solaris Cluster Manager by using the cluster node root user name, go to Step 5.
- If you intend to set up a different user name and password, go to Step 3 to set up Oracle Solaris Cluster Manager user accounts.
Become superuser on a cluster node.
Create a user account to access the cluster through Oracle Solaris Cluster Manager.
You use the useradd(1M) command to add a user account to the system. You must set up at least one user account to access Oracle Solaris Cluster Manager if you do not use the root system account. Oracle Solaris Cluster Manager user accounts are used only by Oracle Solaris Cluster Manager. These accounts do not correspond to any Oracle Solaris OS system user accounts. Creating and assigning an RBAC role to a user account is described in more detail in Creating and Assigning an RBAC Role With an Oracle Solaris Cluster Management Rights Profile.

Note - Users who do not have a user account set up on a particular node cannot access the cluster through Oracle Solaris Cluster Manager from that node, nor can users manage that node through another cluster node to which the users do have access.
(Optional) Repeat Step 3 to set up additional user accounts.
From the administrative console or any other machine outside the cluster, start a browser.
Ensure that the browser's disk and memory cache sizes are set to a value that is greater than 0.
Ensure that the Java and Javascript are enables in the browser.
From the browser, connect to the Oracle Solaris Cluster Manager port on one node of the cluster.
The default port number is 6789.
```
https://node:6789/
```
Accept any certificates that are presented by the web browser.
The Java Web Console login page is displayed.
Enter the user name and password for the user you want to access Oracle Solaris Cluster Manager.
Click the Log In button.
The Java Web Console application launch page is displayed.
Click the Oracle Solaris Cluster Manager link under the Systems category.
Accept any additional certificates that are presented by the web browser.
If you cannot connect to the Oracle Solaris Cluster Manager, perform the following substeps to determine if a restricted network profile was chosen during Solaris installation and to restore external access to the Java Web Console service.
If you choose a restricted network profile during Oracle Solaris installation, external access for the Sun Java Web Console service is restricted. This network is required to use the Oracle Solaris Cluster Manager GUI.
1. Determine whether the Java Web Console service is restricted.
```
# svcprop /system/webconsole:console | grep tcp_listen
```
  If the value of the tcp_listen property is not true, the web console service is restricted.
2. Restore external access to the Java Web Console service.
```
# svccfg svc:> select system/webconsole svc:/system webconsole> setprop options/tcp_listen=true svc:/system/webconsole> quit
# /usr/sbin/smcwebserver restart
```
3. Verify that the service is available.
```
# netstat -a | grep 6789
```
  If the service is available, the command output returns an entry for 6789, which is the port number used to connect to Java Web Condole.

Troubleshooting

If after performing this procedure you cannot connect to Oracle Solaris Cluster Manager, determine if the Sun Java Web Console is running by entering /usr/sbin/smcwebserver status. If the Sun Java Web Console is not running, manually start it by entering /usr/sbin/smcwebserver start. If you still cannot connect to Oracle Solaris Cluster Manager, determine if the common agent container is running by entering usr/sbin/cacaoadm status. If the common agent container is not running, manually start it by entering /usr/sbin/cacaoadm start.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster System Administration Guide