Hitachi

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


13.3.11 System configuration for managing monitored hosts with host names in FQDN format

In JP1/IM - Manager, monitored hosts are managed by their host names.

Using JP1/IM - Manager, you can manage monitored hosts with host names in FQDN format or with the host names that are displayed when the hostname command is executed (short names).

To manage monitored hosts with names in FQDN format, change the JP1/Base event server name to FQDN format. To manage monitored hosts with names in short name format (the host names displayed when the hostname command is executed), change the JP1/Base event server name to short name format.

The following describes how a monitored host with a host name in FQDN format is managed.

In a system with a domain name, a monitored host name and the event source host name might be different as shown in the following figure.

Figure 13‒12: System with a domain name

[Figure]

A JP1 event issued on agent1.d1 is forwarded to host2, and displayed in JP1/IM - View. In this case, the event-source-host mapping function processes the computer name as the event source host name. JP1/IM - View displays agent1 as the event source host name. In this figure, two agent1 hosts exist in the network, so which of them issued the JP1 event cannot be determined.

Because of this, even if the host names are mapped by the event-source-host mapping function, monitoring of hosts for each business group or filtering of JP1 events by host names might not properly work.

To avoid this problem, when you manage a host with the host name in FQDN format, configure JP1/Base and JP1/IM - Manager, referring to 13.3.11(2) Registering a host in an agent configuration or a remote monitoring configuration.

Organization of this subsection

(1) Basic configuration when monitored hosts with names in FQDN format are managed

The following figure shows the basic configuration of JP1/IM - Manager when monitored hosts with names in FQDN format are monitored.

Figure 13‒13: Example of the basic configuration of JP1/IM - Manager (monitored hosts are monitored in FQDN format)

[Figure]

Viewer
  • JP1/IM - View (no restrictions on the version)

Integrated manager

The following products, which support FQDN format, are required:

  • JP1/IM - Manager version 10 or later

  • JP1/Base version 10 or later

Agents (monitored hosts)
  • JP1/Base (no restrictions on the version)

    Note that if a monitored host with a name in FQDN format is registered in agent configuration, the version of JP1/Base on the agent host must be 09-00 or later.

Remotely monitored hosts
  • JP1/Base and JP1/IM - Manager are not required.

In the system hierarchy (IM configuration), you can also place the base managers that manage remotely monitored hosts, and relay managers that consolidate events on individual agents (monitored hosts).

Figure 13‒14: Example of the JP1/IM - Manager configuration when a base manager and relay manager are used (monitored hosts are monitored in FQDN format)

[Figure]

The integrated manager and base managers

The following products, which support FQDN format, are required:

  • JP1/IM - Manager version 10 or later

  • JP1/Base version 10 or later

Relay manager
  • JP1/IM - Manager (no restrictions on the version)

  • JP1/Base (no restrictions on the version)

Agents (monitored hosts)
  • JP1/Base (no restrictions on the version)

Remotely monitored hosts
  • JP1/Base and JP1/IM - Manager are not required.

(2) Registering a host in an agent configuration or a remote monitoring configuration

(a) Using the same name for the host name to be registered in IM Configuration Management and as the event server name for the registered host (setting for JP1/Base)

Register the event server name of the registered host as the host name in IM Configuration Management. For details about how to set the same name, see Setting up an event server in a system that uses DNS services in the JP1/Base User's Guide.

If you change the event server name when the system is monitored by JP1/Base, the event source host name is changed. Therefore, check and, if necessary, revise the conditions of automated actions and the conditions for filtering JP1 events. For details about the items to be checked or revised, see 13.3.11(2)(c) Items to be reviewed when the event server name is changed.

(b) Changing JP1 event attributes (Setting for JP1/IM - Manager)

When managing a host with a name in FQDN format, the attribute for the event source host name for event log traps (JP1 event 3A71) differs depending on the JP1/IM - Manager version as shown in the following table.

Table 13‒7: Attributes for the event source host name

Change

Conditions of the event to be mapped

Attribute to be mapped to the event source host name

Description

Event ID (B.ID)

Product name (E.PPNAME)

Before change (JP1/IM - Manager version 09-50 or earlier)

3A71

--

Computer name (E.A1)

