Add support for Grandstream Access Points (GWN76xx) #18303
Conversation
|
|
a8577f4 to
af46052
Compare
| snmpget: | ||
| oid: .1.3.6.1.4.1.42397.1.1.2.1.0 | ||
| op: starts | ||
| value: GWN76 |
There was a problem hiding this comment.
Any reason to match only starts GWN76 and not GWN?
Because the OS is named "GrandstreamAp" so we would expect it to cover all current (and hopefully futures) aps of the brand ...
There was a problem hiding this comment.
Switches are named GWN78xx (for managed ones), GWN77xx (for unmanged ones) and routers are GWN70xx. All available APs are currently named GWN76xx (e.g. GWN7660, GWN7672, GWN7670WM etc).
af46052 to
15b576c
Compare
| sysObjectID: | ||
| - .1.3.6.1.4.1.8072.3.2.10 | ||
| snmpget: | ||
| oid: .1.3.6.1.4.1.42397.1.1.2.1.0 |
There was a problem hiding this comment.
Your snmprec file doesn't contain this OID so tests are never going to pass. Please can you update the file with the correct information. That probably also means it's missing all the wireless data.
There was a problem hiding this comment.
Your snmprec file doesn't contain this OID so tests are never going to pass
Yes I am aware of this. Thats why I asked for support in my initial message. I executed the two commands as shown above but the values where not written to the file. Is there a way to debug this?
There was a problem hiding this comment.
If the collect command isn't returning all the snmp data, run snmpbulkwalk -v2c -c COMMUNITY HOSTNAME . and share that here. We can convert that to an snmprec file.
There was a problem hiding this comment.
The snmp implementation on this device seems to be very picky and throttles the output when too many requests occour.
root@librenms-dev:~$ snmpget -c public -v1 ap-office.xxxxx 1.3.6.1.2.1.1.2.0
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.8072.3.2.10
root@librenms-dev:~$ snmpbulkwalk -v2c -c public ap-office.xxxxx iso.3.6.1.4.1.42397
iso.3.6.1.4.1.42397.1.1.2.1.0 = STRING: "GWN7660"
iso.3.6.1.4.1.42397.1.1.2.2.0 = STRING: "AP_Office"
iso.3.6.1.4.1.42397.1.1.2.3.0 = STRING: "c0:74:ad:c4:c7:a4"
iso.3.6.1.4.1.42397.1.1.2.4.0 = Hex-STRING: 31 2E 30 2E 32 35 2E 34 31 00
iso.3.6.1.4.1.42397.1.1.2.5.0 = STRING: "192.168.1.75"
iso.3.6.1.4.1.42397.1.1.2.6.0 = Timeticks: (209325400) 24 days, 5:27:34.00
iso.3.6.1.4.1.42397.1.1.2.7.1.1.12.99.48.55.52.97.100.99.52.99.55.97.52 = STRING: "c074adc4c7a4"
iso.3.6.1.4.1.42397.1.1.2.7.1.1.12.99.48.55.52.97.100.99.52.99.55.101.56 = STRING: "c074adc4c7e8"
iso.3.6.1.4.1.42397.1.1.2.7.1.1.12.99.48.55.52.97.100.99.100.55.99.53.56 = STRING: "c074adcd7c58"
iso.3.6.1.4.1.42397.1.1.2.7.1.1.12.99.48.55.52.97.100.99.100.55.99.57.48 = STRING: "c074adcd7c90"
iso.3.6.1.4.1.42397.1.1.2.7.1.2.12.99.48.55.52.97.100.99.52.99.55.97.52 = STRING: "online"
iso.3.6.1.4.1.42397.1.1.2.7.1.2.12.99.48.55.52.97.100.99.52.99.55.101.56 = STRING: "online"
iso.3.6.1.4.1.42397.1.1.2.7.1.2.12.99.48.55.52.97.100.99.100.55.99.53.56 = STRING: "online"
iso.3.6.1.4.1.42397.1.1.2.7.1.2.12.99.48.55.52.97.100.99.100.55.99.57.48 = STRING: "online"
iso.3.6.1.4.1.42397.1.1.3.1.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.42397.1.1.3.1.1.1.2 = INTEGER: 2
iso.3.6.1.4.1.42397.1.1.3.1.1.2.1 = STRING: "wifi0"
iso.3.6.1.4.1.42397.1.1.3.1.1.2.2 = STRING: "wifi1"
iso.3.6.1.4.1.42397.1.1.3.1.1.3.1 = Counter32: 1
iso.3.6.1.4.1.42397.1.1.3.1.1.3.2 = Counter32: 1
Timeout: No Response from ap-office.nobody.lan
This PR adds basic support for Grandstream AP76xx access points
One downside of the SNMP implementation of GWN7660 is, that its not possible to change the sysName or the location. (sysName is always
grandstream. Is there a solution to pull the sysName from another OID?)I also have problems with the test data. The OS detection failes when running the test because the test data does not contain the additional OIDs.
I am currently a little bit helpless how to solve this issue.
I ran the following commands to generate the data:
In the WebUI the devices is detected correctly
DO NOT DELETE THE UNDERLYING TEXT
Please note
Testers
If you would like to test this pull request then please run:
./scripts/github-apply <pr_id>, i.e./scripts/github-apply 5926After you are done testing, you can remove the changes with
./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.