Hurray!

Though we shouldn't forget that these idiot vendors shouldn't be releasing products with such poor manageability in the first place!

Adam.

Sent from BlueMail
On 21 May 2018, at 00:33, Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr> wrote:

Hello,

 

I just upgraded our cluster during a maintenance window and I can confirm that is working perfectly :

 

  • FAN monitoring :

 

 

  • DOM is working perfectly for all interfaces (but not dedicated HA ports, ER open) and all type of transceivers (grey and colored xWDM) :

 

 

 

The rest will follow depending on Juniper’s pace / good will.

 

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 17 avril 2018 à 10:23
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing

 

Hello all,

 

D131 has just been release with the crappy temporary fix :

 

“This is a service release as the mainline release (D140) is tentative on May end.  This have the temporary fix since creation for  individual MIB will take time as this need changes across multiple platforms . 

 

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”

 

The official fix (creation of a dedicated MIB) will be coming in the (near ?!?) future. This can be tracked under RLI 38511 ||  PR1348085.

 

Best regards.

 

 

 

De : Youssef BENGELLOUN - ZAHR <ybzahr@prodware.fr>
Date : mercredi 28 mars 2018 à 11:21
À : Observium <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing

 

Hello Tom,

 

Makes total sense to me as well. I’ll pass that on.

 

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 à 11:19
À : "observium@observium.org" <observium@observium.org>
Objet : Re: [Observium] SRX4200 FAN status missing

 

Youssef,

I would say they'd need to add a new OID for RPM to their MIB.

They have a table (jnxOperatingTable) which consists of jnxOperatingEntry entries, which contain:
- jnxOperatingDescr ("Fan Tray 0")
- jnxOperatingState ("running")
(and some other things)

for CPUs they have
- jnxOpeartingCPU to show CPU usage

for things with a temp sensor they have
- jnxOperatingTemp to show temperature

so it makes sense to me for fanspeeds they'd have
- jnxOperatingSpeed or jnxOperatingFanspeed or jnxOperatingRPM or ... to show fan RPM.

Tom

On 03/28/2018 10:34 AM, Youssef BENGELLOUN - ZAHR wrote:

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

cid:part2.07AEE8C1.41B50A8D@powersource.cx

Web : prodware.fr cid:part4.18BACC5F.EA87DC14@powersource.cx  cid:part6.B29F0C5B.07BC0C64@powersource.cx  cid:part8.F7041446.ECE495DC@powersource.cx  cid:part10.23ED15E9.CEF25049@powersource.cx  cid:part12.D5549606.69E637FE@powersource.cx  cid:part14.2D6A3F5D.47765161@powersource.cx

 

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.

 






observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium