I've got Orion 8.1 installed and on one of my servers, it shows that the CPU utilization is at 100 percent 24/7. When I check the server, it is averaging around 1% utilization and never goes to 100%. Any ideas on how to fix this issue?
Yeah I'd second the question about what device ths is. I've seen Linux/Unix systems have CPU util being reported wrong. But that is the nature of SNMP and Linux. In fact all my Linux systems are constantly at 34% util reported through SNMP. Now if SolarWinds could fix that...
Sorry, this is a Compaq Proliant DL380 running Windows Server 2003. I have the same problem on Mac OS X Server. Doesn't matter what version of net-snmp I use, as soon as I start the service and monitor it with Orion, the CPU spikes to 100% on the Mac server. Haven't found a fix yet and this has been an issue with Solarwinds for quite sometime now. Surprised there is not a fix yet.
FYI, deleting the node from Orion and then re-adding it fixed the issue.
With no changes to my environment on the polled node side or poller I am now seeing this as well. I have 5 windows 2003 servers that are constantly reporting 100% cpu utlization. During this reported period they are not being utilized at all. I run 8.1 w/ only hotfix 1 and 2 installed. I have removed the cpu resource and added it back. I have restarted snmp on the polled node side. Nada still, killing me b/c of capacity planning reports now aren't accurate. I have another ~800 servers not experiencing this issue.
You can also restart the NetPerfMon service to unstick the CPU monitor.
Just FYI everyone. Orion 8.5 didn't fix anything with monitoring Mac OS X. CPU and memory still read 100% and if you monitor volumes the xserve's CPU utilization goes up to 100% and you have to manually kill the snmpd service. I've verified this on net-snmp 5.3.1 (version that is supposed to work) and on 5.4.1.
Can we please get this working Solarwinds? This has never worked correctly! People do want to monitor Macs too...
We are actively working on it. We have finally been able to reproduce in-house, and so we think we know the source of the problem at this point. We are going to deliver it as a hotfix on top of 8.5..
Hotfix doesn't appear to have fixed it.... at least not for my customer.
Support ticket is 10600