| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.0 |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.0 |
1. Introduction to Administering Oracle Solaris Cluster
2. Oracle Solaris Cluster and RBAC
3. Shutting Down and Booting a Cluster
4. Data Replication Approaches
5. Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems
7. Administering Cluster Interconnects and Public Networks
Overview of Administering the Cluster
How to Change the Cluster Name
How to Map Node ID to Node Name
How to Work With New Cluster Node Authentication
How to Reset the Time of Day in a Cluster
SPARC: How to Display the OpenBoot PROM (OBP) on a Node
How to Change the Node Private Hostname
How to Put a Node Into Maintenance State
How to Bring a Node Out of Maintenance State
How to Uninstall Oracle Solaris Cluster Software From a Cluster Node
Troubleshooting a Node Uninstallation
Unremoved Cluster File System Entries
Unremoved Listing in Device Groups
Creating, Setting Up, and Managing the Oracle Solaris Cluster SNMP Event MIB
How to Enable an SNMP Event MIB
How to Disable an SNMP Event MIB
How to Change an SNMP Event MIB
How to Enable an SNMP Host to Receive SNMP Traps on a Node
How to Disable an SNMP Host From Receiving SNMP Traps on a Node
How to Add an SNMP User on a Node
How to Remove an SNMP User From a Node
How to Configure Load Limits on a Node
Changing Port Numbers for Services or Management Agents
How to Use the Common Agent Container to Change the Port Numbers for Services or Management Agents
Performing Zone Cluster Administrative Tasks
How to Remove a File System From a Zone Cluster
How to Remove a Storage Device From a Zone Cluster
Running an Application Outside the Global Cluster
How to Take a Solaris Volume Manager Metaset From Nodes Booted in Noncluster Mode
How to Save the Solaris Volume Manager Software Configuration
How to Purge the Corrupted Diskset
How to Recreate the Solaris Volume Manager Software Configuration
10. Configuring Control of CPU Usage
This section describes how to perform administrative tasks for the entire global cluster or zone cluster. The following table lists these administrative tasks and the associated procedures. You generally perform cluster administrative tasks in the global zone. To administer a zone cluster, at least one machine that will host the zone cluster must be up in cluster mode. All zone-cluster nodes are not required to be up and running; Oracle Solaris Cluster replays any configuration changes when the node that is currently out of the cluster rejoins the cluster.
Note - By default, power management is disabled so that it does not interfere with the cluster. If you enable power management for a single-node cluster, the cluster is still running but it can become unavailable for a few seconds. The power management feature attempts to shut down the node, but it does not succeed.
In this chapter, phys-schost# reflects a global-cluster prompt. The clzonecluster interactive shell prompt is clzc:schost>.
Table 9-1 Task List: Administering the Cluster
|
If necessary, you can change the cluster name after initial installation.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost# clsetup
The Main Menu is displayed.
The Other Cluster Properties menu is displayed.
To delete the Oracle Solaris Cluster service tag instance, complete the following substeps on all nodes in the cluster.
phys-schost# stclient -x
phys-schost# stclient -d -i service_tag_instance_number
phys-schost# reboot
Example 9-1 Changing the Cluster Name
The following example shows the cluster command generated from the clsetup utility to change to the new cluster name, dromedary.
phys-schost# cluster rename -c dromedary
For more information, see the cluster(1CL) and clsetup(1CL) man pages.
During Oracle Solaris Cluster installation, each node is automatically assigned a unique node ID number. The node ID number is assigned to a node in the order in which it joins the cluster for the first time. After the node ID number is assigned, the number cannot be changed. The node ID number is often used in error messages to identify which cluster node the message concerns. Use this procedure to determine the mapping between node IDs and node names.
You do not need to be superuser to list configuration information for a global cluster or a zone cluster. One step in this procedure is performed from a node of the global cluster. The other step is performed from a zone-cluster node.
phys-schost# clnode show | grep Node
For more information, see the clnode(1CL) man page.
The zone-cluster node has the same Node ID as the global cluster-node where it is running.
phys-schost# zlogin sczone clnode -v | grep Node
Example 9-2 Mapping the Node ID to the Node Name
The following example shows the node ID assignments for a global cluster.
phys-schost# clnode show | grep Node === Cluster Nodes === Node Name: phys-schost1 Node ID: 1 Node Name: phys-schost2 Node ID: 2 Node Name: phys-schost3 Node ID: 3
Oracle Solaris Cluster enables you to determine if new nodes can add themselves to the global cluster and the type of authentication to use. You can permit any new node to join the cluster over the public network, deny new nodes from joining the cluster, or indicate a specific node that can join the cluster. New nodes can be authenticated by using either standard UNIX or Diffie-Hellman (DES) authentication. If you select DES authentication, you must also configure all necessary encryption keys before a node can join. See the keyserv(1M) and publickey(4) man pages for more information.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost# clsetup
The Main Menu is displayed.
The New Nodes menu is displayed.
Example 9-3 Preventing a New Machine From Being Added to the Global Cluster
The clsetup utility generates the claccess command. The following example shows the claccess command that prevents new machines from being added to the cluster.
phys-schost# claccess deny -h hostname
Example 9-4 Permitting All New Machines to Be Added to the Global Cluster
The clsetup utility generates the claccess command. The following example shows the claccess command that enables all new machines to be added to the cluster.
phys-schost# claccess allow-all
Example 9-5 Specifying a New Machine to Be Added to the Global Cluster
The clsetup utility generates the claccess command. The following example shows the claccess command that enables a single new machine to be added to the cluster.
phys-schost# claccess allow -h hostname
Example 9-6 Setting the Authentication to Standard UNIX
The clsetup utility generates the claccess command. The following example shows the claccess command that resets to standard UNIX authentication for new nodes that are joining the cluster.
phys-schost# claccess set -p protocol=sys
Example 9-7 Setting the Authentication to DES
The clsetup utility generates the claccess command. The following example shows the claccess command that uses DES authentication for new nodes that are joining the cluster.
phys-schost# claccess set -p protocol=des
When using DES authentication, you must also configure all necessary encryption keys before a node can join the cluster. For more information, see the keyserv(1M) and publickey(4) man pages.
Oracle Solaris Cluster software uses the NTP to maintain time synchronization between cluster nodes. Adjustments in the global cluster occur automatically as needed when nodes synchronize their time. For more information, see the Oracle Solaris Cluster Concepts Guide and the Network Time Protocol's User's Guide at http://download.oracle.com/docs/cd/E19065-01/servers.10k/.
 | Caution - When using NTP, do not attempt to adjust the cluster time while the cluster is up and running. Do not adjust the time by using the date, rdate, or svcadm commands interactively or within the cron scripts. For more information, see the date(1), rdate(1M), svcadm(1M), or cron(1M) man pages. The ntpd(1M) man page is delivered in the service/network/ntp Oracle Solaris 11 package. |
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost# cluster shutdown -g0 -y -i 0
On SPARC based systems, run the following command.
ok boot -x
On x86 based systems, run the following commands.
# shutdown -g -y -i0 Press any key to continue
The GRUB menu appears.
For more information about GRUB based booting, see Booting an x86 Based System Interactively in Booting and Shutting Down Oracle Solaris on x86 Platforms.
The GRUB boot parameters screen appears.
[ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ESC at any time exits. ] grub edit> kernel$ /platform/i86pc/kernel/$ISADIR/unix _B $ZFS-BOOTFS -x
The screen displays the edited command.
Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps again to add the -x option to the kernel boot parameter command.
phys-schost# date HHMM.SS
phys-schost# rdate hostname
phys-schost# reboot
On each node, run the date command.
phys-schost# date
Use this procedure if you need to configure or change OpenBoot™ PROM settings.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
# telnet tc_name tc_port_number
Specifies the name of the terminal concentrator.
Specifies the port number on the terminal concentrator. Port numbers are configuration dependent. Typically, ports 2 and 3 (5002 and 5003) are used for the first cluster installed at a site.
The clnode evacuate command switches over all device groups from the specified node to the next-preferred node. The command also switches all resource groups from the global cluster's specified voting node to the next-preferred voting node.
phys-schost# clnode evacuate node # shutdown -g0 -y
| Caution - Do not use send brk on a cluster console to shut down a cluster node. |
Use this procedure to change the private hostname of a cluster node after installation has been completed.
Default private host names are assigned during initial cluster installation. The default private hostname takes the form clusternode< nodeid>-priv, for example: clusternode3-priv. Change a private hostname only if the name is already in use in the domain.
| Caution - Do not attempt to assign IP addresses to new private host names. The clustering software assigns them. |
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost# clresource disable resource[,...]
Include the following in the applications you disable.
HA-DNS and HA-NFS services, if configured
Any application that has been custom-configured to use the private hostname
Any application that is being used by clients over the private interconnect
For information about using the clresource command, see the clresource(1CL) man page and the Oracle Solaris Cluster Data Services Planning and Administration Guide.
Use the svcadm command to shut down the NTP daemon. See the svcadm(1M) man page for more information about the NTP daemon.
phys-schost# svcadm disable ntp
Run the utility from only one of the nodes in the cluster. for more information, see the clsetup(1CL) man page.
Note - When selecting a new private hostname, ensure that the name is unique to the cluster node.
You can also run the clnode command instead of the clsetup utility to change the private hostname. In the example below, the cluster node name is pred1. After you run the clnode command below, go to Step 6.
phys-schost# /usr/cluster/bin/clnode set -p privatehostname=New-private-nodename pred1
Answer the questions when prompted. You are asked the name of the node whose private hostname you are changing (clusternode< nodeid>-priv), and the new private hostname.
Perform this step on each node in the cluster. Flushing prevents the cluster applications and data services from trying to access the old private hostname.
phys-schost# nscd -i hosts
If you perform this step at installation, also remember to remove names for nodes that are configured. Typically, the ntp.conf.sc file is identical on each cluster node.
Perform this step on each node of the cluster.
Use the svcadm command to restart the NTP daemon.
# svcadm enable svc:network/ntp:default
phys-schost# clresource enable resource[,...]
For information about using the clresourcecommand, see the clresource(1CL) man page and the Oracle Solaris Cluster Data Services Planning and Administration Guide.
Example 9-8 Changing the Private Hostname
The following example changes the private hostname from clusternode2-priv to clusternode4-priv, on node phys-schost-2. Perform this action on each node.
[Disable all applications and data services as necessary.] phys-schost-1# svcadm disable ntp phys-schost-1# clnode show | grep node ... private hostname: clusternode1-priv private hostname: clusternode2-priv private hostname: clusternode3-priv ... phys-schost-1# clsetup phys-schost-1# nscd -i hosts phys-schost-1# vi /etc/inet/ntp.conf.sc ... peer clusternode1-priv peer clusternode4-priv peer clusternode3-priv phys-schost-1# ping clusternode4-priv phys-schost-1# svcadm enable ntp [Enable all applications and data services disabled at the beginning of the procedure.]
You can change the name of a node that is part of an Oracle Solaris Cluster configuration. You must rename the Oracle Solaris hostname before you can rename the node. Use the clnode rename command to rename the node.
The following instructions apply to any application that is running in a global cluster.
For more information on Geographic Edition clusters and nodes, see Chapter 5, Administering Cluster Partnerships, in Oracle Solaris Cluster Geographic Edition System Administration Guide.
If the cluster where you are performing the rename procedure is primary for the protection group, and you want to have the application in the protection group online, you can switch the protection group to the secondary cluster during the rename procedure.
Instead, perform a cluster shutdown after you complete these steps.
ok> boot -x
Rename one node at a time.
# clnode rename -n newnodename oldnodename
# sync;sync;sync;reboot
# clnode status -v
You must update the protection group from one node of the partner cluster that contains the renamed node by using the geopg update <pg>. After you complete that step, run the geopg start -e global <pg> command. At a later time, you can switch the protection group back to the cluster with the renamed node.
See How to Change the Logical Hostnames Used by Existing Oracle Solaris Cluster Logical Hostname Resources for instructions on this optional step.
You can choose to change the logical hostname resource's hostnamelist property either before or after you rename the node by following the steps in How to Rename a Node. This step is optional.
The following steps show how to configure the apache-lh-res resource to work with the new logical hostname, and must be executed in cluster mode.
# clrg offline apache-rg
# clrs disable appache-lh-res
# clrs set -p HostnameList=test-2 apache-lh-res
# clrs enable apache-lh-res
# clrg online -emM apache-rg
# clrs status apache-rs
Put a global-cluster node into maintenance state when taking the node out of service for an extended period of time. This way, the node does not contribute to the quorum count while it is being serviced. To put a node into maintenance state, the node must be shut down with the clnode evacuate and cluster shutdown commands. For more information, see the clnode(1CL) and cluster(1CL) man pages.
Note - Use the Oracle Solaris shutdown command to shut down a single node. Use the cluster shutdown command only when shutting down an entire cluster.
When a cluster node is shut down and put in maintenance state, all quorum devices that are configured with ports to the node have their quorum vote counts decremented by one. The node and quorum device vote counts are incremented by one when the node is removed from maintenance mode and brought back online.
Use the clquorum disable command to put a cluster node into maintenance state. For more information, see the clquorum(1CL) man page.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
The clnode evacuate command switches over all resource groups and device groups.
phys-schost# clnode evacuate node
phys-schost# shutdown -g0 -y -i 0
phys-schost# clquorum disable node
Specifies the name of a node that you want to put into maintenance mode.
phys-schost# clquorum status node
The node that you put into maintenance state should have a Status of offline and 0 (zero) for Present and Possible quorum votes.
Example 9-9 Putting a Global-Cluster Node Into Maintenance State
The following example puts a cluster node into maintenance state and verifies the results. The clnode status output shows the Node votes for phys-schost-1 to be 0 (zero) and the status to be Offline. The Quorum Summary should also show reduced vote counts. Depending on your configuration, the Quorum Votes by Device output might indicate that some quorum disk devices are offline as well.
[On the node to be put into maintenance state:] phys-schost-1# clnode evacuate phys-schost-1 phys-schost-1# shutdown -g0 -y -i0 [On another node in the cluster:] phys-schost-2# clquorum disable phys-schost-1 phys-schost-2# clquorum status phys-schost-1 -- Quorum Votes by Node -- Node Name Present Possible Status --------- ------- -------- ------ phys-schost-1 0 0 Offline phys-schost-2 1 1 Online phys-schost-3 1 1 Online
See Also
To bring a node back online, see How to Bring a Node Out of Maintenance State.
Use the following procedure to bring a global-cluster node back online and reset the quorum vote count to the default. For cluster nodes, the default quorum count is one. For quorum devices, the default quorum count is N-1, where N is the number of nodes with nonzero vote counts that have ports to the quorum device.
When a node has been put in maintenance state, the node's quorum vote count is decremented by one. All quorum devices that are configured with ports to the node will also have their quorum vote counts decremented. When the quorum vote count is reset and a node removed from maintenance state, both the node's quorum vote count and the quorum device vote count are incremented by one.
Run this procedure any time a global-cluster node has been put in maintenance state and you are removing it from maintenance state.
| Caution - If you do not specify either the globaldev or node options, the quorum count is reset for the entire cluster. |
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
You must reset the quorum count from a node other than the node in maintenance state before rebooting the node, or the node might hang while waiting for quorum.
phys-schost# clquorum reset
The change flag that resets quorum.
phys-schost# clquorum status
The node that you removed from maintenance state should have a status of online and show the appropriate vote count for Present and Possible quorum votes.
Example 9-10 Removing a Cluster Node From Maintenance State and Resetting the Quorum Vote Count
The following example resets the quorum count for a cluster node and its quorum devices to their defaults and verifies the result. The cluster status output shows the Node votes for phys-schost-1 to be 1 and the status to be online. The Quorum Summary should also show an increase in vote counts.
phys-schost-2# clquorum reset
On SPARC based systems, run the following command.
ok boot
On x86 based systems, run the following commands.
When the GRUB menu is displayed, select the appropriate Oracle Solaris entry and press Enter.
phys-schost-1# clquorum status
--- Quorum Votes Summary ---
Needed Present Possible
------ ------- --------
4 6 6
--- Quorum Votes by Node ---
Node Name Present Possible Status
--------- ------- -------- ------
phys-schost-2 1 1 Online
phys-schost-3 1 1 Online
--- Quorum Votes by Device ---
Device Name Present Possible Status
----------- ------- -------- ------
/dev/did/rdsk/d3s2 1 1 Online
/dev/did/rdsk/d17s2 0 1 Online
/dev/did/rdsk/d31s2 1 1 Online
`
Perform this procedure to unconfigure Oracle Solaris Cluster software from a global-cluster node before you disconnect it from a fully established cluster configuration. You can use this procedure to uninstall software from the last remaining node of a cluster.
Note - To uninstall Oracle Solaris Cluster software from a node that has not yet joined the cluster or is still in installation mode, do not perform this procedure. Instead, go to How to Unconfigure Oracle Solaris Cluster Software to Correct Installation Problems in Oracle Solaris Cluster Software Installation Guide.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
See Table 8-2.
Ensure that you have removed the node from the cluster configuration by using clnode remove before you continue with this procedure. Other steps might include adding the node you plan to uninstall to the cluster's node–authentication list, uninstalling a zone cluster, and so on.
Note - To unconfigure the node but leave Oracle Solaris Cluster software installed on the node, do not proceed further after you run the clnode remove command.
On a SPARC based system, run the following command.
# shutdown -g0 -y -i0 ok boot -x
On an x86 based system, run the following commands.
# shutdown -g0 -y -i0
...
<<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:
Type b [file-name] [boot-flags] <ENTER> to boot with options
or i <ENTER> to enter boot interpreter
or <ENTER> to boot with defaults
<<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -xok boot -x
For more information about GRUB based booting, see Booting an x86 Based System to a Specified State (Task Map) in Booting and Shutting Down Oracle Solaris on x86 Platforms.
The screen displays the edited command.
Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps to again add the -x option to the kernel boot parameter command.
phys-schost# cd /
phys-schost# scinstall -r [-b bename]
Removes cluster configuration information and uninstalls Oracle Solaris Cluster framework and data-service software from the cluster node. You can then reinstall the node or remove the node from the cluster.
Specifies the name of a new boot environment, which is where you boot into after the uninstall process completes. Specifying a name is optional. If you do not specify a name for the boot environment, one is automatically generated.
See the scinstall(1M) man page for more information.
If the uninstalled node is connected to a storage device that uses Fibre Channel interfaces, no termination is necessary.
Tip - For more information about migrating a global-devices namespace to a lofi, see Migrating the Global-Devices Namespace.
This section describes error messages that you might receive when you run the clnode remove command and the corrective actions to take.
The following error messages indicate that the global-cluster node you removed still has cluster file systems referenced in its vfstab file.
Verifying that no unexpected global mounts remain in /etc/vfstab ... failed clnode: global-mount1 is still configured as a global mount. clnode: global-mount1 is still configured as a global mount. clnode: /global/dg1 is still configured as a global mount. clnode: It is not safe to uninstall with these outstanding errors. clnode: Refer to the documentation for complete uninstall instructions. clnode: Uninstall failed.
To correct this error, return to How to Uninstall Oracle Solaris Cluster Software From a Cluster Node and repeat the procedure. Ensure that you successfully complete Step 4 in the procedure before you rerun the clnode remove command.
The following error messages indicate that the node you removed is still listed with a device group.
Verifying that no device services still reference this node ... failed clnode: This node is still configured to host device service " service". clnode: This node is still configured to host device service " service2". clnode: This node is still configured to host device service " service3". clnode: This node is still configured to host device service " dg1". clnode: It is not safe to uninstall with these outstanding errors. clnode: Refer to the documentation for complete uninstall instructions. clnode: Uninstall failed.
This section describes how to create, set up, and manage the Simple Network Management Protocol (SNMP) event Management Information Base (MIB). This section also describes how to enable, disable, and change the Oracle Solaris Cluster SNMP event MIB.
The Oracle Solaris Cluster software currently supports one MIB, the event MIB. The SNMP manager software traps cluster events in real time. When enabled, the SNMP manager automatically sends trap notifications to all hosts that are defined by the clsnmphost command. The MIB maintains a read-only table of the most current 50 events. Because clusters generate numerous notifications, only events with a severity of warning or greater are sent as trap notifications. This information does not persist across reboots.
The SNMP event MIB is defined in the sun-cluster-event-mib.mib file and is located in the /usr/cluster/lib/mib directory. You can use this definition to interpret the SNMP trap information.
The default port number for the event SNMP module is 11161, and the default port for the SNMP traps is 11162. These port numbers can be changed by modifying the Common Agent Container property file, which is /etc/cacao/instances/default/private/cacao.properties.
Creating, setting up, and managing an Oracle Solaris Cluster SNMP event MIB can involve the following tasks.
Table 9-2 Task Map: Creating, Setting Up, and Managing the Oracle Solaris Cluster SNMP Event MIB
|
This procedure shows how to enable an SNMP event MIB.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmpmib enable [-n node] MIB
Specifies the node on which the event MIB that you want to enable is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.
Specifies the name of the MIB that you want to enable. In this case, the MIB name must be event.
This procedure shows how to disable an SNMP event MIB.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmpmib disable -n node MIB
Specifies the node on which the event MIB that you want to disable is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.
Specifies the type of the MIB that you want to disable. In this case, you must specify event.
This procedure shows how to change the protocol for an SNMP event MIB.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmpmib set -n node -p version=value MIB
Specifies the node on which the event MIB that you want to change is located. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.
Specifies the version of SNMP protocol to use with the MIBs. You specify value as follows:
version=SNMPv2
version=snmpv2
version=2
version=SNMPv3
version=snmpv3
version=3
Specifies the name of the MIB or MIBs to which to apply the subcommand. In this case, you must specify event.
This procedure shows how to add an SNMP host on a node to the list of hosts that will receive trap notifications for the MIBs.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmphost add -c SNMPcommunity [-n node] host
Specifies the SNMP community name that is used in conjunction with the hostname.
You must specify the SNMP community name SNMPcommunity when you add a host to a community other than public. If you use the add subcommand without the -c option, the subcommand uses public as the default community name.
If the specified community name does not exist, this command creates the community.
Specifies the name of the node of the SNMP host that is provided access to the SNMP MIBs in the cluster. You can specify a node name or a node ID. If you do not specify this option, the current node is used by default.
Specifies the name, IP address, or IPv6 address of a host that is provided access to the SNMP MIBs in the cluster.
This procedure shows how to remove an SNMP host on a node from the list of hosts that will receive trap notifications for the MIBs.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmphost remove -c SNMPcommunity -n node host
Removes the specified SNMP host from the specified node.
Specifies the name of the SNMP community from which the SNMP host is removed.
Specifies the name of the node on which the SNMP host is removed from the configuration. You can specify a node name or a node ID. If you do not specify this option, the current node is used by default.
Specifies the name, IP address, or IPv6 address of the host that is removed from the configuration.
To remove all hosts in the specified SNMP community, use a plus sign (+) for host with the -c option. To remove all hosts, use the plus sign (+) for host.
This procedure shows how to add an SNMP user to the SNMP user configuration on a node.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmpuser create -n node -a authentication \ -f password user
Specifies the node on which the SNMP user is added. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.
Specifies the authentication protocol that is used to authorize the user. The value of the authentication protocol can be SHA or MD5.
Specifies a file that contains the SNMP user passwords. If you do not specify this option when you create a new user, the command prompts for a password. This option is valid only with the add subcommand.
You must specify user passwords on separate lines in the following format:
user:password
Passwords cannot contain the following characters or a space:
; (semicolon)
: (colon)
\ (backslash)
\n (newline)
Specifies the name of the SNMP user that you want to add.
This procedure shows how to remove an SNMP user from the SNMP user configuration on a node.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.
phys-schost-1# clsnmpuser delete -n node user
Specifies the node from which the SNMP user is removed. You can specify a node ID or a node name. If you do not specify this option, the current node is used by default.
Specifies the name of the SNMP user that you want to remove.
You can enable the automatic distribution of resource group load across nodes by setting load limits. You can configure a set of load limits for each cluster node. You assign load factors to resource groups, and the load factors correspond to the defined load limits of the nodes. The default behavior is to distribute resource group load evenly across all the available nodes in the resource group's node list.
The resource groups are started on a node from the resource group's node list by the RGM so that the node's load limits are not exceeded. As resource groups are assigned to nodes by the RGM, the resource groups' load factors on each node are summed up to provide a total load. The total load is then compared against that node's load limits.
A load limit consists of the following items:
A user-assigned name.
A soft limit value – You can temporarily exceed a soft load limit.
A hard limit value – Hard load limits can never be exceeded and are strictly enforced.
You can set both the hard limit and the soft limit in a single command. If one of the limits is not explicitly set, the default value is used. Hard and soft load limits for each node are created and modified with the clnode create-loadlimit, clnode set-loadlimit, and clnode delete-loadlimit commands. See the clnode(1CL) man page for more information.
You can configure a resource group to have a higher priority so that it is less likely to be displaced from a specific node. You can also set a preemption_mode property to determine if a resource group will be preempted from a node by a higher-priority resource group because of node overload. A concentrate_load property also allows you to concentrate the resource group load onto as few nodes as possible. The default value of the concentrate_load property is FALSE by default.
Note - You can configure load limits on nodes in a global cluster or a zone cluster. You can use the command line, the clsetup utility, or the Oracle Solaris Cluster Manager interface to configure load limits. The following procedure illustrates how to configure load limits using the command line.
# clnode create-loadlimit -p limitname=mem_load -Z zc1 -p softlimit=11 -p hardlimit=20 node1 node2 node3
In this example, the zone cluster name is zc1 The sample property is called mem_load and has a soft limit of 11 and a hard load limit of 20. Hard and soft limits are optional arguments and default to unlimited if you do not specifically define them. See the clnode(1CL) man page for more information.
# clresourcegroup set -p load_factors=mem_load@50,factor2@1 rg1 rg2
In this example, the load factors are set on the two resource groups, rg1 and rg2. The load factor settings correspond to the defined load limits of the nodes. You can also perform this step during the creation of the resource group with the clresourceroup create command. See the clresourcegroup(1CL) man page for more information.
# clresourcegroup remaster rg1 rg2
This command can move resource groups off their current master to other nodes to achieve uniform load distribution.
# clresourcegroup set -p priority=600 rg1
The default priority is 500. Resource groups with higher priority values get precedence in node assignment over resource groups with lower priorities.
# clresourcegroup set -p Preemption_mode=No_cost rg1
See the clresourcegroup(1CL) man page for more information on the HAS_COST, NO_COST, and NEVER options.
# cluster set -p Concentrate_load=TRUE
A strong positive or negative affinity takes precedence over load distribution. A strong affinity can never be violated, nor can a hard load limit. If you set both strong affinities and hard load limits, some resource groups might be forced to remain offline if both constraints cannot be satisfied.
The following example specifies a strong positive affinity between resource group rg1 in zone cluster zc1 and resource group rg2 in zone cluster zc2.
# clresourcegroup set -p RG_affinities=++zc2:rg2 zc1:rg1
# clnode status -Z all -v
The output includes any load limit settings that are defined on the node.
The common agent container is started automatically when you boot the cluster.
Note - If you receive a System Error message when you try to view information about a node, 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
If the default port numbers for your common agent container services conflict with other running processes, you can use the cacaoadm command to change the port number of the conflicting service or management agent on each node of the cluster.
# /opt/bin/cacaoadm stop
# /opt/bin/cacaoadm get-param parameterName
You can use the cacaoadm command to change the port numbers for the following common agent container services. The following list provides some examples of services and agents that can be managed by the common agent container, along with corresponding parameter names.
jmxmp-connector-port
snmp-adapter-port
snmp-adapter-trap-port
commandstream-adapter-port
Note - If you receive a System Error message when you try to view information about a node, 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
# /opt/bin/cacaoadm set-param parameterName=parameterValue
# /opt/bin/cacaoadm start
|