Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > How Orion counts multiple CPUs from a node, and how it collects CPU load data

How Orion counts multiple CPUs from a node, and how it collects CPU load data

Table of contents
Created by Malik Haider, last modified by Steven Bansil_ret on Apr 19, 2017

Views: 100 Votes: 4 Revisions: 10

 

Updated April 19, 2017

Overview

This article provides information on how Orion counts multiple CPUs on a node and how Orion collects load data from each CPU on a node.

Environment

All Orion Platform modules

Steps

 

​Verify and count to see if there is any mismatch between the node and  Orion.

In order to verify the CPU for (Windows / Linux / Unix ) nodes, the  following OID's should return the value for each CPU core:

  • 1.3.6.1.2.1.25.3.3.1.1 (hrProcessorFrwID) (Number of CPU Core )
  • 1.3.6.1.2.1.25.3.3.1.2 (hrProcessorLoad)  (Each CPU Load )

For Cisco:

  • 1.3.6.1.4.1.9.9.109.1.1.1.1.2 (Total Physical Index of CPU )
  • 1.3.6.1.4.1.9.9.109.1.1.1.1.7 (Total 1 min for each CPU)
  • 1.3.6.1.4.1.9.9.109.1.1.1.1.8 (Total 5 min for each CPU )

For Cisco Extreme Switches:

  • 1.3.6.1.4.1.1916.1.1.1.28.0  ( extremeCpuAggregateUtilization )

 

See also:

 

To create a Universal Device Poller to verify the Value is been returned correctly by the node for each core .

  1. Launch the Universal Device Poller (UDP):
    Start > All programs > SolarWinds Orion > Network Performance Monitor > Universal Device Poller
  2. Enter the OID, and click Browse MIB Tree.

    UNDP1.JPG
     
  3. Select a node, and click the Test button. 
    In the following example, you can see four nodes:

    core .JPG

 

How Orion collects load data from each CPU from the Node

Ensure Processor Load is present for each core.

Orion will not show a CPU Core in the graph if the load is not presented by the node for that Core CPU.

Now test the same for hrProcessorLoad, and make sure the value is been returned by the node. 

Load cpu.JPG

You should be able to see the result below on node detail page.

gg.JPG

If you are running Wireshark the packet should return load for each core.

 

cpuload.JPG

 

Here is an example of the node which is not showing the load for each processor. Therefore Orion will only display a graph for a single Processor .

The 4 processors are shown but the processor load is only returned only for a single core.

cpu.jpg

and here is the results for this node (only showing the single CPU), as we have not received the process load for the other 3 cores from the Node's MIBs.

graph.jpg

 

 

 

Last modified
00:24, 19 Apr 2017

Tags

Classifications

Public