This section describes how to uninstall Systemwalker Operation Manager from the PRIMECLUSTER system.
The explanation in the following examples assumes that the Systemwalker Operation Manager configuration file registered with PRIMECLUSTER is "config", the Systemwalker Operation Manager application name is "OP1", and the mount point for the shared disk has been set to "/disk1".
1) Stop RMS and start the RMS Wizard
Before deleting cluster applications and resources, use either ClusterAdmin or the hvdisp command to check that RMS is not running. If RMS is running, stop it on every node in the cluster system using either ClusterAdmin or the hvshut command.
Refer to the PRIMECLUSTER manual for details on the hvdisp and hvshut commands.
Example of how to stop RMS with the hvshut command:
# /opt/SMAW/SMAWRrms/bin/hvshut -a |
Start the RMS Wizard by executing the hvw command.
Refer to the PRIMECLUSTER manual for details on the hvw command.
Example of how to start the RMS Wizard using "config" as the configuration file name:
# /opt/SMAW/SMAWRrms/bin/hvw -n config |
The "Main Configuration Menu" will be displayed.
2) Delete resources
This section describes the procedure for deleting resources.
Select "Application-Edit".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 4
Select the name of the userApplication where the resources to be deleted are registered.
Edit: Application selection menu (restricted): 1) HELP 2) QUIT 3) RETURN 4) OPTIONS 5) OP1 Application Name: 5
Select "Procedure:SystemState3".
Settings of turnkey wizard "STANDBY" (OP1:consistent) 1) HELP 9) Procedure:BasicApplication(-) 2) READONLY 10) Symfoware(-) 3) SAVE+EXIT 11) Procedure:SystemState3(ProSS3_OP1) 4) - 12) Procedure:SystemState2(-) 5) ApplicationName=OP1 13) Gls:Global-Link-Services(Gls_OP1) 6) Machines+Basics(op1) 14) LocalFileSystems(Lfs_OP1) 7) CommandLines(-) 15) Gds:Global-Disk-Services(-) 8) Procedure:Application(-) Choose the setting to process: 11
Select "REMOVE+EXIT" to cancel the procedure resource settings.
However, if procedure resources of other than OMGR and OMGRMONITOR coexist, delete only the procedure resources of OMGR or OMGRMONITOR by selecting "NONE" in the window displayed after selecting "OMGR" or "OMGRMONITOR".
SystemState3 Procedure (ProSS3_OP1:consistent) 1) HELP 2) NO-SAVE+EXIT 3) SAVE+EXIT 4) REMOVE+EXIT 5) AdditionalProcedureResource 6) ProcedureResources[0]=OMGR:T1800,P100 7) ProcedureResources[1]=OMGRMONITOR:T1800,P150 Choose the setting to process: 4
Enter "yes".
About to remove all data of ProSS3_OP1,
Please confirm this by typing yes: yesSelect "Gls".
Settings of turnkey wizard "STANDBY" (OP1:consistent) 1) HELP 9) Procedure:BasicApplication(-) 2) - 10) Symfoware(-) 3) SAVE+EXIT 11) Procedure:SystemState3(-) 4) - 12) Procedure:SystemState2(-) 5) ApplicationName=OP1 13) Gls:Global-Link-Services(Gls_OP1) 6) Machines+Basics(op1) 14) LocalFileSystems(Lfs_OP1) 7) CommandLines(-) 15) Gds:Global-Disk-Services(-) 8) Procedure:Application(-) Choose the setting to process: 13
Select "REMOVE+EXIT" to cancel the Gls resource settings.
Gls (Gls_OP1:consistent) 1) HELP 5) AdditionalTakeoverIpaddress 2) NO-SAVE+EXIT 6) TakeoverIpaddress[0]=N,000.000.000.00x 3) SAVE+EXIT 7) (Timeout=60) 4) REMOVE+EXIT Choose the setting to process: 4
Enter "yes".
About to remove all data of Gls_OP1,
Please confirm this by typing yes: yesSelect "LocalFileSystems".
Settings of turnkey wizard "STANDBY" (OP1:consistent) 1) HELP 9) Procedure:BasicApplication(-) 2) - 10) Symfoware(-) 3) SAVE+EXIT 11) Procedure:SystemState3(-) 4) - 12) Procedure:SystemState2(-) 5) ApplicationName=OP1 13) Gls:Global-Link-Services(-) 6) Machines+Basics(op1) 14) LocalFileSystems(Lfs_OP1) 7) CommandLines(-) 15) Gds:Global-Disk-Services(-) 8) Procedure:Application(-) Choose the setting to process: 14
Select "REMOVE+EXIT" to cancel the Fsystem resource settings.
File systems (Lfs_OP1:consistent) 1) HELP 5) AdditionalMountPoint 2) NO-SAVE+EXIT 6) MountPoints[0]=LA:/disk1 3) SAVE+EXIT 7) (Filter=) 4) REMOVE+EXIT 8) (Timeout=180) Choose the setting to process: 4
Enter "yes".
About to remove all data of Lfs_OP1,
Please confirm this by typing yes: yesSelect "SAVE+EXIT".
Settings of turnkey wizard "STANDBY" (OP1:not yet consistent) 1) HELP 9) Procedure:BasicApplication(-) 2) - 10) Symfoware(-) 3) SAVE+EXIT 11) Procedure:SystemState3(-) 4) - 12) Procedure:SystemState2(-) 5) ApplicationName=OP1 13) Gls:Global-Link-Services(-) 6) Machines+Basics(op1) 14) LocalFileSystems(-) 7) CommandLines(-) 15) Gds:Global-Disk-Services(-) 8) Procedure:Application(-) Choose the setting to process: 3
Select "RETURN".
Edit: Application selection menu (restricted): 1) HELP 2) QUIT 3) RETURN 4) OPTIONS 5) OP1 Application Name: 3
Select "Configuration-Generate".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 7
Select "Configuration-Activate".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 8
3) Delete the userApplication (cluster application).
Use the following procedure to delete the cluster application:
Select "Application-Remove".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 5
Delete the cluster application by selecting the name of the userApplication to be deleted.
Removal: Application selection menu: 1) HELP 2) QUIT 3) RETURN 4) OPTIONS 5) OP1 Application Name: 5
Enter "yes".
About to remove all data of OP1,
Please confirm this by typing yes: yesSelect "Configuration-Generate".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 7
Select "Configuration-Activate".
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 8
Select "QUIT" to end the procedure.
linux01: Main configuration menu, current configuration: config No RMS active in the cluster 1) HELP 10) Configuration-Remove 2) QUIT 11) Configuration-Freeze 3) Application-Create 12) Configuration-Thaw 4) Application-Edit 13) Configuration-Edit-Global-Settings 5) Application-Remove 14) Configuration-Consistency-Report 6) Application-Clone 15) Configuration-ScriptExecution 7) Configuration-Generate 16) RMS-CreateMachine 8) Configuration-Activate 17) RMS-RemoveMachine 9) Configuration-Copy Choose an action: 2
For N:1 active/standby configuration, delete all N cluster applications by repeating steps 2) and 3).
For dual node mutual standby configuration, delete both cluster applications by repeating steps 2) and 3).
4) Delete resources that use state transition procedures.
Use the cldelprocrsc command to delete the resources that use state transition procedures. In the example below, the resource ID is 113.
Resource IDs that have been registered can be looked up with the clgettree command.
Refer to the PRIMECLUSTER manual for details on the cldelprocrsc and clgettree commands.
# /etc/opt/FJSVcluster/bin/cldelprocrsc -r 113
For N:1 active/standby configuration, delete all N resources. For dual node mutual standby configuration, delete both resources.
5) Delete state transition procedures.
Delete the state transition procedures by using the cldelproc command on each of the active and standby nodes. In the following example, the procedure name is "omgr".
# /etc/opt/FJSVcluster/bin/cldelproc -c SystemState3 omgr
6) Stop the daemons.
Use the poperationmgr command on each node in the cluster system to stop all the Systemwalker Operation Manager daemons. Refer to the Systemwalker Operation Manager Reference Guide for details on the poperationmgr command.
7) Delete the symbolic links.
Delete the symbolic links created to point to the resources that were moved to the shared disk. Do this operation at each node (active and standby) in the cluster system.
8) Copy resources back from the shared disk to the local disks.
Move the resources that were moved to the shared disk when the cluster system was created back to the local disks. Do this operation at each active node.
9) Copy resources to the standby node.
Copy the resources moved back to the local disk on the active node over to the standby node. Copy the resources to the standby node from any one of the N active nodes. For cascading configuration, copy the resources to all the standby nodes.
10) Create symbolic links.
For 1:1 active/standby (without subsystems), 1:1 active/standby (with subsystems), N:1 active/standby, and cascading configurations, recreate the symbolic links that were deleted when the resources were moved to the shared disk.
Create "/var/spool/mjes" as a symbolic link to "var/opt/FJSVMJS/var/spool/mjes".
Create "/etc/mjes" as a symbolic link to "etc/opt/FJSVMJS/etc/mjes".
Do this operation on all nodes (active and standby). This operation is not required for 1:1 active/standby (with subsystems and partial cluster operation) configurations or dual node mutual standby configurations.
11) Perform settings for automatically starting and stopping daemons.
Restore the settings for the monitored processes and the settings for automatically starting and stopping daemons (canceled in "2.2.3 Canceling the settings for starting and stopping daemons automatically") to their original settings.
12) Cancel automatic reflection settings.
Use the following command to cancel the security information settings:
mpaclcls -u
Use the following command to cancel the settings for automatically reflecting calendar and service/application startup information:
/opt/FJSVjmcal/bin/calsetcluster -d
Refer to the Systemwalker Operation Manager Reference Guide for details on the mpaclcls command and the calsetcluster command.
13) Delete cluster information.
Execute the mpsetcluster command with the "-d" option specified on each node in the cluster system to delete cluster information registered after Systemwalker Operation Manager was installed.
# /opt/systemwalker/bin/mpsetcluster -d
Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetcluster command.
14) Cancel SELinux settings.
In Linux environments where SELinux is enabled, the SELinux settings have been made in "2.6 Moving Resources to the Shared Disk", so cancel them.
This must be performed on each node with the shared disk mounted.
The following is a cancellation example for configurations of 1:1 active/standby (without subsystems), 1:1 active/standby (with subsystems), N:1 active/standby, and cascading:
# /usr/sbin/semanage fcontext -d -t var_t '/disk1/FJSVfwseo/JM(/.*)?' # /usr/sbin/semanage fcontext -d -t var_t '/disk1/FJSVjmcal(/.*)?' # /usr/sbin/semanage fcontext -d -t var_t '/disk1/FJSVJOBSC(/.*)?' # /usr/sbin/semanage fcontext -d -t var_t '/disk1/FJSVstem(/.*)?' (*1) # /usr/sbin/semanage fcontext -d -t sw_fjsvmjs_spool_t '/disk1/FJSVMJS/var/spool(/.*)?' # /usr/sbin/semanage fcontext -d -t etc_t '/disk1/FJSVMJS/etc(/.*)?'
This is required only if the Master Schedule Management function is enabled.
15) Delete unnecessary directories from the shared disk.
Delete any unnecessary directories left over on the shared disk from the resources that were moved to the shared disk in "2.6 Moving Resources to the Shared Disk."
Steps 1 through 14 release Systemwalker Operation Manager from its application to the cluster system.
16) Uninstall Systemwalker Operation Manager.
Uninstall Systemwalker Operation Manager. Refer to the Systemwalker Operation Manager Installation Guide for details.
To reinstall Systemwalker Operation Manager, first use the procedure above to uninstall Systemwalker Operation Manager, and then perform a fresh installation in the cluster system again.
To perform an upgrade installation, release Systemwalker Operation Manager from its application to the cluster system by following steps 1 through to 14 above, perform the upgrade installation, and then reapply Systemwalker Operation Manager to the cluster system, starting from "2.2.3 Canceling the settings for starting and stopping daemons automatically."
Note
While uninstalling Systemwalker Operation Manager using the procedure above, be sure to cancel the automatic calendar reflection settings using the "/opt/FJSVjmcal/bin/calsetcluster -d" command. If these settings are not canceled in Red Hat Enterprise Linux 6, the following symbolic file will remain and need to be deleted manually:
/etc/rc3.d/S28JMCAL