1.8.1 When starting PFM - Agent or PFM - RM in a large-scale system

When starting Performance Management, normally you start PFM - Manager first, and then PFM - Base and either PFM - Agent or PFM - RM. In a large-scale system consisting of multiple servers, normally you start the system by controlling the sequence in which services are started among these servers.

You can still collect the performance data by starting PFM - Base and either PFM - Agent or PFM - RM first even when the Master Manager service and the Name Server service of PFM - Manager are not running.

The stand-alone mode refers to when PFM - Agent and PFM - Base or PFM - RM and PFM - Base operate separately.

The modes of the system are designated depending on the state of each program as follows:

Only PFM - Agent, PFM - RM, or PFM - Base is running.

This is called stand-alone mode.
Initially PFM - Manager is running together with PFM - Agent, PFM -RM, or PFM - Base. Then PFM - Manager is stopped, so that only PFM - Base, PFM - Agent, or PFM - RM is running.

This is called non stand-alone mode.
PFM - Manager, PFM - Base, and either PFM - Agent or PFM - RM have started in this sequence and are all running.

This is called normal mode.

Note:: PFM - Agent or PFM - RM cannot start by itself when PFM - Agent or PFM - RM is installed on the same host as PFM - Manager.

Organization of this subsection

(1) Overview of stand-alone mode
(2) Functions available in stand-alone mode
(3) Commands available in stand-alone mode
(4) Overview of non stand-alone mode
(5) Functions available in non stand-alone mode
(6) Commands available in non stand-alone mode

(1) Overview of stand-alone mode

When PFM - Agent, PFM - RM, or PFM - Base starts, they might fail to communicate with PFM - Manager if, for example, the Master Manager or Name Server service of PFM - Manager is not running. If communication with PFM - Manager fails, PFM - Agent, PFM - RM, or PFM - Base starts in stand-alone mode to collect performance data.

The system in stand-alone mode checks the connection to PFM - Manager after startup once every 5 minutes or at random intervals according to the settings in the startup information file (jpccomm.ini) on the local host. If PFM - Manager starts after PFM - Agent, PFM - RM, or PFM - Base have already started in stand-alone mode, and PFM-Manager performs a successful connection check with one of those programs, that program switches from stand-alone mode to normal mode connected to PFM - Manager. At this time, you can consult history reports to check the performance data stored in PFM - Agent or PFM - RM during stand-alone mode.

However, there are partial restrictions on the functionality and executable commands of Performance Management when PFM - Agent and PFM - Base or PFM - RM and PFM - Base run in stand-alone mode.

To Page Top

(2) Functions available in stand-alone mode

Table 1‒3: Functions available in stand-alone mode
Function	Availability	Service name
Starting and stopping services, and checking operation status	Y	In PFM-Agent host Agent Store, Agent Collector, and Action Handler In PFM-RM host Remote Monitor Store, Remote Monitor Collector, and Action Handler
Collecting history data	Y	In PFM-Agent host Agent Store and Agent Collector In PFM-RM host Remote Monitor Store and Remote Monitor Collector
Displaying reports	N	Agent Store and Remote Monitor Store
Issuing alarms that indicate agent start	Y	Agent Collector and Remote Monitor Collector
Monitoring the performance data by alarms	N	Agent Collector and Remote Monitor Collector
Executing actions in response to alarm events	N	Action Handler
Service status management	Y	Status Server

Legend:

Y: Available

N: Not available

To Page Top

(3) Commands available in stand-alone mode

Table 1‒4: Commands available in stand-alone mode
Command	Function	Availability
`jpcconf db define`	Changing the directory settings of the Agent Store service and the Remote Monitor Store service	Y
`jpcconf db display`	Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data	Y
`jpcconf db vrset`	Changing the version of the Store database	Y
`jpcconf hc`	Enabling or disabling the health check function	Y
`jpcconf stat`	Enabling or disabling the status management function	Y
`jpcras`	Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM	Y
`jpcspm start`	Starting services	Y
`jpcspm stop`	Stopping services	Y
`jpctool db backup`	Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
`jpctool db clear`	Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	N
`jpctool db dmconvert`	Converting the data model of backup data	Y
`jpctool db dump`	Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
`jpctool db import`	Importing backup data	Y
`jpctool service delete`	Deleting service information of the agents registered in Performance Management	N
`jpctool service list` (when other host is specified by the `-host` option)	Displaying the structure and status of the Performance Management program services	N
`jpctool service list` (when the `-host` option is not used)	Checking the status of service operations on the local host	Y

Legend:

Y: Available

N: Not available

#

You can execute commands only when specifying the -alone option.

To Page Top

(4) Overview of non stand-alone mode

Initially PFM - Manager runs together with PFM - Agent, PFM - RM or PFM - Base. Then PFM - Manager is stopped, so that only PFM - Base, PFM - Agent or PFM - RM is running. This is called non stand-alone mode.

Unlike stand-alone mode, the system does not check the connection to PFM - Manager once every 5 minutes in non stand-alone mode. When PFM - Manager starts, PFM - Agent or PFM - RM operates in normal mode. Performance data accumulated by PFM - Agent or PFM - RM in non-standalone mode can be viewed with historical reports.

Figure 1‒1: Overview of non stand-alone mode

Notes:

Alarm events cannot be reported to PFM - Manager when PFM - Agent or PFM - RM runs in non stand-alone mode. In such cases, the system holds alarm events by each alarm definition, and continues to attempt to report the alarm event until PFM - Manager starts. The oldest alarm event is overwritten when more than three alarm events are retained. All the retained alarm events are deleted when PFM - Agent or PFM - RM stops.

