Dear Nick,
Ticket number with the vendor is 2017-1001-0083.
Best regards.
Le 02/10/2017 22:33, « observium au nom de Nick Schmalenberger » <observium-bounces@observium.org au nom de nick@schmalenberger.us> a écrit :
On Mon, Oct 02, 2017 at 01:09:49PM -0700, Nick Schmalenberger wrote: > On Sun, Oct 01, 2017 at 04:18:53PM +0100, Adam Armstrong wrote: > > SRX is less than 30 years old so they haven't had time to implement obscure features like optic sensors yet.. > > > > 😄 > > > > Adam. > > > > Sent from BlueMail > > > I have Juniper SRXs and EXs with both 1g and 10g optics in the > same switch or firewall, and they consistently only expose > sensors from the 10g optics (in JUNIPER-DOM-MIB), this is a > snipping from snmpwalk on a SRX1400: > snmpwalk ... IF-MIB::ifDescr > IF-MIB::ifDescr.505 = STRING: ge-0/0/0 > IF-MIB::ifDescr.506 = STRING: ge-0/0/1 > IF-MIB::ifDescr.507 = STRING: ge-0/0/2 > IF-MIB::ifDescr.508 = STRING: ge-0/0/3 > IF-MIB::ifDescr.509 = STRING: ge-0/0/4 > IF-MIB::ifDescr.510 = STRING: ge-0/0/5 > IF-MIB::ifDescr.511 = STRING: ge-0/0/6 > IF-MIB::ifDescr.512 = STRING: xe-0/0/7 > IF-MIB::ifDescr.513 = STRING: xe-0/0/8 > IF-MIB::ifDescr.514 = STRING: xe-0/0/9 > IF-MIB::ifDescr.515 = STRING: ge-0/0/10 > IF-MIB::ifDescr.516 = STRING: ge-0/0/11 > > snmpwalk ... JUNIPER-DOM-MIB::jnxDomCurrentTable > JUNIPER-DOM-MIB::jnxDomCurrentRxLaserPower.512 = INTEGER: -384 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentRxLaserPower.513 = INTEGER: -161 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentRxLaserPower.514 = INTEGER: -126 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserBiasCurrent.512 = INTEGER: 7838 0.001 mA > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserBiasCurrent.513 = INTEGER: 7874 0.001 mA > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserBiasCurrent.514 = INTEGER: 8142 0.001 mA > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPower.512 = INTEGER: -267 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPower.513 = INTEGER: -214 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentTxLaserOutputPower.514 = INTEGER: -206 0.01 dbm > JUNIPER-DOM-MIB::jnxDomCurrentModuleTemperature.512 = INTEGER: 46 Celsius (degrees C) > JUNIPER-DOM-MIB::jnxDomCurrentModuleTemperature.513 = INTEGER: 48 Celsius (degrees C) > JUNIPER-DOM-MIB::jnxDomCurrentModuleTemperature.514 = INTEGER: 46 Celsius (degrees C) > > From the JUNOS command line I know that ge-0/0/11 does have all > the needed sensors. I also have a EX4600 that has mixed 1g and > 10g with the same behavior. I think its pretty annoying too so I > hope your support case helps this be improved :) Let me know if > theres a case number I can tell to my vendor also. Thanks. > -Nick
Someone in #juniper pointed me to this thread https://puck.nether.net/pipermail/juniper-nsp/2012-April/022969.html and I also found https://thwack.solarwinds.com/thread/113303 about this issue. Apparently JUNIPER-DOM-MIB was originally written ONLY for XFP transceivers:
38 DESCRIPTION 39 "Change XFP references to generic SFF in descriptions. Add 40 DOM lane table." 41 REVISION "200912230000Z" 42 DESCRIPTION 43 "Initial revision."
Despite apparently search/replacing XFP with SFF in the MIB, it doesn't actually work on SFP transceivers :( -Nick
BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium