Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/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.

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

  • Solaris

    (JP1/AJS3 - Manager)

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

  • Solaris

    (JP1/AJS3 - Manager or JP1/AJS3 - Agent)

  • AIX

    (JP1/AJS3 - Manager or JP1/AJS3 - Agent)

  • Linux

    (JP1/AJS3 - Manager or JP1/AJS3 - Agent)

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. If JP1/AJS3 - Agent is installed, however, you need not set up scheduler status monitoring.

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

(/etc/opt/jp1ajs2/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 (2) Disabling SNMP trap transmission.

#2

For details about this environment setting parameter, see (3) 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.

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‒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}

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

■ 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 JP1/AJS3 objects on the status-monitoring host (where NNM is installed), specify the new community name in the environment definition file for linkage with HP NNM (/etc/opt/jp1ajs2/conf/jpoov.conf). You can specify a character string not longer than 255 bytes. 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 notes

  • If you want to specify a community name that includes spaces, enclose the community name in double quotation marks (").

  • On a host where only JP1/AJS3 - View is installed, the name of the environment definition file for linkage with HP NNM is /etc/opt/jp1ajs2v/conf/jpoov.conf.

To Page Top

(4) Unlinking HP NNM

This subsection describes the procedure for unlinking HP NNM.

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

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.

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

To unlink HP NNM on the status monitoring side (where NNM is installed), use the following procedure.

To unlink HP NNM on the status monitoring side:

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

  2. Execute the ajsovsymrem command in the monitoring host.

  3. If the NNM window is not open, open it.

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

  5. Open the submap that contained the JP1/AJS3 symbols, and then choose Map, Submap, and Properties.

    The Submap Context dialog box appears.

  6. Select isJP1AJS2ObjExist, and delete it.

    The JP1/AJS3 context is deleted from the submap on which the JP1/AJS3 symbols were.

  7. Close the NNM window.

  8. Execute the ajsovremove command.

    The HP NNM link definition 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):

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

  2. Execute the ajsovsymrem command.

  3. If the NNM window is not open, open it.

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

  5. Open the submap that contained the JP1/AJS3 symbols, and then choose Map, Submap, and Properties.

    The Submap Context dialog box appears.

  6. Select isJP1AJS2ObjExist, and delete it.

    The JP1/AJS3 context is deleted from the submap on which the JP1/AJS3 symbols were located.

  7. Close the NNM window.

  8. Execute the ajsovremove command.

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

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 you use HP NNM linkage in an environment in which HP NNM 6.1 has been updated to HP NNM 6.4 or later, you must set up HP NNM linkage again. To set up HP NNM linkage again, execute the ajsovremove and ajsovsetup commands before starting linkage.

  • 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‒8: 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 host side

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

  • When linking with NNM on a Solaris host, do not execute the ajsovsetup command without first setting the setup language for the HP NNM in the LANG environment variable. For details on the values you can use for the LANG environment variable when linking with the HP NNM linkage, see the documentation for the HP NNM.

  • If the extended use MIB definition file already exists when the ajsovsetup command is executed, the back up file of this file is created as previous-file-name.old. In addition, if the back up file already exists, the system inquires to overwrite. If y is replied, overwrite takes place, and processing continues. If n is replied, processing continues without taking the back up. After executing the ajsovsetup command, the following messages are issued. However, these messages do not pose any problems. 

    KAVT0952-I OpenView Environment(fields) Setup skipped.
KAVT0952-I OpenView Environment(trapd.conf) Setup skipped.
KAVT0952-I OpenView Environment(registration) Setup skipped.

  • 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

  • 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

Trademarks

Copyright (C) 2012, 2014, Hitachi, Ltd.

Copyright (C) 2012, 2014, Hitachi Solutions, Ltd.