Tech Tip: UIM - cdm probe alarms due to high cpu usage caused by mcafee scan

Document created by danst04 Employee on Sep 7, 2016Last modified by Melissa Potvin on Dec 17, 2016
Version 4Show Document
  • View in full screen mode

Document ID:  TEC1956398
Last Modified Date:  09/07/2016
Hide Technical Document Details

Products

  • CA Unified Infrastructure Management

Releases

  • CA Unified Infrastructure Management:Release:8.4
  • CA Unified Infrastructure Management:Release:8.2
  • CA Unified Infrastructure Management:Release:8.31
  • CA Unified Infrastructure Management:Release:8.1
  • CA Unified Infrastructure Management:Release:8.0
  • CA Unified Infrastructure Management:Release:7.6

Components

  • UNIFIED INFRASTRUCTURE MGMT:CAUIM
  • UIM - CDM WITH IOSTAT:UIMCDM

Problem:

A customer has a machine that runs a virus scan at a set time. During this time period the McAfee mcshield.exe process consumes 100% of cpu for the duration of the scan ( 1 1/2 hr - 3 hrs) causing the cdm probe to alarm on total cpu usage. The customer did not want to process the alarm when the McAfee scan was in progress.
 

Environment:

- Windows Server 2008 SR2
- cdm probe
- McAfee scan

 

Workaround:

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/TEC1956398.aspx

Attachments

    Outcomes