8.4.3 Creating a cluster environment after upgrading (for UNIX)

This subsection describes how to upgrade the Intelligent Integrated Management Base that is currently in use in a cluster environment.

Also, if you want to upgrade the linked product at the same time, perform the version upgrade of the linked product before performing step 8.

1. Stop JP1/IM - Manager.

   Stop all JP1/IM - Managers in both the physical and the logical host environments.

2. Copy the plug-ins directory.

   Copy the plugin directory of plug-ins directory on the physical host to the shared directory. Execute the following command:

   cp -a /etc/opt/jp1imm/plugin shared-directory/jp1imm/

3. Copy the definition file.

   Copy the definition file for the physical host to a shared directory. Execute the following command:

   cp -a -n /etc/opt/jp1imm/conf/imdd/ shared-directory/jp1imm/conf/imdd/
   cp -a /etc/opt/jp1imm/conf/imdd/*.model shared-directory /jp1imm/conf/imdd/
   cp -a /etc/opt/jp1imm/conf/imdd/system/*.model shared-directory /jp1imm/conf/imdd/system/
   cp -a /etc/opt/jp1imm/conf/imdd/system/*.update shared-directory /jp1imm/conf/imdd/system/
   cp -a /etc/opt/jp1imm/conf/imdd/system/fileoperation/*.update shared-directory /jp1imm/conf/imdd/system/fileoperation
   cp -a /etc/opt/jp1imm/conf/imdd/responseaction/*.model shared-directory/jp1imm/conf/imdd/responseaction
   cp -a /etc/opt/jp1imm/conf/imdd/fileoperation/*.model shared-directory/jp1imm/conf/imdd/fileoperation
   cp -a /etc/opt/jp1imm/conf/imdd/suggestion/*.model shared-directory/jp1imm/conf/imdd/suggestion
   cp -a /etc/opt/jp1imm/conf/imdd/plugin shared-directory/jp1imm/conf/imdd/
   cp -a /etc/opt/jp1imm/conf/imgndb/postgresql.conf.model shared-directory/jp1imm/conf/imgndb/
   cp shared-directory/jp1imm/conf/imdd/system/imdd_system.properties.update shared-directory/jp1imm/conf/imdd/system/imdd_system.properties
   cp shared-directory/jp1imm/conf/imdd/system/fileoperation/imdd_product_deffile_list.json.update shared-directory/jp1imm/conf/imdd/ system/fileoperation/imdd_product_deffile_list.json

4. Create an event-forwarding relay information directory.

   Create shared-directory/jp1imm/data/imdd/eventForward/. Execute the following command:

   mkdir -p shared-directory/jp1imm/data/imdd/eventForward/

5. Setup Intelligent Integrated Management Database.

   When upgrading from JP1/IM - Manager of V12, build logical host infrastructure for intelligent integrated databases.

   • For active host

     For details about the build process, see 8.3.3(5) JP1/IM - Manager (Intelligent Integrated Management Database) Setup.

   • For standby host

     For details about the build process, see 8.3.5(5) JP1/IM - Manager (Intelligent Integrated Management Database) Setup.

6. Add new settings.

   Add new settings corresponding to the new functions you are going to use.^#

   #

   When upgrading JP1/IM - Manager from 13-00 or 13-01 to 13-10 or later, add three lines ("web-enable-admin-api: true", "db-connections-max: 50", "db-writer-connection-concurrency: 1" (underlined part of "after change" below) to the end of the following file in a text editor.

   When the Intelligent Integrated Management database is rebuilt, this procedure is not required because it is added automatically.

   shared-directory/jp1imm/conf/imgndb/config.yml

   <Example of change>

   - Before change

   db-host: localhost

   db-name: imgndb

   db-user: imuser

   db-password: rCKsdJ8vSQn2

   db-port: 20705

   web-listen-address: localhost:20706

   log-level: info

   db-ssl-mode: allow

   promql-max-points-per-ts: 30001

   - After change

   db-host: localhost

   db-name: imgndb

   db-user: imuser

   db-password: rCKsdJ8vSQn2

   db-port: 20705

   web-listen-address: localhost:20706

   log-level: info

   db-ssl-mode: allow

   promql-max-points-per-ts: 30001

   web-enable-admin-api: true

   db-connections-max: 50

   db-writer-connection-concurrency: 1

   If you do not add a "web-enable-admin-api: true" line, deleting the trend data and deleting integrated agent info will fail.

   For details about deleting trend data and integrated agent information, see 2.2.1 List of Integrated Agents window in the JP1/Integrated Management 3 - Manager GUI Reference and see 5.11.4 Delete Trend Data and 5.18.2 Delete integrated agent info in the JP1/Integrated Management 3 -Manager Command, Definition File and API Reference.

   If you do not add the "db-connections-max: 50" and "db-writer-connection-concurrency: 1" rows, the following events may occur when collecting a large amount of performance data (when the sum of sample collected by integrated agent in the system (in the system of lower manager in a multi-stage configuration) exceeds 10,000 seconds):

   - Performance data is not saved in Intelligent Integrated Management Database and cannot be displayed and retrieved

   - Trend data management service memory usage increases

7. Start the service.

   Start the following services from the cluster software:

   • JP1/IM3-Manager_logical-host-name

   • JP1/IM3-Manager Intelligent Integrated DB Server_logical-host-name

   • JP1/IM3-Manager Trend Data Management Service_logical-host-name

   • JP1/IM3-Agent Base Server_logical-host-name

   • JP1/IM3-Agent Base Proxy Server_logical-host-name

8. By executing the jddcreatetree command, generate the IM management node-related files.

   For details about the jddcreatetree command, see jddcreatetree in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

9. By executing the jddupdatetree command in new and rebuilding mode, apply the definitions to the Intelligent Integrated Management server.

   For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

To Page Top