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.
This procedure shows how to start Sun Cluster Manager on your cluster.
Determine if you intend to access Sun Cluster Manager by using the cluster node root user name and password or set up a different user name and password?
Become superuser on a cluster node.
Create a user account to access the cluster through Sun 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 Sun Cluster Manager if you do not use the root system account. Sun Cluster Manager user accounts are used only by Sun Cluster Manager. These accounts do not correspond to any 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 a Sun Cluster Management Rights Profile.
Users who do not have a user account set up on a particular node cannot access the cluster through Sun 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.
From the browser, connect to the Sun Cluster Manager port on one node of the cluster.
The default port number is 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 Sun Cluster Manager.
Click the Log In button.
The Java Web Console application launch page is displayed.
Click the Sun Cluster Manager link under the Systems category.
Accept any additional certificates that are presented by the web browser.
If you cannot connect to the Sun 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 Solaris installation, external access for the Sun Java Web Console service is restricted. This network is required to use the Sun Cluster Manager GUI.
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.
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
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.
If after performing this procedure you cannot connect to Sun 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 Sun Cluster Manager, determine if the common agent container is running by entering usr/bin/cacoadm status. If the common agent container is not running, manually start it by entering /usr/sbin/cacoadm start.