Hitachi

JP1 Version 13 JP1/Integrated Management 3 - Manager Configuration Guide


7.6.2 Upgrade installation of JP1/IM - Agent (for Windows)

Install JP1/IM - Agent on the local disks of primary server and secondary server.

  1. Stop JP1/IM - Agent servicing.

    Stop JP1/IM - Agent of logical host from the cluster software.

    If physical host is also used, JP1/IM - Agent of physical host is stopped.

  2. Upgrade installation of JP1/IM - Agent.

    For details about how to install the software, see 1.3.1(3) Procedure of JP1/IM - Agent installation.

    This command is executed for both primary server and secondary server.

  3. Add the contents of the share folder. (When upgrading from 13-01 or earlier to 13-10 or later)

    1. Create the following folders in the shared folder.

    Go to the shared folder at the command prompt, and then execute the following command:

    mkdir jp1ima\data\web_exporter
    mkdir jp1ima\logs\web_exporter
    mkdir jp1ima\logs\web_exporter\trace
    mkdir jp1ima\logs\vmware_exporter
    mkdir jp1ima\lib

    2. Copy the added definition files (with extension ".model" and ".update" file) to a shared folder.

    At the command prompt, execute the following command:

    xcopy Agent-path\conf\jpc_file_sd_config_vmware.yml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_file_sd_config_web.yml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_playwright.config.ts.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_vmware_exporter.yml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_vmware_exporter_service.xml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_web_exporter.yml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_web_exporter_service.xml.model shared-folder\jp1ima\conf
    xcopy Agent-path\conf\jpc_product_deffile_list.json.update shared-folder\jp1ima\conf

    3. Copy the files under lib folder to the shared folder. (When using Web scenario monitoring function)

    Copy the following folders that exist in the Agent-path\lib of the primary server under the shared-folder\jp1ima\lib.

    • playwright folder

    • nodejs folder

    At the command prompt, execute the following command:

    xcopy Agent-path\lib\playwright shared-folder\jp1ima\lib\playwright /s /e /i
    xcopy Agent-path\lib\nodejs shared-folder\jp1ima\lib\nodejs /s /e /i

    4. Removes ".model" or ".update" from file name of the definition file.

    For the definition files that you copied to the shared-folder\jp1ima\conf, remove ".model" or ".update" that is granted to the end of file name.

    At the command prompt, execute the following command:

    ren shared-folder\jp1ima\conf\*.model *.
    move /y shared-folder\jp1ima\conf\jpc_product_deffile_list.json.update shared-folder\jp1ima\conf\jpc_product_deffile_list.json

    5. Change the access permissions of definition files and folders that require security-protection to Administrators only.

    When copying files and folders to shared-folder, access permissions are overwritten with those in the destination folder. Therefore, reconfigure the access permissions of the following files and folders to Administrators only.

    shared-folder\jp1ima\data\web_exporter
    shared-folder\jp1ima\logs\web_exporter\trace
    shared-folder\jp1ima\lib\playwright\tests
    shared-folder\jp1ima\conf\jpc_playwright.config.ts

    6. Modify the variables listed in the added definition file.

    The definition files copied to shared-folder\jp1ima\conf contains the variable names listed in the table below. Search for each variable name and rewrite all corresponding parts as shown in the table below.

    Variable name

    Value to be rewritten

    @@autostart@@

    Replace with "Manual".

    @@hostname@@

    Replace with logical host name.

    @@installdir1@@

    Replace it with the path of the folder where you want to install the JP1/IM - Agent.

    @@installdir2@@

    Replace with the path of the shared folder.

    7. Change the binding method of the added service to the IP binding method.

    Both physical host and logical host must be setup.

    For physical host, both nodes require setup. For physical host, restart of the service is required after changing setup.

    In physical host, physical host name is setup to the changes in the definition file as shown below.

    Service

    Target file

    Change point

    web_exporter

    Agent-path\bin\jpc_web_exporter_service.xml

    Specify the physical host name for --web.listen-address.

    --web.listen-address="host-name:port"

    vmware_exporter

    Agent-path\bin\jpc_vmware_exporter_service.xml

    Add the command option --address to <arguments> as follows.

    <arguments>

    --address="physical-host-name"

    </arguments>

    In logical host, logical host is named setup to the changes in definition file below.

    Service

    Target file

    Change point

    web_exporter

    shared-folder\jp1ima\conf\jpc_web_exporter_service.xml

    Specify the logical host name for --web.listen-address.

    --web.listen-address="host-name:port"

    vmware_exporter

    shared-folder\jp1ima\conf\jpc_vmware_exporter_service.xml

    Add the command option --address to <arguments> as follows.

    <arguments>

    --address="logical-host-name"

    </arguments>

    8. Add a logical host name to the service ID and display name in the added service definition file.

    For the added service definition files in the shared-folder\jp1ima\conf, assign logical host names to <id> and <name> described in the files.

    Please implement this procedure for services that are not in use.

    Target file

    Before change

    After change

    shared-folder\jp1ima\conf\jpc_web_exporter_service.xml

    <id>jpc_web_exporter</id>

    <id>jpc_web_exporter_logical-host-name</id>

    <name>JP1/IM3-Agent Synthetic web metric collector</name>

    <name>JP1/IM3-Agent Synthetic web metric collector logical-host-name</name>

    shared-folder\jp1ima\conf\jpc_vmware_exporter_service.xml

    <id>jpc_vmware_exporter</id>

    <id>jpc_vmware_exporter_logical-host-name</id>

    <name>JP1/IM3-Agent VMware metric collector</name>

    <name>JP1/IM3-Agent VMware metric collector logical-host-name</name>

    9. Add a logical host name to the file name of the added service definition file.

    Add a logical host name to the file name of the service definition file under the shared-folder\jp1ima\conf.

    File name before change: jpc_service-name_service.xml

    File name after change: jpc_service-name_service_logical-host-name.xml

    Please implement this procedure for services that are not in use.

    At the command prompt, execute the following command:

    ren shared-folder\jp1ima\conf\jpc_vmware_exporter_service.xml jpc_vmware_exporter_service_logical-host-name.xml
    ren shared-folder\jp1ima\conf\jpc_web_exporter_service.xml jpc_web_exporter_service_logical-host-name.xml

    10. Copy the added service definition files to the destination folder.

    Copy the added service definition files (Files renamed in step 9) in the shared-folder\jp1ima\conf to Agent-path\bin of both the primary server and the secondary server.

    Please implement this procedure for services that are not in use.

    At the command prompt, execute the following command:

    xcopy shared-folder\jp1ima\conf\jpc_vmware_exporter_service_logical-host-name.xml Agent-path\bin
    xcopy shared-folder\jp1ima\conf\jpc_web_exporter_service_logical-host-name.xml Agent-path\bin

    11. Delete the service definition files in the shared folder.

    Delete the service definition files (Copy source files in step 10) in the shared-folder\jp1ima\conf because it is not required.

    Please implement this procedure for services that are not in use.

    At the command prompt, execute the following command:

    del shared-folder\jp1ima\conf\jpc_vmware_exporter_service_logical-host-name.xml
    del shared-folder\jp1ima\conf\jpc_web_exporter_service_logical-host-name.xml

    12. Generate a Windows servicing program for the logical host of the added service.

    On both the executable server and the standby server, copy the Windows serviced program in the Agent-path\bin to create a Windows serviced program for the logical host.

    Note that you copy the file name, not change it. Keep the source file as well.

    Copy original file name: jpc_service-name_service.exe

    copy destination file name: jpc_service-name_service_logical-host-name.exe

    Please implement this procedure for services that are not in use.

    At the command prompt, execute the following command:

    echo f | xcopy Agent-path\bin\jpc_vmware_exporter_service.exe Agent-path\bin\jpc_vmware_exporter_service_logical-host-name.exe
    echo f | xcopy Agent-path\bin\jpc_web_exporter_service.exe Agent-path\bin\jpc_web_exporter_service_logical-host-name.exe

    13. Register the service for the logical host of the added service with Windows.

    When you want to use the added service on a logical host, both the primary server and the secondary server must register the services for logical host to Windows.

    At the command prompt, execute the following command:

    Agent-path\tools\jpc_service -on jpc_vmware_exporter -h logical-host-name
    Agent-path\tools\jpc_service -on jpc_web_exporter -h logical-host-name

    If you do not want the added service to be used on a logical host, move the following discovery configuration file from the shared-folder/jp1ima/conf folder to the shared-folder/jp1ima/conf/jpc_file_sd_config_off folder.

    At the command prompt, execute the following command:

    move shared-folder/jp1ima\conf\jpc_file_sd_config_vmware.yml shared-folder/jp1ima\conf\jpc_file_sd_config_off
    move shared-folder/jp1ima\conf\jpc_file_sd_config_web.yml shared-folder/jp1ima\conf\jpc_file_sd_config_off

    14. Verify that Windows has registered to servicing.

    On both the primary server and the secondary server, display the service of Windows to confirm that the service for logical host has been registered.

    The name of the service for the logical host is the name set in <name> in step 8.

    15. Perform the required setup for the added add-on program.

    When using the added add-on program, see 1.21.2(13) Setting up Web scenario monitoring function , 1.21.2 (14) Setting up VMware exporter , 1.21.2(3)(i) Add a Web exporter scrape job (for Windows) (optional), and 1.21.2(3)(j) Add a VMware exporter scrape job (for Windows) (optional) to make the necessary settings.

    16. Reister the service for logical host in the cluster software.

    When you register the cluster software, setup it so that it has the following dependencies: Register only the services you want to use into the clustered software.

    Service

    Dependency

    jpc_web_exporter_service_logical-host-name

    • IP address resources

    • Physical disk resources

    jpc_vmware_exporter_service_logical-host-name

    • IP address resources

    • Physical disk resources

  4. Copy the existing Windows service program for logical host again.

    Copy Windows service program in Agent-path\jp1ima\bin. Overwrites Windows service program for logical host after copying.

    This command is executed for both primary server and secondary server.

    Instead of renaming the file, copy the file and leave the source file.

    Copy original file name: jpc_service-name_service.exe

    Copy destination file name: jpc_service-name_service_logical-host-name.exe

    The following shows a sample jpc_alertmanager_service.exe.

    Copy original file name

    Copy destination file name

    jpc_alertmanager_service.exe

    jpc_alertmanager_service_logical-host-name.exe

  5. Start JP1/IM - Agent servicing.

    Start JP1/IM - Agent of logical host servicefrom the cluster software.

    If you are also using physical host, start JP1/IM - Agent service of physical host.