8.5.5 Adding and deleting profiles
Using IM Configuration Management, you can add or delete profiles for log file traps that were set on individual agents if the versions of JP1/Base on the agents are 09-10 or later. You can also add or delete profiles for remote-monitoring log file traps that were set on individual remotely monitored hosts.
- Organization of this subsection
(1) Adding profiles
The following figure illustrates the flow for adding profiles for log file traps and remote-monitoring log file traps.
|
You can add profiles in the Add Profile window of the IM configuration management viewer. After you add profiles, the added profiles are displayed in the tree display area in the Display/Edit Profiles window.
After you add profiles, you need to edit and save or apply the following information:
-
For agents:
-
Log-file trap action definition file
-
Log-file trap startup definition file
-
-
For remotely monitored hosts:
-
Remote-monitoring log file trap action-definition file
-
Start options for remote-monitoring log file traps
-
For details about the procedure, see 3.5.1(5) Editing configuration files in the JP1/Integrated Management 3 - Manager Configuration Guide.
The following table describes the items that can be set when you add profiles.
Item |
Description |
---|---|
Log file trap name |
Specify the log file trap name. You cannot specify a log file trap name that is already set or that is the same as the log-file trap action definition file. |
Cluster ID |
Specify the cluster ID when you manage the log file on a shared disk of a logical host. For details about the cluster ID, see the JP1/Base User's Guide. If the cluster ID is enabled, you can specify the log file trap for a cluster. |
For details about how to add profiles, see 3.5.1(4)(a) Adding profiles in the JP1/Integrated Management 3 - Manager Configuration Guide.
The following table shows the paths where the definition files are located when the log file trap information added from IM Configuration Management is applied to the monitoring target of the agent.
Configuration file |
Type of OS on agent |
Location |
---|---|---|
Log-file trap action definition file |
Windows |
Base-path\conf\cf_log_file_trap\ |
UNIX |
/etc/opt/jp1base/conf/cf_log_file_trap/ |
|
Log-file trap startup definition file |
Windows |
Base-path\conf\event\ |
UNIX |
/etc/opt/jp1base/conf/event/ |
(2) Deleting profiles
The following figure illustrates the flow for deleting profiles for log file traps and remote-monitoring log file traps.
|
You can delete profiles in the Display/Edit Profiles window of the IM configuration management viewer. After you delete profiles, the profiles for log file traps and remote-monitoring log file traps that are saved in the IM Configuration Management database are deleted. If the agent's JP1/Base version is 11-10 or later, the agent's log file trap information is also deleted when the profiles are deleted. If the agent's JP1/Base version is 11-00 or earlier, the agent's log file trap information is deleted when the log file trap process is stopped, not when the profiles are deleted.
When you delete profiles for log file traps for a cluster, however, the flow for deleting profiles is different as shown in the following figure.
|
When you delete a profile, the profile for log file traps saved in the IM Configuration Management database is deleted.
-
For agents:
The log-file trap startup definition information is deleted from the log-file trap startup definition file, and then the log-file trap action definition file is deleted. Then, the settings of log file traps are deleted from agents.
-
For remotely monitored hosts:
The log-file trap startup definition information is deleted from the remote-monitoring log file trap startup-definition file, and then the remote-monitoring log file trap action-definition file is deleted.
Note that the profile cannot be deleted if the log file trap whose profile you want to delete is running on the agent regardless of whether it is for a cluster. First stop the log file trap whose profile you want to delete, and then delete the profile.
For details about how to delete profiles, see 3.5.1(4)(b) Deleting profiles in the JP1/Integrated Management 3 - Manager Configuration Guide.