On 22 June 2011 20:15, Scott McLane Gardner <[email protected]> wrote:
> Hello list. I am trying incorporate Avaya's proprietary MIBs in my cacti
> server
> If I specify the MIB file exactly, I get the errors
> sgardne@cacti:~$ snmpwalk -v2c -c A1rB0rn3 -m ~/.snmp/mibs/p80a7002.mib ...
Two things:
Firstly, the value for the -m flag should be the name of the MIB,
rather than the name of the file. Have a look at the first line of the
file, which should look something like
SOME-AVAYA-MIB DEFINITIONS ::= BEGIN
The token to use here is 'SOME-AVAYA-MIB'
Secondly, it's probably worth using the option -m +SOME-AVAYA-MIB
to load this MIB *as well* as the standard list, rather than instead of them.
(Particularly since the Avaya MIBs seem to be missing the usual IMPORTs)
What happens if you try that?
Dave
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
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