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

SP1 and ESX issue?

I'm not sure if anyone else has this issue but ever since I upgraded my Orion pollers and web server to SP1 all of my ESX chassis show all the VMs as "power-ed" off. I verified with the server team that the VMs are indeed online and working so somehting else is up. I have SNMP access to the chassis because I'm getting it's CPU statistics.

BB

Find more posts tagged with

Accepted answers

All comments

Karlo.Zatylny

That should have happened for only one polling cycle. You can check your VirtualMachines table in the database. The GuestState column should now contain either:
poweredOn, poweredOff, or Suspended

This OID was more accurate than the Running, notRunning we were using previously. So the first polling cycle after the upgrade would have shown all the VMs as PoweredOff, then once the database got updated, the values should be reflecting the correct values.

Please let me know if this is not the case, and possibly what your VirtualMachines table is showing.

Thanks

BryanBecker

I see 'running' or 'notrunning' in the DB under that table.

BB

Karlo.Zatylny

It would seem that the SP1 upgrade did not work properly for you. The /Program Files/SolarWinds/Orion/SolarWinds.NPM.BusinessLayer.dll should have a version of 9.1.0.399. You can see the version of the DLL by right-clicking and selecting properties. Then, selecting the versiontab and the version item. This should be updated on all of your servers as this is the DLL that stores the new poweredOn/poweredOff/suspended states.

Are you seeing this across all your ESXs in the table or is it poller specific?

Thanks

BryanBecker

I see 9.1.0.399 on all of my servers. All the ESX servers are on 1 poller but for testing I added one of the ESX servers to a 2nd poller and I have the same issue. I forgot to mention that the poller that the ESX servers are on was upgraded to SP1 on 11/5. The SLX NPM server that runs the web site wasn't upgraded till Friday night. When I looked at the graps I had valid data for te ESX and VMs up until the SLX NPM upgrade on Friday night. So it seems ti be an issue with the SLX NPM sever running the web site. I did check it's DLL but it is also the same version as the rest of them...ie the dll is 9.1.0.399.

BB