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

support limits for pps on ports

Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Discovery, Poller

    Description

      Observium already collect information about "all" ports.
      And observium also collect pps statistics for unicast/broadcast/milticast traffic (ussually from IF-MIB).

      I want to request new feature for this graph - discovery limits.

      Usually on switches configured storm control, so the idea is to discovery that configuration.

      What need to be improved:

      • discovery for ports - os/model specific
      • graph generation
      • db structure for ports table
      • alert checker for ports (support for using limit like @sensor_limit_low)
      • other

       
      Examples (random switch only for example):

      • snmpwalk from D-Link DES-3028.
        Configuration was: 

        # STORM
        		 
         
        		 
        config traffic trap none
        		 
        config traffic control 1-22 broadcast enable multicast enable unicast disable action shutdown threshold 64 countdown 5 time_interval 5
        		 
        config traffic control 23-28 broadcast disable multicast disable unicast disable action drop threshold 1000 countdown 0 time_interval 5

      • snmpwalk from SNR S2995G 

        snmpwalk ... SNR-SWITCH-MIB::portRateLimitTable
        		 
        SNR-SWITCH-MIB::portRateLimitPortIndex.4 = INTEGER: 4
        		 
        SNR-SWITCH-MIB::portRateLimitConfigBroadcastNum.4 = INTEGER: 645
        		 
        SNR-SWITCH-MIB::portRateLimitCurBroadcastNum.4 = INTEGER: 0
        		 
        SNR-SWITCH-MIB::portRateLimitConfigMulticastNum.4 = INTEGER: 500
        		 
        SNR-SWITCH-MIB::portRateLimitCurMulticastNum.4 = INTEGER: 0
        		 
        SNR-SWITCH-MIB::portRateLimitConfigUnicastNum.4 = INTEGER: 0
        		 
        SNR-SWITCH-MIB::portRateLimitCurUnicastNum.4 = INTEGER: 666
        		 
        SNR-SWITCH-MIB::portRateLimitConfigAllNum.4 = INTEGER: 0
        		 
        SNR-SWITCH-MIB::portRateLimitCurAllNum.4 = INTEGER: 666
        		 
        SNR-SWITCH-MIB::portRateLimitPacketsType.4 = INTEGER: 5
        		 
        SNR-SWITCH-MIB::portRateLimitViolationMode.4 = INTEGER: nocontrol(0)
        		 
        SNR-SWITCH-MIB::portRateLimitShutRecoveryTime.4 = INTEGER: 300

        configuration was: 

        Interface Ethernet1/0/4
        		 
        ...
        		 
         rate-violation broadcast 645
        		 
         rate-violation multicast 500
        		 
        ...

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. OBS-3767 New entity : Protocols/Services states

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Review

          Activity

            [OBS-3867] support limits for pps on ports
            mtivi Martyushev Tim added a comment -

            FOR SNR (DCN like) switches portRateLimitConfigMulticastNum and portRateLimitConfigBroadcastNum may be used as limit (line on graph) for multicast/broadcast

            mtivi Martyushev Tim added a comment - FOR SNR (DCN like) switches portRateLimitConfigMulticastNum and portRateLimitConfigBroadcastNum may be used as limit (line on graph) for multicast/broadcast
            mtivi Martyushev Tim added a comment -

            No need to add dump.

            mtivi Martyushev Tim added a comment - No need to add dump.
            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.

            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
              mtivi Martyushev Tim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: