Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back end: mib2db #1

Open
fenner opened this issue Feb 14, 2014 · 1 comment
Open

Back end: mib2db #1

fenner opened this issue Feb 14, 2014 · 1 comment

Comments

@fenner
Copy link
Owner

fenner commented Feb 14, 2014

mib2db uses libsmi's smidump to translate a MIB module into python, and then parses the python and uses the django database bindings to insert the MIB into the database. It runs periodically, over the extracted RFC and I-D MIB database.

If a module doesn't parse because it has a top-level OID of, say, mib-2.XXX since it is an I-D, assign it an OID based on a hash of the module name, under enterprises.fenner.

@fenner
Copy link
Owner Author

fenner commented Feb 14, 2014

Here is how the old perl code did this:

sub mkoid($) {
        my($file) = shift;

        "1.3.6.1.4.1.6316.42." . unpack("%16C*", $file);
}

There is no need to keep the same algorithm, but the same idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant