I’m trying to create automated integration tests for this hardware+software test subject which runs a SNMP agent as it’s command interface. Our test setup looks like this: We’re using Fitnesse as a test runner and PyFit to be able to write the tests in Python. We then use netsnmp with Python bindings to send SNMP commands. This works pretty well.
However, when I try to run a suite the SNMP agent (the test subject) is restarted (and usually at a different simulated time) which makes the internals of netsnmp get all sorts of interesting errors.
Turns out there is a lot of global state stored inside the netsnmp library like community and context names and problematically EngineTime and EngineBootCnt, which is used to prevent replay attacks in SNMP v3. This causes the agent to reject my snmp commands.
My problems is how do I reinitialise the netsnmp library (from the Python bindings) in a way that the internal global state are reset? The netsnmp.Session object in the Python bindings do take the parameter EngineTime and EngineBoots and setting them to 0 should reset them, but actually it doesn’t seem to do that. I also do not know if there is other global state in there which needs to be reset.
I’m at a point where I think I need to rewrite the tests to use the pure python snmp library pysnmp, but I was hoping to avoid it.
The engineTime and engineBoots values are probably what is messing you up because SNMPv3 requires they not go backwards. If you have an agent that is restarting from scratch and not incrementing it’s boots count (which is illegal, but under tests I could see why you’d be doing that) then you’d need to reset the internal notion of boots and time.
However, setting them to 0 and 0 won’t help because it’ll assume those are defaults. You should, instead, change one of them to ‘1’ which should trigger the override clause to actually use the values. Set the time to 1 and try it and I think it’ll work (and if it doesn’t, set them both to 1 instead and try that).