Re: [OPSAWG] discuss on draft-ietf-opsawg-syslog-msg-mib-06.txt

[Adrian Farrel <[e-mail]>]

>> 1.
>> > Do entries ever get removed from this table?
>> Not as I understand it. The index is monotonic increasing and wraps at 
>> the
>> maximum value (defined as the lesser of syslogMsgTableMaxSize and
>> 4294967295).
>
> No, it wraps at 4294967295 always. What makes you believe it maps at
> min(syslogMsgTableMaxSize, 4294967295)?

I'm very sorry. When I wrote this I went back to check on the email thread, 
and copied from my original question and not from your answer. (That's a 
poor excuse, I know.)

So, this impacts Dave's question; Entries *do* get deleted from the table as 
the valid index window slides upwards.

>> > Does rollover just overwrite starting at the beginning of the table?
>> Yes.
>
> Only in the case where the agent has storage for 4294967295 table
> entries, something I consider unlikely implementations will support.
>
>> Yes. And this is what swings it for me.
>> I am just left wondering whether an Agent is more loaded by a bulk read 
>> of
>> 10,000 entries or maintaining a pointer into the table.
>>
>> Clear up this last point, and I'm done.
>
> If you only need the oldest entry in table insertion time, such an
> index is of course handy. The question is what practical value it has
> to be able to retrieve this oldest entry quickly.

If we agree that the management station should read and store the table, 
parse it, and then do whatever it wants to. I agree: none.

Adrian