Issues with discovery protocols on WS-12-250-AC

[bbriggs]

Hey, I have enabled LLDP on a WS-12-250-AC...however I can't find a way to access the information. Nothing in the GUI and via SSH I do not see the LLDP information anywhere either. I also enabled CDP and UDP but none seem to be working / storing the information anywhere.

[sakita]

Tools, Discovery...

The checkboxes for Cisco and LLDP tell the switch to send packets to neighboring switches. If you have the discovery tab checkbox enabled then go to Tools, Discovery to see neighbor switches (if they are sending discovery packets).

[bbriggs]

Is there a way to see the neighbors from either the command line or via an SNMP query?

[sirhc]

sakita is correct.

By enabling the LLDP or CDP protocol the switch will notify neighbors or discovery tools for that protocol of its existence.

In the discovery TAB it will only report a device once by the first protocol it sees. So for sake of argument the switch sees another switch that has UDP, CDP, LLDP enabled whichever protocol it sees first is the one it will report in the Discovery Tab

[sirhc]

Is there a way to see the neighbors from either the command line or via an SNMP query?

No, I do not believe so but have asked Eric to confirm.

[bbriggs]

sakita is correct.

By enabling the LLDP or CDP protocol the switch will notify neighbors or discovery tools for that protocol of its existence.

In the discovery TAB it will only report a device once by the first protocol it sees. So for sake of argument the switch sees another switch that has UDP, CDP, LLDP enabled whichever protocol it sees first is the one it will report in the Discovery Tab

My thought is that if it is in the Interface it will typically be in JSON file on the backend as well?

[Eric Stern]

Is there a way to see the neighbors from either the command line or via an SNMP query?

From the command line, "cat /tmp/discovery.json"

[bbriggs]

Is there a way to see the neighbors from either the command line or via an SNMP query?

From the command line, "cat /tmp/discovery.json"

File is not there, I have confirmed that an upstream device DOES have CDP / LLDP enabled.

Is it possible I need to reboot the device?

[sakita]

The file isn't there unless the 'Discovery Tab' checkbox in Device Configuration is checked...

cmdline

cat /tmp/discovery.json

...I verified this behavior by turning the checkbox OFF and then rebooting to make sure the existing file was deleted. Turning it back ON did NOT require a reboot.

[bbriggs]

The file isn't there unless the 'Discovery Tab' checkbox in Device Configuration is checked...

cmdline

cat /tmp/discovery.json

...I verified this behavior by turning the checkbox OFF and then rebooting to make sure the existing file was deleted. Turning it back ON did NOT require a reboot.

Here is an exact copy/paste of the configure for each being "true".


SIDE NOTE - FIRMWARE: 1.3.9

admin@NET-WAN1:/tmp# cat /tmp/config/discovery
Ubiquiti true
cisco true
lldp true


admin@NET-WAN1:/tmp# ls -l
-rw-r--r-- 1 admin root 19820 Nov 29 17:22 1hr.json
-rw-r--r-- 1 admin root 19699 Nov 29 17:22 30sec.json
-rw-r--r-- 1 admin root 19812 Nov 29 17:22 5min.json
-rw-r--r-- 1 admin root 23 Dec 31 1969 TZ
-rw-r--r-- 1 admin root 15060 Dec 31 1969 boot-config.json
-rw-r--r-- 1 admin root 32 Dec 31 1969 bootid
drwxr-xr-x 2 admin root 0 Dec 31 1969 config
-rw-r--r-- 1 admin root 124 Dec 31 1969 fstab
-rw-r--r-- 1 admin root 1779 Nov 29 17:22 lacpportstatus.json
drwxr-xr-x 3 admin root 0 Dec 31 1969 lib
drwxr-xr-x 2 admin root 0 Dec 31 1969 lock
drwxr-xr-x 4 admin root 0 Jan 7 1970 log
-rw-r--r-- 1 admin root 5181 Nov 29 11:18 mactable.json
srwxr-xr-x 1 admin root 0 Dec 31 1969 php.socket-0
srwxr-xr-x 1 admin root 0 Dec 31 1969 php.socket-1
-rw-r--r-- 1 admin root 5 Nov 18 14:27 pinger_start_date
drwxr-xr-x 2 admin root 0 Dec 31 1969 poe_override
lrwxrwxrwx 1 admin root 21 Dec 31 1969 resolv.conf -> /tmp/resolv.conf.auto
-rw-r--r-- 1 admin root 20 Dec 31 1969 resolv.conf.auto
drwxr-xr-x 2 admin root 0 Nov 29 12:47 run
-rw------- 1 admin root 21 Nov 29 17:22 sess_2bc27d0b1ab2eddccc383efbd892108e
-rw-r--r-- 1 admin root 18 Jan 1 1970 sfpstatus
drwxr-xr-x 2 admin root 0 Dec 31 1969 state
srwxr-xr-x 1 admin root 0 Dec 31 1969 stats.socket-0
-rw-r--r-- 1 admin root 6869 Nov 29 17:22 stats.tmp
-rw-r--r-- 1 admin root 686 Nov 29 17:22 stpstatus.json