5.4.4 Configuring the functionality for binding multiple alarm tables
You must be using version 09-00 or later of PFM - Manager and PFM - Web Console to use the functionality for binding multiple alarm tables. While the functionality for binding multiple alarm tables is enabled, you cannot connect from PFM - Web Console whose version is earlier than 09-00.
The following table describes the configuration of the monitoring agents that can bind multiple alarm tables. In order to use a monitoring agent to bind multiple alarm tables, the configuration in the table must be marked as Y. Even if a monitoring agent with an N marked configuration exists in the system, you can still use the functionality for binding multiple alarm tables. However, you cannot use the function to bind multiple alarm tables with the applicable monitoring agent. If you use a monitoring agent with an N marked configuration to bind multiple alarm tables, evaluation results cannot be guaranteed for the alarm of the applicable monitoring agent.
|
PFM - Agent version |
PFM - Manager or PFM - Base version on a same host |
||
|---|---|---|---|
|
09-00 or later |
Earlier than 09-00 |
None |
|
|
08-00 or later |
Y |
N |
-- |
|
Before 08-00 |
N |
N |
N |
- Legend:
-
Y: Multiple alarm tables can be bound.
N: Multiple alarm tables cannot be bound.
--: Unavailable
To enable or disable the functionality for binding multiple alarm tables, directly edit the contents of the jpccomm.ini file on the PFM - Manager host. The jpccomm.ini file is stored in the following locations:
- On physical hosts:
-
- In UNIX:
-
/opt/jp1pc/
- On logical hosts:
-
- In UNIX:
-
environment-directory/jp1pc/
- Organization of this subsection
(1) Enabling the functionality for binding multiple alarm tables
To enable the functionality for binding multiple alarm tables:
-
Stop Performance Management programs and services.
Stop all Performance Management programs and services that are running by using the jpcspm stop command. If the programs are running on a cluster system, stop them from the cluster software.
-
Use a text editor or a similar tool to open the jpccomm.ini file.
-
Enable the functionality for binding multiple alarm tables.
Change the following label value in the [Common Section] section in the jpccomm.ini file.
Multiple Alarm Table Bind=1
-
Save and then close the jpccomm.ini file.
-
Start Performance Management programs and services by using the jpcspm start command.
If the programs are running on a cluster system, start them from the cluster software.
-
Restart the PFM - Web Console.
(2) Disabling the functionality for binding multiple alarm tables
To disable the functionality for binding multiple alarm tables:
-
Stop Performance Management programs and services.
Stop all Performance Management programs and services that are running by using the jpcspm stop command. If the programs are running on a cluster system, stop them from the cluster software.
-
Use a text editor or a similar tool to open the jpccomm.ini file.
-
Disable the functionality for binding multiple alarm tables.
Change the following label value in the [Common Section] section in the jpccomm.ini file.
Multiple Alarm Table Bind=0
-
Save and then close the jpccomm.ini file.
-
Start Performance Management programs and services by using the jpcspm start command.
If the programs are running on a cluster system, start them from the cluster software.
-
Restart the PFM - Web Console.
- Note:
-
If you disable the functionality for binding multiple alarm tables when multiple alarm tables are bound with PFM - Agent or PFM - RM, the message KAVE00317-W is output the next time you start the Master Manager service. In addition, all the alarm tables bound with the applicable PFM - Agent or PFM - RM are unbound. As a result, it might take some time to start the Master Manager service after the functionality has been disabled. For the operating PFM - Agent or PFM - RM, the multiple alarm tables stay bound until the applicable PFM - Agent or PFM - RM is restarted. If you disabled the functionality for binding multiple alarm tables, in order for the binding status update to take effect, you must restart the PFM - Agent or PFM - RM that outputs the KAVE00317-W message.