@Fleegle61 

Not really familiar with that. Use some port scanner? Angry IP Scanner

@John1234 I am doing an extensive nmap and I do see that UDP port 161 is open but...its not responding back when LibreNMS tries to add them as devices so it can monitor any issues with them.  So my 2008P is fine but my EAP225 and ER605 show an open port but no responses coming from them.  I also confirmed that I have SNMP v2c on and the community is public as is typical. 

 

Discovered open port 161/udp on 192.168.0.3
Discovered open port 161/udp on 192.168.0.1

 

 

 

@Fleegle61 

What if you restart everything? This is strange. 

I actually had done restarts 2 days ago. I did a very comprehensive scan and I see UDP/161 is open on the router and EAP yet...they wont respond back. I may try changing to V3 rather than using V2C and see if that does anything. I am just assuming right now that it was the upgrade from 4.4.4 to 4.4.6...cant nail it down yet.

So I did a full power shut down today of all my hardware.  I STILL cannot get SNMP connectivity to any of the TP-Link hardware other than the switch. The rest say they have UDP 151 open but I cant get any messages. 

 

Was hoping Fae would chime in. 

  @Fleegle61 with an update.....

 

I figured I would wait for a while to see if any of the firmware updates would take care of this problem.  Unfortunately, I still cannot monitor my router or controller using SNMP yet, I can monitor the 225, 2008 and 2210 with no issues.  

 

So not sure why TP-LINK has not yet been able to resolve the problem with monitoring all my devices using an SNMP agent like LibreNMS.  I tried using public and private as community strings with no luck.  I would hope that I DONT have to put the devices in stand alone mode in order to get them to respond.  

 

I dont have high hopes at the moment that this will be resolved any time soon unless they do an update to the ER605 or OC200 which specifically addresses this.