Collecting Support Bundles

As an alternative to using the Support/Troubleshooting screen to generate a support bundle, you can manually collect logs to include in a support bundle by entering commands.

There are two ways to collect support bundles:

To manually collect support logs from the hosts, execute the following command on the RHEL or SLES hosts you want to collect HPE Ezmeral Runtime Enterprise logs as either:

  • The user who installed HPE Ezmeral Runtime Enterprise
  • root
  • or using sudo

Executing the appropriate script generates aggregated .txz files and places them in /tmp/bluedata/sosreport/customerlog, which is the same directory used by the web interface when collecting Support Bundles, meaning that you can view and access script-generated reports using the Support Bundles tab of the Support/Troubleshooting screen (see Support Bundles Tab). The generated .txz file will have a name similar to bdsupport-L1-06-30-20-08-01_66e23857a14f46e0802ea8bda2b1ddf8.txz.

This file is an aggregation, meaning that it contains one or more embedded .txz files. You must therefore untar the generated .txz file and then untar the embedded .txz files to view the Support Bundle contents. To do this, execute the following command:

tar Jxvf <filename>.txz

This file is an aggregation if run from bluedata-report-sc.py and therefore contains 1-n other supportconfig packages. You must therefore untar twice:

  • Once for the outer package
  • Once for the inner packages.

The package contains a .txz file named something like scc_hpecp_level_3_44631395593.txz. Untarring this package reveals a number of text (.txt) files and the hpecp directory, which contains HPE Ezmeral Runtime Enterprise plugin output.

If you need to obscure your organization's IPv6 and MAC addresses, then you will need to manually edit the .txt files.

RHEL

Execute the following command:

/opt/bluedata/common-install/scripts/bluedata-report.py --gen [1,2,3]

where 1, 2, or 3 is the level of detail to include in the support bundle.

SLES

Execute the following command:

/opt/bluedata/common-install/scripts/bluedata-report-sc.py -- gen [1,2,3]

where 1, 2, or 3 is the level of detail to include in the support bundle.

NOTE
The name of the SLES version of this script is different than the RHEL version.

There are two ways to collect support bundles:

To manually collect support logs from the hosts, execute the following command on the hosts you want to collect HPE Ezmeral Runtime Enterprise logs as either:

  • The user who installed HPE Ezmeral Runtime Enterprise
  • root
  • or using sudo

Executing the appropriate script generates aggregated .txz files and places them in /tmp/bluedata/sosreport/customerlog, which is the same directory used by the web interface when collecting Support Bundles, meaning that you can view and access script-generated reports using the Support Bundles tab of the Support/Troubleshooting screen (see Support Bundles Tab). The generated .txz file will have a name similar to bdsupport-L1-06-30-20-08-01_66e23857a14f46e0802ea8bda2b1ddf8.txz.

This file is an aggregation, meaning that it contains one or more embedded .txz files. You must therefore untar the generated .txz file and then untar the embedded .txz files to view the Support Bundle contents. The command to do this is:

tar Jxvf <filename>.txz
CAUTION
All of the files in the hpecp directory contained within each support bundle are sanitized for MAC and IP addresses. However, not all of the .txt files can be sanitized during support bundle generation. If you want to remove this information for security purposes, then you must find and remove it manually.