test

Sun Cluster Software Installation Guide for Solaris OS

Uninstalling the Software

This section provides procedures to uninstall or remove certain software products from a global cluster.

ProcedureHow to Unconfigure Sun Cluster Software to Correct Installation Problems

Perform this procedure if the installed node cannot join the cluster or if you need to correct configuration information. For example, perform this procedure on all nodes to reconfigure the transport adapters or the private-network address.

Note –

If the node has already joined the cluster and is no longer in installation mode, as described in Step 2 of How to Verify the Quorum Configuration and Installation Mode, do not perform this procedure. Instead, go to How to Uninstall Sun Cluster Software From a Cluster Node in Sun Cluster System Administration Guide for Solaris OS.

Before You Begin

Attempt to rerun cluster configuration of the node by using the scinstall utility. You can correct certain cluster node configuration failures by repeating Sun Cluster software configuration on the node.

  1. Add to the cluster's node-authentication list each node that you intend to unconfigure.

    If you are unconfiguring a single-node cluster, skip to Step 2.

    1. On an active cluster member other than the node that you are unconfiguring, become superuser.

    2. Specify the name of the node to add to the authentication list.


      phys-schost# /usr/cluster/bin/claccess allow -h nodename
      -h nodename

      Specifies the name of the node to add to the authentication list.

      You can also use the clsetup utility to perform this task. See How to Add a Node to the Authorized Node List in Sun Cluster System Administration Guide for Solaris OS for procedures.

  2. On a node that you intend to unconfigure, become superuser.

  3. Shut down the node.


    phys-schost# shutdown -g0 -y -i0

  4. Reboot the node into noncluster mode.

    • On SPARC based systems, perform the following command:


      ok boot -x

    • On x86 based systems, perform the following commands:

      1. 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.97 (639K lower / 1047488K 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.

      2. 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.97 (639K lower / 1047488K 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.

      3. Add -x to the command to specify that the 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

      4. Press Enter to accept the change and return to the boot parameters screen.

        The screen displays the edited command.


        GNU GRUB version 0.97 (639K lower / 1047488K 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.-

      5. Type b to boot the node into noncluster mode.

        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.

  5. Change to a directory, such as the root (/) directory, that does not contain any files that are delivered by the Sun Cluster packages.


    phys-schost# cd /

  6. Remove the node from the cluster configuration.


    phys-schost# /usr/cluster/bin/clnode remove

    The node is removed from the cluster configuration but Sun Cluster software is not removed from the node.

    See the clnode(1CL) man page for more information.

  7. Repeat Step 2 through Step 6 for each additional node to unconfigure.

  8. (Optional) Uninstall Sun Cluster framework and data service software packages.

    Note –

    If you do not need to remove or reinstall Sun Cluster software, you can skip this step.

    This step also removes 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 is installed, the Java ES installer will show the Sun Cluster component grayed out and will not permit reinstallation.

    1. Start the uninstall program.

      Run the following command, where ver is the version of the Java ES distribution from which you installed Sun Cluster software.


      phys-schost# /var/sadm/prod/SUNWentsysver/uninstall

    2. Follow the onscreen instructions to select the Sun Cluster components to uninstall.

      Note –

      If Sun Cluster Geographic Edition software is installed, you must uninstall it as well.

      For more information about using the uninstall program, see Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX. Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX

Next Steps

To reinstall or reconfigure Sun Cluster software on the node, refer to Table 2–1. This table lists all installation tasks and the order in which to perform the tasks.

To physically remove the node from the cluster, see How to Remove an Interconnect Component in Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS and the removal procedure in the Sun ClusterHardware Administration Collection manual for your storage array.

ProcedureHow to Remove Sun Cluster Information From a JumpStart Install Server

Perform this procedure to remove Sun Cluster information from a JumpStart install server that was used to install and configure a cluster. You can remove information for one or more individual nodes or for one or more entire clusters. For more information about the JumpStart feature, see Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations.

  1. Become superuser on the JumpStart install server.

  2. Change to the JumpStart directory that you used to install Sun Cluster software.


    installserver# cd jumpstart-dir

  3. Remove from the rules file any entries that were created by the scinstall command that contain the name of a node that you want to remove.

    The Sun Cluster entries reference autostinstall.class or autoscinstall.finish or both. Entries appear similar to the following, where release is the version of Sun Cluster software:


    hostname phys-schost-1  -  autoscinstall.d/release/autoscinstall.class  \ 
autoscinstall.d/release/autoscinstall.finish

  4. Regenerate the rules.ok file.

    Run the check command that is located in the jumpstart-dir/ directory to regenerate the rules.ok file.


    installserver# ./check

  5. Remove from the appropriate clusters/clustername/ directory the symbolic link for each node that you want to remove.

    • To remove the symbolic link for one or more nodes in a cluster, remove the link that is named for each node to remove.


      installserver# rm -f autoscinstall.d/clusters/clustername/nodename

    • To remove the symbolic links for an entire cluster, recursively remove the directory that is named for the cluster to remove.


      installserver# rm -rf autoscinstall.d/clusters/clustername

    • To remove the symbolic links for all clusters, recursively remove the clusters/ directory.


      installserver# rm -rf autoscinstall.d/clusters

  6. Remove from the autoscinstall.d/ directory the node configuration directory that is named for each node that you want to remove.

    If you are removing information for an entire cluster, remove the directory for each node in the cluster.

    • To remove information for one or more nodes in a cluster, recursively remove the directory for each node.


      installserver# rm -rf autoscinstall.d/nodes/nodename

    • To remove all entries for all clusters, recursively remove the autoscinstall.d directory.


      installserver# rm -rf autoscinstall.d

  7. Remove the .autoscinstall.log.3 file.


    installserver# rm .autoscinstall.log.3

  8. (Optional) If you used a flash archive to JumpStart install the cluster, remove the flash archive if you no longer need the file.


    installserver# rm filename.flar
Next Steps

If you intend to use custom JumpStart to reinstall a cluster from which you removed information for one or more nodes that were removed from that cluster, you must rerun interactive scinstall to update the cluster node list. See How to Install Solaris and Sun Cluster Software (JumpStart).

ProcedureHow to Uninstall SunPlex Manager Software

Use this procedure to uninstall SunPlex Manager software that was installed by the Java ES installer utility up to and including the Sun Java Enterprise System 2005Q4 distribution or by any other installation method.

To remove Sun Cluster Manager software that was installed with the Sun Java Enterprise System 5 or compatible distribution of the Java ES installer utility, instead use the Java ES uninstall utility to remove these packages. For more information, see Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Note –

Do not uninstall SunPlex Manager or Sun Cluster Manager or its shared components if you intend to use the graphical user interface (GUI) to Sun Cluster Geographic Edition software or to Sun Cluster features that are available through the GUI. These features include the data-service configuration wizards or system resource monitoring.

However, if you use the command-line interface to administer these features, it is safe to uninstall SunPlex Manager or Sun Cluster Manager software.

Perform this procedure on each node in the cluster to uninstall SunPlex Manager software and related Sun Java Enterprise System (Java ES) shared components.

Note –

SunPlex Manager software must be installed on all cluster nodes or on none.

  1. Become superuser on a cluster node.

  2. Remove the SunPlex Manager software packages.


    phys-schost# pkgrm SUNWscspm SUNWscspmu SUNWscspmr

  3. (Optional) Remove Sun Java Web Console software packages, if you have no other need for them.


    phys-schost# pkgrm SUNWmctag SUNWmconr SUNWmcon SUNWmcos SUNWmcosx

  4. (Optional) If you removed Sun Java Web Console packages, remove Apache Tomcat and Java Studio Enterprise Web Application Framework (Java ATO) software packages, if you have no other need for them.

    Remove the packages listed below for each additional product that you want to uninstall, in the order that the set of packages is listed.


    phys-schost# pkgrm packages

    Product 

    Package Names 

    Apache Tomcat 

    SUNWtcatu

    Java ATO 

    SUNWjato SUNWjatodmo SUNWjatodoc

ProcedureHow to Uninstall the SUNWscrdt Package

Perform this procedure on each node in the cluster.

Before You Begin

Verify that no applications are using the RSMRDT driver before performing this procedure.

  1. Become superuser on the node to which you want to uninstall the SUNWscrdt package.

  2. Uninstall the SUNWscrdt package.


    phys-schost# pkgrm SUNWscrdt

ProcedureHow to Unload the RSMRDT Driver Manually

If the driver remains loaded in memory after completing How to Uninstall the SUNWscrdt Package, perform this procedure to unload the driver manually.

  1. Start the adb utility.


    phys-schost# adb -kw

  2. Set the kernel variable clifrsmrdt_modunload_ok to 1.


    physmem NNNN
clifrsmrdt_modunload_ok/W 1

  3. Exit the adb utility by pressing Control-D.

  4. Find the clif_rsmrdt and rsmrdt module IDs.


    phys-schost# modinfo | grep rdt

  5. Unload the clif_rsmrdt module.

    You must unload the clif_rsmrdt module before you unload the rsmrdt module.


    phys-schost# modunload -i clif_rsmrdt_id
    clif_rsmrdt_id

    Specifies the numeric ID for the module that is being unloaded.

  6. Unload the rsmrdt module.


    phys-schost# modunload -i rsmrdt_id
    rsmrdt_id

    Specifies the numeric ID for the module that is being unloaded.

  7. Verify that the module was successfully unloaded.


    phys-schost# modinfo | grep rdt
Example 9–1 Unloading the RSMRDT Driver

The following example shows the console output after the RSMRDT driver is manually unloaded.


phys-schost# adb -kw
physmem fc54
clifrsmrdt_modunload_ok/W 1
clifrsmrdt_modunload_ok: 0x0 = 0x1
^D
phys-schost# modinfo | grep rsm
 88 f064a5cb 974 - 1 rsmops (RSMOPS module 1.1)
 93 f08e07d4 b95 - 1 clif_rsmrdt (CLUSTER-RSMRDT Interface module)
 94 f0d3d000 13db0 194 1 rsmrdt (Reliable Datagram Transport dri)
phys-schost# modunload -i 93
phys-schost# modunload -i 94
phys-schost# modinfo | grep rsm
 88 f064a5cb 974 - 1 rsmops (RSMOPS module 1.1)
Troubleshooting

If the modunload command fails, applications are probably still using the driver. Terminate the applications before you run modunload again.

ProcedureHow to Remove Quorum Server Software

Before You Begin

Before you uninstall Quorum Server software, ensure that you have completed the following tasks:

  1. (Optional) To use the interactive graphical interface to uninstall the Java Enterprise System components, ensure that the display environment of the host server to uninstall is set to display the GUI.


    % xhost +
% setenv DISPLAY nodename:0.0

  2. Become superuser on the quorum server host computer to uninstall.

  3. Navigate to the directory where the uninstaller is located.


    quorumserver# cd /var/sadm/prod/SUNWentsysver
    ver

    The version of Java Enterprise System that is installed on your system.

  4. Start the uninstallation wizard.


    quorumserver# ./uninstall

  5. Follow instructions on the screen to uninstall the Quorum Server software from the quorum-server host computer.

    After removal is finished, you can view any available log. See Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX for additional information about using the uninstall program.

  6. (Optional) Clean up or remove the quorum server directories.

    By default, this directory is /var/scqsd.

ProcedureHow to Unconfigure a Zone Cluster

Perform this procedure to remove a zone cluster.

  1. Become superuser on a node of the global cluster.

    You perform all steps of this procedure from a node of the global cluster.

  2. Take offline each resource group in the zone cluster and disable its resources.

    Note –

    The following steps are performed from a global-cluster node. To instead perform these steps from a node of the zone cluster, log in to the zone-cluster node and omit “-Z zonecluster” from each command.

    1. Take each resource offline.


      phys-schost# clresource offline -Z zonecluster resource-group

    2. List all enabled resources in the zone cluster.


      phys-schost# clresource show -Z zonecluster -p Enabled
=== Resources ===

Resource:                                       resource
  Enabled{nodename1}:                               True
  Enabled{nodename2}:                               True
…

    3. Identify those resources that depend on other resources.


      phys-schost# clresource show -Z zonecluster -p resource_dependencies
=== Resources ===

Resource:                                       node
  Resource_dependencies:                           node
…

      You must disable dependent resources first before you disable the resources that they depend on.

    4. Disable each enabled resource in the cluster.


      phys-schost# clresource disable -Z zonecluster resource

      See the clresource(1CL) man page for more information.

    5. Verify that all resources are disabled.


      phys-schost# clresource show -Z zonecluster -p Enabled
=== Resources ===

Resource:                                       resource
  Enabled{nodename1}:                               False
  Enabled{nodename2}:                               False
…

    6. Move each resource group to the unmanaged state.


      phys-schost# clresourcegroup unmanage -Z zonecluster resource-group

    7. Verify that all resources on all nodes are Offline and that all resource groups are in the Unmanaged state.


      phys-schost# cluster status -Z zonecluster -t resource,resourcegroup

    8. Delete all resource groups and their resources from the zone cluster.


      phys-schost# clresourcegroup delete -F -Z zonecluster +

  3. Halt the zone cluster.


    phys-schost# clzonecluster halt zoneclustername

  4. Uninstall the zone cluster.


    phys-schost# clzonecluster uninstall zoneclustername

  5. Unconfigure the zone cluster.


    phys-schost# clzonecluster delete zoneclustername