Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Discovery, OS

    Description

      Hi,

      We have a Cisco APIC these run on UCS Chassis in case ours are the UCS C220 m5. 
      Adding this device only brings back some basic info (ports). Its missing Storage, CPU and Memory along with environmental etc. 

      I can see under our instance /mibs section there are the following mibs. 

      CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

      CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB

      CISCO-UNIFIED-COMPUTING-MEMORY-MIB

      CISCO-UNIFIED-COMPUTING-PROCESSOR-MIB

      CISCO-UNIFIED-COMPUTING-STORAGE-MIB

      https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/mib/c-series/b_UCS_Standalone_C-Series_MIBRef/b_UCS_Standalone_C-Series_MIBRef_chapter_01.html

      Following above link states the above mibs can be used for these devices.  

      I debugged the device can see how it matches on the OS and then what mib's are being applied. Below is that output, is it possible to get the Cisco APIC updated to add the above Mibs?

      Attachments

        Activity

          [OBS-3766] Cisco APIC

          Probably trouble in snmp configuration on device.
          Try to switch snmp v2 version..

          Show snmp config from device (apic) without private fields (community/passwords/etc).

          landy Mike Stupalov added a comment - Probably trouble in snmp configuration on device. Try to switch snmp v2 version.. Show snmp config from device (apic) without private fields (community/passwords/etc).
          rizzo Alessandro Rizzo added a comment - - edited

          Hi Mike,

          I've just been over the logs now I've seen failing on the following device is not responding to them...

          CISCO-PROCESS-MIB
          CISCO-ENTITY-SENSOR-MIB
          CISCO-ENTITY-FRU-CONTROL-MIB 

          That's cause it think these need to be the following as I put in the Jira and link the documentation which states these mibs should be used. 

           

          CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

          CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB

          CISCO-UNIFIED-COMPUTING-MEMORY-MIB

          CISCO-UNIFIED-COMPUTING-PROCESSOR-MIB

          CISCO-UNIFIED-COMPUTING-STORAGE-MIB

          I think this might of changed recently with the APIC Models and what MIBs are used. 

          I'll do some digging tomorrow trying outside of obs polling the device to find out what works and doesn't to feedback. 

           

          Cheers

          Alessandro 

          rizzo Alessandro Rizzo added a comment - - edited Hi Mike, I've just been over the logs now I've seen failing on the following device is not responding to them... CISCO-PROCESS-MIB CISCO-ENTITY-SENSOR-MIB CISCO-ENTITY-FRU-CONTROL-MIB  That's cause it think these need to be the following as I put in the Jira and link the documentation which states these mibs should be used.    CISCO-UNIFIED-COMPUTING-COMPUTE-MIB CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB CISCO-UNIFIED-COMPUTING-MEMORY-MIB CISCO-UNIFIED-COMPUTING-PROCESSOR-MIB CISCO-UNIFIED-COMPUTING-STORAGE-MIB I think this might of changed recently with the APIC Models and what MIBs are used.  I'll do some digging tomorrow trying outside of obs polling the device to find out what works and doesn't to feedback.    Cheers Alessandro 

          Hi Mike,

          We've upgraded to latest no change.

          I've attach the discovery as requested. 

          Cheers

          Alessandro 

          rizzo Alessandro Rizzo added a comment - Hi Mike, We've upgraded to latest no change. I've attach the discovery as requested.  Cheers Alessandro 
          wardy5402 Ben Ward added a comment -

          Hi Mike

          We have now updated the version of OBS running to 21.10.11678 (stable)

          wardy5402 Ben Ward added a comment - Hi Mike We have now updated the version of OBS running to 21.10.11678 (stable)

          Hi, by first update your install (you use old revision):

          There is a newer revision of Observium available!
          Version 21.9.11575 (6th December 2021) is 210 revisions ahead.

          After that make debug for all modules than (as I see os detected correctly):

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

          landy Mike Stupalov added a comment - Hi, by first update your install (you use old revision): There is a newer revision of Observium available! Version 21.9.11575 (6th December 2021) is 210 revisions ahead. After that make debug for all modules than (as I see os detected correctly): ./discovery.php -d -h <device>

          Hi Mike, 

          I've attached the debug you requested.  

          We are currently running 21.5.11365

          Its odd from your dev we don't see any status indicators or temperature appearing on the right hand side.

          Cheers
          Alessandro  

           

           

           

           

           

          rizzo Alessandro Rizzo added a comment - Hi Mike,  I've attached the debug you requested.   We are currently running 21.5.11365 Its odd from your dev we don't see any status indicators or temperature appearing on the right hand side. Cheers Alessandro            

          This is how I see your dump on my dev (partially):

          landy Mike Stupalov added a comment - This is how I see your dump on my dev (partially):

          Hi, as I see by your snmp dump, this device already correctly detected and already support all of this MIBs.
          Which version of observium you use?

          Please attach discovery debug for:

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

          landy Mike Stupalov added a comment - Hi, as I see by your snmp dump, this device already correctly detected and already support all of this MIBs. Which version of observium you use? Please attach discovery debug for: ./discovery.php -d -m os -h <device>

          Hi, is there any update on this one?

          Cheers

          rizzo Alessandro Rizzo added a comment - Hi, is there any update on this one? Cheers

          attach the snmp dump

          rizzo Alessandro Rizzo added a comment - attach the snmp dump

          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
            rizzo Alessandro Rizzo
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: