In this post following explained.
How Orion will count Multiple CPU from the Node ?
How Orion will collect load on each CPU from the Node ?
You can verify and count yourself if there is any mismatch between the Node and Orion .
In order to verify the CPU for (Windows / Linux / Unix ) nodes following OID's should return the value for each CPU core .
220.127.116.11.18.104.22.168.3.1.1 (hrProcessorFrwID) (Number of CPU Core )
22.214.171.124.126.96.36.199.3.1.2 (hrProcessorLoad) (Each CPU Load )
(For Cisco )
188.8.131.52.184.108.40.206.220.127.116.11.1.2 (Total Physical Index of CPU )
18.104.22.168.22.214.171.124.126.96.36.199.1.7 (Total 1 min for each CPU)
188.8.131.52.184.108.40.206.220.127.116.11.1.8 (Total 5 min for each CPU )
For Cisco Extreme Switches
18.104.22.168.4.1.1922.214.171.124.28.0 ( extremeCpuAggregateUtilization )
You can create Universal Device Poller in order to verify the Value is been returned correctly by the Node for each core .
Start > All programs > SolarWinds Orion > Network Performance Monitor > Universal Device Poller
place the OID click Browse MIB Tree
Select your Node and Test in this Node can see 4 CPU is been presented
How Orion will collect load on each CPU from the Node .
Now make sure Processor Load is been also presented for each core
Orion will not show that CPU Core in Graph if the load is not been 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.
You should be able to see the result below on node detail page.
If you are running Wireshark the packet should return load for each core.
here is an example of the Node which is not showing the load for each processor and there for Orion will display only graph for single Processor .
we can see the 4 processor however the processor load is returned only for single core by the node .
and here is the results for this Node ( only showing single CPU ) as we have not received the process load for other 3 cores from the Node's MIB's
For more OID's for Vendors please see following KB