Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management User's Guide


14.2.3 Setup for linking with NNM

This subsection describes the setup procedures for using the NNM linkage facility. Implement the setup on a host that has NNM installed.

  1. Execute setup to add an agent.

  2. Set up the destination of the SNMP traps.

  3. Modify the NNM linkage definition file.

  4. Execute the setup command.

  5. Modify the NNM linkage definition file again (only for multiple monitoring).

  6. Define issuing of SNMP traps and reports by alarm definition.

    Important note

    Notes on setting up the NNM linkage facility:

    • Execute the setup command (jpcconf ov enable for Windows, jpcconf ov enable for UNIX) with the NNM service started and the NNM windows closed.

    • NNM command errors during setup are normally output to the standard error output. However, even if an NNM command error occurs, a setup command might output a normal termination of the NNM command to the standard output.

    • To use the NNM linkage, you need to set On-Demand: To what level should submaps be persistent? in All Levels. Display the settings of NNM IP Map from the map properties, and check or change the persistent submap level.

    • If the name of a Performance Management monitoring host differs from its actual host name, you must change the DNS settings or the hosts file settings on the Manager host or on the host where NNM is installed. Changes are as follows:

    When updating the DNS settings

    Use the A record to register the actual host name and the CNAME record to register the monitoring host name.

    When changing the setting in the hosts file

    After the IP address, first specify the actual-host-name, and then that monitoring-host-name. If host names other than the Performance Management monitoring host name exist in the file, the actual-host-name must be specified before those names, as well.

    Example of the hosts file:

    ****.****.****.**** HostA AliasB

Organization of this subsection

(1) Executing setup to add an agent

Execute setup to add an agent to be monitored through NNM linkage. Skip this procedure if PFM - Manager has been installed on a host that has NNM, and PFM - Agent or PFM - RM is already registered when PFM - Manager is setup.

PFM - Manager version 09-00 or later automatically registers PFM - Agent or PFM - RM, so no additional setup is required for the PFM - Agent or PFM - RM information. However, if the release date of PFM - Agent or PFM - RM is later than that of PFM - Manager, PFM - Agent or PFM - RM must be registered manually. For details on the release dates for PFM - Manager, PFM - Agent, and PFM - RM, see the Release Notes for each program.

When PFM - Manager has not been installed and PFM - Base has been installed instead on a host that has NNM, copy the setup files for PFM - Agent or PFM - RM onto a host that has NNM, and then execute the setup command in the same way as you would to register PFM - Agent or PFM - RM during the setup of PFM - Manager.

(a) Copying the setup files for PFM - Agent or PFM - RM

To copy the setup files from a host that has PFM - Agent or PFM - RM onto a host that has PFM - Base installed:

  1. Copy the setup files for PFM - Agent or PFM - RM in binary mode.

    The following table describes file locations and destinations to which files are copied.

    Table 14‒3: Setup files to be copied

    Platform

    File

    Source PFM - Agent or PFM - RM

    Destination PFM - Agent

    Source PFM - Agent or PFM - RM

    Destination PFM - Agent

    Windows

    Windows

    installation-folder\setup\jpcxxxxw.EXE

    installation-folder\setup\

    UNIX

    installation-folder\setup\jpcxxxxu.Z

    /opt/jp1pc/setup/

    UNIX

    Windows

    /opt/jp1pc/setup/jpcxxxxw.EXE

    installation-folder\setup\

    UNIX

    /opt/jp1pc/setup/jpcxxxxu.Z

    /opt/jp1pc/setup/

Legend:

xxxx indicates the service key for each PFM - Agent or PFM - RM. For details on service keys, see the appropriate PFM - Agent or PFM - RM manual.

(b) Executing the setup command on the PFM - Base host

Execute the following command on the PFM - Base host to set up PFM - Agent or PFM - RM.

jpcconf agent setup -key xxxx

xxxx indicates the service key for each PFM - Agent or PFM - RM. For details on service keys, see the appropriate PFM - Agent or PFM - RM manual.

For example, execute the following command to set up PFM - Agent for Oracle:

jpcconf agent setup -key Oracle

In this example, the jpcconf agent setup command is executed in interactive mode. However, the command can also be executed in non-interactive mode. For details on the jpcconf agent setup command, see the chapter on commands in the manual Job Management Partner 1/Performance Management Reference.

Note:

An error might occur if you execute the jpcconf agent setup command when Performance Management programs and services have not completely stopped on the local host where you want to execute the command. In such cases, make sure that Performance Management programs and services have completely stopped, and then re-execute the jpcconf agent setup command.

You can delete the setup files for PFM - Agent or PFM - RM after this procedure has finished.

(2) Setting up the destination of SNMP traps

Set up the required alarms in the window of PFM - Web Console in order to manage networks by using NNM. Set up the destination of SNMP traps in the alarm settings.

  1. Log on to PFM - Web Console from the Web browser of the monitoring console.

    You must log on with a user account that has administrator user permissions.

  2. In the navigation frame of the Main window, select the Services tab.

  3. In the navigation frame of the Services window, select the PFM - Manager folder.

  4. From the list of PFM - Manager services, select a Trap Generator service.

    A Trap Generator service is a service whose name begins from PC, or <Trap Generator>.

    The selected Trap Generator service is marked with a checkmark.

  5. Select the Properties method in the method frame.

  6. In the Properties window for the Trap Generator service, select the ADD OR DELETE A TRAP DESTINATION folder from the properties tree.

  7. In the Value field for the ADD A DESTINATION property at the bottom of the information frame, specify the host name or IP address of the destination for SNMP traps.

  8. Click the Finish or Apply button.

  9. Select the destination folder for SNMP traps which now appears below the Trap Destinations folder.

  10. Change the settings for the property at the bottom of the information frame.

    You can specify the contents as follows:

    Retry Count

    Specify an integer from 0 to 32767 for the number of times a SNMP trap is transmitted. The default value is 1 (time). The default value is used if you specify 0.

    Retry Interval

    Specify an integer from 0 to 32767 for the interval (seconds) between retransmissions of SNMP traps. The default value is 5 (seconds). The default value is tentatively used if you specify 0.

    Trap Port

    Specify a number from 1 to 32767 for the port number of the destination of SNMP traps. The default value is 162. The default value is tentatively used if you specify 0.

    Enabled

    Select Yes or No to specify whether or not to transmit SNMP traps. The default value is Yes.

  11. Click the Finish or Apply button.

    The settings are saved.

(3) Modifying the NNM linkage definition file

Modify the NNM linkage definition file (jpcnnm.ini) to establish linkage with NNM.

The NNM linkage definition file provided by Performance Management is stored in the following directory on a host that contains NNM:

The following table lists examples of settings in the jpcnnm.ini file.

Table 14‒5: Examples of settings in the jpcnnm.ini file

Setting item

Setting example

PFM - Manager host name

PFMMGR

PFM - Web Console host name

PFMWEBCON

Port numbers of PFM - Web Console host

20358

Web browser path of host that has NNM linkage facility installed.

C:\Program Files\Internet Explorer\IEXPLORE.EXE

Figure 14‒3: Example of settings in the jpcnnm.ini file

[Figure]

Note:

Define multiple PFM - Managers in the Manager Definition section of the jpcnnm.ini file as follows if multiple PFM - Managers exist in the systems.

[Figure]

For multiple monitoring, define multiple PFM - Managers as follows:

[Figure]

If multiple PFM - Managers are defined, the window for selecting PFM - Manager for the connection destination appears when you start the window of PFM - Web Console from NNM. Select PFM - Manager to be connected in the window to display the Login window of PFM - Web Console. If a single PFM - Manager has been specified in the Manager Definition section of the jpcnnm.ini file, the window for selecting PFM - Manager for the connection destination does not appear and the Login window of PFM - Web Console appears.

(4) Executing the setup command

Execute the setup command provided by Performance Management. The environment setup for linking with NNM is performed and the services of the NNM linkage function are started when you execute the command.

Execute the jpcconf ov enable command.

Note:

Perform the following setup procedure if you specify multiple PFM - Managers in the Manager Definition section of the jpcnnm.ini file.

  1. Execute the jpcconf ov enable -mkhtml command.

    An HTML file for the window to select PFM - Manager is created.

  2. Execute the jpcconf ov enable command.

(5) Modifying the NNM linkage definition file again (only for multiple monitoring)

For multiple monitoring, you must specify the settings so that only one PFM - Web Console window starts when connecting to PFM - Manager on either of the primary Manager or the secondary Manager. Therefore, you need to modify the jpcnnm.ini file modified in 14.2.3(3) Modifying the NNM linkage definition file so that only the primary PFM - Web Console host name is specified as follows:

[Figure]

Also, when you switch the primary Manager with the secondary Manager, change the definition so that PFM - Web Console will start on the new primary Manager.

(6) Associating alarms with SNMP traps and reports

Set up the following items in the Alarms window of PFM - Web Console:

The following procedure mainly describes operations for setting up SNMP traps to be issued and for associating alarms with reports.

  1. Log on to PFM - Web Console as a user with administrator user permissions.

  2. In the navigation frame of the Main window, click the Alarms tab.

  3. In the navigation frame of the Alarms window, select the alarm definition for which you want to issue SNMP traps.

    The selected alarm is marked with a checkmark.

  4. Select the Edit method in the method frame.

  5. In the Edit > Main Information window in the information frame, click the Next button.

  6. In the Actions to be executed area of the Edit > Action window select the SNMP check box.

    Select the check boxes for the alarm statuses (Abnormal, Warning, or Normal) for which you want to issue SNMP traps.

  7. In Report to be displayed, click the Browse button to select the report to be associated with the alarm.

  8. Click the Finish button.

    SNMP traps are defined as alarm action, and the selected report is associated.

For details on defining alarms, see 6. Monitoring Operations with Alarms.