Re: length of snmpEngineID
Pushpa Thimmaiah <[email protected]> Fri, 26 Apr 2024 12:57:37 +0530
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <CAASqVJVF1Oxy58hQZ1Lf_ke59fo4N7x0Db+J5_F+fsgLUai2wQ@mail.gmail.com> |
--===============3969825843669741315== Content-Type: multipart/alternative; boundary="00000000000023d16d0616faca8f" --00000000000023d16d0616faca8f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Magnus Fromreide, Thanks for clarifying. Thanks, Pushpa.T On Thu, Apr 25, 2024 at 10:17=E2=80=AFAM Magnus Fromreide <[email protected]= u.se> wrote: > On Tue, Apr 23, 2024 at 09:51:08AM +0530, Pushpa Thimmaiah wrote: > > Hi All, > > > > Could you please let me know length of snmpEngineID. Is it 12 octets o= r > 32 > > octets. > > > > In RFC 3411 (https://www.ietf.org/rfc/rfc3411.txt) , > > mib object 'snmpEngineID' says 12 octets in description and 32 octet i= n > > You have to read the whole text. > > An snmpEngineID has a syntax of OCTET STRING (SIZE(5..32)) > > If the first bit of the snmpEngineID is 0 and it is 12 octets long then i= t > might have been generated using the algorithm described in bullet 2 which > is > copied from rfc1910. > > If the first bit is 1 then it is generated in accordance with one of the > methods in bullet 3 (or RFC5343) but it is important to notice that bulle= ts > 1-3 are just an recommended algorithm, not a mandatory one so you should > treat snmpEngineID a a variable length string and not attempt to parse it= . > > /MF > --00000000000023d16d0616faca8f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi Magnus Fromreide,</div><div><br></div><div>Thanks = for clarifying. <br></div><div><br></div><div>Thanks,</div><div>Pushpa.T<br= ></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail= _attr">On Thu, Apr 25, 2024 at 10:17=E2=80=AFAM Magnus Fromreide <<a hre= f=3D"mailto:[email protected]">[email protected]</a>> wrote:<br></= div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor= der-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Apr 23, 2024 = at 09:51:08AM +0530, Pushpa Thimmaiah wrote:<br> > Hi All,<br> > <br> > Could you please let me know length of snmpEngineID.=C2=A0 Is it 12 oc= tets or 32<br> > octets.<br> > <br> > In RFC 3411 (<a href=3D"https://www.ietf.org/rfc/rfc3411.txt" rel=3D"n= oreferrer" target=3D"_blank">https://www.ietf.org/rfc/rfc3411.txt</a>) ,<br= > > mib object 'snmpEngineID' says=C2=A0 12 octets in description = and 32 octet in<br> <br> You have to read the whole text.<br> <br> An snmpEngineID has a syntax of OCTET STRING (SIZE(5..32))<br> <br> If the first bit of the snmpEngineID is 0 and it is 12 octets long then it<= br> might have been generated using the algorithm described in bullet 2 which i= s<br> copied from rfc1910.<br> <br> If the first bit is 1 then it is generated in accordance with one of the<br= > methods in bullet 3 (or RFC5343) but it is important to notice that bullets= <br> 1-3 are just an recommended algorithm, not a mandatory one so you should<br= > treat snmpEngineID a a variable length string and not attempt to parse it.<= br> <br> /MF<br> </blockquote></div> --00000000000023d16d0616faca8f-- --===============3969825843669741315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============3969825843669741315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders --===============3969825843669741315==--