05 eSCN230 Troubleshooting（16：9）(G02806197_OTHZH A)

eSCN230 Troubleshooting
Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
⚫ This course focuses on eSCN230 troubleshooting, including the troubleshooting procedures,
information collection methods, and typical fault analysis.
⚫ Typical faults of the eSCN230:
 Hardware faults.
 Transmission faults.
 eOMC interconnection faults.
 Service function faults.
Page 3 Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
⚫ Upon completion of this course, you will be able to:
 Understand the general troubleshooting procedure.
 Collect and analyze fault information.
 Diagnose typical system faults.
 Rectify typical faults.
Contents
1. Troubleshooting Overview
2. Fault Information Collection
3. Typical Fault Analysis
4. Technical Support
Troubleshooting Procedure
⚫ The general troubleshooting procedure is:
 Information Collection.
 Fault Diagnose.
 Fault Locating.
 Fault Rectification.
Mobile Intranet
General / Extranet Access
Troubleshooting Procedure
Collect Determine Locate the Rectify the

information. the fault type. fault cause. fault.
Information Collection
⚫ Collect the following information before troubleshooting an eSCN230:
 The symptom, time, location, and frequency of the fault.
 Affected areas and impact of the fault.
 Device operating status before the fault occurred.
 Operations performed on devices and corresponding results before the fault occurred.
 Alarms and indicator status when the fault occurred.
 Measures adopted and corresponding results after the fault occurred.
Fault Diagnose
⚫ Determine the fault scope and type:
 Determine the fault scope.
Correct fault scope judgment helps determine the direction of troubleshooting. Determining the fault
scope is the primary prerequisite for rapid troubleshooting.
 Determine the fault type.
The fault types are classified in terms of the service procedure and function module.
Fault Locating
⚫ Locating a fault is to find the cause of the fault from a number of causes. You can analyze and compare
the possible causes by using certain methods, exclude impossible factors, and then confirm the specific
cause of the fault.
⚫ Quickly locating faults can improve troubleshooting efficiency and prevent fault deterioration caused by
misoperation.
Fault Rectification
⚫ Fault rectification methods are as follows:
 Analyzing original information.
 Analyzing alarm information.
 Observing indicator status.
 Comparison and interchange.
 Switchover and restart.
 Analyzing signaling.
 Querying logs.
Contents
Checking Alarms on the eLMT
⚫ In the eLMT main window, click Alarm/Event. In the displayed Alarm/Event window, click the Browse
Alarm/Event tab.
Alarm Information and Handling Suggestions
⚫ To view detailed information about an alarm, double-click the alarm record.
⚫ The Detailed Information dialog box is displayed.
Querying Alarm Logs
⚫ In the eLMT main window, click Alarm/Event, and then click the Query Alarm/Event Log tab in
the Alarm/Event window.
1
2
One-Click Log Collection
⚫ Log in to the eLMT and run the MML command ULD FILE. Select BRDLOG(BRDLOG) from the File Type
drop-down list.
⚫ You can view the upload progress. After it reaches 100%, the file is successfully uploaded. The collected
file is saved in the root directory of the specified FTP server (generally the eOMC).
Configuration File Collection
⚫ The configuration file of an eSCN230 include all configuration data of the site and can be backed up,
uploaded or downloaded. The procedure of configuration file collection is as follows:
1. Run the MML command BKP CFGFILE.
2. Run the MML command ULD CFGFILE.
Message Tracing
⚫ Based on the preliminary determination on the

fault scope, trace the interface, signaling link, user
and internal messages. The system can analyze
the reported messages and display the IEs carried
by the messages, helping fault locating.
⚫ The traced messages can be saved for later view.
Network Analysis
⚫ If any link is faulty, you can run the PING command to inspect the physical connectivity of the
network to locate the failure cause.
⚫ Running the MML command PING:
Contents
Optical Module Fault Hardware faults
Transmission
O&M faults Service faults
faults
⚫ Fault Symptom
 The transmission link where a faulty port resides is unavailable.
 If a backup port or a backup route is configured for the faulty port, services carried on the faulty port
are automatically switched to the backup port or backup route.
 If load sharing is configured on the faulty port, the total available bandwidth for transmission and the
service throughput decrease.
⚫ Possible Cause
 The optical module on the transmission port of the board is faulty.
 Hardware fault alarms related to the board are generated on the NE.
Board Hardware Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 A board cannot work properly, which may interrupt the services carried on the board.
 Some functions of the board are unavailable. The reliability of the board decreases, and services
carried on the board may run improperly.
⚫ Possible Cause
 The board temperature is abnormal.
 Board hardware is faulty.
Board Offline Hardware faults
Transmission
faults
⚫ Fault Symptom
 A board cannot work properly, interrupting the services carried on the board.
⚫ Possible Cause
 The board is not inserted or is not securely inserted.
 The slot that houses the board on the backplane is faulty.
 Board hardware is faulty.
 The main control board in the subrack housing the faulty board is not securely inserted.
 The hardware of the main control board is faulty.
