cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 9

NPM on server 2008

Jump to solution

  I rebuilt my solarwinds server and moved from a server 2003 VM to a server 2008 VM and have started seeing weird issues. Nodes go into warning but when I open or hit the router nothing is found.. Not just a few but most of the sites have been doing this ever since the new server came online. I have pushed the timeouts up to 2 minutes for alert and warnings but still have the same problem.

Has anybody seen this before or have experience running 9.5.1 on server 2008?

0 Kudos
1 Solution

I gave up and went back to the old server 2003 and it works again..Not sure if it was with 2008 server or that VM but threw in the towel and backed out the change..

Bad part was I started this adventure to fix an issue where I couldn't manage nodes anymore.. Finally the support folks said it was related to the version of CLR and our DB..

 Long story short they removed .NET from our SQL server a few weeks back :).. Moved the info to a new SQL server and it is happy again. 

View solution in original post

0 Kudos
13 Replies
Level 20

Is your database also in the VM?  People have had many issues with trying to run their database from a VM.

0 Kudos

Yeah it is running on a separate VM. I started this move because after upgrading to 9.5.1 I am no longer to manage the mode using the GUI. They have suggested a few things so I decided to start from scratch and just pointed it to the existing DB..The problem didn't go away and now nodes go in and out of warning all the time

0 Kudos

I'm currently running our NPM install in a 2008 Hyper-V VM with no issues. The database is also on the same VM (SQL 2008 Standard).

0 Kudos

We also run NPM server and the SQL 2005 server on two VMware VMs.  No issues here.  We just updated to NPM 9.5.1 but we are still on W2k3.

0 Kudos

This is a weird issue..It has Nodes going into warning but when I check the router and logs nothing shows up..One strange thing is it shows packet loss? But I see no errors on the WAN side and confirmed it using ICMP.

This all started when I moved form 2003 to 2008..I even set the timeouts to 800 ms. Any ideas on why solarwinds thinks it is dropping packets?

0 Kudos

 I run SQL/Windows 2008, although they're not on the same VM.

I had a similar issue for a while; phantom packet loss, weird latency and the like that wouldnt' show up in my diagnostics; when I'd hassle the server admin guys we found a correlation between v-motioning and the problems. This would happen even when my Orion box wasn't the one being v-motioned. It turned out the physical port on the blade chassis was getting pushed to max capacity.

I'd been griping so much about v-motioning the orion server killing my performance (which is very true, by the way - the web interface becomes basically unusable during a v-motion) that they decided not to ever v-motion my server - instead they just left me on one of the most active chassis and I suffered the consequences.

Moving it to a quieter chassis/blade fixed the problem. Don't know if you're in the same spot but it's worth looking at.

0 Kudos

Good information. Sounds like your seeing the same thing I am..

 

I will send this to our VM guy to check

 

Thanks!

0 Kudos

Our VM guys said V Motion doesn't use the same interface. 😞

0 Kudos

Ha. Tell your guys to call my guys. I wish they'd do that.

0 Kudos

I was having a similar situation with NP on Windows 2003 VM.  Nodes would change to down and the server could not ping them.  From my own computer I was able to ping them fine.  I talked with the VM Admin and he had my system in a test environment.  I had him move it to a production environment and everything calmed down.  I don't know how he configured them and he wasn't forthcoming about what the differences were.

0 Kudos

I think I will go back to server 2003 and the old box and see if this issue goes away..

0 Kudos

I bet they will go away especially if the SQL server isn't in a VM.  I know some people seem to be able to make everything work in a VM but at the same time I can't tell you how many people have had problem with it.  The solarwinds guys seem to make it sound like you can run everything but the SQL in a VM without issue.  From what I understand some of the resource contention issues with the VM's to the physical hardware can cause big problems with access to the SQL server when it's virtualized.

0 Kudos

I gave up and went back to the old server 2003 and it works again..Not sure if it was with 2008 server or that VM but threw in the towel and backed out the change..

Bad part was I started this adventure to fix an issue where I couldn't manage nodes anymore.. Finally the support folks said it was related to the version of CLR and our DB..

 Long story short they removed .NET from our SQL server a few weeks back :).. Moved the info to a new SQL server and it is happy again. 

View solution in original post

0 Kudos