On 14 July 2010 21:44, Randall C Grimshaw <[email protected]> wrote:
> When I add
>>       PhysAddress
>>             FROM SNMPv2-TC
> To the IMPORTS list in the RFC1213-MIB.txt file – it works….

[shudder]


> Is this safe to adopt in production?

Pragmatically - if it works for you, then fine.
But it's a gross hack, mixing SMIv1 and SMIv2 definitions.
The Net-SNMP tools are relatively easy-going, and won't
mind about this, but it may well break more strict applications.


> I wonder if this is related to my compiling with --enable-old-features

Very unlikely.


If you want to solve this properly, I'd start by removing the RFC1213 MIB
file again, and then running the command with the option -Dparse-mib
This will print out debugging information about the loading and parsing
of MIB files.  That might give some indication about why the IP-MIB
file isn't being read.


Dave

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to