Seemed to have lost ADSL/VDSL stats after upgrading Draytek Vigor2762n to firmware 3.9.6.2

Help
1

Hi I have recently updated the firmware of one of our Draytek Routers and for some reason it is no longer reporting any of the ADSL stats that is was before. Any idea how i can re-instate this

Screenshot 2021-10-15 164229
Screenshot 2021-10-15 1642291218×923 167 KB

2

Did it stop responding to the ADLS MIB? Run the poller in debug mode and check.

3

It looks like there is still info regarding the ADSL/VDSL connection in the snmp - im guessing it must have changed ??? and librenms not compatible with the changes ???

the poller doesnt have the same sql insert statements that another wroking one does on an older firmware

from a router after upgrade to firmware version 3.9.6.2 :-

.1.3.6.1.2.1.10.94.1.1.1.1.1.4 = INTEGER: 2
.1.3.6.1.2.1.10.94.1.1.1.1.2.4 = INTEGER: 2
.1.3.6.1.2.1.10.94.1.1.1.1.3.4 = OID: .0.0
.1.3.6.1.2.1.10.94.1.1.1.1.4.4 = Hex-STRING: 44 45 46 56 41 4C 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.1.1.5.4 = Hex-STRING: 44 45 46 56 41 4C 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.2.1.1.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.2.1.2.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.2.1.3.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.2.1.4.4 = INTEGER: 5
.1.3.6.1.2.1.10.94.1.1.2.1.5.4 = Gauge32: 38
.1.3.6.1.2.1.10.94.1.1.2.1.6.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.2.1.7.4 = INTEGER: 0
.1.3.6.1.2.1.10.94.1.1.2.1.8.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.3.1.1.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.2.4 = Hex-STRING: 44 52 41 59 54 45 4B 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.3.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.4.4 = INTEGER: 10
.1.3.6.1.2.1.10.94.1.1.3.1.5.4 = Gauge32: 24
.1.3.6.1.2.1.10.94.1.1.3.1.6.4 = Hex-STRING: 53 48 4F 57 54 49 4D 45 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.7.4 = INTEGER: 11
.1.3.6.1.2.1.10.94.1.1.3.1.8.4 = Gauge32: 38488056
.1.3.6.1.2.1.10.94.1.1.4.1.1.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.4.1.2.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.4.1.3.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.4.1.4.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.1.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.2.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.3.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.4.4 = Gauge32: 0
.1.3.6.1.2.1.10.251.1.2.2.1.1.4.1 = INTEGER: 1
.1.3.6.1.2.1.10.251.1.2.2.1.1.4.2 = INTEGER: 2
.1.3.6.1.2.1.10.251.1.2.2.1.2.4.1 = Gauge32: 30000000
.1.3.6.1.2.1.10.251.1.2.2.1.2.4.2 = Gauge32: 8354000
.1.3.6.1.2.1.10.251.1.2.2.1.3.4.1 = Gauge32: 0
.1.3.6.1.2.1.10.251.1.2.2.1.3.4.2 = Gauge32: 0
.1.3.6.1.2.1.10.251.1.2.2.1.4.4.1 = INTEGER: 14
.1.3.6.1.2.1.10.251.1.2.2.1.4.4.2 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.5.4.1 = INTEGER: 220
.1.3.6.1.2.1.10.251.1.2.2.1.5.4.2 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.6.4.1 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.6.4.2 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.7.4.1 = INTEGER: 254
.1.3.6.1.2.1.10.251.1.2.2.1.7.4.2 = INTEGER: 254
.1.3.6.1.2.1.10.251.1.2.2.1.8.4.1 = INTEGER: 14
.1.3.6.1.2.1.10.251.1.2.2.1.8.4.2 = INTEGER: 14
.1.3.6.1.2.1.10.251.1.2.2.1.9.4.1 = INTEGER: 2226
.1.3.6.1.2.1.10.251.1.2.2.1.9.4.2 = INTEGER: 2226
.1.3.6.1.2.1.10.251.1.2.2.1.10.4.1 = INTEGER: 1
.1.3.6.1.2.1.10.251.1.2.2.1.10.4.2 = INTEGER: 1
.1.3.6.1.2.1.10.251.1.2.2.1.11.4.1 = INTEGER: 127
.1.3.6.1.2.1.10.251.1.2.2.1.11.4.2 = INTEGER: 127
.1.3.6.1.2.1.10.251.1.2.2.1.12.4.1 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.12.4.2 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.13.4.1 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.13.4.2 = INTEGER: 0
.1.3.6.1.2.1.10.251.1.2.2.1.14.4.1 = INTEGER: 1
.1.3.6.1.2.1.10.251.1.2.2.1.14.4.2 = INTEGER: 1

4

on a router with older firmware it would seem there is only the .1.3.6.1.2.1.10.94 entries and none of the .1.3.6.1.2.1.10.251 entries

from a router still running older firware :-

.1.3.6.1.2.1.10.94.1.1.1.1.1.4 = INTEGER: 2
.1.3.6.1.2.1.10.94.1.1.1.1.2.4 = INTEGER: 2
.1.3.6.1.2.1.10.94.1.1.1.1.3.4 = OID: .0.0
.1.3.6.1.2.1.10.94.1.1.1.1.4.4 = Hex-STRING: 44 45 46 56 41 4C 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.1.1.5.4 = Hex-STRING: 44 45 46 56 41 4C 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.1.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.2.4 = Hex-STRING: 44 52 41 59 54 45 4B 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.3.4 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.9
4.1.1.3.1.4.4 = INTEGER: 6
.1.3.6.1.2.1.10.94.1.1.3.1.5.4 = Gauge32: 31
.1.3.6.1.2.1.10.94.1.1.3.1.6.4 = Hex-STRING: 53 48 4F 57 54 49 4D 45 00 00 00 00 00 00 00 00
00
.1.3.6.1.2.1.10.94.1.1.3.1.7.4 = INTEGER: 7
.1.3.6.1.2.1.10.94.1.1.3.1.8.4 = Gauge32: 28221576
.1.3.6.1.2.1.10.94.1.1.4.1.1.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.4.1.2.4 = Gauge32: 28230000
.1.3.6.1.2.1.10.94.1.1.4.1.3.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.4.1.4.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.1.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.2.4 = Gauge32: 1781000
.1.3.6.1.2.1.10.94.1.1.5.1.3.4 = Gauge32: 0
.1.3.6.1.2.1.10.94.1.1.5.1.4.4 = Gauge32: 0

5

Ok i think i know what the issue is…

this query in the poller is presumably looking for ADSL and VDSL ports to report on

SQL[SELECT COUNT(*) FROM ports WHERE device_id = ? AND ifType in (‘adsl’,‘vdsl’) [85] 0.69ms]

but the ifType of the port after firmware upgrade is ‘ifType’ => ‘vdsl2’,

so im guessing it isnt matching and reporting due to this ???

am i right and what can i do about it ?

6

Hi @Roy_Cruse
You could try to add vdsl2 in the enumeration after ‘vdsl’ and see how it goes. And if you get the expected result, you should start a new pull request.
Be

7

OK i found the query in /includes/pollers/ports.inc.php

I have changed it and all adsl stats have resumed (except sync speed which im still looking into)

I have done a pull request (i think) with the change ??? never done one before so no idea if i did it right

8

the changes required as always are more complicated than originally appear.

as well as simply adding the ‘vdsl2’ check to the query the returned data is now split between 2 sections in the MIB

some of the adsl line stats are still returned in the original 1.3.6.1.2.1.10.94.1 part of the snmp tree but sync speed is not and it and other stats are now available in the 1.3.6.1.2.1.10.251.1 part of the tree

:frowning:

modifications to make use of these bits of data are beyond me - so i need help
as i understand it there will need to be mods to ports.inc.php and ports/ports-adsl.inc.php or maybe im barking up the wrong tree and some draytek config file might need modification ???

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

10

Hi @Roy_Cruse
I started to work on a more generic DSL support, which would take care of both Adsl (using existing code) and VDSL (using new code and new page display). I am currently waiting for a fix from Huawei (cause their VDSL mib support is currently broken on my AR devices) to finish this, and submit a pull request.
Stay tuned.
Bye

1 Like