Event-source-host mapping definition for event 3A71 issued by remote-monitoring event log traps and JP1/Base event log traps

After change

(JP1/IM - Manager version 10-00 or later)

3A71

/HITACHI/JP1/NTEVENT_LOGTRAP

Source event server name (B.SOURCESERVER)

Event-source-host mapping definition for event 3A71 issued by JP1/Base event log traps

--

Computer name (E.A1)

Event-source-host mapping definition for event 3A71 that is issued by a remote-monitoring event log trap and forwarded from a submanager host when JP1/IM - Manager version 09-50 is used

Legend:

--: None

In the case of "Before change" (in the above table), the computer name is mapped to the event source host name. In the case of "After change" (in the above table), the source event server name is mapped to the event source host name.

To change the JP1 event attribute as in "After change" (in the above table), edit the file for setting common definitions (changing JP1 event attributes) as follows:

  1. Perform a new installation or overwrite installation of JP1/IM - Manager.

  2. Copy the model file (jp1im_jp1_event_attributes.conf.model) of the file for setting common definitions (changing JP1 event attributes) to any location.

    For details about the file for setting common definitions (changing JP1 event attributes), see Common definition settings file (changing the attribute of JP1 events) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

  3. Edit the ATTR_EVENT_LOGTRAP_SOURCEHOST line of the copied file as follows:

    [JP1_DEFAULT\JP1CONFIG]

    "ATTR_EVENT_LOGTRAP_SOURCEHOST"=dword:00000001

  4. Execute the jbssetcnf command.

    For details on the jbssetcnf command, see the JP1/Base User's Guide.

  5. Restart JP1/IM - Manager.

    Make sure that you restart JP1/IM - Manager.

(c) Items to be reviewed when the event server name is changed

If the event server name is changed, the event source host name is also changed. Check and, if necessary, revise the following items related to the event source host name.

Table 13‒8: Items that must be reviewed

Product

Function

Item

What to be checked

JP1/IM - Manager

Event list display and detailed event display

Checking the display contents

If an item of the event source host is displayed, the format of the displayed host name is changed. Check whether the displayed format is acceptable.

JP1 event filtering

Checking the conditions of event receiver filters, view filters, severe event definitions, and common exclusion-conditions (in extended mode)

If the event source host name is specified for filter conditions, check whether filtering can be performed correctly.

Event guide display

Checking the display conditions

If an item of the event source host is displayed, the format of the displayed host name is changed. Check whether the displayed format is acceptable.

Checking the event attributes used for event guide messages

If the event source host name is used for an event attribute, check whether the attribute is correct.

Event search

Checking the search conditions

If the event source host name is specified for filter conditions, check whether filtering can be performed correctly.

Event report output

Checking the filter conditions

Checking the output attributes

If the attribute for the event source host name is output, check whether the output value is acceptable.

Correlation event generation

Checking the correlation event generation conditions

If the attribute of the event source host name is inherited to a correlation event, check whether the inherited value is acceptable.

If an automated action is executed for a correlation event, also check the execution conditions of the automated action.

Changing severity of JP1 events

Checking the severity changing conditions

If the event source host name is specified for filter conditions, check whether filtering can be performed correctly.

Event-source-host mapping

Checking the event-source-host mapping definition

Command execution and automated action

Checking the execution conditions

If the event source host name is specified for the execution conditions, check whether the action can be correctly executed.

Checking the inherited information

If the attribute information of the event source host name is specified in the action definitions of commands and actions, check whether the commands and actions can be correctly executed.

Restrictions on viewing and operating business groups

Checking the restrictions on viewing events

Check whether event 3A71 is displayed only for the users in the business group to which the event is applied.

Change of the handling for JP1 events, and setting of memo information

You do not have to check this function.

JP1/Base

Event forwarding setting

When JP1/IM - Manager version 09-50 is used, if a submanager host forwards a 3A71 event to a higher-level manager by using a remote-monitoring event log trap, upgrade JP1/IM - Manager on the submanager host to version 10-00 or later. After that, change the attributes of JP1 events.

Other products

Launching of a linked product by monitor startup, linkage with the Tool Launcher window JP1/IM - Rule Operation, and management of response-waiting events

You do not have to check this function.