10.4.5 Unsetup and uninstallation of PFM - Manager
- Organization of this subsection
(1) Before unsetup and uninstallation
- Notes regarding the order of unsetup:
-
PFM - Manager is required to execute PFM - Agent or PFM - RM. Therefore, when performing unsetup on PFM - Manager, it is necessary to consider its relationship with PFM - Agent or PFM - RM in the system and determine the work order for unsetup. The work order when unsetup is required is the same as the order for a non-cluster system. For details, see the chapter describing installation and setup (in UNIX) in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Notes on stopping of services:
-
Stop all Performance Management programs and services running on the executing nodes and standby nodes on which unsetup is to be performed. Also, stop all PFM - Agent and PFM - RM services across the Performance Management system connected to the instance of PFM - Manager that will be unsetup. For details on how to stop services, see 1. Starting and Stopping Performance Management.
(2) Process flow for unsetup and uninstallation
|
In the procedure explanation, the image indicates the items to be performed on the executing node, and the image
indicates the items to be performed on the standby node. In addition, the image
indicates the setup items required depending on the environment, and the optional setup items for when changing the default
settings.
(3) Unsetup procedure
First, perform unsetup on the executing node. Next, export the logical host environment definitions for the executing node to a file. Finally, import the file containing the environment definitions to the standby node to apply the unsetup content from the executing node to the standby node.
(a) Stopping from the cluster software
![[Figure]](GRAPHICS/ZU115920.GIF)
Use operations from the cluster software to stop Performance Management programs and services running on the executing node and the standby node. For details on how to stop programs and services, see the cluster software documentation.
(b) Making sure the shared disk is mounted ![[Figure]](GRAPHICS/ZU115910.GIF)
Make sure that the shared disk is mounted. If the shared disk is not mounted, execute the mount command to mount it on the file system.
- Note:
-
Even if the shared disk is unmounted, if there is a jp1pc directory and associated files in the environment directory of the logical host that is to be unsetup, setup is performed without mounting the shared disk. If that is the case, use the following procedure:
-
Use the tar command to archive the jp1pc directories in the environment directory of the logical host that is to be unsetup on the local disk.
-
Mount the shared disk.
-
If there is no environment directory of the logical host that is to be unsetup on the shared disk, create an environment directory.
-
Expand the tar file in the environment directory of the logical host that is to be unsetup on the shared disk.
-
Unmount the shared disk.
-
Delete the jp1pc directory and its associated files in the environment directory of the logical host that is to be unsetup on the local disk.
-
(c) Clearing settings for the health check function
![[Figure]](GRAPHICS/ZU105006.GIF)
Execute the following command on the PFM - Manager host on the executing node to clear the settings for the health check function.
jpcconf hc disable
For details on the jpcconf hc disable command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(d) Clearing settings for communication port numbers
![[Figure]](GRAPHICS/ZU105006.GIF)
This procedure is required only when port numbers have been set using the jpcconf port define command during the setup in an environment with a firewall.
-
Clear the settings for communication port numbers.
Execute the jpcconf port define command to clear the settings for communication port numbers.
For example, execute the following command to clear all the settings for port numbers for services that exist on the host with the logical host name jp1-ha1.
jpcconf port define -key all -lhost jp1-ha1
In this example, the jpcconf port define command is executed in interactive mode. However, the command can also be executed in non-interactive mode.
The jpcconf port define command is used to set the port numbers that are used for communications by PFM - Manager on the logical host or by other Performance Management programs. When entering a port number, a value of 0 will clear the setting. In addition, when this command is executed, the port numbers and service names (service names starting with jp1pc by default) for Performance Management defined in the services file are deleted
For details on the jpcconf port define command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(e) Performing unsetup of a logical host for PFM - Manager ![[Figure]](GRAPHICS/ZU115910.GIF)
-
Check the logical host settings.
Check the current settings before performing unsetup on the logical host environment. Check the logical host name and shared disk path.
Execute the command as follows:
jpcconf ha list -key all
An example of executing this command is as follows:
For details on the jpcconf ha list command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
-
Delete the logical host environment for PFM - Manager.
When the jpcconf ha unsetup command is executed, the settings for starting PFM - Manager on the logical host are deleted. In addition, the files for the logical host on shared disks are also deleted. Execute the command as follows:
jpcconf ha unsetup -key Manager -lhost jp1-ha1
For details on the jpcconf ha unsetup command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
- Note:
-
If the shared disk is offline, only the logical host settings will be deleted. The directories and files on the shared disk will not be deleted.
-
Check the logical host settings.
Execute the command as follows:
jpcconf ha list -key all
Make sure that PFM - Manager has been deleted from the logical host environment.
For details on the jpcconf ha list command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(f) Performing unsetup for a logical host of PFM - Agent or PFM - RM
![[Figure]](GRAPHICS/ZU105006.GIF)
This procedure is required only when there is PFM - Agent or PFM - RM on the same logical host from which unsetup will also be performed for PFM - Manager.
Perform unsetup of PFM - Agent or PFM - RM. For details on the unsetup procedure, see the chapters that describe operations on cluster systems in the appropriate PFM - Agent or PFM - RM manual.
(g) Exporting the logical host environment definitions ![[Figure]](GRAPHICS/ZU115910.GIF)
When a logical host environment to perform unsetup of PFM - Manager is created on the executing node, apply the settings information for the executing node to the standby node. First, export the logical host environment definitions for the executing node to a file.
- Note:
-
To perform unsetup of a different instance of Performance Management from the same logical host, perform the export after all unsetup procedures are completed
-
Export the logical host environment definitions.
For example, execute the following command to export the logical host environment definitions to the lhostexp.conf file. The export file allows an arbitrary file name.
jpcconf ha export -f lhostexp.conf
In this example, the jpcconf ha export command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha export command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(h) Copying the file containing the logical host environment definitions to the standby node
![[Figure]](GRAPHICS/ZU115920.GIF)
Copy the file that has been exported in step (f) from the executing node to the standby node, so that it will be applied on the standby node.
Next, unmount the file system to complete the work. If this shared disk will continue to be used, it is not necessary to unmount the file system.
(i) Importing the file containing the logical host environment definitions ![[Figure]](GRAPHICS/ZU115920.GIF)
Import the export file copied from the executing node to the standby node, so that it will be applied to the standby node
Use the jpcconf ha import command to apply the Performance Management settings for the logical host created on the executing node to the standby node. If multiple instances of Performance Management have been set up on a single logical host, import all of the instances as one group.
-
Import the logical host environment definitions.
Use the jpcconf ha import command to import the exported file of the logical host environment definitions copied from the executing node to the standby node.
For example, execute the following command if the export file name is lhostexp.conf.
jpcconf ha import -f lhostexp.conf
When the command is executed, the environment settings for the standby node are changed to the same environment settings specified for the executing node that has been exported. Therefore, the settings for running PFM - Manager on a logical host are deleted. If you perform unsetup of Performance Management on another logical host, the relevant settings are also deleted.
In this example, the jpcconf ha import command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf ha import command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
-
Check the settings for the logical host environment.
Execute the jpcconf ha list command in the same manner as for the executing node, to check the settings of the logical host.
Execute the command as follows:
jpcconf ha list -key all
For details on the jpcconf ha list command, see the chapters that describe commands in the manual Job Management Partner 1/Performance Management Reference.
(4) Clearing the registration of PFM - Manager in the cluster software
![[Figure]](GRAPHICS/ZU115920.GIF)
Delete the settings related to PFM - Manager on the logical host from the cluster software. For details on how to delete settings, see the cluster software documentation.
(5) Uninstalling PFM - Manager
![[Figure]](GRAPHICS/ZU115920.GIF)
Uninstallation is performed separately for the executing node and the standby node. The uninstallation procedure is the same as for a non-cluster system. For details, see the chapter describing installation and setup (in UNIX) in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Notes:
-
-
When performing uninstallation of PFM - Manager, stop all Performance Management programs and services on the node where uninstallation is to be performed.
-
If uninstallation is performed on Performance Management without deleting the logical host environment, the environment directory might remain. When this happens, delete the environment directory.
-