UNIX Health Check sample reports

The following reports are sample reports created by UNIX Health Check.

The reports have been squashed - meaning, all customer identifiable information has been removed or replaced, for obvious reasons of security and privacy. Or, the reports have been generated on test systems of UNIX Health Check, to avoid including customer identifiable information.

The reports do not include all the check scripts available in the full version of UNIX Health Check for AIX and/or UNIX Health Check for Red Hat Enterprise Linux. A selection of the available check scripts has been made when generating these sample reports.

The check scripts in UNIX Health Check change often, to keep up with new available software levels, new vendor recommendations, or newly discovered issues and many other items. Because of this, the sample reports below may be out of date, and when licensing UNIX Health Check software, results may vary per UNIX server.

  • checkall_aix_server1.html [HTML - 214 KB]

    An HTML style report, including 1,085 check scripts, generated on an AIX 6.1 system which serves as an Oracle database server, using PowerHA high availability. The report includes descriptions, and only displays the errors and warnings generated when UNIX Health Check was run.

    Options "-g" (for suppressing successfully completed check scripts) and "-h" (for generating an HTML formatted report) were used. This type of report is very useful for administrators to easily identify all the issues on an UNIX system.

  • checkall_aix_server2.log [TEXT - 902 KB]

    A TEXT (or LOG) formatted report, showing a full inventory of an AIX 7.1 system on Power8 hardware, functioning as a IBM Spectrum Protect (TSM) server with over 300 TB of SAN storage attached.

    Options "-C inventory" (for running all the inventory check scripts) was used, and no format of the report was specified (UNIX Health Check defaults to generating TEXT formatted reports). This results in a full inventory of an UNIX system in TEXT format. This type of report can be useful to run before and after making changes to a system, allowing easy comparison of the reports for any changes to the system. It is also useful to have a lot of system information available, as a run book of a system, in case of issues.

  • checkall_rhel_server3.html [HTML - 4,059 KB]

    An HTML style report that was generated on a Red Hat Enterprise Linux based Oracle database server, on a 40-core Lenovo system with 2 TB of memory. This sample report includes both successful (listed in green) and non-successful (listed in yellow or red) check scripts.

    As you can see in this report, a report generated by UNIX Health Check can quickly become very extensive, especially on systems with lots of running processes and lots of attached SAN storage. Using the -g option will suppress any successful check scripts in the report, and will make the report more manageable.

  • checkall_rhel_server4.log [TEXT - 55 KB]

    A TEXT (or LOG) formatted report, showing only ERRORs (return code 1) and WARNINGs (return code 2), on a VMware based system running Red Hat Enterprise Linux 7.3.

    This makes for a nice and short report, only showing the issues that should be looked into.

  • checkall_rhel_server5.xml [XML - 50 KB]

    An XML formatted report, showing only ERRORs (return code 1) and WARNINGs (return code 2), again on a VMware based system running Red Hat Enterprise Linux 7.3.

    This type of report is generating when using the -x (for XML) option. To view the XML reports that UNIX Health Check produces, an XML reader is required, for example the free XML editor, Foxe, from First Object, or the free MindFusion XML Viewer from MindFusion.

  • checkall_aix_server6.csv [CSV - 92 KB]

    A comma-separated (CSV) report, run on an AIX 7.1 system.

    The comma-separated entries in the report are formatted as follows:
    • Hostname
    • Date and time
    • Name of the check script
    • Result of the check script (0 = successful, 1 = error, 2 = warning)
    • The output of the script
      • The -w (for "width") option determines the length of the output field in the comma-separated output. By default, it is set to 130 characters.