2009/9/2 Suresh, Rahul (NSN - IN/Bangalore) <[email protected]>: > i've implemented a snmp trap and notification mib .
First of all - don't bother with defining a TRAP-TYPE object. SMIv1 is obsolete. Concentrate on SMIv2 - i.e. NOTIFICATIONS. Secondly, I'd strongly suggest that you define an intermediate OBJECT-IDENTIFIER, with a value of '0', in between 'demonotifs' and 'demo-notif' Thirdly, MIB object names should not contain the character '-' Not only is this disallowed by RFC 2578, it can also confuse mib2c. I would also suggest that you indent your MIB file. It's much easier to read than if you shove everything up against the left-hand margin! > I used mib2c -c mib2c.notify.conf demonotifs on my node in the notification > mib. > Now the problem is i'm only getting a .c file but not a .h file. Hmmm... strange. I've just tried exactly the same MIB, and I get both a .c file and a .h file. Now the contents of the .h file are broken (because of the hyphen in the name of the trap), but it was definitely generated. > Is it possible for me to do the entire trap process using mib2c.scalar.conf. No. Notifications (traps and informs) are a completely different thing to scalars. You can't substitute one for the other. It just won't work Dave ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
