Professional Documents
Culture Documents
Code
Issue 011
Date 2021-09-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either expressed or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Email: support@huawei.com
Approved by Huawei
Contents
1 Basic Information
CloudePDG V100R019C10SPC600
2 Problem Description
The customer described that some users cannot connect to the VoWi-Fi network.
Some users can successfully access the Wi-Fi network sometimes but cannot access the Wi-Fi network sometimes.
3 Problem Analysis
According to the initial symptom, no IKE request message is found in the SWU interface tracing result. Therefore, we
need to locate where packet loss occurs. The Datacom tracing result shows that the number of requests is greater than
the number of responses.
According to the IP tracing result, these requests from Datacom are also uploaded to the IP tracing result.
After tracing the two devices, it is found that the VNRS forwards data from all devices on the datacom side to
the CSLB.
After receiving a message from the VNRS, the CSLB sends the message to the service VNFC one by one.
However, only a few messages are found in the SWU interface tracing result.
Therefore, the analysis packets should be lost between the CSLB and ePDG. The collected statistics show that
the PF module sends 341212 packets to the AM module within 5 minutes.
3317915274-3317574062=341212
3298206277-3297865077 = 341200
The statistics are not collected at the same time. Therefore, we compare the statistics based on the time
segment and order of magnitude. We consider that no packet loss occurs in the IKE message from the left to the
AM module.
We also find that a large number of discard IKE messages are counted for wal flow control in AM.
The number of IKE messages discarded by the ePDG increases sharply in the afternoon of June 6 due to CPU
overload.
We see that CPU usage is around 85% due to the previous problem. In the afternoon of September 6, the
number of requests increased sharply, causing the CPU usage to increase to 98%.
4 Root Cause
Mechanism:
1. When the system CPU usage is less than 85%, the WAL is adjusted every 6s.
2. When the system CPU usage is higher than 85%, if the current CPU usage is greater than the previous CPU usage,
the CPU usage increases continuously. In this case, you need to adjust the WAL immediately.
When the CPU level changes, adjust the wal value (for example, > 95%): Current wal x (100 + (- 5))/100 = wal x 95%
The wal value decreases to 95% compared with that in the previous period.
Based on the preceding analysis, we suspect that the IKE messages are discarded due to CPU overload.
5 Solution
We will release a new patch to solve the CPU overload problem in about final days of September . The patch version
is 19.1SPC600+SPH627. Before this, you are advised to perform capacity expansion if you want to rectify the fault. The
SDN network is used. Therefore, recommend perform capacity expansion on the NFVO based on the guide.