|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster|
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.
This procedure shows how to start Oracle Solaris Cluster Manager on your cluster.
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.
The default port number is 6789.
The Java Web Console login page is displayed.
The Java Web Console application launch page is displayed.
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.
# svcprop /system/webconsole:console | grep tcp_listen
If the value of the tcp_listen property is not true, the web console service is restricted.
# svccfg svc:> select system/webconsole svc:/system webconsole> setprop options/tcp_listen=true svc:/system/webconsole> quit # /usr/sbin/smcwebserver restart
# 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 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.
If you receive a System Error message when you try to view information about a node other than the node running the GUI, check whether the common agent container network-bind-address parameter is set to the correct value of 0.0.0.0.
Perform these steps on each node of the cluster.
1. Display the value of the network-bind-address parameter.
# cacaoadm get-param network-bind-address network-bind-address=0.0.0.0
2. If the parameter value is anything other than 0.0.0.0, change the parameter value.
# cacaoadm stop # cacaoadm set-param network-bind-address=0.0.0.0 # cacaoadm start