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

CISCO-ACL-MIB Support

Details

    Description

      Hi there:.-),

      would it be possible to add some extra graph to the "Ports" site to see how many packets got dropped by the applied ACL on this interface? I think it could be a very usefull information.

      In this run it could be also merged with the feature suggestion mentioned in OBS-2940 to get this for extreme networks too.

      Thank you

      Attachments

        Issue Links

          mentions

          New Feature - A new feature of the product, which has yet to be developed. OBS-2940 Extreme ACL Counter per Interface / VLAN

          • Major - Major loss of function.
          • Open

          Activity

            [OBS-3619] CISCO-ACL-MIB Support
            landy Mike Stupalov added a comment -

            Hi Denis Klimek, we have not received the additional information requested earlier from you in this issue 'Hi there:.-),

            would it be possible to add some extra graph to the "Ports" site to see how many packets got dropped by the applied ACL on this interface? I think it could be a very usefull information.

            In this run it could be also merged with the feature suggestion mentioned in OBS-2940 to get this for extreme networks too.

            Thank you'!

            Issues without your response will be closed within 2 weeks.

            landy Mike Stupalov added a comment - Hi Denis Klimek, we have not received the additional information requested earlier from you in this issue 'Hi there:.-), would it be possible to add some extra graph to the "Ports" site to see how many packets got dropped by the applied ACL on this interface? I think it could be a very usefull information. In this run it could be also merged with the feature suggestion mentioned in OBS-2940 to get this for extreme networks too. Thank you'! Issues without your response will be closed within 2 weeks.
            bot Observium Bot added a comment -

            Please make and attach additional information about the device:

            • full snmp dump from device: 

              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              		 
              snmpwalk -v2c -c <community>  --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> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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
              dklimek Denis Klimek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: