This task describes how to gather BMC PATROL installation information. It writes some general information to a task object and writes the remainder of the information to a log file that you specify.
To Capture Installation Diagnostic Information
- Access the UNIX OS application menu as described in Accessing KM Commands and InfoBoxes.
- Select Debug and Diagnostics > Capture UNIX Diagnostics.
BMC PATROL displays the Select Categories of Diagnostics dialog box. To view an example, see Select Categories of Diagnostics Dialog Box. - Select the Installation Diagnostics check box.
- Place the cursor in the Output File for Diagnostics field and type the path and file name to which you want the diagnostic information written.
- Click Accept.
BMC PATROL writes the information to a task object (Capture UNIX Diagnostics) in the UNIX OS container. Your results should resemble this example:
Capturing setuid and setgid files that exist under BEST1_HOME installation. Capturing license details for PATROL installation. Capturing df -k. Capturing ls -ld on all directores under /local/Patrol35. Capturing ls -lRu /local/Patrol35. Capturing ls -lR /local/Patrol35. Closing OutputDiagFile: /tmp/PDiag.log # PSL Serial No.: ######### <NOT INTERACTIVE> The remaining diagnostics will be written to the diagnostic log file but will not be displayed in the task window. Capturing Agent Configuration Variables. Capturing Default Agent Configuration Variables. Capturing Non-Default/Overridden Agent Configuration Variables. Capturing diagnostics related to the PATROL installation and environment. Capturing list of symbolic links under PATROL installation. Capturing setuid and setgid files that exist under PATROL installation. Capturing information about apidll, dcm, and bgscollect. BEST1_HOME directory = /local/Patrol35/Solaris-2-8-sparc-64/best1
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks