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

Alert checkers matching on BGP peer group

Details

    • New Feature
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting
    • Juniper, Cisco, Quagga

    Description

      My company has a need to have differentiated alarming for various BGP peers.  We have hundreds of BGP peers on our network.  Our peers may be upstream providers, internet exchange peers, core nodes, customers, etc, which each one having different priorities for our support team.

      I have created a number of BGP peer groups, which are correctly classifying the peers.  However, when creating an alarm checker, I do not have the option to match on the peer group ID.  Having this feature would be immensely helpful to our business.

      Attachments

        Activity

          [OBS-3235] Alert checkers matching on BGP peer group
          cbaranoski Casey Baranoski added a comment -

          It's doing exactly what we need! Thank you very much!

          cbaranoski Casey Baranoski added a comment - It's doing exactly what we need! Thank you very much!
          adama Adam Armstrong added a comment -

          This might work now in r10278.

          adama Adam Armstrong added a comment - This might work now in r10278.
          cbaranoski Casey Baranoski added a comment -

          Thanks!  Currently, our Alert Checkers match content is the Group membership rules, copied verbatim.  That will start to get quite unwieldy when we start to add more differentiation between our different classes of BGP neighbors.

          cbaranoski Casey Baranoski added a comment - Thanks!  Currently, our Alert Checkers match content is the Group membership rules, copied verbatim.  That will start to get quite unwieldy when we start to add more differentiation between our different classes of BGP neighbors.
          adama Adam Armstrong added a comment -

          Ahh I see!

          BGP is odd in that it's actually two levels, the session itself, and then the AFI/SAFI pair. This might be why groups aren't already supported here.

          I'll see if groups can be exposed here.

          adama Adam Armstrong added a comment - Ahh I see! BGP is odd in that it's actually two levels, the session itself, and then the AFI/SAFI pair. This might be why groups aren't already supported here. I'll see if groups can be exposed here.
          cbaranoski Casey Baranoski added a comment -

          Hi Adam,

          I'm not referring to peer groups that are configured in my routers.  I'm referring to the ones configured in Observium.  See the attached screenshot.

           

          Thanks,

           

          Casey

           

          cbaranoski Casey Baranoski added a comment - Hi Adam, I'm not referring to peer groups that are configured in my routers.  I'm referring to the ones configured in Observium.  See the attached screenshot.   Thanks,   Casey  
          adama Adam Armstrong added a comment -

          I don't think any vendors actually expose peer group information in SNMP.

          adama Adam Armstrong added a comment - I don't think any vendors actually expose peer group information in SNMP.
          cbaranoski Casey Baranoski added a comment -

          Hi Mike,

          Not sure if I actually need to attach any snmpwalk output, as I'm not having any issues polling devices.  It's just a request about alarming.

          Thanks,

          Casey

          cbaranoski Casey Baranoski added a comment - Hi Mike, Not sure if I actually need to attach any snmpwalk output, as I'm not having any issues polling devices.  It's just a request about alarming. Thanks, Casey
          landy Mike Stupalov 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>

          landy Mike Stupalov 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>

          People

            adama Adam Armstrong
            cbaranoski Casey Baranoski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: