2.4.12 Add monitoring setting

Function

Adds multiple servers to be monitored to JP1/Cm2/NNMi and JP1/PFM.

This service template assumes that the following servers are being used.

• NNM 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. Nodes to be monitored are added to JP1/Cm2/NNMi on the NNM server.

2. The following monitoring conditions are set up in JP1/PFM.

(1) A remote agent is added to the PFM-RM server.

For the monitored server name, specify a host name resolved from an IP address specified by property common.foreachIPaddress.

(2) The performance data recording method for the added remote agent is changed.

(3) The performance data storage conditions for the added remote agent are changed.

(4) Process monitoring is set up for the added remote agent.

(5) The alarm table is bound for the added remote agent.

(6) 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 NNM server and PFM-RM server.)

(9) AIX V7 (This does not apply to NNM server and PFM-RM server.)

[Usage conditions of prerequisite products in the system executing the service template]

(1) The following files for transfer to the JP1/PFM server are stored on the JP1/AO server.

• Definition file to be monitored (file name specified with jpcconf target setup command) (required)

However, specify the following value in Target Host within the definition file to be monitored.

#AGENTNAME#

If you are setting the user name and password of the connection destination information in multiple monitor servers, set the same information as that specified in the definition file to be monitored.

• 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.

• Recording methods definition file (the file name specified by the jpcasrec update command) (optional)

If this file name is not specified, the performance data recording method is not set.

Specify the following values for the id field of the service tag in the file.

• Storage conditions definition file (the file name specified by the jpcaspsv update command) (optional)

If this file name is not specified, the performance data storage conditions are not set.

Specify the id field of the service tag in the file as follows to switch values in the specified property.

• Application definition file (the file name specified by the jpcprocdef create command) (optional)

If this file name is not specified, the application definition is not set.

Note: When you specify the above files in the properties, specify the transfer source and transfer destination as well.

(2) The names of the monitor servers can be resolved on the JP1/AO server.

(3) JP1/PFM - Manager is running.

(4) The product name display function is enabled on JP1/PFM.

(5) The alarm table to be bound by JP1/PFM has been created. (If blank, the default alarm table for this service template (PFM RM Platform Template Alarms 09.00) is bound.)

(6) The JP1/PFM - RM for Platform interface has been created.

(7) If you are configuring multiple monitor servers, each server must be on the same subnet. (Only one subnet mask can be specified.)

(8) If the PFM management server is in a cluster configuration, specify the name of the physical host on which the logical host is running in property jp1pfm.pfmHostName, and specify the logical host name in property jp1pfm.jp1pfmLHostName.

(9) 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.

(10) In the PFM management server, the JP1/PFM authentication key has been created.

(11) In order to execute this service, you must set the JP1/AO server (loopback address resolved by ""localhost"") and the server that is the connection destination as agentless connection destinations.

Cautions

(1) Do not execute multiple instances of this service simultaneously on the same NNM server, PFM management server, or PFM-RM server.

(2) IPv6 cannot be specified as the IP address of a monitoring destination.

(3) JP1/Cm2/NNMi does not support multiple tenants, so if you are using tenants, add a node, and then move the node to the tenant manually.

(4) With JP1/Cm2/NNMi, seeds are registered for adding nodes. With JP1/Cm2/NNMi, Hitachi recommends deleting these seeds after the nodes are added. Seeds cannot be deleted automatically, because the timing when nodes are added after seeds is undefined with this service. For details about seeds, see the JP1/CM2/NNMi release notes.

(5) Different OSes can be monitored, depending on the OS on which JP1/PFM - RM for Platform is running.

With JP1/PFM - RM for Platform (Linux), only UNIX and Linux can be monitored.

With JP1/PFM - RM for Platform (Windows), Windows, UNIX, and Linux can be monitored:

(6) Depending on the combination of PFM-RM server and monitor server, ssh authentication and wmi authentication may require separate configurations.

(7) Up to 50 remote agents can be registered per instance of JP1/PFM - RM for Platform. Do not specify more than the maximum of 50 as monitor server IP addresses.

(8) If you are executing this service in a UNIX environment, do not use multibyte characters in properties.

(9) If you specify multibyte characters, and the PFM-RM server OS is Windows, specify a path for the monitoring target definition file (remote) that is no longer than 250 bytes.

(10) 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.

(11) 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.

(12) Sometimes the plugin for adding monitoring settings or the plugin for setting Store database save conditions might end abnormally, and the following message might be output to the task log:

"KNAE08132-E Processing was canceled because the maximum limit on the standard output size for commands was exceeded. (maximum = 100 KB)"

If the above problem occurs, reduce the number of service IDs (<Service> tags) written in the file specified for the recording method definition file (local) property, or written in the file specified in the save-conditions definition file (local) property. After that, retry the operation.

