pysnmp | Python SNMP library

I used the answer from the following thread -> snmpwalk with PySNMP

Instead of iterating over getCmd, I used SNMP walk to walk through all of the OIDs.

You are wrong asking for a getCmd ( Get query ) when the OID points to an object-type definition. Choose between getCmd or nextCmd ( walk operation).

In this case, if you don't know the leaf of the table of this object, you need to do a walk operation, like that:

I found the error:

I was using a global variable (timestamp_packaging_start) in multiple queries as the primary key. As no one can tell when a function in a different thread is executed, sometimes the variable got overwritten by the next entry without executing the query in the first place. That caused my program to update the timestamps for ANOTHER and WRONG primary key. Thanks for your efforts guys.

The documentation gives what you want : pip download

pip download does the same resolution and downloading as pip install, but instead of installing the dependencies, it collects the downloaded distributions into the directory provided

source

So you may try these option with pip download :

You should use JQuery/Ajax to manipulate DOM and fetch data. Following code can make it clear how to do the job :

nextCmd() is not the right function to perform a single snmpget call.

I figured out that I have to use getCmd()

Try calling .setLocalAddress on the hlapi.UdpTransportTarget object. That should make your end of the socket bound to this specific address.

Perhaps it makes sense to keep that endpoint permanently allocated so that you won't bump into a busy port grabbed by some other process.

The name mibdump uses for output file name is taken literally from MIB module definition, which is inside the MIB file.

That makes sense, for example, if other MIBs want to import your MIB as a dependency, they can only do that by canonical MIB name because that's the only thing present in the IMPORT statement.

If you place MY-MIB into a file named EXAMPLE-MIB.txt, some additional map would be required to find your non-canonically named MIB by its canonical name. Perhaps some SNMP implementations might have such mapping facilities, but some do not.

That makes me think that it's best to have exactly the same name for the MIB module and MIB file.

However, it's indeed possible (and quite easy, it seems) to teach mibdump to reuse the original file name where the MIB is read from.