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

Placement of Solarwinds

Hi,

we are currently running solarwinds on a small 500 node network, dedicated server connected close to the core> Its been decided to virtualize the server, on a blade in a remote DC. Every sinu in my body is saying no, bad idea but I can't explain why. What do solarwinds recommend, dedicated hardware or VM (not sql). also placement of server< where's the recommended place to install it. I know it'll work in the remote dc on a blade, but i've just got a feeling that we are painting ourselves in the corner.. If i want to argue against this I need a little more than gut feeling... Any help please.. I have 2 days to formulate a response

andy

Find more posts tagged with

Accepted answers

All comments

mcbridea

NPM is fully supported running on a VM, as are other SolarWinds Orion Products. As long as the SQL server is in the same location as the NPM VM you will be ok. One consideration is that if you decide to expand to server and pplication management you want to local to the server farm. With NPM only, you will see a small increase in SNMP and ICMP traffic betwen the core and the DC devices. If you wish to expand on this with a simple diagram that may help. Also please verify the SW products you have.

Andy

familyofcrowes

I am currently running my Orion in my DC, but it is just my main DC. We monitor servers, routers, riverbeds, logs, via RPC, WMI, SSH, and SNMP perfectly (almost 20,000 elements) fine across a nationwide network. We have two pollers on VM and the main sytem on a hardware platform, but our development system is all VM and will soon be residing in another state.

Using VM is great, absolutly no issues. But like Andy said, keep the SQL DB close to your Orion installation. I have the two systems on the same blade of my 6513.... maybe I'm just paranoid :-)

One great thing about Orion is how flexible it is....

Good Luck!

alexlakustov

We're running Orion NPM in one DC and monitor two other - no problem. But DB is placed in the same DC.

There are hardware server, but it's old and one of future variant is visualization of PE.
Don't worry, I think it isn't bad idea.

FormerMember

biggest issue I see from this is you said REMOTE DC.

if that means you are moving all the polling to a signle link then if that link drops to the remote dc all your monitoring will stop.

having the poller in/near the core of your network alows for pieces to fail and you to continue monitoring.

like you said painting yourself into a corner or single link in this case would probably not be a good idea.

mcbridea

Because DCs are so critical to business continuity, most DCs have multiple connections to the core. If this is the case and there is no single point of failure that would isolate the DC you are OK.