L.5 Changes in version 11-50

(1) Changes in the manuals 3021-3-A06-30(E), 3021-3-A07-30(E), 3021-3-A08-30(E), 3021-3-A09-30(E), 3021-3-A10-30(E), 3021-3-A11-30(E), and 3021-3-A12-30(E)

• For linkage with JP1/Service Support, a new incident registration mode was added to allow any event attributes or character strings to be inherited.

• A common exclusion-condition in extended mode can now exclude a JP1 event that satisfies the condition from automated-action execution.

• A description was added for the common exclusion history file that logs the exclusion processes of common exclusion-conditions.

• A description was added for the common exclusion-conditions definition history file that logs the definition history of common exclusion-conditions.

• A note was added for the common exclusion-conditions.

• The maximum number of repeated event conditions was increased to 2,500. The total size of the definitions of repeated event conditions was increased to 15 MB.

• Saving event listings (CSV snapshot) now includes action-excluded events.

• Saving event information from the integrated monitoring database (output of an event report) now includes the following event attributes:

  • Common exclude conditions group ID (E.JP1_IMCOMEXCLUDE_ID)

  • Common exclude conditions group name (E.JP1_IMCOMEXCLUDE_NAME)

  • Common exclude conditions group target-for-exclusion (E.JP1_IMCOMEXCLUDE_TARGET)

• Defined automated actions can now be enabled or disabled by using the Action Parameter Definitions window or the jcachange command.

• A note was added for cases where the automated action function requests a large number of agents at once to execute a command.

• For automated action definitions, the status of execution conditions can now be retained unless their definitions are changed.

• A consideration on maintenance was added for excluding error events that are caused by maintenance work from action execution.

• The maximum number of hosts that can be managed by one instance of JP1/IM - Manager was increased to 2,500.

• The following files were added to the list of files and folders:

  • Configuration file for incident inheritance information

  • Model file for the configuration file for incident inheritance information

  • Common exclusion history file

  • Common exclusion-conditions definition history file

• The maximum number of hosts on which commands can be executed from one instance of JP1/IM - Manager was increased 2,500.

• The maximum number of defined common exclusion-conditions groups (in extended mode) was increased to 2,500. The maximum filter length of the common exclusion-conditions groups (in extended mode) was increased to 15 MB.

• The maximum number of hosts that can be set in a business group or monitoring group was increased to 2,500.

• A description was added to explain that the automated action definition file must be updated when JP1/IM - Manager is upgraded from versions earlier than 11-10.

• A common exclusion-conditions group (extended) can now be set to exclude a collected JP1 event from automated-action execution.

• Exclusion processing caused by common exclusion-conditions and update processing of common exclusion-conditions definition are now logged into history files.

• For the procedure to link with JP1/Service Support, a step was added for cases where the incident registration mode is set to 3.

• The configuration file for incident inheritance information was added to the list of files to back up.

• A description about the exclusion history and definition history of common exclusion-conditions was added to the section about using historical reports.

• The detailed information of JP1 events displayed in the Event Details window now includes the following items:

  • Common exclude conditions group ID

  • Common exclude conditions group name

  • Common exclude conditions group target-for-exclusion

• The following files were added to the lists of log files and directories:

  • Common exclusion history file

  • Common exclusion-conditions definition history file

• The following files were added to the lists of data to be collected for troubleshooting:

  • Common exclusion history file

  • Common exclusion-conditions definition history file

• A corrective action for cases where a common exclusion-condition is used in extended mode was added to the actions to take when no JP1 event is displayed in the Event Console window.

• A description was added for actions to take when an automated action is not executed.

• In the Event Console window, the Action column now shows an icon indicating that the event is excluded from action execution by a common exclusion-condition (action execution).

• The configuration file for incident inheritance information (incident_info.conf) was added to the relation definition files of the Event Details window and the Edit Event Details window.

• For common exclusion-conditions in extended mode, in the System Environment Settings window, the Type column of the General page now shows an icon indicating that the common exclusion-condition excludes a collected event from action execution.

• For common exclusion-conditions in extended mode, in the Event Acquisition Conditions List window, the Type column of the Common exclusion-conditions groups list now shows an icon indicating that the common exclusion-condition excludes a collected event from action execution.

• In the Common Exclusion-Condition Settings (Extended) window, you can now specify the exclusion target.

• The event list in the Event Console window can now show the following items:

  • Common exclude conditions group ID

  • Common exclude conditions group name

  • Common exclude conditions group target-for-exclusion

• You can now enable or disable automated action definitions in the Action Parameter Definitions window.

• When you apply changes in the Action Parameter Definitions window, you can now retain the suppression status and the status of satisfied conditions of the AND-joined conditions unless the action definition is edited.

• You can now specify an action ID of the action execution condition in the Action Parameter Detailed Definitions window.

• A note was added for cases where a large number of agents are requested at once to execute a command.

• For the jcachange command, the following options were added: -e, -on, -off, and -st.

• The jcadefconv command can now convert an action definition file from a version earlier than 11-50 (the DESC_VERSION value is less than 4) to version 11-50 or later (the DESC_VERSION value is 4).

• The following definition file was added:

  • Configuration file for incident inheritance information (incident_info.conf)

• The following files were added to lists of data collected with the data collection tool:

  • Common exclusion history file

  • Common exclusion-conditions definition history file

• For the automated action environment definition file (action.conf.update), the default value of the ACTIONINFSIZE parameter was changed to dword:00001000 (4,096 KB).

• For the automated action definition file (actdef.conf), the parameters aid and valid were added. Additionally, the DESC_VERSION parameter can now take a new file version of 4.

• For the automated action definition file (actdef.conf) (for conversion), the DESC_VERSION parameter now can take a file version of 4.

• The definitions for the following items were added to the default definition file for extended event attributes:

  • Common exclude conditions group ID

  • Common exclude conditions group name

  • Common exclude conditions group target-for-exclusion

• For the common exclusion-conditions extended definition file, the ex-target parameter was added. Additionally, the DESC_VERSION parameter can now take a new file version of 2.

• For linkage with JP1/Service Support, a new incident registration mode was added to allow any event attributes to be inherited.

• The following messages were added:

  KAVB0518-E, KAVB0759-E, KAVB0762-E, KAVB0763-E, KAVB1604-E to KAVB1608-E, KAVB1873-W, KAVB1874-E, KAVB3173-W, KAVB3180-W, KAVB3181-W, KAVB3185-I, KAVB4026-E to KAVB4029-E, KAVB4148-E, KAVB4155-E, KAVB4451-E, KAVB4452-E, KAVB4714-E, KAVB4715-E, KAVB5112-E, KAVB5505-W, KAVB5506-W, KAVB5559-W to KAVB5561-W, KAVB5760-W to KAVB5762-W, KAVB8821-E, KNAN22533-E, KNAN22534-E

• The output destination of the following message was corrected:

  KAVA1821-E, KAVB1115-W

• The actions for the following messages were changed:

  KAVB1591-E, KAVB1858-E, KAVB2605-E, KAVB5105-W, KNAN22017-E, KNAN22823-E

• For the following messages, the message output lines were added. The actions were also changed.

  KAVB3118-E, KAVB3119-E

• For the following messages, the message description was changed.

  KAVB1869-E, KAVB4450-E

• For the following message, the message description was changed. The actions were also changed.

  KAVB5109-W

To Page Top