i did think this was the issue

i can see from the data that the ifName is being set individually per port, maybe i can join this with the description?

is the a sample os php file i can follow to get it to change the names and stuff?

once I’m happy, i will submit to jira with patch, and you can add it to the svn :)

Simon

On 1 Feb 2016, at 1:53 pm, Adam Armstrong <adama@memetic.org> wrote:

This is because TP-Link don't understand IF-MIB and have taken the "description" part of "ifDescr" a little too literally.

If you look at the data-dump for a port on this device, probably either ifName or ifAlias contains the real port name. This can be fixed by creating an OS for these devices and setting it to use ifName/ifAlias as label.

If it doesn't, well, there's not much you can do, because TP-Link probably won't fix it!

adam.

On 01/02/2016 12:56:16, Simon Smith <simonsmith5521@gmail.com> wrote:

Hi All

not sure if this is a bug or maybe something wrong with our switch?

we added a TP-Link 8 port gigabit switch to monitor as we wanted to see what data we could get

for some reason, observium has listed all interfaces as Ethernet Interface ?

also it appears the vlans are also being found as lans, as well ?

no port 1 port 2 etc

just Ethernet Interface and Vlan ?

what ive also found is on the interfaces page the plans are showing these blue arrows with the ethernet interface name ? never seen it before? any ideas?

attached is screenshots, poller log and discovery log if people what help :)

Simon


_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium