Problems with oid translation

2004-07-21 Thread evgeni popov
Hi, I've some trouble trying to get some oid translated. Here's a console session (Windows XP, net-snmp V5.1.1): C:\>snmptranslate .1.3.6.1.4.1.9.9.48.1.1.1.2.1 SNMPv2-SMI::enterprises.9.9.48.1.1.1.2.1 Not translated, because the MIB is not loaded. Then: C:\>set MIBS=ALL C:\>snmptranslate .1.3.

Re: Problems with oid translation

2004-07-21 Thread evgeni popov
Some new information: snmptable does work (when oid is a table, of course): C:\>snmptable -v 1 -c public 192.168.1.2 ciscoMemoryPoolTable ciscoMemoryPoolName ciscoMemoryPoolAlternate ciscoMemoryPoolValid ciscoMemoryPo olUsed ciscoMemoryPoolFree ciscoMemoryPoolLargestFree PIX system memory

Re: Problems with oid translation

2004-07-22 Thread evgeni popov
> All I can think is that these two commands are actually from different > installations of the software. > What does > snmptable -V > snmpwalk -V > give? I think you caught it ! snmptable gives 'NET-SNMP version: 5.1.1', whereas snmpwalk/snmpget does not recognize th

using remote port other than 161 does not work ?

2004-07-22 Thread evgeni popov
I'm using the lib through the python wrapper yapsnmp. It uses the netsnmp 'session' object to do the job. Whatever I put in the 'remote_port' member of the session object, it seems netsnmp always uses 161. After a (quick) look to the sources, it seems indeed that 'session.remote_port' is not us

Re: Problems with oid translation

2004-07-22 Thread evgeni popov
It appears in fact that I had a snmpwalk/get exe file (coming from HP OpenView) in my path and those were found before the ones from netsnmp ! The latter ones do work indeed. Sorry for the noise. > > All I can think is that these two commands are actually from different > > installations of t