Generally, there are several things that dictate how much server capacity you need to manage a network. The first thing is the number of devices in the network. Generally speaking, the more devices you have connected to your network, the more CPU, memory, I/O and storage capacity you'll need to manage it. The next thing that gauges how much NMS server capacity you need is how often you poll and log each device for its operational and performance information. The more often you poll a device and log its attributes, the more system resources you'll need to manage the network. All commercial NMS products allow you to tune how often you poll and log devices in your network. Most of these products have a default-polling interval of 60 seconds. The logging interval varies by product. I recommend throttling back on device polling as much as possible. For example, set the polling rate for your critical backbone devices to 1-minute and your second tier devices to 5-minute polling. Then set everything else at 15-minute or 30-minute polling. This way you reduce the amount of work the NMS has to do to manage your network. In a similar fashion, set the logging rate so that 1 out of every 10 polls gets logged to the historical database. Don't log every poll unless you absolutely have to.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.