Details

    • Add New Device / OS
    • Resolution: Fixed
    • Trivial
    • None
    • Professional Edition
    • OS

    Description

      The CC3000 does have minimum SNMPv2-MIB support, but the "sysName" is note unique per device so you can't add new devices.

       

      SNMPv2-MIB::sysDescr.0 = STRING: FreeCooling Controller, SNMP V1.0
      SNMPv2-MIB::sysObjectID.0 = OID: RFC1155-SMI::enterprises.0
      DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (84832060) 9 days, 19:38:40.60
      SNMPv2-MIB::sysContact.0 = STRING: Dantherm Cooling A/S, Denmark. Phone:+45 96143700
      SNMPv2-MIB::sysName.0 = STRING: CC3000
      SNMPv2-MIB::sysLocation.0 = STRING: Local
      SNMPv2-MIB::sysServices.0 = INTEGER: 79

      Attachments

        1. dantherm.CC3000.snmpwalk
          13 kB
        2. dantherm.mib.php
          8 kB
        3. dantherm.os.php
          2 kB
        4. DANtherm.snmpwalk.T2.txt
          12 kB
        5. DANTHERM-COOLING-MIB.tar.gz
          8 kB

        Activity

          [OBS-3392] Dantherm CC3000 support

          Inactive is a valide status. it is trigged by low temp in room or negative delta temperature between in and outside.

          $type = 'shelterStatus';
          $config['mibs'][$mib]['states'][$type][0] = array('name' => 'Inactive', 'event' => 'exclude');

           

          Since outdoor1Tempr is always valid (for my 5), it will always be skipped.

           'skip_if_valid_exist' => 'temperature->DANTHERM-COOLING-MIB-outdoor1Tempr'
          

          I notice a UI bug with "$config['mibs'][$mib]['ip-address'][] ", if you have no interface mibs, you can't view the IP-address in interface.

          since the fan can be off and is a valid state, and we have the warnings in the load, i don't think we need it redundantly. And it will generate false alarms, with the low warnings. or we need to be able to tie the sensors with a status (this can also be useful for other users where the sensor valid/invalid based on status. like POE).

          $config['mibs'][$mib]['sensor'][] = [
          ..
          'min'                 => -1,
           //'limit_auto'          => FALSE,
           'oid_limit_low'       => 'deadBandRPMf1',
          //'oid_limit_low_warn'  => 'idleRPMf1',
          ..];
          
          

          Nicely done with the

           'oid_add'             => 'fan1OpertdurMin',
           'scale_add'           => 60,
          

          Can it also be add to sensors? so we can add warning if outdoor1 is highere than Shelter (scale_add => -1 )?

          Eideen Torstein Eide added a comment - Inactive is a valide status. it is trigged by low temp in room or negative delta temperature between in and outside. $type = 'shelterStatus' ; $config [ 'mibs' ][ $mib ][ 'states' ][ $type ][0] = array ( 'name' => 'Inactive' , 'event' => 'exclude' );   Since outdoor1Tempr is always valid (for my 5), it will always be skipped. 'skip_if_valid_exist' => 'temperature->DANTHERM-COOLING-MIB-outdoor1Tempr' I notice a UI bug with "$config ['mibs'] [$mib] ['ip-address'] [] ", if you have no interface mibs, you can't view the IP-address in interface. since the fan can be off and is a valid state, and we have the warnings in the load, i don't think we need it redundantly. And it will generate false alarms, with the low warnings. or we need to be able to tie the sensors with a status (this can also be useful for other users where the sensor valid/invalid based on status. like POE). $config[ 'mibs' ][$mib][ 'sensor' ][] = [ .. 'min' => - 1 , //'limit_auto' => FALSE, 'oid_limit_low' => 'deadBandRPMf1' , //'oid_limit_low_warn' => 'idleRPMf1', ..]; Nicely done with the 'oid_add' => 'fan1OpertdurMin' , 'scale_add' => 60 , Can it also be add to sensors? so we can add warning if outdoor1 is highere than Shelter (scale_add => -1 )?

          Support added in r10586.

          Please note I rewritten some parts of code, you need to be careful when update from svn.
          Better to revert self changes and get our (I already keep all sensors which you added).

          I not sure about add additional device, but that should work with my changes (because used different sysName from vendor MIB).

          landy Mike Stupalov added a comment - Support added in r10586. Please note I rewritten some parts of code, you need to be careful when update from svn. Better to revert self changes and get our (I already keep all sensors which you added). I not sure about add additional device, but that should work with my changes (because used different sysName from vendor MIB).

          tnx

          landy Mike Stupalov added a comment - tnx

          Hi 

          I updated the snmpwalk to include the 7 OID from system.

          Eideen Torstein Eide added a comment - Hi  I updated the snmpwalk to include the 7 OID from system.

          Just this is not correct way when ignored uptime/location/sysdescr if it's exist on device.

          landy Mike Stupalov added a comment - Just this is not correct way when ignored uptime/location/sysdescr if it's exist on device.

          Hrm, your snmp walks contain only enterprise part of oids (.1.3.6.1.4.1).
          Can you make additional (system part) walk:

          snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > myagent.snmpwalk

          in latest versions for such cases additionally compared interfaces list/mac. Not sure it's exist on this devices.

          landy Mike Stupalov added a comment - Hrm, your snmp walks contain only enterprise part of oids (.1.3.6.1.4.1). Can you make additional (system part) walk: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > myagent.snmpwalk in latest versions for such cases additionally compared interfaces list/mac. Not sure it's exist on this devices.
          Eideen Torstein Eide added a comment - dantherm.CC3000.snmpwalk
          Eideen Torstein Eide added a comment - dantherm.CC3000.snmpwalk

          is attached.

          Eideen Torstein Eide added a comment - is attached.

          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
            Eideen Torstein Eide
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: