And I agree it's better model for long run but again it depends on situation. Other thought: If intermapper offers as many sensors as PRTG and better improved support I would probably choose InterMapper since their price is based per devices not per sensor. I found InterMapper a bit quicker for all sensor outages.īoth are great monitoring tools and can make a list longer but I put most important characteristics just for me.
#Intermapper current version windows
Both can be windows based installation, while InterMapper offers other platforms as well - again this is just monitoring tool but I am more fan of Unix/Linux based system in production than WindowsĨ. A bit more forums and help from outside like spiceworks community for PRTG while intermapper fewer outside resources.Ħ. One advantage of InterMapper is detection of spanning tree bridge included in sensor and loop detection while PRTG has that a bit of confusing and not included in any sensors, can be done as dirty work around. However, intemapper documentation is bit better detailed and less confusing.Ĥ. InterMapper support is ok but most likely refers to developing tools and including links to their documentation only. PRTG support - even though is located in Germany - the people working there are nice and pretty responsive (next day answer) with steps and including links of documentation. But again PRTG limits price to 1000 sensors in our case.ģ.
PRTG has a way more build in (included sensors) and most of them works out of box - intermapper is ok but has a way less sensors - period. PRTG seems to be a cheaper solution for 1000 sensors while InterMapper is a bit more expensive.Ģ. PRTG vs InterMapper" I am focusing on these two, so:ġ. While I originally opened this thread for "
#Intermapper current version how to
If you're not sure about how to set everything up, you can always give us a call - live deployment help and support is 100% free, even in trial installations. Default port is 6343, but can be set to a different one. Have a look at our datasheet: We are able to monitor availability (and more) of DNS and DHCP network services and we are working on sensor for HTTPS certificates monitoring.Īs for sFlow, the only requirement is to set NetCrunch as a flow collector on your switch. Keep in mind, you can also add additional MIBs through the compiler.Īlso, we have monitoring packs (sets of rules) for most of your devices out of the box.
Exporting them would be a bit problematic for the purposes of this post, so I would suggest narrowing down your range through search in MIB Compiler window. At the moment, we have more than 3500 precompiled MIBs in the database. Hi, sorry for late reply - I was out on weekend.Īll your SNMP devices should work fine with NetCrunch.
0 kommentar(er)
