Observium using jnxDomCurrent instead of jnxDomCurrentLane on some optics

100G and 400G ZR Optics duplication of due to discovery in two MIBs.

Some background:

We recently have had open a ticket with Juniper Support regarding this, 

with optics like :

  Media Code     : 100GBASE-ZR (Clause 154)

  Media Code     : ZR-400-OFEC-16QAM

We reported to juniper that values, such as 'TX Bias' from the JUNIPER-IFOPTICS-MIB does not return a value, but Observium is able to retrieve the thresholds.

After some further investigation and back and forth on the ticket Juniper has confirmed to us that JUNIPER-IFOPTICS-MIB is supposedly not supported on the PTX device we have and we should instead be using the JUNIPER-DOM-MIB.

However the problem we current see is as such, take example et-0/1/2 Interface,

We have 2xTX-Bias entries, one from each mib as above.

JUNIPER-IFOPTICS-MIBjnxPMCurTxLaserBiasCurrent517, reports a value 0.22A perfect, but doesn't have any thresholds listed, just infinity symbol.

 JUNIPER-DOM-MIBjnxDomCurrentTxLaserBiasCurrent517,, doesn't report a value, just 0A, but does report a threshold. 

To me it looks like Observium almost needs to be aware of ZR optic's having lanes and instead make sure it's using 

 jnxDomCurrentLaneTxLaserBiasCurrent    0.001 mAInteger32    .1.3.6.1.4.1.2636.3.60.1.2.1.1.7

Rather than what it's currently using:

 jnxDomCurrentTxLaserBiasCurrent    0.001 mAInteger32    .1.3.6.1.4.1.2636.3.60.1.1.1.1.6

PIC Information, Optics impacted by this issue is 2,3,6,8,9,10,11. This is on fpc-slot 0, pic-slot 1.

PIC port information:
                         Fiber                    Xcvr vendor       Wave-                     Xcvr          JNPR     MSA
  Port Cable type        type  Xcvr vendor        part number       length                    Firmware      Rev      Version
  0    400G-AOC 3M       MM    JUNIPER-2H3        740-090165        850 nm                    1.3           REV 01   CMIS 3.0     
  1    400G-AOC 3M       MM    JUNIPER-2H3        740-090165        850 nm                    1.3           REV 01   CMIS 3.0     
  2    400G-ZR-M         SM    JUNIPER-2E1        740-157138        1528.77 nm - 1567.13 nm   1.3           REV 01   CMIS 5.1     
  3    400G-ZR-M         SM    JUNIPER-2E1        740-157138        1528.77 nm - 1567.13 nm   1.3           REV 01   CMIS 5.1     
  6    4X10GBASE LR      SM    JUNIPER-INNO       TR-IQ13L-NJ4      1307.5 nm                 0.0           REV 02   SFF-8636 ver 2.7
  8    400G-ZR-M         SM    JUNIPER-2E1        740-157138        1528.77 nm - 1567.13 nm   1.3           REV 01   CMIS 5.1     
  9    400G-ZR-M         SM    JUNIPER-2E1        740-157138        1528.77 nm - 1567.13 nm   1.3           REV 01   CMIS 5.1     
  10   400G-LR4-10KM     SM    JUNIPER-1G2        740-096176        1301 nm                   0.15          REV 01   CMIS 5.0     
  11   100G-ZR           SM    JUNIPER-1A1        740-172665        1528.77 nm - 1567.13 nm   2.6           REV 01   CMIS 5.2     

Observium Version:Observium    26.4.14752 (rolling) (21st April 2026)

The main one to fix is TX Bias, since RX Power and TX Power is ok from the JUNIPER-DOM-MIB currently, but it would be nice to be able to still have the JUNIPER-IFOPTICS-MIB enabled to still keep the data for Carrier Frequency Offset, OSNR and SNR, which seems ok, but then hide the duplicate entries we have from IFOPTICS-MIB for RX power and Tx power.

Then also hiding DOM and Voltage sensors, since both are working ok for both thresholds and values currently.

I've attached the walk of the MIB in question, screenshot of an example of one port et-0/1/2 with snmpIndex 517.

Regards,

Luke.