Ethernet Link Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 The services carried on an Ethernet link are interrupted.
⚫ Possible Cause
 Parameter values are set inconsistently on Ethernet ports at both ends.
 The Ethernet transmission link is abnormal.
 The local Ethernet port is faulty.
 The peer Ethernet port is faulty.
SCTP Link Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 A Stream Control Transmission Protocol (SCTP) link cannot carry signaling.
⚫ Possible Cause
 The SCTP bearer link is faulty.
 Parameter configurations at the two ends are inconsistent.
 The route to the peer end is unreachable.
 The peer device is faulty.
SIP Link Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 Group and P2P services are unavailable.
⚫ Possible Cause
 No route is configured.
 Port configurations do not match the physical ports.
 Ethernet cables are connected incorrectly.
 The port is faulty.
 Ethernet cables are faulty.
 The peer eMDC610 works abnormally.
Diameter Link Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 If multiple Diameter links are configured between the eCN and the peer end, loads of the fault link
are shared by other links, resulting in load increase on other links. If only one Diameter link is
configured between the eCN and the peer end, services between the eCN and the peer end are
interrupted.
⚫ Possible Cause
 The Diameter bearer link is faulty.
 Parameter configurations at the two ends are inconsistent.
 The route to the peer end is unreachable.
 The peer device is faulty.
 The eSCN230 initiates a link disconnection request after detecting a fault.
 The peer device initiates a link disconnection request after detecting a fault.
OMCH Fault Hardware faults
Transmission
faults
⚫ Fault Symptom
 Equipment cannot be maintained remotely because the OMCH is disconnected.
⚫ Possible Cause
 No OMCH is configured or the OMCH is configured incorrectly.
 The transport network is faulty.
 The eOMC works improperly.
 Security authentication fails.
Locked Address Pool Hardware faults
Transmission
faults
⚫ Case
 A UE fails to connect to the network. The GW sends the MME a session creation response message
CREATE_SESSION_RSP carrying the failure cause value 94. The SM sends the default bearer creation
failure message CREATE_DEFAULT_BEARER_FAIL to the MM.
⚫ Analysis
 Check whether all UEs cannot access the network.
 If only some UEs cannot access the network, check whether the registration data is correct.
 Check whether the address pool is locked.
Unmatched Mediation Hardware faults
Transmission
faults
⚫ Case
 In project XX, NE mediations are imported to the eOMC after the eOMC (PC edition) is re-installed.
The eOMC connects to the eNodeBs and eAPP NEs properly, but cannot connect to the eSCN230.
⚫ Alarm
 The alarm on link disconnection between the eSCN230 and the eOMC is reported.
⚫ Analysis
 Check whether eOMC has connected to all NEs properly before the re-installation.
 Check whether the eOMC can ping the IP address of the eSCN230 after the re-installation.
 Run the LST WOEKMODE command to check whether the working mode of the eSCN230 is consistent
with the mediation.
Incorrect APN Address Pool Binding
Transmission
Hardware faults O&M faults Service faults
faults
⚫ Case
 In project XX, after a cell is established successfully, the SIP link and SCTP link are in normal state.
However, the signal bar of the UE is empty and the UE screen displays “No Signal“.
⚫ Analysis
 Check whether all UEs cannot access the network.
 Check whether the registration data is correct.
 Trace signaling over the air interface.
 Check the eSCN230 configuration.
Contents
Technical Support
⚫ You can contact the customer service center or local Huawei office to obtain technical support.
⚫ Contact information for Huawei customer service center:
 Telephone: 400-822-9999
 Email: support_e@huawei.com
 Get in touch with local Huawei offices on the website http://support.huawei.com/enterprise.
Summary
⚫ General procedures for troubleshooting eSCN230 faults.
⚫ eSCN230 fault information collection method.
⚫ Troubleshooting methods for typical eSCN230 faults.
⚫ Methods of obtaining Huawei technical support.
More Information
⚫ Huawei E-learning website
 http://support.huawei.com/learning/Index!toTrainIndex
⚫ Huawei Support website

 http://support.huawei.com/enterprise/servicecenter?lang=en
Thank You
www.huawei.com

05 eSCN230 Troubleshooting（16：9）(G02806197_OTHZH A)

Uploaded by

Copyright:

Available Formats

You might also like

05 eSCN230 Troubleshooting（16：9）(G02806197_OTHZH A)

Uploaded by

Document Information

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

05 eSCN230 Troubleshooting（16：9）(G02806197_OTHZH A)

Uploaded by

Copyright:

Available Formats

eSCN230 Troubleshooting

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

2. Fault Information Collection

3. Typical Fault Analysis

Collect Determine Locate the Rectify the

2. Fault Information Collection

3. Typical Fault Analysis

2. Run the MML command ULD CFGFILE.

⚫ Based on the preliminary determination on the

2. Fault Information Collection

3. Typical Fault Analysis

2. Fault Information Collection

3. Typical Fault Analysis

⚫ Huawei Support website

You might also like