Re: Hopefully, this explains my confusion a bit more

--===============0669649305==
Content-Type: multipart/alternative; boundary="0-1075610314-1181052099=:26249"
Content-Transfer-Encoding: 8bit

--0-1075610314-1181052099=:26249
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I am not familiar how SNMP is used in the real world so explanations like these help me out a lot. Good job and thanks.


Dave Shield <D.T.Shield@csc.liv.ac.uk> wrote: On 05/06/07, Need Help wrote:
> You stated "you don't have to use the se list method, but you must ensure
> that the same row has the same index each time the container is loaded"
>
> I thought the "container_load" routine reloads the container from "scratch"
> when it is called, so why must and index (which was generated previously and
> stored in a particular row of the container) be reused and placed in the
> same exact row of the container when the container is being rebuilt from
> scratch. Am I not understand something?


Think about how this looks to the admin who's trying to monitor his/her systems.

I'm particularly interested in one specific tuner that's been playing
up recently,
so I walk the AVInterfaceTable and the TunerTable, and find that it is
the device
with index 582
So I set up a script to regularly monitor the settings of the row
with index 582.

A few minutes later, your "container_load" routine kicks in to re-load
the latest
information, and chooses a completely new set of index values. Suddenly
row 582 refers to a completely different bit of kit (or nothing at
all), and the tuner
that I'm actually trying to monitor now has index 319.

That's clearly not very helpful for a sys admin.

It's standard practise in SNMP for index values to remain stable - once you've
assigned a particular index to a given row (and hence to a particular piece of
hardware, or software, or whatever the MIB is monitoring), then that index
should remain the same.
It's usually acceptable to re-assign indexes if the whole system reboots
(or the SNMP agent is killed and restarted). But not in normal operation.

Does that make sense?

Dave



---------------------------------
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search.
--0-1075610314-1181052099=:26249
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I am not familiar how SNMP is used in the real world so explanations like these help me out a lot.&nbsp;&nbsp; Good job and thanks.<br><br><br><b><i>Dave Shield &lt;D.T.Shield@csc.liv.ac.uk&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On 05/06/07, Need Help <snmpnoob@yahoo.com> wrote:<br>&gt; You stated "you don't have to use the se list method, but you must ensure<br>&gt; that the same row has the same index each time the container is loaded"<br>&gt;<br>&gt; I thought the "container_load" routine reloads the container from "scratch"<br>&gt; when it is called, so why must and index (which was generated previously and<br>&gt; stored in a particular row of the container) be reused and placed in the<br>&gt; same exact row of the container when the container is being rebuilt from<br>&gt; scratch. Am I not understand something?<br><br><br>Think about how this looks to the admin who's trying
to monitor his/her systems.<br><br>I'm particularly interested in one specific tuner that's been playing<br>up recently,<br>so I walk the AVInterfaceTable and the TunerTable, and find that it is<br>the device<br>with index 582<br> So I set up a script to regularly monitor the settings of the row<br>with index 582.<br><br>A few minutes later, your "container_load" routine kicks in to re-load<br>the latest<br>information, and chooses a completely new set of index values. Suddenly<br>row 582 refers to a completely different bit of kit (or nothing at<br>all), and the tuner<br>that I'm actually trying to monitor now has index 319.<br><br>That's clearly not very helpful for a sys admin.<br><br>It's standard practise in SNMP for index values to remain stable - once you've<br>assigned a particular index to a given row (and hence to a particular piece of<br>hardware, or software, or whatever the MIB is monitoring), then that index<br>should remain the same.<br> It's usually
acceptable to re-assign indexes if the whole system reboots<br>(or the SNMP agent is killed and restarted). But not in normal operation.<br><br>Does that make sense?<br><br>Dave<br></snmpnoob@yahoo.com></blockquote><br><p>
<hr size=1>Luggage? GPS? Comic books? <br>
Check out fitting <a href="http://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz"> gifts for grads</a> at Yahoo! Search.
--0-1075610314-1181052099=:26249--



--===============0669649305==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
--===============0669649305==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders

--===============0669649305==--