Top
PRIMECLUSTER  Installation and Administration Guide4.2

8.8.3 Supplement on Cluster Application and Resource Deletion

This section explains the operations to be done after "8.8.1 Deleting a userApplication" and "8.8.2 Deleting a Resource."

8.8.3.1 Supplement on Cmdline resource deletion

Delete each script used in the Cmdline resources.

Note

Before deleting scripts, you need to delete the Cmdline resources.

Each script is stored in the following directories:

Execute the deletion command as follows:

  # cd /etc/opt/FJSVwvucw/scripts/start

# rm <script name to be deleted>

# cd /etc/opt/FJSVwvucw/scripts/stop

# rm <script name to be deleted>

# cd /etc/opt/FJSVwvucw/scripts/check

# rm <script name to be deleted>

8.8.3.2 Supplement on Fsystem resource deletion

Restore the environment files related to the mount point to the original state.

Note

Before deleting the environment files, you need to delete the Fsystem resources.

Deleting mount point entries that were added at prerequisites

Delete the relevant entry from the following environment files that were edited as part of the "6.6.1.2.1 Prerequisites."

If a dummy entry is deleted from /etc/dfs/dfstab, delete the actual directory.

When an NFS Lock Failover was used

If the NFS Lock Failover functions are no longer used due to deletion of the Fsystem resources, take the following steps:

Procedure:
  1. Change the settings for shared information with the configuration.

    Change the value of NFSLockFailover to "no."

8.8.3.3 Supplement on Gds resource deletion

Delete the disk class if it is no longer necessary.

See the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."

8.8.3.4 Supplement related to Gls resource deletion

Delete the takeover network definition if it is no longer necessary.

See "5.4 Deleting configuration for Cluster System" in the "PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function."

8.8.3.5 Supplement on takeover network resource deletion

Restore the environment files related to the takeover network to the original state.

When MAC address takeover was used

Delete the entries that were added to the following environment files during the prerequisite procedure of the MAC address takeover.

For details on the added entries, see "6.6.1.5.1 Prerequisites."

When node name takeover was used

Change the node name in the cluster system used for node name takeover. To bring the system state back to the state before the change, take the following steps on all the nodes where node name takeover resources were created.

Operation
  1. Execute the command on all the nodes, as follows:

    # setuname -n fuji2

    fuji2 is used as the node name in this example.

  2. Reboot the system.

    # /usr/sbin/shutdown -g0 -i6 -y

8.8.3.6 Supplement on procedure resource deletion

Delete the procedure resource from the cluster resource management facility when it is no longer necessary.

See "F.3 Deleting a Procedure Resource."

8.8.3.7 Supplement on process monitoring resource deletion

Delete scripts that were created automatically if the stop command of the process monitoring resource was used.

Note

Before deleting the created scripts, you need to delete the process monitoring resources.

Each script is stored in the /etc/opt/FJSVwvucw/scripts/process_stop directory.

Execute the deletion command as shown below.

# cd /etc/opt/FJSVwvucw/scripts/process_stop
# rm ./*

8.8.3.8 Supplement on line switching unit resource deletion

Delete the line switching unit resource from the cluster resource management facility if it is not necessary.

See the manual pages of the "cldelswursc(1M)" command.

8.8.3.9 ISV resource deletion procedure (supplement)

For information on the deletion procedure, see the manuals provided with each product.