6.5.8 Starting and stopping log file traps and event log traps

You can manage starting and stopping of the following log file traps and event log traps:

Log file traps (for agents)
Remote-monitoring log file traps (for remotely monitored hosts)
Remote-monitoring event log traps (for remotely monitored hosts)

For agents, you can start and stop log file traps only when the version of JP1/Base is 09-10 or later.

To start and stop them, use the following configuration files:

For log file traps:

Log-file trap action definition file
Log-file trap startup definition file

For remote-monitoring log file traps:

Remote-monitoring log file trap action-definition file

For remote-monitoring event log traps:

Remote-monitoring event log trap action-definition file

If both the following criteria are met for agents, you must move the log-file trap definition to the log-file trap startup definition file:

- If the version of JP1/Base is changed from a version earlier than 09-10 to version 09-10 or later;

- If the setting is defined so that log file traps are started by the start sequence definition file or the jbs_start command.

For details about how to move the log-file trap definition, see the description in Notes on installing and uninstalling JP1/Base in the Job Management Partner 1/Base User's Guide.

Organization of this subsection

(1) Starting log file traps and event log traps
(2) Stopping log file traps and event log traps

(1) Starting log file traps and event log traps

The following illustrates the flow for starting log file traps and event log traps by using IM Configuration Management.

Figure 6‒41: Flow for starting log file traps and event log traps

You can start log file traps and event log traps in the Display/Edit Profiles window of the IM configuration management viewer.

For agents:

After you start log file traps, the log-file trap action definition file saved in the IM Configuration Management database is applied to the agents. Then, the log-file trap startup definition is applied to the log-file trap startup definition file on the agents as follows:

When the log-file trap startup definition file has been defined:

The startup definition information is overwritten.
When the log-file trap startup definition file has not been defined:

The startup definition information is added.

After the definition information in the log-file trap action definition file and the log-file trap startup definition file is applied, commands are executed on the agents, and the log file traps are started.

For remotely monitored hosts:

After you start a remote-monitoring log file trap, commands are executed on the remotely monitored hosts, and the remote-monitoring log file traps are started.
After you start a remote-monitoring event log trap, commands are executed on the remotely monitored hosts, and the remote-monitoring event log traps are started.

In the following statuses, you cannot select Start Process from the Operation menu in the Display/Edit Profiles window.

The log file trap or event log trap you want to start has already been started.
A cluster ID is specified for the agent.

If a cluster ID is specified for the agent, send the configuration files to the agent. For details about how to send the configuration files, see 3.5.1(6)(b) Applying edited information in configuration files individually to each agent in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

If you change the Windows account information after you start a remote-monitoring log file trap and NetBIOS (NetBIOS over TCP/IP) connection is established with the monitored host, the connection is maintained until the NetBIOS (NetBIOS over TCP/IP) is disconnected. If you want to break the NetBIOS (NetBIOS over TCP/IP) connection and reconnect using the new account information, you need to restart the monitored host or the manager.

For details about how to start log file traps on agents, see 3.5.1(7)(a) Starting log file traps in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

For details about how to start remote-monitoring log file traps and remote-monitoring event log traps, see 3.5.2(5)(a) Starting remote-monitoring log file traps in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

To Page Top

(2) Stopping log file traps and event log traps

The following illustrates the flow for stopping log file traps and event log traps by using IM Configuration Management.

Figure 6‒42: Flow for stopping log file traps and event log traps

You can stop log file traps and event log traps in the Display/Edit Profiles window of the IM configuration management viewer.

For agents:

After you stop log file traps, the log-file trap startup definition is deleted from the log-file trap startup definition file on the agent. Also, the log-file trap action definition file is deleted on the agent, and log file trapping is stopped.

For remotely monitored hosts:

After you stop remote-monitoring log file traps, commands are executed on the remotely monitored host, and remote-monitoring log file traps stop.
After you stop remote monitoring event log traps, commands are executed on the remotely monitored host, and remote-monitoring event log traps stop.

In the following statuses, you cannot select Stop Process from the Operation menu in the Display/Edit Profiles window:

The log file trap or event log trap you want to stop has not been started.
A cluster ID is specified for the agent.

For details about how to stop log file traps on agents, see 3.5.1(7)(b) Stopping log file traps in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

For details about how to stop remote-monitoring log file traps and remote-monitoring event log traps, see 3.5.2(5)(b) Stopping remote-monitoring log file traps in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.

To Page Top