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

dot1dTpFdbPort FBD Lookup per vlan context Cisco IOS-XE

Details

    • Improvement
    • Resolution: Won't Fix
    • Minor
    • None
    • None
    • Discovery
    • None

    Description

      Requesting support for FDB Lookup Table Network device  ( ours Cisco 9300) 

      I'm not sure if this is already supported and do not know the feature flag but would be great to get FDB lookup table working on our switches to find devices, or perhaps have that run once a day or manually. 

       

      Based on Google - the walk would have to be performed on a per vlan context. 

      Reference: 

      https://www.nectus5.com/how-to-collect-list-of-mac-addresses-from-cisco-switch-via-snmp-dot1dtpfdbentry/

       

      Thank you  as always.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. OBS-317 No dot1qTpFdbEntry object for Cisco Devices

          • Major - Major loss of function.
          • Closed

          Activity

            [OBS-4279] dot1dTpFdbPort FBD Lookup per vlan context Cisco IOS-XE
            landy Mike Stupalov added a comment -

            For correct work vlan context on cisco devices with SNMPv3, you need add 'match prefix' on device. For example:

            snmp-server group MONITOR v3 auth match prefix access SNMP-MONITOR

            landy Mike Stupalov added a comment - For correct work vlan context on cisco devices with SNMPv3, you need add ' match prefix ' on device. For example: snmp-server group MONITOR v3 auth match prefix access SNMP-MONITOR
            jjozwik Joseph Jozwik added a comment -

            Just wanted to say- now that this is working it is so awesome, lol! Thank you!

            jjozwik Joseph Jozwik added a comment - Just wanted to say- now that this is working it is so awesome, lol! Thank you!
            jjozwik Joseph Jozwik added a comment -

            Disregard, switching to snmp v2c FDB lookup works. It is just v3 that is not working.

            jjozwik Joseph Jozwik added a comment - Disregard, switching to snmp v2c FDB lookup works. It is just v3 that is not working.
            jjozwik Joseph Jozwik added a comment -

            Found another issue that appears closed, could anyone advise if there is additional config  required to get this functional.

            jjozwik Joseph Jozwik added a comment - Found another issue that appears closed, could anyone advise if there is additional config  required to get this functional.
            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
              jjozwik Joseph Jozwik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: