Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion on VMWare ESX 3.5 VI 2.5

Has anyone else had any issues with upgrading their vmware environment to VI 2.5 and ESX 3.5? I have Orion running on a Windows 2003 Server guest VM and the CPU usage for the NetPerfMon service went from approx 10% to running at 100% constantly. It is the only service that has changed this way. Does anyone have any thoughts in troubleshooting this issue.

--Jordan

Find more posts tagged with

Accepted answers

All comments

thurgoodj187

we had a similar issue, although about a month after upgrading to vi3.5. we reverted to a backup from ESXranger and all is well now. Prior to the restore, the service would start peg the cpu, and the client would fail to connect to the netperfmon service.

bcjordo

So you never discovered the root cause? Has anyone else had this issue?

thurgoodj187

Not really, we had it back up in 10 minutes...

bcjordo

I've done some more digging and found that it actually isn't the NetPerfMonService.exe service that is causing the issues. When I turn off the "SolarWinds Orion Job Scheduler" service the NetPerfMonService.exe returns to acceptable CPU levels. Does anyone have any idea why this service could be causing the CPU spike I'm seeing. I don't have any scheduled jobs added to Orion. Is there anywhere that I could check for troubleshooting purposes. Any help would be greatly appreciated.

--Jordan

FormerMember

We had the same issue that the APM jobscheduler engine was causing various problems. The APM Service Pack 3 fixed the memory leak and CPU issue for us. If you don't have all the Orion and APM service packs installed give it a shot.

FormerMember

We're only on SP2 with APM, and it does not fix the issue. The issue is that there are some SQL queries causing churn on servers with limited resources.

bcjordo

I don't know about the limited resources comment. We typically run around 400mhz of processor utilization. With the malfunctioning service we were running 2.3ghz. It isn't like we're running this on a sub 1ghz processor or anything and that certainly is one large jump.

--Jordan