1) that a mib browser, that something we're working on...could be in v5 or v5.1 3) so you would want not only the name of the OID but also the description? For the received traps only or also for the checks that you defined? If for the check I would guess that we could have a parameter that if used with the REMARK field would give you the full description as remark for that entry.
Dirk. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael D. Shook Sent: Thursday, December 02, 2004 4:13 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SNMP OID -> text 1) IF you (SA) have the complete MIB files for my device, then I would think it would be easiest if I could browse via a GUI interface out the text OID tree to find the OID I want. Then if it's kept as a number internally to SA, it wouldn't matter; you'd only have to deal with the full text during a browsing situation. That way I wouldn't have to use a separate tool like GetIF to figure out what I wanted to do. If this little GUI also had the ability to run an instant check (Get Now), then it's even easier. Especially for those who have never dealt with SNMP before. (kinda build in the MBrowser portion of GetIF) 2) I think for my end users, I'd need an alert like "ImportantDevice is DOWN (check returned: CreateAndGo)", because only I or the setter-upper would really remember what all of the status's mean. 3) Finally (?) I'd like the option to somehow return the description or lookup the description for each check because as you can see from the example below, the status text is necessarily short, but doesn't quite have good enough information for someone who isn't intimately familiar with the device or check. Sample MIB OID entry (from an APC UPS): upsAdvInputLineFailCause OBJECT-TYPE SYNTAX INTEGER { noTransfer(1), highLineVoltage(2), brownout(3), blackout(4), smallMomentarySag(5), deepMomentarySag(6), smallMomentarySpike(7), largeMomentarySpike(8), selfTest(9), rateOfVoltageChnage(10) } ACCESS read-only STATUS mandatory DESCRIPTION "The reason for the occurrence of the last transfer to UPS battery power. The variable is set to: - noTransfer(1) -- if there is no transfer yet. - highLineVoltage(2) -- if the transfer to battery is caused by an over voltage greater than the high transfer vloltage. - brownout(3) -- if the duration of the outage is greater than five seconds and the line voltage is between 40% of the rated output voltage and the low transfer voltage. - blackout(4) -- if the duration of the outage is greater than five seconds and the line voltage is between 40% of the rated output voltage and ground. - smallMomentarySag(5) -- if the duration of the outage is less than five seconds and the line voltage is between 40% of the rated output voltage and the low transfer voltage. - deepMomentarySag(6) -- if the duration of the outage is less than five seconds and the line voltage is between 40% of the rated output voltage and ground. The variable is set to - smallMomentarySpike(7) -- if the line failure is caused by a rate of change of input voltage less than ten volts per cycle. - largeMomentarySpike(8) -- if the line failure is caused by a rate of change of input voltage greater than ten volts per cycle. - selfTest(9) -- if the UPS was commanded to do a self test. - rateOfVoltageChange(10) -- if the failure is due to the rate of change of the line voltage." ::= { upsAdvInput 5 } Michael D. Shook Technical Analyst [EMAIL PROTECTED] 863 668 4477 (work) 863 860 4070 (cell) 863 665 1261 (fax) <file:///C:\Documents%20and%20Settings\MichaelS\Application%20Data\Microsoft \Signatures\www.saddlecrk.com> www.saddlecrk.com
<<attachment: winmail.dat>>
