2.4.7 Adding of a node to be monitored by JP1/Cm2

Function

Adds two or more nodes to be monitored by JP1/Cm2/NNMi.

This service template assumes the following servers as prerequisites:

- NNM server

Server where JP1/Cm2/NNMi is installed

- Node to be monitored

Monitored server or device to be added to JP1/Cm2/NNMi

An outline of the processing is as follows:

1. The node to be monitored is added to JP1/Cm2/NNMi on the NNM 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]

Job Management Partner 1/Automatic Operation 10-50 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

[Prerequisite product OS running in the system executing the service template]

(1) Windows Server 2003 Standard Edition/Enterprise Edition (x86/x64) SP1 or later, Windows Server 2003 R2, Standard Edition/Enterprise Edition (x86/x64)

(2) Windows Server 2008 Standard/Enterprise (x64), Windows Server 2008 R2 Standard/Enterprise/Datacenter

(3) Windows Server 2012 Standard/Datacenter, Windows Server 2012 R2 Standard/Datacenter

(4) Red Hat Enterprise Linux 5 Advanced Platform (AMD/Intel 64), Red Hat Enterprise Linux 5 (AMD/Intel 64)

(5) Red Hat Enterprise Linux Server 6 (64-bit x86_64)

[Usage conditions for the required products for the service template execution system]

(1) The JP1/AO server is capable of resolving the name of a monitored node to be added.

(2) To execute this service, the set agent-less destinations must be a JP1/AO server (having a loopback address to be resolved by "localhost") and an NNM server.

Cautions

(1) Do not execute this service for multiple instances of the same NNM server at a time.

(2) JP1/Cm2/NNMi multi-tenants are not supported. If a tenant is used, move monitored nodes to the tenant manually after adding them.

(3) For JP1/Cm2/NNMi, a seed is registered in order to add a monitored node. It is recommended that the seed be deleted after adding a monitored node.

In this service, no seed is deleted automatically, because it is not determined when a monitored node is added after a seed is added.

For details about a seed, please see the JP1/Cm2/NNMi Release Notes.

Version

01.50.01

Category

JP1_Operations/Configuration

Property list

The following shows the list of the property groups set in the property:

Property group	Description	Initial display
Monitoring system environment information	Specify NNM server environment information.	Y
Monitored node information	Specify information about the monitored node to be added.	Y

The following shows the list of the properties to be displayed in the "Service Definition" dialog box:

(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 or IP address of a server where JP1/Cm2/NNMi is installed. IPv6 addresses are not supported. For a cluster configuration, specify the physical or logical host of the active server.	Input	Disabled	R	Monitoring system environment information
jp1cm2nnm.targetSubnetMask	Subnet mask for the node to be monitored	Specify the subnet mask for the monitored node to be added. (Only one subnet mask can be specified.)	Input	Disabled	O	Monitored node information

The following shows the list of the properties to be displayed on the "Service Definition" dialog box and the "Submit Service" dialog box:

Property key	Property name	Description	I/O type	Shared	Required	Property group
common.foreachIPaddress	IP address of a node to be monitored	Specify the IP address of a monitored node to be added. To specify two or more nodes, separate them with a comma. Up to 99 nodes can be specified. IPv6 addresses are not supported.	Input	Disabled	R	Monitored node information

The following shows the list of the properties to be displayed in the "Task Details" dialog box 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 list of properties used as variables for work to inherit the value in the processing. This property is displayed only in the task log.

Property key	Property name	Description	I/O type	Shared
common.target	Host name of the node to be monitored	Contains the host name of the monitored node to be added.	Variable	Disabled

The following shows the restrictions on inputs to the properties displayed in the "Service Definition" dialog box:

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 -.
jp1cm2nnm.targetSubnetMask	A maximum of 15 characters can be entered. Characters that can be used include alphanumeric characters, as well as . .

The following shows the restrictions on inputs to the property displayed on the "Service Definition" dialog box and the "Submit Service" dialog box:

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	Version	Description	Error recovery method
1	addMonitoredNode	Repeated Execution Plug-in	01.00.00	Adds two or more nodes to be monitored by JP1/Cm2/NNMi.	Remove the cause of the error, and then execute the service again.

To Page Top