qos_processor 20.44 checksum failed in UIM 20.4 CU7
search cancel

qos_processor 20.44 checksum failed in UIM 20.4 CU7

book

Article ID: 268730

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

In production the updated "origin" by qos_processor script enrichment.rb is the base of our security for our clients.

With several fixes, the correct updated origin was propagated/updated to cm_computer_system

But now with a fresh CU7:

- we do not see updated origins in cm_computer_system

- in the qos_processor log we seethis error for all qos metrics:

[Qos Monitor Loader, qos_processor] Loaded monitor (QOS_INTERFACE_UTILIZATION with corrupt checksum: <checksum_number> (loaded) <checksum_number> (computed)

Are there known problems with qos_processor and/or data_engine?

Environment

  • Release: 20.4
  • UIM 20.4 CU7
  • Windows 2017
  • MS SQL Server 2022
  • data_engine 20.46
  • qos_processor 20.44
  • New install on a new test server

Resolution

Regarding these messages in the qos_processor log file as shown below:

  • [Qos Monitor Loader, qos_processor] Loaded monitor (QOS_INTERFACE_UTILIZATION with corrupt checksum: <checksum_number> (loaded) <checksum_number> (computed)
  • Actually when you are performing the enrichment then you will always see these messages in your logs because the origin is changed in enrichment. So this is the expected behavior and it will not impact any functionality. This is just an informational message which is expected when performing the enrichment.