Collecting Logs and Alarms Using DeviceManager

Context

• System logs record the information about the configuration information, events, and debugging operations on a storage system and can be used for analyzing the running status of the storage system. The system log file is in *.tgz format.
• Configuration information indicates the real-time running status of a storage system and includes user information and LUN configuration information. The configuration information file is in *.txt format.
• DHA runtime logs are disks' daily running logs, including daily disk health statistics, I/O statistics, and disk service life. The DHA runtime log file is in *.tgz format.
  • DHA runtime logs collect S.M.A.R.T/LogPage information (collected at 2 o'clock every morning), I/O statistics (collected every 2 hours), and disk service life (collected at 2 o'clock every morning). A log package (1 KB) is generated for each disk each day. A controller can generate a maximum of 74 log packages for each of the disks belonging to it within a year (some old log packages will be deleted during the collection). In a log package export, packages corresponding to each controller are generated. Each package contains log packages and one basic information file about each disk belonging to the corresponding controller.

    You can run the change dha policy collect_start_time=? command in developer mode in the CLI to change the start time for collecting DHA runtime logs.

  • The analysis of DHA runtime logs is only performed on samples instead of all logs. The recommended maximum times of export during routine maintenance are listed in the following table.

    Disk Quantity in a Storage System	Recommended Maximum Times of Export During an Inspection
    0 to 200	3
    200 to 500	4
    500 to 1000	5
    1000 to 2000	6
    >2000	6

  • HSSD logs are HSSDs' working logs, including the S.M.A.R.T information and disk running logs. The HSSD log file is in *.tgz format.

    In the event of downloading system logs, DHA runtime logs, or HSSD logs, the system first collects those logs of controllers and displays the collection progress about each controller. After all logs are collected, you can download your desired logs.

    After the system starts collecting system logs, DHA run logs, or HSSD logs, you need to wait for five minutes or download all the collected logs before you collect and download other logs.

• Diagnostic files collect the device faults. The diagnostic files are in *.tgz format.

Procedure

1. Log in to DeviceManager.
2. Choose > Export Data.
3. Export data.
   • Select System Log area, and click Recent logs or All logs. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The system starts collecting logs.

   • In the Configuration Info area, click Export. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The system configuration information is exported.

   • In the Disk Log area, click DHA Runtime Log List. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The system starts collecting logs and expands the log list.

   • In the Disk Log area, click HSSD Log List. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The system starts collecting logs and expands the log list.

   • In the Disk Log area, click Disk Data Erasure Report. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The system starts collecting report.

   • In the Diagnostic File area, click Export. Confirm the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.

     The device's fault information is exported.

   • In the System Log area, if Recent logs is selected, the system exports recent logs that have been generated till the current point in time. The logs include the latest one power-on and power-off log and a maximum of six messages logs. If All logs is selected, the system exports all logs on the current node. Note that historical messages logs are saved to the /OSM/coffer_log/log/his_debug directory.
   • If you export data using the Internet Explorer browser with the default settings, the data will be saved in the download path selected by the user. For example, in Internet Explorer 9, you can choose Save > Save as in the displayed file download dialog box and select a download path.
   • If you export data using the Firefox browser with the default settings, the data will be saved in the default download path of the browser. You can choose Tools > Options to open the Options dialog box and then choose General > Browser in the Options dialog box to view the default download path.
   • If you export data using the Google Chrome browser with the default settings, the data will be saved in the default download path of the browser. You can choose Customize and Control Google Chrome > Settings and view the default download path in the Download Content area of the Settings page.
   • When using Chrome to export data for the first time, click Allow if the This site is attempting to download multiple files. Do you want to allow this message? message is displayed. Otherwise, at the upper right corner of the browser, choose Customize and control Google Chrome > Settings > Privacy > Content Settings... > Automatic downloads > Manage exceptions, select Allow in Behaviour, and click Finished. Then, reopen the web page and you can successfully download multiple files. Alternatively, delete Block from Behaviour and click Finished. Then, reopen the web page again and you can download multiple files. In such a case, a message asking whether to allow multiple files to be downloaded will be displayed.

Context

Specify the alarms to be exported by setting the alarm severity or time of occurrence.

This document uses Internet Explorer on a Windows server as an example. If you are using other web browsers, adjust the operations accordingly.

Precautions

Alarms and system events are saved in *.xls files. After they are exported, do not modify the file content.

Procedure

1. Choose Insight > Alarm and Events.

   The Alarms and Events page is displayed.

2. Export alarms and events.
   1. Click the Current Alarms or All Events tab. In the list, choose alarms and events that you want to export.
      • On the Current Alarms tab page, critical alarms, major alarms, and warnings are displayed.
      • You can export all or specified entries on the Current Alarms tab page.
      • On the All Events tab page, alarms of all severities are displayed. Alarms on the Current Alarms tab page are exported to All Events.
      • You can export all or specified entries on the All Events tab page.
      • To export alarms or events of a specific severity, set the filter condition before exporting them.
   2. Click .

      The Save As dialog box is displayed. Select a save path and click Save.