5.3.2 Cluster operation with the event log trapping function

In a cluster system, you must start the event log trapping function separately on each physical host. You cannot start the function by specifying a logical host. However, you can specify whether JP1 events will be forwarded to the event service on a logical host where they can be centrally managed. Configure a forwarding destination that works well with how your system is run.

To register them in the event service of a logical host, specify the event server name of the logical host in the server parameter in the action definition file. Note that if your system is configured so that JP1 events converted from event log data are registered directly on a logical host, the event log on the secondary node cannot be monitored. If you do not specify an event server name in the server parameter of the action definition file, JP1 events are registered with the event service on the physical host.

To monitor the event log on both the primary and secondary nodes, first register the converted JP1 events in the event service on the physical host. Then forward the registered JP1 events to the event service on the logical host, using a forwarding settings file (forward). For details on the forwarding settings file, see Forwarding settings file in 16. Definition Files.

A configuration example for monitoring event logs on both the primary and secondary nodes is shown in the following figure.

Figure 5‒5: Configuration example for monitoring event logs on both primary and secondary nodes of the logical host

To Page Top