Details

    • Improvement
    • Resolution: Done
    • Major
    • None
    • None
    • Discovery
    • None

    Description

      Hi all,

      In the past OBS-1089 we have requested support to SmartOptics M-series devices, which was implemented and we can confirm all was and is supported very neatly.

      Now we have acquired new SmarOptics devices DCP series [5.3.2]:

      SmartOptics DCP-2
      SmartOptics DCP-M40-PAM4-ZR

      We noticed other tickets requesting support for the DCP series, but as we added these into Observium; support seems to be a bit limited for both; e.g: no PSU / No Fans / DWDM doesn't have light levels / etc

      Would it be possible to add more support for the DCP series?

      Attached MIBs (provided by smartoptics) and snmpwalk , do let us know whatever might be needed and we will gladly help.

      Thank you all for your work!

      All the best.

      Attachments

        1. DCP-2.txt
          107 kB
        2. DCP-5.3_MIB_Description_A.pdf
          422 kB
        3. DCP-M40-PAM4-ZR.txt
          174 kB
        4. myagent.snmpwalk.DCP-2
          126 kB
        5. myagent.snmpwalk.DCP-M40
          200 kB

        Issue Links

          Activity

            [OBS-3609] SmartOptics DCP series support

            Just reread all snmp dumps available for this DCP platforms (DCP-2, DCP-M40-PAM4-ZR, DCP-M40-PAM4-ER+).

            We already added support for all possible sensors.

            landy Mike Stupalov added a comment - Just reread all snmp dumps available for this DCP platforms (DCP-2, DCP-M40-PAM4-ZR, DCP-M40-PAM4-ER+). We already added support for all possible sensors.

            Hi. Please let me know if you need any help. I can get you what ever snmpwalk you need. 

             

            mariuswehmer Marius Wehmer added a comment - Hi. Please let me know if you need any help. I can get you what ever snmpwalk you need.   

            Observium Team,
            just an additional info we got from SmartOptics; as we found no MIB 'nor OID for ENVMON as there is in MSERIES, we opened a ticket and they informed us the ENVMON mib is not yet implemented for the DCP series and its currently roadmapped for release. 
            As a result it won't be possible via oid poll to get the chassis temp/fans/psus. 
            Nevertheless there is a lot of useful info that can be added to better support these DCP units.
            Let us know whatever might be needed.

            pveloso Paulo Veloso added a comment - Observium Team, just an additional info we got from SmartOptics; as we found no MIB 'nor OID for ENVMON as there is in MSERIES, we opened a ticket and they informed us the ENVMON mib is not yet implemented for the DCP series and its currently roadmapped for release.  As a result it won't be possible via oid poll to get the chassis temp/fans/psus.  Nevertheless there is a lot of useful info that can be added to better support these DCP units. Let us know whatever might be needed.

            +1 Seeking for better support of this devices If you require more snmpwalks, let me know. We can provide some too.

            dklimek Denis Klimek added a comment - +1 Seeking for better support of this devices If you require more snmpwalks, let me know. We can provide some too.

            Hi all, 

            Vendor supplied us with some more info, relaying as it may prove useful for DCP implementation. 
            tables.xlsx where all indexes are visible for dcpInterface and dcpLinkview.
            DCP-5.3_MIB_Description_A.pdf > DCP MIB description document

            pveloso Paulo Veloso added a comment - Hi all,  Vendor supplied us with some more info, relaying as it may prove useful for DCP implementation.  tables.xlsx where all indexes are visible for  dcpInterface  and  dcpLinkview . DCP-5.3_MIB_Description_A.pdf > DCP MIB description document

            added:
            myagent.snmpwalk.DCP-2
            myagent.snmpwalk.DCP-M40

            pveloso Paulo Veloso added a comment - added: myagent.snmpwalk.DCP-2 myagent.snmpwalk.DCP-M40

            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
              pveloso Paulo Veloso
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: