A.2 Setup for linking HP NNM (for a Windows host)
When linking HP NNM for monitoring of JP1/AJS3 - Manager and JP1/AJS3 - Agent from NNM, install either JP1/AJS3 - Manager or JP1/AJS3 - View in the host where NNM is installed.
The following figure shows an example of a system configuration for linking with HP NNM.
|
|
![[Figure]](GRAPHICS/ZUL14010.GIF)
In this example, the OpenView Status Report action job is defined and executed using JP1/AJS3 - View for monitoring the status of JP1/AJS3 - Manager and JP1/AJS3 - Agent from NNM in the host where JP1/AJS3 - View is placed.
HP NNM can be linked using the operating systems listed below. If you use JP1/AJS3 as the NNM manager (monitoring host on which NNM is installed), note that NNM does not support the OS versions supported by JP1/AJS3 11-00 or later. To use JP1/AJS3 as the NNM manager, the version of JP1/AJS3 must be 10-50 or earlier.
- When used as the NNM agent (the host monitored by NNM):
-
-
Windows Server 2022#1, Windows Server 2019#1, Windows Server 2016#1, Windows Server 2012, or Windows Server 2012 R2#2
(JP1/AJS3 - Manager or JP1/AJS3 - Agent)
- #1
-
HP NNM can be used when the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent is 11-10 or later.
- #2
-
HP NNM can be used when the version of JP1/AJS3 - Manager or JP1/AJS3 - Agent is 10-00 or later.
-
- Supplementary note
-
When JP1/AJS3 sends SNMP traps as an NNM agent, JP1/AJS3 use the Windows SNMP service to obtain the destinations of the SNMP traps.
The Windows SNMP service is therefore a prerequisite for sending SNMP traps.
The following figure shows the setup procedure for linking HP NNM.
|
|
![[Figure]](GRAPHICS/ZUL14020.GIF)
For further details regarding the setup of HP NNM, see the documentation for HP NNM.
The subsections below describe how to define the SNMP service startup timing and environment settings for a link.
- Organization of this subsection
(1) Defining the SNMP service startup timing
To issue an SNMP trap correctly when starting up or terminating the JP1/AJS3 service, set up the order in which the SNMP service or NNM and the JP1/AJS3 service are activated.
To specify the order of startup, use the startup management function of JP1/Base.
In the host in which NNM is set up, specify the startup so that NNM is activated first and JP1/AJS3 service is activated next. In the host to be monitored by NNM, specify the startup so that the SNMP service is activated first, followed by the JP1/AJS3 service.
For details on the startup management function of JP1/Base, see the JP1/Base User's Guide.
- Important
-
If the HP NNM service has not been activated in the host where NNM is set up when an SNMP trap is issued, the trap might not be reported. The issued SNMP trap also might not be reported depending on the network status because it uses the UDP protocol. The SNMP trap also might not be reported depending on its characteristics. When this occurs, note that SNMP traps are issued but might not be reflected in NNM.
(2) Setting up the environment for the link
If the status of the scheduler is to be monitored, it necessary to set up a monitoring process that monitors the status of the scheduler at 5-minute intervals and, when the status changes, issues snmptrap. To set up a monitoring process, edit the jp1ajs_hstd.conf file as shown below. Note that you need to specify the settings for monitoring the scheduler status only if you want to monitor the scheduler status. You do not need to specify those settings for JP1/AJS3 - Agent.
-
If the jp1ajs_hstd.conf file has been altered to set up a standard configuration without ISAM or to configure a queueless job execution environment:
Back up the jp1ajs_hstd.conf file, and then append the following line to the end of the file:
ajsovstatd|ajsovstatd.exe|||1800|
-
In all other scenarios:
Back up the jp1ajs_hstd.conf file, and then replace the jp1ajs_hstd.conf with the jp1ajs_hstd_ov.conf.model file.
The jp1ajs_hstd.conf file is stored in the JP1/AJS3-installation-folder\conf folder.
To change the SNMP traps to be sent for linkage with HP NNM according to the operating environment, set the required environment setting parameters in the JP1/Base common definition and in the environment definition file for linkage with HP NNM. The following table lists the environment setting parameters required for linkage with HP NNM.
|
Location |
Parameter name |
Description |
|
|---|---|---|---|
|
Common definition |
[JP1_DEFAULT\JP1AOMAGENT\ov_link] |
"TRAPRESTRAIN"= |
This parameter sets whether to suppress sending SNMP traps.#1 |
|
[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT\ov_link] |
"SNMPTRAPCUSTOM"= |
This parameter sets the reference level for customization information during SNMP trap sending.#2 |
|
|
"TRAPAGENTADDRHOST"= |
This parameter sets the name of the host that sends SNMP traps.#2 |
||
|
"TRAPAGENTADDRIP"= |
This parameter sets the IP address of the host that sends SNMP traps.#2 |
||
|
"CUSTOMCOMMUNITY"= |
This parameter sets the community name for authenticating SNMP traps (on the NNM agent side).#2 |
||
- #1
-
For details about this environment setting parameter, see (4) Disabling SNMP trap transmission.
- #2
-
For details about this environment setting parameter, see (5) Customizing the SNMP trap to be sent.
(3) Setting up SNMP trap destinations
In the host (where JP1/AJS3 - Manager or JP1/AJS3 - Agent to be monitored is installed) monitored by NNM, it is necessary to set up the community name of the SNMP service and the destination to which the trap is to be sent. The community name must be Jp1Trap, and the destination to which the trap is to be sent must be the host name of the manager (where NNM is installed) or one or more IP addresses.
If the NNM agent is to be managed in a cluster system, each node must have a monitoring host specified as the destination to which the trap is to be sent.
(4) Disabling SNMP trap transmission
The JP1/AJS3 service transmits SNMP traps that are used for JP1/AJS3 objects to NNM. To disable SNMP trap transmission from JP1/AJS3, you must specify it in the JP1/Base common definition information, using the following procedure. To disable SNMP trap transmission:
-
Execute the following command:
jajs_config -k "[JP1_DEFAULT\JP1AOMAGENT\ov_link]" "TRAPRESTRAIN"="Y"
In the TRAPRESTRAIN parameter, specify whether to disable SNMP trap transmission. If you want to disable SNMP trap transmission, specify Y. If you do not want to disable it, specify N. The default is N. If you do not want to disable SNMP trap transmission, substitute N for Y in the following information. If you specify any value other than Y or N, an error will occur during trap transmission.
(5) Customizing the SNMP trap to be sent
(a) Customizing the send source host name
For sending SNMP traps for JP1/AJS3 objects, the name and IP address of a physical host are generally set for the send source host. If the host sending SNMP traps has more than one IP address, you may have to explicitly specify the name of the send source host. Specify the name of the host sending SNMP traps in the following cases:
-
When NNM is set not to recognize the logical host, a clustered JP1/AJS3 node might send an SNMP trap for which the logical host name is set as the send source host name. In this case, set the physical host name as the send source host name.
-
When NNM is set to recognize the logical host, a clustered JP1/AJS3 node might send an SNMP trap for which the physical host name is set as the send source host name. In this case, set the logical host name as the send source host name.
To customize the name of the host sending the SNMP trap to be sent, you need to set up the JP1/Base common definition information so that the customization information is referenced when the SNMP trap is sent.
■ Setting procedure
To customize the SNMP trap:
-
Execute the following command to set the environment setting parameters.
jajs_config -k definition-key-name "environment-setting-parameter-1"=definition-content-1 ["environment-setting-parameter-2"=definition-content-2] ["environment-setting-parameter-3"=definition-content-3]
■ List of environment setting parameters
|
Definition key |
Environment setting parameter |
Defined information |
|---|---|---|
|
[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT\ov_link]#1 |
"SNMPTRAPCUSTOM"=#2 |
dword:{0|1|2} |
|
"TRAPAGENTADDRHOST"=#3 |
"agent-host-name" |
|
|
"TRAPAGENTADDRIP"=#4 |
"IP-address" |
- #1
-
The {JP1_DEFAULT|logical-host-name} part indicates that you must specify JP1_DEFAULT for the physical host and logical-host-name for the logical host.
- #2
-
The SNMPTRAPCUSTOM environment settings parameter specifies whether to reference the customization information when the SNMP trap is sent. Specify 1 to reference the send source host name. Otherwise, specify 0. The default is 1.
- #3
-
In the TRAPAGENTADDRHOST environment settings parameter, specify the name of the host that sends the SNMP trap. Use up to 255 bytes. The default is the name of the physical host that sends the SNMP trap.
- #4
-
In the TRAPAGENTADDRIP environment settings parameter, specify the IP address of the host that sends the SNMP trap. The default is the IP address of the physical host that sends the SNMP trap.
(b) Customizing the community name for authentication
■ Customizing the community name for authenticating the SNMP traps on the status-monitored host (where JP1/AJS3 is installed)
You may want to customize the community name for authenticating the SNMP traps for the JP1/AJS3 objects of the status-monitored host (where JP1/AJS3 is installed). To do this, specify the settings for referencing the customization information in the JP1/Base common definition.
To specify the settings for referencing the customization information in the JP1/Base common definition:
-
Execute the following command to set the environment setting parameters.
jajs_config -k definition-key-name "environment-setting-parameter-1"=definition-content-1 ["environment-setting-parameter-2"=definition-content-2]
Table A‒3: Environment setting parameters for customizing the community name for authentication Definition key
Environment setting parameter
Defined information
[{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT\ov_link]#1
"SNMPTRAPCUSTOM"=#2
dword:{0|1|2}
"CUSTOMCOMMUNITY"=#3
"community-name-for-authentication"
- #1
-
The {JP1_DEFAULT|logical-host-name} part indicates that you must specify JP1_DEFAULT for the physical host and logical-host-name for the logical host.
- #2
-
The SNMPTRAPCUSTOM environment settings parameter specifies whether to reference the customization information when the SNMP trap is sent. Specify 2 to reference the community name for authentication. The default is 1.
- #3
-
In the CUSTOMCOMMUNITY environment settings parameter, specify the community name for authentication. Use up to 255 bytes. The default is public.
- Cautionary notes
-
-
To customize both the send source host name and the community name for authentication, specify 2 for the SNMPTRAPCUSTOM parameter and specify either the TRAPAGENTADDRHOST or TRAPAGENTADDRIP parameter with the CUSTOMCOMMUNITY parameter.
-
To use NNM for the Windows host to receive the customized SNMP trap, you must set up NNM so that it will not use WinSNMP. For details, see the description of ovtrapd in NNM Run-time Help.
-
(6) Unlinking HP NNM
To disable linkage with HP NNM on the monitored side (where JP1/AJS3 is installed), from the list of trap destinations in the SNMP service settings, delete the host on which NNM is installed.
(7) Cautionary notes on linking HP NNM
(a) General notes
-
We recommend that you set up NNM so that it will not recognize a logical host when monitoring nodes in a cluster system. Because the JP1/AJS3 trap is transmitted with a physical host name specified as a key, no JP1/AJS3 symbol can be displayed if NNM recognizes the nodes by logical host names. When linking JP1/AJS3 with HP NNM, set up NNM in such a way that it will not recognize logical hosts or customize the SNMP trap to be sent.
For details on how to customize the SNMP trap to be sent, see (5) Customizing the SNMP trap to be sent. For details on how to set up NNM, see the documentation for HP NNM.
-
If an SNMP trap contains text whose character encoding is different from the NNM language environment, the reported data is corrupted and will not be displayed correctly in Alarms Browser. Therefore, make sure that the language environment settings of NNM and JP1/AJS3 match if you use multi-byte characters for the following items:
-
Root jobnet name
This information is included in an SNMP trap issued when a root jobnet terminates abnormally.
-
Additional information for the OpenView Status Report Job
This information is included in an SNMP trap issued when the OpenView Status Report Job is executed.
-
(b) Cautionary notes for the NNM agent side
-
If the agent host uses a long host name due to the presence of a DNS or some other reason, ensure that the name of the monitored host (the host where JP1/AJS3 is installed) does not exceed 228 bytes.
In addition, when JP1/AJS3 on a logical host is monitored, the sum of the lengths of the physical host name and the logical host name must not exceed 246 bytes.
If the host names exceed this length, symbols are not created in NNM.
-
An SNMP trap that notifies an abnormal termination of a jobnet is sent when the root jobnet terminates abnormally.