11.1.3 Definition information for multiple monitoring

This subsection describes definition information that needs to be matched between the primary Manager and the secondary Manager.

Organization of this subsection

(1) Definition information on the primary Manager that needs to be duplicated on the secondary Manager
(2) Definition information for which the same setting must be specified on the primary Manager and the secondary Manager

(1) Definition information on the primary Manager that needs to be duplicated on the secondary Manager

Set the definition information shown in the following table on the primary Manager and duplicate it onto the secondary Manager.

If you configure a multiple-monitoring environment and then change the definition information, you must duplicate the definition information on the primary Manager onto the secondary Manager. For details about how to duplicate the definition information, see 11.5 Duplicating definition information.

Table 11‒1: Definition information to be duplicated from the primary Manager onto the secondary Manager
No.	Definition information	How to check	How to match
1	Alarm information (alarm definition / Action definition)	See 11.6.1(1) Checking alarm information of alarm definition and action definition.	See 11.5 Duplicating definition information.
2	Binding information	See 11.6.1(2) Checking binding information.
3	Report definition	See 11.6.1(3) Checking report definitions.
4	Business group information	See 11.6.1(4) Checking business group information.
5	Performance Management user account information	See 11.6.1(5) Checking Performance Management user account information and Agents tree (User Agents) information.
6	Agents tree (User Agents) information
7	Auto alarm bind setting	See 11.6.1(8) Checking the settings of auto alarm bind.
8	Bookmark definition information	See 11.6.2(1) Checking bookmark definition information.
9	Process monitoring template information	See 11.6.2(2) Checking process monitoring template information.

To Page Top

(2) Definition information for which the same setting must be specified on the primary Manager and the secondary Manager

The definition information shown in the following table must be set on both the primary Manager and the secondary Manager. You must make the settings consistent between the primary Manager and the secondary Manager. You can check whether the settings are consistent by using the method shown in the How to check column.

If you configure a multiple-monitoring environment and then change the definition information, you must match the information of the primary Manager and the secondary Manager. See the How to match column and take appropriate action.

Table 11‒2: Definition information for which the same setting must be specified on the primary Manager and the secondary Manager
No.	Definition information	How to check	How to match
1	Managed agent information	See 11.6.1(6) Checking managed agent information.	See the chapter that describes how to delete service information in the JP1/Performance Management Planning and Configuration Guide (This definition information becomes inconsistent only when the number of PFM - Agent or PFM - RM services managed by PFM - Manager is reduced).
2	Settings of PFM - Manager for the connection destination	See 11.6.1(7) Checking the settings of PFM - Manager for the connection destination.	See 11.3.4 Setting PFM - Manager for the connection destination for multiple monitoring.
3	Settings of the health check agent	Check whether editable properties values for the host name `<Health` `Check>` on the Services tree and the host name `<Health` `Check>(store)` match.^#1	See 3.4.8 Distributing agent properties as a batch and distribute properties from the health check agent on the primary Manager to that on the secondary Manager.
4	JP1/SLM linkage definition information Linked JP1/SLM host name	Check whether the properties values of the ITSLM Coordination Configuration/ITSLM Coordination node in the Service Properties window for the Master Manager service on the Services tree match.^#1	Match the editable properties values of ASSIGN ITSLM COORDINATION of the ITSLM Coordination Configuration/MANAGE ITSLM COORDINATION node in the Service Properties window for the Master Manager service on the Services tree.^#1
5	Settings related to JP1 events	In the Service Properties window for the Master Manager service on the Services tree, check whether the editable properties values of the JP1 Event Configurations node, the JP1 Event Configurations/Alarm node, and the JP1 Event Configurations/System node match.^#1	In the Service Properties window for the Master Manager service on the Services tree, match the editable properties values of the JP1 Event Configurations node, the JP1 Event Configurations/Alarm node, and the JP1 Event Configurations/System node.^#1
6	JP1/SLM linkage definition information Custom monitoring items	Check whether the contents of the `monitoringitems.cfg` files match.^#2	See the chapter that describes definition files in the manual JP1/Performance Management Reference and match the `monitoringitems.cfg` setting values.
7	Host information configuration file (`jpchosts`)	Check whether the contents of the `jpchosts` files match.^#2	See the chapter that describes how to set IP addresses in the JP1/Performance Management Planning and Configuration Guide and match the `jpchosts` settings.
8	Setting of Authentication mode	Check whether the `UserServer.authenticationMode` label values in the `jpcvsvr.ini` files match.^#2	See 2.4 Setting the user account authentication mode and match the `UserServer.authenticationMode` label value.
9	Startup information (definition in `jpccomm.ini`)	Necessity for matching differs depending on the setting items. See Table 11-3 Definition information that must be matched in jpccomm.ini.
10	Health check function	Check whether the execution result of the `jpcconf` `hc` `display` command matches.	Execute the `jpcconf` `hc` `enable` command or the `jpcconf` `hc` `disable` command to match the setting.^#3
11	Status management function	Check whether the execution result of the `jpcconf` `stat` `display` command matches.	Execute the `jpcconf` `stat` `enable` command to match the setting.^#3
12	Product name display function	Check whether the execution result of the `jpcconf` `prodname` `display` command matches.	Execute the `jpcconf` `prodname` `enable` command or the `jpcconf` `prodname` `disable` command to match the setting.^#3
13	IPv6 communication	Check whether the execution result of the `jpcconf` `ipv6` `display` command matches.	Execute the `jpcconf` `ipv6` `enable` command or the `jpcconf` `ipv6` `disable` command to match the setting.^#3
14	Port number settings	Check whether the execution result of the `jpcconf` `port` `list` `-key` `stat` command matches.^#4	Execute the `jpcconf` `port` `define` `-key` `stat` command to match the setting.^#3
15	Encrypted communication	Check whether the execution result of the `jpcwconf` `https` `display` command matches.	Execute the `jpcwconf` `https` `enable` command or the `jpcwconf` `https` `disable` command to match the setting.^#3
16	Linking with JP1/IM2	Check whether the execution result of the `jpcconf` `im2` `display` command matches.	Execute the `jpcconf` `im2` `enable` command or the `jpcconf` `im2` `disable` command to match the setting.^#3

