Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Internal_display_only | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Panel | |
---|---|
In this section:
|
...
On the main page of each HWMON instance, the following information is provided:
When the HWMON starts up, its status is set to Initializing until all of the components available in the system have been discovered. Once all the components have been discovered, the status is set to Running. It is important to wait for the HWMON instance to transition to Running before depending on the information provided because the information may still be changing.
Normally HWMON logs errors and unexpected events, but a more verbose logging of activity may be enabled by changing the Debug Logging state to ENABLED, see To enable Debug Logging. When the Debug Logging is enabled, additional HWMON logs are written to /var/log/ptidbglog.
...
Each component includes sensors that provide information such as power state, hot-swap status, temperatures, voltages, currents, fan speeds, and so on. Any sensor value may be read through the Web UI, see To view Hardware Monitor information.
The MCH slots provide this information for the MCH slot themselves, and also provide this information for the power supplies, fans, and shelf where the MCH resides. To view information on one of these system components, select an object under Power Supply, Fan Tray or Shelf to inspect the manufacturing information, sensors, or firmware versions for that component. The information for the Power Supply, Fan Tray, and Shelf is identical for both MCH slots within the chassis where these components reside.
...
...
For the Debug Logging drop-down menu, select ENABLED.
Info | ||
---|---|---|
| ||
The Restore Debug Defaults action restores the Hardware Monitor logging configurations to their default values and clears the associated logging alarms. |
...