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

Device - VLANs | Interfaces attributed to wrong vlan

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Discovery, Ports
    • Juniper, Junos

    Description

      Hello Observium Team, 

       

      the issue I'd like to report is that on all devices of our installation the ports associated to a vlan are reported wrong in the overview in this URI "/device/device=ID/tab=vlans/". 

      Please see the provided image. E.G Interface ge-0/0/1 is reported to be configured with vlan V1062 oder 1062. 

      Clicking on the ge-0/0/1 link shows this result, the port is configured with vlan 1043 on the port level. This report is correct, as the interface is configured that way.  

      When checking the switch I cannot find anything that could associated the interface ge-0/0/1 with VLAN 1092 that is reported by observium. 

      I tried to delete the device, including the rrds. After beeing added by Observium the same result is observed after discorvery / poll. 

      Version Used  12510. I don't know if this issue was observable in earlier versions. 

      Thank you for your feedback and thank you for the awesome monitoring solution. 

       

      Greetings 

      Milan Bätz

      HABA FAMILYGROUP

      Attachments

        1. discovery_n-jun-wk2-001
          2.64 MB
        2. image-2023-02-06-11-38-04-191.png
          image-2023-02-06-11-38-04-191.png
          40 kB
        3. image-2023-02-06-11-39-24-531.png
          image-2023-02-06-11-39-24-531.png
          43 kB
        4. image-2023-02-06-11-40-06-700.png
          image-2023-02-06-11-40-06-700.png
          13 kB
        5. poller_n-jun-wk2-001
          5.83 MB
        6. poller_n-jun-wk2-001-1
          5.83 MB

        Activity

          [OBS-4397] Device - VLANs | Interfaces attributed to wrong vlan
          HABA Familygroup Team Network added a comment -

          This issue is no longer reproducable and this ticket can be closed. Thank you for the assistance. 

          HABA Familygroup Team Network added a comment - This issue is no longer reproducable and this ticket can be closed. Thank you for the assistance. 
          HABA Familygroup Team Network added a comment -

          Hello Mike, 

          HABA Familygroup Team Network added a comment - Hello Mike, 
          landy Mike Stupalov added a comment -

          wait, as I see you set this port to ignore.
          It's mean port not polled mostly params (and vlan keeped old).

          landy Mike Stupalov added a comment - wait, as I see you set this port to ignore. It's mean port not polled mostly params (and vlan keeped old).
          HABA Familygroup Team Network added a comment -

          I missed that -d flag, here are the two documents with the correct output:
          discovery_n-jun-wk2-001poller_n-jun-wk2-001

          HABA Familygroup Team Network added a comment - I missed that -d flag, here are the two documents with the correct output: discovery_n-jun-wk2-001 poller_n-jun-wk2-001
          landy Mike Stupalov added a comment -

          this is not similar issue, because complete different oses and MIBs.

          landy Mike Stupalov added a comment - this is not similar issue, because complete different oses and MIBs.
          landy Mike Stupalov added a comment -

          You need make and attach debug discovery (with -d arg) as Bot requested:

          ./discovery.php -d -h <device>

          landy Mike Stupalov added a comment - You need make and attach debug discovery (with -d arg) as Bot requested: ./discovery.php -d -h <device>
          HABA Familygroup Team Network added a comment -

          OBS-4391 seems to be a similar issue

          HABA Familygroup Team Network added a comment - OBS-4391 seems to be a similar issue
          HABA Familygroup Team Network added a comment -

          poller_n-jun-wk2-001

          discovery_n-jun-wk2-001

          HABA Familygroup Team Network added a comment - poller_n-jun-wk2-001 discovery_n-jun-wk2-001
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

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

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            HABA Familygroup Team Network
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: