Hi Manish,

I think we're talking about different graphs, the ones I am referring to are accessed via [ https://fqdn/customers/ | https://FQDN/customers/ ]

Graphs will only appear here if you have formatted the port description in your router according to the rules set out at [ https://docs.observium.org/port_descr_parsing/ | https://docs.observium.org/port_descr_parsing/ ]

Graphs accessed via a device, e.g. https://FQDN/device/device=97/tab=port/port=4368/ show graphs correctly and RRDs exist for the ports.

Using the Port Description Parsing method to group ports generates graphs in a different way to the devices screen, but I believe using the same underlying RRDs.

In the "customers" section, if you click on a graph there is a link which allows you to view the RRDTool command and parameters being used. There are many more command parameters for the graphs that show correctly, than for those that are missing, which implies the code which is generating the RRDTool command is somehow failing to add the RRD file name(s). There is also an error " RRDTool Output: ERROR: can not parse an empty rpn expression" and the area below that is supposed to list the RRDTool files used, is blank.

Regards

Chris Macneill Zelan Ltd

From: "Manish Shringarpure" manish.shringarpure@smartfren.com To: "observium" observium@observium.org Cc: "Chris Macneill" cmacneill@cmit.nz Sent: Wednesday, 26 February, 2020 19:17:01 Subject: Re: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"

I was facing the same issue, the rrd files are not generated for some routers for only ports.

You can check if the rrd files are present under /opt/observium/rrd/<device_name>/port*.rrd

I ran the poller explicitly and the rrd files were generated.

You can try the same on that specific device, with the following command.

sudo ./poller.php -h <device_id> -m ports -dd

watch out for the snmpbulkwalk command that gets printed on the screen.

Regard’s

Manish

From: observium observium-bounces@observium.org on behalf of Chris Macneill via observium observium@observium.org Reply to: observium observium@observium.org Date: Wednesday, 26 February 2020 at 10:54 AM To: observium observium@observium.org Cc: Chris Macneill cmacneill@cmit.nz Subject: [Observium] Port Description Parsing - Cust Graphs "Error Drawing Graph"

Hi,

We're currently using Observium v20.1.10233 and have a problem with "Error Drawing Graph" for all ports with a "Cust" prefix. Ports with "Core", "Peer" or "Transit" prefix correctly show graphs.

The ports we're monitoring are VLANs, the Peer/Transit are simple 802.1q VLANs, the Core/Customer VLANs are QinQ, i.e. two layers of 802.1q headers.

All port types are correctly detected by SNMP and listed against the Router. Given that "Core" displays graphs correctly, this doesn't seem to be related to QinQ, but specifically to the "Cust" prefix.

Examples that correctly show graphs, 1st is 802.1q, 2nd is QinQ:-

Peering: Datacom CHC<->Chorus [10Gbit] {Chorus SVID.100}

Core: Zelan Workshop, 50 Palmerston St, Westport [1Gbit] {Chorus CVID.100}

Example (QinQ) that gives "Error Drawing Graph":-

Cust: GDC Westland Recreation Centre, 83 High St, Greymouth [100Mbit] {Chorus CVID.113}

All our routers are MikroTik, so can't determine if this is a router OS/hardware specific issue.

Regards

Chris Macneill Zelan Ltd.