TP-Link Help

[gokiwi]

Hi All,

I have several TP-Link devices (Archer VR900 ADSL Router, WA901 Wireless Access Point) , the all support snmp v2 (but use a "public" mib).
I am testing NETXMS alongside Zabbix - Unfortunately Zabbix picks up the interfaces on these where as NetXMS does not  - What am I doing wrong ?

This is the response

[13.08.2020 19:50:28] **** Poll request sent to server ****
[13.08.2020 19:50:28] Poll request accepted
[13.08.2020 19:50:28] Starting configuration poll for node Folly-VR900-Router
[13.08.2020 19:50:28] Checking node's capabilities...
[13.08.2020 19:50:28]    Checking NetXMS agent...
[13.08.2020 19:50:30]    Cannot connect to NetXMS agent (Connect failed)
[13.08.2020 19:50:30]    Checking SNMP...
[13.08.2020 19:51:29]    Checking EtherNet/IP...
[13.08.2020 19:51:31]    Cannot get device identity via EtherNet/IP (CONNECT FAILED)
[13.08.2020 19:51:31] Capability check finished
[13.08.2020 19:51:31] Checking interface configuration...
[13.08.2020 19:51:31] Unable to get interface list from node
[13.08.2020 19:51:31] Interface configuration check finished
[13.08.2020 19:51:31] Checking node name
[13.08.2020 19:51:31] Node name is OK
[13.08.2020 19:51:31] Updating general system hardware information
[13.08.2020 19:51:31] Finished configuration poll for node Folly-VR900-Router
[13.08.2020 19:51:31] Node configuration was not changed after poll
[13.08.2020 19:51:31] **** Poll completed successfully ****

[Filipp Sudanov]

The issue is not with interfaces - netxms does not receive anything via SNMP from this device.
Please check if your community string is set up in Configuration->Network Credentials.

For testing you can also use snmp command line tools on the machine where you have NetXMS installed, e.g.:
nxsnmpwalk -v 2c -c public <device_ip> .1.3.6

[gokiwi]

snmpwalk returns data  - what I did was delete the original and add manually this then worked. Unfortunately TP-Link obviously do not implement snmp properly or fully (for example you cannot see the 4 gigabit interfaces).

(this is just an extract)

C:\NetXMS\bin>nxsnmpwalk -v 2c -c Monday1964! 192.168.1.1 .1
.1.3.6.1.2.1.1.1.0 [STRING]: 0.5.0 0.9.1 v0069.0 Build 200624 Beta.68497n
.1.3.6.1.2.1.1.2.0 [OBJECT IDENTIFIER]: .1.3.6.1.4.1.16972
.1.3.6.1.2.1.1.3.0 [TIMETICKS]: 60955700
.1.3.6.1.2.1.1.4.0 [STRING]: Scott Dawson
.1.3.6.1.2.1.1.5.0 [STRING]: Folly-VR900-Router
.1.3.6.1.2.1.1.6.0 [STRING]: Downstairs Office
.1.3.6.1.2.1.1.7.0 [INTEGER]: 72
.1.3.6.1.2.1.1.8.0 [TIMETICKS]: 0
.1.3.6.1.2.1.1.9.1.2.1 [OBJECT IDENTIFIER]: .1.3.6.1.6.3.1
.1.3.6.1.2.1.1.9.1.3.1 [STRING]: The MIB module for SNMPv2 entities
.1.3.6.1.2.1.1.9.1.4.1 [TIMETICKS]: 0
.1.3.6.1.2.1.2.1.0 [INTEGER]: 20
.1.3.6.1.2.1.2.2.1.1.2 [INTEGER]: 2
.1.3.6.1.2.1.2.2.1.1.4 [INTEGER]: 4
.1.3.6.1.2.1.2.2.1.1.8 [INTEGER]: 8
.1.3.6.1.2.1.2.2.1.1.16 [INTEGER]: 16
.1.3.6.1.2.1.2.2.1.1.17 [INTEGER]: 17
.1.3.6.1.2.1.2.2.1.1.19 [INTEGER]: 19
.1.3.6.1.2.1.2.2.1.1.20 [INTEGER]: 20
.1.3.6.1.2.1.2.2.1.2.2 [STRING]: ifb0
.1.3.6.1.2.1.2.2.1.2.4 [STRING]: gre0
.1.3.6.1.2.1.2.2.1.2.8 [STRING]: bcmsw
.1.3.6.1.2.1.2.2.1.2.16 [STRING]: br0
.1.3.6.1.2.1.2.2.1.2.17 [STRING]: tun0
.1.3.6.1.2.1.2.2.1.2.19 [STRING]: ptm0.101
.1.3.6.1.2.1.2.2.1.2.20 [STRING]: ppp1
.1.3.6.1.2.1.2.2.1.3.2 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.4 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.8 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.16 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.17 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.19 [INTEGER]: 6
.1.3.6.1.2.1.2.2.1.3.20 [INTEGER]: 23
.1.3.6.1.2.1.2.2.1.4.2 [INTEGER]: 1500
.1.3.6.1.2.1.2.2.1.4.4 [INTEGER]: 1476
.1.3.6.1.2.1.2.2.1.4.8 [INTEGER]: 1500
.1.3.6.1.2.1.2.2.1.4.16 [INTEGER]: 1500
.1.3.6.1.2.1.2.2.1.4.17 [INTEGER]: 1500
.1.3.6.1.2.1.2.2.1.4.19 [INTEGER]: 1500
.1.3.6.1.2.1.2.2.1.4.20 [INTEGER]: 1480
.1.3.6.1.2.1.2.2.1.5.2 [GAUGE32]: 100000000
.1.3.6.1.2.1.2.2.1.5.4 [GAUGE32]: 100000000
.1.3.6.1.2.1.2.2.1.5.8 [GAUGE32]: 100000000
.1.3.6.1.2.1.2.2.1.5.16 [GAUGE32]: 100000000
.1.3.6.1.2.1.2.2.1.5.17 [GAUGE32]: 100000000
.1.3.6.1.2.1.2.2.1.5.19 [GAUGE32]: 100000000

[victor]

Hi,

is it possible to organize SNMP access for us to few TPLink devices so we can test how server see them and fix any discovered issues?

Best regards,
Victor