Re: Got NoSuchName when I was SNMP requesting a MIB with long string value

2008-06-27 Thread Roy M. Silvernail
Dave Shield wrote: > 2008/6/27 Roy M. Silvernail <[EMAIL PROTECTED]>: >> ASN.1 coding uses one byte to indicate field length, limiting any one >> component to 255 bytes. > > Where did you get this information? > Because wherever you found it, it's wrong. My apologies. Note to self: coffee before

Re: Got NoSuchName when I was SNMP requesting a MIB with long string value

2008-06-27 Thread Dave Shield
2008/6/27 Roy M. Silvernail <[EMAIL PROTECTED]>: > ASN.1 coding uses one byte to indicate field length, limiting any one > component to 255 bytes. Where did you get this information? Because wherever you found it, it's wrong. ASN.1 and SMI do *not* use a single-byte for value lengths, and can sup

Re: Got NoSuchName when I was SNMP requesting a MIB with long string value

2008-06-27 Thread Roy M. Silvernail
ling zhou wrote: > Hi, Group, > > > > I am using NET-SNMP version 5.2.1 on my embedded Linux system. My subagent > is attached to snmpd via AgentX. The subagent was working well and we could > get the SNMP table objects and scalar objects correctly until I implemented > a string type scalar MIB

Got NoSuchName when I was SNMP requesting a MIB with long string value

2008-06-26 Thread ling zhou
Hi, Group, I am using NET-SNMP version 5.2.1 on my embedded Linux system. My subagent is attached to snmpd via AgentX. The subagent was working well and we could get the SNMP table objects and scalar objects correctly until I implemented a string type scalar MIB variable (len of string > 256 byt