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

Cisco SB switch processor info missing since r13097

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Discovery
    • None

    Description

      A breaking change was introduced in r13097 that stripped the CPU metric off all cisco small business switches.  r13096 has CPU graphs still but once I upgrade to 13097 they disappear:

      root@observium:/var/www/observium# svn up -r 13097
      Updating '.':
      U    includes/definitions/mibs/edgecore.inc.php
      U    includes/definitions/mibs/netgear.inc.php
      A    includes/definitions/mibs/radlan
      A    includes/definitions/mibs/radlan/radlan-rndmng.php
      U    includes/definitions/mibs/radlan.inc.php
      D    includes/discovery/processors/ciscosb-rndmng.inc.php
      U    includes/entities/processor.inc.php

       

      The issue appears to be the deleted file: 
      includes/discovery/processors/ciscosb-rndmng.inc.php

      I updated to the latest r13244 and copied ciscosb-rndmng.inc.php back in and CPU graphs are working again.  Any idea why this file was deleted?

      Attachments

        Activity

          [OBS-4710] Cisco SB switch processor info missing since r13097
          landy Mike Stupalov added a comment -

          Fixed in r13259.

          landy Mike Stupalov added a comment - Fixed in r13259.
          chune Jon Nelson added a comment -

          Thanks, that fixed it for all the models except the newer CBS ones.  I will send over a debug poll of one of those shortly

          chune Jon Nelson added a comment - Thanks, that fixed it for all the models except the newer CBS ones.  I will send over a debug poll of one of those shortly
          landy Mike Stupalov added a comment -

          please attach full discovery debug (not patrial)!
          because here many additional info about selected MIBs.

          You can send debug in DM in our Discord channel (link in Bot message below) to me - user @landy

          landy Mike Stupalov added a comment - please attach full discovery debug (not patrial)! because here many additional info about selected MIBs. You can send debug in DM in our Discord channel (link in Bot message below) to me - user @landy
          chune Jon Nelson added a comment -

          see attached.  Looks like when processors got moved they only moved the HOST-RESCOURCES-MIB but not the CISCOSB-rndMng MIB.

           

          chune Jon Nelson added a comment - see attached.  Looks like when processors got moved they only moved the HOST-RESCOURCES-MIB but not the CISCOSB-rndMng MIB.  
          landy Mike Stupalov added a comment -

          This processors moved to definitions (that why file deleted).
          Run discovery device debug and attach:

          ./discovery.php -d -h <device>

          landy Mike Stupalov added a comment - This processors moved to definitions (that why file deleted). Run discovery device debug and attach: ./discovery.php -d -h <device>
          chune Jon Nelson added a comment -

          Sorry you can lower priority a notch, not seeing a way to edit it from my end.  But I do find this to be an important metric to monitor and have several alerts set for it.

          chune Jon Nelson added a comment - Sorry you can lower priority a notch, not seeing a way to edit it from my end.  But I do find this to be an important metric to monitor and have several alerts set for it.
          chune Jon Nelson added a comment -

          see above

          chune Jon Nelson added a comment - see above
          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
            chune Jon Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: