Just a comment, stay away from virtual servers. It's not really the number of nodes you monitor that is important, it's the number of interfaces. Orion counts every monitored node and every monitored interface as a resource. So in my companies case, we have 2000 nodes, BUT we have over 150,000 interfaces. So what happens in this kind of environment is that the server CPU and the server Ethernet interface get tied up with all the polling. In a virtual environment, which of course a shared environment, the Orion virtual servers start using up all the shared resources. Go with dedicated 64 bit servers with 32g of memory or more and 8 cpu or more for each of the polling servers. The database server is another animal. We're running a Dell R620 with 132g of memory, 24 cpus, SQL standard edition and Windows Server 2008 R2 Enterprise edition. The Enterprise edition is important because you can't use more than 32g of memory with anything less. We have 45g of memory assigned to the SQL instance and Orion is the only instance on the server. Again with our size of data transfer, we're using all the SQL resources.
↧