Re: [Observium] Juniper SRX4200 and transceivers sensors
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
On 1 Oct 2017, 15:58, at 15:58, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Hi Adam,
You are absolutely right. Very sorry about this, I had a very very short night ;-)
Device’s SNMP stack doesn’t expose that information (see attached). I guess I’m up for another case with $J.
Best regards.
Youssef BENGELLOUN - ZAHR - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr _____________________________________________ Web : prodware.fr
De : observium observium-bounces@observium.org au nom de Adam Armstrong adama@memetic.org Répondre à : Observium observium@observium.org Date : dimanche 1 octobre 2017 à 16:47 À : 'Observium' observium@observium.org Objet : Re: [Observium] Juniper SRX4200 and transceivers sensors
You realise that the poller module isn't where things are discovered, right?
If things don't appear, it's because they're not in any of the places observium looks for them.
Before you post here you should have already verified wether this device actually exposes the sensors you're looking for via SNMP.
I can almost guarantee that they're not, though.
Adam.
Sent from BlueMail
On 1 Oct 2017, at 15:36, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Dear Observium Community,
We just migrated to a brand new SRX4200 cluster and I’m not finding any outputs regarding transceivers’ sensors.
Please find attached results from poller in debug mode for sensors module.
Are we looking again at fault on the vendor side ?
Thank you.
Youssef BENGELLOUN - ZAHR - 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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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
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
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
Hi,
After a lot of patience and a ton load of explanations, here are initial findings :
“I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.”
Best regards.
Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
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
Hello community,
So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 :
“As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab :
{primary:node0} root> show version node0: -------------------------------------------------------------------------- Model: srx4200 Junos: 17.3R1.10 JUNOS Software Release [17.3R1.10]
{primary:node0} root> show snmp mib walk ascii jnxDomCurrentModuleTemperature jnxDomCurrentModuleTemperature.509 = 35 jnxDomCurrentModuleTemperature.510 = 34 jnxDomCurrentModuleTemperature.511 = 0 jnxDomCurrentModuleTemperature.512 = 0 jnxDomCurrentModuleTemperature.513 = 0 jnxDomCurrentModuleTemperature.514 = 0 jnxDomCurrentModuleTemperature.515 = 0 jnxDomCurrentModuleTemperature.516 = 32 jnxDomCurrentModuleTemperature.527 = 0 ” I’m pushing to have it implemented for train code 15.1X49.
Best regards.
Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hi,
After a lot of patience and a ton load of explanations, here are initial findings :
“I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.”
Best regards.
Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
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
And the update :
«Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 »
Best regards.
Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello community,
So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 :
“As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab :
{primary:node0} root> show version node0: -------------------------------------------------------------------------- Model: srx4200 Junos: 17.3R1.10 JUNOS Software Release [17.3R1.10]
{primary:node0} root> show snmp mib walk ascii jnxDomCurrentModuleTemperature jnxDomCurrentModuleTemperature.509 = 35 jnxDomCurrentModuleTemperature.510 = 34 jnxDomCurrentModuleTemperature.511 = 0 jnxDomCurrentModuleTemperature.512 = 0 jnxDomCurrentModuleTemperature.513 = 0 jnxDomCurrentModuleTemperature.514 = 0 jnxDomCurrentModuleTemperature.515 = 0 jnxDomCurrentModuleTemperature.516 = 32 jnxDomCurrentModuleTemperature.527 = 0 ” I’m pushing to have it implemented for train code 15.1X49.
Best regards.
Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hi,
After a lot of patience and a ton load of explanations, here are initial findings :
“I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.”
Best regards.
Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
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
Hi Youssef,
Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed.
KR, Tom
On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote:
And the update :
«Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 »
Best regards.
Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello community, So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : {primary:node0} root> show version node0: -------------------------------------------------------------------------- Model: srx4200 Junos: 17.3R1.10 JUNOS Software Release [17.3R1.10] {primary:node0} root> show snmp mib walk ascii jnxDomCurrentModuleTemperature jnxDomCurrentModuleTemperature.509 = 35 jnxDomCurrentModuleTemperature.510 = 34 jnxDomCurrentModuleTemperature.511 = 0 jnxDomCurrentModuleTemperature.512 = 0 jnxDomCurrentModuleTemperature.513 = 0 jnxDomCurrentModuleTemperature.514 = 0 jnxDomCurrentModuleTemperature.515 = 0 jnxDomCurrentModuleTemperature.516 = 32 jnxDomCurrentModuleTemperature.527 = 0 ” I’m pushing to have it implemented for train code 15.1X49. Best regards. Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » <ybzahr@prodware.fr> a écrit : Hi, After a lot of patience and a ton load of explanations, here are initial findings : “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” Best regards. Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » <ybzahr@prodware.fr> a écrit : 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 :( -NickBENGELLOUN - 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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hello Tom,
Always happy to help. I’ll keep you posted.
Best regards.
Le 10/10/2017 13:29, « observium au nom de Tom Laermans » <observium-bounces@observium.org au nom de tom.laermans@powersource.cx> a écrit :
Hi Youssef,
Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed.
KR, Tom
On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote: > And the update : > > «Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 » > > Best regards. > > > > Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : > > Hello community, > > So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : > > “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : > > {primary:node0} > root> show version > node0: > -------------------------------------------------------------------------- > Model: srx4200 > Junos: 17.3R1.10 > JUNOS Software Release [17.3R1.10] > > {primary:node0} > root> show snmp mib walk ascii jnxDomCurrentModuleTemperature > jnxDomCurrentModuleTemperature.509 = 35 > jnxDomCurrentModuleTemperature.510 = 34 > jnxDomCurrentModuleTemperature.511 = 0 > jnxDomCurrentModuleTemperature.512 = 0 > jnxDomCurrentModuleTemperature.513 = 0 > jnxDomCurrentModuleTemperature.514 = 0 > jnxDomCurrentModuleTemperature.515 = 0 > jnxDomCurrentModuleTemperature.516 = 32 > jnxDomCurrentModuleTemperature.527 = 0 > ” > I’m pushing to have it implemented for train code 15.1X49. > > Best regards. > > > > Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : > > Hi, > > After a lot of patience and a ton load of explanations, here are initial findings : > > “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” > > Best regards. > > > > Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : > > 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 > >
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 > > > > > > > > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
This issue concerns SRX series 4100/4200 :
"I am pushing them for having the fix in D120 . Since there is platform team involved ( as the issue is Platform specific ) they need some time for the analysis of the same."
If all goes well, it should be available by late November.
Best regards.
Le 10 oct. 2017 à 13:29, Tom Laermans tom.laermans@powersource.cx a écrit :
Hi Youssef,
Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed.
KR, Tom
On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote: And the update :
«Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 »
Best regards.
Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello community, So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : {primary:node0} root> show version node0: -------------------------------------------------------------------------- Model: srx4200 Junos: 17.3R1.10 JUNOS Software Release [17.3R1.10] {primary:node0} root> show snmp mib walk ascii jnxDomCurrentModuleTemperature jnxDomCurrentModuleTemperature.509 = 35 jnxDomCurrentModuleTemperature.510 = 34 jnxDomCurrentModuleTemperature.511 = 0 jnxDomCurrentModuleTemperature.512 = 0 jnxDomCurrentModuleTemperature.513 = 0 jnxDomCurrentModuleTemperature.514 = 0 jnxDomCurrentModuleTemperature.515 = 0 jnxDomCurrentModuleTemperature.516 = 32 jnxDomCurrentModuleTemperature.527 = 0 ” I’m pushing to have it implemented for train code 15.1X49. Best regards. Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » <ybzahr@prodware.fr> a écrit : Hi, After a lot of patience and a ton load of explanations, here are initial findings : “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” Best regards. Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » <ybzahr@prodware.fr> a écrit : 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 :( -NickBENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hello,
Update :
« Engineering have provided me a private patch for testing and the issue is fixed on the private patch on my testbed for MIB “jnxDomMib". I am trying to get this patch to port onto the next upcoming release. »
Best regards.
Le 13/10/2017 10:39, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hi,
This issue concerns SRX series 4100/4200 :
"I am pushing them for having the fix in D120 . Since there is platform team involved ( as the issue is Platform specific ) they need some time for the analysis of the same."
If all goes well, it should be available by late November.
Best regards.
> Le 10 oct. 2017 à 13:29, Tom Laermans tom.laermans@powersource.cx a écrit : > > Hi Youssef, > > Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed. > > KR, > Tom > >> On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote: >> And the update : >> >> «Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 » >> >> Best regards. >> >> >> >> Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hello community, >> >> So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : >> >> “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : >> >> {primary:node0} >> root> show version >> node0: >> -------------------------------------------------------------------------- >> Model: srx4200 >> Junos: 17.3R1.10 >> JUNOS Software Release [17.3R1.10] >> >> {primary:node0} >> root> show snmp mib walk ascii jnxDomCurrentModuleTemperature >> jnxDomCurrentModuleTemperature.509 = 35 >> jnxDomCurrentModuleTemperature.510 = 34 >> jnxDomCurrentModuleTemperature.511 = 0 >> jnxDomCurrentModuleTemperature.512 = 0 >> jnxDomCurrentModuleTemperature.513 = 0 >> jnxDomCurrentModuleTemperature.514 = 0 >> jnxDomCurrentModuleTemperature.515 = 0 >> jnxDomCurrentModuleTemperature.516 = 32 >> jnxDomCurrentModuleTemperature.527 = 0 >> ” >> I’m pushing to have it implemented for train code 15.1X49. >> >> Best regards. >> >> >> >> Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hi, >> >> After a lot of patience and a ton load of explanations, here are initial findings : >> >> “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” >> >> Best regards. >> >> >> >> Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> 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 >> >>
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 >> >> >> >> >> >> >> >> >> _______________________________________________ >> observium mailing list >> observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hello,
With good news always comes bad news, it’s basic rule in our jobs. Well, here it is :
“I checked on all SRX HE devices running multiple version , since EM ports are dedicated port the MIB does not fetch details from these ports . This is day 1 design for these MIBs . If you need to include EM interface also , it should be an enhancement request which have to be forwarded via your accounts team .
I checked with engineering and they also confirmed the same as this to be enhancement rather than a bug fix.”
I was right to ask if the MIB could poll *all* ports. In the end, a port is a port. Those guys are just killing me.
So, I’m trying to push this with our SE using an old ER we opened a few years ago, ER56557.
But the MIB will be introduced as planned by late November. At least, I won this battle but not the war… yet !
Best regards.
Le 24/10/2017 07:06, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello,
Update :
« Engineering have provided me a private patch for testing and the issue is fixed on the private patch on my testbed for MIB “jnxDomMib". I am trying to get this patch to port onto the next upcoming release. »
Best regards.
Le 13/10/2017 10:39, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hi,
This issue concerns SRX series 4100/4200 :
"I am pushing them for having the fix in D120 . Since there is platform team involved ( as the issue is Platform specific ) they need some time for the analysis of the same."
If all goes well, it should be available by late November.
Best regards.
> Le 10 oct. 2017 à 13:29, Tom Laermans tom.laermans@powersource.cx a écrit : > > Hi Youssef, > > Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed. > > KR, > Tom > >> On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote: >> And the update : >> >> «Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 » >> >> Best regards. >> >> >> >> Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hello community, >> >> So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : >> >> “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : >> >> {primary:node0} >> root> show version >> node0: >> -------------------------------------------------------------------------- >> Model: srx4200 >> Junos: 17.3R1.10 >> JUNOS Software Release [17.3R1.10] >> >> {primary:node0} >> root> show snmp mib walk ascii jnxDomCurrentModuleTemperature >> jnxDomCurrentModuleTemperature.509 = 35 >> jnxDomCurrentModuleTemperature.510 = 34 >> jnxDomCurrentModuleTemperature.511 = 0 >> jnxDomCurrentModuleTemperature.512 = 0 >> jnxDomCurrentModuleTemperature.513 = 0 >> jnxDomCurrentModuleTemperature.514 = 0 >> jnxDomCurrentModuleTemperature.515 = 0 >> jnxDomCurrentModuleTemperature.516 = 32 >> jnxDomCurrentModuleTemperature.527 = 0 >> ” >> I’m pushing to have it implemented for train code 15.1X49. >> >> Best regards. >> >> >> >> Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hi, >> >> After a lot of patience and a ton load of explanations, here are initial findings : >> >> “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” >> >> Best regards. >> >> >> >> Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> 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 >> >>
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 >> >> >> >> >> >> >> >> >> _______________________________________________ >> observium mailing list >> observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hello community,
D120 included the fix has been released. I haven’t been able to test it againt our production cluster, we need to plan a maintenance window for that, but JTAC did it in their lab and it is now corrected :
“ {primary:node0} root> show version node0: -------------------------------------------------------------------------- Model: srx4200 Junos: 15.1X49-D120.3 JUNOS Software Release [15.1X49-D120.3]
{primary:node0} root> show snmp mib walk ascii jnxDomCurrentModuleTemperature jnxDomCurrentModuleTemperature.509 = 34 jnxDomCurrentModuleTemperature.510 = 33 jnxDomCurrentModuleTemperature.511 = 0 jnxDomCurrentModuleTemperature.512 = 0 jnxDomCurrentModuleTemperature.513 = 0 jnxDomCurrentModuleTemperature.514 = 0 jnxDomCurrentModuleTemperature.515 = 0 jnxDomCurrentModuleTemperature.516 = 31 jnxDomCurrentModuleTemperature.527 = 0 “
I will keep you posted regarding ER development.
Best regards.
Le 25/10/2017 11:49, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello,
With good news always comes bad news, it’s basic rule in our jobs. Well, here it is :
“I checked on all SRX HE devices running multiple version , since EM ports are dedicated port the MIB does not fetch details from these ports . This is day 1 design for these MIBs . If you need to include EM interface also , it should be an enhancement request which have to be forwarded via your accounts team .
I checked with engineering and they also confirmed the same as this to be enhancement rather than a bug fix.”
I was right to ask if the MIB could poll *all* ports. In the end, a port is a port. Those guys are just killing me.
So, I’m trying to push this with our SE using an old ER we opened a few years ago, ER56557.
But the MIB will be introduced as planned by late November. At least, I won this battle but not the war… yet !
Best regards.
Le 24/10/2017 07:06, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hello,
Update :
« Engineering have provided me a private patch for testing and the issue is fixed on the private patch on my testbed for MIB “jnxDomMib". I am trying to get this patch to port onto the next upcoming release. »
Best regards.
Le 13/10/2017 10:39, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit :
Hi,
This issue concerns SRX series 4100/4200 :
"I am pushing them for having the fix in D120 . Since there is platform team involved ( as the issue is Platform specific ) they need some time for the analysis of the same."
If all goes well, it should be available by late November.
Best regards.
> Le 10 oct. 2017 à 13:29, Tom Laermans tom.laermans@powersource.cx a écrit : > > Hi Youssef, > > Thanks for the followups! I'm sure not only you but plenty of others will enjoy the fruits of you getting this fixed. > > KR, > Tom > >> On 10/10/2017 10:53, Youssef BENGELLOUN - ZAHR wrote: >> And the update : >> >> «Thanks for the update. I cannot commit for fix to be implemented on D120, but I will try to get in touch with engineering for possible fix in upcoming release . I have created the PR for your reference : PR 1313109 » >> >> Best regards. >> >> >> >> Le 10/10/2017 09:25, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hello community, >> >> So good news is that JTAC finally understood the issue and advanced TAC has taken over it. They have confirmed that the MIB is implemented on train code 17.3 : >> >> “As a Quick test , I have tested our latest version 17.3 in our lab to see if that have the fix for the SNMP issue . And it worked fine in our lab : >> >> {primary:node0} >> root> show version >> node0: >> -------------------------------------------------------------------------- >> Model: srx4200 >> Junos: 17.3R1.10 >> JUNOS Software Release [17.3R1.10] >> >> {primary:node0} >> root> show snmp mib walk ascii jnxDomCurrentModuleTemperature >> jnxDomCurrentModuleTemperature.509 = 35 >> jnxDomCurrentModuleTemperature.510 = 34 >> jnxDomCurrentModuleTemperature.511 = 0 >> jnxDomCurrentModuleTemperature.512 = 0 >> jnxDomCurrentModuleTemperature.513 = 0 >> jnxDomCurrentModuleTemperature.514 = 0 >> jnxDomCurrentModuleTemperature.515 = 0 >> jnxDomCurrentModuleTemperature.516 = 32 >> jnxDomCurrentModuleTemperature.527 = 0 >> ” >> I’m pushing to have it implemented for train code 15.1X49. >> >> Best regards. >> >> >> >> Le 09/10/2017 16:17, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> Hi, >> >> After a lot of patience and a ton load of explanations, here are initial findings : >> >> “I was quickly able to reproduce the issue in LAB with SRX 4200 with 15.1X49-D80 version. Also checked for any known issue and there is none. I will elevate this to Advanced TAC to validate my findings and open a PR with the Engineering team.” >> >> Best regards. >> >> >> >> Le 03/10/2017 00:02, « Youssef BENGELLOUN - ZAHR » ybzahr@prodware.fr a écrit : >> >> 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 >> >>
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 >> >> >> >> >> >> >> >> >> _______________________________________________ >> observium mailing list >> observium@observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (4)
-
Adam Armstrong -
Nick Schmalenberger -
Tom Laermans -
Youssef BENGELLOUN - ZAHR