Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      Q-BRIDGE-MIB has been supported since 15.7.1, which was released 2015-05
      The support for EXTREME-VLAN-MIB does not detect access ports and marks all as dot1q

      https://extremeportal.force.com/ExtrArticleDetail?an=000090678

      https://documentation.extremenetworks.com/release_notes/ExtremeXOS/ExtremeXOS_15.7.1_RelNotes.pdf?_ga=2.96524060.225546487.1646917659-1124733846.1634759629

      Attached svn.diff. I removed the blacklist for q-bridge-mib and commented extreme-vlan-mib, which probably is not the way to go if users has version <15.7. Not sure how to go about it

      Attachments

        1. myagent.snmpwalk
          2.43 MB
        2. svn.diff
          1 kB

        Activity

          [OBS-4045] EXOS (extreme) and Q-BRIDGE-MIB

          snmpwalk attached

          cheri001 Christian Eriksson added a comment - snmpwalk attached

          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
            cheri001 Christian Eriksson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: