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

Add Filter Option for Trunk/Type in FDB Table Search

Details

    • New Feature
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • Default
    • None

    Description

      It would be helpful to have a filter option for "Trunk/Type" in the FDB Table search view (Search -> FDB Table). This would allow users to exclude specific types of entries (e.g., dot1q) from the results. The main use case is to more easily locate which physical port a specific MAC address is connected to, by filtering out trunk-related entries.

      Use case:

      • Finding the actual access port of a MAC address without the noise of trunk entries
      • Quicker troubleshooting of MAC address locations

      Suggested implementation: Add a dropdown filter at the top of the FDB Table for Trunk/Type selection.

      Attachments

        Activity

          [OBS-4952] Add Filter Option for Trunk/Type in FDB Table Search
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          helge.wiethoff@thga.de Helge Wiethoff created issue -
          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            helge.wiethoff@thga.de Helge Wiethoff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: