Me again.

Now i tried to load "3COM0045.MIB" specifying "RFC1155-SMI" to be loaded, too - 
it fails, too, both the imported MIBs are empty, but a smidump of the 
RFC1155-SMI tells me this:


> 
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:110: range limit exceeds 
> underlying basetype
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:110: range limits must 
> be `lower-bound .. upper-bound'
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:114: range limit exceeds 
> underlying basetype
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:114: range limits must 
> be `lower-bound .. upper-bound'
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:118: range limit exceeds 
> underlying basetype
> /usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI:118: range limits must 
> be `lower-bound .. upper-bound'
> smidump: module `/usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI' 
> contains errors, expect flawed output
> # python version 1.0                                          DO NOT EDIT
> #
> # Generated by smidump version 0.4.5:
> #
> #   smidump -f python RFC1155-SMI
> 
> FILENAME = "/usr/local/zenoss/common/share/mibs/ietf/RFC1155-SMI"
> 
> MIB = {
>     "moduleName" : "RFC1155-SMI",
> 
>     "RFC1155-SMI" : {
>         "nodetype" : "module",
>         "language" : "SMIv1",
>     },
> 
>     "typedefs" : {
>         "ObjectName" : {
>             "basetype" : "ObjectIdentifier",
>         },
>         "NetworkAddress" : {
>             "basetype" : "OctetString",
>             "parent module" : {
>                 "name" : "RFC1155-SMI",
>                 "type" : "IpAddress",
>             },
>         },
>         "IpAddress" : {
>             "basetype" : "OctetString",
>             "range" : {
>                 "min" : "4",
>                 "max" : "4"
>             },
>         },
>         "Counter" : {
>             "basetype" : "Unsigned32",
>             "range" : {
>                 "min" : "0",
>                 "max" : "4294967295"
>             },
>         },
>         "Gauge" : {
>             "basetype" : "Unsigned32",
>             "range" : {
>                 "min" : "0",
>                 "max" : "4294967295"
>             },
>         },
>         "TimeTicks" : {
>             "basetype" : "Unsigned32",
>             "range" : {
>                 "min" : "0",
>                 "max" : "4294967295"
>             },
>         },
>         "Opaque" : {
>             "basetype" : "OctetString",
>         },
>     }, # typedefs
> 
>     "nodes" : {
>         "internet" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1",
>         }, # node
>         "directory" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1.1",
>         }, # node
>         "mgmt" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1.2",
>         }, # node
>         "experimental" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1.3",
>         }, # node
>         "private" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1.4",
>         }, # node
>         "enterprises" : {
>             "nodetype" : "node",
>             "moduleName" : "RFC1155-SMI",
>             "oid" : "1.3.6.1.4.1",
>         }, # node
>     }, # nodes
> 
> }
> 


This MIB is part of zenoss und therefore should not be corrupt, should it?




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=24102#24102

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to