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

Support for Commend WS300

Details

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

    Description

      Hi Guys,

       

      can you add support for Commend WS300 IP Video Endpoints?

      The devices dont give output for  .1.3.6.1.4.1, but they do answer for vendor specific OIDs.

       

      Attachments

        Activity

          [OBS-3460] Support for Commend WS300
          landy Mike Stupalov added a comment -

          Basic support added in r11883.

          Completely not sure about reported statuses (there is no description of possible values ​​anywhere).

          landy Mike Stupalov added a comment - Basic support added in r11883. Completely not sure about reported statuses (there is no description of possible values ​​anywhere).
          landy Mike Stupalov added a comment -

          This is was "Bot" notify

          Anyway, device complete not respond by common ".1.3.6" Oid?

          landy Mike Stupalov added a comment - This is was "Bot" notify Anyway, device complete not respond by common ".1.3.6" Oid?
          FloMeyer Florian Meyer added a comment -

          This is just not true.

          FloMeyer Florian Meyer added a comment - This is just not true.
          landy Mike Stupalov added a comment -

          Hi Florian Meyer, we have not received the additional information requested earlier from you in this issue 'Hi Guys,

           

          can you add support for Commend WS300 IP Video Endpoints?

          The devices dont give output for  .1.3.6.1.4.1, but they do answer for vendor specific OIDs.

           '!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Florian Meyer, we have not received the additional information requested earlier from you in this issue 'Hi Guys,   can you add support for Commend WS300 IP Video Endpoints? The devices dont give output for  .1.3.6.1.4.1, but they do answer for vendor specific OIDs.  '! Issues without your response will be closed within 2 weeks.
          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.

          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
            FloMeyer Florian Meyer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: