2.5. ST1X02 OceanStor V3 Converged Storage Systems Troubleshooting PDF

OceanStor V3 Converged
Storage Systems
V300R001&V300R002
Troubleshooting
www.huawei.com
Copyright © 2017 Huawei Technologies Co., Ltd. All rights reserved. Page 0
Objectives
 After completing this course, you will be able to know:
 Methods for troubleshooting the common faults on OceanStor V3
converged storage systems
 Detailed operations for troubleshooting OceanStor V3 converged

storage systems
1
Contents
1. Common faults
2. Methods and process
3. Case study
Common faults
 Hardware module faults
 Installation and initial configuration faults
 UltraPath faults
2
Hardware module faults
 Overview
When a hardware module is faulty, its indicator becomes abnormal.
 Common faults
1. Disk enclosure faults
2. Expansion module faults
3. Power module faults
4. Interface module faults
 Common troubleshooting method

When hardware becomes faulty, an alarm is generated. You can view the alarm
information to locate the faulty hardware and then reinsert or replace it.
Installation and initial configuration faults

 Overview
Storage systems cannot be managed or maintained.
 Common faults For example:

1. Check whether you can log in using a serial port.
1. Remote modem dialup failure 2. Check whether the baud rate is correct.
3. For a Windows-based host, check whether the
2. Login failure through a serial port COM port is occupied.

The preceding faults are caused by incorrect serial cable connection or serial port
parameter settings. You can reinsert the serial cable or reset serial port parameters.
Note: Typical serial port parameter settings are as follows:
Baud rate: 115200; Data bit: 8; Parity check: No; Stop bit: 1
3
UltraPath faults
 Overview
UltraPath malfunctions, reducing storage performance.
 Common faults
1. Failure to load UltraPath after an application server is restarted
2. Failure to discover multiple paths on a SUSE application server
3. Blue screen during UltraPath installation on a Windows application server

The typical cause is that UltraPath is blocked because the server startup items do not
include UltraPath information or the HBA driver has a failover function. To resolve the
problem, unblock UltraPath.
At the same time, check whether:
1. Links are abnormal.
2. Switches are faulty.
3. Controllers are faulty.
Contents
1. Common faults
3. Case study
4
Methods and process
 Flowchart
Troubleshoot faults by following the troubleshooting flowchart.
 Basic rules
Basic fault locating rules help users quickly exclude useless information and locate faults.
 Alarm analysis method

Analyze alarms to troubleshoot faults.
 Replacement
Troubleshoot faults by replacing components of a storage system.
Flowchart
5
Basic rules
 Analyze external factors and then internal factors.
1. External factors include failures in optical fibers, optical cables, power supplies, and customers'
devices.
2. Internal factors include failures in disks, controllers, and interface modules.
 Analyze alarms with higher severities and then alarms with lower severities.
Analyze high-severity alarms and then low-severity alarms. The alarm severity sequence from high to
low is critical alarms, major alarms, and warnings.
 Analyze common alarms and then uncommon alarms.

When analyzing an alarm, confirm whether it is an uncommon or common fault and then determine
its impact. Determine whether the fault occurred on only one component or on multiple components.
Alarm analysis method

 Overview
When a system is faulty, many alarms are generated. By viewing alarm information and analyzing
performance data, the type and location of the fault can be determined roughly.
 Application scenario
If alarm information can be collected, the alarm analysis method can be used to locate any faults.
 Summary
By analyzing alarms, you can locate a fault or its cause. You can also use the alarm analysis method
along with other methods to locate a fault.
6
Replacement method
 Overview
A fault can be located and rectified by replacing components suspected to be faulty.
 Application scenario
This method helps quickly locate faulty components during hardware troubleshooting. The limitation
of this method is that you must prepare spare parts in advance. Therefore, you need to make full
preparations.
 Summary
Advantages of the replacement method are quick and accurate fault location and moderate
requirements on maintenance personnel.
Contents
1. Common faults
3. Case study
7
Case study
 BBU failure
 Inserted disk in the offline state on DeviceManager
 Unable to start DeviceManager when proxy is enabled on the maintenance

terminal
 DeviceManager failure to be loaded or be displayed incorrectly
 Failure to add an iSCSI link to a remote device
 UltraPath unavailable because it is isolated by the antivirus software
 Blue screen during UltraPath installation on a Windows application server
BBU failure
 Symptom
On DeviceManager, the health status of a BBU is Faulty.
 Fault diagnosis
A BBU is faulty. The possible cause is that the BBU is not correctly connected or the BBU does not
function properly.
 Recommended actions
1. View the BBU failure alarm to locate the faulty BBU. Then reinserted the BBU.
2. On DeviceManager, check the BBU health status.
3. If the BBU health status becomes normal, the fault has been rectified. Otherwise, replace the BBU.
If the problem persists, maintain the fault environment and contact Huawei technical support.
8
Disk in the offline state
 Symptom
