Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3622

Wrong lld local port information

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      I have some TP-Link switches and JetStream 24-Port Gigabit L2+ Managed Switch with 4 SFP Slots. LLDP neighbors shows wrong localport information.

      Local ports shold be different. In this case Gigabitethernet1/0/27 and Gigabutethernet1/0/28

       

      Attachments

        1. myagent.snmpwalk.txt
          93 kB
        2. myagent.snmpwalk1.txt
          246 kB
        3. TP_LINK_LLDP_PROBLEM-1.png
          TP_LINK_LLDP_PROBLEM-1.png
          42 kB

        Activity

          [OBS-3622] Wrong lld local port information
          landy Mike Stupalov made changes -
          Due Date New: 2022/02/25
          Labels New: noresponse
          landy Mike Stupalov added a comment -

          Hi Tomasz Karczewski, we have not received the additional information requested earlier from you in this issue 'I have some TP-Link switches and JetStream 24-Port Gigabit L2+ Managed Switch with 4 SFP Slots. LLDP neighbors shows wrong localport information.

          Local ports shold be different. In this case Gigabitethernet1/0/27 and Gigabutethernet1/0/28

           '!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Tomasz Karczewski, we have not received the additional information requested earlier from you in this issue 'I have some TP-Link switches and JetStream 24-Port Gigabit L2+ Managed Switch with 4 SFP Slots. LLDP neighbors shows wrong localport information. Local ports shold be different. In this case Gigabitethernet1/0/27 and Gigabutethernet1/0/28  '! Issues without your response will be closed within 2 weeks.
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          landy Mike Stupalov added a comment -

          yah, seems as device have trouble with walking. try little different snmpwalk command:

          snmpwalk -v2c -c <community> -t 2 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

          There added options for increase timeout and '-Cc' for error 'Error: OID not increasing'

          landy Mike Stupalov added a comment - yah, seems as device have trouble with walking. try little different snmpwalk command: snmpwalk -v2c -c <community> -t 2 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk There added options for increase timeout and '-Cc' for error 'Error: OID not increasing'
          tkarczewski Tomasz Karczewski added a comment -

          myagent.snmpwalk.txtmyagent.snmpwalk1.txt

          tkarczewski Tomasz Karczewski added a comment - myagent.snmpwalk.txt myagent.snmpwalk1.txt
          tkarczewski Tomasz Karczewski made changes -
          Comment [ ^myagent.snmpwalk.txt ]
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          tkarczewski Tomasz Karczewski made changes -
          Attachment New: myagent.snmpwalk.txt [ 19064 ]
          Attachment New: myagent.snmpwalk1.txt [ 19065 ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          landy Mike Stupalov added a comment -

          Please attach full snmp dump as Bot requested.

          landy Mike Stupalov added a comment - Please attach full snmp dump as Bot requested.

          People

            landy Mike Stupalov
            tkarczewski Tomasz Karczewski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: