Hi,

I do have the same issue with RFC1269. Imports successfully  -(i did add a lot 
of debugging information in zenmib) but nothing is finaly visible in the mib.

It seems that the function doing the creation does not work.

I'm running zenoss stack 2.2.3 on a debian fresh install.
--------------------------------
DEBUG:zen.zenmib:running smidump -l10 -fpython  -p 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1155-SMI" -p 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1213-MIB" -p 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC-1212" -p 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1158-MIB" -p 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC-1215" 
"/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB" 
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:17: warning: implicit node 
definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:264: warning: row 
identifier `bgpPathAttrEntry' should have the same prefix as table identifier 
`bgpRcvdPathAttrTable'
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:363: warning: implicit 
node definition
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:4: warning: identifier 
`NetworkAddress' imported from module `RFC1155-SMI' is never used
/usr/local/zenoss/zenoss/share/mibs/ietf/RFC1269-MIB:6: warning: identifier 
`mib-2' imported from module `RFC1213-MIB' is never used
DEBUG:zen.Relations:obj /zport/dmd/Mibs/mibs/RFC1269-MIB already exits on 
/zport/dmd/Mibs/mibs
DEBUG:zen.zenmib:mib.has_key(nodes)
DEBUG:zen.zenmib: -> Adding bgpPathAttrOrigin in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerOutUpdates in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrDestNetwork in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrInterASMetric in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerRemoteAs in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerEntry in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerLastError in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerState in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerLocalPort in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerInTotalMessages in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerRemotePort in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpLocalAs in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerTable in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrPeer in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerInUpdates in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerAdminStatus in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrASPath in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerOutTotalMessages in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerLocalAddr in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrNextHop in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPathAttrEntry in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpVersion in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpRcvdPathAttrTable in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerRemoteAddr in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgp in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerIdentifier in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpIdentifier in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpPeerNegotiatedVersion in RFC1269-MIB
DEBUG:zen.zenmib:mib.has_key(notifications)
DEBUG:zen.zenmib: -> Adding bgpBackwardTransition in RFC1269-MIB
DEBUG:zen.zenmib: -> Adding bgpEstablished in RFC1269-MIB
INFO:zen.zenmib:Loaded mib RFC1269-MIB




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

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

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



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

Reply via email to