Hitachi

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


12.4.2 How to collect JP1/IM - Agent data

Organization of this subsection

(1) For Windows

(a) Integrated agent host

  1. Log in to integrated agent host.

  2. Execute the command to collect the generated file.

    • Secret key

    jimasecret -list > secretkeys.txt
    • System log

    wevtutil el 2> nul 1> event_list.txt
    for /f "delims=" %i in ( event_list.txt ) do echo %i 2> nul 1>> event_info.txt& wevtutil gli "%i" 2> nul 1>> event_info.txt& echo ----- 2> nul 1>> event_info.txt
    wevtutil qe System /rd:true /f:text 2> nul 1> System.evt
    wevtutil qe Application /rd:true /f:text 2> nul 1> Application.evt
    wevtutil qe Security /rd:true /f:text 2> nul 1> Security.evt
    for /f "delims=" %i in ( event_list.txt ) do echo %i 2> nul 1>> event_config_info.txt& wevtutil gl "%i" 2> nul 1>> event_config_info.txt& echo ----- 2> nul 1>> event_config_info.txt
    • OS info

    hostname 1> hostname.txt 2>nul
    "%CommonProgramFiles%\Microsoft Shared\MSInfo\msinfo32" /report os_system.txt /categories SystemSummary 2>nul 1>nul
    set > getenv.log
    • Communication status

    echo --Command netsh interface ip show address -- 1>> netstat.txt 2>nul
    netsh interface ip show address 1>> netstat.txt 2>nul
    echo --Command netsh interface ipv6 show address -- 1>> netstat.txt 2>nul
    netsh interface ipv6 show address 1>> netstat.txt 2>nul
    echo -- netsh advfirewall show currentprofile -- 1> firewall.txt 2>nul
    netsh advfirewall show currentprofile 1>> firewall.txt 2>nul
    echo -- netsh advfirewall firewall show rule -- 1>> firewall.txt 2>nul
    netsh advfirewall firewall show rule name=all verbose 1>> firewall.txt 2>nul
    • Process information

    tasklist /svc > proc_svc.list 2>&1
    tasklist /v > proc_v.list 2>&1
    • Configuration of silence

    With Alertmanager services running, collect silence settings by executing API for acquire Alertmanager's silence list. For more information about API, see the manual "JP1/Integrated Management 3 - Manager Command, Definition File and API Reference", "5.21.3 Getting a List of silence in Alertmanager".

    If you use curl command of OSS, collect the generated file by executing as shown below.

    curl --request GET http://localhost:Alertmanager port-number /api/v2/silences -o scilence.txt

    If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.

    • File list

    dir /S JP1/IM - Agent installation folder 1>jp1ima_list.txt 2>nul
  3. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Collection object

    OS info

    • %systemroot%\system32\drivers\etc\hosts

    • %systemroot%\system32\drivers\etc\services

    Installation documentation

    • When installed with the provided media

      The files under "System drive\Windows \Temp\HCDINST\"

    • When installed with a JP1/IM - Agent package downloaded from the Integrated Operations Viewer

      %TEMP%#\Logfile that was output when installing (MSI*.LOG)

    #: %TEMP% indicates the path specified in the environment-variable TEMP.

    Product information

    Files to be collected in the troubleshooting information described in "A.4(3) Integrated agent host (Windows)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

    Except for the following files:

    • Files under the shared folder for the logical host

    • Files under /usr/lib/systemd/system/

