This chapter provides administrative procedures that affect an entire global cluster or a zone cluster:
For information about adding or removing a node from the cluster, see Chapter 8, Adding and Removing a Node.
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. For Solaris 10 OS, 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; Sun Cluster replays any configuration changes when the node that is currently out of the cluster rejoins the cluster.
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
Task |
Instructions |
---|---|
Add or remove a node from a cluster | |
Change the name of the cluster | |
List node IDs and their corresponding node names | |
Permit or deny new nodes to add themselves to the cluster | |
Change the time for a cluster by using the Network Time Protocol (NTP) | |
Shut down a node to the OpenBoot PROM ok prompt on a SPARC based system or to the Press any key to continue message in a GRUB menu on an x86 based system | |
Add or change the private hostname |
How to Add a Private Hostname for a Non-Voting Node on a Global Cluster |
Put a cluster node in maintenance state | |
Bring a cluster node out of maintenance state | |
Move a zone cluster; prepare a zone cluster for applications, remove a zone cluster | |
Uninstall Sun Cluster software from a node | |
Add and manage an SNMP Event MIB |
How to Enable an SNMP Event MIB How to Add an SNMP User on a Node
|
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser on any node in the global cluster.
Start the clsetup utility.
phys-schost# clsetup |
The Main Menu is displayed.
To change the cluster name, type the number that corresponds to the option for Other Cluster Properties.
The Other Cluster Properties menu is displayed.
Make your selection from the menu and follow the onscreen instructions.
If you want the service tag for Sun Cluster to reflect the new cluster name, delete the existing Sun Cluster tag and restart the cluster. To delete the Sun Cluster service tag instance, complete the following substeps on all nodes in the cluster.
The following example shows the cluster(1CL) command generated from the clsetup(1CL) utility to change to the new cluster name, dromedary.
phys-schost# cluster -c dromedary |
During Sun 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.
Use the clnode(1CL) command to list the cluster configuration information for the global cluster.
phys-schost# clnode show | grep Node |
You can also list the Node IDs for a zone cluster. 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 |
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 |
Sun 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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser on any node in the global cluster.
Start the clsetup(1CL) utility.
phys-schost# clsetup |
The Main Menu is displayed.
To work with cluster authentication, type the number that corresponds to the option for new nodes.
The New Nodes menu is displayed.
Make your selection from the menu and follow the onscreen instructions.
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 |
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 |
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 |
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 |
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.
Sun Cluster software uses the Network Time Protocol (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 Sun Cluster Concepts Guide for Solaris OS and the Network Time Protocol User's Guide.
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(1), rdate(1M), xntpd(1M), or svcadm(1M) commands interactively or within cron(1M) scripts.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser on any node in the global cluster.
Shut down the global cluster.
phys-schost# cluster shutdown -g0 -y -i 0 |
Verify that the node is showing the ok prompt on a SPARC based system or the Press any key to continue message on the GRUB menu on an x86 based system.
Boot the node in noncluster mode.
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 |
In the GRUB menu, use the arrow keys to select the appropriate Solaris entry and type e to edit its commands.
The GRUB menu appears similar to the following:
GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------------+ | Solaris 10 /sol_10_x86 | | Solaris failsafe | | | +-------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. |
For more information about GRUB based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.
In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
The GRUB boot parameters screen appears similar to the following:
GNU GRUB version 0.95 (615K lower / 2095552K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot | | module /platform/i86pc/boot_archive | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu. |
Add -x to the command to specify system boot into noncluster mode.
[ 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/multiboot -x |
Press the Enter key to accept the change and return to the boot parameters screen.
The screen displays the edited command.
GNU GRUB version 0.95 (615K lower / 2095552K upper memory) +----------------------------------------------------------------------+ | root (hd0,0,a) | | kernel /platform/i86pc/multiboot -x | | module /platform/i86pc/boot_archive | +----------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press 'b' to boot, 'e' to edit the selected command in the boot sequence, 'c' for a command-line, 'o' to open a new line after ('O' for before) the selected line, 'd' to remove the selected line, or escape to go back to the main menu.- |
Type b to boot the node into noncluster mode.
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.
On a single node, set the time of day by running the date command.
phys-schost# date HHMM.SS |
On the other machines, synchronize the time to that node by running the rdate(1M) command.
phys-schost# rdate hostname |
Boot each node to restart the cluster.
phys-schost# reboot |
Verify that the change occurred on all cluster nodes.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Connect to the console on the node to be shut down.
# 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.
Shut down the cluster node gracefully by using the clnode evacuate command, then the shutdown command. 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 or non-voting node to the next-preferred voting or non-voting node.
phys-schost# clnode evacuate node # shutdown -g0 -y |
Do not use send brk on a cluster console to shut down a cluster node.
Execute the OBP commands.
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.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Disable, on all nodes in the cluster, any data service resources or other applications that might cache private host names.
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 Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
If your NTP configuration file refers to the private hostname that you are changing, bring down the Network Time Protocol (NTP) daemon on each node of the cluster.
SPARC: If you are using Solaris 9 OS, use the xntpd command to shut down the Network Time Protocol (NTP) daemon. See the xntpd(1M) man page for more information about the NTP daemon.
phys-schost# /etc/init.d/xntpd.cluster stop |
If you are using Solaris 10 OS, use the svcadm command to shut down the Network Time Protocol (NTP) daemon. See the svcadm(1M) man page for more information about the NTP daemon.
phys-schost# svcadm disable ntp |
Run the clsetup(1CL) utility to change the private hostname of the appropriate node.
Run the utility from only one of the nodes in the cluster.
When selecting a new private hostname, ensure that the name is unique to the cluster node.
Type the number that corresponds to the option for the private hostname.
Type the number that corresponds to the option for changing a private hostname.
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.
Flush the name service cache.
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 changed a private hostname in your NTP configuration file, update your NTP configuration file (ntp.conf or ntp.conf.cluster) on each node.
Use the editing tool of your choice.
If you perform this step at installation, also remember to remove names for nodes that are configured. The default template is preconfigured with 16 nodes. Typically, the ntp.conf.cluster file is identical on each cluster node.
Verify that you can successfully ping the new private hostname from all cluster nodes.
Restart the NTP daemon.
Perform this step on each node of the cluster.
SPARC: If you are using Solaris 9 OS, use the xntpd command to restart the NTP daemon.
If you are using the ntp.conf.cluster file, type the following:
# /etc/init.d/xntpd.cluster start |
If you are using the ntp.conf file, type the following:
# /etc/init.d/xntpd start |
If you are using Solaris 10 OS, use the svcadm command to restart the NTP daemon.
# svcadm enable ntp |
Enable all data service resources and other applications that were disabled in Step 1.
phys-schost# clresource disable resource[,...] |
For information about using the scswitch command, see the clresource(1CL) man page and the Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
The following example changes the private hostname from clusternode2-priv to clusternode4-priv, on node phys-schost-2 .
[Disable all applications and data services as necessary.] phys-schost-1# /etc/init.d/xntpd stop 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 ... peer clusternode1-priv peer clusternode4-priv peer clusternode3-priv phys-schost-1# ping clusternode4-priv phys-schost-1# /etc/init.d/xntpd start [Enable all applications and data services disabled at the beginning of the procedure.] |
Use this procedure to add a private hostname for a non-voting node on a global cluster after installation has been completed. In the procedures in this chapter, phys-schost# reflects a global-cluster prompt. Perform this procedure only on a global cluster.
Run the clsetup(1CL) utility to add a private hostname on the appropriate zone.
phys-schost# clsetup |
Type the number that corresponds to the option for private host names and press the Return key.
Type the number that corresponds to the option for adding a zone private hostname and press the Return key.
Answer the questions when prompted. There is no default for a global-cluster non-voting node private hostname. You will need to provide a hostname.
Use this procedure to change the private hostname of a non-voting node after installation has been completed.
Private host names are assigned during initial cluster installation. The 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.
Do not attempt to assign IP addresses to new private hostnames. 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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
On all nodes in the global cluster, disable any data service resources or other applications that might cache private host names.
phys-schost# clresource disable resource1, resource2 |
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 Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Run the clsetup(1CL) utility to change the private hostname of the appropriate non-voting node on the global cluster.
phys-schost# clsetup |
You need to perform this step only from one of the nodes in the cluster.
When selecting a new private hostname, ensure that the name is unique to the cluster.
Type the number that corresponds to the option for private hostnames and press the Return key.
Type the number that corresponds to the option for adding a zone private hostname and press the Return key.
No default exists for a non-voting node of a global cluster's private hostname. You need to provide a hostname.
Type the number that corresponds to the option for changing a zone private hostname.
Answer the questions when prompted. You are asked for the name of the non-voting node whose private hostname is being changed (clusternode< nodeid>-priv), and the new private hostname.
Flush the name service cache.
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 |
Enable all data service resources and other applications that were disabled in Step 1.
Use this procedure to delete a private hostname for a non-voting node on a global cluster. Perform this procedure only on a global cluster.
Run the clsetup(1CL) utility to delete a private hostname on the appropriate zone.
Type the number that corresponds to the option for zone private hostname.
Type the number that corresponds to the option for deleting a zone private hostname.
Type the name of the non-voting node's private hostname that you are deleting.
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 clnode(1CL) evacuate and cluster(1CL) shutdown commands.
Use the 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(1CL) disable command to put a cluster node into maintenance state.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization on the global-cluster node that you are putting into maintenance state.
Evacuate any resource groups and device groups from the node. The clnode evacuate command switches over all resource groups and device groups, including all non-voting nodes from the specified node to the next-preferred node.
phys-schost# clnode evacuate node |
Shut down the node that you evacuated.
phys-schost# shutdown -g0 -y-i 0 |
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization on another node in the cluster and put the node that you shut down in Step 3 in maintenance state.
phys-schost# clquorum disable node |
Specifies the name of a node that you want to put into maintenance mode.
Verify that the global-cluster node is now in maintenance state.
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.
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 |
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.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization on any node of the global cluster other than the one in maintenance state.
Depending on the number of nodes that you have in your global cluster configuration, perform one of the following steps:
If the node that you are removing from maintenance state will have quorum devices, reset the cluster quorum count from a node other than the one in maintenance state.
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.
Boot the node that you are removing from maintenance state.
Verify the quorum vote count.
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.
The following example resets the quorum count for a cluster node and its quorum devices to their defaults and verifies the result. The scstat -q 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 Solaris entry and press Enter. The GRUB menu appears similar to the following:
GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------------+ | Solaris 10 /sol_10_x86 | | Solaris failsafe | | | +-------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. |
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 ` |
You can perform other administrative tasks on a zone cluster, such as moving the zone path, preparing a zone cluster to run applications, and cloning a zone cluster. All of these commands must be performed from the voting node of the global cluster.
The Sun Cluster commands that you run only from the voting node in the global cluster are not valid for use with zone clusters. See the appropriate Sun Cluster man page for information about the valid use of a command in zones.
Task |
Instructions |
---|---|
Move the zone path to a new zone path |
clzonecluster move -f zonepath zoneclustername |
Prepare the zone cluster to run applications |
clzonecluster ready -n nodename zoneclustername |
Clone a zone cluster |
clzonecluster clone -Z source- zoneclustername [-m copymethod] zoneclustername Halt the source zone cluster before you use the clone subcommand. The target zone cluster must already be configured. |
Remove a zone cluster | |
Remove a file system from a zone cluster | |
Remove a storage device from a zone cluster | |
Troubleshoot a node uninstallation | |
Create, set up, and manage the Sun Cluster SNMP Event MIB |
Creating, Setting Up, and Managing the Sun Cluster SNMP Event MIBCreating, Setting Up, and Managing the Sun Cluster SNMP Event MIB |
You can delete a specific zone cluster or use a wildcard to remove all zone clusters that are configured on the global cluster. The zone cluster must be configured before you remove it.
Become a superuser or assume a role that provides solaris.cluster.modify RBAC authorization on the node of the global cluster. Perform all steps in this procedure from a node of the global cluster.
Delete all resource groups and their resources from the zone cluster.
phys-schost# clresourcegroup delete -F -Z zoneclustername + |
This step is performed from a global-cluster node. To perform this step from a node of the zone cluster instead, log into the zone-cluster node and omit -Z zonecluster from the command.
Halt the zone cluster.
phys-schost# clzonecluster halt zoneclustername |
Uninstall the zone cluster.
phys-schost# clzonecluster uninstall zoneclustername |
Unconfigure the zone cluster.
phys-schost# clzonecluster delete zoneclustername |
phys-schost# clresourcegroup delete -F -Z sczone + |
phys-schost# clzonecluster halt sczone |
phys-schost# clzonecluster uninstall sczone |
phys-schost# clzonecluster delete sczone |
Perform this procedure to remove a file system from a zone cluster. Supported file system types in a zone cluster include UFS, Vxfs, standalone QFS, , ZFS (exported as a data set), and loopback file systems. For instructions on adding a file system to a zone cluster, see Adding File Systems to a Zone Cluster in Sun Cluster Software Installation Guide for Solaris OS.
The phys-schost# prompt reflects a global-cluster prompt. This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser on a node of the global cluster that hosts the zone cluster. Some steps in this procedure are performed from a node of the global cluster. Other steps are performed from a node of the zone cluster.
Delete the resources related to the file system being removed.
Identify and remove the Sun Cluster resource types, such as HAStoragePlus and SUNW.ScalMountPoint, that are configured for the zone cluster's file system that you are removing.
phys-schost# clresource delete -F -Z zoneclustername fs_zone_resources |
If applicable, identify and remove the Sun Cluster resources of type SUNW.qfs that are configured in the global cluster for the file system that you are removing.
phys-schost# clresource delete -F fs_global_resouces |
Use the -F option carefully because it forces the deletion of all the resources you specify, even if you did not disable them first. All the resources you specified are removed from the resource-dependency settings of other resources, which can cause a loss of service in the cluster. Dependent resources that are not deleted can be left in an invalid state or in an error state. For more information, see the clresource(1CL) man page.
If the resource group for the removed resource later becomes empty, you can safely delete the resource group.
Determine the path to the file-system mount point directory. For example:
phys-schost# clzonecluster configure zoneclustername |
Remove the file system from the zone-cluster configuration.
phys-schost# clzonecluster configure zoneclustername |
clzc:zoneclustername> remove fs dir=filesystemdirectory |
clzc:zoneclustername> commit |
The file system mount point is specified by dir=.
Verify the removal of the file system.
phys-schost# clzonecluster show -v zoneclustername |
This example shows how to remove a file system with a mount-point directory (/local/ufs-1) that is configured in a zone cluster called sczone. The resource is hasp-rs and is of the type HAStoragePlus.
phys-schost# clzonecluster show -v sczone ... Resource Name: fs dir: /local/ufs-1 special: /dev/md/ds1/dsk/d0 raw: /dev/md/ds1/rdsk/d0 type: ufs options: [logging] ... phys-schost# clresource delete -F -Z sczone hasp-rs phys-schost# clzonecluster configure sczone clzc:sczone> remove fs dir=/local/ufs-1 clzc:sczone> commit phys-schost# clzonecluster show -v sczone |
This example shows to remove a ZFS file systems in a ZFS pool called HAzpool, which is configured in the sczone zone cluster in resource hasp-rs of type SUNW.HAStoragePlus.
phys-schost# clzonecluster show -v sczone ... Resource Name: dataset name: HAzpool ... phys-schost# clresource delete -F -Z sczone hasp-rs phys-schost# clzonecluster configure sczone clzc:sczone> remove dataset name=HAzpool clzc:sczone> commit phys-schost# clzonecluster show -v sczone |
You can remove storage devices, such as SVM disksets and DID devices, from a zone cluster. Perform this procedure to remove a storage device from a zone cluster.
Become superuser on a node of the global cluster that hosts the zone cluster. Some steps in this procedure are performed from a node of the global cluster. Other steps can be performed from a node of the zone cluster.
Delete the resources related to the devices being removed. Identify and remove the Sun Cluster resource types, such as SUNW.HAStoragePlus and SUNW.ScalDeviceGroup, that are configured for the zone cluster's devices that you are removing.
phys-schost# clresource delete -F -Z zoneclustername dev_zone_resources |
Determine the match entry for the devices to be removed.
phys-schost# clzonecluster show -v zoneclustername ... Resource Name: device match: <device_match> ... |
Remove the devices from the zone-cluster configuration.
phys-schost# clzonecluster configure zoneclustername clzc:zoneclustername> remove device match=<devices_match> clzc:zoneclustername> commit clzc:zoneclustername> end |
Reboot the zone cluster.
phys-schost# clzonecluster reboot zoneclustername |
Verify the removal of the devices.
phys-schost# clzonecluster show -v zoneclustername |
This example shows how to remove an SVM disk set called apachedg configured in a zone cluster called sczone. The set number of the apachedg disk set is 3. The devices are used by the zc_rs resource that is configured in the cluster.
phys-schost# clzonecluster show -v sczone ... Resource Name: device match: /dev/md/apachedg/*dsk/* Resource Name: device match: /dev/md/shared/3/*dsk/* ... phys-schost# clresource delete -F -Z sczone zc_rs phys-schost# ls -l /dev/md/apachedg lrwxrwxrwx 1 root root 8 Jul 22 23:11 /dev/md/apachedg -> shared/3 phys-schost# clzonecluster configure sczone clzc:sczone> remove device match=/dev/md/apachedg/*dsk/* clzc:sczone> remove device match=/dev/md/shared/3/*dsk/* clzc:sczone> commit clzc:sczone> end phys-schost# clzonecluster reboot sczone phys-schost# clzonecluster show -v sczone |
This example shows how to remove DID devices d10 and d11, which are configured in a zone cluster called sczone. The devices are used by the zc_rs resource that is configured in the cluster.
phys-schost# clzonecluster show -v sczone ... Resource Name: device match: /dev/did/*dsk/d10* Resource Name: device match: /dev/did/*dsk/d11* ... phys-schost# clresource delete -F -Z sczone zc_rs phys-schost# clzonecluster configure sczone clzc:sczone> remove device match=/dev/did/*dsk/d10* clzc:sczone> remove device match=/dev/did/*dsk/d11* clzc:sczone> commit clzc:sczone> end phys-schost# clzonecluster reboot sczone phys-schost# clzonecluster show -v sczone |
Perform this procedure to uninstall Sun 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.
To uninstall Sun 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 Uninstall Sun Cluster Software to Correct Installation Problems” in the Sun Cluster Software Installation Guide for Solaris OS.
The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.
This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Ensure that you have correctly completed all prerequisite tasks in the task map to remove a cluster node.
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.
Become superuser on an active member of the global cluster other than the global-cluster node that you are uninstalling. Perform this procedure from a global-cluster node.
From the active cluster member, add the node that you intend to uninstall to the cluster's node authentication list.
phys-schost# claccess allow -h hostname |
Specifies the name of the node to be added to the node's authentication list.
Alternately, you can use the clsetup(1CL) utility. See How to Add a Node to the Authorized Node List for procedures.
Become superuser on the node to uninstall.
If you have a zone cluster, uninstall it.
phys-schost# clzonecluster uninstall -F zoneclustername |
For specific steps, How to Remove a Zone Cluster.
If your node has a dedicated partition for the global devices namespace, reboot the global-cluster node into noncluster mode.
On a SPARC based system, run the following command.
# shutdown -g0 -y -i0ok 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 -x |
In the /etc/vfstab file, remove all globally mounted file-system entries except the /global/.devices global mounts.
If you intend to reinstall Sun Cluster software on this node, remove the Sun Cluster entry from the Sun Java Enterprise System (Java ES) product registry.
If the Java ES product registry contains a record that Sun Cluster software was installed, the Java ES installer shows the Sun Cluster component grayed out and does not permit reinstallation.
Start the Java ES uninstaller.
Run the following command, where ver is the version of the Java ES distribution from which you installed Sun Cluster software.
# /var/sadm/prod/SUNWentsysver/uninstall |
Follow the prompts to select Sun Cluster to uninstall.
For more information about using the uninstall command, see Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.
If you do not intend to reinstall the Sun Cluster software on this cluster, disconnect the transport cables and the transport switch, if any, from the other cluster devices.
If the uninstalled node is connected to a storage device that uses a parallel SCSI interface, install a SCSI terminator to the open SCSI connector of the storage device after you disconnect the transport cables.
If the uninstalled node is connected to a storage device that uses Fibre Channel interfaces, no termination is necessary.
Follow the documentation that shipped with your host adapter and server for disconnection procedures.
If you use a loopback file interface (lofi) device, the Java ES uninstaller automatically removes the lofi file, which is called /.globaldevices. 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 scinstall -r 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 scinstall: global-mount1 is still configured as a global mount. scinstall: global-mount1 is still configured as a global mount. scinstall: /global/dg1 is still configured as a global mount. scinstall: It is not safe to uninstall with these outstanding errors. scinstall: Refer to the documentation for complete uninstall instructions. scinstall: Uninstall failed. |
To correct this error, return to How to Uninstall Sun Cluster Software From a Cluster Node and repeat the procedure. Ensure that you successfully complete Step 7 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 scinstall: This node is still configured to host device service " service". scinstall: This node is still configured to host device service " service2". scinstall: This node is still configured to host device service " service3". scinstall: This node is still configured to host device service " dg1". scinstall: It is not safe to uninstall with these outstanding errors. scinstall: Refer to the documentation for complete uninstall instructions. scinstall: 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 Sun Cluster SNMP event MIB.
The Sun 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 a Sun Cluster SNMP event MIB can involve the following tasks.
Table 9–3 Task Map: Creating, Setting Up, and Managing the Sun Cluster SNMP Event MIB
Task |
Instructions |
---|---|
Enable an SNMP event MIB | |
Disable an SNMP event MIB | |
Change an SNMP event MIB | |
Add an SNMP host to the list of hosts that will receive trap notifications for the MIBs | |
Remove an SNMP host |
How to Disable an SNMP Host From Receiving SNMP Traps on a Node |
Add an SNMP user | |
Remove an SNMP user |
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Enable the SNMP event MIB.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Disable the SNMP event MIB.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Change the protocol of the SNMP event MIB.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Add the host to the SNMP host list of a community on another node.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Remove the host from the SNMP host list of a community on the specified node.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Add the SNMP user.
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 Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix B, Sun Cluster Object-Oriented Commands.
Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Remove the SNMP user.
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.
This section contains a troubleshooting procedure that you can use for testing purposes.
Use this procedure to run an application outside the global cluster for testing purposes.
Determine if the quorum device is used in the Solaris Volume Manager metaset, and determine if the quorum device uses SCSI2 or SCSI3 reservations.
phys-schost# clquorum show |
If the quorum device is in the Solaris Volume Manager metaset, add a new quorum device which is not part of the metaset to be taken later in noncluster mode.
phys-schost# clquorum add did |
Remove the old quorum device.
phys-schost# clqorum remove did |
If the quorum device uses a SCSI2 reservation, scrub the SCSI2 reservation from the old quorum and verify that no SCSI2 reservations remain.
phys-schost# /usr/cluster/lib/sc/pgre -c pgre_scrub -d /dev/did/rdsk/dids2 phys-schost# /usr/cluster/lib/sc/pgre -c pgre_inkeys -d /dev/did/rdsk/dids2 |
Evacuate the global-cluster node that you want to boot in noncluster mode.
phys-schost# clresourcegroup evacuate -n targetnode |
Take offline any resource group or resource groups that contain HAStorage or HAStoragePlus resources and contain devices or file systems affected by the metaset that you want to later take in noncluster mode.
phys-schost# clresourcegroup offline resourcegroupname |
Disable all the resources in the resource groups that you took offline.
phys-schost# clresource disable resourcename |
Unmanage the resource groups.
phys-schost# clresourcegroup unmanage resourcegroupname |
Take offline the corresponding device group or device groups.
phys-schost# cldevicegroup offline devicegroupname |
Disable the device group or device groups.
phys-schost# cldevicegroup disable devicegroupname |
Boot the passive node into noncluster mode.
phys-schost# reboot -x |
Verify that the boot process has been completed on the passive node before proceeding.
Solaris 9
The login prompt appears only after the boot process has been completed, so no action is required.
Solaris 10
phys-schost# svcs -x |
Determine if any SCSI3 reservations exist on the disks in the metasets. Run the following command on all disks in the metasets.
phys-schost# /usr/cluster/lib/sc/scsi -c inkeys -d /dev/did/rdsk/dids2 |
If any SCSI3 reservations exist on the disks, scrub them.
phys-schost# /usr/cluster/lib/sc/scsi -c scrub -d /dev/did/rdsk/dids2 |
Take the metaset on the evacuated node.
phys-schost# metaset -s name -C take -f |
Mount the file system or file systems that contain the defined device on the metaset.
phys-schost# mount device mountpoint |
Start the application and perform the desired test. After finishing the test, stop the application.
Reboot the node and wait until the boot process has ended.
phys-schost# reboot |
Bring online the device group or device groups.
phys-schost# cldevicegroup online -e devicegroupname |
Start the resource group or resource groups.
phys-schost# clresourcegroup online -eM resourcegroupname |