(13) Do not execute this service on monitored servers that have already been added, except when the service must be re-executed to recover from a job error.

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 NNM server, PFM management server, and PFM-RM server.	Y
Monitoring information	Set monitoring information for the monitor server to be added.	Y
Option monitoring information	Specify definitions of the agent hierarchy for the PFM management server, definitions related to storage conditions for the Store database, application definitions for process monitoring settings, and information on alarm table settings (bindings).	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	NNMi server host name	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.	Input	Disabled	R	Monitored system environment information
jp1pfm.pfmHostName	PFM management server host name	Specifies the host name of the server where JP1/PFM - Manager and JP1/PFM - Web Console are installed. In the case of a cluster configuration, specify the physical host or logical host of the active server.	Input	Disabled	R	Monitored system environment information
jp1pfm.pfmRMHostName	Host name of PFM-RM server	Specifies the host name of the server where JP1/PFM - RM for Platform is installed. In the case of a cluster configuration, specify the physical host or logical host of the active server.	Input	Disabled	R	Monitored system environment information
jp1cm2nnm.targetSubnetMask	Subnet mask of monitor server	Specify the subnet mask of the monitor server. You cannot specify more than one subnet mask. This property is mandatory when you are using JP1/Cm2/NNM.	Input	Disabled	O	Monitoring 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.agentDefFileLocal	Monitoring target definition file (local)	Specify the full path of the monitoring target definition file to be transferred from the JP1/AO server.	Input	Disabled	R	Monitoring information
jp1pfm.agentDefFileRemote	Monitoring target definition file (remote)	Specify the full destination path for the monitoring target definition files to be transferred to the PFM-RM server.	Input	Disabled	R	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
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.paramDefFileLocal	Recording method definition file (local)	Specify the full path of the recording method definition file to be transferred from the JP1/AO server. If you omit this property, the service will not transfer the file or apply its contents.	Input	Disabled	O	Option monitoring information
jp1pfm.paramDefFileRemote	Recording method definition file (remote)	Specify the full destination path for the recording method definition files to be transferred to the PFM management server.	Input	Disabled	O	Option monitoring information
jp1pfm.saveConditionDefFileNameLocal	Storage conditions definition file (local)	Specify the full path of the storage conditions definition file to be transferred from the JP1/AO server. If you omit this property, the service will not transfer the file or apply its contents.	Input	Disabled	O	Option monitoring information
jp1pfm.saveConditionDefFileNameRemote	Storage conditions definition file (remote)	Specify the full destination path for storage conditions definition files to be transferred to the PFM management server.	Input	Disabled	O	Option monitoring information
jp1pfm.procMonDefFileLocal	Application definition file (local)	Specify the full path of the application definition file to be transferred from the JP1/AO server. If you omit this property, the service will not transfer the file or apply its contents.	Input	Disabled	O	Option monitoring information
jp1pfm.procMonDefFileRemote	Application definition file (remote)	Specify the full destination path for the application 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 to bind to the remote agent on the PFM-RM server.	Input	Disabled	O	Option monitoring 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 -.
jp1cm2nnm.targetSubnetMask	A maximum of 15 characters can be entered. Characters that can be used include alphanumeric characters, as well as . .
jp1pfm.instance	A maximum of 32 characters can be entered. Characters that can be used include alphanumeric character.
jp1pfm.agentDefFileLocal	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", ?, !.
jp1pfm.agentDefFileRemote	A character string of no more than 250 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 -.
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.paramDefFileLocal	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", ?, !.
jp1pfm.paramDefFileRemote	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", !, `.
jp1pfm.saveConditionDefFileNameLocal	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", ? or !.
jp1pfm.saveConditionDefFileNameRemote	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", !, or `.
jp1pfm.procMonDefFileLocal	A character string of no more than 256 characters can be entered. It cannot include <, >, \|, ;, &, *, ", ?, !.
jp1pfm.procMonDefFileRemote	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 \, !, ", #, $, &, ', *, +, :, ;, , , <, >, =, ?, ^, ~, `, {, }, \|.

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
Hierarchy	Display name	Plug-in name	Description	Error recovery method
1	addMonitoringConfiguration	Repeated-execution plug-in	Adds monitor server to NNM server's JP1/Cm2/NNMi	Eliminate the cause of the error, and then re-execute the service.
2	addMonitoringTreeConf	Flow Plug-in	Adds remote agent to JP1/PFM.	--
2-3		Compatible Plug-in	Ascertains whether an Agents tree definition file has been specified.	Eliminate the cause of the error, and then re-execute the service.
2-4		Flow Plug-in	Configures a JP1/PFM Agents tree.	Eliminate the cause of the error, and then re-execute the service.
2-4-1		File-forwarding plug-in	Transfers an Agents tree definition file to a PFM management server.	Eliminate the cause of the error, and then re-execute the service.
2-4-2		Add agent hierarchy setting	Configures a JP1/PFM Agents tree.	Eliminate the cause of the error, and then re-execute the service.
2-4-3		Delete file	Deletes the specified file.	Eliminate the cause of the error, and then re-execute the service.

To Page Top