(b) Integrated agent host on Cluster System

  1. Log in to the integrated agent host of active server.

  2. Collect the files generated in executing commands.

    • Secret key

    jimasecret -list -l Shared folder > secretkeys.txt
    • Configuration of silence

    With Alertmanager services running, collect silence settings by executing API for auquire Alertmanager's silence list. For more information about API, see the manual "JP1/Integrated Management 3 - Manager Command, Definition File and API Reference", "5.21.3 Getting a List of silence in Alertmanager".

    If you use curl command of OSS, collect the generated file by executing as shown below.

    curl --request GET http:// Logical host name: Port number of Alertmanager of the logical host/ api/v2/silences -o scilence_Logical host name.txt

    If Alertmanager is running on a physical host in the active system, execute the following procedure to collect the generated files.:

    curl --request GET http://localhost: physical-host Alertmanager port-number /api/v2/silences -o scilence.txt

    If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.

    • File list

    dir /S JP1/IM - Agent install destination directory 1>jp1ima_list.txt 2>nul
    dir /S Shared Directory 1>jp1ima_list_Logical Hostname.txt 2>nul
    • System log, OS info, communication status, and processing information

    See "System log", "OS info", "Communication status", and "Process info" in step 2 of " 12.4.2 (1)(a)Integrated agent host".

  3. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Objects to be Collected

    OS info

    See "OS info" and "Installation documentation" in step 3 of " 12.4.2(1)(a) Integrated agent host".

    Installation documentation

    Product information

    Files to be collected in the troubleshooting information described in "A.4(3) Integrated agent host (Windows)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

    Except for the following files:

    • Files under /usr/lib/systemd/system/

  4. Log in to integrated agent host of the standby system.

  5. collect the files generated by executing commands.

    • Configuration of silence

    With Alertmanager services running, collect silence settings by executing API for acquire Alertmanager's silence list. For more information about API, see the manual "JP1/Integrated Management 3 - Manager Command, Definition File and API Reference", "5.21.3 Getting a List of silence in Alertmanager".

    If Alertmanager is running on a physical host in the standby system, execute the following procedure when using curl command of OSS to collect the generated filename:

    curl --request GET http://localhost: physical-host Alertmanager port-number /api/v2/silences -o scilence.txt

    If silence setting contains sensitive information such as passwords, delete the corresponding definition from the definition file after collection.

    • System log, OS info, communication status, process information, file list

    See "System log", "OS info", "Communication status", "Process information", and "File list" in step 2 of " 12.4.2(1)(a) Integrated agent host".

  6. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Objects to be Collected

    OS info

    See "OS info" and "Installation documentation" in step 3 of " 12.4.2(1)(a) Integrated agent host".

    Installation documentation

    Product information

    Files to be collected in the troubleshooting information described in "A.4(3) Integrated agent host (Windows)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

    Except for the following files:

    • Files under /usr/lib/systemd/system/

(c) Integrated agent host in Containers

Same as "12.4.2(1)(a) Integrated agent host".

(d) Integration Manager Host

Collect the data related to JP1/IM - Agent management base (imbase, imbaseproxy) with the data collection tool (jim_log.bat).

For the file to be collected, refer to the file folder list in "Appendix A.4 (1) Integrated Manager Host (Windows)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

(e) Integration Manager Host on Cluster Systems

12.4.2(1)(d) Integration Manager Host".

(2) For UNIX

(a) Integrated agent host

  1. Log in to integrated agent host.

  2. Collect the files generated by executing commands.

    • Secret key

    jimasecret -list > secretkeys.txt
    • OS info

    /bin/rpm -qa > os_inst_pp.list 2> /dev/null
    /sbin/sysctl -a > kernel_param.list  2> /dev/null
    hostname >> hostname.txt 2> /dev/null
    echo "-- uname --" > os_system.txt 2> /dev/null
    uname -a >> os_system.txt 2> /dev/null
    echo "-- ls -l /boot --" >> os_system.txt 2> /dev/null
    ls -l /boot >> os_system.txt 2> /dev/null
    echo "-- cat /etc/os-release --" >> os_system.txt 2> /dev/null
    cat /etc/os-release >> os_system.txt 2> /dev/null
    echo "-- timedatectl --" >> os_system.txt 2>&1
    timedatectl >> os_system.txt 2>&1
    env > getenv.log 2> /dev/null
    • Communication status

    echo "--Command ss -a --" > netstat.txt 2> /dev/null
    ss -a >> netstat.txt 2> /dev/null
    echo "--Command ip route --" >> netstat.txt 2> /dev/null
    ip route >> netstat.txt 2> /dev/null
    echo "--Command ip addr --" >> netstat.txt 2> /dev/null
    ip addr >> netstat.txt 2> /dev/null
    echo "-- iptables -v -n -L --line-numbers --" >> firewall.txt 2>&1
    iptables -v -n -L --line-numbers >> firewall.txt 2>&1
    echo "-- firewall-cmd --list-all-zones --" >> firewall.txt 2>&1
    firewall-cmd --list-all-zones >> firewall.txt 2>&1
    • Process information

    ps -elfa > proc.list 2> /dev/null
    • Configuration of silence

    See "silence setting" in step 2 of " 12.4.2(1)(a) Integrated agent host".

    • Setting of Start and stop

    For each unit definition file in JP1/IM - Agent, run the following command:

    systemctl is-enabled unit definition file Name > unit definition file Name.txt 2> /dev/null
    • Container information

    - For Docker

    docker version > ./Docker_Verison 2>&1
    docker ps -a --no-trunc > ./Docker_Process_Container_List 2>&1
    docker_container_list=`docker ps -a --no-trunc -q`;for loop in $docker_container_list;do echo $loop >> Docker_Top 2>&1;docker top $loop >> Docker_Top 2>&1;echo $loop >> Docker_Inspect 2>&1;docker inspect $loop >> Docker_Inspect 2>&1;done
    /bin/cat /etc/docker/daemon.json > docker_daemon.json 2>&1
    /bin/cat /etc/sysconfig/docker > sysconfig_docker 2>&1

    - For Podman

    podman version > Podman_Verison 2>&1
    podman ps --all --no-trunc --format={{.ID}} > Podman_Process_Container_List 2>&1
    podman_container_list=`podman ps --all --no-trunc --format={{.ID}}`;for loop in $podman_container_list;do echo $loop >> Podman_Top 2>&1;podman top $loop hpid args >> Podman_Top 2>&1;echo $loop >> Podman_Inspect 2>&1;podman inspect $loop >> Podman_Inspect 2>&1;done
    • File list

    ls -lR /opt/jp1ima > jp1ima_list.txt 2>&1
    ls -l /usr/lib/systemd/system/jpc* > systemd_jpc_list.txt 2>&1
    getfacl -R /opt/jp1ima > jp1ima_acl_list.txt 2>&1
    getfacl /usr/lib/systemd/system/jpc* > systemd_jpc_acl_list.txt 2>&1
  3. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Objects to be collected

    System log

    /var/log/messages*

    OS info

    • /etc/hosts

    • /etc/services

    Installation documentation

    • /etc/.hitachi/pplistd/pplistd

    • /etc/.hitachi/.install.log*

    • /etc/.hitachi/.uninstall.log*

    • /Files below"/tmp/HITACHI_JP1_INST_LOG"

    Product information

    Files to be collected in the troubleshooting information described in "A.4(4) Integrated agent host (Linux)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

    Except for the following files:

    • Files under the shared directory for the logical host

    • Files for logical hosts under /usr/lib/systemd/system/

