Tuning DIGI CM 16/32's for Conserver

Hello all,
I have been tasked with creating 2 servers running ‘conserver’ [conserver.com] to monitor and log and provide multi-user access/OOB access to multiple DIGI CM boxes. I suspect that this must be a common configuration, and was wondering if anyone else had any tips/tricks for me or knew of any possible things to look out for.
Thanks in advance!
Kodiak Firesmith

Could you explain what conserver.com is? How does the Digi CM fit in this scenario?

From Conserver.com’s webpage:
What is conserver?

From an email I once sent…

Conserver is an application that allows multiple users to watch a serial console at the same time. It can log the data, allows users to take write-access of a console (one at a time), and has a variety of bells and whistles to accentuate that basic functionality. The idea is that conserver will log all your serial traffic so you can go back and review why something crashed, look at changes (if done on the console), or tie the console logs into a monitoring system (just watch the logfiles it creates). With multi-user capabilities you can work on equipment with others, mentor, train, etc. It also does all that client-server stuff so that, assuming you have a network connection, you can interact with any of the equipment from home or wherever.

So, basically, one installs conserver on a machine, and points it at a digi box, and then you have good logging, easy control and access control etc.

It sounds like this probably works via snmp or something. The MIBs for the Digi CM can be found on the product page of any Digi CM under the “Diagnostics, Utilities, and MIBs” section.