No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Administrator Guide

OceanStor V3 Series V300R006

This document is applicable to OceanStor 2200 V3, 2600 V3, 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18500 V3, and 18800 V3. Routine maintenance activities are the most common activities for the storage device, including powering on or off the storage device, managing users, modifying basic parameters of the storage device, and managing hardware components. This document is intended for the system administrators who are responsible for carrying out routine maintenance activities, monitoring the storage device, and rectifying common device faults.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
About the eService

About the eService

The eService enables a storage system to upload its alarms and logs to eService. eService uses artificial intelligence (AI) technologies to implement intelligent fault reporting, real-time health analysis, intelligent fault prevention, and intelligent optimization, minimizing device running risks and reducing operational costs.

Positioning

Traditionally, alarms and logs are manually collected from storage systems and cannot be sent to Huawei technical support center in a timely manner. As a result, faults cannot be discovered promptly. The eService enables a storage system to periodically report alarms and logs. This helps eService analyze storage system's health status in real time, identify potential risks, automatically locate faults, and provide troubleshooting solutions, facilitating fault discovery and shortening troubleshooting time.

The eService securely connects a storage system and eService remotely deployed in Huawei technical support center.

  • The storage system encrypts alarms and logs and sends them to eService through encrypted channels over Internet. eService can receive alarm and log information from storage systems on a 24/7 basis, create orders within minutes, and automatically notify Huawei technical support personnel of exceptions in a timely manner.
  • Uploading of system logs must be manually configured. After technical support personnel configure system log collection tasks for a storage system on eService, the storage system periodically sends requests to eService for uploading system logs. If the eService is enabled, the storage system can upload collected system logs.

The eService uses the secure Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS). The eService allows a storage system to communicate with eService directly or through an internal HTTP proxy server. Figure 5-38 and Figure 5-39 illustrate the two types of networking.

Figure 5-38 Direct-connection networking
Figure 5-39 Internal HTTP proxy server deployed
NOTE:
  • If an internal HTTP proxy server is deployed for network access, ensure that the server is secure and reliable.
  • If neither of these two types of networking is supported, the eService Client can be deployed to upload storage alarms and logs to eService. For details, see the eService V2R2C00 User Guide.

Supported Data Types

After the eService is enabled, alarms and logs of storage systems can be uploaded to Huawei technical support center. Table 5-32 describes the data.

Table 5-32 Supported data types

Data Type

Description

Uploading Interval

Performance log

  • A .txt file in the JSON format
  • Performance logs of disks, controllers, LUNs, front-end port, storage pools, and disk domains

New performance logs are uploaded to eService every 5 minutes.

Operation log

  • A .txt file in the JSON format
  • Operation logs about device status and function modules. Function modules include controllers, enclosures, power supplies, BBUs, fans, disks, cascade modules, interface modules, ports, disk domains, storage pools, and LUNs.

Operation logs are uploaded to eService every 24 hours.

Alarm information

  • A .txt file in the JSON format
  • HTTP POST request, with the media type being application/json
  • Alarm information including the alarm ID, serial number, severity, parameters, time, and type
  • File

    New alarm information is uploaded to eService every 5 minutes.

  • HTTP POST request

    New alarm information is uploaded to eService every minute.

System log

  • A .tgz file
  • System logs including running data, event information, and debug logs about the storage system

Huawei technical support engineers manually trigger the uploading of system logs from eService to Huawei technical support center. In the current version, all system logs and system logs in the latest one hour, latest two hours, latest 24 hours, or a specific time period can be uploaded.

Diagnosis file

  • A .tgz file
  • Diagnosis file including device fault information
  • If alarms are generated on a storage system, the storage system uploads a diagnostic file at the maximum frequency of one time per hour.
  • If no alarm is generated on a storage system, the storage system uploads a diagnostic file every 24 hours.

DHA operation log

  • A .tgz file
  • DHA operation logs record daily operation information about disks, including health statistics, self-monitoring, analysis, and reporting technology (SMART), I/O statistics, and disk life information.

New DHA operation logs are uploaded to eService every 5 minutes.

NOTE:
  • The performance logs uploaded a time must not exceed 5 MB.
  • The DHA operation logs uploaded a time per controller must not exceed 2 MB.
  • There is no limit on the size of alarms, operation logs, system logs, and diagnosis logs to be uploaded.
Download
Updated: 2019-07-12

Document ID: EDOC1000138854

Views: 35735

Downloads: 2043

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next