2.4.3 Deletion of nodes monitored by JP1/Cm2
Function
Deletes two or more nodes from those monitored by JP1/Cm2/NNMi.
This service template assumes the following servers as prerequisites:
- NNMi server
Server where JP1/Cm2/NNMi is installed
- Monitored node
Server or device to be deleted from those monitored by JP1/Cm2/NNMi
An outline of the processing is as follows:
1. The IP address of the specified monitored node is deleted from the JP1/Cm2/NNMi seed on the NNMi server.
2. The monitored node is deleted from JP1/Cm2/NNMi on the NNMi server.
Prerequisites
For the latest support information about [Prerequisite products in the system executing the service template]/[Prerequisite product OS running in the system executing the service template], see the release notes.
In addition, the following OS and products use abbreviations. For the abbreviations of OS and products, see the "Preface".
[Prerequisite products in the system executing the service template]
(1) JP1/NNMi
[Prerequisite product OS running in the system executing the service template]
(1) Windows Server
(2) Red Hat Enterprise Linux Server
The bind-utils package must be installed.
[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 deleted.
(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 NNMi server.
Cautions
(1) Do not execute this service for multiple instances of the same NNMi server at a time.
(2) To delete a monitoring node from this service, either of the following names must match the value of the [hostname] or [mgmtIPAddress] of a monitored node registered in JP1/Cm2/NNMi:
- IP address specified in the IP address property (common.foreachIPaddress) of the monitored node
- Host name resolved on the JP1/AO server from the IP address specified in the IP address property (common.foreachIPaddress) of the monitored node
Each property of a monitored node registered in JP1/Cm2/NNMi might be changed, based on a result of communication with the node or name resolution. When executing this service, make sure that the above conditions are met. If the service fails to delete a monitored node, the service will end abnormally. If the service ends abnormally, manually delete the monitored node from JP1/Cm2/NNMi.
Version
04.00.00
Tags
Configure JP1,NNMi
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 NNMi server environment information. |
Y |
Monitored node information |
Specify information about the monitored node to be deleted. |
Y |
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 an NNMi server |
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 |
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 a node to be monitored |
Specify the IP address of a monitored node to be deleted. 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" 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 -. |
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 |
deleteMonitoredNode |
Repeated Execution Plug-in |
Deletes two or more nodes from those monitored by JP1/Cm2/NNMi. |
Follow the instructions in the repeated jobnet. |