>Currently the SNMP check and SNMP trap receiver only work with OIDs (number >like 1.3.2.3.4.5.6) >We would like to know were you would like to see this translated to >something more meaningfull. > >And how far should the convertion go? > >Example: > OID: 1.3.6.1.6.3.12.1.3.1.7 > > should it be translated to: > snmpTargetParamsRowStatus > OR > >.iso.org.dod.internet.snmpV2.snmpModules.snmpTargetMIB.snmpTargetObjects. snm >pTargetParamsTable.snmpTargetParamsEntry.snmpTargetParamsRowStatus
I don't know that it's necessary to translate the OID being checked. Unless you are going to build in some kind of MIB walking functionality, you'll still need to copy either the numeric or alphabetic representation from something that can walk the MIB's, when you create the check. Therefore it makes no difference which one you copy. The only benefit I can see for allowing the alphabetic rep is to make it easier to identify which check failed upon receiving an alert. However, if you've used descriptive/informative pretty names on your checks, that's not necessary either. >Also if we do a GET (or receive a trap) and get a value back, should we >translate that too? > (using the above OID as example and using the info from the MIB >file) > 1 active > 2 nonInService > 3 notReady > 4 createAndGo > 5 createAndWait > 6 destroy > >Ofcourse to be able to do those "translations" we would need to have the MIB >files (in fact you would need to give the MIB files to SA, and SA will >"compile" them into a database that SA will then use) > >Dirk. Yes, yes, yes! This is something that I've previously "wished" for. There's definately a benefit to doing this. Some of the APC OID's have 10 or more different status' and it's a mission to try and remember what they represent. Regards, Alistair ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
