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

Error al agregar Switch Cisco CBS350

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • None
    • None

    Description

      Hola, buenos días

      Tengo problema para ver la información de 3 Switches Cisco CBS350 en observium (versión profesional), los agrego normalmente como cualquier otro dispositivo, sin embargo no me muestra su Procesador, Temperatura, velocidad del ventilador, Indicadores de Estado, etc.

      Otros modelos de Switches Cisco si me permitio agregarlos sin ningun problema.

       

      Attachments

        Activity

          [OBS-4750] Error al agregar Switch Cisco CBS350
          msierra Miguel Sierra added a comment -

          "If you find something in their SNMP MIBs which is not currently supported, we can add it"

           

          Good afternoon, it was literally what you mentioned in your previous response, likewise, I don't know if it is what you were trying to imply.

          Although the error persists, is there any other solution or steps to follow to resolve the incident?

          msierra Miguel Sierra added a comment - "If you find something in their SNMP MIBs which is not currently supported, we can add it"   Good afternoon, it was literally what you mentioned in your previous response, likewise, I don't know if it is what you were trying to imply. Although the error persists, is there any other solution or steps to follow to resolve the incident?
          adama Adam Armstrong added a comment -

          I didn't tell you to "add the mib"?

          adama Adam Armstrong added a comment - I didn't tell you to "add the mib"?
          msierra Miguel Sierra added a comment -

          Hello Adam

          I tried to add the mib as you told me a few days ago, solving the error on 1 of the devices, but not on the second.

          I don't know if you could suggest any other process to carry out so that the observium can show us the complete data of the device.

          I remain attentive, greetings.

          msierra Miguel Sierra added a comment - Hello Adam I tried to add the mib as you told me a few days ago, solving the error on 1 of the devices, but not on the second. I don't know if you could suggest any other process to carry out so that the observium can show us the complete data of the device. I remain attentive, greetings.
          landy Mike Stupalov 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>

          landy Mike Stupalov 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>
          adama Adam Armstrong added a comment -

          MIBs aren't really what you think they are, they're not like device drivers, they're more like a dictionary.

          Just adding MIBs won't automatically collect any thing, because there is no standard format for MIBs, a human has to read them and write code to collect the data covered by those MIBs.

          If you can show the location in the MIBs of useful information for us to collect, along with an SNMP walk as was requested by the bot when the ticket was first created, we might be able to add support for these.

          It's possible that these are typical low-end vendor per-model MIBs, which are an absolute nightmare to support because it means a human has to read the  MIB and write code to support every single model. I'm not sure if Linksys does this.

          adama Adam Armstrong added a comment - MIBs aren't really what you think they are, they're not like device drivers, they're more like a dictionary. Just adding MIBs won't automatically collect any thing, because there is no standard format for MIBs, a human has to read them and write code to collect the data covered by those MIBs. If you can show the location in the MIBs of useful information for us to collect, along with an SNMP walk as was requested by the bot when the ticket was first created, we might be able to add support for these. It's possible that these are typical low-end vendor per-model MIBs, which are an absolute nightmare to support because it means a human has to read the  MIB and write code to support every single model. I'm not sure if Linksys does this.
          msierra Miguel Sierra added a comment -

          Thanks for your reply Adam.

          We already have the MIBs downloaded directly from Cisco, I don't know if you could guide us so we can add them to the devices and do a test.

          We carried out a test in another tool called Open Manager and it does allow us to monitor both the CPU and the other resources mentioned above. I don't know if with the MIBs as you mention we will be able to solve the incident, since we want to maintain the monitoring in Observium.

          msierra Miguel Sierra added a comment - Thanks for your reply Adam. We already have the MIBs downloaded directly from Cisco, I don't know if you could guide us so we can add them to the devices and do a test. We carried out a test in another tool called Open Manager and it does allow us to monitor both the CPU and the other resources mentioned above. I don't know if with the MIBs as you mention we will be able to solve the incident, since we want to maintain the monitoring in Observium.
          adama Adam Armstrong added a comment -

          Hi,

          Cisco Small Business switches have generally limited and broken SNMP support.

          Note that these aren't really Cisco switches. They're really just rebadged Linksys switches, and aren't running Cisco IOS.

          If you find something in their SNMP MIBs which is not currently supported, we can add it, but I think most issues with those switches is that they're just terrible, and their SNMP support is terrible.

          Thanks,

          adam.

          adama Adam Armstrong added a comment - Hi, Cisco Small Business switches have generally limited and broken SNMP support. Note that these aren't really Cisco switches. They're really just rebadged Linksys switches, and aren't running Cisco IOS. If you find something in their SNMP MIBs which is not currently supported, we can add it, but I think most issues with those switches is that they're just terrible, and their SNMP support is terrible. Thanks, adam.

          People

            landy Mike Stupalov
            msierra Miguel Sierra
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: