Hitachi

JP1 Version 12 JP1/Performance Management User's Guide


11.1.2 Features of multiple monitoring

In a multiple-monitoring configuration, even if an error occurs on the primary Manager, the secondary Manager can continue monitoring. This reduces monitoring downtime and improves the availability.

In addition, as a crisis management measure, you can place the two managers on separate sites so that information assets are saved in separate locations.

The following figure shows how performance data flows when an error occurs on the primary Manager.

Figure 11‒1: Flow of performance data when an error occurs on the primary Manager in a multiple-monitoring configuration

[Figure]

When you employ multiple monitoring, the definition information of the managers must be duplicated. Definition information set on one manager (PFM - Manager and PFM - Web Console) can only migrate to the other manager by an export and import.

When you set remote actions, you can select which manager executes remote actions for events that are sent from the monitoring agent. For details, see 11.3.5 Controlling remote actions.

In a multiple-monitoring configuration, the secondary Manager cannot perform some operations because consistency must be maintained between the primary Manager and the secondary Manager. The following describes operations which the secondary Manager cannot perform.

PFM - Manager commands:
  • jpcconf agttree import command

  • jpcconf bgdef delete command

  • jpcconf bgdef import command

  • jpctool alarm active command

  • jpctool alarm bind command

  • jpctool alarm copy command

  • jpctool alarm delete command

  • jpctool alarm import command

  • jpctool alarm inactive command

  • jpctool alarm unapplied command

  • jpctool alarm unbind command

  • jpctool config alarmsync command

  • jpctool monitor resume command

  • jpctool monitor suspend command

PFM - Web Console commands:
  • jpcrdef create command

  • jpcrdef delete command

Operations in PFM - Web Console:
  • Updating the PFM - Manager definition (except for properties operation)

  • Setting binding of alarm tables

  • Starting and stopping monitoring

  • Suspending and resuming monitoring

  • Checking alarm application status and applying alarm information

  • Updating the bookmark of PFM - Web Console

  • Updating the process monitoring template of PFM - Web Console

When an error occurs on the primary Manager, you can switch from the primary Manager to the secondary Manager to perform the above operations, thus giving the previously secondary Manager the primary functions. For details, see 11.7 Switching the primary Manager and the secondary Manager.