2.4.10 Delete monitoring setting
Function
Deletes multiple nodes to be monitored from JP1/Cm2/NNMi or JP1/PFM.
This service template assumes that the following servers are being used.
• NNMi server
Servers with JP1/Cm2/NNMi installed.
• PFM management server
Servers with JP1/PFM - Manager and JP1/PFM - Web Console installed.
• PFM-RM server
Servers with JP1/PFM - RM for Platform installed.
• Monitor server
Servers configured to be monitored by JP1/Cm2/NNMi and JP1/PFM.
The following summarizes the processing.
1. Servers to be monitored are deleted from the NNMi server's JP1/Cm2/NNMi.
2. Monitored servers are deleted from JP1/PFM. The following processing is performed.
(1) In the PFM management server, the alarm table is unbound.
(2) The JP1/PFM - RM for Platform remote agent is deleted for the PFM-RM server.
(3) The Agents tree is set up for the JP1/PFM - Web Console of the PFM management server.
Prerequisites
For the latest support information about [Required product in the System]/[Prerequisite products in the system executing the service template]/[Prerequisite product OS running in the system executing the service template], see the release notes.
[Required product in the System]
JP1/Automatic Operation 12-00 or later
[Prerequisite products in the system executing the service template]
(1) Job Management Partner 1/Cm2/Network Node Manager i 10-00, 10-10, 10-50
JP1/Network Node Manager i 11-00, 11-10, 11-50, 12-00, 12-10, 12-50, 12-60
(2) Job Management Partner 1/Performance Management - Manager 10-00, or
JP1/Performance Management - Manager 11-00 or later
Job Management Partner 1/Performance Management - Web Console 10-00, or
JP1/Performance Management - Web Console 11-00 or later
Job Management Partner 1/Performance Management - Remote Monitor for Platform 10-00, or
JP1/Performance Management - Remote Monitor for Platform 11-00 or later
Job Management Partner 1/Performance Management - Base 10-00, or
JP1/Performance Management - Base 11-00 or later
(3) JP1/PFM - Manager and JP1/PFM - Web Console are installed on the same server.
[Prerequisite product OS running in the system executing the service template]
(1) Windows Server 2008 R2 Standard/Enterprise/Datacenter
(2) Windows Server 2012 Standard/Datacenter, Windows Server 2012 R2 Standard/Datacenter
(3) Windows Server 2016 Standard/Datacenter
(4) Windows Server 2019 Standard/Datacenter
(5) Red Hat Enterprise Linux Server 6 (32-bit x86), Red Hat Enterprise Linux Server 6 (64-bit x86_64)
(6) Red Hat Enterprise Linux Server 7 (64-bit x86_64)
The bind-utils package must be installed.
(7) Red Hat Enterprise Linux Server 8 (64-bit x86_64)
The bind-utils package must be installed.
(8) AIX V6 (This does not apply to NNMi server and PFM-RM server.)
(9) AIX V7 (This does not apply to NNMi server and PFM-RM server.)
[Usage conditions of prerequisite products in the system executing the service template]
(1) If the PFM-RM server is in a cluster configuration, specify the name of the physical host on which the logical host is running in property jp1pfm.pfmRMHostName, and specify the logical host name in property jp1pfm.jp1pfmRMLHostName.
(2) For a JP1/PFM Agents tree to be configured, the following files that are transferred to the PFM management server must be stored on the JP1/AO server.
• Agents tree definition file (the file name specified by jpcconf agttree import) (optional)
If this file name is not specified, the Agents tree is not set up.
• When you specify the above files in properties, specify the transfer source and destination as well.
(3) The names of the monitor server can be resolved on the JP1/AO server.
(4) In order to execute this service, the JP1/AO server (loopback address resolved by localhost) and the server that is the connection destination must be set as agentless connection destinations.
(5) If the alarm table name is blank, the default alarm table for this service template (PFM RM Platform Template Alarms 09.00) is unbound.
(6) The product name display function is enabled on JP1/PFM.
(7) When using JP1/Cm2/NNMi 09-10, make sure that account credentials (the values used as a user name and password when a JP1/Cm2/NNMi script is executed) have already been specified.
Cautions
(1) Do not execute multiple instances of this service simultaneously on the same NNMi server, PFM management server, or PFM-RM server.
(2) IPv6 cannot be specified as the IP address of a monitor server.
(3) If an IP address that is not included in the JP1/PFM monitoring destinations is specified, the service ends abnormally.
(4) There is only one alarm table that is unbound by this service. Do not execute this service on monitor server that bind more than one alarm table.
(5) A maximum of 50 monitor server IP addresses can be specified.
(6) When a monitor server registered as a node in JP1/Cm2/NNMi is not one of the following names, the monitor server cannot be deleted from JP1/Cm2/NNMi.
• Specified IP address
• Host name resolved on the JP1/AO server from the specified IP address
If deletion of a monitor server fails, the service ends abnormally. If the service ends abnormally, manually delete the settings of the monitor server from JP1/Cm2/NNMi and JP1/PFM.
(7) If you are executing this service in a UNIX environment, do not use multibyte characters in properties.
(8) If a file has already been specified as remote, the remote file is overwritten and deleted. For this reason, make sure that the file name is specified correctly.
(9) If there is no folder at the path specified as remote, a folder is created. The created folder is left undeleted. If it is not used periodically, delete it.
Version
03.00.00
Tags
Configure JP1,NNMi,PFM
Property list
The following shows the list of the property groups set in the property:
|
Property group |
Description |
Initial display |
|---|---|---|
|
Monitored system environment information |
Specify environment information for the NNMi server, PFM management server, and PFM-RM server. |
Y |
|
Monitoring information |
Set monitoring information for the monitor server to be deleted. |
Y |
|
Option monitoring information |
Specify the agent hierarchy definition and alarm table settings (unbound) for the PFM management server. |
N |
The following shows the list of the properties to be displayed in the "Service Definition" window:
- (Legend)
-
R: The property must be specified.
O: The property can be omitted. However, the property might be mandatory depending on what is specified for other properties. See the Description of each property.
|
Property key |
Property name |
Description |
I/O type |
Shared |
Required |
Property group |
|---|---|---|---|---|---|---|
|
jp1cm2nnm.nnmHostName |
Host name of NNMi server |
Specify the host name of the server where JP1/Cm2/NNMi is installed. Specify the physical host name of primary server or the logical host name of JP1/Cm2/NNMi (when using JP1/Cm2/NNMi in a cluster configuration). |
Input |
Disabled |
R |
Monitored system environment information |
|
jp1pfm.pfmHostName |
PFM management server host name |
Specify the host name of the server where JP1/PFM - Manager and JP1/PFM - Web Console are installed. Specify the physical host name of primary server or the logical host name of JP1/PFM - Manager (when using JP1/PFM - Manager in a cluster configuration). |
Input |
Disabled |
R |
Monitored system environment information |
|
jp1pfm.pfmRMHostName |
Host name of PFM-RM server |
Specify the host name of the server where JP1/PFM - RM is installed. Specify the physical host name of primary server or the logical host name of JP1/PFM - RM for Platform (when using JP1/PFM - RM for Platform in a cluster configuration). |
Input |
Disabled |
R |
Monitored system environment information |
|
jp1pfm.instance |
Instance name of JP1/PFM - RM |
Specify the name of the instance of JP1/PFM - RM for Platform associated with the remote agent of the monitor server. |
Input |
Disabled |
R |
Monitoring information |
|
jp1pfm.agentLevelDefFileNameLocal |
Agent tree definition file (local) |
Specify the full path of the agent tree definition file to be transferred from the JP1/AO server. If you omit this property, the service will not transfer a file or apply its contents. |
Input |
Disabled |
O |
Option monitoring information |
|
jp1pfm.agentLevelDefFileNameRemote |
Agent tree definition file (remote) |
Specify the full destination path for agent tree definition files to be transferred to the PFM management server. |
Input |
Disabled |
O |
Option monitoring information |
|
jp1pfm.alarmTableName |
Alarm table name |
Specify the alarm table name to unbind from the remote agent on PFM-RM server. |
Input |
Disabled |
O |
Option monitoring information |
|
jp1pfm.jp1pfmLHostName |
Logical host name of JP1/PFM - Manager |
Specify the logical host name of JP1/PFM - Manager (when you are using JP1/PFM - Manager in a cluster configuration). |
Input |
Disabled |
O |
Monitored system environment information |
|
jp1pfm.jp1pfmRMLHostName |
JP1/PFM - RM logical host name |
Specify the logical host name of JP1/PFM - RM (when using JP1/PFM - RM for Platform in a cluster configuration). |
Input |
Disabled |
O |
Monitored system environment information |
The following shows the list of the properties to be displayed on the "Service Definition" window and the "Submit Service" window:
|
Property key |
Property name |
Description |
I/O type |
Shared |
Required |
Property group |
|---|---|---|---|---|---|---|
|
common.foreachIPaddress |
IP address of monitor server |
Specify the IP address of the monitor server. Separate multiple addresses with commas as in the example below. You cannot specify an IPv6 address. |
Input |
Disabled |
R |
Monitoring information |
The following shows the list of the properties to be displayed in the "Task Details" window only:
|
Property key |
Property name |
Description |
I/O type |
Shared |
|---|---|---|---|---|
|
common.taskResult |
Results of repeating tasks |
This property contains the results of each task (as "true" or "false"), in a comma-delimited format. |
Output |
Disabled |
The following shows the restrictions on inputs to the properties displayed in the "Service Definition" window:
|
Property key |
Characters that can be input |
|---|---|
|
jp1cm2nnm.nnmHostName |
A maximum of 255 characters can be entered. Characters that can be used include alphanumeric characters, as well as . and -. |
|
jp1pfm.pfmHostName |
A maximum of 255 characters can be entered. Characters that can be used include alphanumeric characters, as well as . and -. |
|
jp1pfm.pfmRMHostName |
A maximum of 255 characters can be entered. Characters that can be used include alphanumeric characters, as well as . and -. |
|
jp1pfm.instance |
A maximum of 32 characters can be entered. Characters that can be used include alphanumeric character. |
|
jp1pfm.agentLevelDefFileNameLocal |
A character string of no more than 256 characters can be entered. It cannot include <, >, |, ;, &, *, ", ?, !. |
|
jp1pfm.agentLevelDefFileNameRemote |
A character string of no more than 256 characters can be entered. It cannot include <, >, |, ;, &, *, ", `, !. |
|
jp1pfm.alarmTableName |
A character string of no more than 64 characters can be entered. It cannot include \, !, ", #, $, &, ', *, +, :, ;, , , <, >, =, ?, ^, ~, `, {, }, |. |
|
jp1pfm.jp1pfmLHostName |
A maximum of 255 characters can be entered. Characters that can be used include alphanumeric characters, as well as ., - . |
|
jp1pfm.jp1pfmRMLHostName |
A maximum of 255 characters can be entered. Characters that can be used include alphanumeric characters, as well as . and -. |
The following shows the restrictions on inputs to the property displayed on the "Service Definition" window and the "Submit Service" window:
|
Property key |
Characters that can be input |
|---|---|
|
common.foreachIPaddress |
A maximum of 1024 characters can be entered. Characters that can be used include alphanumeric characters, as well as . and , . |
Flow specification details
The following table shows the detailed specification of the flow:
|
Hierarchy |
Display name |
Plug-in |
||
|---|---|---|---|---|
|
Plug-in name |
Description |
Error recovery method |
||
|
1 |
deleteMonitoringConfiguration |
Repeated-execution plug-in |
Deletes multiple monitor servers from JP1/Cm2/NNMi and JP1/PFM. |
Follow the instructions in the jobnet to be repeated. |
|
2 |
setMonitoringTreeConf |
Flow Plug-in |
Configures a JP1/PFM Agents tree. |
-- |
|
2-3 |
Compatible Plug-in |
Ascertains whether an Agents tree definition file has been specified. |
Configure Agents trees manually. |
|
|
2-4 |
Flow Plug-in |
Configures a JP1/PFM Agents tree. |
-- |
|
|
2-4-1 |
File-forwarding plug-in |
Transfers an Agents tree definition file to a PFM management server. |
Configure Agents trees manually. |
|
|
2-4-2 |
Add agent hierarchy setting |
Configures a JP1/PFM Agents tree. |
Configure Agents trees manually. |
|
|
2-4-3 |
Delete file |
Deletes the specified file. |
Delete the file manually. |
|
|
2-5 |
Synchronize service information |
Synchronizes the JP1/PFM - Manager service information to JP1/PFM Web Console. |
When synchronizing service information, execute a jpctool service sync command on the PFM management server. |
|