Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Overview and System Design Guide


7.5 Profile management

Using IM Configuration Management, you can centrally manage the JP1/Base profiles on the hosts in the system hierarchy (IM configuration) through the IM configuration management viewer.

To manage profiles with IM Configuration Management, the hosts must be added to the system hierarchy and JP1/Base must be active on each host.

This section describes the profiles you can manage by using IM Configuration Management, and the functionality provided for this purpose.

The supported profile management methods include the method that uses IM Configuration Management and the method that uses JP1/Base commands. If the versions of JP1/IM - Manager and of the agent's JP1/Base are both 11-10 or later, these two methods can be combined.

Some notes apply when IM Configuration Management's profile management is used together with JP1/Base's profile management. For details, see 7.5.10 Notes on using IM Configuration Management's profile management together with JP1/Base's profile management.

The following table describes the differences in profile management according to the combination of the version of JP1/IM - Manager and the version of JP1/Base on the agent.

Table 7‒28: Differences in profile management according to the combination of JP1/IM - Manager and JP1/Base on the agent

Functionality

JP1/IM - Manager

11-01 or earlier

JP1/IM - Manager

11-10 or later

JP1/Base on agent

11-00 or earlier

JP1/Base on agent

11-10 or later

JP1/Base on agent

11-00 or earlier

JP1/Base on agent

11-10 or later

Profile management

Profiles cannot be managed by using IM Configuration Management commands and JP1/Base commands together.

Profiles can be managed by using IM Configuration Management commands and JP1/Base commands together.

Collecting profile lists

The agent's profile lists can be collected by using IM Configuration Management.

Collecting profiles

The agent's profiles can be collected by using IM Configuration Management.

Collecting profiles by using a batch operation

The agent's profiles can be collected from IM Configuration Management by using a batch operation.

Applying profiles by reload

Profiles set by using IM Configuration Management can be applied to the agent by reloading the log file trap processes.

Applying log file trap information by restart

Log file trap information set from IM Configuration Management can be applied to the agent by restarting the log file trap processes.

Applying log file trap information by sending a file

Log file trap information for only the cluster can be sent to the agent from IM Configuration Management.

Log file trap information can be sent to the agent from IM Configuration Management.

Applying profiles in a batch operation

The following profile types can be applied to the agent from IM Configuration Management by using a batch operation:

  • Event forwarding

  • Event log trapping

  • Local action

The following profiles can be applied to the agent from IM Configuration Management by using a batch operation:

  • Event forwarding

  • Log file trapping

  • Event log trapping

  • Local action

Displaying profiles

The following information can be displayed by using IM Configuration Management:

  • Service activity status

  • Valid configuration information

  • Contents of configuration files

Editing configuration files

The configuration files for the agent's profiles can be edited.

Saving edited file contents

The contents of edited configuration files can be saved to the manager where IM Configuration Management is running.

Adding log file trap information

Profiles of the log file traps can be added by using IM Configuration Management.

Deleting log file trap information

The profiles of the log file traps that are saved in the IM Configuration Management database will be deleted.

The profiles of the log file traps that are saved in the IM Configuration Management database and the profiles of the agent's log file traps will be deleted.

Starting log file traps

Log file traps can be started by using IM Configuration Management.

Stopping log file traps

The agent's log file trap information will be deleted when the log file traps are stopped by using IM Configuration Management.

The agent's log file trap information will not be deleted when the log file traps are stopped by using IM Configuration Management.

Starting log file trapping automatically

You cannot specify in IM Configuration Management whether to enable or disable the automatic start of log file trapping. When a log file trap is started, automatic start is enabled, and when a log file trap is stopped, automatic start is disabled.

You can specify in IM Configuration Management whether to enable or disable the automatic start of log file trapping.

Organization of this section