in reply to Re: Re: integer encoder/decoder
in thread integer encoder/decoder
yes, i think i understand. but i don't see the reason to limit yourself to a 9 digit sessionid. just use more than one OID slot and give the client people a sessionid with a dots in it.
enterprise.10000.10182.192.168.254.12.3888206 for NAS 192.168.254.12 session 3888206 or take IP and convert to two 16bit numbers and do ...10182.49128.64782.3888206 ( give person 49128.64782.3888206 as sessionid )
i've seen both. another really cool thing i came across recently is to use a timestamp as part of the OID, like ...1.3.1.$time.$id = $value. then you can keep a history of values in your MIB and the user can walk your table from ...1.3.1 and get all of the history or walk the table from ...1.3.1.$last and get all of the updates that have happend since they last walked the table.
Update: if all of your NAS IPs are in the same subnet (/16 or less) you could just forget about the first two octets. give them: 64782.3888206 as the session id if all your NAS are in 192.168.0.0/16.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Re: Re: integer encoder/decoder
by Anonymous Monk on Mar 14, 2003 at 00:47 UTC | |
by merlyn (Sage) on Mar 14, 2003 at 00:58 UTC | |
by zengargoyle (Deacon) on Mar 14, 2003 at 02:10 UTC |