Job Management Partner 1/Automatic Job Management System 3 Linkage Guide

Appendix 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 A-1 Example of a system configuration for linking with HP NNM

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.

When used as the NNM manager (the host where NNM is installed and which is used for monitoring):

Windows Server 2003
(JP1/AJS3 - Manager or JP1/AJS3 - View)

Windows XP Professional
(JP1/AJS3 - View)

When used as the NNM agent (the host monitored by NNM):

Windows Server 2003
(JP1/AJS3 - Manager or JP1/AJS3 - Agent)

The following figure shows the setup procedure for linking HP NNM.

Figure A-2 Setup procedure for linking HP NNM

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

(2) Setting up the environment for the link

(3) Setting up SNMP trap destinations

(4) Disabling SNMP trap transmission

(5) Customizing the SNMP trap to be sent

(6) Unlinking HP NNM

(7) Cautionary notes on linking HP NNM

(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 Job Management Partner 1/Base User's Guide.

Note

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

To link with HP NNM, use ajsovsetup.bat to set up the environment for the link. Execute the command on both the monitoring side (that is, the host where NNM is installed) and the monitored side (the host where JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed).

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. Execute the following commands to set up the monitoring process. If JP1/AJS3 - Agent is installed, however, you need not set up scheduler status monitoring.
 
cd JP1/AJS3-installed-folder\conf
copy jp1ajs_hstd.conf jp1ajs_hstd.conf.model
copy jp1ajs_hstd_ov.conf.model jp1ajs_hstd.conf
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.

Table A-1 List of environment setting parameters 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

Environment definition file for linkage with HP NNM^#3
(JP1/AJS3-installation-folder\conf\jpoov.conf) [SETSYMBOLCOMMUNITY]= This parameter sets the community name for authenticating SNMP traps (on the NNM manager 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

The parameters that are contained in the environment definition file for linkage with HP NNM but are not described in this manual are for maintenance. Do not change the values of these parameters.

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
Environment definition file for linkage with HP NNM^#3 (JP1/AJS3-installation-folder\conf\jpoov.conf)	[SETSYMBOLCOMMUNITY]=	This parameter sets the community name for authenticating SNMP traps (on the NNM manager side).^#2

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

n 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]
n List of environment setting parameters

Table A-2 Environment setting parameters for customizing the send source host name

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

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

n Customizing the community name for authenticating the SNMP traps on the status-monitoring host (where NNM is installed)

To change the community name of the SNMP traps for the JP1/AJS3 objects of the status-monitoring host (where NNM is installed), specify the new community name in environment definition file for linkage with HP NNM (JP1/AJS3-installation-folder\conf\jpoov.conf). You can use 255 or fewer bytes to specify the community name. The following shows the entry in the environment definition file.

[SETSYMBOLCOMMUNITY]=community-name-for-authentication

If you specify a character string longer than 255 bytes, the first 255 bytes are used as the community name. The community name setting is applied immediately. The default community name is public.

Cautionary note

To receive customized SNMP traps with NNM on a Windows host, you must disable the use of WinSNMP in NNM. For details about disabling the use of WinSNMP, see the ovtrapd section in the NNM Runtime Help.

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"

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"

(6) Unlinking HP NNM

This subsection describes the procedure for unlinking HP NNM.

(a) Unlinking HP NNM on the monitored side (where JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed)

To unlink HP NNM on the monitored side (where JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed):

Delete the host where NNM is installed from the trap destinations specified in the SNMP service setup.

Execute ajsovremove.bat.

(b) Unlinking HP NNM on the monitoring side (where NNM is installed)

To unlink HP NNM on the monitoring side (where NNM is installed):

Unlink HP NNM in all hosts that are the status monitoring targets and where JP1/AJS3 - Manager or JP1/AJS3 - Agent is installed.
For details on how to unlink HP NNM from JP1/AJS3 - Manager or JP1/AJS3 - Agent, see (a) above.

Execute ajsovsymrem.bat in the monitoring host.

If the NNM window is not open, open it.

In the NNM window, choose Administer, JP1/AJS2 Manager, Create symbol, and For All hosts.
JP1/AJS3 symbols are deleted from the submap of all hosts.

Open the submap that contained the JP1/AJS3 symbols, and then choose Map, Submap, and Properties.
The Submap Context dialog box appears.

Select isJP1AJS2ObjExist, and delete it.

Close the NNM window.

Execute ajsovremove.bat.
The HP NNM link for JP1/AJS3 is deleted from NNM.

(c) Unlinking HP NNM when the same host serves as the monitored side (where JP1/AJS3 is installed) and monitoring side (where NNM is installed)

To unlink the HP NNM in a situation where the same host serves as the monitored side (where JP1/AJS3 is installed) and monitoring side (where NNM is installed):

Delete the local host from the trap destinations specified in the SNMP service setup.

Execute ajsovsymrem.bat.

Open the NNM window if not already open.

In the NNM window, choose Administer, JP1/AJS2 Manager, Create symbol, and For All hosts.
JP1/AJS3 symbols are deleted from the submap of all hosts.

Open the submap that contained the JP1/AJS3 symbols, and then choose Map, Submap, and Properties.
The Submap Context dialog box appears.

Select isJP1AJS2ObjExist, and delete it.
The JP1/AJS3 context is deleted from the submap on which the JP1/AJS3 symbols were located.

Close the NNM window.

Execute ajsovremove.bat.
The HP NNM link definition for JP1/AJS3 is deleted from NNM.

(7) Cautionary notes on linking HP NNM

(a) Cautionary notes on the HP NNM linkage function
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.
The following table shows the NNM files configured in JP1/AJS3.

Table A-4 The NNM files configured in JP1/AJS3
File types File names
Trap action definition
NNM-install-folder\conf\$LANG\trapd.conf
Field definition
NNM-install-folder\fields\C\jp1ajs2_f
Application definition
NNM-install-folder\registration\$LANG\jp1ajs2_{j|e}
Trusted command definition
NNM-install-folder\conf\trustedCmds.conf\trustajs2
Do not modify these files from their original state. Symbols might not display in NNM if these files are modified.
(b) Cautionary notes for the NNM host side

Make sure that the NNM service is running and the NNM window is closed when you execute ajsovsetup.bat or ajsovremove.bat.

Executing the ajsovsetup.bat command, automatically displays the NNM console. If you do not want to display it, add the component name to the following NNM registry key:

NNM registry key

OVConsole\CannotLaunchViewer

Component name to be added

ovw

For details, see the description of ovconsole in NNM Reference Page.

If the agent host is renamed, NNM might display identical symbols (one for the previous host name and the other for the new host name) on the node submap for that host. In this case, delete the symbol whose status does not change in response to a trap, or delete both symbols and display a symbol with a new trap.

Do not change the object attributes for symbols that JP1/AJS3 manages, or the selection name.

If you change the node submap selection name to a name other than the host name, the JP1/AJS3 symbol might not be created. To specify a name other than the host name for the node submap selection name, change the node submap selection name to the host name and create the JP1/AJS3 symbol. Then change the selection name to a name other than the host name.

To use HP NNM linkage, you need to set All Levels for the fixed submap level (on-demand submap).
To do so, display the IP Map settings for NNM in the map properties, then check and change the fixed submap level.

When the alarm browser in NNM is stopped, even if a trap is received from the monitored host (where JP1/AJS3 is installed), the colors of the symbols do not correspond to the received statuses. Even if the symbols are reset, the statuses of the symbols are unchanged.

Immediately after the system is configured or if a node corresponding to the agent host is deleted, an error message indicating that no status color can be set up might appear. Restarting NNM or choosing Administer, JP1/AJS2 Manager, Create symbol, and For All hosts from the NNM menus will suppress this error message.

(c) Cautionary notes for the NNM agent side

If the agent host uses a long host name due to the presence of a DNS (Domain Name System) 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.

File types	File names
Trap action definition	NNM-install-folder\conf\$LANG\trapd.conf
Field definition	NNM-install-folder\fields\C\jp1ajs2_f
Application definition	NNM-install-folder\registration\$LANG\jp1ajs2_{j\|e}
Trusted command definition	NNM-install-folder\conf\trustedCmds.conf\trustajs2

[Contents][Back][Next]

[Trademarks]