On DeviceManager, the running status of a disk is Offline.
 Fault diagnosis
The possible cause is the disk media failure or disk hardware failure.
 Recommended action
After a disk failure alarm is generated, locate the failed disk according to the enclosure ID and slot ID
provided in the alarm and then replace the disk. Alternatively, you can maintain the fault environment
and contact Huawei technical support.
Unable to start DeviceManager

 Symptom
After a user enters the management network port IP address of a storage system, the DeviceManager
login page is not displayed.
 Fault diagnosis
By checking the proxy settings in the Internet options of Firefox, it is found that the proxy server is
enabled and the URL of the device is not added to the Exceptions list.
Disable the Firefox proxy server settings.
 Summary
It is recommended that before logging in to DeviceManager, disable the proxy server or add the
management network port IP address of the storage system to the Exceptions area.
9
Unable to load the DeviceManager page
 Symptoms
1. The DeviceManager page is being loaded and a blank screen is displayed.
2. Log in to DeviceManager and go to the device view. When the device view is being loaded, click
other navigation paths for several times. The tab page of the web browser breaks down occasionally.
 Fault diagnosis
1. The network is faulty.
2. The web browser is incompatible with the operating system.
Load the page again.
Failure to add an iSCSI link to a remote

device
 Symptoms
When an iSCSI link is added to the remote device immediately after the iSCSI initiator is renamed, a
message is displayed sta ng The communica on is abnormal or the system is busy.
 Fault diagnosis
An iSCSI link is added to the remote device within 30 seconds after the iSCSI initiator is renamed.
1. Delete the existing iSCSI link from the remote device.
2. Add an iSCSI link 30 seconds later.
 Summary
After renaming the iSCSI target, wait more than 30 seconds before adding a link to the remote device.
10
UltraPath failure
 Symptom
UltraPath installed on an application server is automatically isolated by the antivirus software. As a
result, it cannot be used.
 Fault diagnosis
The antivirus software incorrectly takes UltraPath as a virus and isolates it.
1. On the management page of the antivirus software, add UltraPath as a trusted software application.
2. Restart the antivirus software.
 Summary
Before installing UltraPath, disable the antivirus software. After installing the UltraPath, start the
antivirus software and add UltraPath as a trusted software application.
Blue screen during UltraPath installation

 Symptom
An exception occurs during UltraPath installation on a Windows server, which leads to blue screen.
 Fault diagnosis
The latest patch is not installed on the Windows operating system.
1. Restore to the latest correct configuration.
2. Install the latest path for the Windows operating system.
 Summary
Install the latest path for the Windows operating system before installing UltraPath.
11
Summary
 Common faults
 Methods and process
 Case study
Exercises
1. (Multiple-answer question) Which of the following are the common faults?
A. DeviceManager operation faults
B. Hardware module faults
C. Installation and initial configuration faults
D. UltraPath faults
2. (Multiple-answer question) Which of the following are the common troubleshooting methods?
A. Alarm analysis method
B. Replacement method
3. (Multiple-answer question) Which of the following are the troubleshooting rules?
A. Analyze external factors and then internal factors.
B. Analyze alarms with higher severities and then alarms with lower severities.
C. Analyze common alarms and then uncommon alarms.
12
Thank you
www.huawei.com
13

2.5. ST1X02 OceanStor V3 Converged Storage Systems Troubleshooting PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2.5. ST1X02 OceanStor V3 Converged Storage Systems Troubleshooting PDF

Uploaded by

Copyright:

Available Formats

OceanStor V3 Converged

 Detailed operations for troubleshooting OceanStor V3 converged

2. Methods and process

 Installation and initial configuration faults

2. Expansion module faults

3. Power module faults

4. Interface module faults

 Common troubleshooting method

Installation and initial configuration faults

 Common faults For example:

 Common troubleshooting method

2. Failure to discover multiple paths on a SUSE application server

3. Blue screen during UltraPath installation on a Windows application server

 Common troubleshooting method

2. Methods and process

 Alarm analysis method

2. Internal factors include failures in disks, controllers, and interface modules.

 Analyze common alarms and then uncommon alarms.

Alarm analysis method

2. Methods and process

 Inserted disk in the offline state on DeviceManager

 Unable to start DeviceManager when proxy is enabled on the maintenance

 DeviceManager failure to be loaded or be displayed incorrectly

 Failure to add an iSCSI link to a remote device

 UltraPath unavailable because it is isolated by the antivirus software

 Blue screen during UltraPath installation on a Windows application server

2. On DeviceManager, check the BBU health status.

Unable to start DeviceManager

2. The web browser is incompatible with the operating system.

Failure to add an iSCSI link to a remote

2. Add an iSCSI link 30 seconds later.

2. Restart the antivirus software.

Blue screen during UltraPath installation

2. Install the latest path for the Windows operating system.

 Methods and process

B. Hardware module faults

C. Installation and initial configuration faults

You might also like