C.6 Estimates and settings when multiple PFM - Agents and PFM - RMs are connected to PFM - Manager

(1) How to increase the upper limit of connected PFM - Agents and PFM - RMs

When the number of PFM - Agents or PFM - RMs connected to PFM - Manager exceeds the upper limit of connection, connection stalls or reconnection between PFM - Agent and PFM - Manager (or PFM - RM and PFM - Manager) frequently occurs. This might lead to a significant increase of the load on PFM - Manager, making it unable to maintain a connection for an extended period of time. As a result, the following problems might occur:

• Operations in PFM - Web Console time-out

• When starting PFM - Agent or PFM - RM, it takes a long time for PFM - Manager to switch from the stand-alone mode to the normal operation mode

If these problems occur, perform the following procedure in PFM - Manager:

1. Do the following to estimate the maximum time for an idle timeout for PFM - Manager:

   (1) Obtain the minimum record collection interval (in seconds) for each PFM - Agent and PFM - RM connected to PFM - Manager.

   (2) From the values obtained in step 1 above, determine the maximum record collection interval (in seconds).

   (3) Compare 360 with the collection interval obtained in (2) + 60. Whichever is larger is the maximum time (in seconds) for an idle timeout for PFM - Manager.

2. Edit the NS Connection Timeout and NS Maximum Connections labels in the Name Server Section, Master Manager Section, and Correlator Section sections of the jpccomm.ini file.

   The jpccomm.ini file is stored in the following destination. The environment-directory indicates the directory specified when the jpcconf ha setup command was executed.

   OS	Storage location for the jpccomm.ini file
   In Windows:	PFM - Manager (for physical host use) installation-folder\jpccomm.ini PFM - Manager (for logical host use) environment-directory\jp1pc\jpccomm.ini
   In UNIX:	PFM - Manager (for physical host use) /opt/jp1pc/jpccomm.ini PFM - Manager (for logical host use) environment-directory/jp1pc/jpccomm.ini

   Edit the following sections in the jpccomm.ini file:

   [Before change]

   NS Connection Timeout=70
             :
   NS Maximum Connections=100

   [After change]

   NS Connection Timeout=Maximum time for an idle timeout for PFM - Manager that was obtained in step 1
             :
   NS Maximum Connections=1500

3. Restart PFM - Manager.

If this problem still occurs even after changing the settings as above, see C.6(2) If reconnection occurs frequently because the collection interval is too short for details about how to change the record collection period.

Reference note

In an environment where PFM - Manager 09-00 or later is newly installed, NS Maximum Connections is set as 1500 by default.

To Page Top

(2) If reconnection occurs frequently because the collection interval is too short

If PFM - Manager or PFM - Base on the same device is version 09-00 or earlier and if the minimum record collection interval for all collected records is set as 60 seconds or more for PFM - Agent and 300 seconds or more for PFM - RM, reconnection to PFM - Manager is performed each time records are collected.

Thus, if multiple PFM - Agents or PFM - RMs is connected, attempts to reconnect to PFM - Manager are repeatedly performed. This might cause a connection failure, such as events being sent from PFM - Agent to PFM - Manager (or from PFM - RM to PFM - Manager).

If this problem occurs, we recommend that you reduce the load on PFM - Manager. To reduce the load, perform the following setting on the PFM - Agent host (with a minimum record collection interval of at least 60 seconds) or the PFM - RM host (with a minimum record collection interval of at least 300 seconds).

1. Obtain the minimum record collection interval for the PFM - Agent host or PFM - RM host.

   (a) For each instance of PFM - Agent or PFM - RM, obtain the minimum record collection interval (in seconds) set for records collected by PFM - Agent or PFM - RM, or for records used to evaluate an alarm.

   (b) If there are several instances of the same PFM - Agent or PFM - RM product, compare the minimum values obtained in step (a) to determine the maximum value. If there is only a single instance of the same PFM - Agent or PFM - RM product, use the value obtained in step (a).

2. Edit the NS Cache Maintenance Time label in the Agent Collector x Section of the jpccomm.ini file.

   In the Agent Collector x Section, x represents the product ID specific to each PFM - Agent or PFM - RM. For details about the product ID for PFM - Agent or PFM - RM, see the list of identifiers in the appendix of each PFM - Agent or PFM - RM manual.

   The jpccomm.ini file is stored in the following destination. The environment-directory indicates the directory specified when the jpcconf ha setup command was executed.

   OS	Storage location for the jpccomm.ini file
   In Windows:	PFM - Agent or PFM - RM (for physical host use) installation-folder\jpccomm.ini PFM - Agent (for logical host use) environment-directory\jp1pc\jpccomm.ini
   In UNIX:	PFM - Agent or PFM - RM (for physical host use) /opt/jp1pc/jpccomm.ini PFM - Agent (for logical host use) environment-directory/jp1pc/jpccomm.ini

   Edit the following sections in the jpccomm.ini file:

   [Before change]

   NS Cache Maintenance Time=70

   [After change]

   NS Cache Maintenance Time=minimum-collection-interval-calculated-in-Step-1 + 10

3. Restart PFM - Agent.

To Page Top