Troubleshooting

This topic provides troubleshooting information about PATROL for Amazon EC2.

Turning on debugging for the KM

Use these steps when you want to set the debug mode for troubleshooting problems in the KM, usually upon request from BMC Support. This information can be useful for troubleshooting problems with your installation or configuration.

  1. From the PATROL Console work area, right-click the Amazon Web Services icon.
  2. Choose KM Commands > Debug.
  3. In the Debug dialog box, select the areas that you want to debug. You can select from the following options:
    • KM Debug: Select one or more of the following options, if you want to debug information for the Knowledge Module (KM).
      • Request Debug: Activates or deactivates debugging for all the requests sent from PATROL for Amazon EC2 to the collectors.
      • Response Debug: Activates debugging for all responses sent from the collectors to PATROL for Amazon EC2.
    • Collector Debug: If you want debugging information for the collector parameters, select one of the following options:
      • OFF: Deactivates debugging for all the parameters.
      • ALL: Activates debugging for all the parameters.
      • FINE: Activates debugging and provides some information about the parameters.
      • FINER: Activates debugging and provides more information about the parameters.
      • FINEST: Activates debugging and provides the most detailed information about the parameters.
      • INFO: Activates debugging and provides information only about information messages generated for the parameters.
      • SEVERE: Activates debugging and provides information only about the critical error events for the parameters.
      • WARNING: Activates debugging and provides information only about potentially harmful events for the parameters.
  4. Click Accept.
    The settings are applied. When the account is discovered or configured, debugging messages appear in a task output window.
  5. Click Exit.

The KM debugging output is redirected to the System Output Window. Collector debugging generates a log file in the Patrol3/pll directory. The log file is named as RemoteCollector-agentPortNo-aws.log.0. To save the debug output appearing in the System Output Window to a location on your computer, you must manually add the /AWS/dir_location pconfig variable and define the directory path where you want to store the debug information. For more information, see PATROL Agent configuration variables.

Note

The more information you gather, the higher the load on your system. When you are finished debugging the problem that you were experiencing, remember to turn off the debug mode by clearing all logging options in the Debug dialog box.

Fetching the device name and instance SID

Use the following SQL query to fetch the device name and instance SID list:

SELECT I.MOTYPEID, A.UNIQUENAME, P.VALUE, A.STORETYPE, d.USERNAME, A.DISPTYPE from ITEM_CFG I, PARAM_CNTL P, ATTRIBUTE_META A , device_cntl d WHERE I.ITEMID = P.ITEMID AND P.ATTRID = A.ATTRID AND I.ITEMID = 35185 AND i.hostid = d.hostid

This information is used to read and parse the incoming AIS messages from the KM or PATROL Agent and take necessary actions on those messages. For example, you need this information to decide if device registration is required or not for the AIS messages. Click here to see the list of device types with device numbers.

Was this page helpful? Yes No Submitting... Thank you

Comments