Re: [snmpsim-users] sysuptime problem in version 0.2.2
Brought to you by:
elie
Menu
▾
▴
Re: [snmpsim-users] sysuptime problem in version 0.2.2
|
From: Ilya E. <il...@gl...> - 2013-04-26 09:26:43
|
Hi Yateen,
Please verify that there is no syntax error in file near or at line for
OID 1.3.6.1.2.1.1.3.0:
D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.0\135.250.18.151.snmprec
It looks like it does not get parsed properly. The proper syntax is:
1.3.6.1.2.1.1.3.0|67:numeric|rate=100,initial=123999999
You may consider sending me your .snmprec file for analysis.
-ilya
On 04/26/13 12:17, Bhagat, Yateen (Yateen) wrote:
> Hi Ilya
> Looks like the snmpsim has started properly with the numeric module.
> Please see the transcript (with debug messages) below:
> D:\snmpsim-0.2.2rc0\scripts>.\snmpsimd.py --debug=all
> --data-dir=D:\snmpsim-0.2
> .2rc0\devices --variation-modules-dir=D:\snmpsim-0.2.2rc0\variation
> --variation-
> module-options=sql:dbtype:sqlite3,dboptions:NE_ALARM.db
> --agent-udpv4-endpoint=1
> 35.250.32.122 --v2c-arch
> DBG: debug category all enabled
> Scanning "D:\snmpsim-0.2.2rc0\variation" directory for variation
> modules... 8 mo
> re modules found
> Scanning "\Documents and Settings\yateen\SNMP Simulator\Variation"
> directory for
> variation modules... no directory
> Scanning "D:\Documents and Settings\yateen\Application Data\SNMP
> Simulator\Varia
> tion" directory for variation modules... no directory
> Scanning "C:\Program Files\SNMP Simulator\Variation" directory for
> variation mod
> ules... no directory
> Scanning "D:\Python-2.7.3\lib\site-packages\snmpsim\variation" directory
> for var
> iation modules... no directory
> Initializing variation modules:
> notification... OK
> error... OK
> numeric... OK
> subprocess... OK
> delay... OK
> multiplex... OK
> sql... OK
> writecache... OK
> Scanning "D:\snmpsim-0.2.2rc0\devices" directory for *.snmpwalk, *.MVC,
> *.sapwa
> lk, *.snmprec, *.dump data files...
> ==================================================================
> Index
> d:\docume~1\yateen\locals~1\temp\snmpsim\_snmpsim-0.2.2rc0_devices_AdminAd
> min123_1.3.6.1.6.1.1.0_135.250.18.151.dbm out of date
> Building index
> d:\docume~1\yateen\locals~1\temp\snmpsim\_snmpsim-0.2.2rc0_device
> s_AdminAdmin123_1.3.6.1.6.1.1.0_135.250.18.151.dbm for data file
> D:\snmpsim-0.2.
> 2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.0\135.250.18.151.snmprec (open
> flags "n
> ")......53307 entries indexed
> Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.0\135.250.18.1
> 51.snmprec, dbhash-indexed, closed
> SNMPv1/2c community name: AdminAdmin123/1.3.6.1.6.1.1.0/135.250.18.151
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> Scanning "\Documents and Settings\yateen\SNMP Simulator\Data" directory
> for *.s
> nmpwalk, *.MVC, *.sapwalk, *.snmprec, *.dump data files... no directory
> Scanning "D:\Documents and Settings\yateen\Application Data\SNMP
> Simulator\Data"
> directory for *.snmpwalk, *.MVC, *.sapwalk, *.snmprec, *.dump data
> files... no
> directory
> Scanning "C:\Program Files\SNMP Simulator\Data" directory for
> *.snmpwalk, *.MVC
> , *.sapwalk, *.snmprec, *.dump data files... no directory
> Scanning "D:\Python-2.7.3\lib\site-packages\snmpsim\data" directory for
> *.snmpw
> alk, *.MVC, *.sapwalk, *.snmprec, *.dump data files... no directory
> Listening at:
> UDP/IPv4 endpoint 135.250.32.122:161, transport ID 1.3.6.1.6.1.1.0
> DBG: handle_read: transportAddress ('135.250.18.151', 32905)
> incomingMessage '00
> \x02\x01\x01\x04\rAdminAdmin123\xa0\x1c\x02\x04\x17\xe3\xdf\n\x02\x01\x00\x02\x0
> 1\x000\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x05\x00'
> data error at Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.
> 0\135.250.18.151.snmprec, dbhash-indexed, opened for 1.3.6.1.2.1.1.3.0:
> value ev
> aluation for 1.3.6.1.2.1.1.3.0 = ':numeric|rate=100,initial=123999999'
> failed: C
> an't coerce :numeric|rate=100,initial=123999999 into integer: invalid
> literal fo
> r int() with base 10: ':numeric|rate=100,initial=123999999'
> DBG: handle_write: transportAddress ('135.250.18.151', 32905)
> outgoingMessage '0
> 0\x02\x01\x01\x04\rAdminAdmin123\xa2\x1c\x02\x04\x17\xe3\xdf\n\x02\x01\x00\x02\x
> 01\x000\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x81\x00'
> DBG: handle_read: transportAddress ('135.250.18.151', 47537)
> incomingMessage '00
> \x02\x01\x01\x04\rAdminAdmin123\xa0\x1c\x02\x04UI\xb1j\x02\x01\x00\x02\x01\x000\
> x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x05\x00'
> data error at Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.
> 0\135.250.18.151.snmprec, dbhash-indexed, opened for 1.3.6.1.2.1.1.3.0:
> value ev
> aluation for 1.3.6.1.2.1.1.3.0 = ':numeric|rate=100,initial=123999999'
> failed: C
> an't coerce :numeric|rate=100,initial=123999999 into integer: invalid
> literal fo
> r int() with base 10: ':numeric|rate=100,initial=123999999'
> DBG: handle_write: transportAddress ('135.250.18.151', 47537)
> outgoingMessage '0
> 0\x02\x01\x01\x04\rAdminAdmin123\xa2\x1c\x02\x04UI\xb1j\x02\x01\x00\x02\x01\x000
> \x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x81\x00'
> DBG: handle_read: transportAddress ('135.250.18.151', 54577)
> incomingMessage '00
> \x02\x01\x01\x04\rAdminAdmin123\xa0\x1c\x02\x04IC\xe3z\x02\x01\x00\x02\x01\x000\
> x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x05\x00'
> data error at Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.
> 0\135.250.18.151.snmprec, dbhash-indexed, opened for 1.3.6.1.2.1.1.3.0:
> value ev
> aluation for 1.3.6.1.2.1.1.3.0 = ':numeric|rate=100,initial=123999999'
> failed: C
> an't coerce :numeric|rate=100,initial=123999999 into integer: invalid
> literal fo
> r int() with base 10: ':numeric|rate=100,initial=123999999'
> DBG: handle_write: transportAddress ('135.250.18.151', 54577)
> outgoingMessage '0
> 0\x02\x01\x01\x04\rAdminAdmin123\xa2\x1c\x02\x04IC\xe3z\x02\x01\x00\x02\x01\x000
> \x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x81\x00'
> DBG: handle_read: transportAddress ('135.250.18.151', 58068)
> incomingMessage '00
> \x02\x01\x01\x04\rAdminAdmin123\xa0\x1c\x02\x04J\xe0\x88\xdb\x02\x01\x00\x02\x01
> \x000\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x05\x00'
> data error at Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.
> 0\135.250.18.151.snmprec, dbhash-indexed, opened for 1.3.6.1.2.1.1.3.0:
> value ev
> aluation for 1.3.6.1.2.1.1.3.0 = ':numeric|rate=100,initial=123999999'
> failed: C
> an't coerce :numeric|rate=100,initial=123999999 into integer: invalid
> literal fo
> r int() with base 10: ':numeric|rate=100,initial=123999999'
> DBG: handle_write: transportAddress ('135.250.18.151', 58068)
> outgoingMessage '0
> 0\x02\x01\x01\x04\rAdminAdmin123\xa2\x1c\x02\x04J\xe0\x88\xdb\x02\x01\x00\x02\x0
> 1\x000\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x81\x00'
> DBG: handle_read: transportAddress ('135.250.18.151', 49748)
> incomingMessage '00
> \x02\x01\x01\x04\rAdminAdmin123\xa0\x1c\x02\x04#G\x91\xf9\x02\x01\x00\x02\x01\x0
> 00\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x05\x00'
> data error at Data file
> D:\snmpsim-0.2.2rc0\devices\AdminAdmin123\1.3.6.1.6.1.1.
> 0\135.250.18.151.snmprec, dbhash-indexed, opened for 1.3.6.1.2.1.1.3.0:
> value ev
> aluation for 1.3.6.1.2.1.1.3.0 = ':numeric|rate=100,initial=123999999'
> failed: C
> an't coerce :numeric|rate=100,initial=123999999 into integer: invalid
> literal fo
> r int() with base 10: ':numeric|rate=100,initial=123999999'
> DBG: handle_write: transportAddress ('135.250.18.151', 49748)
> outgoingMessage '0
> 0\x02\x01\x01\x04\rAdminAdmin123\xa2\x1c\x02\x04#G\x91\xf9\x02\x01\x00\x02\x01\x
> 000\x0e0\x0c\x06\x08+\x06\x01\x02\x01\x01\x03\x00\x81\x00'
> Thanks
> Yateen
> -----Original Message-----
> From: Ilya Etingof [mailto:il...@gl...]
> Sent: Friday, April 26, 2013 12:20 PM
> To: Bhagat, Yateen (Yateen)
> Cc: snm...@li...; KARNAM, Mahendra (Mahendra)
> Subject: Re: sysuptime problem in version 0.2.2
> Hi Yateen,
> Is there any error message on simulator console? Does simulator find and
> report the 'numeric' variation module on startup?
> -ilya
> On Apr 26, 2013, at 10:28 AM, Bhagat, Yateen (Yateen) wrote:
>> Hi Ilya
>>
>> I tweaked my .snmprec file with following entry for the sysUpTime and
>> restarted trhe snmpsim
>>
>> 1.3.6.1.2.1.1.3.0|67:numeric|rate=100,initial=123999999
>>
>> A simple snmpwalk on this OID resulted in error, as given below
>>
>> # snmpget -v2c -c AdminAdmin123 135.250.32.122 1.3.6.1.2.1.1.3.0
>> DISMAN-EVENT-MIB::sysUpTimeInstance = No Such Instance
>> currently exists at this OID
>>
>> I am using snmpsim version 0.2.2rc0
>>
>> Thanks
>> Yateen
>>
>>
>> -----Original Message-----
>> From: Ilya Etingof [mailto:il...@gl...]
>> Sent: Thursday, April 25, 2013 5:54 PM
>> To: Bhagat, Yateen (Yateen)
>> Cc:snm...@li...
> <mailto:snm...@li...>; KARNAM, Mahendra (Mahendra)
>> Subject: Re: sysuptime problem in version 0.2.2
>>
>> Hi Yateen,
>>
>> I suspect the .snmprec file used for building responses does not have 'numeric' variation module configured for 1.3.6.1.2.1.1.3.0.
>>
>> Could you check that? The example configuration would be:
>>
>> 1.3.6.1.2.1.1.3.0|67:numeric|rate=100,initial=123999999
>>
>> You could check how the above config is working online:
>>
>> $ snmpget -v2c -c public demo.snmplabs.com 1.3.6.1.2.1.1.3.0
>>
>> -ilya
>>
>> On 04/25/13 16:17, Bhagat, Yateen (Yateen) wrote:
>> > Hi Ilya
>> > While we were using the version 0.2.2rc0, we noticed that
>> > Sysuptime(1.3.6.1.2.1.1.3.0) field is not changing with time. It
>> > was changing in earlier version of snmpsim
>> > [root@ems151 ~]# snmpget -v2c -c AdminAdmin123 10.254.13.91
>> > 1.3.6.1.2.1.1.3.0
>> > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (118198) 0:19:41.98
>> > [root@ems151 ~]# snmpget -v2c -c AdminAdmin123 10.254.13.91
>> > 1.3.6.1.2.1.1.3.0
>> > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (118198) 0:19:41.98
>> > [root@ems151 ~]# snmpget -v2c -c AdminAdmin123 10.254.13.91
>> > 1.3.6.1.2.1.1.3.0
>> > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (118198) 0:19:41.98
>> > -Regards, Yateen
|
