Cheshire Cat Computing

Can some one help me .
I was using an old version or router2.cgi (2.11)
and I have installed a new version recently (v2.15) but in the new version I do not see the grey bars when the device is not reachable, which I see in the old version.

Also can some one let me know if I can change the color from grey to RED for the time the devices (or interface) were unreachable.

Thanks in advance.

Ajay

You cannot change the 'unavailable' colour from grey at the moment.

Since v2.11, the greyout only happens if *ALL* datasources are unknown, rather than just one of them. This means that, if you are storing in and out, and in is unknown, then v2.11 would have greyed it out -- v2.15 will not.

It is possible that you are graphing something in the IN value, and just storing a constant 0 in the OUT and using Option: noo to disable this. In this case it would display since one of the values is avaiable?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Just to clarify, In v2.15 I will see Grey lines only when both IN and OUT are unknown, correct.

But when testing one of my circuits , I bought it down for about 30 min , but all I see is a flat line (at the bottom of the graph). I would like to have the grey bars visible . Is there any thing that I need to do to get this working ?

Thanks
Ajay

Do you have the option 'unknaszero' set? If you do, remove it -- this makes all 'unknown's get converted to zero.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

You were right I had the option 'unknaszero' set. I removed it and it is working fine.

Thanks.

Also could you let me know if this option being set is the reason for the values of 'Cur in' and 'Cur out' always show as '0'. Once I remove it , I get current value.

Thanks a lot for your help.

-Ajay

Sometimes, if you are querying the RRD in the next 5-min window from the update, you can get the 'last' value being unknown. The ruoters2 frontend tries to work around this by skipping back one step and getting that value (if you have uselastupdate=y it doesnt happen) but if unknaszero is set, it cannot determine between the last data collection being unknown (and thus zero) or the update-window problem (where we should skip back one sample).

This is a a long explanation to what is actually a fairly difficult problem for me in the graphing routines. I would suggest you never use unknaszero, since routers2 has a different way to handle this and unknaszero will mess up many of the calculations.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11