Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Configuration Guide


6.8.2 Setup for linkage with JP1/Cm2/SSO

This subsection describes the setup process for linking with JP1/Cm2/SSO version 8 or earlier.

Organization of this subsection

(1) Setup for using system-monitoring objects for monitoring

To link with JP1/Cm2/SSO version 8 or earlier, you must convert SNMP traps issued by JP1/Cm2/SSO via HP NNM version 8 or earlier to JP1 events to enable Central Scope to monitor them.

For additional details about setting up the linkage, see the following manual:

(a) For the JP1/Cm2/SSO host

To perform setup on the manager where JP1/Cm2/SSO version 8 or earlier (and HP NNM version 8 or earlier) is installed:

  1. Set the SNMP trap conversion function of JP1/Base.

    To convert SNMP traps to JP1 events, set the SNMP trap conversion function of JP1/Base. The settings for SNMP trap conversion in JP1/Base are the same as those used to link HP NNM version 8 or earlier.

    For details about how to set SNMP trap conversion, see the chapter that describes the event conversion settings in the JP1/Base User's Guide.

    The following is an overview of the setting procedure:

    • Set the linkage between NNM and JP1/Base (execute imevtgw_setup).

    • Set the URL for NNM.

    • Set the JP1 event destination.

    • Set the filter definition file (snmpfilter.conf).

  2. Edit the filter definition file for SNMP trap conversion in JP1/Base.

    Add the contents of the sample file (snmpfilter_im_sample.conf) that contains the settings for converting the SNMP traps handled by Central Scope to the filter definition file for SNMP trap conversion (snmpfilter.conf) in JP1/Base.

    The file names are as follows:

    - Filter definition file for SNMP trap conversion

    In Windows:

    Base-path\conf\evtgw\snmpfilter.conf

    In UNIX:

    /etc/opt/jp1base/conf/evtgw/snmpfilter.conf

    - Sample file in Central Scope

    In Windows:

    Scope-path\conf\snmpfilter_im_sample.conf

    In UNIX:

    /etc/opt/jp1scope/conf/snmpfilter_im_sample.conf

    Important
    • The plus sign (+) at the beginning of the sample file is a setting that SNMP trap variable binding to JP1 events is loaded. Do not remove it.

    • The size of a filter definition file is limited. In the filter definition file, add only the definitions of SNMP traps that are to be monitored in the operating environment.

      For details about the limitation on the size of a filter definition file, see the JP1/Base User's Guide.

  3. Set the daemon operation definition files for JP1/Cm2/SSO.

    Edit the settings in the daemon operation definition files (ssoapmon.def and ssocolmng.def) for JP1/Cm2/SSO version 8 or earlier so that SNMP traps will contain the information required by Central Scope.

    Set the following two files:

    • Location of the file

      JP1/Cm2/SSO-installation-folder\conf\ssoapmon.def

    • Settings

      Configure the issuance of events that indicate changes in the process status (threshold-event) and the loading of source names in variable bindings (source-name).

      threshold-event: on

      source-name: on

    • Location of the file

      JP1/Cm2/SSO-installation-folder\conf\ssocolmng.def

    • Settings

      Configure the issuance of events that indicate changes in the monitoring status of resource threshold values.

      threshold-event: on

(2) Setup for automatic generation of a monitoring tree

JP1/Cm2/SSO version 8 or earlier supports automatic generation of a monitoring tree. To enable the linkage for automatic generation, set up the linkage program.

For additional details about setting up the linkage, see the following manual:

(a) For the JP1/Cm2/SSO host

  1. Setting up the linkage program for JP1/Cm2/SSO

    Execute the following command to enable the collection of definition information from JP1/Cm2/SSO version 8 or earlier when generation of the monitoring tree is automatic:

    ssoimsetup -install (to enable linkage for automatic generation)

    If the setup described above is not completed, a monitoring object for JP1/Cm2/SSO version 8 or earlier is not created when an attempt is made to generate a monitoring tree automatically.

    To release the linkage, execute the following command:

    ssoimsetup -uninstall (to release the linkage for automatic generation)

Note that the following conditions must be satisfied to automatically create the monitoring objects for JP1/Cm2/SSO version 8 or earlier when generation of a monitoring tree is automatic:

  • Before you automatically generate a monitoring tree for JP1/Cm2/SSO version 8 or earlier, close the window of JP1/Cm2/SSO. If these windows remain open, definitions cannot be obtained from SSO.

  • When a monitoring tree is automatically generated for JP1/Cm2/SSO version 8 or earlier, the definitions to be obtained from SSO are the resource information whose collection status is Being collected.