sm_getinfo data collection

If no command-line option is specified, the sm_getinfo utility will store the following information in the tar archive:

• For each server, the latest server log file in BASEDIR/smarts/local/logs and the related .audit and .archive files in BASEDIR/smarts/local/logs. If a server name is specified, only the files that correspond to the server will be collected. To avoid generating a too-large tar archive (too large to email), any log file that is larger than 700 MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

• For each server, the latest repository file in BASEDIR/smarts/local/repos. If a server name is specified, only the repository file for the server will be archived. Any repository file that is larger than 700 MB will be excluded and its information will be logged in smgetinfo-versions.log<date>.

• The local files that are not in the BASEDIR/smarts/local/logs and repos directories and changed since last temporary test patch (TTP) and patch.

• The new local files that are not in the BASEDIR/smarts/local/logs and repos directories and were added since the last TTP and patch.

• All local files except the files in logs and repos directories if no TTP or patch is installed.

• All files in the BASEDIR/smarts/setup/info and BASEDIR/smarts/setup/logs directories.

• Core files (RHEL/CentOS) that are generated by the VMware Smart Assurance software, and the corresponding server log files. On Linux, some library (lib) files that are related to the cores are also collected.

• VMware Smart Assurance TTP or patch version information. Additionally, it verifies MD5 checksum for the installed TTP files and the files that are listed in manifest.md5 in the BASEDIR/smarts/setup/info directory.

• The data collected by sm_monitor. If a server name is specified, only the files that correspond to the server will be collected.

• The data generated by the VMware Smart Assurance Health Monitor (SHM).

• System environment information.