11.6.1 Checking duplication of the PFM - Manager definition information
Use the following procedure to check whether the PFM - Manager definition information is duplicated and consistent between the primary Manager and the secondary Manager.
- Organization of this subsection
(1) Checking alarm information of alarm definition and action definition
-
Start the PFM - Manager service on the primary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the primary Manager.
jpctool alarm export -f output-file-name -key service-key
-
Start the PFM - Manager service on the secondary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the secondary Manager.
jpctool alarm export -f output-file-name -key service-key
-
Compare the output files of the primary Manager and the secondary Manager.
If the output files match, the alarm information matches.
(2) Checking binding information
-
Start the PFM - Manager service on the primary Manager if it has stopped
-
Execute the following command in PFM - Manager on the primary Manager.
jpctool alarm list -key service-key -table alarm-table-name
-
Start the PFM - Manager service on the secondary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the secondary Manager.
jpctool alarm list -key service-key -table alarm-table-name
-
Compare the display results of the primary Manager and the secondary Manager.
If the display results match, the binding information matches.
(3) Checking report definitions
-
Start the PFM - Manager service and the PFM - Web Console service on the primary Manager if they have stopped.
-
Execute the following command in PFM - Web Console on the primary Manager.
Specify the input file so that all reports are output.
jpcrdef output -o output-file-name input-file-name
-
Execute the following command in PFM - Web Console on the secondary Manager.
Specify the input file so that all reports are output.
jpcrdef output -o output-file-name input-file-name
-
Compare the output files of the primary Manager and the secondary Manager.
If the output files match, the report definitions match.
(4) Checking business group information
-
Start the PFM - Manager service on the primary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the primary Manager to display the list of business group names.
jpcconf bgdef list
-
Check the result of step 2 and execute the following command in PFM - Manager on the primary Manager.
jpcconf bgdef export -f output-file-name -group business-group-name
-
Start the PFM - Manager service on the secondary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the secondary Manager to display the list of business group names.
jpcconf bgdef list
-
Check the result of step 5 and execute the following command in PFM - Manager on the secondary Manager.
jpcconf bgdef export -f output-file-name -group business-group-name
-
Compare the output files of the primary Manager and the secondary Manager.
If the output files match, the business group information matches.
(5) Checking Performance Management user account information and Agents tree (User Agents) information
-
Compare files that are collected from the primary Manager and the secondary Manager.
The collected files are in binary format. Compare these files. If they match, the Performance Management user account information and the User Agents information are consistent. Use a command, such as FC (Windows) or diff (UNIX), to compare the binary files.
The Performance Management user account information and the User Agents information are managed in the same file. The following table shows the file path.
Table 11‒7: Path of files to be compared Data
Authentication mode
Path
Performance Management user account information, Agents tree (User Agents) information
PFM authentication
- In Windows:
-
installation-folder\mgr\viewsvr\data\UserList.lmk
- In UNIX:
-
/opt/jp1pc/mgr/viewsvr/data/UserList.lmk
JP1 authentication
- In Windows:
-
installation-folder\mgr\viewsvr\data\UserListforJP1.lmk
- In UNIX:
-
/opt/jp1pc/mgr/viewsvr/data/UserListforJP1.lmk
(6) Checking managed agent information
-
Start the PFM - Manager service on the primary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the primary Manager.
jpctool service list -id * -host *
-
Start the PFM - Manager service on the secondary Manager if it has stopped.
-
Execute the following command in PFM - Manager on the secondary Manager.
jpctool service list -id * -host *
-
Compare the display results of the primary Manager and the secondary Manager.
If the service IDs other than Status Server, Trap Generator, and View Server match, the managed agent information matches.
(7) Checking the settings of PFM - Manager for the connection destination
-
Execute the following command in PFM - Manager on the primary Manager.
jpcconf mgrhost display
-
Execute the following command in PFM - Manager on the secondary Manager.
jpcconf mgrhost display
-
Compare the display results of the primary Manager and the secondary Manager.
If the display results match, the settings of PFM - Manager for the connection destination match between the primary Manager and the secondary Manager.
(8) Checking the settings of auto alarm bind
-
Compare files as binary that are collected from the primary Manager and the secondary Manager.
The following files are collected:
- In Windows:
-
installation-directory\jpcautobind.cfg
- In UNIX:
-
/opt/jp1pc/jpcautobind.cfg
Compare these files. If they match, the settings of auto alarm bind are consistent. Use a command, such as FC (Windows) or diff (UNIX), to compare the binary files.