hey all
been trying for a while to load some proprietary MIBS onto zen. i have been
using the
> http://www.zenoss.com/Members/jwrober/how-to-manage-mibs-in-zenoss#Troubleshooting
guide, but it does not provide insight into my current problem. I have loaded
a top-level mib that others depend on to map OIDs (MIB1) which is in smiv1, the
dependent mib (MIB2) is smiv2. the problem is that when running zenmib, MIB2
cannot import modules from MIB1.
Smidump running with both files passes with no errors.
Code:
zen...@zen:$ smidump -k -fpython ./MIB1 ./MIB2
# python version 1.0 DO NOT EDIT
#
# Generated by smidump version 0.4.8:
#
# smidump -f python MIB1
FILENAME = "./MIB1"
MIB = {
"moduleName" : "MIB1",
"MIB1" : {
"nodetype" : "module",
"language" : "SMIv1",
},
"imports" : (
{"module" : "RFC1155-SMI", "name" : "enterprises"},
),
"nodes" : {
"convergent-net" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "1.3.6.xxx",
}, # node
"ics" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "1.3.6.xxx",
}, # node
"cnCommon" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
"cnTrap" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
"ers" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
"csp" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
"cnProducts" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
"cnErs" : {
"nodetype" : "node",
"moduleName" : "MIB1",
"oid" : "xxx",
}, # node
}, # nodes
}
# python version 1.0 DO NOT EDIT
#
# Generated by smidump version 0.4.8:
#
# smidump -f python MIB2
FILENAME = "./MIB2"
MIB = {
"moduleName" : "MIB2",
"MIB2" : {
"nodetype" : "module",
"language" : "SMIv2",
"organization" :
"""Company""",
"contact" :
"""
Company""",
"description" :
"""
CSP top level MIB module.""",
"revisions" : (
{
"date" : "2009-08-11 00:00",
"description" :
"""
Initial revision.""",
},
),
"identity node" : "MIB2Module",
},
"imports" : (
{"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
{"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
{"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
{"module" : "MIB1", "name" : "csp"},
),
"typedefs" : {
"CspSipMethodType" : {
"basetype" : "Enumeration",
"status" : "current",
"default" : {
"nodetype" : "namednumber",
"number" : "1"
},
"register" : {
"nodetype" : "namednumber",
"number" : "2"
},
"invite" : {
"nodetype" : "namednumber",
"number" : "3"
},
"ack" : {
"nodetype" : "namednumber",
"number" : "4"
},
"cancel" : {
"nodetype" : "namednumber",
"number" : "5"
},
"bye" : {
"nodetype" : "namednumber",
"number" : "6"
},
"options" : {
"nodetype" : "namednumber",
"number" : "7"
},
"notify" : {
"nodetype" : "namednumber",
"number" : "8"
},
"info" : {
"nodetype" : "namednumber",
"number" : "9"
},
"subscribe" : {
"nodetype" : "namednumber",
"number" : "10"
},
"refer" : {
"nodetype" : "namednumber",
"number" : "11"
},
"description" :
"""
Allowable SIP methods.""",
},
}, # typedefs
"nodes" : {
"cspSystem" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for CSP system/application management.""",
}, # node
"cspInterface" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for CSP Interfaces.""",
}, # node
"cspDestEntity" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for destination entities.""",
}, # node
"cspRegSubscriber" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for registered subscribers.""",
}, # node
"cspIPBlock" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for IP address table used for
blocking incoming packets.""",
}, # node
"cspSipTrace" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
"description" :
"""
Subtree for SIP trace tables used for
tracing SIP messages based on a configured
filter.""",
}, # node
"cspNotificationPrefix" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
}, # node
"cspNotifications" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
}, # node
"cspNotificationObjects" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
}, # node
"cspMibModule" : {
"nodetype" : "node",
"moduleName" : "MIB2",
"oid" : "xxx",
"status" : "current",
}, # node
}, # nodes
}
so i would expect that zenmib would be able to run these mibs with no issue,
however:
Code:
zen...@zen:/usr/local/zenoss/common/share/mibs/site/cspMibs$ zenmib run -v10
./MIB1 ./MIB2
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/ietf/.index -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/iana/.index -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/irtf/IRTF-NMRG-SMING-TYPES -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/irtf/.index -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/irtf/IRTF-NMRG-SMING-EXTENSIONS -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/irtf/IRTF-NMRG-SMING -- skipping
DEBUG:zen.zenmib:Unable to parse information from
/usr/local/zenoss/zenoss/share/mibs/tubs/.index -- skipping
DEBUG:zen.zenmib:Unable to parse information from ./MIB1 -- skipping
DEBUG:zen.zenmib:Unable to parse information from ./MIB2 -- skipping
DEBUG:zen.zenmib:Running smidump -k -fpython ./MIB1
DEBUG:zen.Relations:obj /zport/dmd/Mibs/mibs/MIB1 already exits on
/zport/dmd/Mibs/mibs
INFO:zen.zenmib:Loaded MIB MIB1 into the DMD
DEBUG:zen.zenmib:Running smidump -k -fpython ./MIB2
DEBUG:zen.zenmib:Found warnings while trying to import MIB:
./MIB2:76: identifier `csp' cannot be imported from module `MIB1'
./MIB2:98: unknown object identifier label `csp'
smidump: module `./MIB2' contains errors, expect flawed output
INFO:zen.zenmib:Loaded MIB MIB1 into the DMD
INFO:zen.zenmib:Loaded 2 MIB file(s)
so, why is it unable to parse the information, and
is there a limitation on an SMIv2 mib importing modules from an SMIv1 mib?
thanks for any insight, even if only into my own stupidity. :)
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=38171#38171
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
