I find the simplest way is to
1. Write the notification MIB with the varbinds defined
2. run mib2c with mib2c.notify.conf, this builds the varbind list
automatically
3. link the code generated into the snmpd application
4. send the trap from snmpd
-Original Message-
From: [EMAIL PROTECTE
hi, all,
I am new in this area I would apprciate any help with the following issue.
Bellow is the skeleton that has been generated by mib2c, what am I
experiencing problem with is the third the snmp_varlist_add_variable
statement handling the attribute "alarmActiveResourceId"
suppose there is
On 19/04/07, Fong Tsui <[EMAIL PROTECTED]> wrote:
> I think there is some inconsistency in support laTable.
>
> 1) 15-minute average or 10-minute average?
15 minute. That's what the underlying O/S measures.
The MIB file is wrong (and has been for years!)
Thanks for reporting it - I've corrected