Collecting Information on DeviceManager
You can use DeviceManager to collect system data, alarms, and events in the storage system.
Exporting System Data
Periodically export the system data of a storage system and save it in a safe place. This helps you know the operating status of the storage system and prevent the damage to the storage system caused by system faults and unexpected disasters. When a system failure occurs, the exported system data can be used to locate and analyze the failure. The system data to be exported includes running data, system logs, disk logs, storage resource (for V500R007C20 and later), and diagnostic file (for V500R007C30 and later).
Context
- Running data indicates the real-time running status of a storage system, such as the configuration information of LUNs. The running data file is in *.txt format.
- System logs record the information about the running data, 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.
- 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 daily at 2 a.m.), I/O statistics (collected every 2 hours), and disk service life (collected daily at 2 a.m.). 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 per 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 collection start time of DHA logs.
- Recommended times of export during routine maintenance are listed in the following table. The analysis of DHA logs is only performed on samples instead of all logs. To prevent the analysis of DHA logs from affecting the entire routine maintenance, take the recommended values only for reference.
Disk Quantity in an Array
Maximum Number of Exports During an Inspection
0 to 200
3
200 to 500
4
500 to 1000
5
1000 to 2000
6
> 2000
6
- DHA runtime logs collect S.M.A.R.T/LogPage information (collected daily at 2 a.m.), I/O statistics (collected every 2 hours), and disk service life (collected daily at 2 a.m.). 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 per 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.
- An HSSD log is a working log of an HSSD. It contains the S.M.A.R.T information and run logs of the disk. The HSSD log file is in *.tgz format.
Before the download of system logs, DHA runtime logs, or HSSD logs, the system collects those logs of controllers and shows the collection progress. 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.
- In the storage resource file, you can easily view information about resources, including storage pools, LUNs, file systems, Qtrees, and quotas.
- Diagnostic files collect the device faults. The diagnostic files are in *.tgz format.
Procedure
- Log in to DeviceManager.
- Choose
Settings >
Export Data.
- Export data.
- In the Running Data area, click Download. Read 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 running data is exported.
- In the System Log area, select Recent logs or All logs, and click Log List. Read 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 DHA Runtime Log List. Read 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. Read 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.
- For V500R007C20 and later, in Storage Resource area, click Export Storage Resource. Read 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 storage resource configuration file is exported.
- For V500R007C30 and later, in Diagnostic File area, click Export. Read 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 faults information is exported.
- In the System Log area, if Recent logs is selected, the system exports recent logs that have been generated by the current point in time. The logs include the most recent 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 the data using the Internet Explorer browser with the default settings, the data will be saved in the download path which the user has selected. For example, you can choose Save > Save as in the displayed file download dialog box and select the download path in Internet Explorer 9 browser.
- If you export the 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 and click the General > Browser in the Options dialog box to view the default download path.
- If you export the 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 for the first time, click Allow if the This site is attempting to download multiple files. Do you want to allow this? message is displayed. Alternatively, go to the upper right corner of the browser, choose Customize and control Google Chrome > Settings > Privacy and security > 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. As a third alternative, you can delete Block from Behaviour and click Finished. Then, reopen the web page again and you can download multiple files. At this point, a message asking whether to allow multiple files to be downloaded will be displayed.
- If the exported logs cannot be viewed, export the logs again. If the new logs still cannot be viewed, contact Huawei technical support.
- In the Running Data area, click Download. Read the information in the security alert dialog box, select I have read and understand the consequences associated with performing this operation, and click OK.
- Click Close.
Exporting Alarms and Events
Alarms and events record the faults and events that occur during storage system operation. When the storage device is faulty, view the alarms and events to locate and rectify the fault.
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 another web browser, adjust the operations accordingly.
Precautions
Alarms and system logs are saved in *.xls files. After they are exported, do not modify the file content.
Procedure
- Go to the Alarms and Events page.
- On the right navigation bar of DeviceManager, click
Monitor.
- Click Alarms and Events.
The Alarms and Events page is displayed.
- On the right navigation bar of DeviceManager, click
- Export alarms and events.
- Click the Current Alarms or All Events tab. In the list, choose the 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.
- Click Save As. In the drop-down list, select Save Selected or Save All, and follow the instructions to save alarms and events.
- Click the Current Alarms or All Events tab. In the list, choose the alarms and events that you want to export.