All good things come in threes… consider the following code snippet that uses python-agentx: axd.RegisterVar(“a”, 0) axd.RegisterVar(“b”, 1) snmpwalk will show both a and b correctly. Now consider the following code: axd.RegisterVar(“a”, 0) axd.RegisterVar(“b”, 1) axd.RegisterVar(“a”, 2) snmpwalk will show a only. Which is a bug. Why?
Tag: python
Float variables not working with python-agentx
I just found another bug in current versions of the python-agentx. If, in your agent, you do something like this: cpuTemp = 24.5 axd.RegisterVar(“cpuTemp”, cpuTemp) you will hit Internal error in type switching error messages.
“Error: OID not increasing” when declaring SNMP tables with python-agentx
At work, I’m currently working with python-agentx to implement an AgentX-based SNMP agent. Testing around with snmpwalk, I got the following error: $ snmpwalk -Of -v2c -c public localhost DFS-HW-MIB::cpus .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusNumber = INTEGER: 2 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.0 = INTEGER: 0 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuIndex.1 = INTEGER: 0 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuIndex.2 = INTEGER: 1 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuStatus.1 = INTEGER: OK(1) .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuStatus.2 = INTEGER: OK(1) .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuNumCores.1… Continue reading “Error: OID not increasing” when declaring SNMP tables with python-agentx