12.4.2 How to collect JP1/IM - Agent data

(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.txt
   wevtutil qe Application /rd:true /f:text 2> nul 1> Application.txt
   wevtutil qe Security /rd:true /f:text 2> nul 1> Security.txt
   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

   • Service information

   sc query > service.list 2>&1

   • Configuration of silence

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

   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 Files under system-drive\Windows\Temp\HCDINST\ When installed with a JP1/IM - Agent package downloaded from the Integrated Operations Viewer Log files (MSI*.LOG) that was output when installing under %TEMP%#\ #: %TEMP% indicates the path specified in the environment-variable TEMP.
   Product information	■Files to be collected in the troubleshooting information described in Appendix A.4(3) Integrated agent host (Windows) in the 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/ ■If you deployed the OracleDB exporter, manually extract the following files: OracleDB exporter location\oracledb_exporter_windows\jp1ima\logs folder Service definition file of OracleDB exporter ■If you have already set up the SAP system log extract command, collect the following files manually: Environment parameter configuration file (any name.ini) Log files of SAP system log extract commands Trace files for SAP system log extract commands The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

(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 details about API, see 5.21.3 Get silence list of Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

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

   curl --request GET http://logical-host-name:logical-host-Alertmanager-port-number/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-host-name.txt 2>nul

   • System log, OS info, Communication status, Processing information, and Service information

   See System log, OS info, Communication status, Process information, and Service information 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 Appendix A.4(3) Integrated agent host (Windows) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. Except for the following files: Files under /usr/lib/systemd/system/ ■If you have already set up the SAP system log extract command, collect the following files manually: Environment-parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

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 details about API, see 5.21.3 Get silence list of Alertmanager in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

   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, service information, file list

   See System log, OS info, Communication status, Process information, Service 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 Appendix A.4(3) Integrated agent host (Windows) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. Except for the following files: Files under /usr/lib/systemd/system/ ■If you have already set up the SAP system log extract command, collect the following files manually: Environment-parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

(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, see the file folder list in Appendix A.4 (1) Integrated Manager host (Windows) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.

(e) Integration Manager Host on Cluster Systems

Same as 12.4.2(1)(d) Integration Manager Host.

(f) Monitored AIX hosts (When Node exporter for AIX is deployed)

1. Log in to the monitored AIX host.

2. Execute the command to collect the generated file.

   • OS information

   echo "-- lslpp -l -a --" > os_inst_pp.list 2> /dev/null
   lslpp -l -a >> os_inst_pp.list 2> /dev/null
   echo "-- /usr/sbin/instfix -a -icv --" >> os_inst_pp.list 2> /dev/null
   /usr/sbin/instfix -a -icv >> os_inst_pp.list 2> /dev/null
   lsattr -E -l sys0 > 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 "-- date --" >> os_system.txt 2>&1
   date >> os_system.txt 2>&1
   env > getenv.log 2> /dev/null

   • Communication status

   echo "--Command netstat -an --" > netstat.txt 2> /dev/null
   netstat -an >> netstat.txt 2> /dev/null
   echo "--Command netstat -rn --" >> netstat.txt 2> /dev/null
   netstat -rn >> netstat.txt 2> /dev/null
   echo "--Command ifconfig -a --" >> netstat.txt 2> /dev/null
   ifconfig -a >> netstat.txt 2> /dev/null
   echo "-- lsfilt --" >> firewall.txt 2>&1
   lsfilt >> firewall.txt 2>&1

   • Process information

   ps -elfa > proc.list 2> /dev/null

   • Autostart settings

   lsitab -a > lsitab.txt 2> /dev/null

   • File list

   ls -lR Node exporter for AIX location #/jp1ima > jp1ima_list.txt 2>&1

   # In the case of logical host operation, the shared folder of the logical host is located.

3. Manually collect the necessary files.

   Manually collect the files listed in the following table.

   Materials to be collected	Target of collection
   System log	/var/adm/syslog/syslog.log# # The destination of the system log is obtained by referring to the "/etc/syslog.conf" setting.
   OS information	/etc/hosts /etc/services
   Automatic stop setting	/etc/rc.shutdown

(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

   • Service information

   systemctl list-unit-files -t service > service.list 2> /dev/null

   • Configuration of silence

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

   • Settings 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 under /tmp/HITACHI_JP1_INST_LOG
   Product information	■Files to be collected in the troubleshooting information described in Appendix A.4(4) Integrated agent host (Linux) in the 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/ ■If you have placed OracleDB exporter, collect the following files manually: OracleDB exporter location/oracledb_exporter_linux/jp1ima/logs directory Unit definition file ■If you have already set up the SAP system log extract command, collect the following files manually: Environment parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

(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 -list -l shared-Directory > secretkeys.txt

   • Configuration of silence

   See Configuration of silence 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-host-name.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-host-name.txt 2>&1

   • OS, Communication status, Process information, Service information, Settings of start and stop, and Container information

   • See OS info, Communication status, Process information, Service information, 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 Appendix A.4(4) Integrated agent host (Linux) in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. ■If you have already set up the SAP system log extract command, collect the following files manually: Environment parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

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

5. Collect the files generated by executing commands.

   • Configuration of silence

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

   • OS info, Communication status, Process information, Service information, Settings of start and stop, Container information, File list

   See OS info, Communication status, Process information, Service information, Settings of start and stop, Container 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	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 Appendix A.4(4) Integrated agent host (Linux)" in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. Except for the following files: Files under the shared directory for the logical host ■If you have already set up the SAP system log extract command, collect the following files manually: Environment parameter configuration file (any name.ini) RFC library allocated when the SAP system log extract command was built CRT library allocated when the SAP system log extract command was built The following files-stored in the path set in WORKDIR of configuration file environment parameter - Log file of SAP system log extract command (any name) - SAP system log extract command trace file (command name.log, command name.dat) - Trace file (dev_rfc*) output by RFC library If the directory where the above files are stored is changed in the environment parameter configuration file or the argument when the SAP system log extract command is executed, the changed directory must also be collected.

(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, see the file and directory list in Appendix A.4 (2) Integrated Manager Host (Linux) in the 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.

(f) Monitored AIX hosts (When Node exporter for AIX is deployed)

Same as 12.4.2(1)(f) Monitored AIX hosts (When Node exporter for AIX is deployed).