maybe I am making a newbie question, but I have come across it and I
couldn't find an adequate answer.

If I had a variable of very big size, let's say 1MB or so, can SNMP split it
up in several messages? I know that the minimum size for the messages
accepted by every SNMP implementation is 484 bytes. How could then the
manager recombine this messages? What I am trying to do is assign a variable
the value of the SEL (System Event Log) to a variable, but as it may be
quite big, I think there would be problems, wouldn't it?

Well, thanks in advance

10-02-2007, 07:39 PM

unix

Re: Splitting up long variables

Agustin <juan-agustin_sanchez-reyREMOVETHIS@agilent.com> wrote:
[color=blue]
> If I had a variable of very big size, let's say 1MB or so, can SNMP split it
> up in several messages? I know that the minimum size for the messages
> accepted by every SNMP implementation is 484 bytes. How could then the
> manager recombine this messages? What I am trying to do is assign a variable
> the value of the SEL (System Event Log) to a variable, but as it may be
> quite big, I think there would be problems, wouldn't it?[/color]

1) The max. theoretic size of an OCTET STRING is 64k.

2) The MIB has to fragment the data appropriately. See the smCodeTable
defined in RFC 3165 for a possible example how to do this.

"Juergen Schoenwaelder" <schoenw@ibr.cs.tu-bs.de> wrote in message
news:1066919025.233054@salvator.ibr.cs.tu-bs.de...[color=blue]
> Agustin <juan-agustin_sanchez-reyREMOVETHIS@agilent.com> wrote:
>[color=green]
> > If I had a variable of very big size, let's say 1MB or so, can SNMP[/color][/color]
split it[color=blue][color=green]
> > up in several messages? I know that the minimum size for the messages
> > accepted by every SNMP implementation is 484 bytes. How could then the
> > manager recombine this messages? What I am trying to do is assign a[/color][/color]
variable[color=blue][color=green]
> > the value of the SEL (System Event Log) to a variable, but as it may be
> > quite big, I think there would be problems, wouldn't it?[/color]
>
> 1) The max. theoretic size of an OCTET STRING is 64k.
>
> 2) The MIB has to fragment the data appropriately. See the smCodeTable
> defined in RFC 3165 for a possible example how to do this.
>
> /js
>
> --
> Juergen Schoenwaelder International University Bremen
> <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen,[/color]
Germany