Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Linkage Guide

A.3 Setup for linking HP NNM (for a UNIX 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‒3: Example of a system configuration for linking with HP NNM

[Figure]

In this example, the OpenView Status Report action job is defined and executed using JP1/AJS3 - View installed in the Windows host 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. Note that if you use a JP1/AJS3 host as an NNM manager (monitoring host on which NNM is installed), JP1/AJS3 12-00 or later supports no OS that allows use as an NNM manager. To use a JP1/AJS3 host as an NNM manager, make sure that the version of JP1/AJS3 is 11-50 or earlier.

OSs that can be used for NNM agents (hosts monitored by NNM) are as follows:

Supplementary note

JP1/AJS3 uses the following functions and files of Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent or HP Software Extensible SNMP Agent as the NNM agent:

  • SNMP trap destination referencing

  • snmptrap command

  • Extensible MIB definition file

For this reason, Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent or HP Software Extensible SNMP Agent is required as a prerequisite program.

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

Figure A‒4: Setup procedure for linking HP NNM

[Figure]

For details on how to set up HP NNM, see the relevant manual or the HP NNM documentation.

For details on setting up Job Management Partner 1/Consolidated management 2/Extensible SNMP Agent or HP Software Extensible SNMP Agent, see the manual Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent or the HP NNM document.

The subsections below describe environment settings for a link.

Organization of this subsection

(1) Setting up the environment for the link

To link with HP NNM, use the ajsovsetup command 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 is 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. However, if JP1/AJS3 - Agent is installed or the status of the scheduler is not to be monitored, you do not need to specify the settings for monitoring the scheduler status.

The jp1ajs_hstd.conf file is stored in the /etc/opt/jp1ajs2/conf directory.

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‒4: 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
#1

For details about this environment setting parameter, see (2) Disabling SNMP trap transmission.

#2

For details about this environment setting parameter, see (3) Customizing the SNMP trap to be sent.

To Page Top

(2) 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:

  1. 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 anything other than Y or N, an error will occur during trap transmission.

To Page Top

(3) 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:

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

Table A‒5: 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

SNMP traps for JP1/AJS3 objects use public as the community name for authentication. To customize the community name for authenticating the send SNMP traps, you must specify the settings so that the customization information be referenced during sending of SNMP traps.

■ Customizing the community name for authenticating the SNMP traps on the status-monitored host (where JP1/AJS3 is installed)

To customize the community name to authenticate the SNMP traps for JP1/AJS3 objects on the status-monitored host (where JP1/AJS3 is installed), specify the settings for referencing the customization information in the JP1/Base common definition. The procedure is as follows.

To customize the community name for authenticating the SNMP traps on the status-monitored host:

  1. 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‒6: 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}

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

To Page Top

(4) Unlinking HP NNM

To unlink HP NNM on the monitored side (where JP1/AJS3 is installed), use the following procedure.

To unlink HP NNM on the monitored side:

  1. To disable SNMP trap transmission, you must specify it.

    For details on how to disable SNMP trap transmission, see (2) Disabling SNMP trap transmission.

  2. Execute the ajsovremove command.

To Page Top

(5) 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 (3) Customizing the SNMP trap to be sent. For details on how to set up NNM, see the HP NNM documentation.

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

  • The following table shows the NNM files configured in JP1/AJS3.

    Table A‒7: The NNM files configured in JP1/AJS3

    Purpose of file

    File names

    Trap action definition

    /etc/opt/OV/share/conf/$LANG/trapd.conf

    Field definition

    /etc/opt/OV/share/fields/C/jp1ajs2_f

    Application definition

    /etc/opt/OV/share/registration/$LANG/jp1ajs2

    Trusted command definition

    /etc/opt/OV/share/conf/trustedCmds.conf/trustajs2

    Extended user MIB definition

    /etc/SnmpAgent.d/snmpd.extend

    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 agent side

  • SNMP traps might fail to send if the process that controls the sending of SNMP traps is inactive, for example. Because different software controls the sending of SNMP traps in different ways, the cause of the error might differ depending on the software. On the host from which SNMP traps are sent (the host where JP1/AJS3 is installed), make sure that SNMP traps can be sent correctly.

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

  • When the ajsovsetup command is executed, JP1/AJS3 MIB definition information is added to the extended MIB definition file. When the ajsovremove command is executed, JP1/AJS3 MIB definition information is deleted from the extended MIB definition file. Note that the changes to the extended MIB definition file are applied when the SNMP agent is restarted.

    For details about restarting the SNMP agent, see the Job Management Partner 1/Consolidated Management 2/Extensible SNMP Agent Description, Operator's Guide and Reference.

  • An SNMP trap that notifies an abnormal termination of a jobnet is sent when the root jobnet terminates abnormally.

To Page Top

Copyright (C) 2019, 2022, Hitachi, Ltd.

Copyright (C) 2019, 2022, Hitachi Solutions, Ltd.