How CPU Utilization for SystemEDGE is gathered in CA Performance Management

Products

• CA Infrastructure Management
• CA Performance Management - Usage and Administration

Issue/Introduction

This article defines the current MIB OIDs and Metric Expressions used in CA Performance Management to poll and provide CPU Utilization metric data for SystemEDGE Agents.

How is the CPU Utilization metric data for SystemEDGE agents gathered in CA Performance Management?

Environment

All supported CA Performance Management relkease

Resolution

1. The CPU Utilization metric data in CAPM represents the data polled every five minutes from the agents MIB data.
2. The MIB OIDs polled to gather CPU data for a SystemEDGE agent are detailed in the Vendor Certification in use.
3. The most common Vendor Certification (VC) to get applied for polling SystemEDGE CPU metrics is the "SystemEDGE Processor, LPAR(CPUs)" VC.
4. The Utilization related Metrics have the following expressions which defines both which MIB OIDs it uses for it's data, and how that data is calculated. The following table shows the current Metrics along with their OIDs & Expressions.
   
   1. 
      

      CPU Idle Utilization	cpuStatsIdlePercent
      CPU System Utilization	cpuStatsSysPercent
      CPU User Utilization	cpuStatsUserPercent
      CPU Wait Utilization	cpuStatsWaitPercent
      Utilization	cpuStatsUserPercent+cpuStatsSysPercent

      
      
   
   
5. The OIDs related to CPU Utilization metric data are defined in the SystemEDGE MIB as follows:
   
   1. CPU Table Details (all OIDs defined under the same table)
      
      1. -- cpuGroup MIB group ( 1.3.6.1.4.1.546.13 )
      2. -- iso(1). org(3). dod(6). internet(1). private(4). enterprises(1). empire(546). cpuGroup(13)
      
      
   2. cpuStatsIdlePercent OBJECT-TYPE
      
      1. -- 1.3.6.1.4.1.546.13.1.1.8
      2. -- iso(1). org(3). dod(6). internet(1). private(4). enterprises(1). empire(546). cpuGroup(13). cpuStatsTable(1). cpuStatsEntry(1). cpuStatsIdlePercent(8)
      3.          SYNTAX        INTEGER  ( 0..100 )        
      4.          ACCESS        read-only         
      5.          DESCRIPTION: "The percentage of time (over the sample period) that the system's CPU was idle."
      6. ::= { cpuStatsEntry 8  }
      
      
   3. cpuStatsSysPercent OBJECT-TYPE
      
      1. -- 1.3.6.1.4.1.546.13.1.1.10
      2. -- iso(1). org(3). dod(6). internet(1). private(4). enterprises(1). empire(546). cpuGroup(13). cpuStatsTable(1). cpuStatsEntry(1). cpuStatsSysPercent(10)
      3.          SYNTAX        INTEGER  ( 0..100 )        
      4.          ACCESS        read-only         
      5.          DESCRIPTION: "The percentage of time (over the sample period) that the system's CPU was executing the kernel or operating system."
      6. ::= { cpuStatsEntry 10  }
      
      
   4. cpuStatsUserPercent OBJECT-TYPE
      
      1. -- 1.3.6.1.4.1.546.13.1.1.9
      2. -- iso(1). org(3). dod(6). internet(1). private(4). enterprises(1). empire(546). cpuGroup(13). cpuStatsTable(1). cpuStatsEntry(1). cpuStatsUserPercent(9)
      3.          SYNTAX        INTEGER  ( 0..100 )        
      4.          ACCESS        read-only         
      5.          DESCRIPTION: "The percentage of time (over the sample period) that the system's CPU was executing in user mode."
      6. ::= { cpuStatsEntry 9  }
      
      
   5. cpuStatsWaitPercent OBJECT-TYPE
      
      1. -- 1.3.6.1.4.1.546.13.1.1.11
      2. -- iso(1). org(3). dod(6). internet(1). private(4). enterprises(1). empire(546). cpuGroup(13). cpuStatsTable(1). cpuStatsEntry(1). cpuStatsWaitPercent(11)
      3.          SYNTAX        INTEGER  ( 0..100 )        
      4.          ACCESS        read-only         
      5.          DESCRIPTION: "The percentage of time (over the sample period) that the system's CPU was waiting for I/O. This object may not be supported by the underlying operating system."
      6. ::= { cpuStatsEntry 11  }
      
      
   
   

CA Performance Manager polls these OIDs every five minutes by default. It takes the values it receives from the device, in response to its request for those OIDs values. It then uses that data to provide the metric data in reports upon request.