This is a multi-part message in MIME format.
--===============1093112989==
Content-Type: multipart/alternative;
boundary="------------050601000501050906090709"

This is a multi-part message in MIME format.
--------------050601000501050906090709
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I fixed the python module "client.py" to accept the concatentated label
and index, because from the source code you can tell this was allowable.
It was a regular expression error that only allowed one digit instead of
multiple digits.

I'll try and submit a patch.



Jack G Atkinson Jr wrote:
> Got it figured out! Woohoo!
>
> The problem was concatenating the label with the index!
>
> The label and the index need to be passed separately to the Varbind()
> function!
>
> Example:
>
> Varbind(tag = 'adGenEasyBridgeRowStatus', iid='20', val = '5', type =
> 'INTEGER')
>
> or just:
>
> Varbind('adGenEasyBridgeRowStatus', '20', '5', 'INTEGER')
>
> Not :
> Varbind(tag='adGenEasyBridgeRowStatus.20', iid=None,val='5',
> type='INTEGER')
>
> It would work with the single digits for some reason.
>
> I wish that was more clear in the documentation or else I need to work
> on my comprehensive reading skills some more.
>
>
> BTW, iid and val can actually be integers, the python module will
> convert them to strings.
>
> Thanks for the help.
>
> Mike Ayers wrote:
>>> From: Jack G Atkinson Jr [mailto:jgatkinsn@gmail.com]
>>> Sent: Tuesday, January 22, 2008 3:48 PM
>>>

>>
>>
>>> I have done a little more investigating, and it seems to
>>> consistently fail when I go from a one digit index to two
>>> digits. I did this repeatedly by deleting all the rows after
>>> a failure. I'm trying to look at the string creation part
>>> and the hand off to the netsnmp command at the lower level,
>>> and see if something is going wrong. For the life of me, I
>>> can't see why that extra digit is making a difference.
>>>

>>
>> I don't have my python refs handy, but I do recall the automatic number conversions giving me some grief. I note that you are taking the returned get value, which appears, from the code you sent, to return a string, and are passing it back to set, declared as an integer. You may want to add 0 to it before doing it, just to ensure that it can be accepted as an integer.
>>
>>
>> HTH,
>>
>> Mike
>>
>>

>
>
> --



--------------050601000501050906090709
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit







I fixed the python module "client.py" to accept the concatentated label
and index, because from the source code you can tell this was
allowable. It was a regular expression error that only allowed one
digit instead of multiple digits.



I'll try and submit  a patch.







Jack G Atkinson Jr wrote:


Got it figured out! Woohoo!



The problem was concatenating the label with the index!



The label and the index need to be passed separately to the Varbind()
function!



Example:



Varbind(tag = 'adGenEasyBridgeRowStatus', iid='20', val = '5', type =
'INTEGER')



or just:



Varbind('adGenEasyBridgeRowStatus', '20', '5', 'INTEGER')



Not :

Varbind(tag='adGenEasyBridgeRowStatus.20', iid=None,val='5',
type='INTEGER')



It would work with the single digits for some reason.



I wish that was more clear in the documentation or else I need to work
on my comprehensive reading skills some more.





BTW, iid and val can actually be integers, the python module will
convert them to strings.



Thanks for the help.



Mike Ayers wrote:
cite="mid:83E753BE7B6A324ABB336245BAF1DAAC07CDC3A9@mails erver.metatv-ds.metatv.com"
type="cite">

From: Jack G Atkinson Jr [
class="moz-txt-link-freetext" href="mailto:jgatkinsn@gmail.com">mailto:jgatkinsn@gmail.com]
Sent: Tuesday, January 22, 2008 3:48 PM





I have done a little more investigating, and it seems to
consistently fail when I go from a one digit index to two
digits. I did this repeatedly by deleting all the rows after
a failure. I'm trying to look at the string creation part
and the hand off to the netsnmp command at the lower level,
and see if something is going wrong. For the life of me, I
can't see why that extra digit is making a difference.



I don't have my python refs handy, but I do recall the automatic number conversions giving me some grief. I note that you are taking the returned get value, which appears, from the code you sent, to return a string, and are passing it back to set, declared as an integer. You may want to add 0 to it before doing it, just to ensure that it can be accepted as an integer.


HTH,

Mike







--