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

Cisco IOS/ASA- Module "Processors"

Details

    • Vendor Bug
    • Resolution: Fixed
    • Trivial
    • None
    • Enterprise Edition
    • Poller

    Description

      Seems like we collect CPU info with HOST-RESOURCES-MIB
      But instead  we should use CISCO-PROCESS-MIB, described below

      https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15215-collect-cpu-util-snmp.html

      I have attached a pic and debug of a Cisco FP-1010 that seems a bit whacky. It has one CPU with 4 cores according to spec, but observium sees multiple cpu's and also wrong utilization

      Attachments

        1. debug.log
          341 kB
        2. pic.png
          pic.png
          125 kB

        Activity

          [OBS-4394] Cisco IOS/ASA- Module "Processors"
          landy Mike Stupalov added a comment -

          Fixed in r12507.

          HOST-RESOURCES-MIB skipped.

          landy Mike Stupalov added a comment - Fixed in r12507. HOST-RESOURCES-MIB skipped.
          landy Mike Stupalov added a comment -

          Probably they incorrectly report "idle" instead normal "load"

          landy Mike Stupalov added a comment - Probably they incorrectly report "idle" instead normal "load"
          landy Mike Stupalov added a comment -

          I will see,
          but mainly this mean device(s) report incorrect values by HOST-RESOURCES-MIB.
          This vendor issue and anyway need write Cisco TAC for this.

          landy Mike Stupalov added a comment - I will see, but mainly this mean device(s) report incorrect values by HOST-RESOURCES-MIB. This vendor issue and anyway need write Cisco TAC for this.
          cheri001 Christian Eriksson added a comment -

          Attached snmpwalk

          cheri001 Christian Eriksson added a comment - Attached snmpwalk
          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 -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

          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 -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 This comment is added automatically.

          People

            landy Mike Stupalov
            cheri001 Christian Eriksson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: