<div>Hi Alex,</div>
<div> </div>
<div>Thanks for your response. </div>
<div>You have described my problem somewhat correctly.</div>
<div> </div>
<div>My data availability will be like:- </div>
<div> </div>
<div>12:00 counter value = no response</div>
<div>12:05 counter value = 100,300. </div>
<div>12:10 counter value = 10, 600 The difference is 300 bytes in300 seconds = 1 byte per second.<br>12:15 counter value = 100,900. The difference is 300 bytes in 300 seconds =<br>1 byte per second.<br>12:20 counter value = 101,200. The difference is 300 bytes in 300 seconds =<br>
1 byte per second.</div>
<div>12:25 counter value = no response</div>
<div>
<div>12:30 counter value = no response</div>
<div> </div></div>
<div>I am trying to say that,<u> i will have data running on the interface for a short duration and the rest of the time there will be no response.</u></div>
<div><u></u> </div>
<div>So is setting the heartbeat to a higher value the right way to go about it?</div>
<div> </div>
<div>If it helps, I am trying to plot the data on a Data MDT in a multicast network, where the traffic on the MDT flows only at certain times. <br></div>
<div><u>Option 2 </u></div>
<div><u></u> </div>
<div>I have tried the option using 'U'. But here, the problem lies with MRTG behaviour of "assume last". </div>
<div>It shows me the "currrent in" value at the bottom of the graph as</div>
<div> 10 bytes @ 12:30 even if there is no traffic on the interface (since the last valid value was 10bytes @12:20)</div>
<div> </div>
<div>To counter that, i used 'unknaszero'. But that also gave me another problem (sigh!). </div>
<div>With using 'unknaszero' my graph is plotting fine when there is traffic on the interface, but the legend at the bottom "current in" always is "0 bytes". </div>
<div> </div>
<div>So I am still stuck with this problem. :(</div>
<div> </div>
<div>Much appreciate any suggestions. </div>
<div> </div>
<div> </div>
<div class="gmail_quote">On Thu, Oct 1, 2009 at 3:53 PM, Alex van den Bogaerdt <span dir="ltr"><<a href="mailto:alex@vandenbogaerdt.nl">alex@vandenbogaerdt.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="h5">----- Original Message -----<br>From: "Jayashree" <<a href="mailto:jayashree.nayak09@gmail.com">jayashree.nayak09@gmail.com</a>><br>To: <<a href="mailto:rrd-users@lists.oetiker.ch">rrd-users@lists.oetiker.ch</a>><br>
Sent: Thursday, October 01, 2009 12:03 PM<br>Subject: [rrd-users] Can i get the <last_ds> value?<br><br><br>> Hi,<br>><br>> I am interested in getting the counter value stored in <last_ds> in the<br>> rrd<br>
> file. Any rrd function which can help me?<br>><br>><br>> The idea is, i dont have response from the router at a certain point and I<br>> want to log a zero in my graph. So to achieve this, I am trying to get the<br>
> last counter value stored in <last_ds> in my rrd file. If there is a<br>> better<br>> way to handle this problem of updating my rrd file with a '0' when i dont<br>> have response from the device, please let me know.<br>
<br><br></div></div>If you would do that, and if your router would continue working, then at the<br>next update you will have all of the traffic in the next update interval. Is<br>that really what you want?<br><br>Example:<br>
<br>12:00 counter value = 100,000<br>12:05 counter value = 100,300. The difference is 300 bytes in 300 seconds =<br>1 byte per second.<br>12:10 no response. You update with 100,300. The difference is 0 bytes in<br>300 seconds = 0 bytes per second.<br>
12:15 counter value = 100,900. The difference is 600 bytes in 300 seconds =<br>2 bytes per second.<br>12:20 counter value = 101,200. The difference is 300 bytes in 300 seconds =<br>1 byte per second.<br><br>Four intervals of 5 minutes become: 1, 0, 2 and 1 bytes per second.<br>
<br>You can set heartbeat to (some value just over) 600 seconds and do not<br>update. Then the example becomes:<br><br>12:00 counter value = 100,000<br>12:05 counter value = 100,300. The difference is 300 bytes in 300 seconds =<br>
1 byte per second.<br>12:10 no response. You do not update.<br>12:15 counter value = 100,900. The difference is 600 bytes in 600 seconds =<br>1 byte per second.<br>12:20 counter value = 101,200. The difference is 300 bytes in 300 seconds =<br>
1 byte per second.<br><br>Four intervals of 5 minutes become: 1, 1, 1 and 1 bytes per second.<br><br><br>You can also signal that you don't know what happened by inserting an "U" in<br>the data:<br><br>12:00 counter value = 100,000<br>
12:05 counter value = 100,300. The difference is 300 bytes in 300 seconds =<br>1 byte per second.<br>12:10 no response. You update with "U". The difference is unknown so the<br>rate becomes unknown.<br>12:15 counter value = 100,900. The difference is unknown so the rate<br>
becomes unknown.<br>12:20 counter value = 101,200. The difference is 300 bytes in 300 seconds =<br>1 byte per second.<br><br>Four intervals of 5 minutes become: 1, unknown, unknown, 1 bytes per second<br><br><br>If the unavailability of your router lasts longer than the heartbeat<br>
interval time, then above is what automatically would happen, even if you do<br>update with a known counter value.<br><br><br>HTH<br>Alex<br><br>_______________________________________________<br>rrd-users mailing list<br>
<a href="mailto:rrd-users@lists.oetiker.ch">rrd-users@lists.oetiker.ch</a><br><a href="https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users" target="_blank">https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users</a><br></blockquote>
</div><br>