NMS Server: should it go virtual

We have an NMS server monitoring our 100 remote sites.

This server could / should go virtual ?? Should be placed to an ESX server or remain to a standalone server? Server is monitoring IP SLA of the various remote sites and should provide accurate results.

It am afraid of delays due to cpu usages , downtime etc. What do you suggest?

Thank you
LVL 10
Who is Participating?
Daniel McAllisterConnect With a Mentor President, IT4SOHO, LLCCommented:
In my experience, NMS servers should be standalone hardware. You don't need anything "major" there, even a "converted" OLD desktop should be able to do the trick... there is VERY little non-RAM, non-NETWORK I/O on an NMS server, so the "heavy iron" servers would be a massive overkill for that service.

If you don't have a "retired" desktop (that still is usable) around, a $400 sale computer would do as well -- just put a reasonable amount of RAM into it!

Just my thoughts...

AngelGabrielConnect With a Mentor Commented:
Dan has expressed the same concern as myself. Any NMS should be on it's own hardware - If there is any issue with the NMS host, then you are now blind across your network - plus the original problem.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.