<br><br><div><span class="gmail_quote">On 2/23/07, <b class="gmail_sendername"><a href="mailto:janvb@caselaboratories.com">janvb@caselaboratories.com</a></b> <<a href="mailto:janvb@caselaboratories.com">janvb@caselaboratories.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
First and doremost alarms. <br>
<br>
Any alarm raised by any module/application. And I would like a config
option in FreeSWITCH where I could format how Alarms where printed out.
Meaning that if I in the stack raise a LOS/LOF I want to see it in SNMP
in a confugurable format. There should also be a filtering mechanisme
where I in a module can raise an alarm with a alarm no etc, and in
config decide what severity and processing this alarm will receive
(Ignore, Log, SNMP, email etc). The issue is that many maintenance
departments have big display boards where alarms with major or critical
severity is shown. Some of this might already be in here?<br>
<br>
Jan</div></blockquote><div><br><br>Its my understanding that you would be given some data, baed on the OID you could tell what its related to. I dont understand how it would be configurable.<br><br>Also, I think clarification is in order here. There are two basic methods for doing SNMP, traps where FreeSWITCH would send to some SNMP monitoring agent and gets, where a client would poll FreeSWITCH for information. It is my understanding that traps are not currently supported, although my futher understanding is that its desired they would be.
<br><br>To get alarms in realtime you would likely want traps to be sent, so that you can see them as they happen. Polling via a SNMP get would work but you dont always want to poll too frequently as it does cause some load however minor.
<br><br>As for logging, it would be on the SNMP module to decide what gets logged. There is an eventing system already within the core of FreeSWITCH that would enable a SNMP module to monitor certain things. This would be similar to how the CDR modules work, except on other events. It would be upto the other modules to push events they think are desirable, such as a red alarm on a pri line in mod_wanpipe. The SNMP module would (presumably by configuration file) see that event, decide its worthy to be sent out, and send it.
<br><br>It should not be configured for each module to say what to do with it, it should instead be on the event omnitor modules such as SNMP to decide if they want it. So, you could have a module that wants critical events, and would send an email, as well as an SNMP module that would fire a trap, and whatever else, and they can all see the events as they happen. This already exists, its a matter of getting the modules to react to the events that is missing.
<br></div><br></div><br clear="all"><br>-- <br>Trixter <a href="http://www.0xdecafbad.com">http://www.0xdecafbad.com</a> Bret McDanel<br>Belfast +44 28 9099 6461 US +1 516 687 5200<br><a href="http://www.trxtel.com">
http://www.trxtel.com</a> the VoIP provider that pays you!