Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum
  1. Home
  2. Support
  3. L2 topology - LLDP gives NO links

L2 topology - LLDP gives NO links

Scheduled Pinned Locked Moved Support
9 Posts 2 Posters 27.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    A
    amitayb
    wrote on last edited by
    #1

    Hi,
    I'm having a huge problem using the L2 topology - which is a great feature.
    my devices use lldp - see attached info but nothing is draw in the L2 map (i have the devices without the lldp links).
    what do I miss?
    is it a bug?
    centos \ netxms 3.0.2258.

    as you can see I've attached both netxms and device data.

    device: R1.R3073.S3930
    [11.12.2019 09:44:42] **** Poll request sent to server ****
    [11.12.2019 09:44:42] Poll request accepted
    [11.12.2019 09:44:42] Starting topology poll for node R1.R3073.S3930
    [11.12.2019 09:44:42] VLAN list successfully retrieved from node
    [11.12.2019 09:44:42] Switch forwarding database retrieved
    [11.12.2019 09:44:42] Link layer topology retrieved (1 connections found)
    [11.12.2019 09:44:42] Updating peer information on interfaces
    [11.12.2019 09:44:42]    Local interface ge-1/0/2 linked to remote interface R1.R3073.S3930:fxp0.0
    [11.12.2019 09:44:42] Link layer topology processed
    [11.12.2019 09:44:42] Finished topology poll for node R1.R3073.S3930
    [11.12.2019 09:44:42] **** Poll completed successfully ****

    [email protected]> show lldp neighbors
    Local Interface Chassis Id        Port info    System Name
    xe-1/3/1        30:7c:5e:38:d8:f0 529          R1.R3073.S6375
    xe-1/3/0        30:7c:5e:39:e7:70 528          R1.R3073.S6048

    [email protected]> show interfaces descriptions | match xe-
    xe-1/3/0        up    up  802-03-3073_RING_3073_TO_R1.R3073.S6048_xe-1/3/1
    xe-1/3/1        up    up  802-03-3073_RING_3073_TO_R1.R3073.S6375_xe-1/3/0

    **********************************
    device: R1.R3073.S6048
    [11.12.2019 09:41:23] **** Poll request sent to server ****
    [11.12.2019 09:41:23] Poll request accepted
    [11.12.2019 09:41:23] Starting topology poll for node R1.R3073.S6048
    [11.12.2019 09:41:23] VLAN list successfully retrieved from node
    [11.12.2019 09:41:23] Switch forwarding database retrieved
    [11.12.2019 09:41:23] Link layer topology retrieved (1 connections found)
    [11.12.2019 09:41:23] Updating peer information on interfaces
    [11.12.2019 09:41:23]    Local interface ge-1/0/2 linked to remote interface R1.R3073.S6048:fxp0.0
    [11.12.2019 09:41:23] Link layer topology processed
    [11.12.2019 09:41:23] Finished topology poll for node R1.R3073.S6048
    [11.12.2019 09:41:23] **** Poll completed successfully ****

    [email protected]> show lldp neighbors
    Local Interface Chassis Id        Port info    System Name
    xe-1/3/1        30:7c:5e:39:0d:70 527          R1.R3073.S3930
    xe-1/3/0        54:4b:8c:0e:3c:70 530          R1.R3073.S0020

    [email protected]> show interfaces descriptions | match xe-
    xe-1/3/0        up    up  802-03-3073_RING_3073_TO_R1.R3073.S0020_xe-1/3/1
    xe-1/3/1        up    up  802-03-3073_RING_3073_TO_R1.R3073.S3930_xe-1/3/0

    lldp.JPG

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      looks like server cannot retrieve all links for some reason. Could you please provide output of SNMP walk for .1.0.8802.1.1.2.1.4.1.1 for both nodes?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • A
        A
        amitayb
        wrote on last edited by
        #3

        Hi'
        Thanks for your reply.
        BTW - I've tested it with CA Spectrum - the L2 LLDP topology is created perfect there.

        [root@vmnetxms monitor]# snmpwalk  -v 2c -cXXXX R1.R3073.S3930 .1.0.8802.1.1.2.1.4.1.1
        iso.0.8802.1.1.2.1.4.1.1.4.997072.527.3 = INTEGER: 4
        iso.0.8802.1.1.2.1.4.1.1.4.1257372.528.4 = INTEGER: 4
        iso.0.8802.1.1.2.1.4.1.1.5.997072.527.3 = Hex-STRING: 30 7C 5E 39 E7 70
        iso.0.8802.1.1.2.1.4.1.1.5.1257372.528.4 = Hex-STRING: 30 7C 5E 38 D8 F0
        iso.0.8802.1.1.2.1.4.1.1.6.997072.527.3 = INTEGER: 7
        iso.0.8802.1.1.2.1.4.1.1.6.1257372.528.4 = INTEGER: 7
        iso.0.8802.1.1.2.1.4.1.1.7.997072.527.3 = STRING: "528"
        iso.0.8802.1.1.2.1.4.1.1.7.1257372.528.4 = STRING: "529"
        iso.0.8802.1.1.2.1.4.1.1.8.997072.527.3 = STRING: "802-03-3073_RING_3073_TO_R1.R3073.S3930_xe-1/3/0"
        iso.0.8802.1.1.2.1.4.1.1.8.1257372.528.4 = STRING: "802-03-3073_RING_3073_TO_R1.R3073.S3930_xe-1/3/1"
        iso.0.8802.1.1.2.1.4.1.1.9.997072.527.3 = STRING: "R1.R3073.S6048"
        iso.0.8802.1.1.2.1.4.1.1.9.1257372.528.4 = STRING: "R1.R3073.S6375"
        iso.0.8802.1.1.2.1.4.1.1.10.997072.527.3 = STRING: "Juniper Networks, Inc. acx2100 , version 12.3X54-D31.1 Build date: 2017-04-05 01:00:14 UTC "
        iso.0.8802.1.1.2.1.4.1.1.10.1257372.528.4 = STRING: "Juniper Networks, Inc. acx2100 , version 12.3X54-D31.1 Build date: 2017-04-05 01:00:14 UTC "
        iso.0.8802.1.1.2.1.4.1.1.11.997072.527.3 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.11.1257372.528.4 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.12.997072.527.3 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.12.1257372.528.4 = STRING: "("

        [root@vmnetxms monitor]# snmpwalk  -v 2c -cXXXX R1.R3073.S6048 .1.0.8802.1.1.2.1.4.1.1
        iso.0.8802.1.1.2.1.4.1.1.4.45.528.1 = INTEGER: 4
        iso.0.8802.1.1.2.1.4.1.1.4.46.527.2 = INTEGER: 4
        p"o.0.8802.1.1.2.1.4.1.1.5.45.528.1 = STRING: "0|^9
        iso.0.8802.1.1.2.1.4.1.1.5.46.527.2 = Hex-STRING: 54 4B 8C 0E 3C 70
        iso.0.8802.1.1.2.1.4.1.1.6.45.528.1 = INTEGER: 7
        iso.0.8802.1.1.2.1.4.1.1.6.46.527.2 = INTEGER: 7
        iso.0.8802.1.1.2.1.4.1.1.7.45.528.1 = STRING: "527"
        iso.0.8802.1.1.2.1.4.1.1.7.46.527.2 = STRING: "530"
        iso.0.8802.1.1.2.1.4.1.1.8.45.528.1 = STRING: "802-03-3073_RING_3073_TO_R1.R3073.S6048_xe-1/3/1"
        iso.0.8802.1.1.2.1.4.1.1.8.46.527.2 = STRING: "802-03-3073_RING_3073_TO_R1.R3073.S6048_xe-1/3/0"
        iso.0.8802.1.1.2.1.4.1.1.9.45.528.1 = STRING: "R1.R3073.S3930"
        iso.0.8802.1.1.2.1.4.1.1.9.46.527.2 = STRING: "R1.R3073.S0020"
        iso.0.8802.1.1.2.1.4.1.1.10.45.528.1 = STRING: "Juniper Networks, Inc. acx2100 , version 12.3X54-D31.1 Build date: 2017-04-05 01:00:14 UTC "
        iso.0.8802.1.1.2.1.4.1.1.10.46.527.2 = STRING: "Juniper Networks, Inc. acx2100 , version 12.3X54-D31.1 Build date: 2017-04-05 01:00:14 UTC "
        iso.0.8802.1.1.2.1.4.1.1.11.45.528.1 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.11.46.527.2 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.12.45.528.1 = STRING: "("
        iso.0.8802.1.1.2.1.4.1.1.12.46.527.2 = STRING: "("

        1 Reply Last reply
        0
        • A
          A
          amitayb
          wrote on last edited by
          #4

          Hi,
          does the retrieve data looks OK?

          1 Reply Last reply
          0
          • V
            V
            Victor Kirhenshtein
            wrote on last edited by
            #5

            Could you please show output of commands

            nxadm -c "show lldp id"

            for both nodes, replacing id with actual node ID?

            Best regards,
            Victor

            1 Reply Last reply
            0
            • A
              A
              amitayb
              wrote on last edited by
              #6

              for first node:
              ./nxadm -c "show lldp 267"
              * Node LLDP ID: 4@307C5E390D70

              * Local LLDP ports
                Port | ST | Len | Local ID                | Description
                -----+----+-----+--------------------------+--------------------------------------
                  527 |  7 |  3 | 353237                  | 802-03-3073_RING_3073_TO_R1.R3073.S6048_xe-1/3/1
                  528 |  7 |  3 | 353238                  | 802-03-3073_RING_3073_TO_R1.R3073.S6375_xe-1/3/0

              second node:
              ./nxadm -c "show lldp 265"
              * Node LLDP ID: 4@307C5E39E770

              * Local LLDP ports
                Port | ST | Len | Local ID                | Description
                -----+----+-----+--------------------------+--------------------------------------
                  527 |  7 |  3 | 353237                  | 802-03-3073_RING_3073_TO_R1.R3073.S0020_xe-1/3/1
                  528 |  7 |  3 | 353238                  | 802-03-3073_RING_3073_TO_R1.R3073.S3930_xe-1/3/0

              1 Reply Last reply
              0
              • A
                A
                amitayb
                wrote on last edited by
                #7

                attached 2 files with L5 debug

                lldpR1.R3073.S6048.txt

                lldpR1.R3073.S3930.txt

                1 Reply Last reply
                0
                • A
                  A
                  amitayb
                  wrote on last edited by
                  #8

                  attached interface and overview

                  interface.jpg

                  overview.jpg

                  1 Reply Last reply
                  0
                  • A
                    A
                    amitayb
                    wrote on last edited by
                    #9

                    [root@vmnetxms bin]# snmpwalk  -v 2c -cXXX R1.R3073.S3930 .1.3.6.1.2.1.17.1.4.1.2
                    SNMPv2-SMI::mib-2.17.1.4.1.2.41 = INTEGER: 517
                    SNMPv2-SMI::mib-2.17.1.4.1.2.42 = INTEGER: 518
                    SNMPv2-SMI::mib-2.17.1.4.1.2.43 = INTEGER: 519
                    SNMPv2-SMI::mib-2.17.1.4.1.2.44 = INTEGER: 520
                    SNMPv2-SMI::mib-2.17.1.4.1.2.51 = INTEGER: 0
                    SNMPv2-SMI::mib-2.17.1.4.1.2.54 = INTEGER: 524
                    [root@vmnetxms bin]# snmpwalk  -v 2c -cXXX R1.R3073.S6048 .1.3.6.1.2.1.17.1.4.1.2
                    SNMPv2-SMI::mib-2.17.1.4.1.2.41 = INTEGER: 517
                    SNMPv2-SMI::mib-2.17.1.4.1.2.42 = INTEGER: 518
                    SNMPv2-SMI::mib-2.17.1.4.1.2.43 = INTEGER: 519
                    SNMPv2-SMI::mib-2.17.1.4.1.2.44 = INTEGER: 520

                    1 Reply Last reply
                    0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes

                    • Login
                    • Don't have an account? Register
                    • Login or register to search.
                    Powered by NodeBB Contributors
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Users
                    • Groups