Creating Hard Shutdown interfaces/alarm for NIC Sensor

Creating Hard Shutdown interfaces/alarm for NIC Sensor

[Kumar Thangavel]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Hi All,



         We have an use case of NIC sensor value goes above 120 (upper non
recoverable), need to shutdown the slots.



         Critical and Warning interfaces and alarm created based on the
sensor threshold Severity value. Please refer the below code.


https://github.com/openbmc/dbus-sensors/blob/master/src/Thresholds.cpp#L116



         For NIC sensor, planning to create soft and hard shutdown
interfaces and alarm based on severity value in hwmonTempSensor.



         Already we have Severity 0  for Warning and Severity 1 for
Critical.

         We can have Severity 2 for Softshutdown and Severity 3 for
Hardshutdown.



         So, Based on the Severity value, the soft and hard shutdown alarm
will set as true.

         Then the sensor-monitor application would take the action based on
the soft/hard shutdown alarm.


         Could you please provide your suggestions on this.



Thanks,

Kumar.

[-- Attachment #2: Type: text/html, Size: 3181 bytes --]

Re: Creating Hard Shutdown interfaces/alarm for NIC Sensor

[Kumar Thangavel]

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Hi All,

        Gentle Reminder.  Any suggestions/idea on this.

Thanks,
Kumar

On Wed, Aug 11, 2021 at 4:51 PM Kumar Thangavel <
kumarthangavel.hcl@gmail.com> wrote:

> Hi All,
>
>
>
>          We have an use case of NIC sensor value goes above 120 (upper non
> recoverable), need to shutdown the slots.
>
>
>
>          Critical and Warning interfaces and alarm created based on the
> sensor threshold Severity value. Please refer the below code.
>
>
> https://github.com/openbmc/dbus-sensors/blob/master/src/Thresholds.cpp#L116
>
>
>
>          For NIC sensor, planning to create soft and hard shutdown
> interfaces and alarm based on severity value in hwmonTempSensor.
>
>
>
>          Already we have Severity 0  for Warning and Severity 1 for
> Critical.
>
>          We can have Severity 2 for Softshutdown and Severity 3 for
> Hardshutdown.
>
>
>
>          So, Based on the Severity value, the soft and hard shutdown alarm
> will set as true.
>
>          Then the sensor-monitor application would take the action based
> on the soft/hard shutdown alarm.
>
>
>          Could you please provide your suggestions on this.
>
>
>
> Thanks,
>
> Kumar.
>

[-- Attachment #2: Type: text/html, Size: 3716 bytes --]

Re: Creating Hard Shutdown interfaces/alarm for NIC Sensor

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Mon, Aug 16, 2021 at 09:27:58PM +0530, Kumar Thangavel wrote:
>         Gentle Reminder.  Any suggestions/idea on this.

Hi Kumar,

Can you frame your original email with a question?

I'm not versed in the details here enough to know what you're underlying
concern is.  When I read the email I see mostly a list of "facts".

I suspect others are similarly not responding because they don't know what you
want to know or where your doubts are.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Creating Hard Shutdown interfaces/alarm for NIC Sensor

[Ed Tanous]

On Mon, Aug 16, 2021 at 11:54 AM Patrick Williams <patrick@stwcx.xyz> wrote:
>
> On Mon, Aug 16, 2021 at 09:27:58PM +0530, Kumar Thangavel wrote:
> >         Gentle Reminder.  Any suggestions/idea on this.
>
> Hi Kumar,
>
> Can you frame your original email with a question?
>
> I'm not versed in the details here enough to know what you're underlying
> concern is.  When I read the email I see mostly a list of "facts".
>
> I suspect others are similarly not responding because they don't know what you
> want to know or where your doubts are.

I wasn't responding because there's been several discussions on almost
this exact use case, as well as patchsets to add the new types and
interfaces.  To reiterate Patricks comment, I was hoping you'd search
for them and either jump into those discussions where the work is
being done, or propose some more pointed questions once you got more
versed on what already exists along those lines.

>
> --
> Patrick Williams