| #
4c62fc77 |
| 14-Feb-2024 |
Matt Spinler <spinler@us.ibm.com> |
monitor: Add fan_frus_with_nonfunc_rotors cause
Create a new power off rule to power off when a specific number of fan
FRUs have nonfunctional rotors. With this rule failing rotors can be
treated d
monitor: Add fan_frus_with_nonfunc_rotors cause
Create a new power off rule to power off when a specific number of fan
FRUs have nonfunctional rotors. With this rule failing rotors can be
treated differently when they are spread across fans FRUS than when they
are within the same fan FRU.
For example, if both rotors of a 2 rotor fan fail the system can stay
up, but if 2 rotors in separate fans fail then the system could be made
to power off.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia1d13596a9e8a6e3a361e5b631699a3c80e36fb8
show more ...
|
| #
00237439 |
| 14-Oct-2020 |
Matt Spinler <spinler@us.ibm.com> |
monitor: Create PowerOffCause class hierarchy
The PowerOffCause base class and its derived classes will be used to
determine when a power off needs to be done based on fan failures.
The 'satisified
monitor: Create PowerOffCause class hierarchy
The PowerOffCause base class and its derived classes will be used to
determine when a power off needs to be done based on fan failures.
The 'satisified()' method, which takes the fan health map, is used to
say if the cause is satisfied and a shut down will need to occur.
It provides two types of causes:
* MissingFanFRUCause - Looks at missing fan FRUs
* NonfuncFanRotorCause - Looks at nonfunctional rotors (sensors)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3c43347782dc559eb7c7441bf9c03d3407b248e2
show more ...
|