Prodware France
T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
Hi,
Here is JTAC’s initial feedback :
“Thanks for the update , I do understand this is not a conventional way of doing it . But to give you a simple fix in a short
time . This is as good as reading the output from any MIB OID ( whether its “jnxOperatingDescr” or “ jnxOperatingStat” ) . This is not a final product as we will try to implement this as a “jnxOperatingStat” .
I will pass on the feedback to the engineering on this . Please let us know what the NMS development is looking for . Does the RPM have to include on the “jnxOperatingStat” or we need to have another
OID for the same ? ( Just getting some feedback ).”
So, where would you have this implemented ?
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 : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : mercredi 28 mars 2018 à 10:12
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Dear Observium Community,
That is absolutely correct, I didn’t pay attention to how crappy it is.
Let me feed that back to them.
Best regards.
De : observium <observium-bounces@observium.org> au nom de Tom Laermans <tom.laermans@powersource.cx>
Répondre à : Observium <observium@observium.org>
Date : mercredi 28 mars 2018 à 09:44
À : "observium@observium.org" <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Oh man, technically this is worse than not having the rpm at all! Now your description will update every 5 minutes and you still won't have rpm graphs.
Tom
On 3/28/2018 9:40 AM, Adam Armstrong wrote:
God, this is so dumb. Why would you put this information in the description? Are they expecting everyone who wants to use this information to parse this out?
It's super great that they 'solve' one mistake by making another one.
adam.
------ Original Message ------
From: "Youssef BENGELLOUN - ZAHR" <ybzahr@prodware.fr>
To: "Observium" <observium@observium.org>
Sent: 2018-03-28 08:07:18
Subject: Re: [Observium] SRX4200 FAN status missing
Hi,
Update :
« FYI , engineering have included the RPM status on the ‘jnxOperatingDescr’ MIB entity .Here is the output. :
root@cd-forge6> show snmp mib walk jnxOperatingDescr
jnxOperatingDescr.1.1.0.0 = midplane
jnxOperatingDescr.2.1.1.0 = Power Supply 0 @ 0/0/*
jnxOperatingDescr.4.1.1.0 = Fan Tray 0 Fan 0 [RPM: 4518]
jnxOperatingDescr.4.2.1.0 = Fan Tray 1 Fan 0 [RPM: 4603]
jnxOperatingDescr.4.3.1.0 = Fan Tray 2 Fan 0 [RPM: 4623]
jnxOperatingDescr.4.4.1.0 = Fan Tray 3 Fan 0 [RPM: 4703]
jnxOperatingDescr.7.1.0.0 = FPC: FEB @ 0/*/*
jnxOperatingDescr.8.1.1.0 = PIC: 12x1G-T-4x1G-SFP-4x10G @ 0/0/*
jnxOperatingDescr.9.1.0.0 = Routing Engine
jnxOperatingDescr.9.1.1.0 = USB Hub
Please let us know if you have any concerns . I am trying to get this done on D140 . »
I’m still waiting on the exact release number that will include this fix, possibly in a service release in between 15.1X49-D130 et D140.
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 : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : mardi 20 mars 2018 à 10:34
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Hello community,
So, 15.1X49-D130 has been releases. I just tested it againt a vSRX cluster and everything related to FAN has been corrected but RPM speed :
{primary:node0}
root@fw01-tpt-par02> show snmp mib walk jnxFruName
jnxFruName.7.1.0.0 = node0 FPC: FPC @ 0/*/*
jnxFruName.7.2.0.0 = node1 FPC: FPC @ 0/*/*
jnxFruName.8.1.1.0 = node0 PIC: VSRX DPDK GE @ 0/0/*
jnxFruName.8.2.1.0 = node1 PIC: VSRX DPDK GE @ 0/0/*
jnxFruName.9.1.0.0 = node0 Routing Engine
jnxFruName.9.2.0.0 = node1 Routing Engine
{primary:node0}
root@fw01-tpt-par02> show snmp mib walk jnxOperatingDescr
jnxOperatingDescr.1.1.0.0 = node0 midplane
jnxOperatingDescr.1.2.0.0 = node1 midplane
jnxOperatingDescr.7.1.0.0 = node0 FPC: FPC @ 0/*/*
jnxOperatingDescr.7.2.0.0 = node1 FPC: FPC @ 0/*/*
jnxOperatingDescr.8.1.1.0 = node0 PIC: VSRX DPDK GE @ 0/0/*
jnxOperatingDescr.8.2.1.0 = node1 PIC: VSRX DPDK GE @ 0/0/*
jnxOperatingDescr.9.1.0.0 = node0 Routing Engine
jnxOperatingDescr.9.2.0.0 = node1 Routing Engine
{primary:node0}
root@fw01-tpt-par02> show snmp mib walk jnxFruState
jnxFruState.7.1.0.0 = 6
jnxFruState.7.2.0.0 = 6
jnxFruState.8.1.1.0 = 6
jnxFruState.8.2.1.0 = 6
jnxFruState.9.1.0.0 = 6
jnxFruState.9.2.0.0 = 6
{primary:node0}
root@fw01-tpt-par02> show snmp mib walk jnxOperatingState
jnxOperatingState.1.1.0.0 = 2
jnxOperatingState.1.2.0.0 = 2
jnxOperatingState.7.1.0.0 = 2
jnxOperatingState.7.2.0.0 = 2
jnxOperatingState.8.1.1.0 = 2
jnxOperatingState.8.2.1.0 = 2
jnxOperatingState.9.1.0.0 = 2
jnxOperatingState.9.2.0.0 = 2
RLI 38511, which will fix FAN RPM speed, should be included in D140 (and other major releases like 17.3 and 17.4).
If you need me to provide more traces, I will be happy to do that.
Best regards.
De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : mardi 13 février 2018 à 10:26
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Hello community,
Here are is a little update regarding both issues :
- Regarding FAN state :
“The fix will be included on D130. But the release have been pushed to Mid-March dues to some blocker. This version is a major bug fix version on 15.1X49 Train. So they are trying to include all the bug fixes till date on D130. ”
- Regarding FAN RPM inclusion :
“Engineering have open an RLI for this requirement : RLI 38511.
They also have a prototype and its been tested. They are trying to implement on D140 release as of now. It may change based on approvals and other internal. But as per our priority, they made the blocker for D140.”
If you have access to your Juniper SEs, please have them push for this one.
So all in all, things are moving slowly but surely.
Best regards.
De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : vendredi 2 février 2018 à 08:20
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Hello community,
Here is a little update regarding this topic :
“To Add a Quick note . Engineering is opening a feature PR to add the RPM details to the SNMP module . It will be fixed in upcoming releases ( not in D130 ) on all the New gen Platforms . I will keep you posted on the progress . Our current issue is committed on D130 .”
So, yet again, I can only deplore that people aren’t connecting dots on their own.
On the bright side, this will be fixed for all of us at some point.
Best regards.
De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : lundi 29 janvier 2018 à 09:41
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Hello community,
Here is a little update regarding this topic :
I have pushing JTAC and it’s finally payed off. Fix has been included in the following train codes : 15.1X49 (starting release D130), 17.3 and 17.4.
Here is what’s been fixed :
“Currently we have the Operating status and state of the FAN as in the enterprise MIB . Here is the output :
root@gland04> show snmp mib walk jnxFruName
jnxFruName.2.1.1.0 = Power Supply 0 @ 0/0/*
jnxFruName.2.1.2.0 = Power Supply 1 @ 0/1/*
jnxFruName.4.1.1.1 = Fan Tray 0 Fan 0
jnxFruName.4.1.1.2 = Fan Tray 0 Fan 1
jnxFruName.4.1.2.1 = Fan Tray 1 Fan 0
jnxFruName.4.1.2.2 = Fan Tray 1 Fan 1
jnxFruName.4.1.3.1 = Fan Tray 2 Fan 0
jnxFruName.4.1.3.2 = Fan Tray 2 Fan 1
jnxFruName.4.1.4.1 = Fan Tray 3 Fan 0
jnxFruName.4.1.4.2 = Fan Tray 3 Fan 1
jnxFruName.7.1.0.0 = FPC: FEB @ 0/*/*
jnxFruName.8.1.1.0 = PIC: 8x10G-SFP @ 0/0/*
jnxFruName.9.1.0.0 = Routing Engine
jnxFruName.9.1.1.0 = USB Hub
root@gland04> show snmp mib walk jnxOperatingDescr
jnxOperatingDescr.1.1.0.0 = midplane
jnxOperatingDescr.2.1.1.0 = Power Supply 0 @ 0/0/*
jnxOperatingDescr.4.1.1.1 = Fan Tray 0 Fan 0
jnxOperatingDescr.4.1.1.2 = Fan Tray 0 Fan 1
jnxOperatingDescr.4.1.2.1 = Fan Tray 1 Fan 0
jnxOperatingDescr.4.1.2.2 = Fan Tray 1 Fan 1
jnxOperatingDescr.4.1.3.1 = Fan Tray 2 Fan 0
jnxOperatingDescr.4.1.3.2 = Fan Tray 2 Fan 1
jnxOperatingDescr.4.1.4.1 = Fan Tray 3 Fan 0
jnxOperatingDescr.4.1.4.2 = Fan Tray 3 Fan 1
jnxOperatingDescr.7.1.0.0 = FPC: FEB @ 0/*/*
jnxOperatingDescr.8.1.1.0 = PIC: 8x10G-SFP @ 0/0/*
jnxOperatingDescr.9.1.0.0 = Routing Engine
jnxOperatingDescr.9.1.1.0 = USB Hub
root@gland04> show snmp mib walk jnxFruState
jnxFruState.2.1.1.0 = 6
jnxFruState.2.1.2.0 = 2
jnxFruState.4.1.1.1 = 6
jnxFruState.4.1.1.2 = 6
jnxFruState.4.1.2.1 = 6
jnxFruState.4.1.2.2 = 6
jnxFruState.4.1.3.1 = 6
jnxFruState.4.1.3.2 = 6
jnxFruState.4.1.4.1 = 6
jnxFruState.4.1.4.2 = 6
jnxFruState.7.1.0.0 = 6
jnxFruState.8.1.1.0 = 6
jnxFruState.9.1.0.0 = 6
jnxFruState.9.1.1.0 = 6
root@gland04> show snmp mib walk jnxOperatingState
jnxOperatingState.1.1.0.0 = 2
jnxOperatingState.2.1.1.0 = 2
jnxOperatingState.4.1.1.1 = 2
jnxOperatingState.4.1.1.2 = 2
jnxOperatingState.4.1.2.1 = 2
jnxOperatingState.4.1.2.2 = 2
jnxOperatingState.4.1.3.1 = 2
jnxOperatingState.4.1.3.2 = 2
jnxOperatingState.4.1.4.1 = 2
jnxOperatingState.4.1.4.2 = 2
jnxOperatingState.7.1.0.0 = 2
jnxOperatingState.8.1.1.0 = 2
jnxOperatingState.9.1.0.0 = 2
jnxOperatingState.9.1.1.0 = 2”
Regarding FAN RPM speed, they are still checking but it seems that no MIB exists for this. I’m still waiting for a feedback from escalation to engineering.
Please be advised that tentative release date for 15.1X49-D130 is currently set for mid-february.
I’ll keep you posted on the fly.
Best regards.
De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : mercredi 29 novembre 2017 à 09:34
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Little update regarding this topic.
Regarding FAN sensors, PR 1324161 has been issued and the SRX platform team is working on a fix for the next patch release. I believe it is due by early January, but no commitment yet.
Regarding Chassis / CPU sensors, a PR will be filled by our SE in order to revamp MIBs for the newest hardware generations.
I will keep you updated.
Best regards.
De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : lundi 27 novembre 2017 à 09:34
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Hi Adam,
You are absolutely correct. There is nothing you can do here as JTAC confirmed MIB currently implemented MIBs can’t be used to retrieve individual components sensors per card.
They have acknowledged that MIBs need updating / revamping to be fully able to monitor new-gen hardware.
At this stage, the only thing I can do is ask for an ER and track the development of this for both :
- Chassis sensors,
- CPU sensors,
- FAN sensors,
I’ll update you with my progress.
Best regards.
De : observium <observium-bounces@observium.org> au nom de Adam Armstrong <adama@observium.org>
Répondre à : Observium <observium@observium.org>
Date : dimanche 26 novembre 2017 à 11:28
À : "observium@observium.org" <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing
Your device is only exposing two temperature sensors in SNMP. They are both being detected and polled.
If you find any other sensors, we can add them, but the sensor you are referring to is not a new sensor, it is just node0 routing engine.
adam.
Adam Armstrong
Managing Director & Lead Architect
Observium Limited
On 2017-11-26 10:21:52, Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr> wrote:
Hello Mike,
So how come I can’t see rear-chassis Temp ?
Best regards.
Le 26 nov. 2017 à 11:19, Mike Stupalov <mike@observium.org> a écrit :This OIDs already polled in observium, read 4 mails before..
jnxOperatingDescr.9.1.0.0 = node0 Routing Engine
jnxOperatingDescr.9.2.0.0 = node1 Routing Engine
jnxOperatingTemp.9.1.0.0 = 29
jnxOperatingTemp.9.2.0.0 = 21
Youssef BENGELLOUN - ZAHR wrote:
Hello,
Ok, it is aligned with what JTAC said (see attached).
Basically, old MIBs covering old gen hardware have been re-used for new gen hardware. So, it needs revamping in order to take into consideration all the new components.
In regards with chassis temp, Observium already polls values for Front-chassis temp. Rear-chassis temp can also be polled using the following OID :
SRX4200 :
{primary:node0}
root> show snmp mib walk jnxOperatingDescr
jnxOperatingDescr.1.1.0.0 = node0 midplane
jnxOperatingDescr.2.1.1.0 = node0 Power Supply 0 @ 0/0/*
jnxOperatingDescr.2.1.2.0 = node0 Power Supply 1 @ 0/1/*
jnxOperatingDescr.7.1.0.0 = node0 FPC: FEB @ 0/*/*
jnxOperatingDescr.8.1.1.0 = node0 PIC: 8x10G-SFP @ 0/0/*
jnxOperatingDescr.9.1.0.0 = node0 Routing Engine
jnxOperatingDescr.9.1.1.0 = node0 USB Hub
{primary:node0}
root> show snmp mib walk jnxOperatingTable | match temp
jnxOperatingTemp.1.1.0.0 = 0
jnxOperatingTemp.2.1.1.0 = 0
jnxOperatingTemp.2.1.2.0 = 0
jnxOperatingTemp.7.1.0.0 = 0
jnxOperatingTemp.8.1.1.0 = 0
jnxOperatingTemp.9.1.0.0 = 31 ⇐
jnxOperatingTemp.9.1.1.0 = 0
{primary:node0}
root> show chassis routing-engine | match te
Temperature 31 degrees C / 87 degrees F
SRX5800 :
{primary:node1}
root@F07-01> show snmp mib walk jnxOperatingDescr | match engine
jnxOperatingDescr.9.1.0.0 = node0 Routing Engine 0
jnxOperatingDescr.9.2.0.0 = node0 Routing Engine 1
jnxOperatingDescr.9.3.0.0 = node1 Routing Engine 0
jnxOperatingDescr.9.4.0.0 = node1 Routing Engine 1
{primary:node1}
root@F07-01> show snmp mib walk jnxOperatingTable | match temp | match 9
jnxOperatingTemp.9.1.0.0 = 32 ⇐
jnxOperatingTemp.9.2.0.0 = 0
jnxOperatingTemp.9.3.0.0 = 34 ⇐
jnxOperatingTemp.9.4.0.0 = 0
{primary:node1}
root@F07-01> show chassis routing-engine | match temp
Temperature 32 degrees C / 89 degrees F
CPU temperature 29 degrees C / 84 degrees F
Temperature 34 degrees C / 93 degrees F
CPU temperature 30 degrees C / 86 degrees F
I’ll keep you updated regarding FAN (state / RPM speed) advancements.
Have a nice WE.
Best regards.
Le 25/11/2017 13:28, « observium au nom de Mike Stupalov » <observium-bounces@observium.org au nom de mike@observium.org> a écrit :
Youssef BENGELLOUN - ZAHR wrote:
Hello Mike,
In regards to what I just learned from JTAC, that is normal.
What about the rest of the missing sensors (back chassis temp, CPU temp) ?
I said exactly about sensors too!
No such sensors in walk output!..
Best regards.
Le 25 nov. 2017 à 11:59, Mike Stupalov <mike@observium.org
<mailto:mike@observium.org>> a écrit :
Ok, I re-read full walk for your device
and still not found any additional sensors with Fans and Temps (except
those already discussed).
Youssef BENGELLOUN - ZAHR wrote:
Hello community,
Regarding the FAN sensors state (status / speed), JTAC confirmed MIB
are missing for the newest hardware gen. They have opened a PR
1324161 to track it (see attached).
That leaves us with the rest of the missing sensors :
- Back chassis temp
- CPU temp
Mike, were you able to analyze the traces I sent you ?
Best regards.
Le 24/11/2017 09:31, « Youssef BENGELLOUN - ZAHR »
<ybzahr@prodware.fr <mailto:ybzahr@prodware.fr>> a écrit :
Hello Mike,
Your last email didn’t mention that, doesn’t matter.
Requested outputs can be found here :
https://dl.prodware.org/zljh (password : observium)
Please note that for the second OID, device times out :
root@prod-monit-002:/opt/observium# snmpbulkwalk -v 2c -c XYZ -On
fw01-par01 .1.3.6.1.4.1.2636 > snmpbulkwalk-1361412636.txt
Timeout: No Response from fw01-par01
Waiting for your feedback.
Best regards.
Le 24/11/2017 08:16, « observium au nom de Mike Stupalov »
<mailto:observium-bounces@observium.org> au nom de
mike@observium.org <mailto:mike@observium.org>> a écrit :
Youssef BENGELLOUN - ZAHR wrote:
Hello Mike,
What is your take on this ?
About what?
You did not send the information I wrote (please re-read my
previous mail).
...
Pls send me another full walk from device, I will try to find
if here
exist another Oids with Temp.
2 commands:
snmpbulkwalk -v2c -c <community> -On <host> .1.3.6.1.2.1
snmpbulkwalk -v2c -c <community> -On <host> .1.3.6.1.4.1.2636
Best regards.
Le 23 nov. 2017 à 10:57, Mike Stupalov <mike@observium.org
<mailto:mike@observium.org>> a écrit :
Wheel..
Youssef BENGELLOUN - ZAHR wrote:
Hello Adam,
It appears I got mixed up copying the wrong email output. That is
what
happens when you do it while you are mobile and in between things.
My bad.
So let’s take a step back here :
_1/ regarding CPU temps :_
You are right about those two objects
(.1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0.0 /
.1.3.6.1.4.1.2636.3.1.13.1.7.9.2.0.0), they are being queried
correctly and match with Chassis Temp1 - Front :
What is missing here are the following highlighted entries in
Yellow :
root@fw01-par01> show chassis environment
node0:
--------------------------------------------------------------------------
Class Item Status Measurement
Power FPC 0 Power Supply 0 OK
FPC 0 Power Supply 1 OK
Temp System Temp1 - Front OK 30 degrees C / 86
degrees F
System Temp2 - Back OK 40 degrees C /
104 degrees F
CPU0 Temp OK 70 degrees C /
158 degrees F
CPU1 Temp OK 61 degrees C /
141 degrees F
Fans FPC 0 Fan Tray 0 OK Spinning at
normal speed
FPC 0 Fan Tray 1 OK Spinning at normal
speed
FPC 0 Fan Tray 2 OK Spinning at normal
speed
FPC 0 Fan Tray 3 OK Spinning at normal
speed
I believe the rest of those entries can be found in the same MIB.
If I
poll the whole MIB, I do get results (see attached file). Is that
something you can add on your end ?
Ok, I not see "CPUX Temp" entries inside jnxOperatingTemp Oid,
here only:
jnxOperatingDescr.9.1.0.0 = node0 Routing Engine
jnxOperatingDescr.9.2.0.0 = node1 Routing Engine
jnxOperatingTemp.9.1.0.0 = 29
jnxOperatingTemp.9.2.0.0 = 21
which I not sure correctly corresponded with system temp X, since here
different values against from device CLI.
Another temp sensors which I see:
jnxFruName.9.1.0.0 = node0 Routing Engine
jnxFruName.9.2.0.0 = node1 Routing Engine
jnxFruTemp.9.1.0.0 = 30
jnxFruTemp.9.2.0.0 = 21
jnxFruType.9.1.0.0 = routingEngine
jnxFruType.9.2.0.0 = routingEngine
but this is exactly same as in jnxOperatingTemp.
Pls send me another full walk from device, I will try to find if here
exist another Oids with Temp.
2 commands:
snmpbulkwalk -v2c -c <community> -On <host> .1.3.6.1.2.1
snmpbulkwalk -v2c -c <community> -On <host> .1.3.6.1.4.1.2636
_2/ regarding FAN status / spinning speed :_
I was able to confirm with JTAC the correct MIB, it can be found
here :
I tried with jnxSRX4200SlotFan or 1.3.6.1.4.1.2636.1.1.2.2.143.4, I
don’t get any answers from the device :
root@prod-monit-002:~# snmpwalk -v 2c -c asp fw01-par01
1.3.6.1.4.1.2636.1.1.2.2.143.4
SNMPv2-SMI::enterprises.2636.1.1.2.2.143.4 = No Such Object available
on this agent at this OID
Or
root@fw01-par01> show snmp mib walk ascii jnxSRX4200SlotFan
root@fw01-par01> show snmp mib walk ascii
1.3.6.1.4.1.2636.1.1.2.2.143.4
I’m having JTAC check the status of the MIB implantation. I’ll keep
you updated.
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 <http://prodware.fr> <http://prodware.fr>
<http://twitter.com/Prodware/> <http://www.facebook.com/Prodware/>
*De : *observium <observium-bounces@observium.org
<mailto:observium-bounces@observium.org>> au nom de Adam
Armstrong <adama@observium.org <mailto:adama@observium.org>
*Répondre à : *Observium <observium@observium.org
*Date : *mercredi 22 novembre 2017 à 22:47
*À : *"observium@observium.org <mailto:observium@observium.org>
*Objet : *Re: [Observium] SRX4200 FAN status missing
Both of those sensors are polled:
CMD[/usr/bin/snmpget -v2c -c *** -Pu -OQUsn -M /opt/observium/mibs
'udp':'fw01-par01':'161' .1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0.0
.1.3.6.1.4.1.2636.3.1.13.1.7.9.2.0.0]
CMD EXITCODE[0]
CMD RUNTIME[0.0178s]
STDOUT[
.1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0.0 = 29
.1.3.6.1.4.1.2636.3.1.13.1.7.9.2.0.0 = 21
]
SNMP STATUS[TRUE]
DescrClass
TypeOrigin
ValueEvent
Last Changed
node0 Routing Engine temperaturejunos
snmp29C
ok2017-02-02 11:40:44
node1 Routing Engine temperaturejunos
snmp21C
ok2017-10-01 07:00:02
adam.
Adam Armstrong
Managing Director & Lead Architect
Observium Limited
On 2017-11-22 21:43:53, Youssef BENGELLOUN - ZAHR
<mailto:ybzahr@prodware.fr>> wrote:
I’m not seeing them in the device page.
Moreover, no mention at all in the poller output in debug output I
provided with my initial email.
What kind of trace do you want me to run ?
Best regards.
Le 22 nov. 2017 à 22:22, Adam Armstrong <adama@observium.org
<mailto:adama@observium.org>> a écrit :
The process of collecting temperature sensors from this table
certainly works for me.
The only requirement in the code seems to be that the value
returned isn't zero.
Are you /sure/ these sensors aren't being discovered?
adam.
Adam Armstrong
CEO & Lead Architect
Observium Limited
On 2017-11-22 21:14:23, Youssef BENGELLOUN - ZAHR
<mailto:ybzahr@prodware.fr>> wrote:
CPUs temps (2x units) from race node :
root@fw01-par01> show chassis environment
node0:
--------------------------------------------------------------------------
Class Item Status Measurement
Power FPC 0 Power Supply 0 OK
FPC 0 Power Supply 1 OK
Temp System Temp1 - Front OK 29 degrees
C / 84 degrees F
System Temp2 - Back OK 39 degrees
C / 102 degrees F
CPU0 Temp OK 70 degrees
C / 158 degrees F
CPU1 Temp OK 61 degrees
C / 141 degrees F
Best regards.
Le 22 nov. 2017 à 21:53, Adam Armstrong
<mailto:adama@observium.org>> a écrit :
What is the inventory entry referred to by the
indexes 9.1.0.0 and 9.2.0.0?
We should definitely already see temperatures from
here.
BTW, i honestly tend to ignore walks without MIBs
loaded. I can easily work out what a numerical OID is
from the text, but it's not so useful the other way.
adam.
Adam Armstrong
CEO & Lead Architect
Observium Limited
On 2017-11-22 19:29:22, Youssef BENGELLOUN - ZAHR
wrote:
Hi,
From Observium box, there you go :
root@prod-monit-002:~# snmpwalk -v 2c -c asp
fw01-par01 1.3.6.1.4.1.2636.4.1.2
SNMPv2-SMI::enterprises.2636.4.1.2 = No Such
Object available on this agent at this OID
⇒No answer regarding FANs.
root@prod-monit-002:~# snmpwalk -v 2c -c asp
fw01-par01 1.3.6.1.4.1.2636.3.1.13.1.7
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.1.1.0.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.1.2.0.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.2.1.1.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.2.1.2.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.2.2.1.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.2.2.2.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.7.1.0.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.7.2.0.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.8.1.1.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.8.2.1.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.9.1.0.0 =
Gauge32: 29
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.9.1.1.0 =
Gauge32: 0
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.9.2.0.0 =
Gauge32: 23
SNMPv2-SMI::enterprises.2636.3.1.13.1.7.9.2.1.0 =
Gauge32: 0
⇒Answers are returned regarding CPU temps.
Best regards.
Le 22/11/2017 20:23, « observium au nom de Michael
» a écrit :
Youseff,
By now you should know that there can be a world
of difference between what the cli of a device can
tell you and what it actually presents out the
snmp stack.
Try running the queries to the oids from a remote
host (such as from your observium box).
If it doesn't respond to the queries, there's not
much that can be done.
Michael
On 23 November 2017 6:02:39 AM AEDT, Youssef
BENGELLOUN - ZAHR wrote:
BENGELLOUN - ZAHR Youssef - Consultant Expert
Prodware France
T : +33 979 999 000 F : +33 988 814 001 -
Web : prodware.fr <http://prodware.fr>
*Youssef BENGELLOUN - ZAHR* - Consultant Expert
Prodware France
T : +33 979 999 000 - F : +33 988 814 001 -
------------------------------------------------------------------------
Web : prodware.fr <http://prodware.fr> <http://prodware.fr>
*Youssef BENGELLOUN - ZAHR* - Consultant Expert
Prodware France
T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
------------------------------------------------------------------------
Web : prodware.fr <http://prodware.fr> <http://prodware.fr>
*Youssef BENGELLOUN - ZAHR* - Consultant Expert
Prodware France
T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
------------------------------------------------------------------------
Web : prodware.fr <http://prodware.fr> <http://www.prodware.fr>
<http://twitter.com/Prodware/> <http://www.facebook.com/Prodware/>
BENGELLOUN - ZAHR Youssef - Consultant Expert
Prodware France
T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr
Web : prodware.fr <http://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
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
<mailto:observium@observium.org> <mailto:observium@observium.org>
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Mike Stupalov
Observium Limited, http://observium.org
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Mike Stupalov
Observium Limited, http://observium.org
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Mike Stupalov
Observium Limited, http://observium.org
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
*Youssef BENGELLOUN - ZAHR* - Consultant Expert
Prodware France
T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr
------------------------------------------------------------------------
Web : prodware.fr <http://www.prodware.fr>
<http://twitter.com/Prodware/> <http://www.facebook.com/Prodware/>
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Mike Stupalov
Observium Limited, http://observium.org
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--
Mike Stupalov
Observium Limited, http://observium.org
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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 listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
