NetXMS Support Forum

Please login or register.

Login with username, password and session length

Author Topic: LLDP not discovered on NETONIX  (Read 261 times)

gmonk63

  • Full Member
  • ***
  • Posts: 122
    • View Profile
LLDP not discovered on NETONIX
« on: March 13, 2019, 08:57:35 pm »

I have version 2.2.6 which I noticed does not properly discovery lldp on NETONIX switches.  I have looked at the release notes of the newer versions and no of these address this. Im wondering if this is a bug.  I can pull the lldp database using snmp client and see all listed neighbors but node does not show lldp enabled


Thanks
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6533
    • View Profile
Re: LLDP not discovered on NETONIX
« Reply #1 on: March 20, 2019, 07:58:27 pm »

Hi,

server checks OID .1.0.8802.1.1.2.1.3.2.0 (lldpLocChassisId) as test for LLDP support on device. Did your device returns anything under .1.0.8802.1.1.2.1.3 (lldpLocalSystemData)?

Best regards,
Victor
Logged

gmonk63

  • Full Member
  • ***
  • Posts: 122
    • View Profile
Re: LLDP not discovered on NETONIX
« Reply #2 on: April 01, 2019, 11:52:40 pm »

Victor,

Sorry i completely forgot about this.  No this switch does not respond to those OID's only the remote table seems to be populated. Is it possible to do a check on the remote table for any entries and enable LLDP  based on if any neighbors are found as well.   I dont know why this switch does not respond to .1.0.8802.1.1.2.1.3.2.0  or  .1.0.8802.1.1.2.1.3  but Im sure there could be other off brand switches that do the same.


Thanks,

Gary 
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6533
    • View Profile
Re: LLDP not discovered on NETONIX
« Reply #3 on: April 02, 2019, 10:54:59 am »

Hi,

LLDP chassis ID is important to match LLDP data from two peer switches. Can you show me remote table from one of peers of this switch?

Best regards,
Victor
Logged

gmonk63

  • Full Member
  • ***
  • Posts: 122
    • View Profile
Re: LLDP not discovered on NETONIX
« Reply #4 on: May 09, 2019, 10:05:16 pm »

.1.0.8802.1.1.2.1.4.1.1.2.84659416.13.1 [INTEGER] = 13
.1.0.8802.1.1.2.1.4.1.1.2.84658408.12.2 [INTEGER] = 12
.1.0.8802.1.1.2.1.4.1.1.3.84659416.13.1 [INTEGER] = 1
.1.0.8802.1.1.2.1.4.1.1.3.84658408.12.2 [INTEGER] = 2
.1.0.8802.1.1.2.1.4.1.1.4.84659416.13.1 [INTEGER] = 4
.1.0.8802.1.1.2.1.4.1.1.4.84658408.12.2 [INTEGER] = 4
.1.0.8802.1.1.2.1.4.1.1.5.84659416.13.1 [STRING] = ec-13-b2-63-96-7c
.1.0.8802.1.1.2.1.4.1.1.5.84658408.12.2 [STRING] = 6c-3b-6b-54-b0-e2
.1.0.8802.1.1.2.1.4.1.1.6.84659416.13.1 [INTEGER] = 5
.1.0.8802.1.1.2.1.4.1.1.6.84658408.12.2 [INTEGER] = 5
.1.0.8802.1.1.2.1.4.1.1.7.84659416.13.1 [STRING] = Port 14
.1.0.8802.1.1.2.1.4.1.1.7.84658408.12.2 [STRING] = ether1
.1.0.8802.1.1.2.1.4.1.1.8.84659416.13.1 [STRING] = Port 14
.1.0.8802.1.1.2.1.4.1.1.8.84658408.12.2 [STRING] =
.1.0.8802.1.1.2.1.4.1.1.9.84659416.13.1 [STRING] = 1971_BPDO_SW
.1.0.8802.1.1.2.1.4.1.1.9.84658408.12.2 [STRING] = MTIK_UNDO_AP
.1.0.8802.1.1.2.1.4.1.1.10.84659416.13.1 [STRING] = Netonix WS-12-250-AC
.1.0.8802.1.1.2.1.4.1.1.10.84658408.12.2 [STRING] = MikroTik RouterOS 6.42.9 (long-term) RB Groove A-52HPn r2

The above is the lldpRemTable from a Netonix switch in the field.  We are having the same issues with our Mikrotik switches.  I understand the need for the LLDP chassis ID but it seems there are several switches that only populate remote table info  and are there any cases why the LLDP chassis ID would differ from the Bridge Base Address could you not supplement this base address assuming the checks for LLDP chassis ID fail but only if there are entries in the LLDPRemtable

Thanks,

Gary
Logged