flex50h temperature

Dpj

I think the 50h doesn't have an temperature sensor?

PeterUK

yes it might not use this in SSH

cmd cpu-temperature

Zyxel_Tina

Hi @Dpj,

Please use the following CLI command to check device's temperature:

cmd cpu-temperature

cmd fan-get

Dpj

Yes thx, but i was looking for an message in Nebula, so we can place triggers for our ticketing system. And i haven't seen those messages in the eventlogs of the Flex50h, like the Flex200 has.

Zyxel_Tina

Hi @Dpj,

Thanks for your feedback.

To help us clarify your request, could you please share a screenshot showing the event log entries you’re referring to on the FLEX 200 — specifically the ones that show CPU or sensor temperature information?

This would help us better understand the difference you're seeing compared to the FLEX 50H.

Dpj

Hello Tina,

this message is comming into nebula on the flex200: CPU Temperature: 76 degrees celsius.
on the USGflex50h, i don't see any message of temperature in the eventlogs. (at least till now). And the firewall is allready running for about 4 weeks at the customer.

Futher an other question:
About the API and Firmware

In nebula, you have a few states of firmware:
you can run latest firmware, you can run stable firmware, then you can run older firmware, or you can run out-of-date firmware.

But when request the API for the firmware update i have have this at the moment:

running latest firmware

    "currentVersion": "1.32(ACLO.0)",

    "latestVersion": "V1.32(ACLO.0)",

    "status": "UP_TO_DATE",

    "lastUpgradeTime": null

running stable firmware:


    "currentVersion": "V7.00(ACIL.1)",

    "latestVersion": "V7.10(ACIL.2)",

    "status": "NOT_UP_TO_DATE",

running old firmware:

        "currentVersion": "V4.50(ABKZ.2) | 08/30/2018",

        "latestVersion": "V5.00(ABKZ.1)",

        "status": "NOT_UP_TO_DATE",

So as you can see: i can see it's not the latest, and its not up to date. But that's it.

I think it would be better if it was formatted like this (for example)

"currentVersion": "V4.50(ABKZ.2) | 08/30/2018",        

"latestVersion": "V5.00(ABKZ.1)", 
"status": "NOT_UP_TO_DATE",
"Firmware-state: "Warning"

"currentVersion": "V7.00(ACIL.1)",

"latestVersion": "V7.10(ACIL.2)",

"status": "NOT_UP_TO_DATE",
"Firmware-state": "Stable"

"currentVersion": "1.32(ACLO.0)",
"latestVersion": "V1.32(ACLO.0)",
"status": "UP_TO_DATE",
"Firmware-state": "Latest"

and in case of an out of date firmware:

"Firmware-state": "Error"

We normally use Stable version, so in case of warning or error, we can create tickets in our ticketing system.

Dpj

or maybe use row names like in the nebula table:

status, and availability

Dpj

or (last comment ;) ) add an row:

latestversion:

stableversion

currentversion

status

Zyxel_Tina

Hi @Dpj,

Thanks for the detailed feedback!

Currently, the USG FLEX H series devices do not report CPU temperature to the NCC, so it's expected that you don't see temperature-related event logs on the USG FLEX 50H.

Regarding your second question —

Are you suggesting to include more specific information (such as "Latest", "Stable", "Warning", or "Error") in the API response — so it's easier to identify the firmware status of each device programmatically, especially when integrating with your ticketing system?

Dpj

Yes tina, that's right. We are working on a system to retrieve information from the api, to create tickets in our system. so you are correct.

We are missing quite a bit on the API's. but i understanded tha't is work in progress. (like creating organizations.) Zyxel melen told me allready, that's on the roadmap in the 3th quarter of this year. So that's great.

Further i'm missing an API to read the eventlogs of Access Points. But looking forward for the next upgrade of the API. Step by step.

Zyxel_Tina

Hi @Dpj,

Thank you for your feedback! As Nebula already shows AP event logs directly in the interface, could you please share more about your use case and why you prefer accessing logs via API polling? We’d appreciate it if you could share how you plan to use the AP logs through API. This will help us better understand your needs and forward them for future feature enhancements.