Full Utilizations are not shown for Tunnel Graphs of Router NE40E in Newer Version (1.2.20)

[kalanabg]

Current Cacti Version : 1.2.20

Full Utilizations(Bits/second) of tunnel Graphs of the Huawei NE40E Device, which are visible in the old Cacti version (0.8.8 ) are not totally visible(only Low Utilizations are visible ) in the new version (1.2.20). In New version the tunnel Graphs are like cropped only to show the lower bits per second as shown in attached image

Is there any method to adjust and auto scale the Utilizations (bits/second) in Tunnel Graphs. (This issue only present in Tunnel Graphs)
Please mention any probable cause for this issue and any updates to rectify it.

Device Version:
Huawei Versatile Routing Platform Software
VRP (R) software, Version 8.190 (NE40E V800R011C10SPC100)
Copyright (C) 2012-2019 Huawei Technologies Co., Ltd.
HUAWEI NE40E-X16A
Patch Version: V800R011SPH085

[TheWitness]

Your RRDfile max value is clipped. It's likely due to the Interface reporting the wrong ifHighSpeed value from the SNMP agent. You need to run the

Code: Select all

rrdtool tune filename [options]

command to tune the max values for the file to match the "real" ifHighSpeed value.

[kalanabg]

Thanks for the Info. I'll Check

[kalanabg]

This specific issue occurred only for Tunnel Graphs. For all other interfaces of Huawei NE40E (Eth-Trunks, Gigabit Ethernet etc) shows the bits/second graph correctly without setting the Max limit (Graph auto scales) as attached herewith, but with tunnel Graphs the graphs are automatically limited to around 8 gbps (I even extended the graph but utilizations above 6 gbps are not recorded). Only one tunnel graph having utilization below 6 gbps is correctly shown as attached herewith.

Is there any way to correct the issue (to activate autoscale) - How to auto scale the tunnel graphs through the Cacti Web interface?

[TheWitness]

For those tunnel graphs, the SNMP Agent is likely returning an incorrect ifHighSpeed.

Contact the hardware vendor and see if they can show you how to set the right value on the router, then reindex the interfaces and use the data source debug to set the right max value.

Your second option is to use RRDtool tune to make the max values 'U' if the hardware vendor tells you to f-off.