> I have been following the net-snmp tutorial on creating a MIB.
> The outline of the structure I have come up with so far is ...
[snip]
> Does the syntax look ok?
Well the first thing I'd suggest is that you define this using
SMIv2, rather than SMIv1. You can still use this with SNMPv1
requests, but it uses a much more sensible syntax.
Other things you'd be advised to tweak include:
> tcaphostname OBJECT-TYPE
> SYNTAX DisplayString
> ACCESS Not-accessible
That should be "MAX-ACCESS accessible-for-notify"
> aTrap TRAP-TYPE
> ENTERPRISE customerDetails
> VARIABLES { tcaphostname }
> DESCRIPTION "The tcap hostname."
> ::= 1
And that should be defined as '{ customerDetails 0 1 }'
(It doesn't *have* to include that intermediate '0'
subidentifier, but it's generally good practise.)
> When I compile this using the SNMP::MIB::Compiler Perl module from CPAN,
> it compiles without error but doesn't produce a compiled MIB file.
> I have tried various other vendor mib files and they have compiled ok,
> AND dumped a compiled mib file.
That's not a module I've had call to use, but did those other
vendor MIB files include traps or notifications? And did the
Compiler module generate code for them, or just for the (accessible)
OBJECT-TYPE definitions?
Dave
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