(b) Integrated agent host on Cluster System

  1. Log in to the integrated agent host of active system.

  2. Collect the files generated by executing commands.

    • Secret key

    jimasecret -lis t-l Shared Directory > secretkeys.txt
    • Configuration of silence

    See "silence setting" in step 2 of " 12.4.2(1)(b)Integrated agent host on Cluster System".

    • File list

    ls -lR /opt/jp1ima > jp1ima_list.txt 2>&1
    ls -l /usr/lib/systemd/system/jpc* > systemd_jpc_list.txt 2>&1
    ls -lR Shared Directory > jp1ima_list_Logical Hostname.txt 2>&1
    getfacl -R /opt/jp1ima > jp1ima_acl_list.txt 2>&1
    getfacl /usr/lib/systemd/system/jpc* > systemd_jpc_acl_list.txt 2>&1
    getfacl -R Shared Directory > jp1ima_acl_list_Logical Hostname.txt 2>&1
    • OS, communication status, process information, settings of start and stop, and container information

    • See "OS Info", "Communication Status", "Process Info", "Settings of Start and Stop", and "Container Information" in step 2 of " 12.4.2(2)(a)Integrated agent host".

  3. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Objects to be collected

    System log

    See "System log", "OS info", and "Installation documentation" in step 3 of " 12.4.2(2)(a)Integrated agent host".

    OS info

    Installation documentation

    Product information

    Files to be collected in the troubleshooting information described in "A.4(4) Integrated agent host (Linux)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

  4. Log in to integrated agent host of the standby system.

  5. Collect the files generated by executing commands.

    • Configuration of silence

    See "silence setting" in step 4 of " 12.4.2(1)(b)Integrated agent host on Cluster System".

    • OS, communication status, process information, settings of start and stop, container information, file list

    See "OS Info", "Communication Status", "Process Info", "Settings of start and stop", "Container Info", and "File List" in step 2 of " 12.4.2(1)(a)Integrated agent host".

  6. Manually collect the necessary files.

    Manually collect the files listed in the following table.

    Data to be collected

    Collection object

    System log

    See "System log", "OS info", and "Installation documentation" in step 3 of " 12.4.2(2)(a)Integrated agent host".

    OS info

    Installation documentation

    Product information

    Files to be collected in the troubleshooting information described in "A.4(4) Integrated agent host (Linux)" in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

    Except for the following files:

    • Files under the shared directory for the logical host

(c) Integrated agent host in Containers

Same as "12.4.2(2)(a) Integrated agent host".

(d) Integrated Manager Host

Collect the data related to JP1/IM - Agent management base (imbase, imbaseproxy) with the data collection tool (jim_log.sh).

For the file to be collected, refer to the file and directory list in "Appendix A.4 (2) Integrated Manager Host (Linux) " in the manual "JP1/Integrated Management 3 - Manager Overview and System Design Guide".

(e) Integrated Manager Host on Cluster Systems

Same as " 12.4.2(2)(d) Integrated Manager Host".