#1: For details, see the appendix that describes verification of definition information in the manual JP1/Performance Management Reference.
#2: For details, see the appendix that lists files and directories in the manual JP1/Performance Management Reference.
#3: For details, see the chapter that describes commands in the manual JP1/Performance Management Reference.
#4: The port number of Name Server and Status Server must match.

The following table shows definition information that must be matched in the startup information file (jpccomm.ini).

Table 11‒3: Definition information that must be matched in jpccomm.ini
No.	Section name	Label name
1	Common Section	Multiple Alarm Table Bind
2		Alarm Message Mode
3		JP1 Event Double Quote
4		Correlator Startup Mode
5		Retry Getting Alarm Status
6		Business Group Monitor Mode
7		Agent Remote Protection
8		Service List Protection
9		Prioritize Manager Startup Communication
10		Remote Action Control
11		Alarm Command Wait Mode
12		Alarm Command Timeout
13		Historical Data Collection Priority Mode
14		Random Retry Mode
15		Monitoring Suspend Mode
16		Auto Sync for Suspend Setting
17		Auto Alarm Bind Mode
18	All sections other than the following sections: Common Section Action Log Section	NS Keepalive Mode
19	All the following sections: Name Server Section Master Manager Section Correlator Section	NS Connection Timeout^#
19		NS Maximum Connections
20	Tools Section	StartService Retry Interval
21	Tools Section	StartService Retry Count
22	Agent Collector 0 Section	Historical Data Collection Priority Mode
23	Action Handler Section	Action Execution Count Limitation
24		Action Concurrent Execution Count
25		Action Execution Queue Count
26		Action Execution Time Limit

#: With version 11-50 or later, if the value differs between the primary and secondary managers, set the value to 70.

If an item in the startup information file (jpccomm.ini) is inconsistent, take action as follows:

Stop the Performance Management programs and services.
Open jpccomm.ini with a text editor.
Match the section names and label names of PFM - Manager in Table 11-3 between the primary Manager and the secondary Manager.
Save and close jpccomm.ini.
Start the Performance Management programs and services.

For details, see the chapter that describes definition files in the manual JP1/Performance Management Reference.

To Page Top