Reference note:

Because the Event Monitor and event history windows handle event data in different ways, the information displayed will differ.

Event history display of three alarm events that occurred in non stand-alone mode

PFM - Manager is stopped
PFM - Manager starts
The three alarms that occurred while PFM - Manager was stopped are sent from PFM - Agent.
The events are recorded by the Master Store service of PFM - Manager

Event information can now be displayed for all three events in the event history.

Event monitor display of three alarm events that occurred in non stand-alone mode

The event monitor displays the information stored in the PFM - Web Console cache.

The PFM - Web Console cache is cleared when PFM - Web Console reconnects to the View Server service of PFM - Manager.

When the PFM - Web Console connects to the View Server, its cache is synchronized with that of the View Server service and reconstructed.

In this case, only the most recent event related to the current alarm status of the agent is acquired.

If the alarm status received from the View Server service is normal (green), the event does not appear in the event monitor because the system is considered to be functioning normally.

If the alarm status is Warning (yellow) or Abnormal (red), the system is considered to be in a warning or abnormal state and the alarm event appears in the event monitor.

Note that alarm events for which Always notify is selected do not appear in the event monitor.

When PFM - Manager is restarted, the behavior of the alarm status indicating that a notification has been sent to PFM - Manager (the status of the alarm, indicated by the color of the alarm icon) differs depending on whether Correlator Startup Mode is enabled or disabled.

When Correlator Startup Mode is enabled (recommended)

A check of the information of the alarm status (alarm table status which is indicated by the color of the alarm icon) is performed when PFM - Manager receives an alarm event from PFM - Agent. This operation is for reducing the startup time of the Correlator service and preventing the startup of the Correlator service from failing. Until PFM - Manager receives an alarm event and verifies the agent status, PFM - Manager assumes that the agent status is unchanged since the last time PFM - Manager terminated.

When Correlator Startup Mode is disabled

The alarm statuses of all the agents that are registered in (connected to) the PFM - Manager service are checked when PFM - Manager restarts.

The information of alarm statuses (alarm table status, which is indicated by the color of the alarm icon) is checked.

For details about how to set Correlator Startup Mode, see the section that explains the setting items of the startup information file (jpccomm.ini) in the appendixes of the manual JP1/Performance Management Reference.

To Page Top

(5) Functions available in non stand-alone mode

Table 1‒5: Functions available in non stand-alone mode
Function	Availability	Service name
Starting and stopping services, and checking operation status	Y	In PFM-Agent host Agent Store, Agent Collector, and Action Handler In PFM-RM host Remote Monitor Store, Remote Monitor Collector, and Action Handler
Collecting history data	Y	In PFM-Agent host Agent Store and Agent Collector In PFM-RM host Remote Monitor Store and Remote Monitor Collector
Displaying reports	N	Agent Store and Remote Monitor Store
Monitoring the performance data by alarms	Y	Agent Collector and Remote Monitor Collector
Executing actions in response to alarm events	N^#	Action Handler
Service status management	Y	Status Server

Legend:

Y: Available

N: Not available

#

The system operates differently according to the following conditions:

When "LOCAL" is specified as the Action Handler service

If the host executing the action is running PFM - Base 09-00-09 or later or 10-00 or later

The action is executed even if PFM - Manager is stopped.

If the host executing the action is running PFM - Base 09-00-08 or earlier

If no action has been executed

No action is executed while PFM - Manager is stopped.

Even when PFM - Manager restarts, any action that was generated while PFM - Manager was stopped is not executed.
If at least one action has been executed but the Action Handler service that executed the action has not restarted

The action is executed even while PFM - Manager is stopped.

When a value other than "LOCAL" is specified as the Action Handler service

No actions are executed while PFM - Manager is stopped.

After PFM - Manager starts, any actions that were generated while PFM - Manager was stopped are executed. However, if you specify the Action Handler service on the PFM - Manager host, the actions might not be executed depending on the position of the Action Handler service in the startup sequence.

To Page Top

(6) Commands available in non stand-alone mode

Table 1‒6: Commands available in non stand-alone mode
Command	Function	Availability
`jpcconf db define`	Changing the directory settings of the Agent Store service or the Remote Monitor Store service	Y
`jpcconf db display`	Displaying information about the Agent Store service, the Remote Monitor Store service, or backup data	Y
`jpcconf db vrset`	Changing the version of the Store database	Y
`jpcconf hc`	Enabling or disabling the health check function	Y
`jpcconf stat`	Enabling or disabling the status management function	Y
`jpcras`	Collecting troubleshooting data of PFM - Manager, PFM - Agent, or PFM - RM	Y
`jpcspm start`	Starting services	Y
`jpcspm stop`	Stopping services	Y
`jpctool db backup`	Creating backup files of the data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
`jpctool db clear`	Deleting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	N
`jpctool db dmconvert`	Converting the data model of backup data	Y
`jpctool db dump`	Exporting data stored in the database of the Master Store service, the Agent Store service, or the Remote Monitor Store service	Y^#
`jpctool db import`	Importing backup data	Y
`jpctool service delete`	Deleting service information of the agents registered in Performance Management	N
`jpctool service list` (when other host is specified by the `-host` option)	Displaying the structure and status of the Performance Management program services	N
`jpctool service list` (when the `-host` option is not used)	Checking the status of service operations on the local host	Y

Legend:

Y: Available

N: Not available

#

You can execute commands only when specifying the -alone option.

To Page Top