Here is what I had to do to be able to import my MIBS. The key is to export the SMIPATH variable to include all of your mib direcotries. Do this as the zenoss users before you the the zenmib command.
export SMIPATH=/usr/local/zenoss/common/share/snmp/mibs/:/usr/local/zenoss/common/share/mibs/iana/:/usr/local/zenoss/common/share/mibs/ietf:/usr/local/zenoss/common/share/mibs/irtf:/usr/local/zenoss/common/share/mibs/site:/usr/local/zenoss/common/share/mibs/tubs Travis Llewellyn mdavid wrote: > I have the same problem and when I'm checking my logs, I have these errors: > > > ../share/mibs/site/freedom9.2.80.mib:656: unknown type `IpAddress' > ../share/mibs/site/freedom9.2.80.mib:656: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:657: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:663: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:664: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:670: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:671: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:677: unknown type `IpAddress' > ../share/mibs/site/freedom9.2.80.mib:677: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:678: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:684: unknown type `IpAddress' > ../share/mibs/site/freedom9.2.80.mib:684: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:685: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:691: unknown type `IpAddress' > ../share/mibs/site/freedom9.2.80.mib:691: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:692: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:708: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:709: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:717: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:718: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:724: unknown type `IpAddress' > ../share/mibs/site/freedom9.2.80.mib:724: MAX-ACCESS is SMIv2 style, use > ACCESS in SMIv1 MIBs instead > ../share/mibs/site/freedom9.2.80.mib:725: invalid status `current' in SMIv1 > MIB > ../share/mibs/site/freedom9.2.80.mib:99: unknown object identifier label > `enterprises' > ../share/mibs/site/freedom9.2.80.mib:127: type `[unknown]' of node > `fdSysSerial' does not resolve to a known base type > ../share/mibs/site/freedom9.2.80.mib:376: type `DisplayString' of node > `fdAdminName' does not resolve to a known base type > ../share/mibs/site/freedom9.2.80.mib:446: type `DisplayString' of node > `fdUserName' does not resolve to a known base type > ../share/mibs/site/freedom9.2.80.mib:532: type `DisplayString' of node > `fdVdName' does not resolve to a known base type > ../share/mibs/site/freedom9.2.80.mib:706: type `DisplayString' of node > `fdBridgeFgtFailure' does not resolve to a known base type > ../share/mibs/site/freedom9.2.80.mib:128: unknown type `DisplayString' > smidump: module `../share/mibs/site/freedom9.2.80.mib' contains errors, > expect flawed output -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=23504#23504 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
