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

Add Packetlight PL2000T CFP Uplink preFEC BER?

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, Poller, Ports
    • None

    Description

      Current Packetlight OS support does not include CFP Uplink preFEC BER (bit error rate).  This is very important to monitor for any degradation in Coherent link quality and operating margin.

      As this is retrieved as a compound value from two OIDs (as Mantissa and Exponent of a scientific notation number).

      The relevant OIDs (within the slOTNCurrentPmTable table) are:

      {{ .1.3.6.1.4.1.4515.1.1.15.2.1.1.6 -  slOTNCurrentPmFecCerMantFE}}

      {{ .1.3.6.1.4.1.4515.1.1.15.2.1.1.7 -  slOTNCurrentPmFecCerExpFE}}

      Which are followed by the corresponding ifIndex of the associated interface.

      Only interfaces of the ifType 'opticalTransport' will have corresponding values in the slOTNCurrentPmTable.

      I've attached the snmptable and walk command output of both the ifTable and slOTNCurrentPmTable tables.  As you can see, index 13157120 in the table has the following values:

      • slOTNCurrentPmFecCerMantFE: 599
      • slOTNCurrentPmFecCerExpFE:  6

      This corresponds to an actual prefFEC BER of 5.99E-4, as per the devices WebUI:

      Please let me know if you want any further test outputs to proceed with this?

       

      Best regards,

      Matt Clancy

       

      Attachments

        Activity

          [OBS-3786] Add Packetlight PL2000T CFP Uplink preFEC BER?

          Thanks Mike - I will follow up with the vendor.

          As it currently is working to get the value at least (although against a not associated interface), is it possible for the values to be graphed still?  It seems like it's polling the instantaneous value but not recording the historical for graphing at the moment?

          Best regards,

          Matt Clancy

          mcslc Matthew Clancy added a comment - Thanks Mike - I will follow up with the vendor. As it currently is working to get the value at least (although against a not associated interface), is it possible for the values to be graphed still?  It seems like it's polling the instantaneous value but not recording the historical for graphing at the moment? Best regards, Matt Clancy

          I think you need to ask Vendor, how possible associate such indexes with correct interface (or better ask for fix this indexes).

          I not found any other ways in this MIB for associations (except ifIndex), see walk from your dump:

          $ grep '.13157120 = ' devel/walks/packetlight-2000t-SL-OTN-MIB.walk
          SL-OTN-MIB::slOTNConfigLineIndex.13157120 = INTEGER: 13157120
          SL-OTN-MIB::slOTNConfigOperationMode.13157120 = Wrong Type (should be INTEGER): Gauge32: 2
          SL-OTN-MIB::slOTNConfigFECEnabled.13157120 = INTEGER: 1
          SL-OTN-MIB::slOTNConfigStuffingEnabled.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNConfigOTUkTIMDetEnabled.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNConfigOTUkDAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigOTUkSAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigOTUkDAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigOTUkSAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigOTUkDAPIReceived.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigOTUkSAPIReceived.13157120 = Hex-STRING: 31 30 2E 32 30 35 2E 35 32 2E 31 37 2F 31 00 00
          SL-OTN-MIB::slOTNConfigODUkTIMDetEnabled.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNConfigODUkDAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigODUkSAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigODUkDAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigODUkSAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
          SL-OTN-MIB::slOTNConfigODUkDAPIReceived.13157120 = Hex-STRING: 00 10 97 C1 FF BD FF EF 44 04 B0 5D CD FF BB 00
          SL-OTN-MIB::slOTNConfigODUkSAPIReceived.13157120 = Hex-STRING: 00 10 97 C1 FF BD FF EF 44 04 B0 5D CD FF BB 00
          SL-OTN-MIB::slOTNConfigOTUkTIMKillEnabled.13157120 = INTEGER: true(1)
          SL-OTN-MIB::slOTNConfigODUkTIMKillEnabled.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNConfigInbandGCC.13157120 = INTEGER: 0
          SL-OTN-MIB::slOTNMsiDisable.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNCurrentPmIndex.13157120 = INTEGER: 13157120
          SL-OTN-MIB::slOTNCurrentPmFecCe.13157120 = INTEGER: 0
          SL-OTN-MIB::slOTNCurrentPmFecCerMant.13157120 = INTEGER: 6
          SL-OTN-MIB::slOTNCurrentPmFecCerExp.13157120 = INTEGER: -4
          SL-OTN-MIB::slOTNCurrentPmFecCerValid.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNCurrentPmFecCerMantFE.13157120 = INTEGER: 627
          SL-OTN-MIB::slOTNCurrentPmFecCerExpFE.13157120 = INTEGER: -6
          SL-OTN-MIB::slOTNCurrentPmFecCerValidFE.13157120 = INTEGER: false(2)
          SL-OTN-MIB::slOTNCurrentPmReset.13157120 = INTEGER: 0
          

          not possible associate with ifdescr or any other type of interface data..

          landy Mike Stupalov added a comment - I think you need to ask Vendor, how possible associate such indexes with correct interface (or better ask for fix this indexes). I not found any other ways in this MIB for associations (except ifIndex), see walk from your dump: $ grep '.13157120 = ' devel/walks/packetlight-2000t-SL-OTN-MIB.walk SL-OTN-MIB::slOTNConfigLineIndex.13157120 = INTEGER: 13157120 SL-OTN-MIB::slOTNConfigOperationMode.13157120 = Wrong Type (should be INTEGER): Gauge32: 2 SL-OTN-MIB::slOTNConfigFECEnabled.13157120 = INTEGER: 1 SL-OTN-MIB::slOTNConfigStuffingEnabled.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNConfigOTUkTIMDetEnabled.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNConfigOTUkDAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigOTUkSAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigOTUkDAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigOTUkSAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigOTUkDAPIReceived.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigOTUkSAPIReceived.13157120 = Hex-STRING: 31 30 2E 32 30 35 2E 35 32 2E 31 37 2F 31 00 00 SL-OTN-MIB::slOTNConfigODUkTIMDetEnabled.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNConfigODUkDAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigODUkSAPIToTransmit.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigODUkDAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigODUkSAPIToExpect.13157120 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SL-OTN-MIB::slOTNConfigODUkDAPIReceived.13157120 = Hex-STRING: 00 10 97 C1 FF BD FF EF 44 04 B0 5D CD FF BB 00 SL-OTN-MIB::slOTNConfigODUkSAPIReceived.13157120 = Hex-STRING: 00 10 97 C1 FF BD FF EF 44 04 B0 5D CD FF BB 00 SL-OTN-MIB::slOTNConfigOTUkTIMKillEnabled.13157120 = INTEGER: true(1) SL-OTN-MIB::slOTNConfigODUkTIMKillEnabled.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNConfigInbandGCC.13157120 = INTEGER: 0 SL-OTN-MIB::slOTNMsiDisable.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNCurrentPmIndex.13157120 = INTEGER: 13157120 SL-OTN-MIB::slOTNCurrentPmFecCe.13157120 = INTEGER: 0 SL-OTN-MIB::slOTNCurrentPmFecCerMant.13157120 = INTEGER: 6 SL-OTN-MIB::slOTNCurrentPmFecCerExp.13157120 = INTEGER: -4 SL-OTN-MIB::slOTNCurrentPmFecCerValid.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNCurrentPmFecCerMantFE.13157120 = INTEGER: 627 SL-OTN-MIB::slOTNCurrentPmFecCerExpFE.13157120 = INTEGER: -6 SL-OTN-MIB::slOTNCurrentPmFecCerValidFE.13157120 = INTEGER: false(2) SL-OTN-MIB::slOTNCurrentPmReset.13157120 = INTEGER: 0 not possible associate with ifdescr or any other type of interface data..

          Hi Mike, 

          Thanks for the update.  On closer inspection, and as you suggest, the preFEC BER seems to be recorded against the, e.g. "Line Interface 200" rather than "SFP Interface 200".  This means you likely can't correlate by ifType 'opticalTransport' as I suggested. 

          The "Line Interface 200" and "SFP Interface 200" possibly should be related interfaces somehow though?  This is a little confusing as the "Line Interface 200" doesn't actually appear up, even though the "SFP Interface 200" is up.

          Let me know if you need any further inputs, or if this is generally good-to-go despite the quirks?

          Best regards,

          Matt Clancy

          mcslc Matthew Clancy added a comment - Hi Mike,  Thanks for the update.  On closer inspection, and as you suggest, the preFEC BER seems to be recorded against the, e.g.  "Line Interface 200" rather than " SFP Interface 200".   This means you likely can't correlate by ifType 'opticalTransport' as I suggested.  The  "Line Interface 200"  and " SFP Interface 200"  possibly should be related interfaces somehow though?  This is a little confusing as the  "Line Interface 200" doesn't actually appear up, even though the  " SFP Interface 200" is up. Let me know if you need any further inputs, or if this is generally good-to-go despite the quirks? Best regards, Matt Clancy

          Support added in r11434.

          But seems as index not correct ifIndex:

          landy Mike Stupalov added a comment - Support added in r11434. But seems as index not correct ifIndex:

          Attached snmpwalk files as per bot request - some error during snmpwalks seen however:

          $ snmpwalk -v2c -c read-only -M .:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp -m +ALL --hexOutputLength=0 -ObentxU 10.205.52.16 .1 > myagent.snmpwalk
          Error in packet.
          Reason: Unknown Error
          Failed object: .1.3.6.1.4.1.4515.1.11.1.2.1.4.0

          [^myagent.snmpwalk.gz]

          mcslc Matthew Clancy added a comment - Attached snmpwalk files as per bot request - some error during snmpwalks seen however: $ snmpwalk -v2c -c read-only -M .:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp -m +ALL --hexOutputLength=0 -ObentxU 10.205.52.16 .1 > myagent.snmpwalk Error in packet. Reason: Unknown Error Failed object: .1.3.6.1.4.1.4515.1.11.1.2.1.4.0 [^myagent.snmpwalk.gz]

          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
            mcslc Matthew Clancy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: