10.1.1 Determining which JP1 events to forward
First, determine which JP1 events to forward. Consider the following when determining which JP1 events to forward:
-
Only important JP1 events need to be forwarded for error monitoring.
By default, only important events are sent to a higher-level server as defined in the system configuration of JP1/IM - Manager. We recommend that you keep the default setting if your goal is to monitor the system for errors. If you do change this setting from the default, make sure that the system does not forward unnecessary JP1 events to higher-level servers.
-
Consider JP1 events that are forwarded by default.
The following JP1 events are forwarded to every destination in the forwarding settings file (forward), even if the events do not match the event filter conditions. If you do not want JP1/Base to forward these events, define them in an exclusion condition or specify the auto-forward-off flag for the options parameter in the event server settings file (conf).
-
Event reporting of JP1/Base startup (00004724)
-
Event reporting of JP1/Base shutdown (00004725)
-
Event reporting of a threshold-based suppression (00003D0B)
-
Event reporting of a stop of a threshold-based suppression (00003D0C)
-
Event reporting of a stop of all threshold-based suppressions (00003D0D)
-
Event reporting of the continuation of threshold-based suppressions (00003D0E)
-
-
Consider the number of JP1 events to be forwarded per unit of time.
Delays could occur in the transfer processing if there are a large number of JP1 events being forwarded.
Set the conditions so that the types of forwarded JP1 events will not be in close proximity or, if they do occur in quick succession, this situation does not continue for very long. For example, define a filter condition in the forwarding settings file (forward) so that only JP1 events with a severity level of Warning or higher will be sent.
-
Consider the total number of JP1 events that will be stored on the higher-level host (manager or submanager).
Delays could occur when the JP1 events are registered in the event database if there are a large number of JP1 events being forwarded to the higher-level host.
Consider the number of hosts managed by the manager host, the number of JP1 events sent from each host, and the number of JP1 events generated on the local host. For example, define filter conditions in the forwarding settings file (forward) on each host so that only JP1 events with a severity level of Warning or higher will be sent from an agent to a submanager, and only JP1 events with a severity level of Error or higher will be sent from a submanager to the manager host.
-
Consider the amount of traffic data on the network.
Use the following equation to estimate the amount of data transferred on the network per JP1 event:
60#1 + 600#2 (bytes)
#1: The amount of data transferred per JP1 event when a 16-byte remote event server name, with close as its communication type, is specified in the remote-server parameter in the event server settings file (conf). When keep-alive is specified as the communication type, this amount of data is transferred only for the first JP1 event.
#2: For a JP1 event generated when a character string of approximately 100 bytes is trapped by a log file trap.