Too Many Hardware Sentry Internal Events Generated in TrueSight/PATROL Consoles

  • kb1213
  • Jan. 31, 2018
  • 2 min read

How to reduce the number of Hardware Sentry internal events in TrueSight or PATROL consoles.

Troubleshooting Hardware Sentry KM Events Internal Message Events

Related Topics

Introduction

Contrary to the "41", "HardwareProblem" or "ConnectorProblem" events which report on actual reporting issues, Hardware Sentry internal events report on the KM-internal issues. Depending on the value set for the /SENTRY/HARDWARE/pemMessages configuration variable, the following information will be sent as PATROL events:

  • all internal messages (problems and information events)
  • only errors and problems
  • no internal messages at all.

If you notice too many Hardware internal events and wish to reduce their number, you will have to set this variable to "nothing".

Figure 1 - Hardware Internal Events displayed in TrueSight

Figure 1 - Hardware Internal Events displayed in TrueSight

Procedure

For PATROL Classic Environments

To disable the Hardware Sentry internal events:

  1. In the PATROL console, right-click the Hardware icon > KM Commands > KM Settings > Additional Settings > Internal KM Issues Notification
    Figure 2 - Disabling the Hardware Sentry Internal Events (PATROL Environments)

    Figure 2 - Disabling the Hardware Sentry Internal Events (PATROL Environments)

  2. In the Register messages as PATROL events drop-down list, select No internal message
  3. Click OK.

For TrueSight Environments

  1. Edit your monitoring policy
  2. Select the Configuration Variables tab and click Add Configuration Variable
  3. Configure the pemMessages variable:
    Figure 3 - Configuring the pemMessages variable in TrueSight

    Figure 3 - Configuring the pemMessages variable in TrueSight

    • In the Variable field, enter /SENTRY/HARDWARE/pemMessages
    • In the Value field, enter nothing
  4. Click OK. The pemMessages variable is added to your policy:
    Figure 4 - Adding the pemMessages variable to a policy

    Figure 4 - Adding the pemMessages variable to a policy

  5. Click Save.
  6. As these events DO NOT self-close, you may need to either manually close or delete them in the cells. To do so:
    1. Run the following query to display the number of Hardware Sentry internal events:

      mquery -n <cellname> -a PATROL_EV -w "p_class: == 'HardwareSentryInternal'" -s COUNT

      Example:
      C:\>mquery -n supts10ag -a PATROL_EV -w "p_class: == 'HardwareSentryInternal'" -s COUNT
      BMC TrueSight Impact Query 10.5.00.002 (Build 281369066 - 24-Mar-2017) [w6]
      Copyright 1998-2017 BMC Software, Inc. as an unpublished work. All rights reserved.
      70

    2. Run the following command to delete them:
      mquery -n <cellname> -a PATROL_EV -w "p_class: == 'HardwareSentryInternal'" -s DELETE

      Example:
      C:\>mquery -n supts10ag -a PATROL_EV -w "p_class: == 'HardwareSentryInternal'" -s DELETE
      BMC TrueSight Impact Query 10.5.00.002 (Build 281369066 - 24-Mar-2017) [w6]
      Copyright 1998-2017 BMC Software, Inc. as an unpublished work. All rights reserved.
      70

      IMPORTANT: The cell may not respond during this operation, especially when deleting more than 100 000 events.

    3. If needed, restart the BPPM/TrueSight services for the cell to propagate those changes to the different consoles (TSOM/TSPS).
Troubleshooting Hardware Sentry KM Events Internal Message Events