Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c87bd7898a017be2475bca0007, userName='null'}
JIRAIDAUTHDSC-21148
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85e00fa, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc1e0747, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c8637b11640163b0313b5e004b, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cec20c77, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce5f0b98, userName='null'}

Internal_display_only
serverRibbon JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdd45d42c2-4546-3f1b-bbde-ff79196e8c48
keyDSC-22178


Panel

In this section:

Table of Contents

...

On the main page of each HWMON instance, the following information is provided:

  • For DSC 8000 and SP2000 (3U and 13U):The slot where the HWMON instance is running
    • The status (either Initializing or Running) of the instance
    • If the Debug-level logging is enabled or disabled 
    • A list of populated slots
  • For DSC 8000 only:
    • The slot where the HWMON instance is running
    • The state of the Critical, Major and Minor Telco Alarm Indicators
    • The Active MCH in the Control chassis
    • The Refresh Time indicating when the data retrieval started in the application
  • A list of populated slots

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.

...

  1. Login to the Web UI.

  2. From the Main Menu, click Hardware Monitor.

  3. Click the required Management Slot Number Number (2 14 or 1324). 
    Image RemovedImage Added

  4. Click the Slot Number you want to see the Hardware status for. 
  5. Click the required sensor (in this example the Threshold Sensor).


  6. Click on Read-Sensor button and confirm.

...

  1. Login to the Web UI.

  2. From the Main Menu, click Hardware Monitor.

  3. Click the required Slot Number.

  4. For the Debug Logging drop-down menu, select ENABLED.

    Info
    titleNote

    The Restore Debug Defaults action restores the Hardware Monitor logging configurations to their default values and clears the associated logging alarms.


  5. Click Continue.

...