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

Issue with Extreme 210/220 series switches not populating VLAN information

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Default
    • None

    Description

      VLAN table and information missing from Observium.

      Attached an image and snmpwalk dump.

      Attachments

        Activity

          [OBS-3892] Issue with Extreme 210/220 series switches not populating VLAN information

          Added in r11638.

          landy Mike Stupalov added a comment - Added in r11638.

          Oh these are another broadcom OEM device, i spy 4413!

          .1.3.6.1.2.1.1.9.1.2.18 = OID: .1.3.6.1.4.1.4413.1.1.59

          adama Adam Armstrong added a comment - Oh these are another broadcom OEM device, i spy 4413! .1.3.6.1.2.1.1.9.1.2.18 = OID: .1.3.6.1.4.1.4413.1.1.59

          VLAN data is missing because they don't seem to populate EXTREME-VLAN-MIB. Not sure if they are an OEM product with standard MIBs from elsewhere.

          adama Adam Armstrong added a comment - VLAN data is missing because they don't seem to populate EXTREME-VLAN-MIB. Not sure if they are an OEM product with standard MIBs from elsewhere.

          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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - 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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            stobeh Tuomas Rantala
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: