I've discovered a problem with the way the smidump dumps MIBs. Right now, everything is a dictionary. Dictionaries within dictionaries. That's ok in most cases, but the problem is that a dictionary returns values in arbitrary order (since it's really a hash table). At least one element requires retrieval in a specific order, namely the INDEX construct. For example:
INDEX { rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr, rtpSessionIndex }
The OID instance identifier part needs to be constructed in the exact order given here. But the python dump will return this in an undefined order (usually mixed up). So it's not possible to intelligently construct an index from the Python MIB.
I've include a patch with is really a quick-and-dirty fix to enable something I was working on. It just makes the INDEX a list. But it will lose some other information, and fail in some circumstances. So it's not the ultimate fix, but might help someone in a similiar situation.
I should probably abandon this tack and return to the pysmi wrapper...
\|// (O O) -- --------------------oOOo~(_)~oOOo---------------------------------------- Keith Dart mailto:kdart@kdart.com http://www.kdart.com/ ---------------------------------------------------------------------------- Ever since my brain transplant I ... ============================================================================